INTERNATIONAL TELECOMMUNICATION UNION
`
`ITU-T
`
`TELECOMMUNICATION
`STANDARDIZATION SECTOR
`OF ITU
`
`Q.1221
`
`(09/97)
`
`SERIES Q: SWITCHING AND SIGNALLING
`Intelligent Network
`
`Introduction to Intelligent Network Capability
`Set 2
`
`ITU-T Recommendation Q.1221
`
`(Previously CCITT Recommendation)
`
`Bright House Networks - Ex. 1022, Page 1
`
`

`
`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
`SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4 AND No. 5
`SPECIFICATIONS OF SIGNALLING SYSTEM No. 6
`SPECIFICATIONS OF SIGNALLING SYSTEM R1
`SPECIFICATIONS OF SIGNALLING SYSTEM R2
`DIGITAL EXCHANGES
`INTERWORKING OF SIGNALLING SYSTEMS
`SPECIFICATIONS OF SIGNALLING SYSTEM No. 7
`DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1
`PUBLIC LAND MOBILE NETWORK
`INTERWORKING WITH SATELLITE MOBILE SYSTEMS
`INTELLIGENT NETWORK
`BROADBAND ISDN
`
`For further details, please refer to ITU-T List of Recommendations.
`
`Q.1–Q.3
`Q.4–Q.59
`Q.60–Q.99
`Q.100–Q.119
`Q.120–Q.249
`Q.250–Q.309
`Q.310–Q.399
`Q.400–Q.499
`Q.500–Q.599
`Q.600–Q.699
`Q.700–Q.849
`Q.850–Q.999
`Q.1000–Q.1099
`Q.1100–Q.1199
`Q.1200–Q.1999
`Q.2000–Q.2999
`
`Bright House Networks - Ex. 1022, Page 2
`
`

`
`ITU-T RECOMMENDATION Q.1221
`
`INTRODUCTION TO INTELLIGENT NETWORK CAPABILITY SET 2
`
`Summary
`Intelligent Network Capability Set 2 (IN CS-2) is the second standardized stage of the Intelligent
`Network (IN) as an architectural concept for the creation and provision of services, including
`telecommunication services, service management services and service creation services. This
`Recommendation gives an introduction to IN CS-2. It describes the main characteristics and overall
`capabilities of IN CS-2 and defines the service aspects, network aspects and functional relationships
`that form the basis of the IN CS-2 capabilities.
`
`This Recommendation is the first in the Q.122x-Series of Recommendations devoted to IN CS-2,
`which builds on the architectural principles of IN as described in the Q.121x- and the Q.120x-Series
`of Recommendations.
`
`The IN CS-2 Recommendations form a detailed and stable basis for implementing IN CS-2
`telecommunication services. They also provide high-level guidelines for supporting service
`management services, service creation services and some partially supported telecommunication
`services. The IN CS-2 Recommendations are intended to give the same degree of technical
`information as the IN CS-1 Recommendations (1995).
`
`Source
`ITU-T Recommendation Q.1221 was prepared by ITU-T Study Group 11 (1997-2000) and was
`approved under the WTSC Resolution No. 1 procedure on the 12th of September 1997.
`
`Bright House Networks - Ex. 1022, Page 3
`
`

`
`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, operating 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 their 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. 1.
`
`In some areas of information technology which fall within ITU-T’s purview, the necessary standards are
`prepared on a collaborative basis with ISO and IEC.
`
`In this Recommendation, the expression "Administration" is used for conciseness to indicate both a
`telecommunication administration and a recognized operating agency.
`
`NOTE
`
`INTELLECTUAL PROPERTY RIGHTS
`
`The ITU draws attention to the possibility that the practice or implementation 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 process.
`
`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 strongly urged to consult the
`TSB patent database.
`
`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.
`
` ITU 1998
`
`ii
`
`Recommendation Q.1221 (09/97)
`
`Bright House Networks - Ex. 1022, Page 4
`
`ª
`

`
`CONTENTS
`
`Page
`
`1
`
`2
`
`3
`
`3.1
`
`3.2
`
`4
`
`5
`
`5.1
`
`5.2
`
`5.3
`
`5.4
`
`6
`
`6.1
`
`6.2
`
`6.3
`
`6.4
`
`7
`
`7.1
`
`7.2
`
`Introduction ................................................................................................................
`
`Phased standardization ...............................................................................................
`
`General description and scope of IN CS-2 .................................................................
`
`Criteria for IN CS-2....................................................................................................
`
`Evolution of IN CS-2 .................................................................................................
`
`Overview of IN CS-2 Recommendations...................................................................
`
`Service aspects ...........................................................................................................
`
`Telecommunication services ......................................................................................
`
`Service management services.....................................................................................
`
`Service creation services ............................................................................................
`
`Network support of IN CS-2 services ........................................................................
`
`Network aspects .........................................................................................................
`
`Network functions ......................................................................................................
`
`Control architecture principles ...................................................................................
`6.2.1
`Service invocation and control......................................................................
`6.2.2
`End-user interactions.....................................................................................
`6.2.3
`Service management .....................................................................................
`
`Feature interactions ....................................................................................................
`
`Consistency among IN CS-2 supported service features............................................
`
`Functional relationships and interfaces ......................................................................
`
`Functional relationships and control classes ..............................................................
`7.1.1 Bearer connection control .............................................................................
`7.1.2 Non-IN call control .......................................................................................
`7.1.3
`IN service control..........................................................................................
`7.1.4
`Service management control.........................................................................
`7.1.5 Non-IN call unrelated control .......................................................................
`
`Key functions and interfaces ......................................................................................
`7.2.1
`Single point multiple points of control .........................................................
`7.2.2
`Single-ended/multi-ended calls.....................................................................
`7.2.3 Mid-call interruption .....................................................................................
`7.2.4 Call party handling........................................................................................
`7.2.5
`Enhanced SRF...............................................................................................
`7.2.6 Call unrelated user interaction ......................................................................
`7.2.7 Out-channel call related user interaction.......................................................
`
`1
`
`2
`
`2
`
`2
`
`2
`
`3
`
`3
`
`5
`
`5
`
`6
`
`7
`
`7
`
`8
`
`9
`9
`9
`10
`
`10
`
`10
`
`10
`
`10
`11
`11
`12
`12
`12
`
`12
`12
`12
`13
`13
`13
`13
`13
`
`Recommendation Q.1221 (09/97)
`
`iii
`
`Bright House Networks - Ex. 1022, Page 5
`
`

`
`Service/feature interaction (service processing)............................................
`7.2.8
`Internetworking.............................................................................................
`7.2.9
`7.2.10 Security .........................................................................................................
`7.2.11 IN-TMN ........................................................................................................
`7.2.12 Service management .....................................................................................
`7.2.13 Service creation.............................................................................................
`7.2.14 Personal mobility ..........................................................................................
`
`Appendix I – IN CS-2 benchmark services and features.........................................................
`
`I.1
`
`I.2
`
`I.3
`
`I.4
`
`I.5
`
`General .......................................................................................................................
`
`Definitions..................................................................................................................
`I.2.1
`Telecommunication services.........................................................................
`I.2.2
`Service management services........................................................................
`I.2.3
`Service creation services ...............................................................................
`
`Telecommunication services ......................................................................................
`I.3.1
`General ..........................................................................................................
`I.3.2
`Definitions.....................................................................................................
`I.3.3 Mobility service features (UPT, FPLMTS)...................................................
`I.3.4
`Other services................................................................................................
`I.3.5
`Other service features....................................................................................
`
`Service management services.....................................................................................
`I.4.1
`General ..........................................................................................................
`I.4.2
`Definition ......................................................................................................
`I.4.3
`Service management service/service feature.................................................
`
`Service creation services ............................................................................................
`I.5.1
`General ..........................................................................................................
`I.5.2
`Service specification services .......................................................................
`I.5.3
`Service development services .......................................................................
`I.5.4
`Service verification services .........................................................................
`I.5.5
`Service deployment services.........................................................................
`I.5.6
`Service creation service management services .............................................
`
`Page
`13
`14
`15
`16
`16
`19
`21
`
`22
`
`22
`
`22
`22
`22
`22
`
`22
`22
`22
`23
`28
`30
`
`34
`34
`34
`35
`
`37
`37
`37
`37
`38
`38
`39
`
`iv
`
`Recommendation Q.1221 (09/97)
`
`Bright House Networks - Ex. 1022, Page 6
`
`

