Scheduling method and apparatus for a quality of service data flow

1. A scheduling method, wherein the method comprises:

determining, by an application processor, a type of a to-be-sent data packet based on a quality of service (QoS) data flow identifier (QFI), wherein the determining the type of a to-be-sent data packet comprises:

matching, by the application processor, the to-be-sent data packet with a plurality of QoS rules, wherein each of the plurality of QoS rules comprises a respective QFI; and

determining the type of a to-be-sent data packet, by the application processor based on a QFI in a first QoS rule that successfully matches the to-be-sent data packet and a mapping relationship between the QFI and the type of the to-be-sent data packet;

putting, by the application processor, the to-be-sent data packet into a quality of service (QoS) data flow corresponding to the type of the to-be-sent data packet, wherein the type of the to-be-sent data packet is a guaranteed bit rate (GBR) type or a non-guaranteed bit rate (non-GBR) type;

scheduling, by the application processor, a to-be-sent data packet in a QoS data flow corresponding to the GBR type to send the to-be-sent data packet to a modem in a terminal in which the application processor is located, wherein the application processor is located outside of the modem; and

after determining that a data transmission rate requirement of the GBR type is met, scheduling, by the application processor, a to-be-sent data packet in a QoS data flow corresponding to the non-GBR type to send the to-be-sent data packet to the modem.

2. The method according to claim 1 , wherein the method further comprises:

marking, by the application processor, the to-be-sent data packet by using the QFI in the first QoS rule.

3. The method according to claim 2 , wherein

a header field is followed by a packet header of the to-be-sent data packet, and content of the header field is the QFI in the first QoS rule, or

a first field is comprised in a descriptor of the to-be-sent data packet, and content of the first field is the QFI in the first QoS rule.

4. The method according to claim 1 , wherein the putting, by the application processor, the to-be-sent data packet into a QoS data flow corresponding to the type of the to-be-sent data packet comprises:

putting, by the application processor, the to-be-sent data packet into a QoS data flow corresponding to the QFI in the first QoS rule.

5. The method according to claim 4 , wherein a rate at which the application processor schedules the to-be-sent data packet in a first QoS data flow is greater than or equal to a first guaranteed flow bit rate (GFBR), the first GFBR is a GFBR in a QoS rule that successfully matches the to-be-sent data packet in the first QoS data flow, and the first QoS data flow is a QoS data flow corresponding to the GBR type.

6. The method according to claim 4 , wherein a rate at which the application processor schedules the to-be-sent data packet in a second QoS data flow is less than or equal to an aggregate maximum bit rate (AMBR) in a QoS parameter, and the second QoS data flow is a QoS data flow corresponding to the non-GBR type.

7. The method according to claim 1 , wherein the scheduling, by the application processor, a to-be-sent data packet in a QoS data flow corresponding to the GBR type comprises: scheduling, by the application processor based on priorities of a plurality of QoS data flows corresponding to the GBR type, to-be-sent data packets in the plurality of QoS data flows corresponding to the GBR type; and

the scheduling, by the application processor, a to-be-sent data packet in a QoS data flow corresponding to the non-GBR type comprises: scheduling, by the application processor based on priorities of a plurality of QoS data flows corresponding to the non-GBR type, to-be-sent data packets in the plurality of QoS data flows corresponding to the non-GBR type.

8. An application processor, wherein the application processor comprises:

a processor, configured to:

determine a type of a to-be-sent data packet based on a quality of service (QoS) data flow identifier (QFI)), wherein the processor is configured to:

match the to-be-sent data packet with a plurality of QoS rules, wherein each of the plurality of QoS rules comprises a respective QFI; and

determine the type of a to-be-sent data packet, based on a QFI in a first QoS rule that successfully matches the to-be-sent data packet and a mapping relationship between the QFI and the type of the to-be-sent data packet;

put the to-be-sent data packet into a quality of service (QoS) data flow corresponding to the type of the to-be-sent data packet, wherein the type of the to-be-sent data packet is a guaranteed bit rate (GBR) type or a non-guaranteed bit rate (non-GBR) type;

schedule a to-be-sent data packet in a QoS data flow corresponding to the GBR type to send the to-be-sent data packet to a modem in a terminal in which the application processor is located, wherein the application processor is located outside of the modem; and

