WO2015192295A1

WO2015192295A1 - Method and device for controlling qos of a service

Info

Publication number: WO2015192295A1
Application number: PCT/CN2014/079953
Authority: WO
Inventors: Zhengzheng Li; Haichao LI; Xiufeng Wu; Long Luo
Original assignee: Huawei Technologies Co., Ltd.
Priority date: 2014-06-16
Filing date: 2014-06-16
Publication date: 2015-12-23
Also published as: CN106465194B; CN106465194A

Abstract

Embodiments of the present application provide a method and a device for controlling QoS of a service. The service includes a GBR service having a first service stage and a second service stage. The method includes : obtaining a service type of the service; obtaining a first QoS requirement for the first service stage and a second QoS requirement for the second service stage; and generating indication information indicating the QoS first requirement for the first service stage, the second QoS requirement for the second service stage and a service stage sign used to identify the first service stage and the second service stage. The indication information is used to identify the service stage and generate a QoS policy so as to control QoS in the first service stage and QoS in the second service stage. According to the present application, resource is efficiently allocated while user experience is guaranteed.

Description

METHOD AND DEVICE FOR CONTROLLING QOS OF A

SERVICE

TECHNICAL FIELD

[0001] The present application relate to the field of communications technologies, and in particular, to a method and a device for controlling quality of service (QoS) of a service.

BACKGROUND

[0002] Evolved packet system (EPS) is a telecommunications system referring to the architecture designed for long term evolution (LTE) network. An EPS bearer is an internet protocol (IP) stream satisfying a certain quality of service (QoS) in the EPS, and includes a guaranteed bit rate (GBR) type bearer and a non-GBR type bearer. Specific resource is allocated to the GBR type bearer so that the bandwidth of the GBR type bearer is guaranteed, even when the network load is heavy or any congestion is occurred in the system. A non-GBR type bearer is a best effort type bearer and its bandwidth is not guaranteed. A GBR bearer is mainly used for real-time service such as voice over Internet protocol (VoIP) service, or on-line video or real-time games, while a non-GBR bearer is mainly used for non-real-time service such as Email, file transfer protocol (FTP) service, or hypertext transfer protocol (HTTP) service. The priority of a GBR service is higher than that of a non-GBR service.

[0003] GBR and maximum bit rate (MBR) are two QoS parameters used for a GBR service. GBR indicates the bandwidth (also known as bit rate) to be guaranteed by the LTE network, and MBR indicates the maximum bit rate allowed in the LTE network. The bit rate of the data stream is controlled above GBR while less than MBR to satisfy QoS requirement, which affects scheduling policy, queue management, rate shaping policy and radio link control (RLC) configuration for all end-to-end network nodes in the EPS.

[0004] However, QoS parameter such as GBR or MBR is set while a GBR type bearer is established for a GBS service. Therefore, either resource allocation is inefficient or user experience cannot be guaranteed. SUMMARY

[0005] Embodiments of the present invention provide a method and a device for controlling QoS of a service.

[0006] According to a first aspect, a method for controlling QoS of a service is provided. The service includes a GBR service having at least a first service stage and a second service stage. The method performed by a first device includes: the first device obtains a service type of the service. The first device obtains a first QoS requirement for the first service stage and a second QoS requirement for the second service stage according to the service type of the service. The first device generates first indication information indicating the QoS first requirement for the first service stage, the second QoS requirement for the second service stage and a service stage sign used to identify the first service stage and the second service stage. The first indication information is used to generate a QoS policy, so as to control QoS according to the first QoS requirement indicated in the QoS policy in the first service stage and control QoS according to the second QoS requirement indicated in the QoS policy in the second service stage.

[0007] In a first possible implementation form of the method according to the first aspect, the service stage sign is represented in form of any one or any combination of time of a data packet and packet capacity of the data packet.

[0008] In a second possible implementation form of the method according to the first aspect as such or according to the first implementation forms of the first aspect, the first indication information indicates the first QoS requirement for the first service stage and the second QoS requirement for the second service stage which are corresponding to a first rank of user experience of the service, and further indicates a third QoS requirement for the first service stage and a fourth QoS requirement for the second service stage which are corresponding to a second rank of user experience of the service.

[0009] According to a second aspect, a device for controlling QoS of a service is provided. The service includes a GBR service having at least a first service stage and a second service stage. The device includes a first obtaining unit, a second obtaining unit, and a generating unit. The first obtaining unit is configured to obtain a service type of the service. The second obtaining unit is configured to obtain a first QoS requirement for the first service stage and a second QoS requirement for the second service stage according to the service type of the service. The generating unit is configured to generate first indication information indicating the first QoS requirement for the first service stage, the second QoS requirement for the second service stage and a service stage sign used to identify the first service stage and the second service stage. The first indication information is used to generate a QoS policy, so as to control QoS according to the first QoS requirement indicated in the QoS policy in the first service stage and control QoS according to the second QoS requirement indicated in the QoS policy in the second service stage.

[0010] In a first possible implementation form of the device according to the second aspect, the service stage sign is represented in form of any one or any combination of time of a data packet and packet capacity of the data packet.

[0011] In a second possible implementation form of the device according to the second aspect or according to the first implementation form of the second aspect, the first indication information indicates the first QoS requirement for the first service stage and the second QoS requirement for the second service stage which are corresponding to a first rank of user experience of the service, and further indicates a third QoS requirement for the first service stage and a fourth QoS requirement for the second service stage which are corresponding to a second rank of user experience of the service.

[0012] These and other aspects of the invention will be apparent from the embodiments described below. According to the embodiments of the present application, the first device generates the first indication information indicating the different QoS requirements for different service stages and a service stage sign used to identify the different service stages. According to the first indication information, the first service stage and the second service stage are identified, and a QoS policy is generated to control QoS according to the first QoS requirement in the first service stage and control QoS according to the second QoS requirement in the second service stage. After receiving the QoS policy, each node in the EPS operates the service according to a QoS first requirement in the first service stage, and operates the service according to a second QoS requirement in the second service stage. Thus, different QoS requirements for different service stage of a service are met. Therefore, resource is efficiently allocated while user experience is guaranteed. BRIEF DESCRIPTION OF DRAWINGS

[0013] To illustrate the technical solutions in the embodiments of the present invention more clearly, the following briefly introduces the accompanying drawings required for describing the embodiments or the prior art. Apparently, the accompanying drawings in the following description show merely some embodiments of the present invention, and a person of ordinary skill in the art may still derive other drawings from these accompanying drawings without creative efforts.

[0014] FIG. 1 A illustrates a diagram of a method for establishing an EPS bearer;

[0015] FIG. IB illustrates a diagram of a method for modifying QoS parameter of the EPS bearer;

[0016] FIG. 2 A illustrates a diagram of a method for controlling QoS of a service, in accordance with one embodiment of the present invention;

[0017] FIG. 2B illustrates a method for controlling QoS of a service when a service identification module is integrated on a first device, in accordance with one embodiment of the present invention;

[0018] FIG. 2C illustrates a method for controlling QoS of a service when a service identification module is integrated on another first device, in accordance with one embodiment of the present invention;

[0019] FIG. 3Aand FIG. 3B, FIG. 3C and FIG. 3D illustrate four examples of the method for controlling QoS of a service, in accordance with one embodiment of the present invention, respectively;

[0020] FIG. 4A, FIG. 4B and FIG. 4C illustrate three examples of the method for controlling QoS of a service, in accordance with one embodiment of the present invention, respectively;

[0021] FIG. 5 illustrates a simplified block diagram of a device for controlling QoS of a service, in accordance with one embodiment of the present invention;

[0022] FIG. 6A, FIG. 6B and FIG. 6C illustrate three examples of the device for controlling QoS of a service, in accordance with one embodiment of the present invention, respectively; and

[0023] FIG. 7A and FIG. 7B illustrate simplified block diagrams of a second device for controlling QoS of a service, in accordance with one embodiment of the present invention, respectively.

DESCRIPTION OF EMBODIMENTS

[0024] The following clearly and completely describes the technical solutions in the embodiments of the present invention with reference to the accompanying drawings in the embodiments of the present invention. Apparently, the described embodiments are merely a part rather than all of the embodiments of the present invention. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments of the present invention without creative efforts shall fall within the protection scope of the present invention.

