SendAuthenticationInfo - Revision history

Monica at 13:56, 27 August 2013

2013-08-27T13:56:49Z

Monica at 13:55, 27 August 2013

2013-08-27T13:55:13Z

Monica: /* References */

2013-08-23T14:03:03Z

‎References

Monica: /* Invoke parameters */

2013-08-23T14:01:47Z

‎Invoke parameters

Monica: /* Result parameters */

2013-08-23T14:01:13Z

‎Result parameters

Monica: /* Example: Requester supports UMTS, card is USIM */

2013-08-23T13:58:30Z

‎Example: Requester supports UMTS, card is USIM

Monica: /* Example: Requester supports UMTS, card is GSM */

2013-08-23T13:58:14Z

‎Example: Requester supports UMTS, card is GSM

Monica: /* Example: Requester supports only GSM */

2013-08-23T13:58:03Z

‎Example: Requester supports only GSM

Monica: /* Note */

2013-08-23T13:57:26Z

‎Note

Monica: Created page with "==Capability: Authentication== ==Usage== This message is sent by a MSC, VLR or SGSN to the HLR to retrieve authentication parameters. ==Expected actions== The application ..."

2013-08-23T13:53:32Z

Created page with "==Capability: Authentication== ==Usage== This message is sent by a MSC, VLR or SGSN to the HLR to retrieve authentication parameters. ==Expected actions== The application ..."

New page

==Capability: Authentication==

==Usage==

This message is sent by a MSC, VLR or SGSN to the HLR to retrieve authentication parameters.

==Expected actions==

The application name or OID are checked against known values to detect if the requester supports only GSM authentication or both GSM and UMTS.

After checking that the IMSI is known an Authentication Center must be invoked to compute one or more (up to 5) authentication triplets (rand,sres,Kc) or UMTS quintuplets (rand,xres,ck,ik,autn) based on the secret Ki and eventually sequence number (for UMTS) stored with the IMSI. These triplets or quintuplets are sent back to the invoker to use for authentication.

If the IMSI is known but authentication sets cannot be retrieved an empty list may be returned, indicating to the invoker that existing information is to be reused.

==Invoke parameters==

* '''imsi''' – Identity of the SIM requiring authentication

* ''numberOfRequestedVectors'' – How many authentication sets are desired (UMTS)

* ''re-synchronisationInfo'' – Information used for UMTS resynchronization procedure

** '''rand''' – Random number (16 octets)

** '''auts''' – Synchronization authentication token (16 octets)
* ''requestingNodeType'' – The type of service that tries to authenticate the SIM, may be "hlr", "sgsn", "bsf" or others like "gan-aaa-server" or "wlan-aaa-server"

* ''requestingPLMN-Id'' – Identity of the mobile network that tries to authenticate the SIM

==Result parameters==

* sendAuthenticationInfoRes-v3 – If requester used a v3 application context

** '''authenticationSetList'''

*** tripletList – If the SIM is GSM

**** triplet – Authentication triplet(s) consisting of:

***** '''rand''' – Random number (16 octets)

***** '''sres''' – Signed response (4 octets)

***** '''kc''' – Ciphering key (8 octets)

*** quintupletList – If the SIM is UMTS

**** quintuplet – Authentication quintuplet(s) consisting of:

***** '''rand''' – Random number (16 octets)

***** '''xres''' – Signed response (4-16 octets, 8 typical)

***** '''ck''' – Ciphering key (16 octets)

***** '''ik''' – Integrity key (16 octets)

***** '''autn''' – Network authentication token (16 octets)

* sendAuthenticationInfoRes-v2 – If requester used a v2 application context (GSM only)

** set – Authentication triplet(s) consisting of:

*** '''rand''' – Random number (16 octets)

*** '''sres''' – Signed response (4 octets)

*** '''kc''' – Ciphering key (8 octets)

==Possible errors==

* systemFailure
* dataMissing
* unexpectedDataValue
* unknownSubscriber

==Note==

