CN106465194B - Method and apparatus for controlling QOS of service - Google Patents

Method and apparatus for controlling QOS of service Download PDF

Info

Publication number
CN106465194B
CN106465194B CN201480079810.9A CN201480079810A CN106465194B CN 106465194 B CN106465194 B CN 106465194B CN 201480079810 A CN201480079810 A CN 201480079810A CN 106465194 B CN106465194 B CN 106465194B
Authority
CN
China
Prior art keywords
qos
service
phase
traffic
traffic phase
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN201480079810.9A
Other languages
Chinese (zh)
Other versions
CN106465194A (en
Inventor
李铮铮
李海朝
吴秀峰
罗龙
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Publication of CN106465194A publication Critical patent/CN106465194A/en
Application granted granted Critical
Publication of CN106465194B publication Critical patent/CN106465194B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • H04W28/24—Negotiating SLA [Service Level Agreement]; Negotiating QoS [Quality of Service]

Landscapes

  • Engineering & Computer Science (AREA)
  • Quality & Reliability (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Embodiments of the present application provide a method and apparatus for controlling QoS of traffic. The traffic comprises GBR traffic having a first traffic phase and a second traffic phase. The method comprises the following steps: acquiring the service type of the service; acquiring a first QoS requirement aiming at the first service phase and a second QoS requirement aiming at the second service phase; and generating indication information indicating the first QoS requirements for the first traffic phase, the second QoS requirements for the second traffic phase, and a traffic phase flag identifying the first traffic phase and the second traffic phase. The indication is used to identify the traffic phase and generate a QoS policy to control QoS in the first traffic phase and to control QoS in the second traffic phase. According to the application, resources can be efficiently allocated while user experience is guaranteed.

Description

用于控制业务的QOS的方法和设备Method and apparatus for controlling QoS of services

技术领域technical field

本申请案涉及通信技术领域，并且具体来说，涉及一种用于控制业务的业务质量(quality of service，QoS)的方法和设备。The present application relates to the field of communication technologies, and in particular, to a method and device for controlling the quality of service (QoS) of a service.

背景技术Background technique

演进分组系统(Evolved packet system，EPS)是指代设计用于长期演进(longterm evolution，LTE)网络的架构的电信系统。EPS承载是满足EPS中某一业务质量(quality of service，QoS)的互联网协议(internet protocol，IP)流，且包含保证比特率(guaranteed bit rate，GBR)型承载和非GBR型承载。将特定资源分配到GBR型承载，使得即使在网络负载繁重或系统中出现任何拥塞时也能保证GBR型承载的带宽。非GBR型承载是尽力而为型承载，并且其带宽不受保证。GBR承载主要用于实时业务，例如基于互联网协议的语音发送(voice over Internet protocol，VoIP)业务，或在线视频或实时游戏，而非GBR承载主要用于非实时业务，例如电子邮件、文件传送协议(file transfer protocol，FTP)业务，或超文本传送协议(HTTP)业务。GBR业务的优先权高于非GBR业务的优先权。Evolved packet system (EPS) refers to a telecommunication system designed for the architecture of a long term evolution (LTE) network. An EPS bearer is an internet protocol (IP) stream that satisfies a certain quality of service (QoS) in the EPS, and includes a guaranteed bit rate (guaranteed bit rate, GBR) type bearer and a non-GBR type bearer. Allocate specific resources to GBR-type bearers so that the bandwidth of GBR-type bearers is guaranteed even when the network is heavily loaded or any congestion occurs in the system. Non-GBR bearers are best-effort bearers and their bandwidth is not guaranteed. GBR bearers are mainly used for real-time services, such as voice over Internet protocol (VoIP) services, or online video or real-time games, while non-GBR bearers are mainly used for non-real-time services, such as email, file transfer protocols (file transfer protocol, FTP) service, or hypertext transfer protocol (HTTP) service. The priority of GBR services is higher than that of non-GBR services.

GBR和最大比特率(maximum bit rate，MBR)是用于GBR业务的两种QoS参数。GBR指示带宽(也被称作比特率)由LTE网络保证，MBR指示LTE网络中所允许的最大比特率。数据流的比特率控制成高于GBR但低于MBR以满足QoS要求，所述QoS要求影响EPS中所有端到端网络节点的调度策略、队列管理、速率整形策略和无线链路控制(radio link control，RLC)配置。GBR and maximum bit rate (maximum bit rate, MBR) are two QoS parameters for GBR services. GBR indicates the bandwidth (also called bit rate) guaranteed by the LTE network, and MBR indicates the maximum bit rate allowed in the LTE network. The bit rate of the data flow is controlled to be higher than the GBR but lower than the MBR to meet the QoS requirements that affect the scheduling policy, queue management, rate shaping policy and radio link control (radio link control) of all end-to-end network nodes in the EPS. control, RLC) configuration.

然而，在为GBR业务建立GBR型承载时设定了GBR或MBR等QoS参数。因此，要么资源分配效率低下，要么无法保证用户体验。However, QoS parameters such as GBR or MBR are set when a GBR-type bearer is established for the GBR service. Therefore, either the resource allocation is inefficient, or the user experience cannot be guaranteed.

发明内容SUMMARY OF THE INVENTION

本发明的实施例提供一种用于控制业务的QoS的方法和设备。Embodiments of the present invention provide a method and device for controlling QoS of a service.

根据第一方面，提供用于控制业务的QoS的方法。所述业务包含具有至少第一业务阶段和第二业务阶段的GBR业务。由第一设备执行的方法包含：第一设备获取业务的业务类型。第一设备根据业务的业务类型获取针对第一业务阶段的第一QoS要求和针对第二业务阶段的第二QoS要求。第一设备产生第一指示信息，所述第一指示信息指示针对第一业务阶段的第一QoS要求、针对第二业务阶段的第二QoS要求，以及用于识别第一业务阶段和第二业务阶段的业务阶段标志。第一指示信息用于产生QoS策略，以便在第一业务阶段中根据QoS策略中指示的第一QoS要求控制QoS，以及在第二业务阶段中根据QoS策略中指示的第二QoS要求控制QoS。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 the first device includes: the first device acquires the service type of the service. The first device acquires the first QoS requirement for the first service phase and the second QoS requirement for the second service phase according to the service type of the service. The first device generates first indication information, where the first indication information indicates a first QoS requirement for the first service phase, a second QoS requirement for the second service phase, and is used to identify the first service phase and the second service Stages of business stage signs. The first indication information is used to generate a QoS policy to control QoS according to the first QoS requirement indicated in the QoS policy in the first service phase, and to control QoS according to the second QoS requirement indicated in the QoS policy in the second service phase.

在根据第一方面的方法的第一可能实施形式中，业务阶段标志以数据包的时间和所述数据包的包容量中的任一者或任何组合的形式表示。In a first possible implementation form of the method according to the first aspect, the service phase marker is represented in the form of any one or any combination of the time of the data packet and the packet capacity of the data packet.

在同样根据第一方面或根据第一方面的第一实施形式的方法的第二可能实施形式中，第一指示信息指示针对第一业务阶段的第一QoS要求和针对第二业务阶段的第二QoS要求，所述QoS要求对应于业务的第一等级的用户体验，第一指示信息指示进一步指示针对第一业务阶段的第三QoS要求和针对第二业务阶段的第四QoS要求，所述QoS要求对应于业务的第二等级的用户体验。In a second possible implementation form of the method also according to the first aspect or according to the first implementation form of the first aspect, the first indication information indicates a first QoS requirement for the first service phase and a second QoS requirement for the second service phase QoS requirements, the QoS requirements correspond to the user experience of the first level of the service, the first indication information indication further indicates a third QoS requirement for the first service phase and a fourth QoS requirement for the second service phase, the QoS requirements A second level of user experience corresponding to the service is required.

根据第二方面，提供一种用于控制业务的QoS的设备。所述业务包含具有至少第一业务阶段和第二业务阶段的GBR业务。所述设备包含第一获取单元、第二获取单元和产生单元。第一获取单元用于获取业务的业务类型。第二获取单元用于根据业务的业务类型获取针对第一业务阶段的第一QoS要求和针对第二业务阶段的第二QoS要求。产生单元用于产生第一指示信息，所述第一指示信息指示针对第一业务阶段的第一QoS要求、针对第二业务阶段的第二QoS要求，以及用于识别第一业务阶段和第二业务阶段的业务阶段标志。第一指示信息用于产生QoS策略，以便在第一业务阶段中根据QoS策略中指示的第一QoS要求控制QoS，以及在第二业务阶段中根据QoS策略中指示的第二QoS要求控制QoS。According to a second aspect, an apparatus 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 apparatus includes a first acquiring unit, a second acquiring unit and a generating unit. The first obtaining unit is used to obtain the service type of the service. The second obtaining unit is configured to obtain the first QoS requirement for the first service stage and the 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, the first indication information indicates a first QoS requirement for the first service stage, a second QoS requirement for the second service stage, and is used to identify the first service stage and the second service stage Business stage sign for business stage. The first indication information is used to generate a QoS policy to control QoS according to the first QoS requirement indicated in the QoS policy in the first service phase, and to control QoS according to the second QoS requirement indicated in the QoS policy in the second service phase.

在根据第二方面的设备的第一可能实施形式中，业务阶段标志以数据包的时间和所述数据包的包容量中的任一者或任何组合的形式表示。In a first possible implementation form of the device according to the second aspect, the service phase marker is represented in the form of any one or any combination of the time of the data packet and the packet capacity of the data packet.

在根据第二方面或根据第二方面的第一实施形式的设备的第二可能实施形式中，第一指示信息指示针对第一业务阶段的第一QoS要求和针对第二业务阶段的第二QoS要求，所述QoS要求对应于业务的第一等级的用户体验，第一指示信息进一步指示针对第一业务阶段的第三QoS要求和针对第二业务阶段的第四QoS要求，所述QoS要求对应于业务的第二等级的用户体验。In a second possible implementation form of the device according to the second aspect or the first implementation form according to the second aspect, the first indication information indicates a first QoS requirement for the first service phase and a second QoS for the second service phase requirements, the QoS requirements correspond to the user experience of the first level of the service, and the first indication information further indicates the third QoS requirements for the first service stage and the fourth QoS requirements for the second service stage, and the QoS requirements correspond to User experience at the second level of the business.

本发明的这些和其它方面将根据下文描述的实施例而显而易见。根据本申请案的实施例，第一设备产生第一指示信息，其指示针对不同业务阶段的不同QoS要求和用于识别不同业务阶段的业务阶段标志。根据第一指示信息，对第一业务阶段和第二业务阶段加以识别，并产生QoS策略以在第一业务阶段中根据第一QoS要求控制QoS，以及在第二业务阶段中根据第二QoS要求控制QoS。在接收QoS策略之后，EPS中的每个节点在第一业务阶段中根据第一QoS要求操作业务，并在第二业务阶段中根据第二QoS要求操作业务。因此，满足针对业务的不同业务阶段的不同QoS要求。因此，能高效分配资源同时保证用户体验。These and other aspects of the invention will be apparent from the embodiments described hereinafter. According to an embodiment of the present application, the first device generates first indication information, which indicates different QoS requirements for different service stages and service stage flags for identifying 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 according to the second QoS requirement in the second service stage Control QoS. After receiving the QoS policy, each node in the EPS operates the service according to the first QoS requirement in the first service phase and operates the service according to the second QoS requirement in the second service phase. Therefore, different QoS requirements for different service stages of the service are met. Therefore, resources can be efficiently allocated while ensuring user experience.

附图说明Description of drawings

为了更清楚地说明本发明实施例中的技术方案，下面将对实施例描述中所需要使用的附图作简单地介绍。显而易见地，下面描述中的附图仅仅是本发明的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其它的附图。In order to illustrate the technical solutions in the embodiments of the present invention more clearly, the following briefly introduces the accompanying drawings that need to be used in the description of the embodiments. Obviously, the drawings in the following description are only some embodiments of the present invention, and for those of ordinary skill in the art, other drawings can also be obtained from these drawings without creative effort.

图1A示出了用于建立EPS承载的方法的图式；1A shows a diagram of a method for establishing an EPS bearer;

图1B示出了用于修改EPS承载的QoS参数的方法的图式；FIG. 1B shows a diagram of a method for modifying QoS parameters of an EPS bearer;

图2A示出了根据本发明的一个实施例的用于控制业务的QoS的方法的图式；2A shows a schematic diagram of a method for controlling QoS of a service according to one embodiment of the present invention;

图2B示出了根据本发明的一个实施例的用于当业务识别模块集成在第一设备上时控制业务的QoS的方法；2B shows a method for controlling the QoS of a service when a service identification module is integrated on the first device according to an embodiment of the present invention;

图2C示出了根据本发明的一个实施例的用于当业务识别模块集成在另一第一设备上时控制业务的QoS的方法；2C shows a method for controlling the QoS of a service when a service identification module is integrated on another first device according to an embodiment of the present invention;

图3A和图3B、图3C和图3D分别示出了根据本发明的一个实施例的用于控制业务的QoS的方法的四个实例；Figure 3A and Figure 3B, Figure 3C and Figure 3D respectively show four examples of a method for controlling QoS of a service according to an embodiment of the present invention;

图4A、图4B和图4C分别示出了根据本发明的一个实施例的用于控制业务的QoS的方法的三个实例；4A, 4B and 4C respectively illustrate three examples of a method for controlling QoS of a service according to an embodiment of the present invention;

图5示出了根据本发明的一个实施例的用于控制业务的QoS的设备的简化框图；5 shows a simplified block diagram of an apparatus for controlling QoS of a service according to an embodiment of the present invention;

图6A、图6B和图6C分别示出了根据本发明的一个实施例的用于控制业务的QoS的设备的三个实例；以及6A, 6B and 6C respectively illustrate three examples of an apparatus for controlling QoS of a service according to an embodiment of the present invention; and

图7A和图7B分别示出了根据本发明的一个实施例的用于控制业务的QoS的第二设备的简化框图。7A and 7B respectively show simplified block diagrams of a second device for controlling QoS of a service according to an embodiment of the present invention.

具体实施方式Detailed ways

下面将结合本发明实施例中的附图，对本发明实施例中的技术方案进行清楚、完整地描述。显然，所描述的实施例仅是本发明一部分实施例，而不是全部的实施例。基于本发明中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其它实施例，都属于本发明保护的范围。The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are only some, but not all, embodiments of the present invention. Based on the embodiments of the present invention, all other embodiments obtained by those of ordinary skill in the art without creative efforts shall fall within the protection scope of the present invention.

图1A示出了用于建立EPS承载的方法的图式，图1B示出了用于更新EPS承载参数的常规方法的图式。在图1A和图1B中所示的实例中，EPS 100包含用户设备(user equipment，UE)101、eNodeB 102(在下文中称为“eNB”)、移动性管理实体(MME)103、服务网关(servinggateway，SGW)104、分组数据网络网关(packet data network gateway，PGW)105，以及策略和计费规则功能(policy and charging rules function，PCRF)106。通过使用下文在图1A和图1B中所描述的方法，将由PCRF 106产生的QoS策略发送到EPS 100中的每个其它节点，例如，UE 101、eNB 102、MME 103、SGW 104或PGW 105。FIG. 1A shows a diagram of a method for establishing an EPS bearer, and FIG. 1B shows a diagram of a conventional method for updating EPS bearer parameters. In the example shown in FIGS. 1A and 1B, the EPS 100 includes a user equipment (UE) 101, an eNodeB 102 (hereinafter referred to as "eNB"), a mobility management entity (MME) 103, a serving gateway ( A serving gateway (SGW) 104 , a packet data network gateway (PGW) 105 , and a policy and charging rules function (PCRF) 106 . The QoS policy generated by PCRF 106 is sent to each other node in EPS 100, eg, UE 101, eNB 102, MME 103, SGW 104, or PGW 105, using the methods described below in Figures 1A and 1B.

PCRF 106用于动态地产生QoS策略，并将指示业务的QoS要求的QoS策略发送到PGW105。PGW 105用于执行QoS策略。在通过SGW 104和MME 103转发QoS策略之后，eNB 102根据QoS参数利用UE 101建立承载。PCRF 106 is used to dynamically generate QoS policies and send the QoS policies to PGW 105 indicating the QoS requirements of the service. PGW 105 is used to enforce QoS policies. After forwarding the QoS policy through the SGW 104 and the MME 103, the eNB 102 establishes a bearer with the UE 101 according to the QoS parameters.

例如，如图1A中所示，用于建立网络侧所请求的EPS承载的方法包含：For example, as shown in FIG. 1A , the method for establishing the EPS bearer requested by the network side includes:

在步骤1中：通过启动IP连通性接入网(IP-connectivity access network，IP-CAN)会话修改程序，PCRF 106动态地产生QoS策略，并将指示业务的QoS要求的QoS策略发送到PGW 105。In step 1: PCRF 106 dynamically generates a QoS policy by initiating an IP-connectivity access network (IP-CAN) session modification procedure and sends the QoS policy indicating the QoS requirements of the service to PGW 105 .

在步骤2中：PGW 105使用此QoS策略对EPS承载的QoS参数分配值，并将指示QoS参数的创建承载请求发送到SGW 104。In step 2: PGW 105 assigns values to QoS parameters of EPS bearers using this QoS policy and sends a create bearer request to SGW 104 indicating the QoS parameters.

在步骤3中：SGW 104将创建承载请求转发到MME 103。In step 3: SGW 104 forwards the create bearer request to MME 103.

在步骤4中：MME 103将指示EPS承载的QoS参数的承载设置请求消息或会话管理请求传信到eNB 102。In step 4: MME 103 signals to eNB 102 a bearer setup request message or a session management request indicating the QoS parameters of the EPS bearer.

在步骤5和6中，eNB 102将EPS承载的QoS参数映射到无线承载的QoS参数。随后，它将RRC连接重配置消息传信到UE 101。UE 101利用RRC连接重配置完成消息向eNB 102确认无线承载激活。In steps 5 and 6, the eNB 102 maps the QoS parameters of the EPS bearers to the QoS parameters of the radio bearers. It then signals an RRC connection reconfiguration message to the UE 101 . The UE 101 confirms the radio bearer activation to the eNB 102 using the RRC connection reconfiguration complete message.

在步骤7到12中，通过直接传送、会话管理响应、承载设置响应、创建承载响应和IP-can会话修改确认承载激活。In steps 7 to 12, bearer activation is confirmed by direct transfer, session management response, bearer setup response, create bearer response and IP-can session modification.

如图1B中所示，用于更新网络侧所请求的EPS承载参数的方法包含：As shown in FIG. 1B , the method for updating the EPS bearer parameters requested by the network side includes:

在步骤1'中：通过启动IP-CAN会话修改程序，PCRF 106动态地产生QoS策略，并将指示业务的QoS要求的QoS策略发送到PGW 105；In step 1': by starting the IP-CAN session modification procedure, PCRF 106 dynamically generates a QoS policy, and sends the QoS policy indicating the QoS requirements of the service to PGW 105;

在步骤2'中：PGW 105使用此QoS策略对EPS承载的QoS参数分配值，并将指示QoS参数的更新承载请求发送到SGW 104；In step 2': the PGW 105 uses this QoS policy to assign values to the QoS parameters of the EPS bearer, and sends an update bearer request indicating the QoS parameters to the SGW 104;

在步骤3'中：SGW 104将更新承载请求转发到MME 103；In step 3': the SGW 104 forwards the update bearer request to the MME 103;

在步骤4'中：MME 103将指示EPS承载的QoS参数的会话管理请求或承载修改请求消息发送到eNB 102；In step 4': the MME 103 sends a session management request or a bearer modification request message indicating the QoS parameters of the EPS bearer to the eNB 102;

在步骤5'和6'中，eNB 102将EPS承载的QoS参数映射到无线承载的QoS参数。随后，它将RRC连接重配置消息传信到UE 101。UE 101利用RRC连接重配置完成消息向eNB 102确认无线承载激活；In steps 5' and 6', the eNB 102 maps the QoS parameters of the EPS bearers to the QoS parameters of the radio bearers. It then signals an RRC connection reconfiguration message to the UE 101 . UE 101 confirms radio bearer activation to eNB 102 using the RRC connection reconfiguration complete message;

在步骤7'到12'中，通过直接传送、会话管理响应、承载修改响应、更新承载响应和IP-can会话修改确认承载修改。In steps 7' to 12', bearer modification is confirmed by direct transfer, session management response, bearer modification response, update bearer response and IP-can session modification.

在常规方法中，在如图1A中所示建立EPS承载时或在如图1B中所示修改EPS承载参数时设定QoS参数，并使QoS参数在整个业务期间保持恒定。根据本申请案的实施例，公开一种用于控制业务的QoS的方法，使得EPS中的每个节点在不同业务阶段中根据不同QoS要求操作。In a conventional method, QoS parameters are set when the EPS bearer is established as shown in FIG. 1A or when the EPS bearer parameters are modified as shown in FIG. 1B , and the QoS parameters are kept constant throughout the service period. According to an embodiment of the present application, a method for controlling QoS of a service is disclosed so that each node in an EPS operates according to different QoS requirements in different service phases.

图2A示出了根据本发明的一个实施例的用于控制业务的QoS的方法的流程图。所述方法适用于EPS 200，其包含UE 201、eNB 202、MME 203、SGW 204、PGW 205以及PCRF 206。FIG. 2A shows a flowchart of a method for controlling QoS of a service according to one embodiment of the present invention. The method is applicable to EPS 200 which includes UE 201 , eNB 202 , MME 203 , SGW 204 , PGW 205 and PCRF 206 .

EPS 200进一步包含业务识别模块207。实施业务识别模块207的功能的设备是第一设备。在一个实施例中，业务识别模块207是功能模块，其可在EPS 200中的任何节点上集成为第一设备，例如，UE 201、eNB 202、MME 203、SGW 204、PGW 205或PCRF 206。在另一实施例中，业务识别模块207可在独立硬件设备上实施为第一设备，例如，控制器。EPS 200 further includes service identification module 207 . The device implementing the functions of the service identification module 207 is the first device. In one embodiment, the service identification module 207 is a functional module that can be integrated as a first device on any node in the EPS 200, eg, UE 201, eNB 202, MME 203, SGW 204, PGW 205 or PCRF 206. In another embodiment, the service identification module 207 may be implemented as a first device on a separate hardware device, eg, a controller.

用于控制EPS 200中的业务的QoS的方法包含：Methods for controlling the QoS of traffic in EPS 200 include:

S210：第一设备获取业务的业务类型。S210: The first device acquires the service type of the service.

业务类型可包含但不限于VoIP业务或在线视频业务等。The service type may include, but is not limited to, VoIP service or online video service.

在一个实施例中，业务包含GBR业务，其具有若干业务阶段，并具有针对业务的不同业务阶段的不同QoS要求。例如，业务具有第一业务阶段和第二业务阶段，并具有针对第一业务阶段的第一QoS要求和针对第二业务阶段的第二QoS要求。QoS要求可包含对QoS参数的要求，所述QoS参数例如GBR、MBR、时延、抖动或错误包速率。In one embodiment, the service includes GBR service, which has several service phases and has different QoS requirements for different service phases of the service. For example, a service has a first service phase and a second service phase, and has a first QoS requirement for the first service phase and a second QoS requirement for the second service phase. QoS requirements may include requirements for QoS parameters such as GBR, MBR, delay, jitter or error packet rate.

以在线视频业务为例。在线视频业务具有作为第一业务阶段的缓冲阶段和作为第二业务阶段的播放阶段。在一个例子中，在线视频业务具有对缓冲阶段的GBR参数的第一要求GBR1(例如，GBR1大于或等于6Mbps)，并具有对播放阶段的GBR参数的第二要求GBR2(例如，GBR2大于或等于900Kbps)。在一个例子中，GBR1设定成高于GBR2。Take the online video business as an example. The online video service has a buffering phase as the first service phase and a playback phase as the second service phase. In one example, the online video service has a first requirement GBR1 (eg, GBR1 greater than or equal to 6 Mbps) for GBR parameters in the buffering phase, and has a second requirement GBR2 (eg, GBR2 greater than or equal to 6 Mbps) for GBR parameters in the playback phase 900Kbps). In one example, GBR1 is set higher than GBR2.

S220：第一设备根据业务类型获取针对业务的不同业务阶段的不同QoS要求。例如，根据业务类型，第一设备获取针对第一业务阶段的第一QoS要求和针对第二业务阶段的第二QoS要求。S220: The first device acquires 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 phase and the second QoS requirement for the second service phase.

S230：第一设备产生第一指示信息。第一指示信息指示针对不同业务阶段的不同QoS要求和用于识别不同业务阶段的业务阶段标志。例如，第一指示信息指示针对第一业务阶段的第一QoS要求、针对第二业务阶段的第二QoS要求，以及用于识别第一业务阶段和第二业务阶段的业务阶段标志。第一指示信息用于产生QoS策略，以便在第一业务阶段中根据QoS策略中指示的第一QoS要求控制QoS，以及在第二业务阶段中根据QoS策略中指示的第二QoS要求控制QoS。S230: The first device generates first indication information. The first indication information indicates different QoS requirements for different service stages and service stage flags for identifying different service stages. For example, the first indication information indicates a first QoS requirement for the first service phase, a second QoS requirement for the second service phase, and a service phase flag for identifying the first service phase and the second service phase. The first indication information is used to generate a QoS policy to control QoS according to the first QoS requirement indicated in the QoS policy in the first service phase, and to control QoS according to the second QoS requirement indicated in the QoS policy in the second service phase.

有利的是，第一设备产生指示针对不同业务阶段的不同QoS要求和用于识别不同业务阶段的业务阶段标志的第一指示信息。根据第一指示信息，对第一业务阶段和第二业务阶段加以识别，并产生QoS策略，以在第一业务阶段中根据第一QoS要求控制QoS，在第二业务阶段中根据第二QoS要求控制QoS。在接收QoS策略之后，EPS 200中的每个节点，例如，UE 201、eNB 202、MME 203、SGW 204或PGW 205，根据每个业务阶段中的所要QoS要求操作业务。例如，EPS 200中的每个节点在第一业务阶段中根据第一QoS要求操作业务，在第二业务阶段中根据第二QoS要求操作业务。以eNB 202为更特定的实例，eNB 202在第一业务阶段中以GBR1的比特率调度数据包，在第二业务阶段中以GBR2的比特率调度数据包。以UE 201为另一特定的实例，类似地，UE 201在第一业务阶段中以GBR1的比特率接收数据包，在第二业务阶段中以GBR2的比特率接收数据包。因此，满足了针对业务的不同业务阶段的不同QoS要求。例如，视频业务在缓冲阶段以6Mbps的GBR进行调度，在播放阶段以900Kbps的GBR进行调度。在缓冲阶段，满足相对较高水平的GBR以保证用户体验。在播放阶段，满足相对较低水平的GBR以保持更少的资源，这能增加其它UE的比特率。因此，能高效分配资源同时保证用户体验。Advantageously, the first device generates first indication information indicating different QoS requirements for different service stages and service stage flags for identifying 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 according to the second QoS requirement in the second service stage Control QoS. After receiving the QoS policy, each node in EPS 200, eg, UE 201, eNB 202, MME 203, SGW 204 or PGW 205, operates the traffic according to the desired QoS requirements in each traffic phase. For example, each node in EPS 200 operates a service according to a first QoS requirement in a first service phase and operates a service according to a second QoS requirement in a second service phase. Taking the eNB 202 as a more specific example, the eNB 202 schedules data packets at the bit rate of GBR1 in the first traffic phase and schedules the data packets at the bit rate of GBR2 in the second traffic phase. Taking UE 201 as another specific example, similarly, UE 201 receives data packets at the bit rate of GBR1 in the first service phase, and receives data packets at the bit rate of GBR2 in the second service phase. Therefore, different QoS requirements for different service stages of the service are met. For example, a video service is scheduled with a GBR of 6 Mbps in the buffering stage, and is scheduled with a GBR of 900 Kbps in the playback stage. In the buffering phase, a relatively high level of GBR is met to guarantee user experience. During the playback phase, a relatively low level of GBR is met to keep fewer resources, which can increase the bit rate of other UEs. Therefore, resources can be efficiently allocated while ensuring user experience.

在实施例的第一实施方案中，业务识别模块207集成在第一设备2091上，所述第一设备2091包含UE 201、eNB 202、MME 203、SGW 204或PGW 205。因此，如图2B中所示，所述方法进一步包含：In the first implementation of the embodiment, the service identification module 207 is integrated on the first device 2091 , and the first device 2091 includes the UE 201 , the eNB 202 , the MME 203 , the SGW 204 or the PGW 205 . Accordingly, as shown in Figure 2B, the method further comprises:

S240：第一设备根据第一指示信息将指示信息发送到PCRF 206。指示信息供PCRF206用来产生QoS策略。因此，PCRF 206根据指示信息产生QoS策略，如S820中所示。S240: The first device sends the indication information to the PCRF 206 according to the first indication information. The indication information is used by PCRF 206 to generate QoS policies. Therefore, the PCRF 206 generates a QoS policy according to the indication information, as shown in S820.

S250：在PCRF 206产生QoS策略之后，第一设备从PCRF 206接收QoS策略。S250: After the PCRF 206 generates the QoS policy, the first device receives the QoS policy from the PCRF 206.

S260：在第一业务阶段中，第一设备根据如QoS策略中所指示的第一QoS要求操作业务。S260: In the first service phase, the first device operates the service according to the first QoS requirement as indicated in the QoS policy.

S270：在第二业务阶段中，第一设备根据如QoS策略中所指示的第二QoS要求操作业务。S270: In the second service phase, the first device operates the service according to the second QoS requirement as indicated in the QoS policy.

在实施例的第二实施方案中，业务识别模块207集成在第一设备2092上，所述第一设备2092包含PCRF 206。因此，如图2C中所示，所述方法进一步包含：In a second implementation of the embodiment, the service identification module 207 is integrated on the first device 2092 , which includes the PCRF 206 . Accordingly, as shown in Figure 2C, the method further comprises:

S280：第一设备根据第一指示信息产生QoS策略。S280: The first device generates a QoS policy according to the first indication information.

S290：第一设备将QoS策略发送到第二设备2093，例如，第二设备2093可包含UE201、eNB 202、MME 203、SGW 204或PGW 205。QoS 策略供第二设备用来在不同业务阶段中根据不同QoS要求操作业务。例如，QoS策略供第二设备用来在第一业务阶段中根据第一QoS要求操作业务，以及在第二业务阶段中根据第二QoS要求操作业务。因此，第二设备在第一业务阶段中根据第一QoS要求操作业务，如S620中所示，在第二业务阶段中根据第二QoS要求操作业务，如S720中所示。S290: The first device sends the QoS policy to the second device 2093, for example, the second device 2093 may include the UE 201, the eNB 202, the MME 203, the SGW 204 or the PGW 205. The QoS policy is used by the second device to operate the service according to different QoS requirements in different service phases. For example, the QoS policy is used by the second device to operate the service according to the first QoS requirement in the first service phase and to operate the service according to the second QoS requirement in the second service phase. Therefore, the second device operates the service according to the first QoS requirement in the first service phase, as shown in S620, and operates the service according to the second QoS requirement in the second service phase, as shown in S720.

图3A、图3B、图3C和图3D示出了用于控制业务的QoS的方法的四个实例。图3A、图3B、图3C和图3D相对于图2B进行描述。在图2B中的实施例的第一实施方案中，业务识别模块207集成在第一设备2091上，所述第一设备2091包含UE 201、eNB 202、MME 203、SGW 204或PGW 205。Figures 3A, 3B, 3C and 3D illustrate four examples of methods for controlling the QoS of traffic. Figures 3A, 3B, 3C, and 3D are described with respect to Figure 2B. In the first implementation of the embodiment in FIG. 2B , the service identification module 207 is integrated on the first device 2091 , which includes the UE 201 , the eNB 202 , the MME 203 , the SGW 204 or the PGW 205 .

在图3A中所示的实例中，第一设备2091从第三设备接收指示业务的业务类型的消息。例如，第三设备包含EPS 200中的业务提供商208，执行步骤S211、S212和S213以实现图2A中的S210。In the example shown in Figure 3A, the first device 2091 receives a message from the third device indicating the service type of the service. For example, if the third device includes the service provider 208 in the EPS 200, steps S211, S212 and S213 are performed to implement S210 in FIG. 2A.

S211：由业务提供商208接收业务请求。例如，当UE 201开始使用业务，例如，在线视频业务时，UE 201将业务请求发送到业务提供商208。S211: The service request is received by the service provider 208. For example, when UE 201 starts using a service, eg, an online video service, UE 201 sends a service request to service provider 208 .

S212：业务提供商208将指示UE身份(identification，ID)和业务的业务类型的消息0发送到第一设备。S212: The service provider 208 sends a message 0 indicating the UE identity (identification, ID) and the service type of the service to the first device.

S213：在第一设备从业务提供商208接收到消息0之后，第一设备获取业务的业务类型。S213: After the first device receives the message 0 from the service provider 208, the first device acquires the service type of the service.

在另一例子中，当第一设备是UE 201时，第一设备可识别业务的业务类型。例如，当用户在UE 201开始业务时，UE 201用于识别业务的业务类型。In another example, when the first device is UE 201, the first device may identify the service type of the service. For example, when the user starts a service at the UE 201, the UE 201 is used to identify the service type of the service.

在图3A中所示的实例中，执行S221以实现图2A中的S220。In the example shown in FIG. 3A, S221 is performed to implement S220 in FIG. 2A.

S221：第一设备根据业务的业务类型和用户签约数据获取针对不同业务阶段的不同QoS要求。在一个例子中，第一设备根据UE ID从EPS 200中的归属用户业务器(homesubscriber server，HSS)获取用户签约数据。S221: The first device acquires different QoS requirements for different service stages according to the service type of the service and user subscription data. In one example, the first device acquires user subscription data from a home subscriber server (home subscriber server, HSS) in the EPS 200 according to the UE ID.

在图3A中所示的实例中，执行S231以实现图2A中的S230。In the example shown in FIG. 3A, S231 is performed to implement S230 in FIG. 2A.

S231：第一设备产生第一指示信息，其指示针对业务的所有业务阶段的所有QoS要求以及用以识别业务阶段的业务阶段标志。例如，第一指示信息指示针对第一业务阶段的第一QoS要求、针对第二业务阶段的第二QoS要求，又指示用于识别第一业务阶段和第二业务阶段的业务阶段标志。因此，第一指示信息可包含若干字段，如表1中所示。S231: The first device generates first indication information, which indicates all QoS requirements for all service phases of the service and a service phase flag used to identify the service phase. For example, the first indication information indicates a first QoS requirement for the first service phase, a second QoS requirement for the second service phase, and a service phase flag for identifying the first service phase and the second service phase. Therefore, the first indication information may contain several fields, as shown in Table 1.

Figure GDA0002210638600000101
Figure GDA0002210638600000101

表1Table 1

如表1中所示，字段1用于表示业务类型，字段2用于表示业务阶段标志，字段3和字段4分别用于表示针对第一业务阶段的第一QoS要求和针对第二业务阶段的第二QoS要求。As shown in Table 1, field 1 is used to indicate the service type, field 2 is used to indicate the service stage flag, and field 3 and field 4 are used to indicate the first QoS requirement for the first service stage and the second service stage respectively. Second QoS requirement.

字段2中的业务阶段标志用于识别不同业务阶段。例如，在一个例子中，业务阶段标志以时间形式表示：从业务开始到时间点T1的时段对应于第一业务阶段，从时间点T1到时间点T2的时段对应于第二业务阶段。在另一例子中，业务阶段标志以包容量形式表示：从业务开始时计算的包容量为X1的数据包对应于第一业务阶段，包容量为X1的数据包之后的包容量为X2的数据包对应于第二业务阶段。在又一例子中，业务阶段标志以时间和包容量的组合的形式表示。The business stage flags in field 2 are used to identify different business stages. For example, in one example, the service stage indicator is expressed in time form: the period from the start of the service to the time point T1 corresponds to the first service stage, and the period from the time point T1 to the time point T2 corresponds to the second service stage. In another example, the service phase flag is expressed in the form of packet capacity: the data packet with the packet capacity X1 calculated from the start of the service corresponds to the first service phase, and the data packet with the packet capacity X2 after the data packet with the packet capacity X1 The package corresponds to the second service phase. In yet another example, the service phase indicator is expressed in the form of a combination of time and packet size.

任选地，根据用户体验的等级进一步区分指示针对不同业务阶段的不同QoS要求的第一指示信息。例如，用户体验的等级包含极佳、良好、一般或不佳。以在线视频业务为例，当视频业务具有较快开始速度(少于2.5秒)并且播放流畅时，用户体验极佳。当视频业务具有正常开始速度(少于4秒)并且视频每小时卡住少于1.5次时，用户体验良好。当开始视频业务花费4到10秒，或视频每小时卡住1.5到5次时，用户体验一般。在其余情形中，用户体验不佳。Optionally, the first indication information indicating different QoS requirements for different service stages is further distinguished according to the level of user experience. For example, the user experience rating includes excellent, good, fair, or poor. Taking the online video service as an example, when the video service has a fast start speed (less than 2.5 seconds) and plays smoothly, the user experience is excellent. The user experience is good when the video traffic has a normal start speed (less than 4 seconds) and the video gets stuck less than 1.5 times per hour. The user experience is mediocre when it takes 4 to 10 seconds to start a video service, or the video gets stuck 1.5 to 5 times an hour. In the remaining cases, the user experience is poor.

用户体验的每个等级对应于针对不同业务阶段的不同QoS要求。例如，为了具有极佳的用户体验，针对第一业务阶段，例如针对缓冲阶段的GBR要求是每秒6Mbit，针对第二业务阶段，例如针对播放阶段的GBR要求是每秒900Kbit。为了具有良好的用户体验，针对第一业务阶段的GBR要求是每秒3Mbit，针对第二业务阶段的GBR要求是每秒720Kbit。可根据用户签约数据和EPS 200的目前网络状态，选择对应于特定用户体验的不同QoS要求的集合。因此，在一个例子中，第一指示信息可包含若干字段，如表2中所示。Each level of user experience corresponds to different QoS requirements for different service stages. For example, in order to have an excellent user experience, the GBR requirement for the first service stage, eg, the buffer stage, is 6 Mbits per second, and the GBR requirement for the second service stage, eg, the playback stage, is 900Kbits per second. In order to have a good user experience, the GBR requirement for the first service stage is 3Mbits per second, and the GBR requirement for the second service stage is 720Kbits per second. A set of different QoS requirements corresponding to a particular user experience may be selected based on the user subscription data and the current network state of the EPS 200 . Therefore, in one example, the first indication information may contain several fields, as shown in Table 2.

表2Table 2

应理解，第一指示信息不限于表1或表2中所示的形式。只要第一指示信息指示针对业务的不同业务阶段的不同QoS要求，它就在本发明的范围中。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 phases of the service, it is within the scope of the present invention.

在图3A中的实例中，第一指示信息供PCRF 206用来产生QoS策略。分别执行S241和S821以实现图2B中的S240和S820。In the example in FIG. 3A, the first indication information is used by PCRF 206 to generate a QoS policy. S241 and S821 are respectively performed to realize S240 and S820 in FIG. 2B .

S241：第一设备2091将第一指示信息发送到PCRF 206。PCRF 206从第一设备2091接收第一指示信息。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 .

S821：根据第一指示信息，PCRF 206产生QoS策略，其指示业务阶段标志和针对不同业务阶段的对应的不同QoS要求。在一个例子中，PCRF 206根据呈表1的形式的第一指示信息产生QoS策略。在另一例子中，PCRF 206根据用户签约数据和EPS 200的目前网络状态选择用户体验，并根据呈表2的形式的第一指示信息产生对应于所选用户体验的QoS策略。在这两种情形中，所产生的QoS策略供第三设备用来在第一业务阶段中根据第一QoS要求操作业务，在第二业务阶段中根据第二QoS要求操作业务。第三设备包含除了PCRF 206外的EPS 200中的每个节点，例如，UE 201、eNB 202、MME 203、SGW 204或PGW 205。第三设备包含第一设备2091。在图3A中，QoS策略指示针对第一业务阶段的第一QoS要求、针对第二业务阶段的第二QoS要求以及业务阶段标志。S821: According to the first indication information, the PCRF 206 generates a QoS policy, which indicates a service stage flag and corresponding different QoS requirements for different service stages. In one example, PCRF 206 generates a QoS policy based on the first indication information in the form of Table 1 . In another example, PCRF 206 selects a user experience according to the user subscription data and the current network state of EPS 200, and generates a QoS policy corresponding to the selected user experience according to the first indication in the form of Table 2. In both cases, the generated QoS policy is used by the third device to operate the service according to the first QoS requirement in the first service phase and according to the second QoS requirement in the second service phase. The third device includes every node in EPS 200 except PCRF 206, eg UE 201, eNB 202, MME 203, SGW 204 or PGW 205. The third device includes the first device 2091 . In Figure 3A, the QoS policy indicates a first QoS requirement for the first service phase, a second QoS requirement for the second service phase, and a service phase flag.

随后，在S250中，PCRF 206将QoS策略发送到第三设备。例如，通过使用如图1A中所描述的承载建立方法，或通过如图1B中所描述的承载修改方法，将QoS策略发送到EPS 200中的节点。Then, in S250, the PCRF 206 sends the QoS policy to the third device. The QoS policy is sent to the nodes in EPS 200, for example, by using the bearer establishment method as described in FIG. 1A, or by the bearer modification method as described in FIG. 1B.

在图3A中的实例中，所述方法进一步包含：In the example in Figure 3A, the method further comprises:

S310：在接收到QoS策略之后，EPS 200中的每个节点(例如，PGW 205、SGW 204、MME203、eNB 202和UE 201)用于根据QoS策略识别业务阶段，并进一步用于识别业务阶段的QoS要求。例如，PGW 205在承载建立时识别第一业务阶段，并根据如QoS策略中指示的业务阶段标志识别之后的不同业务阶段。作为更特定的实例，PGW 205根据时间和数据容量中的至少一者识别之后的不同业务阶段。当时间T1截止和/或达到包容量X1时，PGW 205识别第二业务阶段。在识别业务阶段之后，PGW 205用于根据接收到的QoS策略识别业务阶段的QoS要求。EPS 200中的其它节点如何识别业务阶段和业务阶段的QoS要求类似于PGW 205，此处将不再重复。S310: After receiving the QoS policy, each node in the EPS 200 (eg, PGW 205, SGW 204, MME 203, eNB 202, and UE 201) is used to identify the service phase according to the QoS policy, and is further used to identify the QoS requirements. For example, the PGW 205 identifies the first service phase at bearer establishment, and identifies different service phases afterward according to the service phase flags as indicated in the QoS policy. As a more specific example, the PGW 205 identifies different traffic phases thereafter according to at least one of time and data capacity. When the time T1 expires and/or the packet capacity X1 is reached, the PGW 205 identifies the second traffic phase. After identifying the service phase, the PGW 205 is used to identify the QoS requirements of the service phase according to the received QoS policy. How other nodes in EPS 200 identify the traffic phase and the QoS requirements for the traffic phase is similar to PGW 205 and will not be repeated here.

因此，EPS 200中的每个节点在S260中在第一业务阶段根据第一QoS要求操作业务，并在S270中在第二业务阶段根据第二QoS要求操作业务。例如，在第一业务阶段中，SGW204以GBR1的比特率转发用户的数据包，eNB 202以GBR1的比特率调度所述数据包。在第二业务阶段中，SGW 204以GBR2的比特率转发用户的数据包，eNB 202以GBR2的比特率调度所述数据包。Therefore, each node in EPS 200 operates the service according to the first QoS requirement in the first service phase in S260 and operates the service according to the second QoS requirement in the second service phase in S270. For example, in the first service phase, the SGW 204 forwards the user's data packet at the bit rate of GBR1, and the eNB 202 schedules the data packet at the bit rate of GBR1. In the second service phase, the SGW 204 forwards the user's data packet at the bit rate of GBR2, and the eNB 202 schedules the data packet at the bit rate of GBR2.

图3B示出了用于控制业务的QoS的方法的另一实例。图3B相对于图2B和图3A进行描述。FIG. 3B shows another example of a method for controlling QoS of traffic. Figure 3B is described with respect to Figures 2B and 3A.

在图3B中所示的实例中，执行S210、S220、S231和S241。如何执行S210、S220、S231和S241的例子已经在图3A中加以描述，此处将不再重复。第一指示信息供PCRF 206用来识别业务阶段和业务阶段的QoS要求，并进一步产生QoS策略。因此，分别执行S822到824和S251到S252以实现图2B中的S820和S250。In the example shown in FIG. 3B, S210, S220, S231 and S241 are performed. An example of how to perform S210, S220, S231 and S241 has been described in FIG. 3A and will not be repeated here. The first indication information is used by the PCRF 206 to identify the service phase and the QoS requirements of the service phase, and further generate a QoS policy. Therefore, S822 to 824 and S251 to S252 are respectively performed to realize S820 and S250 in FIG. 2B .

S822：PCRF 206根据第一指示信息识别业务阶段和针对业务阶段的QoS要求。例如，PCRF 206在承载建立时识别第一业务阶段。在识别第一业务阶段之后，PCRF 206用于根据第一指示信息识别针对第一业务阶段的第一QoS要求。PCRF 206根据第一指示信息中的业务阶段标志识别之后的不同业务阶段。例如，PCRF 206根据时间或数据容量中的至少一者识别第二业务阶段。当时间T1截止和/或达到包容量X1时，PCRF 206识别第二业务阶段。在识别第二业务阶段之后，PCRF 206用于根据第一指示信息识别针对第二业务阶段的第二QoS要求。S822: The PCRF 206 identifies the service phase and the QoS requirement for the service phase according to the first indication information. For example, PCRF 206 identifies the first traffic phase at bearer establishment. After identifying the first service stage, the PCRF 206 is configured to identify the first QoS requirement for the first service stage according to the first indication information. The PCRF 206 identifies different service phases afterward according to the service phase flags in the first indication information. For example, PCRF 206 identifies the second traffic phase based on at least one of time or data volume. When the time T1 expires and/or the packet capacity X1 is reached, the PCRF 206 identifies the second traffic phase. After identifying the second service stage, the PCRF 206 is configured to identify the second QoS requirement for the second service stage according to the first indication information.

S823：当PCRF 206识别第一业务阶段和针对第一业务阶段的第一QoS要求时，PCRF206根据针对第一业务阶段的第一QoS要求产生第一QoS策略。第一QoS策略可以现有QoS策略的形式产生，无需修改。第一QoS策略供第三设备用来在第一业务阶段中根据第一QoS要求操作业务。S823: When the PCRF 206 identifies the first service phase and the first QoS requirement for the first service phase, the PCRF 206 generates a first QoS policy according to the first QoS requirement for the first service phase. The first QoS policy can be generated in the form of an existing QoS policy without modification. The first QoS policy is used by the third device to operate the service according to the first QoS requirement in the first service phase.

S251：第三设备，例如EPS 200中的每个节点，从PCRF 206接收第一QoS策略。因此，EPS 200中的每个节点在第一业务阶段中根据第一QoS要求操作业务，如S260中所描述。例如，在第一业务阶段中，SGW 204以GBR1的比特率转发用户的数据包，eNB 202以GBR1的比特率调度所述数据包。S251: A third device, eg, each node in the EPS 200, receives the first QoS policy from the PCRF 206. Therefore, each node in EPS 200 operates traffic according to the first QoS requirement in the first traffic phase, as described in S260. For example, in the first service phase, the SGW 204 forwards the user's data packet at the bit rate of GBR1, and the eNB 202 schedules the data packet at the bit rate of GBR1.

S824：当PCRF 206识别第二业务阶段和针对第二业务阶段的第二QoS要求时，PCRF206根据针对第二业务阶段的第二QoS要求产生第二QoS策略。第二QoS策略也可以现有QoS策略的形式产生，无需修改。第二QoS策略供第三设备用来在第二业务阶段中根据第二QoS要求操作业务。S824: When the PCRF 206 identifies the second service phase and the second QoS requirement for the second service phase, the PCRF 206 generates a second QoS policy according to the second QoS requirement for the second service phase. The second QoS policy can also be generated in the form of an existing QoS policy without modification. The second QoS policy is used by the third device to operate the traffic according to the second QoS requirement in the second traffic phase.

S252：第三设备，例如EPS 200中的每个节点，从PCRF 206接收第二QoS策略。因此，包含第一设备的EPS 200中的每个节点在第二业务阶段中根据第二QoS要求操作业务，如S270中所描述。例如，在第二业务阶段中，SGW 204以GBR2的比特率转发用户的数据包，eNB202以GBR2的比特率调度所述数据包。S252: A third device, eg, each node in the EPS 200, receives the second QoS policy from the PCRF 206. Therefore, each node in EPS 200 containing the first device operates traffic according to the second QoS requirement in the second traffic phase, as described in S270. For example, in the second service phase, the SGW 204 forwards the user's data packet at the bit rate of GBR2, and the eNB 202 schedules the data packet at the bit rate of GBR2.

有利的是，能高效分配资源同时保证用户体验。此外，由于PCRF 206用于识别业务阶段和针对业务阶段的对应的不同QoS要求，所以由PCRF 206产生的QoS策略可以现有QoS策略的形式实施，无需任何修改。因此，所产生的QoS策略不需要考虑业务阶段标志和针对不同业务阶段的对应的QoS要求。Advantageously, resources can be allocated efficiently while ensuring user experience. Furthermore, since PCRF 206 is used to identify service phases and corresponding different QoS requirements for the service phases, the QoS policies generated by PCRF 206 can be implemented in the form of existing QoS policies without any modification. Therefore, the generated QoS policy does not need to consider the service stage flags and the corresponding QoS requirements for different service stages.

图3C示出了用于控制业务的QoS的方法的另一实例。图3C相对于图2B进行描述。FIG. 3C shows another example of a method for controlling QoS of traffic. Figure 3C is described with respect to Figure 2B.

在图3C的实例中，执行S210、S220和S231。如何执行S210、S220和S231的例子已经在图3A中加以描述，此处将不再重复。In the example of FIG. 3C, S210, S220 and S231 are performed. An example of how to perform S210, S220 and S231 has been described in FIG. 3A and will not be repeated here.

在图3C中所示的实例中，方法进一步包含S232到S234。分别执行S242到S243和S825到S826以实现图2B中的S240和S820。In the example shown in FIG. 3C, the method further includes S232 to S234. S242 to S243 and S825 to S826 are respectively performed to realize S240 and S820 in FIG. 2B .

S232：第一设备根据第一指示信息识别针对第一业务阶段的第一QoS要求。S232: The first device identifies the first QoS requirement for the first service stage according to the first indication information.

S233：第一设备产生指示针对第一业务阶段的第一QoS要求的第二指示信息。S233: The first device generates second indication information indicating the first QoS requirement for the first service stage.

S242：第一设备将第二指示信息发送到PCRF 206。第二指示信息供PCRF 206用来产生指示针对第一业务阶段的第一QoS要求的第一QoS策略。S242: The first device sends the second indication information to the PCRF 206. The second indication information is used by PCRF 206 to generate a first QoS policy indicating the first QoS requirement for the first traffic phase.

S825：PCRF 206根据第二指示信息产生第一QoS策略。第一QoS策略可以现有QoS策略的形式产生，无需修改。S825: The PCRF 206 generates the first QoS policy according to the second indication information. The first QoS policy can be generated in the form of an existing QoS policy without modification.

S251：第一设备接收第一QoS策略。因此，EPS 200中的每个节点在第一业务阶段中根据第一QoS要求操作业务，如S260中所描述。S251: The first device receives the first QoS policy. Therefore, each node in EPS 200 operates traffic according to the first QoS requirement in the first traffic phase, as described in S260.

S234：第一设备根据第一指示信息识别针对第二业务阶段的第二QoS要求。S234: The first device identifies the second QoS requirement for the second service stage according to the first indication information.

S235：第一设备产生指示针对第二业务阶段的第二QoS要求的第三指示信息。S235: The first device generates third indication information indicating the second QoS requirement for the second service stage.

S243：第一设备将第三指示信息发送到PCRF 206。第三指示信息供PCRF 206用来产生指示针对第二业务阶段的第二QoS要求的第二QoS策略。S243: The first device sends the third indication information to the PCRF 206. The third indication information is used by PCRF 206 to generate a second QoS policy indicating the second QoS requirement for the second traffic phase.

S826：PCRF 206根据第三指示信息产生第二QoS策略。第二QoS策略也可以现有QoS策略的形式产生，无需修改。S826: The PCRF 206 generates a second QoS policy according to the third indication information. The second QoS policy can also be generated in the form of an existing QoS policy without modification.

S252：第一设备接收第二QoS策略。因此，EPS 200中的每个节点在第二业务阶段中根据第二QoS要求操作业务，如S270中所描述。S252: The first device receives the second QoS policy. Therefore, each node in EPS 200 operates traffic according to the second QoS requirement in the second traffic phase, as described in S270.

在图3C中所示的实例中，第一设备进一步用于识别业务阶段从而识别不同QoS要求。In the example shown in Figure 3C, the first device is further configured to identify the traffic phase and thus identify the different QoS requirements.

例如，在图3C中，分别执行S2321和S2341以实现S232和S234。For example, in FIG. 3C, S2321 and S2341 are performed to implement S232 and S234, respectively.

S2321：第一设备根据第一指示信息中指示的业务阶段标志识别第一业务阶段，从而识别针对第一业务阶段的第一QoS要求。例如，第一设备在承载建立时识别第一业务阶段。在识别第一业务阶段之后，第一设备用于识别针对第一业务阶段的第一QoS要求。S2321: The first device identifies the first service stage according to the service stage flag indicated in the first indication information, thereby identifying the first QoS requirement for the first service stage. For example, the first device identifies the first service phase when the bearer is established. After identifying the first traffic phase, the first device is used to identify the first QoS requirements for the first traffic phase.

S2341：第一设备根据第一指示信息中指示的业务阶段标志识别第二业务阶段，从而识别针对第二业务阶段的第二QoS要求。例如，第一设备根据时间或数据容量中的至少一者识别第二业务阶段。当时间T1截止和/或达到包容量X1时，第一设备识别第二业务阶段。在识别第二业务阶段之后，第一设备用于识别针对第二业务阶段的第二QoS要求。S2341: The first device identifies the second service phase according to the service phase flag indicated in the first indication information, thereby identifying the second QoS requirement for the second service phase. For example, the first device identifies the second traffic phase based on at least one of time or data volume. When the time T1 expires and/or the packet capacity X1 is reached, the first device identifies the second service phase. After identifying the second traffic phase, the first device is configured to identify second QoS requirements for the second traffic phase.

有利的是，能高效分配资源同时保证用户体验。此外，由于第一设备用于识别业务阶段，所以其在识别出第一业务阶段时将指示第一QoS要求的第二指示信息发送到PCRF206，并在识别出第二业务阶段时将指示第二QoS要求的第三指示信息发送到PCRF 206。根据接收到的指示信息，PCRF 206产生指示针对业务阶段的QoS要求的QoS策略。因此，所产生的QoS策略可以现有QoS策略的形式实施，无需任何修改。因此，所产生的QoS策略不需要考虑业务阶段标志和针对不同业务阶段的对应的QoS要求。Advantageously, resources can be allocated efficiently while ensuring user experience. In addition, since the first device is used to identify the service phase, it sends the second indication information indicating the first QoS requirement to the PCRF 206 when the first service phase is identified, and indicates the second service phase when the second service phase is identified. The third indication of QoS requirements is sent to PCRF 206 . Based on the received indication information, PCRF 206 generates a QoS policy indicating QoS requirements for the traffic phase. Therefore, the generated QoS policies can be implemented in the form of existing QoS policies without any modification. Therefore, the generated QoS policy does not need to consider the service stage flags and the corresponding QoS requirements for different service stages.

图3D示出了用于控制业务的QoS的方法的又一实例。图3D相对于图3C进行描述。与图3C标记相同的步骤以类似方式执行。Figure 3D shows yet another example of a method for controlling QoS of a traffic. Figure 3D is described with respect to Figure 3C. The same steps as labeled in Figure 3C are performed in a similar manner.

在图3D中，仅通过另外多个步骤来实施S232和S234。执行S2322到S2324和S2342到S2343以实现S232和S234。In FIG. 3D, S232 and S234 are only implemented by further steps. S2322 to S2324 and S2342 to S2343 are executed to realize S232 and S234.

S2322：第一设备发送请求以激活UE 201，从而识别第一业务阶段和第二业务阶段(当第一设备不是UE 201时)。S2322: The first device sends a request to activate the UE 201, thereby identifying the first service phase and the second service phase (when the first device is not the UE 201).

在一个例子中，在激活UE 201之后，UE 201根据软件操作指令和状态信息中的至少一者识别业务阶段。仍以视频业务为例，UE 201根据软件操作指令识别业务阶段包含：当用户点击图标以开始UE 201中的视频业务时，UE 201识别出视频业务进入第一业务阶段，例如，初始阶段。UE 201根据状态信息识别业务阶段包含：当缓冲区中的数据容量达到阈值时，例如，所述阈值设定为缓冲区容量的70％，UE 201识别出视频业务进入第二业务阶段，例如，播放阶段。In one example, after activating the UE 201, the UE 201 identifies the traffic phase according to at least one of software operating instructions and status information. Still taking the video service as an example, the UE 201 identifying the service stage according to the software operation instruction includes: when the user clicks the icon to start the video service in the UE 201, the UE 201 recognizes that the video service enters the first service stage, for example, the initial stage. The UE 201 identifying the service stage according to the status information includes: when the data capacity in the buffer reaches a threshold, for example, the threshold is set to 70% of the buffer capacity, the UE 201 identifies that the video service enters the second service stage, for example, Play stage.

在另一例子中，请求包含指示业务阶段标志的信息。业务阶段标志供UE 201用来识别不同业务阶段。业务阶段标志可以时间和包容量中的至少一个或组合的形式表示，如上文所描述。因此，UE 201根据时间和包容量中的至少一者识别业务阶段。In another example, the request contains information indicating a service phase flag. The service phase flags are used by the UE 201 to identify different service phases. The traffic phase indicator may be represented in at least one or a combination of time and packet size, as described above. Therefore, the UE 201 identifies the traffic phase according to at least one of time and packet capacity.

S2323：当UE 201识别出第一业务阶段时，第一设备接收UE 201报告的指示业务阶段是第一业务阶段的反馈消息4。S2323: When the UE 201 identifies the first service phase, the first device receives a feedback message 4 reported by the UE 201 indicating that the service phase is the first service phase.

S2324：在接收到UE 201报告的反馈消息4之后，第一设备识别针对第一业务阶段的第一QoS要求。S2324: After receiving the feedback message 4 reported by the UE 201, the first device identifies the first QoS requirement for the first service phase.

S2342：当UE 201识别出第二业务阶段时，第一设备接收UE 201报告的指示业务阶段是第二业务阶段的反馈消息5。S2342: When the UE 201 identifies the second service phase, the first device receives a feedback message 5 reported by the UE 201 indicating that the service phase is the second service phase.

S2343：在接收到UE 201报告的消息5之后，第一设备识别针对第二业务阶段的第二QoS要求。S2343: After receiving the message 5 reported by the UE 201, the first device identifies the second QoS requirement for the second service phase.

有利的是，由于第一设备激活UE 201以识别业务阶段，所以第一设备在UE 201识别出第一业务阶段时将指示第一QoS要求的第二指示信息发送到PCRF 206，并在UE 201识别出第二业务阶段时将指示第二QoS要求的第三指示信息发送到PCRF 206。根据接收到的指示信息，PCRF 206产生指示针对业务阶段的QoS要求的QoS策略。因此，由PCRF 206产生的QoS策略可以现有QoS策略的形式实施，无需任何修改。因此，所产生的QoS策略不需要考虑业务阶段标志和针对不同业务阶段的对应的QoS要求。Advantageously, since the first device activates the UE 201 to identify the service phase, the first device sends the second indication information indicating the first QoS requirement to the PCRF 206 when the UE 201 identifies the first service phase, and sends the second indication information to the PCRF 206 when the UE 201 recognizes the first service phase. Third indication information indicating the second QoS requirement is sent to the PCRF 206 when the second service phase is identified. Based on the received indication information, PCRF 206 generates a QoS policy indicating QoS requirements for the traffic phase. Therefore, the QoS policies generated by PCRF 206 can be implemented in the form of existing QoS policies without any modification. Therefore, the generated QoS policy does not need to consider the service stage flags and the corresponding QoS requirements for different service stages.

图4A、图4B和图4C示出了用于控制业务的QoS的方法的另外三个实例。图4A、图4B和图4C相对于图2C进行描述。在图2C中的实施例的第二实施方案中，业务识别模块207集成在包含PCRF 206的第一设备2092上。Figures 4A, 4B, and 4C illustrate three further examples of methods for controlling QoS of traffic. Figures 4A, 4B and 4C are described with respect to Figure 2C. In a second implementation of the embodiment in FIG. 2C , the service identification module 207 is integrated on the first device 2092 containing the PCRF 206 .

在图4A中，执行S211到S213、S221和S231。第一设备2092如何执行上述步骤的例子类似于第一设备2091，此处将不再重复。在图4A中的实例中，第一指示信息供第一设备2092用来产生QoS策略。在第一设备2092在S231中产生第一指示信息之后，执行S281以实现图2C中的S280。In FIG. 4A, S211 to S213, S221 and S231 are performed. An example of how the first device 2092 performs the above steps is similar to that of the first device 2091, and will not be repeated here. In the example in Figure 4A, the first indication information is used by the first device 2092 to generate a QoS policy. After the first device 2092 generates the first indication information in S231, S281 is performed to implement S280 in FIG. 2C.

S281：第一设备2092根据第一指示信息产生QoS策略。QoS策略指示针对第一业务阶段的第一QoS要求、针对第二业务阶段的第二QoS要求，以及业务阶段标志。第一设备2092如何产生指示针对第一业务阶段的第一QoS要求、针对第二业务阶段的第二QoS要求以及业务阶段标志的QoS策略的例子类似于如S821中所描述的PCRF 206如何产生QoS策略，此处将不再重复。随后，第一设备将QoS策略发送到第二设备，如S290中所描述。第二设备从第一设备接收QoS策略。QoS策略供第二设备用来识别业务阶段。S281: The first device 2092 generates a QoS policy according to the first indication information. The QoS policy indicates a first QoS requirement for the first service phase, a second QoS requirement for the second service phase, and a service phase flag. An example of how the first device 2092 generates a QoS policy indicating the first QoS requirement for the first service phase, the second QoS requirement for the second service phase, and the service phase flag is similar to how PCRF 206 generates QoS as described in S821 strategy, which will not be repeated here. Subsequently, 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 by the second device to identify the traffic phase.

在S320中，根据QoS策略，第二设备识别业务阶段和业务阶段的QoS要求。第二设备2093如何根据QoS策略识别业务阶段类似于如S310中所描述的第一设备2091如何识别业务阶段，此处将不再重复。因此，第二设备在第一业务阶段中根据第一QoS要求操作业务，如S620中所描述，在第二业务阶段中根据第二QoS要求操作业务，如S720中所描述。In S320, according to the QoS policy, the second device identifies the service phase and the QoS requirements of the service phase. How the second device 2093 identifies the service phase according to the QoS policy is similar to how the first device 2091 identifies the service phase as described in S310, and will not be repeated here. Therefore, the second device operates the service according to the first QoS requirement in the first service phase, as described in S620, and operates the service according to the second QoS requirement in the second service phase, as described in S720.

图4B示出了用于控制业务的QoS的方法的另一实例。图4B相对于图4A和图2C进行描述。FIG. 4B shows another example of a method for controlling the QoS of traffic. Figure 4B is described with respect to Figures 4A and 2C.

在图4B中所示的实例中，执行S210、S220和S231。如何执行S210、S220和S231的例子已经在图3A中加以描述，此处将不再重复。In the example shown in FIG. 4B, S210, S220 and S231 are performed. An example of how to perform S210, S220 and S231 has been described in FIG. 3A and will not be repeated here.

在图4B中所示的实例中，第一指示信息供PCRF 206等第一设备用来识别QoS要求并相应地产生QoS策略。分别执行S282到S285和S291到S292以实现图2C中的S280和S290。In the example shown in Figure 4B, the first indication information is used by a first device, such as PCRF 206, to identify QoS requirements and generate QoS policies accordingly. S282 to S285 and S291 to S292 are respectively performed to realize S280 and S290 in FIG. 2C .

S282：第一设备根据第一指示信息识别针对业务阶段的第一QoS要求。在图4B中，执行S2821以实现S282。S282: The first device identifies the first QoS requirement for the service phase according to the first indication information. In FIG. 4B, S2821 is performed to implement S282.

S2821：第一设备识别第一业务阶段，从而进一步识别针对所述业务阶段的第一QoS要求。例如，第一设备在承载建立时默认识别第一业务阶段。在识别第一业务阶段之后，第一设备根据第一指示信息识别针对第一业务阶段的第一QoS要求。S2821: The first device identifies the first service stage, so as to further identify the first QoS requirement for the service stage. For example, the first device identifies the first service phase by default when the bearer is established. After identifying the first service stage, the first device identifies the first QoS requirement for the first service stage according to the first indication information.

S283：当第一设备识别第一业务阶段时，第一设备根据针对第一业务阶段的第一QoS要求产生第一QoS策略。第一QoS策略可以现有QoS策略的形式产生，未需修改。S283: When the first device identifies the first service stage, the first device generates a first QoS policy according to the first QoS requirement for the first service stage. The first QoS policy can be generated in the form of an existing QoS policy without modification.

S291：第一设备将第一QoS策略发送到EPS 200中的第二设备，因此，第二设备在第一业务阶段中根据第一QoS要求操作业务，如S620中所描述。例如，在第一业务阶段中，SGW204以GBR1的比特率转发用户的数据包，eNB 202以GBR1的比特率调度所述数据包。S291: The first device sends the first QoS policy to the second device in the EPS 200, so the second device operates the service according to the first QoS requirement in the first service phase, as described in S620. For example, in the first service phase, the SGW 204 forwards the user's data packet at the bit rate of GBR1, and the eNB 202 schedules the data packet at the bit rate of GBR1.

S284：第一设备识别针对第二业务阶段的第二QoS要求。在图4B中，执行S2841以实现S284。S284: The first device identifies the second QoS requirement for the second service phase. In FIG. 4B, S2841 is performed to implement S284.

S2841：第一设备根据第一指示信息识别业务阶段，从而进一步识别针对所述业务阶段的第二QoS要求。例如，第一设备根据第一指示信息中的业务阶段标志识别之后的不同业务阶段。作为更特定的实例，第一设备根据时间或数据容量中的至少一者识别第二业务阶段。当时间T1截止和/或达到包容量X1时，PCRF 206识别第二业务阶段。在识别第二业务阶段之后，第一设备根据第一指示信息识别针对第二业务阶段的第二QoS要求。S2841: The first device identifies the service stage according to the first indication information, so as to further identify the second QoS requirement for the service stage. For example, the first device identifies subsequent different service stages according to the service stage flag in the first indication information. As a more specific example, the first device identifies the second traffic phase based on at least one of time or data volume. When the time T1 expires and/or the packet capacity X1 is reached, the PCRF 206 identifies the second traffic phase. After identifying the second service stage, the first device identifies the second QoS requirement for the second service stage according to the first indication information.

S285：第一设备根据针对第二业务阶段的第二QoS要求产生第二QoS策略。第二QoS策略也可以现有QoS策略的形式产生，无需修改。S285: The first device generates a second QoS policy according to the second QoS requirement for the second service phase. The second QoS policy can also be generated in the form of an existing QoS policy without modification.

S292：第一设备2092将第二QoS策略发送到第二设备，因此，第二设备在第二业务阶段中根据第二QoS要求操作业务，如S720中所描述。例如，在第二业务阶段中，SGW 204以GBR2的比特率转发用户的数据包，eNB 202以GBR2的比特率调度所述数据包。S292: The first device 2092 sends the second QoS policy to the second device, so the second device operates the service according to the second QoS requirement in the second service phase, as described in S720. For example, in the second service phase, the SGW 204 forwards the user's data packet at the bit rate of GBR2, and the eNB 202 schedules the data packet at the bit rate of GBR2.

图4C示出了用于控制业务的QoS的方法的又一实例。图4C相对于图4B进行描述。与图3C标记相同的步骤以类似方式执行。Figure 4C shows yet another example of a method for controlling QoS of a traffic. Figure 4C is described with respect to Figure 4B. The same steps as labeled in Figure 3C are performed in a similar manner.

在图4C中，仅通过另外多个步骤来实施S282和S284。执行S2822到S2824和S2842到S2843以实现S282和S284。In FIG. 4C, S282 and S284 are implemented only by additional steps. S2822 to S2824 and S2842 to S2843 are executed to implement S282 and S284.

S2822：第一设备发送请求以激活UE 201，从而识别业务阶段。UE 201如何识别业务阶段的例子已经在S2322中加以描述，此处将不再描述。S2822: The first device sends a request to activate the UE 201, thereby identifying the service phase. An example of how the UE 201 identifies the service phase has been described in S2322 and will not be described here.

S2823：当UE 201识别出第一业务阶段时，第一设备接收UE 201报告的指示业务阶段是第一业务阶段的反馈消息4。S2823: When the UE 201 identifies the first service phase, the first device receives a feedback message 4 reported by the UE 201 indicating that the service phase is the first service phase.

S2824：在接收到UE 201报告的反馈消息4之后，第一设备识别针对第一业务阶段的第一QoS要求。S2824: After receiving the feedback message 4 reported by the UE 201, the first device identifies the first QoS requirement for the first service phase.

S2842：当UE 201识别出第二业务阶段时，第一设备接收UE 201报告的指示业务阶段是第二业务阶段的反馈消息5。S2842: When the UE 201 identifies the second service phase, the first device receives a feedback message 5 reported by the UE 201 indicating that the service phase is the second service phase.

S2843：在接收到UE 201报告的消息5之后，第一设备识别针对第二业务阶段的第二QoS要求。S2843: After receiving the message 5 reported by the UE 201, the first device identifies the second QoS requirement for the second service phase.

图5示出了用于控制业务的QoS的设备502的简化框图。图5相对于图2A进行描述。设备502可为EPS 200中的任何节点，例如，UE 201、eNB 202、MME 203、SGW 204、PGW 205或PCRF 206。Figure 5 shows a simplified block diagram of an apparatus 502 for controlling the QoS of traffic. Figure 5 is described with respect to Figure 2A. Apparatus 502 may be any node in EPS 200 , eg, UE 201 , eNB 202 , MME 203 , SGW 204 , PGW 205 , or PCRF 206 .

如图5中所示，设备502包含第一获取单元506、第二获取单元508和产生单元510。第一获取单元506、第二获取单元508和产生单元510可通过例如设备502的节点中的处理器实施。如本文所使用，术语“处理器”指代一个或多个设备、电路和/或用于处理数据的处理核心，例如计算机程序指令。As shown 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 may be implemented by, for example, a processor in a node of the device 502 . As used herein, the term "processor" refers to one or more devices, circuits, and/or processing cores, such as computer program instructions, for processing data.

第一获取单元506用于获取业务的业务类型。所述业务包含具有至少第一业务阶段和第二业务阶段的GBR业务。第二获取单元508用于根据业务的业务类型获取针对第一业务阶段的第一QoS要求和针对第二业务阶段的第二QoS要求。产生单元510用于产生第一指示信息，其指示针对第一业务阶段的第一QoS要求、针对第二业务阶段的第二QoS要求，以及用于识别第一业务阶段和第二业务阶段的业务阶段标志。例如，业务阶段标志以数据包的时间和所述数据包的包容量中的任一者或任何组合的形式表示。第一指示信息用于产生QoS策略，以便在第一业务阶段中根据QoS策略中指示的第一QoS要求控制QoS，以及在第二业务阶段中根据QoS策略中指示的第二QoS要求控制QoS。The first obtaining unit 506 is configured to obtain the 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 the first QoS requirement for the first service stage and the 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, which indicates the first QoS requirement for the first service stage, the second QoS requirement for the second service stage, and the service for identifying the first service stage and the second service stage Stage sign. For example, the traffic phase flag is represented in the form of either or any combination of the time of the data packet and the packet capacity of the data packet. The first indication information is used to generate a QoS policy to control QoS according to the first QoS requirement indicated in the QoS policy in the first service phase, and to control QoS according to the second QoS requirement indicated in the QoS policy in the second service phase.

在一个例子中，第一指示信息指示针对第一业务阶段的第一QoS要求和针对第二业务阶段的第二QoS要求，所述QoS要求对应于业务的第一等级的用户体验，第一指示信息进一步指示针对第一业务阶段的第三QoS要求和针对第二业务阶段的第四QoS要求，所述QoS要求对应于业务的第二等级的用户体验。In one example, the first indication information indicates a first QoS requirement for the first service stage and a second QoS requirement for the second service stage, where the QoS requirement corresponds to the user experience of the first level of the service, and the first indication The information further indicates a third QoS requirement for the first service phase and a fourth QoS requirement for the second service phase, the QoS requirements corresponding to a second level of user experience of the service.

有利的是，第一设备产生第一指示信息，其指示针对不同业务阶段的不同QoS要求和用于识别不同业务阶段的业务阶段标志。根据第一指示信息，对第一业务阶段和第二业务阶段加以识别，并且产生QoS策略，以在第一业务阶段中根据第一QoS要求控制QoS，以及在第二业务阶段中根据第二QoS要求控制QoS。在接收到QoS策略之后，EPS 200中的每个节点，例如，UE 201、eNB 202、MME 203、SGW 204或PGW 205，根据每个业务阶段中的所要QoS要求操作业务。例如，EPS 200中的每个节点在第一业务阶段中根据第一QoS要求操作业务，在第二业务阶段中根据第二QoS要求操作业务。以eNB 202为更特定的实例，eNB 202在第一业务阶段中以GBR1的比特率调度数据包，在第二业务阶段中以GBR2的比特率调度数据包。因此，满足了针对业务的不同业务阶段的不同QoS要求。例如，视频业务在缓冲阶段以6Mbps的GBR进行调度，并在播放阶段以900Kbps的GBR进行调度。在缓冲阶段，满足相对较高水平的GBR以保证用户体验。在播放阶段，满足相对较低水平的GBR以保持更少的资源，这能增加其它UE的比特率。因此，能高效分配资源同时保证用户体验。Advantageously, the first device generates first indication information indicating different QoS requirements for different service stages and service stage flags for identifying 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 according to the second QoS in the second service stage Requires control of QoS. After receiving the QoS policy, each node in EPS 200, eg, UE 201, eNB 202, MME 203, SGW 204 or PGW 205, operates the traffic according to the desired QoS requirements in each traffic phase. For example, each node in EPS 200 operates a service according to a first QoS requirement in a first service phase and operates a service according to a second QoS requirement in a second service phase. Taking the eNB 202 as a more specific example, the eNB 202 schedules data packets at the bit rate of GBR1 in the first traffic phase and schedules the data packets at the bit rate of GBR2 in the second traffic phase. Therefore, different QoS requirements for different service stages of the service are met. For example, a video service is scheduled with a GBR of 6 Mbps in the buffering stage, and is scheduled with a GBR of 900 Kbps in the playback stage. In the buffering phase, a relatively high level of GBR is met to guarantee user experience. During the playback phase, a relatively low level of GBR is met to keep fewer resources, which can increase the bit rate of other UEs. Therefore, resources can be efficiently allocated while ensuring user experience.

图6A、图6B和图6C示出了用于控制业务的QoS的设备的三个实例。图6A、图6B和图6C相对于图5进行描述。标记相同的元件执行类似功能。Figures 6A, 6B and 6C show three examples of devices for controlling the QoS of traffic. 6A, 6B and 6C are described with respect to FIG. 5 . Elements marked the same perform similar functions.

在图6A和图6B中，用于控制业务的QoS的设备602通过UE 201、eNB 202、MME 203、SGW 204或PGW 205实施。设备602包含第一获取单元506、第二获取单元508、产生单元510、QoS接收单元604和业务操作单元608。In FIGS. 6A and 6B , the apparatus 602 for controlling the QoS of traffic is implemented by the UE 201 , the eNB 202 , the MME 203 , the SGW 204 or the PGW 205 . The device 602 includes a first obtaining unit 506 , a second obtaining unit 508 , a generating unit 510 , a QoS receiving unit 604 and a service operating unit 608 .

QoS接收单元604用于从PCRF 206接收QoS策略。业务操作单元608用于在第一业务阶段中根据QoS策略中指示的第一QoS要求操作业务，以及在第二业务阶段中根据QoS策略中指示的第二QoS要求操作业务。The QoS receiving unit 604 is used to receive the QoS policy from the PCRF 206 . The service operation unit 608 is configured to operate the service according to the first QoS requirement indicated in the QoS policy in the first service phase, and operate the service according to the second QoS requirement indicated in the QoS policy in the second service phase.

在图6A中，产生单元510进一步用于将第一指示信息发送到PCRF206。第一指示信息供PCRF 206用来产生QoS策略。在一个例子中，由PCRF 206产生的QoS策略指示针对第一业务阶段的第一QoS要求、针对第二业务阶段的第二QoS要求，以及用于识别第一业务阶段和第二业务阶段的业务阶段标志。因此，设备602进一步包含第一识别单元610。第一识别单元610用于根据QoS策略中指示的业务阶段标志识别第一业务阶段和第二业务阶段，使得第一设备能够在第一业务阶段中根据QoS策略中指示的第一QoS要求操作业务，以及在第二业务阶段中根据QoS策略中指示的第二QoS要求操作业务。In FIG. 6A , the generating unit 510 is further configured to send the first indication information to the PCRF 206 . The first indication information is used by PCRF 206 to generate a QoS policy. In one example, the QoS policy generated by PCRF 206 indicates a first QoS requirement for a first service phase, a second QoS requirement for a second service phase, and identifies services for the first and second service phases Stage sign. Accordingly, the device 602 further comprises 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 flag indicated in the QoS policy, so that the first device can operate the service according to the first QoS requirement indicated in the QoS policy in the first service stage , and operating the service according to the second QoS requirement indicated in the QoS policy in the second service phase.

在另一例子中，第一指示信息供PCRF 206用来识别业务阶段和产生QoS策略。当PCRF 206根据第一指示信息识别第一业务阶段和针对第一业务阶段的第一QoS要求时，所述PCRF产生第一QoS策略。因此，设备600在第一业务阶段中根据第一QoS策略按照第一QoS要求操作业务。当PCRF 206根据第一指示信息识别第二业务阶段和针对第二业务阶段的第二QoS要求时，所述PCRF产生第二QoS策略。因此，设备600在第二业务阶段中根据第二QoS策略按照第二QoS要求操作业务。In another example, the first indication information is used by PCRF 206 to identify traffic phases and generate QoS policies. When the PCRF 206 identifies the first service phase and the first QoS requirement for the first service phase according to the first indication information, the PCRF generates the first QoS policy. Therefore, the device 600 operates the service according to the first QoS requirement according to the first QoS policy in the first service phase. When PCRF 206 identifies the second service phase and the second QoS requirement for the second service phase according to the first indication information, the PCRF generates a second QoS policy. Therefore, the device 600 operates the service according to the second QoS requirement according to the second QoS policy in the second service phase.

在图6B中，设备614进一步包含第二识别单元616。第二识别单元616用于根据第一指示信息识别针对第一业务阶段的第一QoS要求和针对第二业务阶段的第二QoS要求。因此，产生单元510用于在识别出针对第一业务阶段的第一QoS要求时产生指示针对第一业务阶段的第一QoS要求的第二指示信息，并将第二指示信息发送到PCRF 206以产生第一QoS策略。产生单元510用于在识别出针对第二业务阶段的第二QoS要求时产生指示针对第二业务阶段的第二QoS要求的第三指示信息，并将第三指示信息发送到PCRF 206以产生第二QoS策略。In FIG. 6B , the device 614 further includes a second identification unit 616 . The second identifying 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. Therefore, the generating unit 510 is configured to generate second indication information indicating the first QoS requirement for the first service phase when the first QoS requirement for the first service phase is identified, and send the second indication information to the PCRF 206 for A first QoS policy is generated. The generating unit 510 is configured to generate third indication information indicating the second QoS requirement for the second service phase when the second QoS requirement for the second service phase is identified, and send the third indication information to the PCRF 206 to generate the first QoS requirement. Two QoS policies.

在一个例子中，第二识别单元616用于根据第一指示信息中指示的业务阶段标志识别第一业务阶段，从而识别针对第一业务阶段的第一QoS要求，以及根据第一指示信息中指示的业务阶段标志识别第二业务阶段，从而识别针对第二业务阶段的第二QoS要求。In one example, the second identifying unit 616 is configured to identify the first service stage according to the service stage flag indicated in the first indication information, thereby identifying the first QoS requirement for the first service stage, and according to the indication in the first indication information The service phase flag of the identifies the second service phase and thus the second QoS requirement for the second service phase.

在另一例子中，第二识别单元616用于将请求发送到用户设备(user equipment，UE)，以激活UE从而识别第一业务阶段和第二业务阶段、从UE接收指示识别出第一业务阶段的第一反馈消息，并根据第一反馈消息识别针对第一业务阶段的第一QoS要求。第二识别单元616进一步用于从UE接收指示识别出第二业务阶段的第二反馈消息，并根据第二反馈消息识别针对第二业务阶段的第二QoS要求。In another example, the second identifying unit 616 is configured to send a request to a user equipment (user equipment, UE) to activate the UE to identify the first service phase and the second service phase, and to receive an indication from the UE to identify the first service the first feedback message of the stage, and identify the first QoS requirement for the first service stage according to the first feedback message. The second identifying unit 616 is further configured to receive a second feedback message from the UE indicating that the second service stage is identified, and identify the second QoS requirement for the second service stage according to the second feedback message.

在图6C中，用于控制业务的QoS的设备630通过PCRF 206实施。设备630包含第一获取单元506、第二获取单元508、产生单元510以及QoS产生单元632。QoS产生单元632用于根据第一指示信息产生QoS策略，并将QoS策略发送到第二设备，例如，UE 201、eNB 202、MME203、SGW 204或PGW 205。QoS策略供第二设备用来在第一业务阶段中根据第一QoS要求操作业务，以及在第二业务阶段中根据第二QoS要求操作业务。In FIG. 6C , a device 630 for controlling the QoS of traffic is implemented by PCRF 206 . The device 630 includes a first obtaining unit 506 , a second obtaining unit 508 , a generating unit 510 and a QoS generating unit 632 . The QoS generating unit 632 is configured to generate a QoS policy according to the first indication information, and send the QoS policy to a second device, for example, the UE 201 , the eNB 202 , the MME 203 , the SGW 204 or the PGW 205 . The QoS policy is used by the second device to operate the service according to the first QoS requirement in the first service phase and to operate the service according to the second QoS requirement in the second service phase.

在一个例子中，设备630产生QoS策略，其指示针对第一业务阶段的第一QoS要求、针对第二业务阶段的第二QoS要求，以及用于识别第一业务阶段和第二业务阶段的业务阶段标志。因此，第二设备根据QoS策略中指示的业务阶段标志识别第一业务阶段和第二业务阶段，使得第二设备能够在第一业务阶段中根据QoS策略中指示的第一QoS要求操作业务，以及在第二业务阶段中根据QoS策略中指示的第二QoS要求操作业务。In one example, device 630 generates a QoS policy indicating a first QoS requirement for a first traffic phase, a second QoS requirement for a second traffic phase, and identifying traffic for the first and second traffic phases Stage sign. Therefore, the second device identifies the first service phase and the second service phase according to the service phase flag indicated in the QoS policy, so that the second device can operate the service in the first service phase according to the first QoS requirement indicated in the QoS policy, and The traffic is operated in the second traffic phase according to the second QoS requirement indicated in the QoS policy.

在另一例子中，设备630进一步包含第三识别单元634。第三识别单元634用于根据第一指示信息识别针对第一业务阶段的第一QoS要求和针对第二业务阶段的第二QoS要求。因此，QoS产生单元632用于在识别出针对第一业务阶段的第一QoS要求时根据针对第一业务阶段的第一QoS要求产生第一QoS策略，以及在识别出针对第二业务阶段的第二QoS要求时根据针对第二业务阶段的第二QoS要求产生第二QoS策略。In another example, the device 630 further includes a third identification unit 634 . The third identifying 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. Therefore, the QoS generating unit 632 is configured to generate a first QoS policy according to the first QoS requirement for the first service phase when the first QoS requirement for the first service phase is identified, and to generate the first QoS policy according to the first QoS requirement for the first service phase when identifying the first QoS requirement for the second service phase When there are two QoS requirements, a second QoS policy is generated according to the second QoS requirements for the second service stage.

例如，在一个例子中，第三识别单元634用于根据第一指示信息中指示的业务阶段标志识别第一业务阶段，从而识别针对第一业务阶段的第一QoS要求，以及根据第一指示信息中指示的业务阶段标志识别第二业务阶段，从而识别针对第二业务阶段的第二QoS要求。For example, in one example, the third identification unit 634 is configured to identify the first service stage according to the service stage flag indicated in the first indication information, thereby identifying the first QoS requirement for the first service stage, and according to the first indication information The service phase flag indicated in identifies the second service phase and thus the second QoS requirement for the second service phase.

在另一例子中，第三识别单元634用于将请求发送到用户设备(user equipment，UE)，以激活UE从而识别第一业务阶段和第二业务阶段、从UE接收指示识别出第一业务阶段的第一反馈消息，并根据第一反馈消息识别针对第一业务阶段的第一QoS要求。第三识别单元634进一步用于从UE接收指示识别出第二业务阶段的第二反馈消息，并根据第二反馈消息识别针对第二业务阶段的第二QoS要求。In another example, the third identifying unit 634 is configured to send a request to user equipment (user equipment, UE) to activate the UE to identify the first service phase and the second service phase, and to receive an indication from the UE to identify the first service the first feedback message of the stage, and identify the first QoS requirement for the first service stage according to the first feedback message. The third identifying unit 634 is further configured to receive a second feedback message from the UE indicating that the second service stage is identified, and identify the second QoS requirement for the second service stage according to the second feedback message.

图7A和图7B示出了用于控制业务的QoS的第二设备的两个简化框图。所述业务包含具有至少第一业务阶段和第二业务阶段的GBR业务。在图7A中，第二设备700包含接收单元702、产生单元704和发送单元706。设备700可通过PCRF实施，例如，通过图3A和图3B中的PCRF 206实施。接收单元702、产生单元704和发送单元706可通过PCRF 206中的处理器实施。Figures 7A and 7B show two simplified block diagrams of a second device for controlling the QoS of traffic. The service includes a GBR service having at least a first service stage and a second service stage. In FIG. 7A , the second device 700 includes a receiving unit 702 , a generating unit 704 and a transmitting unit 706 . Apparatus 700 may be implemented by PCRF, eg, by PCRF 206 in Figures 3A and 3B. The receiving unit 702 , the generating unit 704 and the transmitting unit 706 may be implemented by a processor in the PCRF 206 .

接收单元702用于从第一设备接收第一指示信息。第一指示信息指示针对第一业务阶段的第一QoS要求、针对第二业务阶段的第二QoS要求，以及用于识别第一业务阶段和第二业务阶段的业务阶段标志。The receiving unit 702 is configured to receive the first indication information from the first device. The first indication information indicates a first QoS requirement for the first service phase, a second QoS requirement for the second service phase, and a service phase flag for identifying the first service phase and the second service phase.

产生单元704用于根据第一指示信息产生QoS策略。发送单元706用于将QoS策略发送到第三设备。QoS策略供第三设备用来在第一业务阶段中根据第一QoS要求操作业务，以及在第二业务阶段中根据第二QoS要求操作业务。第三设备包含第一设备。The generating unit 704 is configured to generate a QoS policy according to the first indication information. The sending unit 706 is configured to send the QoS policy to the third device. The QoS policy is used by the third device to operate the service according to the first QoS requirement in the first service phase and to operate the service according to the second QoS requirement in the second service phase. The third device includes the first device.

在一个例子中，QoS策略指示针对第一业务阶段的第一QoS要求、针对第二业务阶段的第二QoS要求，以及用于识别第一业务阶段和第二业务阶段的业务阶段标志。QoS策略供第三设备用来根据QoS策略中指示的业务阶段标志识别第一业务阶段和第二业务阶段。In one example, the QoS policy indicates a first QoS requirement for a first service phase, a second QoS requirement for a second service phase, and a service phase flag identifying the first and second service phases. The QoS policy is used by the third device to identify the first service phase and the second service phase according to the service phase flag indicated in the QoS policy.

在另一例子中，任选地，设备700进一步包含识别单元708。识别单元708用于根据第一指示信息识别第一业务阶段和针对第一业务阶段的第一QoS要求。产生单元704用于根据针对第一业务阶段的第一QoS要求产生第一QoS策略，所述第一QoS策略供第三设备用来在第一业务阶段中根据第一QoS要求操作业务。产生单元704进一步用于根据针对第二业务阶段的第二QoS要求产生第二QoS策略，所述第二QoS策略供第三设备用来在第二业务阶段中根据第二QoS要求操作业务。In another example, optionally, apparatus 700 further includes an identification 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, where the first QoS policy is used by 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 phase, where the second QoS policy is used by the third device to operate the service according to the second QoS requirement in the second service phase.

在图7B的实例中，设备710包含接收单元712、识别单元714和操作单元716。设备710可通过EPS 200中的任何节点实施，例如，通过图4A中的第二设备2093实施。接收单元712、识别单元714和操作单元716可通过第二设备2093中的处理器实施。In the example of FIG. 7B , device 710 includes receiving unit 712 , identifying unit 714 , and operating unit 716 . Device 710 may be implemented by any node in EPS 200, eg, by second device 2093 in Figure 4A. The receiving unit 712 , the identifying unit 714 and the operating unit 716 may be implemented by a processor in the second device 2093 .

接收单元712用于从第一设备接收QoS策略。QoS策略指示针对第一业务阶段的第一QoS要求、针对第二业务阶段的第二QoS要求，以及用于识别第一业务阶段和第二业务阶段的业务阶段标志。The receiving unit 712 is configured to receive the QoS policy from the first device. The QoS policy indicates a first QoS requirement for the first service phase, a second QoS requirement for the second service phase, and a service phase flag for identifying the first service phase and the second service phase.

识别单元714用于根据QoS策略中指示的业务阶段标志识别第一业务阶段，以及识别针对第一业务阶段的第一QoS要求。操作单元716用于根据QoS策略在第一业务阶段中按照第一QoS要求操作业务。识别单元714进一步用于根据QoS策略中指示的业务阶段标志识别第二业务阶段，以及识别针对第二业务阶段的第二QoS要求。操作单元716进一步用于根据QoS策略在第二业务阶段中按照第二QoS要求操作业务。The identifying unit 714 is configured to identify the first service stage according to the service stage flag indicated in the QoS policy, and identify the first QoS requirement for the first service stage. The operation 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 configured to identify the second service stage according to the service stage flag indicated in the QoS policy, and identify the second QoS requirement for the second service stage. The operation unit 716 is further configured to operate the service according to the second QoS requirement in the second service phase according to the QoS policy.

本领域普通技术人员能够认识到，结合本说明书所公开的实施例中所描述的实例，可通过电子硬件或计算机软件与电子硬件的组合来实施单元和算法步骤。功能是由硬件还是由软件执行取决于技术方案的特定应用和设计约束条件。本领域技术人员可使用不同方法实现每个特定应用的所描述功能，但是不应认为该实现超出本发明的范围。Those of ordinary skill in the art can recognize that, in conjunction 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 function is performed by hardware or software depends on the specific application and design constraints of the technical solution. Skilled artisans may use different methods to implement the described functionality for each particular application, but such implementations should not be considered beyond the scope of the present invention.

本领域技术人员可清楚地理解，出于方便和简单描述的目的，对于前述系统、设备和单元的详细工作过程，可参考前述方法实施例中的对应过程，本文中不再描述细节。Those skilled in the art can clearly understand that, for the purpose of convenience and simple description, for the detailed working process of the foregoing systems, devices and units, reference may be made to the corresponding processes in the foregoing method embodiments, and details are not described herein.

在本应用中提供的若干实施例中，应理解，所公开的系统、设备和方法可通过其它方式实现。例如，所描述的设备实施例仅仅是示例性的。例如，单元划分仅仅是逻辑功能划分且在实际实现中可以是其它划分。例如，可将多个单元或部件合并或集成到另一系统中，或可忽略或不执行部分特征。另外，可通过一些接口实现所显示或论述的互相耦合或直接耦合或通信连接。设备或单元之间的直接耦合或通信连接可通过电子、机械或其它形式实现。In the several embodiments provided in this application, it should be understood that the disclosed systems, devices, and methods may be implemented in other ways. For example, the device embodiments described are merely exemplary. For example, cell division is only logical function division and may be other divisions in actual implementation. For example, multiple units or components may be combined or integrated into another system, or some features may be omitted or not implemented. Additionally, inter-coupling or direct coupling or communicative connections shown or discussed may be achieved through some interfaces. Direct couplings or communication connections between devices or units may be achieved electronically, mechanically or otherwise.

作为单独部分描述的单元可或可不物理分离，作为单元描述的部分可为或可不为物理单元、可位于一个位置或可在多个网络单元上分布。可根据实际需求选择部分或所有单元以实现实施例中解决方案的目的。Elements described as separate parts may or may not be physically separated, parts described as elements may or may not be physical elements, may be located in one location, or may be distributed over multiple network elements. Some or all of the units can be selected according to actual needs to achieve the purpose of the solutions in the embodiments.

另外，本发明实施例中的功能单元可集成到一个处理单元中，或每个单元可物理上单独存在，或两个或更多单元可集成到一个单元中。In addition, the functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

当这些功能以软件功能单元的形式实现以及作为单独产品销售或使用时它们可存储在计算机可读存储介质中。基于这种理解本发明的技术方案基本上或构成现有技术的部分或技术方案的部分可通过软件产品的形式实现。计算机软件产品存储在存储介质中并包含若干指令，用于指示计算机设备(其可为为个人计算机、业务器、网络设备等)执行本发明实施例中所描述的方法的所有或部分步骤。上述存储介质包含：可存储程序代码的任何介质，例如USB盘、可移动硬盘、只读存储器(ROM，Read-Only Memory)、随机存取存储器(RAM，Random Access Memory)、磁盘或光学光盘。When these functions are implemented in the form of software functional units and sold or used as separate products, they may be stored in a computer-readable storage medium. Based on this understanding, the technical solutions of the present invention basically or constitute parts of the prior art or parts of the technical solutions can be implemented in the form of software products. The computer software product is stored in a storage medium and contains several instructions for instructing a computer device (which may be a personal computer, a business server, a network device, etc.) to execute all or part of the steps of the methods described in the embodiments of the present invention. The above storage medium includes: any medium that can store program codes, such as a USB disk, 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 disk.

上述描述仅是本发明的具体实施方式但并非旨在限制本发明的保护范围。本领域技术人员在本发明所公开的技术范围中容易发现的任意变体或替代应落入本发明的保护范围内。因此，本发明的保护范围应以权利要求的保护范围为准。The above descriptions are only specific embodiments of the present invention and are not intended to limit the protection scope of the present invention. Any variations or substitutions easily found by those skilled in the art in the technical scope disclosed in the present invention should fall within the protection scope of the present invention. Therefore, the protection scope of the present invention should be subject to the protection scope of the claims.

Claims (40)

1. A method for controlling quality of service (QoS) of a service, comprising:
the method comprises the steps that first equipment obtains a service type of the service, wherein the service comprises Guaranteed Bit Rate (GBR) service with at least a first service stage and a second service stage;
the first equipment acquires a first QoS requirement aiming at the first service phase and a second QoS requirement aiming at the second service phase according to the service type of the service; and
the first device generates first indication information, wherein the first indication information indicates the first QoS requirements for the first traffic phase, the second QoS requirements for the second traffic phase, and a traffic phase flag identifying the first traffic phase and the second traffic phase, wherein the first indication information is used to generate QoS policies to control QoS in the first traffic phase according to the first QoS requirements indicated in the QoS policies and to control QoS in the second traffic phase according to the second QoS requirements indicated in the QoS policies.
2. The method of claim 1, wherein the service phase flag is represented in any one or any combination of the following forms: the time of the data packet and the packet's capacity.
3. The method of claim 1, wherein the first indication information indicates the first QoS requirement for the first traffic phase and the second QoS requirement for the second traffic phase, wherein the first QoS requirement and the second QoS requirement correspond to a first level of user experience for the traffic, and wherein the first indication information further indicates a third QoS requirement for the first traffic phase and a fourth QoS requirement for the second traffic phase, wherein the third QoS requirement and the fourth QoS requirement correspond to a second level of user experience for the traffic.
4. The method of claim 2, wherein the first indication information indicates the first QoS requirement for the first traffic phase and the second QoS requirement for the second traffic phase, the first QoS requirement and the second QoS requirement corresponding to a first level of user experience for the traffic, and wherein the first indication information further indicates a third QoS requirement for the first traffic phase and a fourth QoS requirement for the second traffic phase, the third QoS requirement and the fourth QoS requirement corresponding to a second level of user experience for the traffic.
5. The method according to any one of claims 1 to 4, characterized in that the method further comprises:
the first device receiving the QoS policy from a Policy and Charging Rules Function (PCRF);
the first device operating the traffic in the first traffic phase according to the first QoS requirement indicated in the QoS policy; and
the first device operates the traffic in the second traffic phase according to the second QoS requirements indicated in the QoS policy.
6. The method of claim 5, further comprising:
the first device sending the first indication information to the PCRF, wherein the first indication information is used by the PCRF to generate the QoS policy;
the first device identifies the first service phase and the second service phase according to the service phase flag indicated in the QoS policy.
7. The method of claim 5, further comprising:
the first device identifies the first QoS requirement for the first traffic phase according to the first indication information;
generating, by the first device, second indication information indicating the first QoS requirement for the first traffic phase, wherein the second indication information is sent to the PCRF and used by the PCRF to generate a first QoS policy indicating the first QoS requirement for the first traffic phase;
the first device identifies the second QoS requirement for the second traffic phase according to the first indication information;
the first device generates third indication information indicating the second QoS requirements for the second traffic phase, wherein the third indication information is sent to the PCRF and used by the PCRF to generate a second QoS policy indicating the second QoS requirements for the second traffic phase.
8. The method of claim 7, wherein identifying the first QoS requirement for the first traffic phase comprises:
the first device sending a request to activate a User Equipment (UE) to identify the first traffic phase and the second traffic phase;
the first equipment receives a first feedback message reported by the UE, wherein the first feedback message indicates that the first service phase is identified;
the first device identifying the first QoS requirement for the first traffic phase from the first feedback message;
wherein identifying the second QoS requirement for the second traffic phase comprises:
the first equipment receives a second feedback message reported by the UE, wherein the second feedback message indicates that the second service phase is identified;
the first device identifies the second QoS requirement for the second traffic phase from the second feedback message.
9. A method for controlling quality of service of a service, the method having any one of claims 1 to 7, wherein the first device includes a User Equipment (UE), an evolved NodeB (eNodeB), a Mobility Management Entity (MME), a Serving Gateway (SGW), or a packet data network gateway (PGW).
10. A method for controlling quality of service of a service, characterized in that the method has the method of any of claims 1 to 4, and that the first device comprises a Policy and Charging Rules Function (PCRF);
wherein the method further comprises:
the first device generates the QoS policy according to the first indication information; and
the first device sends the QoS policy to a second device, wherein the QoS policy is for use by the second device to operate the traffic according to the first QoS requirements in the first traffic phase and to operate the traffic according to the second QoS requirements in the second traffic phase.
11. The method of claim 10, wherein the generated QoS policy indicates the first QoS requirement for the first traffic phase, the second QoS requirement for the second traffic phase, and the traffic phase flag identifying the first traffic phase and the second traffic phase, wherein the QoS policy is used by the second device to identify the first traffic phase and the second traffic phase.
12. The method of claim 10, wherein generating the QoS policy according to the first indication information comprises:
the first device identifies the first QoS requirement for the first traffic phase according to the first indication information;
the first device generating a first QoS policy according to the first QoS requirement;
the first device identifies the second QoS requirement for the second traffic phase according to the first indication information; and
the first device generates a second QoS policy according to the second QoS requirement.
13. The method of claim 12, wherein identifying the first QoS requirement for the first traffic phase comprises:
the first device sending a request to activate a User Equipment (UE) to identify the first traffic phase and the second traffic phase;
the first equipment receives a first feedback message reported by the UE, wherein the first feedback message indicates that the first service phase is identified;
the first device identifying the first QoS requirement for the first traffic phase from the first feedback message;
wherein identifying the second QoS requirement for the second traffic phase comprises:
the first equipment receives a second feedback message reported by the UE, wherein the second feedback message indicates that the second service phase is identified;
the first device identifies the second QoS requirement for the second traffic phase from the second feedback message.
14. A method for controlling quality of service of a service, characterized in that the method has the method of any of claims 1 to 13, and obtaining the service type of the service comprises:
the first device receives a message from a third device indicating the traffic type of the traffic.
15. A first apparatus for controlling quality of service (QoS) of a service, comprising:
a first obtaining unit, configured to obtain a service type of the service, where the service is a Guaranteed Bit Rate (GBR) service having at least a first service phase and a second service phase;
a second obtaining unit, configured to obtain, according to the service type of the service, a first QoS requirement for the first service phase and a second QoS requirement for the second service phase; and
a generating unit configured to generate first indication information indicating the first QoS requirement for the first traffic phase, the second QoS requirement for the second traffic phase, and a traffic phase flag identifying the first traffic phase and the second traffic phase, wherein the first indication information is used to generate a QoS policy to control QoS in the first traffic phase according to the first QoS requirement indicated in the QoS policy, and to control QoS in the second traffic phase according to the second QoS requirement indicated in the QoS policy.
16. The first device of claim 15, wherein the traffic phase flag is represented in any one or any combination of the following: the time of the data packet and the packet's capacity.
17. The first device of claim 15, wherein the first indication information indicates the first QoS requirements for the first traffic phase and the second QoS requirements for the second traffic phase, wherein the first QoS requirements and the second QoS requirements correspond to a first level of user experience for the traffic, and wherein the first indication information further indicates a third QoS requirements for the first traffic phase and a fourth QoS requirements for the second traffic phase, wherein the third QoS requirements and the fourth QoS requirements correspond to a second level of user experience for the traffic.
18. The first device of claim 16, wherein the first indication information indicates the first QoS requirements for the first traffic phase and the second QoS requirements for the second traffic phase, wherein the first QoS requirements and the second QoS requirements correspond to a first level of user experience for the traffic, and wherein the first indication information further indicates a third QoS requirements for the first traffic phase and a fourth QoS requirements for the second traffic phase, wherein the third QoS requirements and the fourth QoS requirements correspond to a second level of user experience for the traffic.
19. The first apparatus of any of claims 15-18, further comprising:
a QoS receiving unit for receiving the QoS policy from a Policy and Charging Rules Function (PCRF); and
a service operation unit, configured to operate the service according to the first QoS requirement indicated in the QoS policy in the first service phase, and operate the service according to the second QoS requirement indicated in the QoS policy in the second service phase.
20. The first apparatus of claim 19, wherein the generating unit is configured to send the first indication information to the PCRF, wherein the first indication information is used by the PCRF to generate the QoS policy;
wherein the apparatus further comprises:
a first identification unit, configured to identify the first service phase and the second service phase according to the service phase flag indicated in the QoS policy.
21. The first device of claim 19, further comprising:
a second identification unit, configured to identify the first QoS requirement for the first traffic phase and the second QoS requirement for the second traffic phase according to the first indication information;
wherein the generating unit is to generate second indication information indicating the first QoS requirement for the first traffic phase when the first QoS requirement for the first traffic phase has been identified and to send the second indication information to the PCRF to generate a first QoS policy, and wherein the generating unit is to generate third indication information indicating the second QoS requirement for the second traffic phase when the second QoS requirement for the second traffic phase has been identified and to send the third indication information to the PCRF to generate a second QoS policy.
22. The first apparatus of claim 21, wherein the second identifying unit is configured to send a request to a User Equipment (UE) to activate the UE to identify the first traffic phase and the second traffic phase, to receive a first feedback message from the UE indicating that the first traffic phase is identified, and to identify the first QoS requirement for the first traffic phase based on the first feedback message;
wherein the second identifying unit is further configured to receive a second feedback message from the UE indicating that the second traffic phase is identified, and identify the second QoS requirement for the second traffic phase according to the second feedback message.
23. A first device, characterized in that the first device has all the features of the first device of any one of claims 15 to 21, and in that 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).
24. A first device, characterized in that it has all the features of the first device of any of claims 15 to 18, and in that it 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 send the QoS policy to a second device, wherein the QoS policy is used by the second device to operate the service according to the first QoS requirement in the first service phase and operate the service according to the second QoS requirement in the second service phase.
25. The first device of claim 24, wherein the QoS policy indicates the first QoS requirement for the first traffic phase, the second QoS requirement for the second traffic phase, and the traffic phase flag for use by the second device to identify the first traffic phase and the second traffic phase.
26. The first device of claim 24, further comprising:
a third identifying unit, configured to identify the first QoS requirement for the first traffic phase and the second QoS requirement for the second traffic phase according to the first indication information;
wherein the QoS policies comprise a first QoS policy and a second QoS policy, the QoS generation unit to generate the first QoS policy according to the first QoS requirement for the first traffic phase when the first QoS requirement for the first traffic phase has been identified, and to generate the second QoS policy according to the second QoS requirement for the second traffic phase when the second QoS requirement for the second traffic phase has been identified.
27. The first apparatus of claim 26, wherein the third identifying unit is configured to send a request to a User Equipment (UE) to activate the UE to identify the first traffic phase and the second traffic phase, receive a first feedback message from the UE indicating that the first traffic phase is identified, and identify the first QoS requirement for the first traffic phase according to the first feedback message;
wherein the second identifying unit is configured to receive a second feedback message from the UE indicating that the second traffic phase is identified, and identify the second QoS requirement for the second traffic phase according to the second feedback message.
28. A first device, characterized in that it has all the features of the first device of any of claims 15 to 27, and in that said first acquisition unit is configured to receive a message from a third device indicating said service type of said service.
29. A method for controlling quality of service (QoS) for a service, the service comprising a Guaranteed Bit Rate (GBR) service having at least a first service phase and a second service phase, 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 traffic phase, a second QoS requirement for the second traffic phase, and a traffic phase flag identifying the first traffic phase and the second traffic phase;
the second equipment generates a QoS strategy according to the first indication information; and
the second device sends the QoS policy to a third device, the QoS policy for use by the third device to operate the traffic according to the first QoS requirements in the first traffic phase and to operate the traffic according to the second QoS requirements in the second traffic phase.
30. The method of claim 29, wherein the QoS policy indicates the first QoS requirement for the first traffic phase, the second QoS requirement for the second traffic phase, and the traffic phase flag identifying the first traffic phase and the second traffic phase, wherein the QoS policy is used by the third device to identify the first traffic phase and the second traffic phase according to the traffic phase flag indicated in the QoS policy.
31. The method of claim 29, wherein the generating a QoS policy according to the first indication information comprises:
the second device identifies the first traffic phase and the first QoS requirement for the first traffic phase according to the first indication information;
the second device generating a first QoS policy in accordance with the first QoS requirement for the first traffic phase, wherein the first QoS policy is for use by the third device to operate the traffic in accordance with the first QoS requirement in the first traffic phase;
the second device identifies the second traffic phase and the second QoS requirement for the second traffic phase according to the first indication information;
the second device generates a second QoS policy based on the second QoS requirements for the second traffic phase, wherein the second QoS policy is used by the third device to operate the traffic in the second traffic phase according to the second QoS requirements.
32. The method of any one of claims 29 to 31, wherein the third device comprises the first device.
33. A second apparatus for controlling quality of service (QoS) for a service, the service comprising a Guaranteed Bit Rate (GBR) service having at least a first service phase and a second service phase, the apparatus 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 traffic phase, a second QoS requirement for the second traffic phase, and a traffic phase flag identifying the first traffic phase and the second traffic phase;
a generating unit, configured to generate a QoS policy according to the first indication information; and
a sending unit, configured to send the QoS policy to a third device, where the QoS policy is used by the third device to operate the service according to the first QoS requirement in the first service phase, and operate the service according to the second QoS requirement in the second service phase.
34. The second device of claim 33, wherein the QoS policy indicates the first QoS requirement for the first traffic phase, the second QoS requirement for the second traffic phase, and the traffic phase flag identifying the first traffic phase and the second traffic phase, wherein the QoS policy is used by the third device to identify the first traffic phase and the second traffic phase according to the traffic phase flag indicated in the QoS policy.
35. The second device of claim 33, further comprising:
an identifying unit, configured to identify the first traffic phase and the first QoS requirement for the first traffic phase according to the first indication information; wherein the generating unit is to generate a first QoS policy according to the first QoS requirement for the first traffic phase, the first QoS policy for use by the third device to operate the traffic according to the first QoS requirement in the first traffic phase; and wherein the generating unit is to generate a second QoS policy according to the second QoS requirement for the second traffic phase, the second QoS policy for use by the third device to operate the traffic according to the second QoS requirement in the second traffic phase.
36. A method for controlling quality of service (QoS) for a service, the service comprising a Guaranteed Bit Rate (GBR) service having at least a first service phase and a second service phase, the method comprising:
receiving, by a second device, a QoS policy from a first device, wherein the QoS policy indicates a first QoS requirement for the first traffic phase, a second QoS requirement for the second traffic phase, and the traffic phase flag identifying the first traffic phase and the second traffic phase;
the second device identifies the first traffic phase according to the traffic phase flag indicated in the QoS policy and identifies a first QoS requirement for the first traffic phase;
the second device operates the service according to the first QoS requirement in the first service stage according to the QoS strategy;
the second device identifying the second service phase according to the service phase flag indicated in the QoS policy and identifying a second QoS requirement for the second service phase;
and the second equipment operates the service according to the second QoS requirement in the second service stage according to the QoS strategy.
37. A second apparatus for controlling quality of service (QoS) for a service, the service comprising a Guaranteed Bit Rate (GBR) service having at least a first service phase and a second service phase, the apparatus comprising:
a receiving unit to receive a QoS policy from a first device, wherein the QoS policy indicates a first QoS requirement for the first traffic phase, a second QoS requirement for the second traffic phase, and the traffic phase flag to identify the first traffic phase and the second traffic phase;
an identifying unit, configured to identify the first service phase according to the service phase flag indicated in the QoS policy, and identify a first QoS requirement for the first service phase;
an operation unit, configured to operate the service according to the first QoS requirement in the first service phase according to the QoS policy;
wherein the identifying unit is further configured to identify the second traffic phase based on the traffic phase flag indicated in the QoS policy, and to identify a second QoS requirement for the second traffic phase, wherein the operating unit is further configured to operate the traffic in the second traffic phase according to the second QoS requirement based on the QoS policy.
38. A computer-readable storage medium, characterized in that it stores a computer program, which is executable by hardware to implement the method of any one of claims 1 to 14.
39. A computer-readable storage medium, characterized in that it stores a computer program, which, when executed by hardware, is capable of implementing the method of any one of claims 29 to 32.
40. A computer-readable storage medium, characterized in that the computer-readable storage medium stores a computer program, which is executable by hardware to implement the method of claim 36.
CN201480079810.9A 2014-06-16 2014-06-16 Method and apparatus for controlling QOS of service Active CN106465194B (en)

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2014/079953 WO2015192295A1 (en) 2014-06-16 2014-06-16 Method and device for controlling qos of a service

