Reporting a network slice parameter for admission control
US-2024073802-A1 · Feb 29, 2024 · US
US9479652B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-9479652-B2 |
| Application number | US-201514737227-A |
| Country | US |
| Kind code | B2 |
| Filing date | Jun 11, 2015 |
| Priority date | Dec 14, 2012 |
| Publication date | Oct 25, 2016 |
| Grant date | Oct 25, 2016 |
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.
The present invention relates to a method, a system, a gateway, and a server for canceling redirection. When balances of a user are insufficient, a gateway (GW) receives a redirection policy delivered by a policy and charging rules function (PCRF) and redirects the user to a recharging page of a server; after recharging is finished, the server sends a recharging success packet to the GW, and the GW instructs the PCRF to cancel the redirection policy. In this way, after the recharging succeeds, the server directly sends the recharging success packet to the GW, and the GW can immediately instruct the PCRF to cancel the redirection policy after receiving the packet. Therefore, no delay problem of a billing system exists, thereby avoiding that the user is repeatedly redirected to the recharging page of the server during a delay time and enhancing user experience.
Opening claim text (preview).
What is claimed is: 1. A method for canceling redirection, the method comprising: redirecting, by a gateway (GW), a user equipment (UE) to a recharging page of a server according to a redirection policy; receiving a recharging success packet sent by the server; and instructing, according to the recharging success packet, a policy and charging rules function (PCRF) to cancel the redirection policy. 2. The method for canceling redirection according to claim 1 , wherein receiving the recharging success packet sent by the server comprises: obtaining, by the GW, the recharging success packet by monitoring a packet that is sent from the server to the UE. 3. The method for canceling redirection according to claim 1 , wherein receiving the recharging success packet sent by the server comprises: receiving the recharging success packet from the UE, wherein the recharging success packet is sent by the server to the UE. 4. The method for canceling redirection according to claim 1 , wherein the GW receives the redirection policy from the PCRF. 5. A method for canceling redirection, the method comprising: receiving, by a server, a recharging request of a user equipment (UE); and when recharging for the UE succeeds, sending a recharging success packet to a gateway (GW) for the GW to instruct a policy and charging rules function (PCRF) to cancel a redirection policy. 6. The method for canceling redirection according to claim 5 , wherein sending the recharging success packet to the GW comprises: sending the recharging success packet to the UE, and the recharging success packet is acquired by the GW at the same time. 7. The method for canceling redirection according to claim 5 , wherein sending the recharging success packet to the GW comprises: sending the recharging success packet to the UE, and the recharging success packet is sent by the UE to the GW. 8. A gateway, comprising: a redirecting unit, configured to redirect a user equipment (UE) to a recharging page of a server according to a redirection policy; a receiving unit, configured to receive a recharging success packet sent by the server; and a canceling unit, configured to instruct, according to the recharging success packet, a policy and charging rules function (PCRF) to cancel the redirection policy. 9. The gateway according to claim 8 , wherein the receiving unit is further configured to: obtain the recharging success packet by monitoring a packet that is sent from the server to the UE. 10. The gateway according to claim 8 , wherein the receiving unit is further configured to: receive the recharging success packet from the UE, wherein the recharging success packet is sent by the server to the UE. 11. The gateway according to claim 8 , wherein the redirecting unit is further configured to: receive the redirection policy from the PCRF. 12. A server, comprising: a receiving unit, configured to receive a recharging request of a user equipment (UE) sent by a gateway (GW); and a canceling unit, configured to, when recharging for the UE succeeds, send a recharging success packet to the GW for the GW to instruct a policy and charging rules function (PCRF) to cancel a redirection policy. 13. The server according to claim 12 , wherein the canceling unit is further configured to: send the recharging success packet to the UE, and the recharging success packet is acquired by the GW at the same time. 14. The server according to claim 12 , wherein the canceling unit is further configured to: send the recharging success packet to the UE, and the recharging success packet is sent by the UE to the GW. 15. A gateway, comprising: a network interface; a processor; a memory; and an application program physically stored in the memory, wherein the application program comprises instructions configured to cause the processor to: redirect a user equipment (UE) to a recharging page of a server according to a redirection policy, receive a recharging success packet sent by the server, and instruct, according to the recharging success packet, a policy and charging rules function (PCRF) to cancel the redirection policy. 16. The gateway according to claim 15 , wherein the application program comprises instructions configured to cause the processor to: obtain, by the GW, the recharging success packet by monitoring a packet that is sent from the server to the UE. 17. The gateway according to claim 15 , wherein the application program comprises instructions configured to cause the processor to: receive the recharging success packet from the UE, wherein the recharging success packet is sent by the server to the UE. 18. The gateway according to claim 15 , wherein the application program further comprises instructions configured to cause the processor to: receive the redirection policy from the PCRF. 19. A server, comprising: a network interface; a processor; a memory; and an application program physically stored in the memory, wherein the application program comprises instructions configured to cause the processor to: receive a recharging request of a user equipment (UE), and when recharging for the UE succeeds, send a recharging success packet to a gateway (GW) for the GW to instruct a policy and charging rules function (PCRF) to cancel a redirection policy. 20. A system for canceling redirection, the system comprising: a gateway; and a server; wherein the gateway is configured to redirect a user equipment (UE) to a recharging page of a server according to a redirection policy, receive a recharging success packet sent by the server, and instruct, according to the recharging success packet, a policy and charging rules function (PCRF) to cancel the redirection policy; and wherein the server is configured to receive the recharging request of the UE sent by the GW, and when recharging for the UE succeeds, send a recharging success packet to the GW.
Provision for limiting connection, or expenditure · CPC title
Low balance or limit reached · CPC title
Advice-of-Charge [AOC], i.e. notify subscriber of charges/cumulative charge; meter at the substation · CPC title
characterised by the type of condition triggering a notification · CPC title
Notification aspects · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.