[0025] FIG. 1A illustrates a diagram of a method for establishing an EPS bearer and FIG. IB illustrates a diagram of a conventional method for updating the EPS bearer parameter. In the example shown in FIG. 1A and FIG. IB, the EPS 100 includes a user equipment (UE) 101, an eNodeB 102 (referred to as "e B" hereinafter), a mobility management entity (MME) 103, a serving gateway (SGW) 104, a packet data network gateway (PGW) 105, and a policy and charging rules function (PCRF) 106. By using the method as described below in FIG. 1 A and FIG. IB, a QoS policy generated by the PCRF 106 is transmitted to each other node in the EPS 100, e.g., the UE 101, the eNB 102, the MME 103, the SGW 104, or the PGW 105.

[0026] The PCRF 106 is configured to generate QoS policy dynamically and send the QoS policy indicating the QoS requirement for a service to the PGW 105. The PGW 105 is configured to perform the QoS policy. After the QoS policy is forwarded by the SGW 104 and the MME 103, the eNB 102 established a bearer with the UE 101 according to the QoS parameter.

[0027] For example, as illustrated in FIG. 1A, the method for establishing an EPS bearer requested by the network side includes:

[0028] In step 1 : the PCRF 106 generates QoS policy dynamically and sends the QoS policy indicating the QoS requirement for the service to the PGW 105 by initiating IP-connectivity access network (IP-CAN) session modification procedure.

[0029] In step 2: the PGW 105 uses this QoS policy to assign value to the QoS parameter of the EPS bearer and sends a create bearer request indicating the QoS parameter to the SGW 104.

[0030] In step 3 : the SGW 104 forwards the create bearer request to the MME 103.

[0031] In step 4: the MME 103 signals a bearer setup request message or a session management request indicating the QoS parameter for the EPS bearer, to the eNB 102.

[0032] In steps 5 and 6, the eNB 102 maps the QoS parameter for the EPS bearer to the QoS parameter for a radio bearer. It then signals a RRC connection reconfiguration message to the UE 101. The UE 101 acknowledges the radio bearer activation to the eNB 102 with a RRC connection reconfiguration complete message. [0033] In steps 7-12, the bearer activation is acknowledged by direct transfer, a session management response, a bearer setup response, a create bearer response, and IP-can session modification.

[0034] As illustrated in FIG. IB, the method for updating the EPS bearer parameter requested by the network side includes:

[0035] In step : the PCRF 106 generates QoS policy dynamically and sends the QoS policy indicating the QoS requirement for the service to the PGW 105 by initiating IP-CAN session modification procedure;

[0036] In step 2' : the PGW 105 uses this QoS policy to assign value to the QoS parameter of the EPS bearer and sends an update bearer request indicating the QoS parameter to the SGW 104;

[0037] In step 3 ' : the SGW 104 forwards the update bearer request to the MME 103 ;

[0038] In step 4' : the MME 103 sends a session management request or a bearer modify request message indicating QoS parameter for the EPS bearer, to the eNB 102;

[0039] In steps 5' and 6', the eNB 102 maps the QoS parameter for the EPS bearer to the QoS parameter for a radio bearer. It then signals a RRC connection reconfiguration message to the UE 101. The UE 101 acknowledges the radio bearer activation to the eNB 102 with a RRC connection reconfiguration complete message;

[0040] In steps 7'-12', the bearer modification is acknowledged by direct transfer, a session management response, a bearer modify response, an update bearer response, and IP-can session modification.

[0041] In the conventional method, the QoS parameter is set when the EPS bearer is established as shown in FIG. 1 A or when the EPS bearer parameter is modified as shown in FIG. IB, and the QoS parameter remains constant during the whole service. According to the embodiment of the present application, a method for controlling QoS of a service is disclosed, so that each node in the EPS operates according to different QoS requirements in different service stages.

[0042] FIG. 2 A illustrates a flowchart of a method for controlling QoS of a service, in accordance with one embodiment of the present invention. The method is applicable to an EPS 200, which includes a UE 201, an eNB 202, a MME 203, a SGW 204, a PGW 205 and a PCRF 206.

[0043] The EPS 200 further includes a service identification module 207. A device implementing the function of the service identification module 207 is a first device. In one embodiment, the service identification module 207 is a functional module which can be integrated on any nodes in the EPS 200 as the first device, e.g., the UE 201, the e B 202, the MME 203, the SGW 204, the PGW 205 or the PCRF 206. In another embodiment, the service identification module 207 can be implemented on a stand-alone hardware device as the first device, e.g., a controller.

[0044] The method for controlling QoS of a service in the EPS 200 includes:

[0045] S210: the first device obtains a service type of a service.

[0046] The service type may include but not limited to VoIP service, or on-line video service, etc.

[0047] In one embodiment, the service includes a GBR service having several service stages, and having different QoS requirements for different service stages of the service. For example, the service has a first service stage and a second service stage, and has a first QoS requirement for the first service stage and has a second QoS requirement for the second service stage. The QoS requirement may include a requirement for a QoS parameter such as GBR, MBR, time delay, jitter, or error-packet rate.

[0048] Take on-line video service as example. The on-line video service has a buffering stage as the first service stage and a playing stage as the second service stage. In one instance, the on-line video service has a first requirement GBRl for the GBR parameter (e.g, GBRl is greater than or equal to 6Mbps) for the buffering stage and has a second requirement GBR2 for the GBR parameter (e.g, GBR2 is greater than or equal to 900Kbps) for the playing stage. In one instance, GBRl is set higher than GBR2.

[0049] S220: the first device obtains different QoS requirements for different service stages of the service according to the service type. For example, according to the service type, the first device obtains the first QoS requirement for the first service stage and the second QoS requirement for the second service stage.

[0050] S230: the first device generates first indication information. The first indication information indicates the different QoS requirements for different service stages and a service stage sign used to identify the different service stages. For example, the first indication information indicates the first QoS requirement for the first service stage, the second QoS requirement for the second service stage, and the service stage sign used to identify the first service stage and the second service stage. The first indication information is used to generate a QoS policy, so as to control QoS according to the first QoS requirement indicated in the QoS policy in the first service stage and control QoS according to the second QoS requirement indicated in the QoS policy in the second service stage. [0051] Advantageously, the first device generates the first indication information indicating the different QoS requirements for different service stages and the service stage sign used to identify the different service stages. According to the first indication information, the first service stage and the second service stage are identified, and a QoS policy is generated to control QoS according to the first QoS requirement in the first service stage and control QoS according to the second QoS requirement in the second service stage. After receiving the QoS policy, each node in the EPS 200, e.g., the UE 201, the e B 202, the MME 203, the SGW 204, or the PGW 205, operates the service according to a desired QoS requirement in each service stage. For example, each node in the EPS 200 operates the service according to the QoS first requirement in the first service stage, and operates the service according to the second QoS requirement in the second service stage. Take the eNB 202 as a more specific example, the eNB 202 schedules the data packet with a bit rate of GBRl in the first service stage and schedules the data packet with a bit rate of GBR2 in the second service stage. Take the UE 201 as another specific example, similarly, the UE 201 receives the data packet with a bit rate of GBRl in the first service stage and receives the data packet with a bit rate of GBR2 in the second service stage. Therefore, different QoS requirements for different service stage of a service are met. For example, the video service is scheduled at a GBR of 6Mbps in the buffering stage and is scheduled at a GBR of 900Kbps in the playing stage. In the buffering stage, a relatively high level of GBR is satisfied so that the user experience is guaranteed. In the playing stage, a relatively low level of GBR is satisfied so that less resource is held, which increases other UE's bit rate. Therefore, resource is efficiently allocated while user experience is guaranteed.

[0052] In a first implementation of the embodiment, the service identification module 207 is integrated on a first device 2091 including the UE 201, the eNB 202, the MME 203, the SGW 204, or the PGW 205. Thus, as shown in FIG. 2B, the method further includes:

[0053] S240: the first device sends indication information to the PCRF 206 according to the first indication information. The indication information is used for the PCRF 206 to generate the QoS policy. Accordingly, the PCRF 206 generates the QoS policy according to the indication information as shown in S820.

[0054] S250: after the QoS policy is generated by the PCRF 206, the first device receives the QoS policy from the PCRF 206.

[0055] S260: in the first service stage, the first device operates the service according to the first QoS requirement as indicated in the QoS policy. [0056] S270: in the second service stage, the first device operates the service according to the second QoS requirement as indicated in the QoS policy.