`
`Recommendation Q.1221
`
`INTRODUCTION TO INTELLIGENT NETWORK CAPABILITY SET 2
`(Geneva, 1997)
`
`Introduction
`1
`Intelligent Network Capability Set 2 (IN CS-2) is the second standardized stage of the Intelligent
`Network (IN) as an architectural concept for the creation and provision of services, including
`telecommunication services, service management services and service creation services. This
`Recommendation gives an introduction to IN CS-2. It describes the main characteristics and overall
`capabilities of IN CS-2 and defines the service aspects, network aspects and functional relationships
`that form the basis of the IN CS-2 capabilities.
`
`Listed below are the acronyms used in this Recommendation:
`BCSM
`Basic Call State Model
`CCAF
`Call Control Agent Function
`CCF
`Call Control Function
`CCIS
`Common Channel Interoffice Signalling
`CRACF
`Call-related Radio Access Control Function
`CS
`Capability Set
`CURACF Call-Unrelated Radio Access Control Function
`CUSF
`Call-Unrelated Service Function
`DTMF
`Dual-Tone Multi-Frequency
`FE
`Functional Entity
`GFP
`Global Functional Plane
`IAF
`Intelligent Access Function
`INAP
`Intelligent Network Application Protocol
`IN-SSM IN-Switching State Model
`ISDN
`Integrated Services Digital Network
`ISUP
`ISDN User Part
`ITU-T
`International Telecommunication Union – Telecommunication Standardization Sector
`OAM
`Operation, Administration, and Maintenance
`PBX
`Private Branch Exchange
`PE
`Physical Entity
`PLMN
`Public Land Mobile Network
`PSTN
`Public Switched Telephone Network
`QOS
`Quality of Service
`RCF
`Radio Control Function
`SCE
`Service Creation Environment
`SCEF
`Service Creation Environment Function
`SCF
`Service Control Function
`
`Recommendation Q.1221 (09/97)
`
`1
`
`Bright House Networks - Ex. 1022, Page 7
`
`

