ETSI EG 201 992-2001 Services and Protocols for Advanced Networks (SPAN) Intelligent Networks (IN) Architectures and Signalling Requirements for IN-Based Networks Interworking with.pdf

1、ETSI EG 201 992 1.1.1 (2001-12) ETSI Guide Services and Protocols for Advanced Networks (SPAN); Intelligent Networks (IN); Architectures and signalling requirements for IN-based networks interworking with IP-based networks 2 ETSI EG 201 992 VI .I .I (2001-12) Reference DEGISPAN-I40304 Keywords IN, I

2、P, protocol, signalling ETSI 650 Route des Lucioles F-O6921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94 42 O0 Fax: +33 4 93 65 47 16 Siret No 348 623 562 00017 - NAF 742 C Association but non lucratif enregistre la Sous-prfecture de Grasse (06) No 7803/88 Important notice Individual copies of

3、the present document can be downloaded from: http:l/w.etsi .orq The present document may be made available in more than one electronic version or in print. In any case of existing or perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF).

4、In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive within ETSI Secretariat. Users of the present document should be aware that the document may be subject to revision or change of status. Information on the current status of t

5、his and other ETSI documents is available at 3 If you find errors in the present document, send your comment to: Cori vriaht Notifica tion No part may be reproduced except as authorized by written permission. The copyright and the foregoing restriction extend to reproduction in all media. O European

6、 Telecommunications Standards Institute 2001. All rights reserved. ETSI 3 ETSI EG 201 992 VI .I .I (2001-12) Contents Intellectual Property Rights . .5 Introduction . .5 Foreword . 5 1 2 3 3.1 3.2 4 4.1 4.2 5 5.1 5.2 5.3 5.3.1 5.3.2 5.3.3 5.3.4 5.3.5 5.3.6 5.4 5.4.1 5.4.2 5.4.3 5.4.4 5.4.5 5.5 5.5.1

7、 5.5.2 5.5.3 5.5.4 5.5.5 5.5.6 5.5.7 5.5.8 5.5.9 5.5.10 5.6 5.6.1 5.6.2 5.6.3 5.6.4 5.6.5 5.6.6 5.7 5.7.1 5.7.2 5.7.3 5.7.4 5.7.5 5.7.6 5.7.7 Scope 6 References . .6 Definitions and abbreviations. . .7 . 7 . 9 Services 11 . 11 . 11 Benchmark services . IN-Internet service examples. Functional archit