[0057] In a second implementation of the embodiment, the service identification module 207 is integrated on a first device 2092 including the PCRF 206. Thus, as shown in FIG. 2C, the method further includes:

[0058] S280: the first device generates the QoS policy according to the first indication information.

[0059] S290: the first device sends the QoS policy to a second device 2093, for example, the second device 2093 may include the UE 201, the e B 202, the MME 203, the SGW 204, or the PGW 205. The QoS policy is used for the second device to operate the service according to different QoS requirements in different service stages. For example, the QoS policy is used for the second device to operate the service according to the first QoS requirement in the first service stage and operate the service according to the second QoS requirement in the second service stage. Accordingly, the second device operates the service according to the first QoS requirement in the first service stage as shown in S620, and operates the service according to the second QoS requirement in the second service stage as shown in S720.

[0060] FIG. 3 A, FIG. 3B, FIG. 3C and FIG. 3D illustrate four examples of the method for controlling QoS of a service. FIG. 3A, FIG. 3B, FIG. 3C and FIG. 3D are described in relation with FIG. 2B. In the first implementation of the embodiment in FIG. 2B, the service identification module 207 is integrated on the first device 2091 including the UE 201, the eNB 202, the MME 203, the SGW 204, or the PGW 205.

[0061] In the example shown in FIG. 3 A, the first device 2091 receives a message indicating the service type of the service from a third device. For example, the third device includes a service provider 208 in the EPS 200, and steps S211, S212 and S213 are performed to realize S210 in FIG. 2 A.

[0062] S211 : a service request is received by the service provider 208. For example, the UE 201 sends a service request to the service provider 208 when the UE 201 starts to use a service, e.g., an on-line video service.

[0063] S212: the service provider 208 sends to the first device a message 0 indicating UE identification (ID) and the service type of the service.

[0064] S213 : after the first device receives the message 0 from the service provider 208, the first device obtains the service type of the service.

[0065] In another instance, when the first device is the UE 201, the first device can identify the service type of the service. For example, when a user starts a service on the

UE 201, the UE 201 is configured to identify the service type of the service.

[0066] In the example shown in FIG. 3 A, S221 is performed to realize S220 in FIG.

2A.

[0067] S221 : the first device obtains different QoS requirements for different service stages according to the service type of the service and user subscription data. In one instance, user subscription data is obtained from a home subscriber server (HSS) in the EPS 200 by the first device according to the UE ID.

[0068] In the example shown in FIG. 3 A, S231 is performed to realize S230 in FIG. 2A.

[0069] S231 : the first device generates the first indication information indicating all QoS requirements for all service stages of the service and the service stage sign to identify the service stages. For example, the first indication information indicates both the first QoS requirement for the first service stage, the second QoS requirement for the second service stage and the service stage sign used to identify the first service stage and the second service stage. Accordingly, the first indication information may include several fields as illustrated in Table 1.

Table 1

[0070] As illustrated in Table 1, field 1 is used to represent the service type, field 2 is used to represent the service stage sign, the field 3 and the field 4 are used to represent the first QoS requirement for the first service stage and the second QoS requirement for the second service stage, respectively.

[0071] The service stage sign in field 2 is used to identify different service stages. For example, in one instance, the service stage sign is represented in form of time: a time period from the service is started to a time point Tl corresponds to the first service stage, and a time period from the time point Tl to a time point T2 corresponds to the second service stage. In another instance, the service stage sign is represented in form of packet capacity: a data packet of a packet capacity of XI calculated from the service is started corresponds to the first service stage, and a data packet of a packet capacity of X2 following the data packet of a packet capacity of XI corresponds to the second service stage. In yet another instance, the service stage sign is represented in combination of time and packet capacity.

[0072] Optionally, the first indication information indicating different QoS requirements for different service stages is further differentiated according to a rank of user experience. For example, a rank of user experience includes excellent, good, accepted or poor. Take the on-line video service as an example, the user experience is excellent when the video service has a fast start speed (less than 2.5 seconds) and the video is fluently played. The user experience is good when the video service has a normal start speed (less than 4 seconds) and the video is stuck less than 1.5 times per hour. The user experience is accepted when it takes 4-10 seconds to start the video service or the video is stuck 1.5-5 times per hour. The user experience is poor in the remaining situation.

[0073] Each rank of user experience corresponds to different QoS requirements for different service stages. For example, to have an excellent user experience, the GBR requirement for the first service stage, e.g., the buffering stage, is 6Mbit per second, and the GBR requirement for the second service stage, e.g., the playing stage, is 900Kbit per second. To have a good user experience, the GBR requirement for the first service stage is 3Mbit per second, and the GBR requirement for the second service stage is 720Kbit per second. A set of different QoS requirements corresponding to a specific user experience can be selected according to user subscription data and current network status of the EPS 200. Accordingly, in one instance, the first indication information may include several fields as illustrated in Table 2.

Table 2 [0074] It should be understood that the first indication information is not limited to the form shown in Table 1 or Table 2. As long as the first indication information indicates different QoS requirements for different service stages of the service, it's under the scope of the present invention.

[0075] In the example in FIG. 3 A, the first indication information is used for the PCRF 206 to generate the QoS policy. S241 and S821 are performed to realize S240 and S820 in FIG. 2B, respectively.

[0076] S241 : the first device 2091 sends the first indication information to the PCRF 206. The PCRF 206 receives the first indication information from the first device 2091.

[0077] S821 : according to the first indication information, the PCRF 206 generates the QoS policy indicating the service stage sign and corresponding different QoS requirements for different service stages. In one instance, the PCRF 206 generates the QoS policy according to the first indication information in form of Table 1. In another instance, the PCRF 206 selects a user experience according to user subscription data and current network status of the EPS 200, and generates the QoS policy corresponding to the selected user experience according to the first indication information in form of Table 2. In both situations, the generated QoS policy is used for a third device to operate the service according the first QoS requirement in the first service stage and to operate the service according to the second QoS requirement in the second service stage. The third device includes each node in EPS 200 except the PCRF 206, e.g., the UE 201, the eNB 202, the MME 203, the SGW 204, or the PGW 205. The third device includes the first device 2091. In FIG. 3 A, the QoS policy indicates the first QoS requirement for the first service stage, the second QoS requirement for the second service stage, and the service stage sign.

[0078] Then, the PCRF 206 transmits the QoS policy to the third device in S250. For example, the QoS policy is transmitted to the nodes in the EPS 200 by using the bearer establishment method as described in FIG. 1 A or by the bearer modification method as described in FIG. IB.

[0079] In the example in FIG. 3 A, the method further includes:

[0080] S310: after receiving the QoS policy, each node in the EPS 200 (e.g., the PGW 205, the SGW 204, the MME 203, the eNB 202, and the UE 201) is configured to identify the service stage according to the QoS policy, and further to identify QoS requirement for the service stage. For example, the PGW 205 identifies the first service stage when a bearer is established, and identifies following different service stages according to the service stage sign as indicated in the QoS policy. For a more specific example, the PGW 205 identifies the following different service stages according to at least one of time and data capacity. When a time Tl is expired and/or a packet capacity XI is reached, the PGW 205 identifies the second service stage. After the service stage is identified, the PGW 205 is configured to identify QoS requirement for the service stage according to the received QoS policy. How other nodes in the EPS 200 identify the service stage and QoS requirement for the service stage is similar to the PGW 205, which will not be repeated here.

[0081] Accordingly, each node in the EPS 200 operates the service according to the first QoS requirement in the first service stage in S260, and operates the service according to the second QoS requirement in the second service stage in S270. For example, in the first service stage, SGW 204 forwards user's data packet with a bit rate of GBRl, and the e B 202 schedules the data packet with a bit rate of GBRl . In the second service stage, SGW 204 forwards user's data packet with a bit rate of GBR2, and the eNB 202 schedules the data packet with a bit rate of GBR2.

[0082] FIG. 3B illustrates another example of the method for controlling QoS of a service. FIG. 3B is described in relation with FIG. 2B and FIG. 3 A.

[0083] In the example shown in FIG. 3B, S210, S220, S231 and S241 are performed. The instances of how S210, S220, S231 and S241 are performed have been described in FIG. 3A, and will not be repeated here. The first indication information is used for the PCRF 206 to identify the service stage and QoS requirement for the service stage, and further to generate the QoS policy. Accordingly, S822-824 and S251-S252 are performed to realize S820 and S250 in FIG. 2B, respectively.

