Mobile gateway selection using a direct connection between a pcrf node and a mobility management node
US-2015382386-A1 · Dec 31, 2015 · US
US10484933B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-10484933-B2 |
| Application number | US-201113816597-A |
| Country | US |
| Kind code | B2 |
| Filing date | Aug 10, 2011 |
| Priority date | Aug 12, 2010 |
| Publication date | Nov 19, 2019 |
| Grant date | Nov 19, 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.
A network entity for managing communications towards a user entity over a communication network, the network entity having an access domain selector for determining an access domain of the user entity upon the basis of user entity specific data, and an application server for providing the user entity specific data.
Opening claim text (preview).
The invention claimed is: 1. A network entity for managing communications towards a user entity over a communication network, the network entity having: an access domain selector, collocated to the network entity, for determining an access domain of the user entity upon a basis of user entity specific data; wherein an access domain selector implemented on a hardware processor; a storage collocated to the network entity; and an IP Multimedia Subsystem application server, collocated to the network entity and separate from the access domain selector, for providing the user entity specific data, configured to transmit a request, via an Sh interface according to the IP Multimedia Subsystem, for the user entity specific data towards a home subscriber server; receive the user entity specific data from the home subscriber server upon transmitting the request; and store the user entity specific data in the storage, wherein the access domain selector is further configured to retrieve the user entity specific data upon receiving a session initiation protocol request, the session initiation request requesting to establish a communication link towards the access domain serving the user entity for an incoming session; refer to the storage of the application server to obtain the user entity specific data; and when the user entity specific data is unavailable from the storage, query the user entity specific data from the home subscriber server; wherein the application server is an IP Multimedia Subsystem multimedia telephony service application server; wherein the access domain selector is an IP Multimedia Subsystem access domain selector configured as a service centralization and continuity application server; and wherein the user entity specific data comprises: repository data according to the IP Multimedia Subsystem technology, a network identifier, wherein the network identifier is a visitor location register number, voice support information indicating whether the access domain supports a voice service within a packet-switched access domain, information relating to a communication status of the user entity, the communication status indicating whether the user entity is in a busy status, an idle status, a non-available status, or a non-network registered status, type information indicating a type of the access domain, the type of the access domain indicating a packet-switched access domain or a circuit-switched access domain, and a user entity identifier, wherein the user entity identifier is an International Mobile Subscriber Identity. 2. The network entity of claim 1 , wherein the access domain selector is configured to retrieve the user entity specific data from the storage. 3. The network entity of claim 1 , wherein the application server is configured to determine the user entity specific data upon registration of the user entity to the communication network. 4. The network entity of claim 1 , wherein the application server is an IP Multimedia Subsystem application server being configured to receive the user entity specific data via an Sh interface over the communication network. 5. The network entity of claim 1 , wherein the network entity or the application server and the access domain selector has a transmitter for transmitting a request for the user entity specific data towards the communication network. 6. The network entity of claim 1 , wherein the network entity or the application server or the access domain selector has a receiver for receiving the user entity specific data from the communication network. 7. The network entity of claim 1 , wherein the access domain selector is configured to determine upon the basis of the user entity specific data whether the access domain is a packet-switched access network; or whether the access domain is a circuit-switched access network. 8. A method for managing communications towards a user entity over a communication network, the method being performed by a network entity having an IP Multimedia Subsystem access domain selector configured as a service centralization and continuity application server, collocated to the network entity, a storage collocated to the network entity, and an IP Multimedia Subsystem multimedia telephony service application server collocated to the network entity and separate from the access domain selector, the method comprising: providing user entity specific data by the application server for access domain selection, including transmitting a request, via an Sh interface according to the IP Multimedia Subsystem, for the user entity specific data by the application server towards a home subscriber server, receiving the user entity specific data by the application server from the home subscriber server upon transmitting the request, and storing the user entity specific data by the application server in the storage; and determining an access domain of the user entity by the access domain selector upon a basis of the user entity specific data, including retrieving the user entity specific data upon receiving a session initiation protocol request, the session initiation request requesting to establish a communication link towards the access domain serving the user entity for an incoming session, referring to the application server to obtain the user entity specific data, and when the user entity specific data is unavailable from the storage, querying the user entity specific data from the home subscriber server, wherein the user entity specific data comprises: repository data according to the IP Multimedia Subsystem technology, a network identifier, wherein the network identifier is a visitor location register number, voice support information indicating whether the access domain supports a voice service within a packet-switched access domain, information relating to a communication status of the user entity, the communication status indicating whether the user entity is in a busy status, an idle status, a non-available status, or a non-network registered status, type information indicating a type of the access domain, the type of the access domain indicating a packet-switched access domain or a circuit-switched access domain, and a user entity identifier, wherein the user entity identifier is an International Mobile Subscriber Identity.
Responding to QoS · CPC title
Selecting a data network PoA [Point of Attachment] · CPC title
Discovering, processing access restriction or access information · CPC title
Registration or de-registration · CPC title
Selecting a network or a communication service · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.