8、ecture .13 . . New functional entity requirements . . PINT server . . Service Application Gateway Function . . SPIRITS client . . . Extensions to existing functional entity re Specialized Resource Function (SRF) . Service Data Function (SDF) Service Switching Function ( Call Control Function (CCF) F

9、unctional interfaces . IF3: SCF to SRF interface IF4: SCF to SSF interfa IF6: SCF to SA-GF interface IF7: SA-GF to GF for distributed service logic platforms interface. IFS: SCF to SPIRITS client interface . IF9: SPIRITS client to SPIRITS proxy interface IF10: SPIRITS proxy to SPIRITS server interfa

10、ce . Lower layer protocol gateway and mapping functions . Service Control Gateway Function (SC-GF) Signalling Gateway Function (S-GF) . Dial Access Gateway Function (DA-GF) . Media Manager Gateway Function (MM-GF) Lower layer functional interfaces. 21 21 21 21 21 . .22 . . .22 . .22 23 23 . .24 . .2

11、4 . .24 25 25 25 . .25 25 25 25 IFa: SCF to SC-GF interface . IFb: SRF to SC-GF interface IFc: CCF to S-GF interface . IFd: SDF to DA-GF interface . IFe: CCF to MM-GF interface IFf CCF to DA-GF interface IFh: SRF to MM-GF interface ETSI 4 ETSI EG 201 992 VI .I .I (2001-12) 5.7.8 IFh: SC-GF to PINT s

12、erver interface . 26 . 26 5.7.10 IFJ: S-GF to CCF-CM interface .26 5.7.11 IFk: MM-GF to CCF-RM interface . 26 6 IN/IP Implementation Scenarios 26 IFi: SC-GF to SSF interface 5.7.9 6.1 6.1.1 6.1.2 6.1.3 6.1.4 6.1.5 6.1.5.1 6.1.5.2 6.1.5.3 6.2 6.2.1 6.2.2 6.2.3 6.2.4 6.2.4.1 6.2.4.2 6.3 6.4 6.5 6.6 6.

13、7 7 7.1 7.2 7.3 7.4 7.5 7.6 7.6.1 7.6.2 7.7 7.7.1 7.7.2 7.7.3 7.8 7.8.1 7.8.2 7.8.3 8 8.1 8.2 8.3 8.3.1 8.4 NIP interworking for IN CS-3 to support SIP systems . The SIP architecture . SIP Call call models Functional niodel . Requirements for IN-interaction with S . ms . SIP assumptions architecture

14、 and implementation issues. . IN-SIP interaction Basic concept of the p Assumptions IN/IP interworking for IN CS-3 to support H.323 systems . . Functional niodel supporting the H.323 GRC model . Void . . Requirements for IN CS-3 H.323 system Call control Architecture and assuniptions for IN CS-3 int

15、eraction with H.323 call contro H.323/SIP differences and implementation issues . . IN/IP interworking for IN CS-3 to support PINT based services . INAP interworking for IN CS-3 to support SPIRITS based implementa IN/IP interworking for IN CS-3 to support distributed service logic servers via an API

16、 . 43 IN/IP interworking to support IN CS-3 signalling transport functionality ISDN/IP interworking to support signalling transport functionality Signalling Requirements . .48 .37 s . 40 . .46 . .47 Introduction . . IN based service for dial-up internet access Information flow for Click-To-Dial (CTD

17、) . . Information flow for Click-To-Fax (CTF) service Information flow for Internet Call Waiting (ICW) service Example information flows of in-ip telephony interworking Information flow for H.323 terminal originated number translation service . Information flow for GW Initiated number translated ser

18、vice . IN interaction with SIP call control message flows . Proposed registration process tion . Terminating call with Core INAP interaction. . NH.323 interaction Message Flows Registration Originating call requiring Core INAP interaction Terminating call requiring Core INAP interaction Originating

19、call with Core . 57 . 60 Security aspects 6 1 61 61 61 61 Core INAP SCF to SSF interface 62 Introduction . . Requirements on the INLP interface Requirements on the IN domain Requirements on the IP Doma in . . . . Annex A (informative): Bibliography . 63 History 64 ETSI 5 ETSI EG 201 992 VI .I .I (20

20、01-12) Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared to ETSI. The information pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found in ETSI SR O00 314: “Intellectual P

21、roperty Rights (7PRs); Essential, orpotentially Essential, IPRs notlJied to ETSI in respect ofETSI standards“, which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web server (5). Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been ca

22、rried out by ETSI. No guarantee can be given as to the existence of other IPRs not referenced in ETSI SR O00 3 14 (or the updates on the ETSI Web server) which are, or may be, or may become, essential to the present document. Foreword This ETSI Guide (EG) has been produced by ETSI Technical Committe

23、e Services and Protocols for Advanced Networks (SPAN). I n t rod uct ion The present document is closely aligned with ITU-T Recommendation Q.1244 19, such that clauses 5 and 7 are similar in technical content with the related parts of the ITU-T Recommendation. Clause 6 whilst aligned with ITU-T Reco

24、mmendation Q. 1244 19 provides more detail in the figures and tables describing the relationship of the reference scenarios with the lower layer transport protocols. The intention of the present document is to define a set of enhancements for IN CS-3 for intenvorking with IP-networks, which comprise

25、s IN CS-4 in the ITU-T. In ETSI these enhancements will be considered as a revision of ETSI Core INAP. ETSI 6 ETSI EG 201 992 VI .I .I (2001-12) 1 Scope The present document describes the standardization of functions to allow intenvorking between Intelligent Networks and IP-networks for IN CS-3. The

26、se functions include: - - Signalling Requirements for interworking between functional entities in the IN and IP-networks; Signalling Requirements to support benchmark capabilities between functional entities in the IN and IP-networks; - Architecture supporting the transport of higher layer session m

27、ultimedia protocols between IP-network and the Circuit Switched Network; - Intenvorking and addressing of service control functions and service control gateway functionality across IN and IP-network boundaries; - Study of the security aspects. The present document only considers scenarios for intenv

28、orking IN CS-3 capabilities and IP-based networks. Service and network integration is outside the scope of the present document. The management functional entity requirements and interfaces are outside the scope of the present document. 2 Re fe re nces The following documents contain provisions whic

29、h, through reference in this text, constitute provisions of the present document. References are either specific (identified by date of publication andor edition number or version number) or non-specific. For a specific reference, subsequent revisions do not apply. For a non-specific reference, the

30、latest version applies. il Void. 21 Void. 31 Void. 41 ITU-T Recommendation Q. 1224: “Distributed functional plane for intelligent network Capability Set 2“. 51 61 ITU-T Recommendation Q. 123 1 : “Introduction to Intelligent Network Capability Set 3“ ITU-T Recommendation H.225.0: “Call signalling pro

31、tocols and media stream packetization for packet-based multimedia communication systems“. ITU-T Recommendation H.245: “Control protocol for multimedia communication“. ITU-T Recommendation H.246: “Interworking of H-Series multimedia terminals with H-Series multimedia terminals and voice/voiceband ter

32、minals on GSTN and ISDN“. 71 SI 91 lo1 ITU-T Recommendation H.248: “Gateway control protocol“. ITU-T Recommendation H.323 : “Packet-based multimedia communications systems“. 111 121 IETF RFC 2543 (1999): “SIP: Session Initiation Protocol“ IETF RFC 2458 (1998): “Toward the PSTNAnternet Inter-Networki

33、ng - Pre-PINT Implementations“. ETSI 7 ETSI EG 201 992 VI .I .I (2001-12) i31 IETF RFC 2848 (2000): “The Pint Service Protocol: Extensions to SIP and SDP for IP Access to Telephone Call Services“. IETF RFC 3 136 (2001): “The SPIRITS Architecture“. ETSI TR 123 821: “Technical Specification Group Serv

34、ices and System Aspects; Architecture Principles for Release 2000“. i41 i51 161 i71 I81 IETF RFC 791 (1981): “Internet Protocol“ IETF RFC 3015 (2000): “Megaco Protocol Version 1.0“. ETSI ES 201 915 (Vl.l.1) Parts 1 to 12: “Open Service Access; Application Programming Interface“. i91 ITU-T Recommenda

35、tion Q. 1244: “Distributed functional plane for Intelligent Network Capability Set 4“. 3 3.1 Definitions and abbreviations De fi nit ions For the purposes of the present document, the following terms and definitions apply: call: point-to-point multimedia communication between two H.323 endpoints NOT

36、E: The call begins with the call set-up procedure and ends with the call termination procedure. The call consists of the collection of reliable and unreliable channels between the endpoints. A call may be directly between two endpoints, or may include other H.323 entities such as a Gatekeeper or MG.

37、 In case of interworking with some CSN endpoints via a Gateway, all the channels terminate at the Gateway where they are converted to the appropriate representation for the CSN end system. Typically, a call is between two users for the purpose of communication, but may include signalling-only calls.

38、 An endpoint may be capable of supporting multiple simultaneous calls. call signalling channel: reliable channel used to convey the call set-up and teardown messages (see ITU-T Recommendation H.225.0) between two H.323 entities composite gateway: logical entity composed of a single MGC and one or mo

39、re MGs that may be reside on different machines NOTE: Together, they preserve the behaviour of a gateway as defined in ITU-T Recommendations H.323 lo and H.246 SI. GateKeeper (GK): H.323 entity on the network that provides address translation and controls access to the network for H.323 terminals, G

40、ateways and MCUs NOTE: The Gatekeeper may also provide other services to the terminals, Gateways and MCUs such as bandwidth management and locating Gateways. Gateway (GW): an H.323 Gateway (GW) is an endpoint on the network which provides for real-time, two-way communications between H.323 Terminals

41、 on the packet based network and other ITU Terminals on a switched circuit network, or to another H.323 Gateway NOTE: Other ITU-T terminals include those complying with Recommendations H.3 10 (H.320 on B-ISDN), H.320 (ISDN), H.321 (ATM), H.322 (GQOS-LAN), H.324 (GSTN), H.324M (Mobile), and V.70 (DSV

42、D). ETSI 8 ETSI EG 201 992 VI .I .I (2001-12) H.248: describes a control model and protocol for an MGC to control an MG NOTE: An MGC-MG association reserves the behaviour of a H.323 gateway. H.248 has been developed in ITU-T SG16, in co-operation with IETF MEGACO, with the intention of providing a s

43、ingle, international standard for Media Gateway Control. H.323 Entity: any H.323 component, including terminals, Gateways, Gatekeepers, MGCs and MGs H.323 Sewice Control Protocol: specifies protocol for multimedia communications over packet networks to be used between gatekeepers NOTE: This is work

44、under study in SG16, intended to enhance service related information transfer to and from the gatekeeper, which is currently limited to RAS. This work is expected to be strongly influenced by the IN-IPT intenvorking model and the joint work of SG16/SGll in general. IP-address: 32-bit address defined

45、 by the Internet Protocol in IETF RFC 791 NOTE: It is usually represented in dotted decimal notation. IP-network general term denoting networks based on the Internet Protocol (IP) suite NOTE: A network which uses IP as the Layer 3 protocol. JAVA: software platform trademark of Sun Microsystems Media

46、 Gateway (MG): converts media provided in one type of network to the format required in another type of network NOTE: For example, an MG could terminate bearer channels from a switched circuit network (i.e. DSOs) and media streams from a packet network (e.g., RTP streams in an IP-network). This gate

47、way may be capable of processing audio, video and T. 120 alone or in any combination, and will be capable of full duplex media translations. The MG may also play audiohide0 messages and perform other IVR functions, or may perform media conferencing. Media Gateway Controller (MGC): controls the parts

48、 of the call state that pertain to connection control for media channels in a MG proxy, proxy sewer: intermediary program that acts as both a server and a client for the purpose of making requests on behalf of other clients NOTE: Requests are serviced internally or by passing them on, possibly after

49、 translation, to other servers. A proxy interprets, and, if necessary, rewrites a request message before forwarding it, see i i. This functional element is functionally similar to the user agent server. In essence the proxy server is comprised of both a SIP client and a SIP server. RAS (Reservation, Admission and Status): the RAS signalling function uses H.225.0 messages to perform registration, admissions, bandwidth changes, status, and disengage procedures between endpoints and Gatekeepers NOTE: For details refer to ITU-T Recommendations H.323 lo and H.