ATIS 0500024-2013 Comparison of SIP Profiles.pdf

1、 TECHNICAL REPORT ATIS-0500024 COMPARISON OF SIP PROFILES As a leading technology and solutions development organization, ATIS brings together the top global ICT companies to advance the industrys most-pressing business priorities. Through ATIS committees and forums, nearly 200 companies address clo

2、ud services, device solutions, emergency services, M2M communications, cyber security, ehealth, network evolution, quality of service, billing support, operations, and more. These priorities follow a fast-track development lifecycle from design and innovation through solutions that include standards

3、, specifications, requirements, business use cases, software toolkits, and interoperability testing. ATIS is accredited by the American National Standards Institute (ANSI). ATIS is the North American Organizational Partner for the 3rd Generation Partnership Project (3GPP), a founding Partner of oneM

4、2M, a member and major U.S. contributor to the International Telecommunication Union (ITU) Radio and Telecommunications sectors, and a member of the Inter-American Telecommunication Commission (CITEL). For more information, visit . Notice of Disclaimer Stage 3 (Release 10), March 15, 2013.12. ATIS-1

5、000009.2006 (R2011), IP Network - to -Network Interface (NNI) Standard for VOIP, May 2006.23. ATIS-0700015, ATIS Standard for Implementation of 3GPP Common IMS Emergency Procedures for IMS Origination and Esinet/Legacy Selective Router Termination pending publication.31This document is available fro

6、m the Third Generation Partnership Project (3GPP) at . 2This document is available from the Alliance for Telecommunications Industry Solutions (ATIS), 1200 G Street N.W., Suite 500, Washington, DC 20005 . 3Requests for information regarding this document should be made to the ATIS Document Center Ad

7、ministrator at . ATIS-0500024 2 2.2 Informative References 4. NENA 08-003 V1, Detailed Functional and Interface Specification for the NENA I3 Solution Stage 3, June 14, 2011.45. RFC 8661, Best Current Practice for Communications Services in Support of Emergency Calling, March 2013.53 Definitions, Ac

8、ronyms, & Abbreviations 3.1 Definitions NENA i3 NENA i3 describes the “end state” that has been reached after a migration from legacy TDM circuit-switched telephony, and the legacy E9-1-1 system built to support it, to an all IP-based telephony system with a corresponding IP-based Emergency Services

9、 IP network. ESInet An ESInet defined by NENA i3 and is a managed IP network that is used for emergency services communications, and which can be shared by all public safety agencies. Mm/Mx/Ici, These 3GPP reference points are defined in Reference 1 and are among the reference points that apply for

10、interconnections to the ESInet. 3.2 Acronyms & Abbreviations 3GPP 3rdGeneration Partnership Project ANSI American National Standards Institute ATIS Alliance for Telecommunications Industry Solutions ESIF Emergency Services Interconnection Forum IETF Internet Engineering Task Force IMS IP Multimedia

11、Subsystem NENA National Emergency Numbering Association NNI Network to Network Interface SDO Standard Development Organization SIP Session Initiation Protocol TR Technical Report 4This document is available from the National Emergency Number Association. 5This document is available from the Internet

12、 Engineering Task Force (IETF). ATIS-0500024 3 4 SIP Profile Comparison This Technical Report (TR) compares the INVITE SIP profiles that have been defined in ATISs IP Network to Network (NNI) Standard 2, ATISs Standard for Implementation of 3GPP Common IMS Emergency Procedures for IMS Origination an

13、d ESInet/Legacy Selective Router Termination, 3GPP IMS Stage 3 1, and NENAs i3 Stage 3 specification 4. NENAs i3 specification does not define a formal profile, so the inclusion of NENA proposed SIP headers have been extracted from the text the NENA i3 stage 3 specification and IETF RFC 6881 5. This

14、 TR contains four profile comparisons. The first comparison table shows the combined headers provided by all organizations. The 3GPP profile was used as the baseline since it included the most headers. The second comparison table compares the ATIS NNI with the ATIS Standard for Implementation of 3GP

15、P Common IMS Emergency Procedures for IMS Origination and ESInet/Legacy Selective Router Termination. The ATIS Standard for Implementation of 3GPP Common IMS Emergency Procedures for IMS Origination and ESInet/Legacy Selective Router Termination used the ATIS NNI as a baseline and adapted the profil