A description of the GSM authentication and encryption is available at:
http://www.gsmfordummies.com/encryption/encryption.shtml \\
It is possible to have a batch of GSM authentication triplets precomputed for each SIM.\\
For UMTS the order of the returned quintuplets is important and must be preserved.\\
There is never a case when both GSM and UMTS authentication is returned. Normally in a dual mode SIM each mode has its own separate IMSI although they have associated the same MSISDN.\\
If the requesting entity supports only GSM authentication but the SIM is known to support UMTS then the quintuplets are converted to triplets by applying the c1, c2 and c3 transforms1. In this case the SIM will degrade authentication and ciphering to GSM level.

==Example: Requester supports only GSM==

<component remoteCID=1" type="Invoke" operationCode="sendAuthenticationInfo">
<imsi enc="e212">497012345678900</imsi>
</component>
...
<component remoteCID=1" type="ResultLast" operationCode="sendAuthenticationInfo">
<sendAuthenticationInfoRes-v2>
<set>
<rand>00 11 22 33 44 55 66 77 88 99 aa bb cc dd ee ff</rand>
<sres>11 22 33 44</sres>
<kc>00 11 22 33 44 55 66 77</kc>
</set>
</sendAuthenticationInfoRes-v2>
</component>

==Example: Requester supports UMTS, card is GSM==

<component remoteCID=1" type="Invoke" operationCode="sendAuthenticationInfo">
<imsi enc="e212">497012345678900</imsi>
</component>
...
<component remoteCID=1" type="ResultLast" operationCode="sendAuthenticationInfo">
<sendAuthenticationInfoRes-v3>
<authenticationSetList>
<tripletList>
<triplet>
<rand>00 11 22 33 44 55 66 77 88 99 aa bb cc dd ee ff</rand>
<sres>11 22 33 44</sres>
<kc>00 11 22 33 44 55 66 77</kc>
</triplet>
</tripletList>
</authenticationSetList>
</sendAuthenticationInfoRes-v3>
</component>

==Example: Requester supports UMTS, card is USIM==

<component remoteCID=1" type="Invoke" operationCode="sendAuthenticationInfo">
<imsi enc="e212">497012345678900</imsi>
</component>
...
<component remoteCID=1" type="ResultLast" operationCode="sendAuthenticationInfo">
<sendAuthenticationInfoRes-v3>
<authenticationSetList>
<quintupletList>
<quintuplet>
<rand>00 11 22 33 44 55 66 77 88 99 aa bb cc dd ee ff</rand>
<xres>11 22 33 44 55 66 77 88</xres>
<ck>00 11 22 33 44 55 66 77 88 99 aa bb cc dd ee ff</ck>
<ik>00 11 22 33 44 55 66 77 88 99 aa bb cc dd ee ff</ik>
<autn>00 11 22 33 44 55 66 77 88 99 aa bb cc dd ee ff</autn>
<quintuplet>
</quintupletList>
</authenticationSetList>
</sendAuthenticationInfoRes-v3>
</component>

==References==
* 1 - ETSI TS 100 974 V7.15.0 (2004-03) p1050
* 2 - ETSI TS 129 002 V9.3.0 (2010-10) p352

← Older revision		Revision as of 13:56, 27 August 2013
Line 1:		Line 1:
	{{DISPLAYTITLE:sendAuthenticationInfo}}		{{DISPLAYTITLE:sendAuthenticationInfo}}
−
	==Capability: Authentication==		==Capability: Authentication==

← Older revision		Revision as of 13:55, 27 August 2013
Line 1:		Line 1:
		+	{{DISPLAYTITLE:sendAuthenticationInfo}}
		+
	==Capability: Authentication==		==Capability: Authentication==

@@ Line 126: / Line 126: @@
 ==References==
-* 1 - ETSI TS 100 974 V7.15.0 (2004-03) p1050
+*  ETSI TS 100 974 V7.15.0 (2004-03) p1050
-* 2 - ETSI TS 129 002 V9.3.0 (2010-10) p352
+*  ETSI TS 129 002 V9.3.0 (2010-10) p352