[0084] S822: the PCRF 206 identifies the service stage and QoS requirement for the service stage according to the first indication information. For example, the PCRF 206 identifies the first service stage when a bearer is established. After the first service stage is identified, the PCRF 206 is configured to identify first QoS requirement for the first service stage according to the first indication information. The PCRF 206 identifies following different service stages according to the service stage sign in the first indication information. For example, the PCRF 206 identifies the second service stage according to at least one of time or data capacity. When a time Tl is expired and/or a packet capacity XI is reached, the PCRF 206 identifies the second service stage. After the second service stage is identified, the PCRF 206 is configured to identify the second QoS requirement for the second service stage according to the first indication information.

[0085] S823 : when the PCRF 206 identifies the first service stage and first QoS requirement for the first service stage, the PCRF 206 generates a first QoS policy according to first QoS requirement for the first service stage. The first QoS policy can be generated in form of existing QoS policy without modification. The first QoS policy is used for the third device to operate the service according to the first QoS requirement in the first service stage

[0086] S251 : the third device, e.g., each node in the EPS 200, receives the first QoS policy from the PCRF 206. Accordingly, each node in the EPS 200 operates the service according to the first QoS requirement in the first service stage, as described in S260. For example, in the first service stage, the SGW 204 forwards user's data packet with a bit rate of GBR1, and the eNB 202 schedules the data packet with a bit rate of GBR1.

[0087] S824: when the PCRF 206 identifies the second service stage and second QoS requirement for the second service stage, the PCRF 206 generates a second QoS policy according to second QoS requirement for the second service stage. The second QoS policy can also be generated in form of existing QoS policy without modification. The second QoS policy is used for the third device to operate the service according to the second QoS requirement in the second service stage.

[0088] S252: the third device, e.g., each node in the EPS 200, receives the second QoS policy from the PCRF 206. Accordingly, each node in the EPS 200 including the first device operates the service according to the second QoS requirement in the second service stage, as described in S260. For example, in the second service, the SGW 204 forwards user's data packet with a bit rate of GBR2, and the eNB 202 schedules the data packet with a bit rate of GBR2.

[0089] Advantageously, both resource is efficiently allocated and user experience is guaranteed. Furthermore, since the PCRF 206 is configured to identify the service stage and corresponding different QoS requirement for the service stage, the QoS policy generated by the PCRF 206 can be implemented in form of existing QoS policy without any modification. Thus, there is no need for the generated QoS policy to consider the service stage sign and corresponding QoS requirements for different service stages.

[0090] FIG. 3C illustrates another example of the method for controlling QoS of a service. FIG. 3C is described in relation with FIG. 2B.

[0091] In the example in FIG. 3C, S210, S220 and S231 are performed. The instances of how S210, S220 and S231 are performed have been described in FIG. 3 A, and will not be repeated here.

[0092] In the example shown in FIG. 3C, the method further includes S232-S234. S242-S243 and S825-S826 are performed to realize S240 and S820 in FIG. 2B, respectively.

[0093] S232: the first device identifies the first QoS requirement for the first service stage according to the first indication information.

[0094] S233 : the first device generates second indication information indicating the first QoS requirement for the first service stage.

[0095] S242: the first device sends the second indication information to the PCRF 206. The second indication information is used for the PCRF 206 to generate a first QoS policy indicating the first QoS requirement for the first service stage.

[0096] S825: the PCRF 206 generates a first QoS policy according to the second indication information. The first QoS policy can be generated in form of existing QoS policy without modification.

[0097] S251 : the first device receives the first QoS policy. Accordingly, each node in the EPS 200 operates the service according to the QoS first requirement in the first service stage, as described in S260.

[0098] S234: the first device identifies the second QoS requirement for the second service stage according to the first indication information.

[0099] S235: the first device generates third indication information indicating the second QoS requirement for the first service stage.

[00100] S243 : the first device sends the third indication information to the PCRF 206. The third indication information is used for the PCRF 206 to generate a second QoS policy indicating the second QoS requirement for the first service stage.

[00101] S826: the PCRF 206 generates a second QoS policy according to the third indication information. The second QoS policy can also be generated in form of existing QoS policy without modification.

[00102] S252: the first device receives the second QoS policy. Accordingly, each node in the EPS 200 operates the service according to the second QoS requirement in the second service stage, as described in S270.

[00103] In the example shown in FIG. 3C, the first device is further configured to identify the service stage to identify different QoS requirements.

[00104] For example, in FIG. 3C, S2321 and S2341 are performed to realize S232 and S234, respectively.

[00105] S2321 : the first device identifies the first service stage according to the service stage sign indicated in the first indication information to identify the first QoS requirement for the first service stage. For example, the first device identifies the first service stage when a bearer is established. After the first service stage is identified, the first device is configured to identify first QoS requirement for the first service stage.

[00106] S2341 : the first device identifies the second service stage according to the service stage sign indicated in the first indication information to identify the second QoS requirement for the second service stage. For example, the first device identifies the second service stage according to at least one of time or data capacity. When a time Tl is expired and/or a packet capacity XI is reached, the first device identifies the second service stage. After the second service stage is identified, the first device is configured to identify second QoS requirement for the second service stage.

[00107] Advantageously, both resource is efficiently allocated and user experience is guaranteed. Furthermore, since the first device is configured to identify the service stage, and send the second indication information indicating the first QoS requirement to the PCRF 206 when the first service stage is identified, and send the third indication information indicating the second QoS requirement to the PCRF 206 when the second service stage is identified. According to the received indication information, the PCRF 206 generates a QoS policy indicating QoS requirement for the service stage. Therefore, the QoS policy generated can be implemented in form of existing QoS policy without any modification. Thus, there is no need for the generated QoS policy to consider the service stage sign and corresponding QoS requirements for different service stages.

[00108] FIG. 3D illustrates yet another example of the method for controlling QoS of a service. FIG. 3D is described in relation with FIG. 3C. Steps labeled the same as in FIG. 3C are performed similarly.

[00109] In FIG. 3D, only S232 and S234 are implemented through another multiple steps. S2322-S2324 and S2342-S2343 are performed to realize S232 and S234.

[00110] S2322: the first device sends a request to activate the UE 201 to identify the first service stage and the second service stage (when the first device is not the UE 201).

[00111] In one instance, after the UE 201 is activated, the UE 201 identifies the service stage according to at least one of software operation instruction and status information. Still take video service as an example, the UE 201 identifies the service stage according to the software operation instruction includes: when a user clicks an icon to start the video service in the UE 201, the UE 201 identifies that the video service enters into the first service stage, e.g., the initial stage. The UE 201 identifies the service stage according to the status information includes: when data capacity in the buffer reaches a threshold, e.g., the threshold is set to 70% of capacity of the buffer, the UE 201 identifies that the video service enters into the second service stage, e.g., the playing stage.

[00112] In another instance, the request includes information indicating the service stage sign. The service stage sign is used for the UE 201 to identify different service stages. The service stage sign can be represented in form of at least one or combination of time and packet capacity as described above. Accordingly, the UE 201 identifies the service stage according to at least one of time and packet capacity.

[00113] S2323 : the first device receives a feedback message 4 reported by the UE 201 indicating that the service stage is the first service stage, when the first service stage is identified by the UE 201.

[00114] S2324: after receiving the feedback message 4 reported by the UE 201, the first device identifies the first QoS requirement for the first service stage.

[00115] S2342: the first device receives a feedback message 5 reported by the UE 201 indicating that the service stage is the second service stage, when the second service stage is identified by the UE 201.

[00116] S2343 : after receiving the message 5 reported by the UE 201, the first device identifies the second QoS requirement for the second service stage.

[00117] Advantageously, since the first device activates the UE 201 to identify the service stage, the first device sends the second indication information indicating the first QoS requirement to the PCRF 206 when the first service stage is identified by the UE 201, and sends the third indication information indicating the second QoS requirement to the PCRF 206 when the second service stage is identified by the UE 201. According to the received indication information, the PCRF 206 generates a QoS policy indicating QoS requirement for the service stage. Therefore, the QoS policy generated by the PCRF 206 can be implemented in form of existing QoS policy without any modification. Thus, there is no need for the generated QoS policy to consider the service stage sign and corresponding QoS requirements for different service stages.

