ATIS 1000050-2012 Next Generation Network (NGN) Operator Regular Intercept Standard.pdf

《ATIS 1000050-2012 Next Generation Network (NGN) Operator Regular Intercept Standard.pdf》由会员分享，可在线阅读，更多相关《ATIS 1000050-2012 Next Generation Network (NGN) Operator Regular Intercept Standard.pdf（23页珍藏版）》请在麦多课文档分享上搜索。

1、 AMERICAN NATIONAL STANDARD FOR TELECOMMUNICATIONS ATIS-1000050.2012 NEXT GENERATION NETWORK (NGN) OPERATOR REGULAR INTERCEPT STANDARD As a leading technology and solutions development organization, ATIS brings together the top global ICT companies to advance the industrys most-pressing business pri

2、orities. Through ATIS committees and forums, nearly 200 companies address cloud services, device solutions, M2M communications, cyber security, ehealth, network evolution, quality of service, billing support, operations, and more. These priorities follow a fast-track development lifecyclefrom design

3、 and innovation through solutions that include standards, 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 Generatio

4、n Partnership Project (3GPP), a founding Partner of oneM2M, 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 . AMERICAN NAT

5、IONAL STANDARD Approval of an American National Standard requires review by ANSI that the requirements for due process, consensus, and other criteria for approval have been met by the standards developer. Consensus is established when, in the judgment of the ANSI Board of Standards Review, substanti

6、al agreement has been reached by directly and materially affected interests. Substantial agreement means much more than a simple majority, but not necessarily unanimity. Consensus requires that all views and objections be considered, and that a concerted effort be made towards their resolution. The

7、use of American National Standards is completely voluntary; their existence does not in any respect preclude anyone, whether he has approved the standards or not, from manufacturing, marketing, purchasing, or using products, processes, or procedures not conforming to the standards. The American Nati

8、onal Standards Institute does not develop standards and will in no circumstances give an interpretation of any American National Standard. Moreover, no person shall have the right or authority to issue an interpretation of an American National Standard in the name of the American National Standards

9、Institute. Requests for interpretations should be addressed to the secretariat or sponsor whose name appears on the title page of this standard. CAUTION NOTICE: This American National Standard may be revised or withdrawn at any time. The procedures of the American National Standards Institute requir

10、e that action be taken periodically to reaffirm, revise, or withdraw this standard. Purchasers of American National Standards may receive current information on all standards by calling or writing the American National Standards Institute. Notice of Disclaimer the information and parameters required

11、 for this service are only available either within a trust domain or between trusted domains. In addition, in the absence of trust, and depending on exactly which information is not trusted, basic call setup may not function as expected. 3 Normative References The following standards contain provisi

12、ons which, through reference in this text, constitute provisions of this Standard. At the time of publication, the editions indicated were valid. All standards are subject to revision, and parties to agreements based on this Standard are encouraged to investigate the possibility of applying the most

13、 recent editions of the standards indicated below. ATIS-1000009 ATIS-1000009.2006 (R2011), IP Network-to-Network Interface (NNI) Standard for VoIP.11This document is available from the Alliance for Telecommunications Industry Solutions (ATIS), 1200 G Street N.W., Suite 500, Washington, DC 20005. ATI

14、S-0100050.2012 2 ATIS-10000036 ATIS-1000036, Technical Report on NGN Operator Services.1ATIS-1000018 ATIS-1000018, Technical Report on NGN Architecture.1ATIS-1000027 ATIS-1000027, Operator Services Technical Report.1ATIS-1000666 ATIS-1000666.1999 (R2009), Signalling System No. 7 Operator Services Ne

15、twork Capabilities.1 4 Definitions the mechanism for deriving the appropriate referral address is outside the scope of this document. Once the desired destination address has been derived, the options for follow-on services (e.g., Call Completion) are similar to the Simple Announcement use cases. 6.

16、2.2 Interaction Provided by NGN Operator Intercept Service AS As with the simple announcement case, there are no signaling requirements specific to NGN Operator Regular Intercept service delivering the initial call/session setup to a number subject to Regular Intercept service. Normal call/session s

17、etup procedures set up a call path to the AS associated with the called number. This may be the Called AS (i.e., the AS associated with the number before Regular Intercept service was activated), or may be the Regular Intercept AS (i.e., an AS that provides Regular Intercept processing). In the form

18、er case, the service will redirect the call/session setup to an AS that will play any necessary announcements, interact with the calling party to obtain the information needed to derive the referral number, or offer additional services. The Regular Intercept AS may be in the same network as the Inte

19、rcepted Number AS (and, therefore, in the same network as the Called AS) or may be in a different network. Annex A contains illustrative examples of the messaging to set up the call using SIP Redirection (section A.2) and using Call Forwarding (section A.3) for the use case where the Intercepted Num