16、e to support emergency services. The third comparison table compares the ATIS Standard for Implementation of 3GPP Common IMS Emergency Procedures for IMS Origination and ESInet/Legacy Selective Router Termination with the 3GPP specification. Note that 3GPP has not defined the Mm interface which woul

17、d support emergency services. Therefore, the 3GPP profile is not specific for emergency services. The fourth comparison table compares the ATIS Standard for Implementation of 3GPP Common IMS Emergency Procedures for IMS Origination and ESInet/Legacy Selective Router Termination with the NENA i3 spec

18、ification. Again, NENA did not provide a formal profile so the header support was extracted from the text. The following table identifies the coding used in the ATIS standards. Table 1 - ATIS NNI Legend Code Code name Sending side Receiving side M Mandatory See Reference 2 for definition. See Refere

19、nce 2 for definition. ND Not Defined Header is not explicitly defined in standard. Header is not explicitly defined in standard. O Optional See Reference 2 for definition. See Reference 2 for definition. - Not Supported See Reference 2 for definition. See Reference 2 for definition. S Recommended Se

20、e Reference 2 for definition. See Reference 2 for definition. ATIS-0500024 4 The following table identifies the coding used in the 3GPP standards. Table 2- 3GPP Legend Status code Status name MeaningM Mandatory See Reference 1 for definition. O Optional See Reference 1 for definition. N/A Not Applic

21、able See Reference 1 for definition. X Prohibited (excluded) See Reference 1 for definition. C Conditional See Reference 1 for definition. O. Qualified optional See Reference 1 for definition. I Irrelevant See Reference 1 for definition. The following table shows the use of headers from the four spe

22、cifications. ATIS and 3GPP specified the needs for both the sender and receiver. Since the NENA i3 information was extracted from the text, no assumptions were made regarding differences between the sender and receiver. ATIS-0500024 5 Table 3 - Combined Profile Comparison Item Header field Send Send

23、 Send Receive Receive Receive3GPP Profile status ATIS ici6ATIS NNI IETF 3GPP Profile status ATIS ici ATIS NNI NENA I3 1 Accept C47 M M O M M M O 1A Accept-Contact C24 ND ND O C32 ND ND O 2 Accept-Encoding O O O O M M M O 3 Accept-Language O S S O M M M O 4 Alert-Info O O O O C1 O O O 5 Allow O M M O

24、 M M M O 6 Allow-Events C2 O ND O C53 O ND O 7 Answer-Mode C49 ND ND O C50 ND ND ND 8 Authorization C3 - O O C3 - O O 8A Authentication-Info ND ND O O ND ND O O 9 Call-ID M M M M M M M M 10 Call-Info O O O O O O O M711 Contact M M M M M M M M 12 Content-Disposition O O O O M M M O 13 Content-Encodin

25、g O O O O M M M O 14 Content-Language O O O O M O O O 15 Content-Length M M M O M M M M 16 Content-Type M M M O M M M M 6The 3GPP defined Ici reference point is used in the ATIS-0700015, Standard for Implementation of 3GPP Common IMS Emergency Procedures for IMS Origination and ESInet/Legacy Selecti

26、ve Router Termination. 7The NENA 08-003 specification requires this header. However, a call that does not contain such a header will be accepted at the ESInet interface. ATIS-0500024 6 Item Header field Send Send Send Receive Receive Receive3GPP Profile status ATIS ici6ATIS NNI IETF 3GPP Profile sta

27、tus ATIS ici ATIS NNI NENA I3 17 Cseq M M M M M M M M 18 Date C4 O O O M O O O 18A Error-Info ND O O O ND O O O 19 Expires O - M O O - M O 20 From M M M M M M M M 20A Geolocation C33 O ND O C33 O ND M720B History-Info C31 O ND O C31 M ND O 21 In-Reply-To O - O O O - O O 21A Join C30 ND ND O C30 ND N

28、D ND 21B Max-Breadth C45 ND ND O N46 ND ND ND 22 Max-Forwards M M M M C52 M M M 23 MIME-Version O O O O M M M O 23A Min-SE C26 ND ND O C25 ND ND ND 24B Min-Expires ND ND O O ND ND O ND 24 Organization O - O O O - O O 24A P-Access-Network-Info C16 ND ND O C17 ND ND ND 24B P-Asserted-Identity N/A O ND

