Establishing a session initiation protocol session
US-11297111-B2 · Apr 5, 2022 · US
US11637875B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-11637875-B2 |
| Application number | US-202217707567-A |
| Country | US |
| Kind code | B2 |
| Filing date | Mar 29, 2022 |
| Priority date | Jun 30, 2015 |
| Publication date | Apr 25, 2023 |
| Grant date | Apr 25, 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.
The present disclosure describes methods and systems for establishing a Session Initiation Protocol Session. One method includes transmitting a first message requesting authentication configuration information; in response to the first message, receiving a second message that includes the authentication configuration information; transmitting a third message that includes authentication information based upon the received authentication configuration information; receiving an authentication challenge request that is formatted according to the second protocol; and in response to receiving the authentication challenge request, transmitting an authentication response to the second network node.
Opening claim text (preview).
The invention claimed is: 1. One or more non-transitory computer-readable media storing computer instructions, that when executed by one or more processors, cause a computing device to perform operations comprising: transmitting, from a user equipment (UE) to a first network node, a first message requesting authentication configuration information, wherein the first message is formatted according to a first protocol, and the first network node is an identity management server; in response to the first message, receiving, at the UE and from the identity management server, a second message that includes the authentication configuration information, wherein the authentication configuration information comprises, a phone number that is assigned to a Mission Critical Push to Talk (MCPTT) user identity, a public identity assigned by the identity management server during a user authentication process, and a private identity assigned by the identity management server during the user authentication process; transmitting, from the UE to a second network node, a third message that includes authentication information based upon the received authentication configuration information, wherein the third message is formatted according to a second protocol, and the third message comprises the public identity and the private identity received in the second message; in response to the third message that includes the public identity and the private identity, receiving, at the UE and from the second network node, an authentication challenge request that is formatted according to the second protocol; and in response to receiving the authentication challenge request, transmitting an authentication response to the second network node. 2. The one or more non-transitory computer-readable media of claim 1 , wherein the second network node comprises a Session Initiation Protocol (SIP) core. 3. The one or more non-transitory computer-readable media of claim 1 , wherein the first protocol is at least one of a Hypertext Transfer Protocol (HTTP), an Extensible Authentication Protocol (EAP), or a Session Initiation Protocol (SIP). 4. The one or more non-transitory computer-readable media of claim 1 , wherein the second protocol is a Session Initiation Protocol (SIP). 5. A first network node, comprising: at least one processor; one or more non-transitory computer-readable storage medium coupled to the at least one processor and storing programming instructions for execution by the at least one processor, wherein the programming instructions, when executed, cause the first network node to perform operations comprising: receiving a first authentication request, wherein the first authentication request includes a first user identifier (ID) associated with a first Mission Critical Push to Talk (MCPTT) system, and the first network node is an identity management server; determining that the first user ID is mapped to a second user ID that is associated with a second Mission Critical Push to Talk (MCPTT) system; transmitting, to a user equipment (UE), authentication configuration information, wherein the authentication configuration information includes a phone number that is assigned to the first ID, the second user ID, and a third user ID, the second user ID comprises a private user identity assigned by the identity management server during a user authentication process, and the third user ID comprises a public user identity assigned by the identity management server during the user authentication process; transmitting, to a second network node, a second authentication request, wherein the second authentication request includes the second user ID; in response to the second authentication request, receiving a first authentication response including an authentication response vector; and in response to receiving the first authentication response, transmitting a second authentication response including the authentication response vector. 6. The first network node of claim 5 , wherein the first network node is part of a common services core. 7. The first network node of claim 5 , wherein the authentication response vector is generated based on the second user ID. 8. One or more non-transitory computer-readable media storing computer instructions, that when executed by one or more processors, cause a computing device to perform operations comprising: receiving, at a first network node, a first authentication request, wherein the first authentication request includes a first user identifier (ID) associated with a first Mission Critical Push to Talk (MCPTT) system, and the first network node is an identity management server; determining that the first user ID is mapped to a second user ID that is associated with a second Mission Critical Push to Talk (MCPTT) system; transmitting, from the first network node to a user equipment (UE), authentication configuration information, wherein the authentication configuration information includes a phone number that is assigned to the first ID, the second user ID, and a third user ID, the second user ID comprises a private user identity assigned by the identity management server during a user authentication process, and the third user ID comprises a public user identity assigned by the identity management server during the user authentication process; transmitting, from the first network node to a second network node, a second authentication request, wherein the second authentication request includes the second user ID; in response to the second authentication request, receiving a first authentication response including an authentication response vector; and in response to receiving the first authentication response, transmitting a second authentication response including the authentication response vector. 9. The one or more non-transitory computer-readable media of claim 8 , wherein the first network node is part of a common services core. 10. The one or more non-transitory computer-readable media of claim 8 , wherein the authentication response vector is generated based on the second user ID.
Anonymization, e.g. involving pseudonyms · CPC title
based on the content carried by the session initiation protocol [SIP] messages · CPC title
IP multimedia subsystem [IMS] · CPC title
using challenge-response · CPC title
Address allocation · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.