`
`SCUAF
`SDF
`SIB
`SMAF
`SMF
`SRF
`SS7
`SSF
`TMN
`UPT
`
`Service Control User Agent Function
`Service Data Function
`Service-Independent Building Blocks
`Service Management Access Function
`Service Management Function
`Specialized Resource Function
`Signalling System No. 7
`Service Switching Function
`Telecommunications Management Network
`Universal Personal Telecommunication
`
`Phased standardization
`2
`The phased approach of IN capability sets has been described in Recommendation Q.1201.
`
`In order to prepare for the next phases of IN (CS-3 and beyond), the IN CS-2 Recommendations
`contain both complete technical specifications (with complete support for physical architecture and
`detailed protocol description) and incomplete specifications that are intended to be the base for
`subsequent capability sets (with SIB description and the impact on the functional architecture).
`Capabilities which are only incompletely covered by IN CS-2 Recommendations are highlighted
`through special notes or caveats.
`
`3
`
`General description and scope of IN CS-2
`
`Criteria for IN CS-2
`3.1
`IN CS-2 defines an initial subset of IN capabilities that meet the following general criteria:
`a)
`IN CS-2 is a subset of the target Intelligent Network architecture;
`b)
`IN CS-2 is a superset of IN CS-1, as defined in the IN CS-1 Recommendations (1995);
`c)
`IN CS-2 is a set of definitions of capabilities that is of direct use to both manufacturers and
`network operators;
`IN CS-2 provides network capabilities defined to support the set of IN CS-2 benchmark
`services or service features. These capabilities can also be used for the support of other
`services that may, or may not, be standardized by ITU-T.
`
`d)
`
`The IN CS-2 architecture could be applied for PSTN, ISDN, and mobile networks.
`
`Evolution of IN CS-2
`3.2
`The IN CS-2 Recommendations (Q.122x-Series) form a detailed and stable basis for implementing
`IN CS-2 telecommunication services. They also give high-level guidelines for supporting service
`management services and service creation services and some partially supported telecommunication
`services. Complete technical specifications of these services will be in the subsequent IN capability
`sets.
`
`As IN CS-1, IN CS-2 takes into account the evolution requirement. It is defined to support the IN
`CS-2 benchmark services and service features without assumptions that are known to limit its
`evolution into future capability sets.
`
`2
`
`Recommendation Q.1221 (09/97)
`
`Bright House Networks - Ex. 1022, Page 8
`
`

`
`The IN CS-2 Recommendations are intended to give the same degree of technical information as the
`IN CS-1 Recommendations (Q.121x-Series).
`
`Overview of IN CS-2 Recommendations
`4
`Table 1 contains an overview of the Recommendations that are specifically related to IN CS-2:
`
`Table 1/Q.1221 – IN CS-2 Recommendations
`
`Title
`
`Q.1220-Series Intelligent network capability set 2 Recommendation structure
`Introduction to Intelligent Network Capability Set 2
`Service plane for Intelligent Network Capability Set 2
`Global functional plane for Intelligent Network Capability Set 2
`Distributed functional plane for Intelligent Network Capability Set 2
`Physical plane for Intelligent Network Capability Set 2
`Interface Recommendation for Intelligent Network Capability Set 2
`Intelligent network users guide for capability set 2
`Glossary of terms used in the definition of intelligent networks
`
`Rec.
`
`Q.1220
`Q.1221
`Q.1222
`Q.1223
`Q.1224
`Q.1225
`Q.1228
`Q.1229
`Q.1290
`
`Service aspects
`5
`The services and service features that are to be supported by IN CS-2 are fundamental to the IN CS-2
`Service-Independent Building Blocks (SIBs), call processing model and service control principles.
`Three types of services have been identified in IN CS-2: telecommunication service, service
`management service and service creation services. The last two types of services are first introduced
`in IN CS-2.
`
`Tables 2 and 3 list IN CS-2 benchmark services and service features, which, in addition to IN CS-1
`related telecommunication services/service features, can be used to identify and verify the
`service-independent capabilities of IN CS-2.
`
`Appendix I provides short prose descriptions of the benchmark services and service features. It was
`used to develop the current Q.122x-Series of Recommendations and was intended for this purpose
`only. It is not to be used by service designers for service creation.
`
`Recommendation Q.1221 (09/97)
`
`3
`
`Bright House Networks - Ex. 1022, Page 9
`
`