after determining that a data transmission rate requirement of the GBR type is met, schedule a to-be-sent data packet in a QoS data flow corresponding to the non-GBR type to send the to-be-sent data packet to the modem.

9. The application processor according to claim 8 , wherein the processor is further configured to:

mark the to-be-sent data packet by using the QFI in the first QoS rule.

10. The application processor according to claim 9 , wherein a header field is followed by a packet header of the to-be-sent data packet, and content of the header field is the QFI in the first QoS rule, or

a first field is comprised in a descriptor of the to-be-sent data packet, and content of the first field is the QFI in the first QoS rule.

11. The application processor according to claim 8 , wherein the processor is configured to:

put the to-be-sent data packet into a QoS data flow corresponding to the QFI in the first QoS rule.

12. The application processor according to claim 11 , wherein a rate at which the processor schedules the to-be-sent data packet in a first QoS data flow is greater than or equal to a first GFBR, the first GFBR is a GFBR in a QoS rule that successfully matches the to-be-sent data packet in the first QoS data flow, and the first QoS data flow is a QoS data flow corresponding to the GBR type.

13. The application processor according to claim 11 , wherein a rate at which the processor schedules the to-be-sent data packet in a second QoS data flow is less than or equal to an AMBR in a QoS parameter, and the second QoS data flow is a QoS data flow corresponding to the non-GBR type.

14. The application processor according to claim 8 , wherein the processor is configured to:

schedule, based on priorities of a plurality of QoS data flows corresponding to the GBR type, to-be-sent data packets in the plurality of QoS data flows corresponding to the GBR type; and

schedule, based on priorities of a plurality of QoS data flows corresponding to the non-GBR type, to-be-sent data packets in the plurality of QoS data flows corresponding to the non-GBR type.

15. A terminal, comprising:

a modem, and an application processor, wherein application processor configured to:

determine a type of a to-be-sent data packet based on a quality of service (QoS) data flow identifier (QFI), wherein the application processor is configured to:

match the to-be-sent data packet with a plurality of QoS rules, wherein each of the plurality of QoS rules comprises a respective QFI; and

determine the type of a to-be-sent data packet, based on a QFI in a first QoS rule that successfully matches the to-be-sent data packet and a mapping relationship between the QFI and, the type of the to-be-sent data packet;

put the to-be-sent data packet into a quality of service (QoS) data flow corresponding to the type of the to-be-sent data packet, wherein the type of the to-be-sent data packet is a guaranteed bit rate (GBR) type or a non-guaranteed bit rate (non-GBR) type;

schedule a to-be-sent data packet in a QoS data flow corresponding to the GBR type to send the to-be-sent data packet to the modem, wherein the application processor is located outside of the modem; and

after determining that a data transmission rate requirement of the GBR type is met, schedule a to-be-sent data packet in a QoS data flow corresponding to the non-GBR type to send the to-be-sent data packet to the modem.

16. The terminal according to claim 15 , wherein the application processor is further configured to:

mark the to-be-sent data packet by using the QFI in the first QoS rule.

17. The terminal according to claim 16 , wherein a header field is followed by a packet header of the to-be-sent data packet, and content of the header field is the QFI in the first QoS rule, or

a first field is comprised in a descriptor of the to-be-sent data packet, and content of the first field is the QFI in the first QoS rule.

18. The terminal according to claim 15 , wherein the application processor is configured to put the to-be-sent data packet into a QoS data flow corresponding to the QFI in the first QoS rule.

19. The terminal according to claim 18 , wherein a rate at which the application processor schedules the to-be-sent data packet in a first QoS data flow is greater than or equal to a first guaranteed flow bit rate (GFBR), the first GFBR is a GFBR in a QoS rule that successfully matches the to-be-sent data packet in the first QoS data flow, and the first QoS data flow is a QoS data flow corresponding to the GBR type.

20. The terminal according to claim 18 , wherein a rate at which the application processor schedules the to-be-sent data packet in a second QoS data flow is less than or equal to an aggregate maximum bit rate (AMBR) in a QoS parameter, and the second QoS data flow is a QoS data flow corresponding to the non-GBR type.