Application buffering of packets by fog computing node for deterministic network transport
US-2019149629-A1 · May 16, 2019 · US
US11546269B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-11546269-B2 |
| Application number | US-202016911455-A |
| Country | US |
| Kind code | B2 |
| Filing date | Jun 25, 2020 |
| Priority date | Dec 27, 2017 |
| Publication date | Jan 3, 2023 |
| Grant date | Jan 3, 2023 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
This application provides a scheduling method and an apparatus. The method includes: determining, by an application processor, a type of a to-be-sent data packet, and 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, where the type of the to-be-sent data packet is a GBR type or a non-GBR type; and 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, 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.
Opening claim text (preview).
What is claimed is: 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
Quantum based scheduling, e.g. credit or deficit based scheduling or token bank · CPC title
Traffic characterised by specific attributes, e.g. priority or QoS · CPC title
using specific QoS parameters for wireless networks, e.g. QoS class identifier [QCI] or guaranteed bit rate [GBR] (negotiating SLA or negotiating QoS H04W28/24) · CPC title
Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP] · CPC title
the individual bearer or channel having a maximum bit rate or a bit rate guarantee · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.