`
`Table 2/Q.1221 – Target set of IN CS-2 telecommunication services
`
`Benchmark telecommunication services
`
`Internetwork Freephone (IFPH)
`Internetwork Premium rate (IPRM)
`Internetwork Mass calling (IMAS)
`Internetwork televoting (IVOT)
`Global Virtual Network Service (GVNS)
`Completion of Call to Busy Subscriber
`(CCBS) a)
`Conference calling (CONF)
`Call Hold (HOLD)
`
`Call Transfer (CT)
`Call Waiting (CW)
`Hot line (HOT)
`Multimedia (MMD) a)
`Terminating Key Code Screening (TKCS) a)
`Message Store and Forward (MSF)
`
`International Telecommunication Charge Card (ITCC) a)
`Mobility services (UPT) a)
`NOTE 1 – The above service names apply to the descriptions of targeted services (see Appendix I), and
`not to the user-network interface descriptions provided by ITU-T Study Group 1.
`NOTE 2 – Network implementation aspects may be important for some services.
`a) These services may be partially supported in IN CS-2. For example, they may be supported at the
`GFP level but not supported at the protocol level. Some of these services may also require capabilities
`beyond IN CS-2. Please note that SIBs are used for modelling purpose. They are not meant to be used
`as a standardized solution for service creation, even though some organizations may wish to use them
`for this purpose.
`
`Table 3/Q.1221 – Target set of IN CS-2 telecommunication service features
`
`Benchmark telecommunication service features
`User Authentication (UAUT)
`InterNetwork Service Identification (INSI)
`InterNetwork Rate Indicator, Forward (INRI-F) a)
`User Registration (UREG/outgoing call
`registration)
`InterNetwork Rate Indicator, Backward (INRI-B) a)
`Secure Answering (SANSW)
`Real Time Flexible Rating (RTFR) a)
`Follow-On (FO)
`Flexible (call) Origination Authorization (FOA) Originating Carrier Identification (OCI) a)
`Flexible (call) Termination Authorization (FTA) Terminating carrier identification (OTC) a)
`Resource Allocation (RAL) a)
`Provision of Stored Messages (PSM)
`Delivery of Complementary Information (DCI) a)
`Multiple Terminal Address Registration
`(MTAR) a)
`Intended Recipient Identity Presentation (IRIP)
`Blocking/Unblocking of Incoming Calls (BUIC)
`a)
`
`Service Indication (SIND)
`Service Negotiation (SNEG) a)
`
`Terminal Authentication (TAUT) a)
`Handover (HOV) a)
`
`Terminal Location Registration (TLR) a)
`
`Call Forwarding (CF)
`B-ISDN Multiple Connections Point to Point
`(BI-MCPP) a)
`B-ISDN Multi-Casting (BI-MCAST) a)
`
`4
`
`Recommendation Q.1221 (09/97)
`
`Bright House Networks - Ex. 1022, Page 10
`
`

