Discontinuous reception (DRX) enhancements in LTE systems
US-11979768-B2 · May 7, 2024 · US
US10334468B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-10334468-B2 |
| Application number | US-201615285403-A |
| Country | US |
| Kind code | B2 |
| Filing date | Oct 4, 2016 |
| Priority date | Oct 5, 2015 |
| Publication date | Jun 25, 2019 |
| Grant date | Jun 25, 2019 |
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.
In an example, there is disclosed a computing apparatus, having: a processor; a memory; a network interface to communicatively couple to a mobile data network; and an interconnection and routing function (IRF) server engine to: receive an incoming Control plane message from a source network function (NF) via the network interface; examine a header of the incoming Control plane message to determine a destination NF of the Control plane message; and route the Control plane message to the destination NF.
Opening claim text (preview).
What is claimed is: 1. A computing apparatus, comprising: a processor; a memory; a network interface configured to communicatively couple to a mobile data network; and an interconnection and routing function (IRF) server engine configured to: provide a general interface between a plurality of Control plane network functions in a core network of the mobile data network, wherein the plurality of Control plane network functions each comprises a single reference point at the IRF server engine, and wherein each of the plurality of Control plane network functions provides a service on the mobile data network; receive an incoming Control plane message from a source network function (NF) via the network interface; examine a header of the incoming Control plane message to determine a destination NF of the Control plane message, wherein the destination NF is one of the plurality of Control plane network functions; and route the Control plane message to the destination NF using the single reference point of the destination NF, thereby bypassing the remaining plurality of Control plane network functions. 2. The computing apparatus of claim 1 , wherein the IRF server engine is further to identify in a binding repository a binding between an identity of a user equipment (UE) and a serving NF. 3. The computing apparatus of claim 2 , wherein the IRF server engine is further to determine that the binding does not exist, select an instance of the destination NF, and update the binding repository. 4. The computing apparatus of claim 1 , wherein the IRF server engine is further to determine that the destination NF is on a separate public land mobile network (PLMN), and forward the message to a second IRF associated with the separate PLMN. 5. The computing apparatus of claim 1 , wherein the IRF server engine is further to perform authorization, comprising determining that the source NF is authorized to send the incoming Control plane message. 6. The computing apparatus of claim 1 , wherein the IRF server engine is further to provide a subscribe-notify framework. 7. The computing apparatus of claim 1 , wherein the IRF server engine is further to convert a protocol for the source NF to a protocol for the destination NF. 8. The computing apparatus of claim 1 , wherein the IRF server engine is further to protect NFs during a signaling storm, comprising providing overload control. 9. A method of providing interconnection and routing for a mobile data network, comprising: receiving, at an interconnection and routing function (IRF) server engine via a network interface for the mobile data network, an incoming Control plane message from a source network function (NF), wherein the IRF server engine provides a general interface between a plurality of Control plane network functions in a core network of the mobile data network, wherein the plurality of Control plane network functions each comprise a single reference point at the IRF, and wherein each of the plurality of Control plane network functions provides a service on the mobile data network; examining a header of the incoming Control plane message to determine a destination NF of the Control plane message, wherein the destination NF is one of the plurality of Control plane network functions; and routing the Control plane message the destination NF using the single reference point of the destination NF, thereby bypassing the remaining plurality of Control plane network functions. 10. The method of claim 9 , further comprising identifying in a binding repository a binding between an identity of a user equipment (UE) and a serving NF. 11. The method of claim 10 , further comprising determining that the binding does not exist, select an instance of the destination NF, and update the binding repository. 12. The method of claim 9 , further comprising determining that the destination NF is on a separate public land mobile network (PLMN), and forward the message to a second IRF associated with the separate PLMN. 13. The method of claim 9 , further comprising providing a subscribe-notify framework. 14. The method of claim 9 , further comprising converting a protocol for the source NF to a protocol for the destination NF. 15. One or more tangible, non-transitory computer-readable storage mediums having stored thereon executable instructions for providing an interconnection and routing function (IRF) server for a mobile data network, wherein the IRF server is operable for: providing a general interface between a plurality of Control plane network functions in a core network of the mobile data network, wherein the plurality of Control plane network functions each comprises a single reference point at the IRF server, and wherein each of the plurality of Control plane network functions provides a service on the mobile data network; receiving via a network interface for the mobile data network, an incoming Control plane message from a source network function (NF) via the network interface; examining a header of the incoming Control plane message to determine a destination NF of the Control plane message, wherein the destination NF is one of the plurality of Control plane network functions; and routing the Control plane message the destination NF using the single reference point of the destination NF, thereby bypassing the remaining plurality of Control plane network functions. 16. The one or more tangible, non-transitory computer-readable mediums of claim 15 , wherein the IRF server is further operable for identifying in a binding repository a binding between an identity of a user equipment (UE) and a serving NF. 17. The one or more tangible, non-transitory computer-readable mediums of claim 16 , wherein the IRF server is further operable for determining that the binding does not exist, select an instance of the destination NF, and update the binding repository. 18. The one or more tangible, non-transitory computer-readable mediums of claim 15 , wherein the IRF server is further operable for determining that the destination NF is on a separate public land mobile network (PLMN), and forward the message to a second IRF associated with the separate PLMN. 19. The one or more tangible, non-transitory computer-readable mediums of claim 15 , wherein the IRF server is further operable for performing authorization, comprising determining that the source NF is authorized to send the incoming Control plane message. 20. The one or more tangible, non-transitory computer-readable mediums of claim 15 , wherein the IRF server is further operable for converting a protocol for the source NF to a protocol for the destination NF.
adapting protocols for flow control or congestion control to wireless environment, e.g. adapting transmission control protocol [TCP] (wireless network protocols or protocol adaptations to wireless operation, e.g. wireless application protocol H04W80/00) · CPC title
based on user or device properties, e.g. MTC-capable devices (services for machine-to-machine communication [M2M] or machine type communication [MTC] H04W4/70; wireless resource selection or allocation plan definition based on terminal or device properties H04W72/51) · CPC title
Address table lookup; Address filtering · CPC title
Communication route or path selection, e.g. power-based or shortest path routing · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.