[00118] FIG. 4A, FIG. 4B and FIG. 4C illustrate another three examples of the method for controlling QoS of a service. FIG. 4A, FIG. 4B and FIG. 4C are described in relation with FIG. 2C. In the second implementation of the embodiment in FIG. 2C, the service identification module 207 is integrated on the first device 2092 including the PCRF 206.

[00119] In FIG. 4A, S211-S213, S221 and S231 are performed. Instances of how the first device 2092 performs the above steps are similar to the first device 2091, and will not be repeated here. In the example in FIG. 4A, the first indication information is used for the first device 2092 to generate the QoS policy. After the first device 2092 generates the first indication information in S231, S281 is performed to realize S280 in FIG. 2C.

[00120] S281 : the first device 2092 generates the QoS policy according to the first indication information. The QoS policy indicates the first QoS requirement for the first service stage, the second QoS requirement for the second service stage, and the service stage sign. Instance of how the first device 2092 generates the QoS policy indicating the first QoS requirement for the first service stage, the second QoS requirement for the second service stage, and the service stage sign, is similar to how the PCRF 206 generates the QoS policy as described in S821, and will not be repeated here. Then, the first device sends the QoS policy to the second device as described in S290. The second device receives the QoS policy from the first device. The QoS policy is used for the second device to identify the service stage.

[00121] According to QoS policy, the second device identifies the service stage and QoS requirement for the service stage in S320. How the second device 2093 identifies the service stage according to the QoS policy is similar to how the first device 2091 identifies the service stage as described in S310, and will not be repeated here. Accordingly, the second device operates the service according to the first QoS requirement in the first service stage as described in S620, and operates the service according to the second QoS requirement in the second service stage as described in S720.

[00122] FIG. 4B illustrates another example of the method for controlling QoS of a service. FIG. 4B is described in relation with FIG. 4A and FIG. 2C.

[00123] In the example shown in FIG. 4B, S210, S220 and S231 are performed. The instances of how S210, S220 and S231 are performed have been described in FIG. 3 A, and will not be repeated here.

[00124] In the example shown in FIG. 4B, the first indication information is used for the first device, e.g., the PCRF 206, to identify the QoS requirement and to generate the QoS policy accordingly. S282-S285 and S291-S292 are performed to realize S280 and S290 in FIG. 2C, respectively.

[00125] S282: the first device identifies the first QoS requirement for the service stage according to the first indication information. In FIG. 4B, S2821 is performed to realize S282.

[00126] S2821 : the first device identifies the first service stage, to further identify the first QoS requirement for the service stage. For example, the first device identifies the first service stage in default when a bearer is established. After the first service stage is identified, the first device identifies the first QoS requirement for the first service stage according to the first indication information.

[00127] S283 : when the first device identifies the first service stage, the first device generates a first QoS policy according to first QoS requirement for the first service stage. The first QoS policy can be generated in form of existing QoS policy without modification.

[00128] S291 : the first device sends the first QoS policy to the second device in the EPS 200, accordingly, the second device operates the service according to the first QoS requirement in the first service stage, as described in S620. For example, in the first service stage, the SGW 204 forwards user's data packet with a bit rate of GBR1, and the e B 202 schedules the data packet with a bit rate of GBR1.

[00129] S284: the first device identifies the second QoS requirement for the second service stage. In FIG 4B, S2841 is performed to realize S284.

[00130] S2841 : the first device identifies the service stage according to the first indication information, to further identify the second QoS requirement for the service stage. For example, the first device identifies following different service stages according to the service stage sign in the first indication information. For a more specific example, the first device identifies the second service stage according to at least one of time or data capacity. When a time Tl is expired and/or a packet capacity XI is reached, the PCRF 206 identifies the second service stage. After the second service stage is identified, the first device identifies the second QoS requirement for the second service stage according to the first indication information.

[00131] S285: the first device generates a second QoS policy according to second QoS requirement for the second service stage. The second QoS policy can also be generated in form of existing QoS policy without modification.

[00132] S292: the first device 2092 sends the second QoS policy to the second device, accordingly, the second device operates the service according to the second QoS requirement in the second service stage, as described in S720. For example, in the second service, the SGW 204 forwards user's data packet with a bit rate of GBR2, and the eNB 202 schedules the data packet with a bit rate of GBR2.

[00133] FIG. 4C illustrates yet another example of the method for controlling QoS of a service. FIG. 4C is described in relation with FIG. 4B. Steps labeled the same as in FIG. 3C are performed similarly.

[00134] In FIG. 4C, only S282 and S284 are implemented through another multiple steps. S2822-S2824 and S2842-S2843 are performed to realize S282 and S284. [00135] S2822: the first device sends a request to activate the UE 201 to identify the service stage. Instance of how the UE 201 identifies the service stage has been described in S2322, and will not be repeated here.

[00136] S2823 : the first device receives a feedback message 4 reported by the UE 201 indicating that the service stage is the first service stage, when the first service stage is identified by the UE 201.

[00137] S2824: after receiving the feedback message 4 reported by the UE 201, the first device identifies the first QoS requirement for the first service stage.

[00138] S2842: the first device receives a feedback message 5 reported by the UE 201 indicating that the service stage is the second service stage, when the second service stage is identified by the UE 201.

[00139] S2843 : after receiving the message 5 reported by the UE 201, the first device identifies the second QoS requirement for the second service stage.

[00140] FIG. 5 illustrates a simplified block diagram of a device 502502 for controlling QoS of a service. FIG. 5 is described in relation to FIG. 2A. The device 502 may be any node in the EPS 200, e.g., the UE 201, the e B 202, the MME 203, the SGW 204, the PGW 205 or the PCRF 206.

[00141] As illustrated in FIG. 5, the device 502 includes a first obtaining unit 506, a second obtaining unit 508 and a generating unit 510. The first obtaining unit 506, the second obtaining unit 508 and the generating unit 510 can be implemented by a processor in the node as the device 502. As used herein, the term "processor" refers to one or more devices, circuits, and/or processing cores configured to process data, such as computer program instructions.

[00142] The first obtaining unit 506 is configured to obtain a service type of the service. The service includes a GBR service having at least a first service stage and a second service stage. The second obtaining unit 508 is configured to obtain a first QoS requirement for the first service stage and a second QoS requirement for the second service stage according to the service type of the service. The generating unit 510 is configured to generate first indication information indicating the first QoS requirement for the first service stage, the second QoS requirement for the second service stage and a service stage sign used to identify the first service stage and the second service stage. For example, the service stage sign is represented in form of any one or any combination of time of a data packet and packet capacity of the data packet. The first indication information is used to generate a QoS policy, so as to control QoS according to the first QoS requirement indicated in the QoS policy in the first service stage and QoS according to the second QoS requirement indicated in the QoS policy in the second service stage.

[00143] In one instance, the first indication information indicates the first QoS requirement for the first service stage and the second QoS requirement for the second service stage which are corresponding to a first rank of user experience of the service, and further indicates a third QoS requirement for the first service stage and a fourth QoS requirement for the second service stage which are corresponding to a second rank of user experience of the service.

[00144] Advantageously, the first device generates the first indication information indicating the different QoS requirements for different service stages and the service stage sign used to identify the different service stages. According to the first indication information, the first service stage and the second service stage are identified, and a QoS policy is generated to control QoS according to the first QoS requirement in the first service stage and control QoS according to the second QoS requirement in the second service stage. After receiving the QoS policy, each node in the EPS 200, e.g., the UE 201, the e B 202, the MME 203, the SGW 204, or the PGW 205, operates the service according to a desired QoS requirement in each service stage. For example, each node in the EPS 200 operates the service according to the QoS first requirement in the first service stage, and operates the service according to the second QoS requirement in the second service stage. Take the eNB 202 as a more specific example, the eNB 202 schedules the data packet with a bit rate of GBRl in the first service stage and schedules the data packet with a bit rate of GBR2 in the second service stage. Therefore, different QoS requirements for different service stage of a service are met. For example, the video service is scheduled at a GBR of 6Mbps in the buffering stage and is scheduled at a GBR of 900Kbps in the playing stage. In the buffering stage, a relatively high level of GBR is satisfied so that the user experience is guaranteed. In the playing stage, a relatively low level of GBR is satisfied so that less resource is held, which increases other UE's bit rate. Therefore, resource is efficiently allocated while user experience is guaranteed.

[00145] FIG. 6A, FIG. 6B, and FIG. 6C illustrate three examples of the device for controlling the QoS of a service. FIG. 6A, FIG. 6B and FIG. 6C are described in relation with FIG. 5. Elements labeled the same perform similar functions.