`
`Table 3/Q.1221 – Target set of IN CS-2 telecommunication service features (concluded)
`
`Terminal Equipment Validation (TEV) a)
`
`Cryptographic Information Management (CIM)
`a)
`
`Automatic Call Back (ACB) a)
`Call Hold (HOLD)
`Call Retrieve (CRET)
`Call Transfer (CT)
`Call Toggle (CTOG)
`
`Call Waiting (CW)
`
`Meet-Me Conference (MMC) a)
`
`Benchmark telecommunication service features
`Terminal Attach/Detach (ATDT) a)
`B-ISDN Conferencing (BI-CONF) a)
`Terminal Paging (TPAG) a)
`Call Connection Elapsed time Limitation (CCEL) a)
`Radio Paging (RPAG) a)
`Special Facility Selection (SFS) a)
`Emergency Calls in Wireless (ECW) a)
`Concurrent Features Activation with Bi-Control
`(CFA BC) a)
`Customized Call Routing with Public network
`(CCR-PU)
`Customized Call Routing with Private network
`(CCR-PR)
`Internetwork Service Profile Interrogation (ISPI)
`Internetwork Service Profile Modification (ISPM)
`Internetwork Service Profile Transfer (ISPT)
`Reset of UPT registration for incoming calls (IRUR) a)
`Mobility Call Origination (MCO) (mobile call
`origination/UPT outcall)a)
`Mobility Incall Delivery (MID) (Mobile user call
`term./UPT incall delivery)a)
`Data Communication between different Protocol
`Terminals (DCPT) a)
`Charge Determination (CDET) a)
`Charge Card Validation (CCV) a)
`Call Disposition (CD) a)
`Enhanced Call Disposition (ECD) a)
`User Service Interaction (USI) a)
`
`Multi-Way Calling (MWC) a)
`Call Pick-Up (CPU) a)
`Calling Name Delivery (CND)
`Message Waiting Indication (MWI) a)
`Feature Use Charging (FUC) a)
`Services On-Demand (SOD) a)
`a) These services may be partially supported in IN CS-2. For example, they may be supported at the GFP
`level but not supported at the protocol level. Some of these services may also require capabilities
`beyond IN CS-2. Please note that SIBs are used for modelling purpose. They are not meant to be used
`as a standardized solution for service creation, even though some organizations may wish to use them
`for this purposes
`
`Telecommunication services
`5.1
`As in IN CS-1, IN CS-2 capabilities are intended to support single-ended single-point-of-control
`services and service features. Single-ended and single-point-of-control are to be described in 7.2.1
`and 7.2.2.
`
`Service management services
`5.2
`Service management services/service features are supported by IN CS-2. The following list (Table 4)
`represents service names but not user-network interface descriptions provided by ITU-T Study
`Group 1.
`
`Recommendation Q.1221 (09/97)
`
`5
`
`Bright House Networks - Ex. 1022, Page 11
`
`

`
`Table 4/Q.1221 – Target set of IN CS-2 service management services/service features
`
`Benchmark service management services and service features
`
`Service customization services
`Telecommunications Service Customization (TSC)
`Service Control Customization (SCC)
`Service Monitoring Customization (SMC)
`Service control services
`Subscriber Service Activation/Deactivation (SSAD)
`
`Subscriber Monitoring Activation/Deactivation
`(SMAD)
`Subscriber Profile Management (SPM)
`Subscriber Service Limiter (SSL)
`Subscriber Service Invocation (SSI)
`
`Service monitoring services
`Subscriber Service Report (SSR)
`Billing Report (BR)
`Subscriber Service Status Report (SSSR)
`Subscriber Traffic Monitoring (STM)
`Subscriber service Management Usage Report
`(SMPUR)
`Other management services
`
`Subscriber Service Testing (SST)
`SMP Usage Report (SUR)
`Subscriber Security Control (SSC)
`
`Service creation services
`5.3
`Service creation services/service features are supported by IN CS-2. The following list (Table 5)
`represents service names but not user-network interface descriptions provided by ITU-T Study Group
`1.
`
`Table 5/Q.1221 – Target set of IN CS-2 services creation services/service features
`
`Benchmark service creation services and service features
`Service specification services
`Service deployment services
`Feature interaction detection
`SMP-created service data and SLP update
`Cross-service feature interaction detection
`Service distribution
`Feature interaction rule/guidelines generation
`SIB distribution
`Service and SIB cataloguing
`Data rule distribution
`Created service resource utilization
`Feature interaction rule distribution
`Service development services
`Multiple SMP support
`Creation interface selection
`Network tailoring
`Creation initiation
`Network element capability specification
`Editing
`Network element function/capability assignment
`Service creation management services
`Combining
`Data population rule generation
`SCE access control
`SMP service creation
`SCE usage scope
`
`6
`
`Recommendation Q.1221 (09/97)
`
`Bright House Networks - Ex. 1022, Page 12
`
`

`
`Table 5/Q.1221 – Target set of IN CS-2 services creation services/service features (concluded)
`
`Benchmark service creation services and service features
`Syntax and data checking
`SCE recovery
`Service and SIB archiving
`SCE release management
`Service configuration control
`SCE capability expansion
`SIB configuration control
`SCE conversion
`Network configuration tracking capability
`Cross-SCE service maintenance
`Service verification services
`SCE-to-SCE system consistency
`SCE testing
`SCE service/modular/system transference
`Created service simulation
`Conversion of created services
`Created service live testing
`Service management interaction
`
`Network support of IN CS-2 services
`5.4
`The services are to be supported over various networks. For IN CS-2 applications the following
`networks are considered:
`i)
`PSTN;
`ii)
`ISDN (public and private networks);
`iii)
`PLMN.
`
`Network aspects
`6
`This clause provides an overview of the IN network functions and sets guidelines for the control
`architecture of IN CS-2. It also describes how the issues of feature interaction and service-feature
`consistency are handled in IN CS-2.
`
`Figure 1 summarizes the IN network functions and their functional relationships.
`
`Recommendation Q.1221 (09/97)
`
`7
`
`Bright House Networks - Ex. 1022, Page 13
`
`