29、 O C7 ND ND O 24C P-Asserted-Service N/A ND ND O C38 ND ND ND 24D P-Called-Party-ID X ND ND O C13 ND ND ND 24E P-Charging-Function-Addresses C21 ND ND O C21 ND ND ND 24F P-Charging-Vector C19 ND ND O C19 ND ND ND 24G P-Debug-ID C43 ND ND O C44 ND ND ND 24H P-Early-Media C34 ND ND O C34 ND ND ND ATIS

30、-0500024 7 Item Header field Send Send Send Receive Receive Receive3GPP Profile status ATIS ici6ATIS NNI IETF 3GPP Profile status ATIS ici ATIS NNI NENA I3 25 P-Media-Authorization N/A ND ND O C12 ND ND ND 25A P-Preferred-Identity C5 ND ND O N/A ND ND O 25B P-Preferred-Service C36 ND ND O N/A ND ND

31、ND 25C P-Private-Network-Indication C42 ND ND O C42 ND ND ND 25D P-Profile-Key N/A ND ND O N/A ND ND ND 25E P-Served-User C51 ND ND O C51 ND ND ND 25F P-User-Database N/A ND ND O N/A ND ND ND 25G P-Visited-Network-ID X ND ND O N/A ND ND ND 26 Priority O - O O O - O O 26A Privacy C9 ND ND O C9 ND ND

32、O 26B Priv-Answer-Mode C49 ND ND O C50 ND ND ND 26C Proxy-Authentication ND ND O O ND ND O O 27 Proxy-Authorization C6 - O O N/A - O O 28 Proxy-Require O (NOTE 2) - M O N/A - M O 28A Reason C8 ND ND O C55 ND ND O 29 Record-Route C52 ND M O M ND M O 29A Recv-Info C48 ND ND O C48 ND ND ND 30 Referred-

33、By C27 ND ND O C28 ND ND O 31 Reject-Contact C24 ND ND O C32 ND ND ND 31A Replaces C29 ND ND O C29 ND ND O 31B Reply-To O - O O O - O O 31C Request-Disposition C24 ND ND O C32 ND ND ND ATIS-0500024 8 Item Header field Send Send Send Receive Receive Receive3GPP Profile status ATIS ici6ATIS NNI IETF 3

34、GPP Profile status ATIS ici ATIS NNI NENA I3 32 Require M M M O M M M O 32A Resource-Priority C35 ND ND O C35 ND ND O 32B Retry-After ND ND O O ND ND O ND 33 Route M - M O C52 - M M 33A Security-Client C22 ND ND O N/A ND ND ND 33B Security-Verify C23 ND ND O N/A ND ND ND 33C Server ND ND O O ND ND O

35、 O 33D Session-Expires C25 ND ND O C25 ND ND ND 33E Session-ID C54 ND ND O C54 ND ND ND 34 Subject O - O O O - O O 35 Supported M M M O M M M O 35A Target-Dialog C56 ND ND O C57 ND ND ND 36 Timestamp C10 O O O M M M O 37 To M M M M M M M M 37A Trigger-Consent C39 ND ND O C40 ND ND ND 38 User-Agent O

36、 - O O O - O O 38A User-to-User C41 ND ND O C41 ND ND ND 39 Via M M M M M M M M 40 Warning O O O ND O O O 41 WWW-Authenticate ND - O O ND - O O ATIS-0500024 9 3GPP Comments (See Reference 1 for the clarification of these comments) c1: IF A.4/12 THEN m ELSE n/a - - downloading of alerting information

37、. c2: IF A.4/22 THEN m ELSE n/a - - acting as the notifier of event information. c3: IF A.4/7 THEN m ELSE n/a - - authentication between UA and UA. c4: IF A.4/11 THEN o ELSE n/a - - insertion of date in requests and responses. c5: IF A.3/1 AND A.4/25 THEN o ELSE n/a - - UE and private extensions to

38、the Session Initiation Protocol (SIP) for asserted identity within trusted networks. c6: IF A.4/8A THEN m ELSE n/a - - authentication between UA and proxy. c7: IF A.4/25 THEN o ELSE n/a - - private extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks. c8:

