ITU-T Q 1244-2001 Distributed Functional Plane for Intelligent network Capability Set-4《IN CS-4分布功能平台》.pdf

《ITU-T Q 1244-2001 Distributed Functional Plane for Intelligent network Capability Set-4《IN CS-4分布功能平台》.pdf》由会员分享，可在线阅读，更多相关《ITU-T Q 1244-2001 Distributed Functional Plane for Intelligent network Capability Set-4《IN CS-4分布功能平台》.pdf（55页珍藏版）》请在麦多课文档分享上搜索。

1、INTERNATIONAL TELECOMMUNICATION UNIONITU-TQ.1244TELECOMMUNICATIONSTANDARDIZATION SECTOROF ITU(07/2001)SERIES Q: SWITCHING AND SIGNALLINGIntelligent NetworkDistributed functional plane for intelligentnetwork capability set-4CAUTION !PREPUBLISHED RECOMMENDATIONThis prepublication is an unedited versio

2、n of a recently approved Recommendation.It will be replaced by the published version after editing. Therefore, there will bedifferences between this prepublication and the published version.FOREWORDThe International Telecommunication Union (ITU) is the United Nations specialized agency in the field

3、oftelecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ ofITU. ITU-T is responsible for studying technical, operating and tariff questions and issuingRecommendations on them with a view to standardizing telecommunications on a worldwide basis.The World Tel

4、ecommunication Standardization Assembly (WTSA), which meets every four years,establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations onthese topics.The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1.In some area

5、s of information technology which fall within ITU-Ts purview, the necessary standards areprepared on a collaborative basis with ISO and IEC.NOTEIn this Recommendation, the expression “Administration“ is used for conciseness to indicate both atelecommunication administration and a recognized operatin

6、g agency.INTELLECTUAL PROPERTY RIGHTSITU draws attention to the possibility that the practice or implementation of this Recommendation mayinvolve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence,validity or applicability of claimed Intellectual Property

7、 Rights, whether asserted by ITU members or othersoutside of the Recommendation development process.As of the date of approval of this Recommendation, ITU had/had not received notice of intellectualproperty, protected by patents, which may be required to implement this Recommendation. However,implem

8、entors are cautioned that this may not represent the latest information and are therefore strongly urgedto consult the TSB patent database. ITU 2001All rights reserved. No part of this publication may be reproduced or utilized in any form or by any means,electronic or mechanical, including photocopy

9、ing and microfilm, without permission in writing from ITU.ITU-T Q.1244 (07/2001) Prepublished version 1ITU-T RECOMMENDATION Q.1244DISTRIBUTED FUNCTIONAL PLANE FOR INTELLIGENT NETWORK CAPABILITYSET-4SUMMARYIntelligent Network Capability Set-4 (IN CS-4) is the fourth standardized stage of the Intellig

10、ent Network (IN) as anarchitectural concept for the creation and provision of services, including telecommunication services, servicemanagement services and service creation services. This Recommendation gives the Distributed functional plane for INCS-4. It describes the main characteristics and ove

11、rall capabilities of IN CS-4 and defines the network aspects andfunctional relationships that form the basis of the IN CS-4 capabilities.This Recommendation is the second to be produced in the Q.124x series of Recommendations devoted to IN CS-4,which builds on the architectural principles of IN as d

12、escribed in the Q.121x, Q.122x and the Q.123x series ofRecommendations.The IN CS-4 Recommendations form a detailed and stable basis for implementing IN CS-4 telecommunication services.They also provide high level guidelines for supporting service management services, service creation services and so

13、mepartially supported telecommunication services. The IN CS-4 Recommendations are intended to give the same degree oftechnical information as the IN CS-3 Recommendations .1. IntroductionIntelligent Network Capability Set-4 (IN CS-4) is the fourth standardized stage of the Intelligent Network (IN) as

14、 anarchitectural concept for the creation and provision of network services, including telecommunication services, servicemanagement services and service creation services. This Recommendation gives the distributed functional plane for INCS-4. It describes the main characteristics and overall capabi

15、lities of the IN CS-4 functional architecture, networkaspects and functional relationships that form the basis for IN CS-4. Chapter 4 describes the generic functional model atthe control plane and illustrates how IN and IP may be seen to inter-work. Chapter 5 describes the relationships andinterface

16、s that are enhanced, when related to the previous IN Capability Sets. Chapter 6 illustrates a number ofimportant scenarios for inter-working and interoperability between IN and other networks not specified before in earlierIN Capability Sets. Annex B describes the relation between the generic contro

17、l plane functional architecture and otherallied functions that may be present in the underlying network.2. Phased StandardizationThe phased approach of IN Capability Sets has been described in ITU-T Recommendation Q.1201. IN CS4 extends theservice aspects, network aspects and management aspects of I

18、N CS-3 as specified in the Q.123x series ofRecommendations. Definition of IN CS-4 service features may be found in Recommendation Q.1241.3. References3.1 Normative referencesThe following ITU-T recommendations and other references contain provisions which, through reference in the text,constitute pr

19、ovision of this recommendation. At the time of publication, the editions indicated were valid. Allrecommendations and other references are subject to revisions; all users of this recommendation are thereforeencouraged to investigate the possibility of applying the most recent editions of the recomme

20、ndations and otherreferences listed below. A list of a currently valid ITU-T recommendations is regularly published.1 ITU-T Recommendation Q.1241 Introduction to Intelligent Network Capability Set-42 ITU-T Recommendation Q.1248 Interface Recommendation for Intelligent Network CS-43 ITU-T Recommendat

21、ion Q.1222 Service plane for intelligent network Capability Set 24 ITU-T Recommendation Q.1223 Global functional plane for intelligent network CapabilitySet 25 ITU-T Recommendation Q.1224 Distributed functional plane for intelligent networkCapability Set 2ITU-T Q.1244 (07/2001) Prepublished version

22、26 ITU-T Recommendation Q.1225 Physical plane for intelligent network Capability Set 27 ITU-T Recommendation Q.1228 Interface Recommendation for intelligent networkCapability Set 28 ITU-T Recommendation Q.1231 Introduction to intelligent network Capability Set 39 ITU-T Recommendation Q.1236 Intellig

23、ent Network Capability Set-3 ManagementInformation Model Requirements and Methodology10 ITU-T Recommendation Q.1237 Extensions to Intelligent Network Capability Set-3 insupport of B-ISDN11 ITU-T Recommendation Q.1238 Interface Recommendation for intelligent networkCapability Set 312 ITU-T Recommenda

24、tion Q.1290 Glossary of Terms Used in the Definition of IntelligentNetworks13 ITU-T Recommendation H.323 Packet Based Multimedia Communications Systems; ITU-T199814 ITU-T Recommendation H.248 Media Gateway Control Protocol; ITU-T 02/20003.2 BibliographyThe documents listed in this clause provide inf

25、ormative background information for the reader and are notnormative within this Recommendation.15 ETSI Standard ES 301 xyz “API for Open Service Access (OSA)” draft SPAN 12 ES12007016 IETF RFC 2543 (March 1999); Session Initiation Protocol; Schulzrinne, Handley, Schoolerand Rosenberg.17 IETF RFC 294

26、7 (October 2000); “The SIP INFO Method”; S. Donovan.18 draft-ietf-sip-rfc2543bis-01 (August 2000): “SIP: Session Initiation Protocol”.19 IETF RFC 2484, “The Pint Service Protocol: Extensions to SIP and SDP for IP Access toTelephone Call Services” (June 2000); S. Petrack and L. Conroy20 IETF RFC 2327

27、 (April 1998): “SDP: Session Description Protocol”; Schulzrinne, Handley,Schooler and Rosenberg.21 Charging for IN CS-3 draft ETSI Standard (SPAN-03wxyz version ).22 3GPP Technical Specification 29.198 Technical Specification Group Core Networks;Mapping of Virtual Home Environment / Open Service Arc

28、hitecture to CAP/INAP.23 3GPP Technical Specification 23.127 Technical Specification Group Services and SystemAspects; Virtual Home Environment / Open Service Architecture.24 ETSI Guide EG 201 xxx-1 “Requirements on an API for Open Service Access (OSA)”;draft ETSI Guide SPAN 141606 part 1 (release 1

29、999)ITU-T Q.1244 (07/2001) Prepublished version 325 ETSI Guide EG 201 xxx-2 “Requirements on an API for Open Service Access (OSA)”;draft ETSI Guide SPAN 141606 part 2 (release 2000)26 IETF Working Group draft “The SPIRITS Architecture” L. Slutsman, I. Faynberg H. Lu, M. Weissman4. Distributed functi

30、onal model for IN CS-4The functional model proposed is an extension of the IN CS-2 functional model (see Figure 4-1/Q.1244). It is intendedto support IN CS-4 benchmark services, Internet based service customisation and termination of Voice over IP to reachusers in the telephone domain as well as gen

31、eral IN capabilities.4.1 Functional Entities to Support IN CS-4 Benchmark FeaturesThe option to have minimal support for accessing IN from H.323 Gatekeepers and SIP/SDP proxy redirection serversfor implementing services that require explicit handling of the call configuration is agreed working assum

32、ption for INCS-4, considered below:For INAP CS-4 the following minimum capabilities are considered: redirection services, charging, the charging operations defined in ETSI 21 need to be restricted for H.323 and the exact definition ofthe control of the CDRs will be standardised. number translation s

33、ervices including the storage of related information (time of day) for e.g. portability and 800based services.Note: It is further required to define the service capabilities INAP provides to H.323 or SIP call control. And alsodefine the arming and configuration of Trigger conditions.Note: Triggering

34、 criteria can only be based on e.g. E.164 addresses in INAP CS-3 and therefore the limitation on thealias Address has to be indicated, or extension proposed.For the H.323 architecture the translation of alias addresses to IP transport addresses is to be performed by gatekeeper.The gatekeeper will al

35、so map the specific H.323 parameters to the INAP parameters. Mapping analysis is thereforerequested and specific information must be identified. It is proposed that the information should not be sent in acontainer e.g. Mapping of the cause values will be as specified in the H.225 Recommendation towa

36、rds the Q.850 causesvalues.The following lower layer protocol gateways, mapping functions may be required depending on the protocolArchitectures employed in each domain:- Signalling Gateway Function (S-GF)- Service Control Gateway Function (SC-GF)4.1.1 PINT ServerA PINT server accepts PINT requests

37、from PINT clients. It processes the requests and returns responses to the clients.A PINT server may perform these functions as a proxy server or a redirect server. A proxy server makes requests toanother PINT server on behalf of its clients; a redirect server returns to its clients addresses of othe

38、r PINT servers towhich requests can be redirected. The gateway capability includes the ability to communicate with a so-called ExecutiveSystem located outside the IP network domain that will actually perform the service call requested by a PINT Client.Additionally, this function transfers data (e.g.

39、 fax, data) between IP-networks and the IN, and associates IP-networkentities with the related entities in gateway function. This function is situated at the edge of the IP-network domain,where the Application Association with PINT Client/Server is subject of standardisation of the IETF and where th

40、eApplication Association with SCF in the IN domain is subject of standardisationThe functions related to PINT Server are:- In case the Executive System is an IN system, the PINT Server delivers received PINT requests to the SCF. Itprovides the SCF with the necessary information to control service re

41、quests, identify users and authenticate data,ITU-T Q.1244 (07/2001) Prepublished version 4and protect the IN from misuse or attacks from the IP-network. Furthermore, it hides the SCF/ SRF from entitiesin the IP-network domain and acts as a mediation device between the IP-network and the IN.- It also

42、 relays requests from an SCF to the IP-network domain to perform services (e.g. user notification).4.1.2 Service Application Gateway Function (SA-GF)The Service Application Gateway Function allows the inter-working:- between the service control layer in Intelligent and Distributed Service Logic appl

43、ications (API based functions).- between the Call Manager Function and Distributed Service Logic.Note: Inter-working of the CCF (representing specific functionality in a VoIP environment. e.g. SIP Proxy orGK) and the SA GF in the particular VoIP environment is not subject of IN CS-4 standardisation.

44、For IN CS-4, on the application level, the types of API based functionality may include:-CORBA platforms- JAVA platforms-JAIN platforms- Other API based platformsAdditionally this functionality may provide protocol mapping/service mediation.4.1.3 Call Control Function (CCF)CCF is an enhanced functio

45、nal entity, responsible for handling call signalling on either network. The CCFcommunicates with the SM using Registration and admission capabilities. To support ISUP signalling, the CCF has toimplement H.246 Annex C. In that case it appears to the IN side CCF as being another CCF. This functionalit

46、y includeshandling the management of the call processing, and call signalling.This entity is responsible for passing service related information to and from IN service layer, namely the SCF, andmanaging the service control relationship. As such, the CCF may contain a SSF-like functionality or subset

47、 thereof, tomodel the pre and post conditions that are required to interact with an SCF.A Call Control function could be seen as a logical switch (CCF). Call control signalling (e.g. H.225.0, Q.931-like) andconnection control signalling (H.245) for VoIP is transferred via the RM/MM, which make netwo

48、rk routing decisions.A Call Control Function can require SCF assistance for these routing decisions, e.g. for 1-800 numbers, numberportability, user profile consultation, VPN support.The functions related to Call Control Function are:- - Inter-working for:- Number Portability;- Freephone Translation

49、s;- VPN support;- O.A. possibly via the SC-GF if used.For example, for the Internet Call Waiting service, the SCF needs to notify the Internet user of an incoming call. Then,IF1 should allow the SCF to request Internet services.This interface will relay requests either from the IN or the IP-network. This interface is modelling the information relay,The information transfer on this interface is specified in the SIP Pint extensions in 19.The IETF PINT working group has developed a set of protocol extensions set based on the