20、ber AS and the AS that provides Regular Intercept processing are in different networks. 7 Security Considerations The information and parameters required for this service are only available within a trust domain or between trusted domains as defined by the network operators. In addition, in the abse

21、nce of trust, and depending on exactly which information is not trusted, basic call setup may not function as expected. ATIS-0100050.2012 8 Annex A (informative) A Detailed Example Service Call Flows A.1. Simple Announcement UE P-CSCF Home Intercepted # Intercepted # Intercepted # Intercepted #S-CSC

22、F IBCF S-CSCF AS MS| |(1) INVITE| |-(2) INVITE| |-| | | | | | |(3) INVITE | | | | | |-| | | | | | |(4) INVITE | | | | | |-| | | | | | |(5) INVITE | | | | | | | | | | | |-| | | | | | |-|(5a) MS Signalig | | | | | | | | | | | | | | | | (6) 183 Session Progress | | | | | | P-CSCF INVITE sip:+1-NPA-NXX-

23、DIALprovider-; user=phone SIP/2.0 Via: SIP/2.0/UDP sip:client.provider-:5060;branch=z9hG4bK74bf9 Max-Forwards: 70 From: ;tag=1234567 To: CSeq: 101 INVITE Call-ID: f81d4fae-7dec-11d0-a765-00a0c91e6bf6192.168.1.2 Contact: P-Preferred-Identity: Content-Type: application/sdp Content-Length: . ATIS-01000

24、50.2012 9 This INVITE is generated by the UE, and sent to the P-CSCF. It contains: a. Request-URI indicates the user to which this request is being addressed. In this example, the Request-URI contains a “SIP” URI indicating the digits “1+NPA-NXX-DIAL” as dialed by the user. The domain identifies the

25、 callers home provider, and the “user=phone” URI parameter is provided to identify that this represents a phone number. b. Via The Via header field indicates the path taken by the request so far and indicates the path that should be followed in routing responses. The branch ID parameter in the Via h

26、eader field serves as a transaction identifier, and is used by proxies to detect loops. c. Max-Forwards The Max-Forwards header field serves to limit the number of hops a request can transit on the way to its destination. It consists of an integer that is decremented by one at each hop. If the Max-F

27、orwards value reaches 0 before the request reaches its destination, it will be rejected with a 483 (Too Many Hops) error response. The default initial value is 70 per RFC 3261. d. From The From header field indicates the logical identity of the initiator of the request, possibly the users address-of

28、-record. Like the To header field, it contains a URI and optionally a display name. The contents of the From header being generated by the UE are not trusted; rather, the network asserted identity in the P-Asserted-Identity header is trusted. e. To The To header field first and foremost specifies th

29、e desired “logical“ recipient of the request, or the address-of-record of the user or resource that is the target of this request. This may or may not be the ultimate recipient of the request. f. CSeq The CSeq header field serves as a way to identify and order transactions. It consists of a sequence

30、 number and a method. g. Call-ID The Call-ID header field acts as a unique identifier to group together a series of messages. h. Contact The Contact header field provides a SIP or SIPS URI that can be used to contact that specific instance of the UA for subsequent requests. In this example, the UE s

31、upplies the Address of Record that was used at registration. i. Content-Type The Content-Type header field indicates the media type of the message-body sent to the recipient. The “media-type“ element is defined in RFC 2046, Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types. At a min

32、imum, application/sdp will be indicated. j. Content-Length The Content-Length header field indicates the size of the message-body, in decimal number of octets, sent to the recipient. k. Session Description The INVITE contains a message body including a Session Description (SDP) offer per RFC 2327, S

33、DP: Session Description Protocol. l. Other headers and message bodies may potentially be present, but are not included here. 2. INVITE P-CSCF- Home S-CSCF INVITE sip:+1-NPA-NXX-DIALprovider-; user=phone SIP/2.0 Via: SIP/2.0/UDP p-cscf-1.provider-:5060;branch=z9hG4bK74bg0 Via: SIP/2.0/UDP client.prov

34、ider-:5060;branch=z9hG4bK74bf9 Max-Forwards: 69 Record-Route: From: ;tag=1234567 ATIS-0100050.2012 10 To: CSeq: 101 INVITE Call-ID: f81d4fae-7dec-11d0-a765-00a0c91e6bf6192.168.1.2 Contact: P-Asserted-Identity: “+1NPA-NXX-ORIG“ P-Charging-Vector: icid-value=1234bc9876e; icid-generated-at=192.0.6.8; o

35、rig-ioi=provider- Content-Type: application/sdp Content-Length: . In addition to information received from the user, the P-CSCF adds the P-Asserted-Identity header. It also adds the P-Charging-Vector header which provides correlation information. The P-CSCF also adds to the Via header and adds a Rec