[00146] In FIG. 6A and FIG. 6B, a device 602 for controlling QoS of a service is implemented by the UE 201, the eNB 202, the MME 203, the SGW 204, or the PGW 205. The device 600 includes the first obtaining unit 506, the second obtaining unit 508, the generating unit 510, a QoS receiving unit 604, and a service operating unit 608.

[00147] The QoS receiving unit 604 is configured to receive the QoS policy from the PCRF 206. The service operating unit 608 is configured to operate the service according to the first QoS requirement indicated in the QoS policy in the first service stage and to operate the service according to the second QoS requirement indicated in the QoS policy in the second service stage.

[00148] In FIG. 6 A, the generating unit 510 is further configured to send the first indication information to the PCRF 206. The first indication information is used for the PCRF 206 to generate the QoS policy. In one instance, the QoS policy generated by the PCRF 206 indicates the first QoS requirement for the first service stage, the second QoS requirement for the second service stage and the service stage sign used to identify the first service stage and the second service stage. Accordingly, the device 602 further includes a first identification unit 610. The first identification unit 610 is configured to identify the first service stage and the second service stage according to the service stage sign indicated in the QoS policy, so that the first device is able to operate the service according to the first QoS requirement indicated in the QoS policy in the first service stage and to operate the service according to the second QoS requirement indicated in the QoS policy in the second service stage.

[00149] In another instance, the first indication information is used for the PCRF 206 to identify the service stage and to generate the QoS policy. When the PCRF 206 identifies the first service stage and the first QoS requirement for the first service stage according to the first indication information, the PCRF generates a first QoS policy. Thus, the device 600 operates the service according to the first QoS requirement according to the first QoS policy in the first service stage. When the PCRF 206 identifies the second service stage and the second QoS requirement for the second service stage according to the first indication information, the PCRF generates a second QoS policy. Thus, the device 600 operates the service according to the second QoS requirement according to the second QoS policy in the second service stage.

[00150] In FIG. 6B, the device 602 further includes a second identification unit 616. The second identification unit 616 is configured to identify the first QoS requirement for the first service stage and the second QoS requirement for the second service stage according to the first indication information. Accordingly, the generating unit 510 is configured to generate second indication information indicating the first QoS requirement for the first service stage when the first QoS requirement for the first service stage is identified, and send the second indication information to the PCRF 206 to generate a first QoS policy. The generating unit 510 is configured to generate third indication information indicating the second QoS requirement for the second service stage when the second QoS requirement for the second service stage is identified, and send the third indication information to the PCRF 206 to generate a second QoS policy.

[00151] In one instance, the second identification unit 616 is configured to identify the first service stage according to the service stage sign indicated in the first indication information to identify the first QoS requirement for the first service stage, and to identify the second service stage according to the service stage sign indicated in the first indication information to identify the second QoS requirement for the second service stage.

[00152] In another instance, the second identification unit 616 is configured to send a request to a user equipment (UE) to activate the UE to identify the first service stage and the service stage, and to receive a first feedback message indicating that the first service stage is identified from the UE, and to identify the first QoS requirement for the first service stage according to the first feedback message. The second identification unit 616 is further configured to receive a second feedback message indicating that the second service stage is identified from the UE, and to identify the second QoS requirement for the second service stage according to the second feedback message.

[00153] In FIG. 6C, a device 614 for controlling QoS of a service is implemented by the PCRF 206. The device 614 includes the first obtaining unit 506, the second obtaining unit 508, the generating unit 510, and a QoS generating unit 632. The QoS generating unit 632 is configured to generate the QoS policy according to the first indication information and to send the QoS policy to a second device, e.g., the UE 201, the e B 202, the MME 203, the SGW 204, or the PGW 205. The QoS policy is used for the second device to operate the service according to the first QoS requirement in the first service stage and operate the service according to the second QoS requirement in the second service stage.

[00154] In one instance, the device 614 generates the QoS policy indicating the first QoS requirement for the first service stage, the second QoS requirement for the second service stage, and the service stage sign used to identify the first service stage and the second service stage. Accordingly, the second device identifies the first service stage and the second service stage according to the service stage sign indicated in the QoS policy, so that the second device is able to operate the service according to the first QoS requirement indicated in the QoS policy in the first service stage and to operate the service according to the second QoS requirement indicated in the QoS policy in the second service stage.

[00155] In another instance, the device 614 further includes a third identification unit 634. The third identification unit 634 is configured to identify the first QoS requirement for the first service stage and the second QoS requirement for the second service stage according to the first indication information. Accordingly, the QoS generating unit 632 is configured to generate a first QoS policy according to the first QoS requirement for the first service stage when the first QoS requirement for the first service stage is identified and to generate a second QoS policy according to the second QoS requirement for the second service stage when the second QoS requirement for the second service stage is identified.

[00156] For example, in one instance, the third identification unit 634 is configured to identify the first service stage according to the service stage sign indicated in the first indication information to identify the first QoS requirement for the first service stage, and to identify the second service stage according to the service stage sign indicated in the first indication information to identify the second QoS requirement for the second service stage.

[00157] In another instance, the third identification unit 634 is configured to send a request to a user equipment (UE) to activate the UE to identify the first service stage and the service stage, and to receive a first feedback message indicating that the first service stage is identified from the UE, and to identify the first QoS requirement for the first service stage according to the first feedback message. The third identification unit 634 is further configured to receive a second feedback message indicating that the second service stage is identified from the UE, and to identify the second QoS requirement for the second service stage according to the second feedback message.

[00158] FIG. 7 A and FIG. 7B illustrates two simplified block diagrams of a second device for controlling QoS of a service device. The service includes a GBR service having at least a first service stage and a second service stage. In FIG. 7A, a second device 700 includes a receiving unit 702, a generating unit 704, and a transmitting unit 706. The device 700 can be implemented by a PCRF, e.g., the PCRF 206 in FIG. 3A and FIG. 3B. The receiving unit 702, the generating unit 704, and the transmitting unit 706 can be implemented by a processor in the PCRF 206.

[00159] The receiving unit 702 is configured to receive first indication information from a first device. The first indication information indicates a first QoS requirement for the first service stage, a second QoS requirement for the second service stage and a service stage sign used to identify the first service stage and the second service stage. [00160] The generating unit 704 is configured to generate a QoS policy according to the first indication information. The transmitting unit 706 is configured to transmit the QoS policy to a third device. The QoS policy is used for the third device to operate the service according the first QoS requirement in the first service stage and to operate the service according to the second QoS requirement in the second service stage. The third device includes the first device.

[00161] In one instance, the QoS policy indicates the first QoS requirement for the first service stage, the second QoS requirement for the second service stage and the service stage sign used to identify the first service stage and the second service stage. The QoS policy is used for the third device to identify the first service stage and the second service stage according to the service stage sign indicated in the QoS policy.

[00162] In another instance, optionally, the device 700 further includes an identifying unit 708. The identifying unit 708 is configured to identify the first service stage and the first QoS requirement for the first service stage according to the first indication information. The generating unit 704 is configured to generate a first QoS policy according to the first QoS requirement for the first service stage, and the first QoS policy is used for the third device to operate the service according to the first QoS requirement in the first service stage. The generating unit 704 is further configured to generate a second QoS policy according to the second QoS requirement for the second service stage, and the second QoS policy is used for the third device to operate the service according to the second QoS requirement in the second service stage.

[00163] In the example in FIG. 7B, a device 710 includes a receiving unit 712, an identifying unit 714, and an operating unit 716. The device 710 can be implemented by any node in the EPS 200, e.g., the second device 2093 in FIG. 4A. The receiving unit 712, the identifying unit 714, and the operating unit 716 can be implemented by a processor in the second device 2093.

[00164] The receiving unit 712 is configured to receive a QoS policy from a first device. The QoS policy indicates the first QoS requirement for the first service stage, the second QoS requirement for the second service stage and the service stage sign used to identify the first service stage and the second service stage.

[00165] The identifying unit 714 is configured to identify the first service stage according to the service stage sign indicated in the QoS policy and to identify a first QoS requirement for the first service stage. The operating unit 716 is configured to operate the service according to the first QoS requirement in the first service stage according to the QoS policy. The identifying unit 714 is further configure to identify the second service stage according to the service stage sign indicated in the QoS policy and to identify a second QoS requirement for the second service stage. The operating unit 716 is further configured to operate the service according to the second QoS requirement in the second service stage according to the QoS policy.

