Method for establishing mcptt group call in wireless communication system and device therefor
US-2017289776-A1 · Oct 5, 2017 · US
US10499245B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-10499245-B2 |
| Application number | US-201615565801-A |
| Country | US |
| Kind code | B2 |
| Filing date | Apr 12, 2016 |
| Priority date | Apr 2, 2015 |
| Publication date | Dec 3, 2019 |
| Grant date | Dec 3, 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.
Embodiments herein provide a method for performing multiple authentications within a service registration procedure. The method includes sending, by a User Equipment (UE) a REGISTER request message to an IP Multimedia Subsystem (IMS) server. Further, the method includes receiving, an IMS authentication challenge from the IMS server, where the IMS authentication challenge includes an IMS authentication parameter and a MCPTT authentication challenge. Further, the method includes verifying, at the UE, the IMS authentication challenge. Further, the method includes generating, at the UE, a REGISTER response message. Further, the method includes sending, a REGISTER response message to the IMS server, where the REGISTER response message includes an IMS authentication response to authenticate UE at the IMS server and a MCPTT authentication response to authenticate the UE at the MCPTT server.
Opening claim text (preview).
The invention claimed is: 1. A method for performing multiple authentications within a service registration procedure by a user equipment (UE), the method comprising: receiving, from a session initiation protocol (SIP) core, an authentication challenge; verifying the authentication challenge; and transmitting, to the SIP core, a first register message including an access token to authenticate the UE in the SIP core and to authenticate the UE in a mission critical push to talk (MCPTT) server, wherein a second register message including the access token is transmitted from the SIP Core to the MCPTT server to authenticate the UE in the MCPTT server in case that a successful SIP authentication is performed based on the first register message. 2. The method of claim 1 , wherein an IP multimedia public user identity (IMPU) is bound with a MCPTT ID by the MCPTT server when the MCPTT server receives the second register message. 3. The method of claim 1 , wherein the first register message and the second register message include a parameter to authenticate the UE in the MCPTT server respectively. 4. A method for performing multiple authentications within a service registration procedure by a session initiation protocol (SIP) core, the method comprising: transmitting, to a user equipment (UE), an authentication challenge to be verified the authentication challenge in the UE; receiving, from the UE, a first register message including an access token to authenticate the UE in the SIP core and to authenticate the UE in a mission critical push to talk (MCPTT) server; and transmitting, to the MCPTT server, a second register message including the access token to authenticate the UE in the MCPTT server in case that a successful SIP authentication is performed based on the first register message. 5. The method of claim 4 , wherein an IP multimedia public user identity (IMPU) is bound with a MCPTT ID by the MCPTT server when the MCPTT server receives the second register message. 6. The method claim 4 , wherein the first register message and the second register message include a parameter to authenticate the UE in the MCPTT server respectively. 7. A user equipment (UE) for performing multiple authentications within a service registration procedure, the UE comprising: a transceiver; and a controller coupled with the transceiver and configured to control to: receive, from a session initiation protocol (SIP) core, an authentication challenge, verify the authentication challenge, and transmit, to the SIP core a first register message including an access token to authenticate the UE in the SIP core and to authenticate the UE in a mission critical push to talk (MCPTT) server, wherein a second register message including the access token is transmitted from the SIP Core to the MCPTT server to authenticate the UE in the MCPTT server in case that a successful SIP authentication is performed based on the first register message. 8. The UE of claim 7 , wherein the first register message and the second register message include a parameter to authenticate the UE in the MCPTT server respectively. 9. A session initiation protocol (SIP) core for performing multiple authentications within a service registration procedure, the SIP core comprising: a transceiver; and a controller coupled with the transceiver and configured to control to: transmit, to a user equipment (UE), an authentication challenge to be verified the authentication challenge in the UE, receive, from the UE, a first register message including an access token to authenticate the UE in the SIP core and to authenticate the UE in a mission critical push to talk (MCPTT) server, and transmit, to the MCPTT server, a second register message including the access token to authenticate the UE in the MCPTT server in case that a successful SIP authentication is performed based on the first register message. 10. The SIP core of claim 9 , wherein an IP multimedia public user identity (IMPU) is bound with a MCPTT ID by the MCPTT server when the MCPTT server receives the second register message. 11. The SIP core of claim 9 , wherein the first register message and the second register message include a parameter to authenticate the UE in the MCPTT server respectively. 12. The SIP core of claim 9 , wherein an IP multimedia public user identity (IMPU) is bound with a MCPTT ID by the MCPTT server when the MCPTT server receives the second register message.
for Push-to-Talk [PTT] or Push-to-Talk over cellular [PoC] services · CPC title
Multiple registrations, e.g. multihoming · CPC title
IP multimedia subsystem [IMS] · CPC title
Push-to services, e.g. push-to-talk or push-to-video · CPC title
for emergency connections · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.