36、ord-Route header, which are of no special consequence to Operator Services. It also decrements the Max-Forwards value. Therefore, this INVITE has changed: a. Via The P-CSCF adds a Via header identifying itself to the top of the Via header stack. b. Max-Forwards The P-CSCF decrements the value by one

37、. c. Record-Route The P-CSCF inserts itself into the Record-Route header. d. P-Asserted-Identity The P-Asserted-Identity header field is used among trusted SIP entities (typically intermediaries) to carry the identity of the user sending a SIP message as it was verified by authentication. The P-CSCF

38、 inserts the P-Asserted-Identity header field, in this example, asserting the identity received in the P-Preferred-Identity. e. P-Preferred-Identity The P-CSCF deletes the P-Preferred Identity f. P-Charging-Vector This is defined in RFC 3455, Private Extensions to the Session Initiation Protocol (SI

39、P) for the 3rd-Generation Partnership Project (3GPP). It provides correlation information for charging purposes. It contains a globally-unique IMS Charging Identity (icid). The orig-ioi represents the IMS Inter Operator Identifier for the home provider. The P-CSCF inserts the P-Charging-Vector. 3. I

40、NVITE Home S-CSCF- Intercepted Number IBCF INVITE sip:+1-NPA-NXX-DIALprovider-; user=phone SIP/2.0 Via: SIP/2.0/UDP s-cscf-1.provider-:5060;branch=z9hG4bK74bh1 Via: SIP/2.0/UDP p-cscf-1.provider-:5060;branch= z9hG4bK74bg0 Via: SIP/2.0/UDP client.provider-:5060;branch=z9hG4bK74bf9 Max-Forwards: 68 Re

41、cord-Route: Record-Route: From: ; tag=1234567 To: CSeq: 101 INVITE Call-ID: f81d4fae-7dec-11d0-a765-00a0c91e6bf6192.168.1.2 ATIS-0100050.2012 11 Contact: P-Asserted-Identity: “+1NPA-NXX-ORIG“ P-Charging-Vector: icid-value=1234bc9876e; icid-generated-at=192.0.6.8; orig-ioi=provider- Content-Type: app

42、lication/sdp Content-Length: . The S-CSCF determines the home provider of the called party, changes the domain in the Request-URI accordingly, and routes the INVITE to the ingress node of this domain. It also adds to the Via header and adds a Record-Route header, which are of no special consequence

43、to Operator Services. It also decrements the Max-Forwards value. Therefore, this INVITE has changed: 1. Request-URI The S-CSCF replaces the domain with the home domain of called party. 2. Via The S-CSCF adds a Via header identifying itself to the top of the Via header stack. 3. Max-Forwards The S-CS

44、CF decrements the value by one. 4. Record-Route The S-CSCF inserts itself into the Record-Route header. There may be separate IBCFs in each (provider-a and provider-b) network. 4. INVITE Intercepted Number IBCF - Intercepted Number S-CSCF INVITE sip:+1-NPA-NXX-DIALprovider-; user=phone SIP/2.0 Via:

45、SIP/2.0/UDP ibcf-1.provider-:5060;branch=z9hG4bK74bi2 Via: SIP/2.0/UDP s-cscf-1.provider-:5060;branch=z9hG4bK74bh1 Via: SIP/2.0/UDP p-cscf-1.provider-:5060;branch= z9hG4bK74bg0 Via: SIP/2.0/UDP client.provider-:5060;branch=z9hG4bK74bf9 Max-Forwards: 67 Record-Route: Record-Route: Record-Route: From:

46、 ;tag=1234567 To: CSeq: 101 INVITE Call-ID: f81d4fae-7dec-11d0-a765-00a0c91e6bf6192.168.1.2 Contact: P-Asserted-Identity: “+1NPA-NXX-ORIG“ P-Charging-Vector: icid-value=2345bc9876e; icid-generated-at=192.1.6.8; ATIS-0100050.2012 12 orig-ioi=provider- Content-Type: application/sdp Content-Length: . T

47、he ingress node routes the call to the S-CSCF. It also adds to the Via header and adds a Record-Route header, which are of no special consequence to Operator Services. It also decrements the Max-Forwards value. Therefore, this INVITE has changed: a. Via The IBCF adds a Via header identifying itself

48、to the top of the Via header stack. b. Max-Forwards The IBCF decrements the value. c. Record-Route The Record-Route header field is inserted by proxies in a request to force future requests in the dialog to be routed through the proxy. The IBCF inserts itself into the Record-Route header. d. P-Charg

49、ing-Vector A new P-Charging-Vector is generated for use in this domain. There may be separate IBCFs in each (provider-a and provider-b) network. Each IBCF makes similar changes to the INVITE. 5. INVITE Intercepted Number S-CSCF - Intercepted Number AS INVITE sip:+1-NPA-NXX-DIALprovider-; user=phone S