[00166] A person of ordinary skill in the art may be aware that, in combination with the examples described in the embodiments disclosed in this specification, units and algorithm steps may be implemented by electronic hardware, or a combination of computer software and electronic hardware. Whether the functions are performed by hardware or software depends on the particular applications and design constraint conditions of the technical solution. A person skilled in the art may use different methods to implement the described functions for each particular application, but it should not be considered that the implementation goes beyond the scope of the present invention.

[00167] It may be clearly understood by a person skilled in the art that, for the purpose of convenient and brief description, for a detailed working process of the foregoing system, device, and unit, reference may be made to a corresponding process in the foregoing method embodiments, and details are not described herein again.

[00168] In the several embodiments provided in the present application, it should be understood that the disclosed system, device, and method may be implemented in other manners. For example, the described device embodiment is merely exemplary. For example, the unit division is merely logical function division and may be other division in actual implementation. For example, a plurality of units or components may be combined or integrated into another system, or some features may be ignored or not performed. In addition, the displayed or discussed mutual couplings or direct couplings or communication connections may be implemented through some interfaces. The indirect couplings or communication connections between the devices or units may be implemented in electronic, mechanical, or other forms.

[00169] The units described as separate parts may or may not be physically separate, and the parts displayed as units may or may not be physical units, may be located in one position, or may be distributed on a plurality of network units. A part of or all of the units may be selected according to actual needs to achieve the objectives of the solutions of the embodiments.

[00170] In addition, functional units in the embodiments of the present invention may be integrated into one processing unit, or each of the units may exist alone physically, or two or more units may be integrated into one unit.

[00171] When the functions are implemented in a form of a software functional unit and sold or used as an independent product, the functions may be stored in a computer-readable storage medium. Based on such an understanding, the technical solutions of the present invention essentially, or the part contributing to the prior art, or a part of the technical solutions may be implemented in a form of a software product. The computer software product is stored in a storage medium and includes several instructions for instructing a computer device (which may be a personal computer, a server, a network device, or the like) to perform all or a part of the steps of the methods described in the embodiments of the present invention. The foregoing storage medium includes: any medium that can store program code, such as a USB flash drive, a removable hard disk, a read-only memory (ROM, Read-Only Memory), a random access memory (RAM, Random Access Memory), a magnetic disk, or an optical disc.

[00172] The foregoing descriptions are merely specific implementation manners of the present invention, but are not intended to limit the protection scope of the present invention. Any variation or replacement readily figured out by a person skilled in the art within the technical scope disclosed in the present invention shall fall within the protection scope of the present invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the claims.

Claims

CLAIMS What is claimed is:

1. A method for controlling quality of service (QoS) of a service, comprising:

obtaining, by a first device, a service type of the service, wherein the service comprises a guaranteed bit rate (GBR) service having at least a first service stage and a second service stage; obtaining, by the first device, a first QoS requirement for the first service stage and a second QoS requirement for the second service stage according to the service type of the service; and

generating, by the first device, first indication information, wherein the first indication information indicates the first QoS requirement for the first service stage, the second QoS requirement for the second service stage and a service stage sign used to identify the first service stage and the second service stage, wherein the first indication information is used to generate a QoS policy, so as to control QoS according to the first QoS requirement indicated in the QoS policy in the first service stage and control QoS according to the second QoS requirement indicated in the QoS policy in the second service stage.

2. The method as claimed in claim 1, wherein the service stage sign is represented in form of any one or any combination of time of a data packet and packet capacity of the data packet.

3. The method as claimed in claim 1 or 2, wherein the first indication information indicates the first QoS requirement for the first service stage and the second QoS requirement for the second service stage which are corresponding to a first rank of user experience of the service, and further indicates a third QoS requirement for the first service stage and a fourth QoS requirement for the second service stage which are corresponding to a second rank of user experience of the service.

4. The method as claimed in any one of claims 1-3, wherein the method further comprises: receiving, by the first device, the QoS policy sent from a policy and charging rules function (PCRF);

operating, by the first device, in the first service stage, the service according to the first QoS requirement indicated in the QoS policy; and

operating, by the first device, in the second service stage, the service according to the second QoS requirement indicated in the QoS policy.

5. The method as claimed in claim 4, wherein the method further comprises:

sending, by the first device, the first indication information to the PCRF, wherein the first indication information is used for the PCRF to generate the QoS policy;

identifying, by the first device, the first service stage and the second service stage according to the service stage sign indicated in the QoS policy.

6. The method as claimed in claim 4, wherein the method further comprises:

identifying, by the first device, the first QoS requirement for the first service stage according to the first indication information;

generating, by the first device, second indication information indicating the first QoS requirement for the first service stage, wherein the second indication is sent to the PCRF and is used for the PCRF to generate a first QoS policy indicating the first QoS requirement for the first service stage;

identifying, by the first device, the second QoS requirement for the second service stage according to the first indication information;

generating, by the first device, third indication information indicating the second QoS requirement for the first service stage, wherein the third indication information is sent to the PCRF and is used for the PCRF to generate a second QoS policy indicating the second QoS requirement for the first service stage.

7. The method as claimed in claim 6, wherein identifying the first QoS requirement for the first service stage comprises:

sending, by the first device, a request to activate a user equipment (UE) to identify the first service stage and the second service stage;

receiving, by the first device, a first feedback message reported by the UE indicating that the first service stage is identified;

identifying, by the first device, the first QoS requirement for the first service stage according to the first feedback message;

wherein identifying the second QoS requirement for the second service stage comprises:

receiving, by the first device, a second feedback message reported by the UE indicating that the second service stage is identified;

identifying, by the first device, the second QoS requirement for the second service stage according to the second feedback message.

8. The method as claimed in any one of claims 1-6, wherein the first device comprises a user equipment (UE), an evolved NodeB (eNodeB), a mobility management entity (MME), a serving gateway (SGW), or a packet data network gateway (PGW).

9. The method as claimed in any one of claims 1-3, wherein the first device comprises a policy and charging rules function (PCRF);

wherein the method further comprises:

generating, by the first device, the QoS policy according to the first indication information; and

sending, by the first device, the QoS policy to a second device, wherein the QoS policy is used for the second device to operate the service according to the first QoS requirement in the first service stage and operate the service according to the second QoS requirement in the second service stage.

10. The method as claimed in claim 9, wherein the generated QoS policy indicates the first QoS requirement for the first service stage, the second QoS requirement for the second service stage and the service stage sign used to identify the first service stage and the second service stage, wherein the QoS policy is used for the second device to identify the first service stage and the second service stage.

11. The method as claimed in claim 9, wherein generating the QoS policy according to the first indication information comprises:

generating, by the first device, a first QoS policy according to the first QoS requirement;

identifying, by the first device, the second QoS requirement for the second service stage according to the first indication information; and

generating, by the first device, a second QoS policy according to the second QoS requirement.

12. The method as claimed in claim 11, wherein identifying the first QoS requirement for the first service stage comprises: sending, by the first device, a request to activate a user equipment (UE) to identify the first service stage and the second service stage;

13. The method as claimed in any one of claim 1-12, wherein obtaining the service type of the service comprises:

receiving, by the first device, a message indicating the service type of the service from a third device.

14. A first device for controlling quality of service (QoS) of a service, comprising:

a first obtaining unit, configured to obtain a service type of the service, wherein the service is a guaranteed bit rate (GBR) service having at least a first service stage and a second service stage; a second obtaining unit, configured to obtain a first QoS requirement for the first service stage and a second QoS requirement for the second service stage according to the service type of the service; and

a generating unit, configured to generate first indication information indicating the first QoS requirement for the first service stage, the second QoS requirement for the second service stage and a service stage sign used to identify the first service stage and the second service stage, wherein the first indication information is used to generate a QoS policy, so as to control QoS according to the first QoS requirement indicated in the QoS policy in the first service stage and control QoS according to the second QoS requirement indicated in the QoS policy in the second service stage.

15. The first device as claimed in claim 14, wherein the service stage sign is represented in form of any one or any combination of time of a data packet and packet capacity of the data packet.