Publications (2)

Publication Number Publication Date
CN106465194A CN106465194A (en) 2017-02-22
CN106465194B true CN106465194B (en) 2020-01-21

Family

ID=54934654

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201480079810.9A Active CN106465194B (en) 2014-06-16 2014-06-16 Method and apparatus for controlling QOS of service

Country Status (2)

Country Link
CN (1) CN106465194B (en)
WO (1) WO2015192295A1 (en)

Families Citing this family (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107734562B (en) * 2016-08-11 2020-04-03 华为技术有限公司 A service transmission control method, related equipment and communication system
CN110476459B (en) * 2017-03-24 2022-12-06 瑞典爱立信有限公司 QoS flow inactivity counter
EP3652984B1 (en) * 2017-07-14 2023-03-01 Telefonaktiebolaget LM Ericsson (publ) Method and apparatus for link adaptation in a mixed traffic environment
CN113329244B (en) * 2017-09-30 2022-07-22 华为技术有限公司 Service transmission method and device
CN109982391B (en) 2017-12-28 2023-04-11 华为技术有限公司 Data processing method and device
CN112333828B (en) * 2020-11-18 2023-11-24 中国联合网络通信集团有限公司 Communication method, device and system
CN115474232B (en) * 2021-06-10 2025-03-25 维沃移动通信有限公司 QoS control method and device
CN115707038A (en) * 2021-08-17 2023-02-17 中兴通讯股份有限公司 Service processing method, base station and computer readable storage medium

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2007068266A1 (en) * 2005-12-12 2007-06-21 Telefonaktiebolaget Lm Ericsson (Publ) Method and devices for specifying the quality of service in a transmission of data packets
EP2104275A1 (en) * 2008-03-21 2009-09-23 Research In Motion Limited Dynamic aggregated maximum bit rate for evolved packet system non-guaranteed bit rate quality of service enforcement and network bandwidth utilization
CN102883377A (en) * 2011-07-12 2013-01-16 中兴通讯股份有限公司 Service quality processing method and device
WO2014036338A2 (en) * 2012-08-31 2014-03-06 Qualcomm Incorporated Selective network parameter configuratons based on network identification of non-ims multimedia applications

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101128040A (en) * 2006-08-18 2008-02-20 华为技术有限公司 Wireless communication network and service control method thereof
US8542642B2 (en) * 2008-06-26 2013-09-24 Freescale Semiconductor, Inc. Channel condition dependent scheduling
US8285298B2 (en) * 2009-12-23 2012-10-09 At&T Mobility Ii Llc Chromatic scheduler for network traffic with disparate service requirements
CN102238743A (en) * 2010-05-05 2011-11-09 联芯科技有限公司 Multiplex bearer management method and device
CN102625377B (en) * 2011-01-31 2014-06-18 电信科学技术研究院 Method for establishing radio bearer, access point equipment, user equipment and system

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2007068266A1 (en) * 2005-12-12 2007-06-21 Telefonaktiebolaget Lm Ericsson (Publ) Method and devices for specifying the quality of service in a transmission of data packets
EP2104275A1 (en) * 2008-03-21 2009-09-23 Research In Motion Limited Dynamic aggregated maximum bit rate for evolved packet system non-guaranteed bit rate quality of service enforcement and network bandwidth utilization
CN102883377A (en) * 2011-07-12 2013-01-16 中兴通讯股份有限公司 Service quality processing method and device
WO2014036338A2 (en) * 2012-08-31 2014-03-06 Qualcomm Incorporated Selective network parameter configuratons based on network identification of non-ims multimedia applications

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
3GPP Organizational Partners.3GPP TS 23.203 V12.2.0-Technical Specification Group Services and System Aspects *
Policy and charging control architecture.《3GPP Technical Specification》.2013, *

Also Published As

Publication number Publication date
WO2015192295A1 (en) 2015-12-23
CN106465194A (en) 2017-02-22

Similar Documents

Publication Publication Date Title
CN106465194B (en) Method and apparatus for controlling QOS of service
CN110049517B (en) QoS flow control method and device
WO2019228214A1 (en) Method and apparatus for establishing radio bearer and monitoring service flow
CN106255148B (en) Promoting QoS differentiation in bearer in multi-connectivity 5G network
US9936534B2 (en) Method and apparatus for data transmission
WO2020200066A1 (en) Data packet latency parameter acquisition method, system and apparatus
CN103248451B (en) Service rate control method and system and equipment
JP6408697B2 (en) Bearer setup apparatus and method
CN109845389B (en) A communication method and device
WO2012089056A1 (en) Method, device and system for processing messages
US11044629B2 (en) Wireless communication method, user equipment, access network device, and core network device
WO2017177753A1 (en) Flow-based bearer management method, and data transmission method and device
CN111213403B (en) Method and device for scheduling QoS (quality of service) flow in wireless communication system
CN110138685B (en) A communication method and device
CN110099407A (en) A kind of service quality QoS control method and relevant device
EP4040845B1 (en) Communication method, apparatus and system
CN108141866A (en) A kind of method and device of processing business data packet
CN107809750B (en) A VoLTE service processing method and device
CN104054363B (en) A kind of method and apparatus of data stream transmitting
Guo et al. Quality of service control
WO2016150115A1 (en) Bearer establishment method, packet data gateway, serving gateway and system
US10212722B2 (en) Volume-deadline scheduling
EP3395017B1 (en) Improvements in network transmission of usb traffic

Legal Events

Date Code Title Description
C06 Publication
PB01 Publication
C10 Entry into substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant