ITU-T Q 1225-1997 Physical Plane for Intelligent Network Capability Set 2 - Series Q Switching and Signalling Intelligent Network (Study Group 11 16 pp)《IN CS-2物理平台》.pdf

《ITU-T Q 1225-1997 Physical Plane for Intelligent Network Capability Set 2 - Series Q Switching and Signalling Intelligent Network (Study Group 11 16 pp)《IN CS-2物理平台》.pdf》由会员分享，可在线阅读，更多相关《ITU-T Q 1225-1997 Physical Plane for Intelligent Network Capability Set 2 - Series Q Switching and Signalling Intelligent Network (Study Group 11 16 pp)《IN CS-2物理平台》.pdf（16页珍藏版）》请在麦多课文档分享上搜索。

1、INTERNATIONAL TELECOMMUNICATION UNION ITU=T TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU SERIES Q: SWITCHING AND SIGNALLING Intelligent Network Q.1225 (09197) Physical plane for Intelligent Network Capability Set 2 ITU-T Recommendation Q. 1225 (Previously CClTT Recommendation) - STDmITU-T RECMN Q

2、mL225-ENGL 1997 m 4862591 ObY338L 663 ITU-T Q-SERIES RECOMMENDATIONS SWITCHING AND SIGNALLING SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS SPECIF

3、ICATIONS OF SIGNALLING SYSTEMS No. 4 AND No. 5 SPECIFICATIONS OF SIGNALLING SYSTEM No. 6 SPECIFICATIONS OF SIGNALLING SYSTEM RI SPECIFICATIONS OF SIGNALLING SYSTEM R2 DIGITAL EXCHANGES INTERWORKING OF SIGNALLING SYSTEMS SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 DIGITAL SUBSCRIBER SIGNALLING SYSTEM N

4、o. 1 PUBLIC LAND MOBILE NETWORK INTERWORKING WITH SATELLITE MOBILE SYSTEMS lnterworking with Standard-A INMARSAT system lnterworking with Standard-B INMARSAT system lnterworking with the INMARSAT aeronautical mobile-satellite system Q.l-Q.3 Q.4-Q.59 Q.6O-Q.99 Q.100-Q.119 Q. 120-Q.249 Q.250-Q.309 (2.

5、31 04.399 Q.400-(2.499 Q.500-(2.599 Q.600-Q.699 Q.700-Q.849 Q.850-(2.999 Q. 1 0004.1 O99 Q.1100-Q.1199 Q.110O-Q.1109 Q.1110-(2.1149 Q.1150-(2.1199 For further details, please refer to TU-T List of Recommendations. STDmITU-T RECMN Q-1225-ENGL L997 m 4862591 Ob43382 5TT m ITU-T RECOMMENDATION 4.1225 P

6、HYSICAL PLANE FOR INTELLIGENT NETWORK CAPABILITY SET 2 Summary This Recommendation describes the physical plane of the Intelligent Network (IN) architecture for CS-2. The physical plane identifies different Physical Entities (PES), the allocation of functional entities to PES, and the interfaces bet

7、ween the PES. Companion Recommendations include the Q. 120x- and Q. 122x-Series Recommendations. Source 1TU-T Recommendation Q. 1225 was prepared by ITU-T Study Group 1 1 (1997-2000) and was approved under the WTSC Resolution No. 1 procedure on the 12th of September 1997. STDaITU-T RECMN Q.1225-ENGL

8、 1997 m 4862593 Ob43383 436 m FOREWORD ITU (International Telecommunication Union) is the United Nations Specialized Agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of the ITU. The ITU-T is responsible for studying technical, o

9、perating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. The World Telecommunication Standardization Conference (WTSC), which meets every four years, establishes the topics for study by the ITU-T Study Groups which, in th

10、eir turn, produce Recommendations on these topics. The approval of Recommendations by the Members of the ITU-T is covered by the procedure laid down in WTSC Resolution No. l. In some areas of information technology which fall within ITU-Ts purview, the necessary standards are prepared on a collabora

11、tive basis with IS0 and IEC. NOTE In this Recommendation, the expression “Administration” is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. INTELLECTUAL PROPERTY RIGHTS The ITU draws attention to the possibility that the practice or implem

12、entation of this Recommendation may involve the use of a claimed Intellectual Property Right. The ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development proc

13、ess. As of the date of approval of this Recommendation, the ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore str

14、ongly urged to consult the TSB patent database. O ITU 1998 All rights reserved. No part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from the ITU. 11 Recommendation 4.1225

15、(09/97) CONTENTS 1 2 2.1 2.2 3 4 5 5.1 5.2 5.3 General . Requirements and assumptions Requirements Assumptions . Physical Entities (PES) . Mapping requirements Mapping the distributed functional plane to the physical plane . Mapping of functional entities to physical entities . Mapping of FE-FE rela

16、tionships to PE-PE relationships . Selection of underlying protocol platforms 5.3.1 SCP-SSP interface . 5.3.2 AD-S SP interface 5.3.3 IP-SSP interface 5.3.4 SN-SSP interface . 5.3.5 SCP-IP interface 5.3.6 AD-IP interface . 5.3.7 SCP-SDP interface 5.3.8 User interfaces 5.3.9 Enhanced ISDN CPE-CUSP in

17、terface 5.3.1 O AD-CUSP interface . Page 1 2 2 3 3 5 5 5 6 7 7 8 8 8 8 8 8 8 9 10 Recommendation Q.1225 (09/97) . 111 STD-ITU-T RECMN Q=L225-ENGL L997 0 48b2591 Ob43385 209 Recommendation 4.1225 PHYSICAL PLANE FOR INTELLIGENT NETWORK CAPABILITY SET 2 (Geneva, I99 7) 1 General This Recommendation des

18、cribes the physical plane of the Intelligent Network (IN) architecture for CS-2. General IN physical plane information is contained in Recommendation 4.1205. The physical plane of the IN conceptual model identifies the different physical entities and the interfaces between these entities. The physic

19、al plane architecture should be consistent with the IN conceptual model. The IN conceptual model is a tool that can be used to design the IN architecture to meet the following main objectives: I - service implementation independence; - network implementation independence; - vendor and technology ind

20、ependence. The I. 130 stage 3 service description methodology may be used (which includes the functional specification of the node and detailed description of the protocol between the nodes) in developing the physical plane architecture. The following is the list of abbreviations used in this Recomm

21、endation: AD BRI CCAF CCF CS CUSF DSS NAP IP ISDN ISDN-CPE ISUP NAP NCP N-ISDN PBX PRI Adjunct Basic Rate Interface Call Control Agent Function Call Control Function Capability Set Call-Unrelated Service Function Digital Signalling System Intelligent Network Application Protocol Intelligent Peripher

22、al Integrated Services Digital Network ISDN Customer Premises Equipment ISDN User Part (Protocol) Network Access Point Network Control Point Narrow-band Integrated Services Digital Networks Private Branch Exchange (ISDN) Primary Rate Interface Recommendation 4.1225 (09/97) 1 SCCP SCEF SCF SCP SCUAF

23、SDF SDP SMF SMP SN SRF SS No. 7 SSCP SSF SSP TMN Signalling Connection Control Part Service Creation Environment Function Service Control Function Service Control Point Service Control User Agent Function Service Data Function Service Data Point Service Management Function Service Management Point S

24、ervice Node Specialized Resource Function Signalling System No. 7 Service Switching and Control Point Service Switching Function Service Switching Point Telecommunications Management Network 2 Requirements and assumptions 2.1 Requirements The key requirements of the physical plane architecture are a

25、s follows: - the functional entities in the CS-2 distributed functional plane can be mapped onto the CS-2 physical entities; however, there is no present need to describe (or map to Physical Plane) the IN Management aspects; - one or more functional entities may be mapped onto the same physical enti

26、ty; - one functional entity cannot be split between two physical entities (i.e. the functional entity - duplicate instances of a functional entity can be mapped to different physical entities, though - physical entities can be grouped to form a physical architecture; - the physical entities may offe

27、r standard interfaces; - vendors must be able to develop physical entities based on the mapping of functional entities - vendors must be able to support mature technologies and new technologies as they become - the Telecommunications Management Network (TMN) represents the system or systems is mappe

28、d entirely within a single physical entity); not to the same physical entity; and the standard interfaces; available; and associated with management of IN. As such, it is not restrained to any single physical implementation but may be implemented by distributing its functionality to one or more phys

29、ical entities. This requirement is reflected in Figure 1/Q.1215 by means of the “TMN Cloud“. 2 Recommendation Q.1225 (09/97) STD-ITU-T RECMN Q-LZ25-ENGL L997 m 48b2.591 Ob43387 081 m 2.2 Assumptions The following assumptions are made for the development of the physical plane architecture: - The IN c

30、onceptual model is used as a tool to develop the IN physical architecture. - Existing and new technologies can be used to develop the physical entities. - The specification of functional entities in the distributed functional plane and standard interfaces in the physical plane support network vendor

31、 independence and service independence. creation and OAM functions are not addressed. - For CS-2, a sufficient number of interfaces are identified for support of services. Service 3 Physical Entities (PES) This clause describes a selection of PES to support IN CS-2. That selection is not intended to

32、 preclude or disallow the application of any other IN PE to support CS-2. Service Switching Point (SSP) In addition to providing users with access to the network (if the SSP is a local exchange) and performing any necessary switching functionality, the SSP allows access to the set of IN capabilities

33、. The SSP contains detection capability to detect requests for IN-based services. It also contains capabilities to communicate with other PE(s) containing a Service Control Function (SCF), such as a Service Control Point (SCP), and to respond to instructions fiom the other PE. Functionally, an SSP c

34、ontains a Call Control Function (CCF), a Service Switching Function (SSF), and, if the SSP is a local exchange, a Call Control Agent Function (CCAF). It also may optionally contain a Service Control Function (SCF), and/or a Specialized Resource Function (SRF), andor a Service Data Function (SDF). Th

35、e SSP may provide IN-based services to users connected to subtending Network Access Points. Network Access Point (NAP) A NAP is a PE that includes only the CCAF and CCF functional entities. It may also be present in the network. The NAP supports early and ubiquitous deployment of IN-based services.

36、This NAP cannot communicate with an SCF, but it has the ability to determine when IN processing is required. It must send calls requiring IN processing to an SSP. Service Control Point (SCP) The SCP contains the Service Logic Programs (SLPs) and data that are used to provide IN-based services. The S

37、CP is connected to SSPs by a signalling network. Multiple SCPs may contain the same SLPs and data to improve service reliability and to facilitate load sharing between SCPs. Functionally, an SCP contains an SCF and it may contain an SDF. The SCP can access data in an SDP either directly or through a

38、 signalling network. The SDP may be in the same network as the SCP, or in another network. The SCP can be connected to SSPs, and optionally to IPS, through the signalling network. The SCP can also be connected to an IP via an SSP relay function. Adjunct (AD) The AD is functionally equivalent to an S

39、CP (i.e. it contains the same functional entities) but it is directly connected to an SSP. Communication between an AD and an SSP is supported by a high-speed interface. This arrangement may result in differing performance characteristics for an AD and an SCP. The application layer messages are iden

40、tical in content to those carried by the signalling network to an SCP. Recommendation 4.1225 (09/97) 3 An AD may be connected to more than one SSP and an SSP may be connected to more than one Adjunct. e) Intelligent Peripheral (IP) The IP provides resources such as customized and concatenated voice

41、announcements, voice recognition, and Dual Tone Multi-Frequencies (DTMF) digit collection, and contains switching matrix to connect users to these resources. The IP supports flexible information interactions between a user and the network, and may contain service-specific user interaction scripts, w

42、hich allow user interactions to be grouped. Functionally, the IP contains the SRF. The IP may directly connect to one or more SSPs, and/or may connect to the signalling network. In the ISDN stimulus protocol environment, the IP will also provide resources such as customized and concatenated Informat

43、ion Display and Digit collection, out of channel, and it contains the necessary coordination and multiplexing to connect users to these resources. An SCP or AD can request an SSP to connect a user to a resource located in an IP that is connected to the SSP from which the service request is detected.

44、 An SCP or AD can also request the SSP to connect a user to a resource located in an IP that is connected to another SSP. 0 Service Node (SN) The SN can control IN-based services and engage in flexible information interactions with users. The SN communicates directly with one or more SSPs, each with

45、 a point-to-point signalling and transport connection. Functionally, the SN contains an SCF, SDF, SRF, and an SSF/CCF. This SSFKCF is closely coupled to the SCF within the SN, and is not accessible by external SCFs. In a manner similar to an AD, the SCF in an SN receives messages from the SSP, execu

46、tes SLPs, and sends messages to the SSP. SLPs in an SN may be developed by the same service creation environment used to develop SLPs for SCPs and ADS. The SRF in an SN enables the SN to interact with users in a manner similar to an IP. An SCF can request the SSF to connect a user to a resource loca

47、ted in an SN that is connected to the SSP from which the service request is detected. An SCF can also request the SSP to connect a user to a resource located in an SN that is connected to another SSP. g) Service Switching and Control Point (SSCP) The SSCP is a combined SCP and SSP in a single node.

48、Functionally, it contains an SCF, SDF, CCAF, CCF, and SSF. The connection between the SCF/SDF functions and the CCAF/CCF/SSF functions is proprietary and closely coupled, but it provides the same service capability as an SSP and SCP separately. This node may also contain SRF functional capabilities

49、(i.e. SRF as an optional capability). The interfaces between the SSCP and other PES are the same as the interfaces between the SSP and other PES, and therefore will not be explicitly stated. h) Service Data Point (SDP) The SDP contains the customer and network data which is accessed during the execution of a service. Functionally, the SDP contains an SDF. i) Enhanced ISDN Customer Premises Equipment (Enhanced ISDN CPE) Recommendation 1.1 12 defines the ISDN CPE as “a node that provides the functions necessary for the operation of the acc