16. The first device as claimed in claim 14 or 15, wherein the first indication information indicates the first QoS requirement for the first service stage and the second QoS requirement for the second service stage which are corresponding to a first rank of user experience of the service, and further indicates a third QoS requirement for the first service stage and a fourth QoS requirement for the second service stage which are corresponding to a second rank of user experience of the service.

17. The first device as claimed in any one of claims 14-16, further comprising:

a QoS receiving unit, configured to receive the QoS policy from a policy and charging rules function (PCRF); and

a service operating unit, configured to operate the service according to the first QoS requirement indicated in the QoS policy in the first service stage and to operate the service according to the second QoS requirement indicated in the QoS policy in the second service stage.

18. The first device as claimed in claims 17, wherein the generating unit is configured to send the first indication information to the PCRF, wherein the first indication information is used for the

PCRF to generate the QoS policy;

wherein the device further comprises:

a first identification unit configured to identify the first service stage and the second service stage according to the service stage sign indicated in the QoS policy.

19. The first device as claimed in claims 17, further comprising:

a second identification unit configured to identify the first QoS requirement for the first service stage and the second QoS requirement for the second service stage according to the first indication information;

wherein the generating unit is configured to generate second indication information indicating the first QoS requirement for the first service stage when the first QoS requirement for the first service stage is identified, and to send the second indication information the PCRF to generate a first QoS policy, and wherein the generating unit is configured to generate third indication information indicating the second QoS requirement for the second service stage when the second QoS requirement for the second service stage is identified, and to send the third indication information to the PCRF to generate a second QoS policy.

20. The first device as claimed in claim 19, wherein the second identification unit is configured to send a request to a user equipment (UE) to activate the UE to identify the first service stage and the service stage, and to receive a first feedback message indicating that the first service stage is identified from the UE, and to identify the first QoS requirement for the first service stage according to the first feedback message;

wherein the second identification unit is further configured to receive a second feedback message indicating that the second service stage is identified from the UE, and to identify the second QoS requirement for the second service stage according to the second feedback message.

21. The first device as claimed in any one of claims 14-19, wherein the device comprises a user equipment (UE), an evolved NodeB (eNodeB), a mobility management entity (MME), a serving gateway (SGW), or a packet data network gateway (PGW).

22. The first device as claimed in any one of claims 14-16, wherein the device comprises a policy and charging rules function (PCRF) comprising:

a QoS generating unit, configured to generate the QoS policy according to the first indication information and to send the QoS policy to a second device, wherein the QoS policy is used for the second device to operate the service according to the first QoS requirement in the first service stage and operate the service according to the second QoS requirement in the second service stage.

23. The first device as claimed in claim 22, wherein the QoS policy indicates the first QoS requirement for the first service stage, the second QoS requirement for the second service stage, and the service stage sign used for the second device to identify the first service stage and the second service stage.

24. The first device as claimed in claim 22, further comprising:

a third identification unit configured to identify the first QoS requirement for the first service stage and the second QoS requirement for the second service stage according to the first indication information;

wherein the QoS policy comprises a first QoS policy and a second QoS policy, the QoS generating unit is configured to generate the first QoS policy according to the first QoS requirement for the first service stage when the first QoS requirement for the first service stage is identified and to generate the second QoS policy according to the second QoS requirement for the second service stage when the second QoS requirement for the second service stage is identified.

25. The first device as claimed in claim 24, wherein the third identification unit is configured to send a request to a user equipment (UE) to activate the UE to identify the first service stage and the service stage, and to receive a first feedback message indicating that the first service stage is identified from the UE, and to identify the first QoS requirement for the first service stage according to the first feedback message;

26. The first device as claimed in any one of claim 14-25, wherein the first obtaining unit is configured to receive a message indicating the service type of the service from a third device.

27. A method for controlling quality of service (QoS) of a service, wherein the service comprises a guaranteed bit rate (GBR) service having at least a first service stage and a second service stage, the method comprising:

receiving, by a second device, first indication information from a first device, wherein the first indication information indicates a first QoS requirement for the first service stage, a second QoS requirement for the second service stage and a service stage sign used to identify the first service stage and the second service stage;

generating, by the second device, a QoS policy according to the first indication information; and

transmitting, by the second device, the QoS policy to a third device, the QoS policy is used for the third device to operate the service according the first QoS requirement in the first service stage and to operate the service according to the second QoS requirement in the second service stage.

28. The method as claimed in claim 27, wherein the QoS policy indicates the first QoS requirement for the first service stage, the second QoS requirement for the second service stage and the service stage sign used to identify the first service stage and the second service stage, wherein the QoS policy is used for the third device to identify the first service stage and the second service stage according to the service stage sign indicated in the QoS policy.

29. The method as claimed in claim 27, wherein the generating a QoS policy according to the first indication information, comprises:

identifying, by the second device, the first service stage and the first QoS requirement for the first service stage according to the first indication information; generating, by the second device, a first QoS policy according to the first QoS requirement for the first service stage, wherein the first QoS policy is used for the third device to operate the service according to the first QoS requirement in the first service stage;

identifying, by the second device, the second service stage and the second QoS requirement for the second service stage according to the first indication information;

generating, by the second device, a second QoS policy according to the second QoS requirement for the second service stage, wherein the second QoS policy is used for the third device to operate the service according to the second QoS requirement in the second service stage.

30. The method as claimed in any one of claims 27-29, wherein the third device comprises the first device.

31. A second device for controlling quality of service (QoS) of a service, wherein the service comprises a guaranteed bit rate (GBR) service having at least a first service stage and a second service stage, the device comprising:

a receiving unit, configured to receive first indication information from a first device, wherein the first indication information indicates a first QoS requirement for the first service stage, a second

QoS requirement for the second service stage and a service stage sign used to identify the first service stage and the second service stage;

a generating unit, configured to generate a QoS policy according to the first indication information; and

a transmitting unit, configured to transmit the QoS policy to a third device, the QoS policy is used for the third device to operate the service according the first QoS requirement in the first service stage and to operate the service according to the second QoS requirement in the second service stage.

32. The second device as claimed in claim 31, wherein the QoS policy indicates the first QoS requirement for the first service stage, the second QoS requirement for the second service stage and the service stage sign used to identify the first service stage and the second service stage, wherein the QoS policy is used for the third device to identify the first service stage and the second service stage according to the service stage sign indicated in the QoS policy.

33. The second device as claimed in claim 31, further comprising:

an identifying unit, configured to identify the first service stage and the first QoS requirement for the first service stage according to the first indication information; wherein the generating unit is configured to generate a first QoS policy according to the first QoS requirement for the first service stage, the first QoS policy is used for the third device to operate the service according to the first QoS requirement in the first service stage; and wherein the generating unit is configured to generate a second QoS policy according to the second QoS requirement for the second service stage, the second QoS policy is used for the third device to operate the service according to the second QoS requirement in the second service stage.

34. A method for controlling quality of service (QoS) of a service, wherein the service comprises a guaranteed bit rate (GBR) service having at least a first service stage and a second service stage, the method comprising:

receiving, by a second device, a QoS policy from a first device, wherein the QoS policy indicates the first QoS requirement for the first service stage, the second QoS requirement for the second service stage and the service stage sign used to identify the first service stage and the second service stage;

identifying, by the second device, the first service stage according to the service stage sign indicated in the QoS policy and identifying a first QoS requirement for the first service stage;

operating, by the second device, the service according to the first QoS requirement in the first service stage according to the QoS policy;

identifying, by the second device, the second service stage according to the service stage sign indicated in the QoS policy and identifying a second QoS requirement for the second service stage; operating, by the second device, the service according to the second QoS requirement in the second service stage according to the QoS policy.

35. A second device for controlling quality of service (QoS) of a service, wherein the service comprises a guaranteed bit rate (GBR) service having at least a first service stage and a second service stage, the device comprising:

a receiving unit, configured to receive a QoS policy from a first device, wherein the QoS policy indicates the first QoS requirement for the first service stage, the second QoS requirement for the second service stage and the service stage sign used to identify the first service stage and the second service stage;

an identifying unit, configured to identify the first service stage according to the service stage sign indicated in the QoS policy and to identify a first QoS requirement for the first service stage; an operating unit, configured to operate the service according to the first QoS requirement in the first service stage according to the QoS policy;

wherein the identifying unit is further configure to identify the second service stage according to the service stage sign indicated in the QoS policy and to identify a second QoS requirement for the second service stage, wherein the operating unit is further configured to operate the service according to the second QoS requirement in the second service stage according to the QoS policy.