`
`SMF
`
`All other
`network functions
`except CCAF
`
`SRF
`
`SCF
`
`SCUAF
`
`CCAF
`
`CUSF
`
`SSF
`
`CCF
`
`SSF
`
`CCF
`
`SMAF
`
`SCEF
`
`SDF
`
`SCF
`
`CCF
`
`SDF
`
`CCAF
`
`T1184890-97
`
`
`CCAF Call control agent function
`
`CCF
`Call control function
`SCEF
`Service creation environment function
`SCF
`Service control function
`
`SDF
`Service data function
`
`SMAF Service management access function
`
`
`
`
`
`
`
`Service management function
`SMF
`Specialized resource function
`SRF
`Service switching function
`SSF
`CUSF Call-unrelated service function
`SCUAF Service control user agent function
`
`Figure 1/Q.1221 – IN functions and functional relationships
`
`6.1
`
`Network functions
`
`Call control and call unrelated control related functions
`SSF – Service switching function: This function interfaces with CCF and SCF. It allows the CCF to
`be directed by the SCF.
`
`SRF – Specialized resources function: This function provides a category of resources for access by
`other network entities. Examples of resources include DTMF sending and receiving, protocol
`conversion, speech recognition, and synthesized speech provision.
`
`CCF – Call control function: This function refers to call and connection handling in the classical
`sense (e.g. that of an exchange).
`
`CCAF – Call control agent function: This function provides the user access to the network.
`
`CUSF – Call unrelated service function: This function handles call unrelated activities.
`
`SCUAF – Service control user agent function: This function provides the user access to the network
`call unrelated service function.
`
`Service control related functions
`SCF – Service control function: This function contains the IN service logic and handles service
`related processing activity.
`
`SDF – Service data function: This function handles access to service-related data and network data
`and provides consistency checks on data. It hides from the SCF the real data implementation and
`provides a logical data view to SCF.
`
`Management related functions
`SCEF – Service creation environment function: This function allows an intelligent network service
`to be defined, developed, tested and input to the SMF. The output of this function involves service
`logic and service data templates.
`
`8
`
`Recommendation Q.1221 (09/97)
`
`Bright House Networks - Ex. 1022, Page 14
`
`

`
`SMAF – Service management access function: This function provides an interface (e.g. screen
`presentation) for service subscribers and service administrators who have access to the SMF.
`
`SMF – Service management function: This function involves service operation control, service
`provision control, service deployment control, service monitoring and billing.
`
`Control architecture principles
`6.2
`As stated in clause 5 (Service aspects), the service scope of IN CS-2 shall be restricted to single-
`ended single-point-of-control services. This subclause identifies principles for the control
`architecture of IN CS-2, in the context of this service scope.
`
`This subclause is organized around three control aspects:
`–
`service invocation and control;
`–
`end-user interaction with and without the SRF; and
`–
`service management.
`
`Service invocation and control
`6.2.1
`This control aspect involves the CCF, SSF and SCF.
`
`2)
`
`3)
`
`As in IN CS-1, the following points capture key principles for IN CS-2:
`1)
`The CCF retains ultimate responsibility for integrity and control of the local connection at all
`times.
`The SSF-to-SCF relationship is, by definition, service-independent. Therefore, the CCF and
`SSF should never contain service logic specific to IN CS-2 supported services.
`In the event of SCF malfunction, or time-out in the SCF to SSF response, the SSF/CCF
`combination should be capable of reverting to a default call completion sequence, with
`appropriate announcement(s) to the calling and/or called party.
`The SSF should never have to interact with more than one SCF at any given time in order to
`complete a sequence of query/response interactions on behalf of a calling or called party.
`Call hand-offs (transfer of responsibility) between SCFs, and between SSFs are permitted in
`IN CS-2. Nevertheless, the hand-off must be explicit, and must not violate principle 4).
`
`4)
`
`5)
`
`6.2.2 End-user interactions
`As part of the process of formulating a response to the SSF, the SCF may need to enter into a
`dialogue with the calling or called party. This would take the form of a prompt and collection
`sequence with the aid of an SRF, or the form of call unrelated/out-channel call related interactions,
`which are new in IN CS-2 (see 7.2.6 and 7.2.7 for more details).
`
`As in IN CS-1, when the SRF is being used, the SCF in IN CS-2 does not have to enter into this
`dialogue directly. Instead, it instructs the SRF to carry out a prompt and collection sequence with the
`calling or called party on its behalf. In general, the actual implementation of IN services will govern
`the kind of transport systems and protocols (e.g. DTMF, D-channel user-to-user signalling, and data
`services) used to collect information from the user.
`
`Again, the following key principles apply, when the SRF is being used in IN CS-2:
`1)
`The SCF has full IN-supported service control of instruction formulation and sequencing
`with respect to the SRF and SSF.
`As a corollary to principle 1), there shall be no direct service control interaction between the
`SSF and SRF for IN CS-2-based services. The SSF and SRF have a peer-peer relationship
`for the control of IN CS-2-based services, and both are subsidiary to the SCF.
`
`2)
`
`Recommendation Q.1221 (09/97)
`
`9
`
`Bright House Networks - Ex. 1022, Page 15
`
`

`
`3)
`
`The SCF will require the capability of suspending processing of an I