39、 IF A.4/38 THEN o ELSE n/a - - the Reason header field for the session initiation protocol. c9: IF A.4/26 THEN o ELSE n/a - - a privacy mechanism for the Session Initiation Protocol (SIP). c10: IF A.4/6 THEN o ELSE n/a - - timestamping of requests. c11: IF A.4/19 THEN m ELSE n/a - - SIP extensions f

40、or media authorization. c12: IF A.3/1 AND A.4/19 THEN m ELSE n/a - - UE, SIP extensions for media authorization. c13: IF A.4/32 THEN o ELSE n/a - - the P-Called-Party-ID extension. c14: IF A.4/33 THEN o ELSE n/a - - the P-Visited-Network-ID extension. c15: IF A.4/34 THEN o ELSE n/a - - the P-Access-

41、Network-Info header extension. c16: IF A.4/34 AND A.3/1 THEN m ELSE n/a - - the P-Access-Network-Info header extension and UE. c17: IF A.4/34 AND (A.3/7A OR A.3/7D OR A3A/84) THEN m ELSE n/a - - the P-Access-Network-Info header extension and AS acting as terminating UA, AS acting as third-party call

42、 controller or EATF. c18: IF A.4/36 THEN o ELSE n/a - - the P-Charging-Vector header extension. c19: IF A.4/36 THEN m ELSE n/a - - the P-Charging-Vector header extension. c20: IF A.4/35 THEN o ELSE n/a - - the P-Charging-Function-Addresses header extension. c21: IF A.4/35 THEN m ELSE n/a - - the P-C

43、harging-Function-Addresses header extension. c22: IF A.4/37 OR A.4/37A THEN o ELSE n/a - - security mechanism agreement for the session initiation protocol or mediasec header field parameter for marking security mechanisms related to media (note 4). c23: IF A.4/37 OR A.4/37A THEN m ELSE n/a - - secu

44、rity mechanism agreement for the session initiation protocol or mediasec header field parameter for marking security mechanisms related to media. c24: IF A.4/40 THEN o ELSE n/a - - caller preferences for the session initiation protocol. c25: IF A.4/42 THEN m ELSE n/a - - the SIP session timer. c26:

45、IF A.4/42 THEN o ELSE n/a - - the SIP session timer. c27: IF A.4/43 THEN m ELSE n/a - - the SIP Referred-By mechanism. c28: IF A.4/43 THEN o ELSE n/a - - the SIP Referred-By mechanism. c29: IF A.4/44 THEN m ELSE n/a - - the Session Inititation Protocol (SIP) “Replaces“ header. c30: IF A.4/45 THEN m

46、ELSE n/a - - the Session Inititation Protocol (SIP) “Join“ header. c31: IF A.4/47 THEN m ELSE n/a - - an extension to the session initiation protocol for request history information. c32: IF A.4/40 THEN m ELSE n/a - - caller preferences for the session initiation protocol. c33: IF A.4/60 THEN m ELSE

47、 n/a - - SIP location conveyance. c34: IF A.4/66 THEN m ELSE n/a - - The SIP P-Early-Media private header extension for authorization of early media. c35: IF A.4/70 THEN m ELSE n/a - - communications resource priority for the session initiation protocol. c36: IF (A.3/1 OR A.3A/81) AND A.4/74 THEN o

48、ELSE n/a - - UE, MSC Server enhanced for ICS and SIP extension for the identification of services. c37: IF A.4/74 THEN o ELSE n/a - - SIP extension for the identification of services. c38: IF A.4/74 THEN m ELSE n/a - - SIP extension for the identification of services. c39: IF A.4/75A THEN m ELSE n/a

49、 - - a relay within the framework for consent-based communications in SIP. c40: IF A.4/75B THEN m ELSE n/a - - a recipient within the framework for consent-based communications in SIP. c41: IF A.4/76 THEN o ELSE n/a - - transporting user to user information for call centers using SIP. c42: IF A.4/77 THEN m ELSE n/a - - the SIP P-Private-Network-Indication private-header (P-Header). c43: IF A.4/80 THEN o ELSE n/a - - the P-Debug-ID header field for the session initiation protocol. c44: IF A.4/80 THEN m ELSE n/a - - the P-Debug-ID header field f