Mechanisms for differentiated treatment of offloaded traffic
US-2017034756-A1 · Feb 2, 2017 · US
US11889343B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-11889343-B2 |
| Application number | US-202217731804-A |
| Country | US |
| Kind code | B2 |
| Filing date | Apr 28, 2022 |
| Priority date | Oct 28, 2015 |
| Publication date | Jan 30, 2024 |
| Grant date | Jan 30, 2024 |
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.
A bearer processing method and system, and a related apparatus. A GW-U is configured to receive a data packet and match the data packet with a rule, and send bearer processing indication information to a GW-C if a rule matching result of the data packet meets a trigger condition for bearer processing, where the bearer processing indication information is used to trigger the GW-C to perform bearer processing according to quality of service QoS information of a data service corresponding to the data packet. The GW-C is configured to receive the bearer processing indication information from the GW-U, determine, according to the bearer processing indication information, the QoS information of the data service corresponding to the data packet, and perform bearer processing according to the QoS information of the data service corresponding to the data packet.
Opening claim text (preview).
What is claimed is: 1. A bearer processing method, comprising: receiving, by a gateway user plane device, a data packet of a service; determining, by the gateway user plane device, a rule that matches the data packet, wherein the rule is associated with quality of service (QoS) information required for the service; determining, by the gateway user plane device, whether the QoS information required for the service is consistent with QoS information of a first bearer that exists for transmitting the data packet of the service; and triggering, by the gateway user plane device, in response to the QoS information required for the service being inconsistent with the QoS information of the first bearer, a gateway control plane device to create a dedicated bearer that satisfies the QoS requirement for the service; and creating, by the gateway control plane device, the dedicated bearer that satisfies the QoS requirement for the service, wherein the gateway user plane device and the gateway control plane device are two separate devices in a core network. 2. The method according to claim 1 , wherein the rule being associated with the QoS information required for the service comprises the rule being associated with a relationship between the service and the QoS information required for the service. 3. The method according to claim 1 , wherein the rule is locally configured by the gateway user plane device. 4. The method according to claim 1 , wherein the determining whether the QoS information required for the service is consistent with the QoS information of the first bearer comprises: determining, by the gateway user plane device, whether allocation/retention priority (ARP) information required for the service is consistent with ARP information of the first bearer. 5. The method according to claim 1 , wherein the determining whether the QoS information required for the service is consistent with the QoS information of the first bearer comprises: determining, by the gateway user plane device, whether a QoS class identifier (QCI) required for the service is consistent with a QCI of the first bearer. 6. The method according to claim 1 , wherein the triggering the gateway control plane device to create the dedicated bearer comprises: sending, by the gateway user plane device, the QoS information required for the service to the gateway control plane device. 7. The method according to claim 1 , further comprising: interacting, by the gateway user plane device, with the gateway control plane device to delete the dedicated bearer in response to the gateway user plane device determining that the service has ended. 8. The method according to claim 1 , further comprising: interacting, by the gateway user plane device, with the gateway control plane device to update the rule in response to the gateway user plane device determining to update the rule. 9. The method according to claim 1 , further comprising: sending, by the gateway user plane device, packet feature information of the data packet to the gateway control plane device. 10. The method according to claim 9 , wherein the packet feature information comprises at least one item of a service quintet of the data packet. 11. A bearer processing system comprising: a gateway user plane device, configured to: receive a data packet of a service; determine a rule that matches the data packet, wherein the rule is associated with quality of service (QoS) information required for the service; determine whether the QoS information required for the service is consistent with QoS information of a first bearer that exists for transmitting the data packet of the service; and trigger, in response to the QoS information required for the service being inconsistent with the QoS information of the first bearer, a gateway control plane device to create a dedicated bearer that satisfies the QoS requirement for the service; and the gateway control plane device, wherein the gateway control plane device is configured to create the dedicated bearer that satisfies the QoS requirement for the service, wherein the gateway user plane device and the gateway control plane device are devices in a core network that are separate from each other. 12. The system according to claim 11 , wherein the rule being associated with the QoS information required for the service comprises the rule being associated with a relationship between the service and the QoS information required for the service. 13. The system according to claim 11 , wherein the rule is locally configured by the gateway user plane device. 14. The system according to claim 11 , wherein the gateway user plane device being configured to determine whether the QoS information required for the service is consistent with the QoS information of the first bearer comprises the gateway user plane device being configured to determine whether allocation/retention priority (ARP) information required for the service is consistent with ARP information of the first bearer. 15. The system according to claim 11 , wherein the gateway user plane device being configured to determine whether the QoS information required for the service is consistent with the QoS information of the first bearer comprises the gateway user plane device being configured to determine whether a QoS class identifier (QCI) required for the service is consistent with a QCI of the first bearer. 16. The system according to claim 11 , wherein the gateway user plane device being configured to trigger the gateway control plane device to create the dedicated bearer comprises the gateway user plane device being configured to send the QoS information required for the service to the gateway control plane device. 17. The system according to claim 11 , wherein the gateway user plane device is further configured to interact with the gateway control plane device to delete the dedicated bearer in response to the gateway user plane device determining that the service has ended. 18. The system according to claim 11 , wherein the gateway user plane device is further configured to interact with the gateway control plane device to update the rule in response to the gateway user plane device determining to update the rule. 19. The system according to claim 11 , wherein the gateway user plane device is further configured to send packet feature information of the data packet to the gateway control plane device. 20. The system according to claim 19 , wherein the packet feature information comprises at least one item of a service quintet of the data packet.
per individual bearer or channel (dynamic wireless traffic scheduling H04W72/12) · CPC title
Traffic characterised by specific attributes, e.g. priority or QoS · CPC title
Parsing or analysis of headers · CPC title
based on conditions of the access network or the infrastructure network (central resource management H04W28/16) · 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
Related publications grouped by family.
Answers are generated from the same data shown on this page.