@@ Line 16: / Line 16: @@
 * '''imsi''' – Identity of the SIM requiring authentication
 * ''numberOfRequestedVectors'' – How many authentication sets are desired (UMTS)
 * ''re-synchronisationInfo'' – Information used for UMTS resynchronization procedure
 ** '''rand''' – Random number (16 octets)
 ** '''auts''' – Synchronization authentication token (16 octets)
 * ''requestingNodeType'' – The type of service that tries to authenticate the SIM, may be "hlr", "sgsn", "bsf" or others like "gan-aaa-server" or "wlan-aaa-server"
 * ''requestingPLMN-Id'' – Identity of the mobile network that tries to authenticate the SIM

@@ Line 31: / Line 31: @@
 * sendAuthenticationInfoRes-v3 – If requester used a v3 application context
 **'''authenticationSetList'''
-** '''authenticationSetList'''
+***tripletList – If the SIM is GSM
 ****triplet – Authentication triplet(s) consisting of:
 *** tripletList – If the SIM is GSM
-−
 **** triplet – Authentication triplet(s) consisting of:
-−
 ***** '''rand''' – Random number (16 octets)
 ***** '''sres''' – Signed response (4 octets)
 ***** '''kc''' – Ciphering key (8 octets)
 *** quintupletList – If the SIM is UMTS
 **** quintuplet – Authentication quintuplet(s) consisting of:
 ***** '''rand''' – Random number (16 octets)
 ***** '''xres''' – Signed response (4-16 octets, 8 typical)
 ***** '''ck''' – Ciphering key (16 octets)
 ***** '''ik''' – Integrity key (16 octets)
 ***** '''autn''' – Network authentication token (16 octets)
 * sendAuthenticationInfoRes-v2 – If requester used a v2 application context (GSM only)
 ** set – Authentication triplet(s) consisting of:
 *** '''rand''' – Random number (16 octets)
 *** '''sres''' – Signed response (4 octets)
 *** '''kc''' – Ciphering key (8 octets)

@@ Line 125: / Line 125: @@
   </component>
-==Example: Requester supports UMTS, card is USIM==
+=== Requester supports UMTS, card is USIM===
   <component remoteCID=1" type="Invoke" operationCode="sendAuthenticationInfo">
@@ Line 146: / Line 146: @@
   	</sendAuthenticationInfoRes-v3>
   </component>
 ==References==
 * 1 - ETSI TS 100 974 V7.15.0 (2004-03) p1050
 * 2 - ETSI TS 129 002 V9.3.0 (2010-10) p352

@@ Line 105: / Line 105: @@
   </component>
-==Example: Requester supports UMTS, card is GSM==
+===Requester supports UMTS, card is GSM===
   <component remoteCID=1" type="Invoke" operationCode="sendAuthenticationInfo">

@@ Line 88: / Line 88: @@
 If the requesting entity supports only GSM authentication but the SIM is known to support UMTS then the quintuplets are converted to triplets by applying the c1, c2 and c3 transforms1. In this case the SIM will degrade authentication and ciphering to GSM level.
-==Example: Requester supports only GSM==
+==Examples==
   <component remoteCID=1" type="Invoke" operationCode="sendAuthenticationInfo">

@@ Line 75: / Line 75: @@
 * unknownSubscriber
-==Note==
+==Notes==
 A description of the GSM authentication and encryption is available at:
-http://www.gsmfordummies.com/encryption/encryption.shtml \\
+http://www.gsmfordummies.com/encryption/encryption.shtml
-It is possible to have a batch of GSM authentication triplets precomputed for each SIM.\\
-For UMTS the order of the returned quintuplets is important and must be preserved.\\
+It is possible to have a batch of GSM authentication triplets precomputed for each SIM.
-There is never a case when both GSM and UMTS authentication is returned. Normally in a dual mode SIM each mode has its own separate IMSI although they have associated the same MSISDN.\\
 If the requesting entity supports only GSM authentication but the SIM is known to support UMTS then the quintuplets are converted to triplets by applying the c1, c2 and c3 transforms1. In this case the SIM will degrade authentication and ciphering to GSM level.