1、 TIA-41.750-E (Revision of TIA-41.D) October 2010 Part 750: Wireless Radiotelecommunications Intersystem Operations SSF/CCF Call and Service Logic Model ANSI/TIA-41.750-E-2004 APPROVED: APRIL 20, 2004 REAFFIRMATION: SEPTEMBER 1, 2010 NOTICE TIA Engineering Standards and Publications are designed to
2、serve the public interest through eliminating misunderstandings between manufacturers and purchasers, facilitating interchangeability and improvement of products, and assisting the purchaser in selecting and obtaining with minimum delay the proper product for their particular need. The existence of
3、such Standards and Publications shall not in any respect preclude any member or non-member of TIA from manufacturing or selling products not conforming to such Standards and Publications. Neither shall the existence of such Standards and Publications preclude their voluntary use by Non-TIA members,
4、either domestically or internationally. Standards and Publications are adopted by TIA in accordance with the American National Standards Institute (ANSI) patent policy. By such action, TIA does not assume any liability to any patent owner, nor does it assume any obligation whatever to parties adopti
5、ng the Standard or Publication. This Standard does not purport to address all safety problems associated with its use or all applicable regulatory requirements. It is the responsibility of the user of this Standard to establish appropriate safety and health practices and to determine the applicabili
6、ty of regulatory limitations before its use. (From Standards Proposal No. 3-3590.750-RV5, formulated under the cognizance of the TIA TR-45.2 Subcommittee on Wireless Intersystem Technology.) Published by TELECOMMUNICATIONS INDUSTRY ASSOCIATION 2002 Standards and Technology Department 2500 Wilson Bou
7、levard Arlington, VA 22201 U.S.A. PRICE: Please refer to current Catalog of TIA TELECOMMUNICATIONS INDUSTRY ASSOCIATION STANDARDS AND ENGINEERING PUBLICATIONS or call Global Engineering Documents, USA and Canada (1-800-854-7179) International (303-397-7956) or search online at http:/www.tiaonline.or
8、g/standards/search_n_order.cfm All rights reserved Printed in U.S.A. PLEASE! DONT VIOLATE THE LAW! This document is copyrighted by the TIA and may not be reproduced without permission. Organizations may obtain permission to reproduce a limited number of copies through entering into a license agreeme
9、nt. For information, contact: Global Engineering Documents 15 Inverness Way East Englewood, CO 80112-5704 U.S.A. or call U.S.A. and Canada 1-800-854-7179, International (303) 397-7956 NOTICE OF DISCLAIMER AND LIMITATION OF LIABILITY The document to which this Notice is affixed has been prepared by o
10、ne or more Engineering Committees of the Telecommunications Industry Association (“TIA”). TIA is not the author of the document contents, but publishes and claims copyright to the document pursuant to licenses and permission granted by the authors of the contents. TIA Engineering Committees are expe
11、cted to conduct their affairs in accordance with the TIA Engineering Manual (“Manual”), the current and predecessor versions of which are available at http:/www.tiaonline.org/standards/sfg/engineering_manual.cfm. TIAs function is to administer the process, but not the content, of document preparatio
12、n in accordance with the Manual and, when appropriate, the policies and procedures of the American National Standards Institute (“ANSI”). THE USE OR PRACTICE OF CONTENTS OF THIS DOCUMENT MAY INVOLVE THE USE OF INTELLECTUAL PROPERTY RIGHTS (“IPR”), INCLUDING PENDING OR ISSUED PATENTS, OR COPYRIGHTS,
13、OWNED BY ONE OR MORE PARTIES. TIA MAKES NO SEARCH OR INVESTIGATION FOR IPR. WHEN IPR CONSISTING OF PATENTS AND PUBLISHED PATENT APPLICATIONS ARE CLAIMED AND CALLED TO TIAS ATTENTION, A STATEMENT FROM THE HOLDER THEREOF IS REQUESTED, ALL IN ACCORDANCE WITH THE MANUAL. TIA TAKES NO POSITION WITH REFER
14、ENCE TO, AND DISCLAIMS ANY OBLIGATION TO INVESTIGATE OR INQUIRE INTO, THE SCOPE OR VALIDITY OF ANY CLAIMS OF IPR. ALL WARRANTIES, EXPRESS OR IMPLIED, ARE DISCLAIMED, INCLUDING WITHOUT LIMITATION, ANY AND ALL WARRANTIES CONCERNING THE ACCURACY OF THE CONTENTS, ITS FITNESS OR APPROPRIATENESS FOR A PAR
15、TICULAR PURPOSE OR USE, ITS MERCHANTABILITY AND ITS NON-INFRINGEMENT OF ANY THIRD PARTYS INTELLECTUAL PROPERTY RIGHTS. TIA EXPRESSLY DISCLAIMS ANY AND ALL RESPONSIBILITIES FOR THE ACCURACY OF THE CONTENTS AND MAKES NO REPRESENTATIONS OR WARRANTIES REGARDING THE CONTENTS COMPLIANCE WITH ANY APPLICABL
16、E STATUTE, RULE OR REGULATION. TIA SHALL NOT BE LIABLE FOR ANY AND ALL DAMAGES, DIRECT OR INDIRECT, ARISING FROM OR RELATING TO ANY USE OF THE CONTENTS CONTAINED HEREIN, INCLUDING WITHOUT LIMITATION ANY AND ALL INDIRECT, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES (INCLUDING DAMAGES FOR LOSS OF BUS
17、INESS, LOSS OF PROFITS, LITIGATION, OR THE LIKE), WHETHER BASED UPON BREACH OF CONTRACT, BREACH OF WARRANTY, TORT (INCLUDING NEGLIGENCE), PRODUCT LIABILITY OR OTHERWISE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. THE FOREGOING NEGATION OF DAMAGES IS A FUNDAMENTAL ELEMENT OF THE USE OF THE C
18、ONTENTS HEREOF, AND THESE CONTENTS WOULD NOT BE PUBLISHED BY TIA WITHOUT SUCH LIMITATIONS. TIA-41-750-E123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960750-1 SSF/CCF CALL AND SERVICE LOGIC MODELPART 7501 SSF/CCF CALL AND SERVICE LOGIC MOD
19、EL1.1 GeneralWIN call and service logic processing encompasses call and connection processing in the SSF/CCF,service logic execution in the SCF, and the use of supporting resources and data in the SRF and SDF,respectively. This section describes the WIN call and service logic processing in terms of
20、callmodeling and modeling of service logic processing. Call modeling provides a high-level service, vendor, and implementation independentabstraction of WIN call and connection processing in the SSF/CCF. This abstraction providesan observable view of SSF/CCF activities and resources to the SCF, enab
21、ling the SCF to interactwith the SSF in the course of executing service logic. The modeling of service logic processing provides an abstraction of SCF activities needed tosupport this service logic execution, as well as an abstraction of SRF and SDF activities andresources accessible to the SCF.Sinc
22、e this modeling only provides an observable (i.e., external) view of SSF/CCF, SCF, SRF andSDF activities and resources, this modeling does not imply an obligation to vendors to implementfunctional entities into products as a one-to-one mapping of functional entity model components. Inparticular, the
23、re is no requirement at this time to partition the SSF/CCF into separate SSF and CCFnor to identify which resources are located within the SSF or CCF.TIA-41-750-EGeneral123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960750-21.1.1 Feature a
24、nd Service Interaction ManagementFeature and service interactions managers provide mechanisms for controlling feature interactions.These may be customized per subscriber. The SSF-based feature interactions manager (FIM)coordinates interactions between SSF/CCF-executed features and the interactions w
25、ith SCF. TheSCF-based service interactions manager (SIM) coordinates interactions among SCF-executedservice logic programs (SLPs). These SLPs may be on different SCFs. Rules for feature precedenceand the coordination of data modifications that affect call processing must be enforced by the FIMand SI
26、M.Basic rules include:a. Feature invocation precedence is managed at the SSF/CCF by the FIM.b. Feature invocation precedence at the SCF is managed by the SIM.c. A single response is given to the Basic Call Manager (BCM) representing the results of oneor more feature invocations.d. A response to the
27、BCM that keeps the TCAP transaction open for subsequent triggering ofthis BCM to the same SLP sending the response, is a capability for a future phase of WIN(e.g., EDP-R, EDP-N). Setting new WIN triggers for subsequent TCAP transactions maybe done in the response to the BCM, but no assumption is mad
28、e regarding the SLPinteraction at the SCF.The FIM and SIM are introduced in WIN to handle the additional complexity of managing featureinteractions in a WIN environment. Prior to WIN, pre-defined rules were used for managingprecedence among multiple features that may be invoked at the same point in
29、call processing.Feature interactions for TIA/EIA-664 features have been defined, and the SSF/CCF-based FIM hasonly to invoke the subscribed features in the prescribed order. A premise of WIN is that featureinteractions are not pre-determined. Service providers create value-added services by offering
30、subscribers flexibility in how features interact. This creates a need for the FIM and SIM to manageservice interactions on a per subscriber basis.With WIN, the FIM must manage not only the pre-defined feature interactions of a pre-WIN systembut also the interactions of these features with invocation
31、s of WIN features. Some guidelines havebeen defined for the FIM: within a Detection Point trigger precedence is specified, although locallyallowed numbers may escape certain triggers. The precedence of features invoked from a WINtrigger is not specified; however, the precedence of TIA/EIA-664 define
32、d features is specified in thatstandard. The FIM is further defined in Section 1.1.2.The concept of a SIM is introduced with WIN. A SIM manages feature interactions at a single WINtrigger which may result in multiple feature invocations. The features invoked by the SIM mayinclude HLR-based features
33、existing prior to WIN. In this case the relative precedence of featuresis determined by the SIM and may differ from the precedence defined in TIA/EIA-664. The SIMresides on the SCF platform to which the trigger query is sent. For that specific trigger, the SIMmanages the invocation of multiple subsc
34、ribed services, some of which may reside on separatephysical platforms. The SIM is further defined in Section 1.1.3.TIA-41-750-E123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960750-3 General1.1.2 Feature Interactions Manager (FIM) - SSF/C
35、CFThe feature interactions manager (FIM) at the SSF coordinates the invocation of SSF/CCF-executedfeatures and SCF-executed features as illustrated in Figure 1.Figure 1 Feature Interactions Manager at the SSF/CCFBasic rules include:a. At a particular Detection Point (DP), if a locally allowed number
36、 (e.g., 9-1-1, * 9-1-1, N11,*N11) is dialed, treatment as a locally allowed number will take precedence over othertreatments. In some cases, these locally allowed numbers may invoke SCF-executedfeatures instead of SSF/CCF-executed features. Such invocations are done on an office-basis and cannot be
37、individually subscribed.b. At the same Detection Point (DP), SCF-executed features receive the next highestprecedence, after completion of the execution of locally allowed numbers. The rules forDP processing are further described in Section 1.2.3.6.c. Following the conclusion of SCF-executed feature
38、 processing, if call processing continuesat the DP, the SSF/CCF-executed features may be invoked. In cases where the TIA-41query has not been identified for invoking SCF-executed features and services, thesequeries are considered part of the SSF/CCF-executed feature set. If call processing isresumed
39、 at a different point in call, any remaining criteria at the DP from which the servicelogic was invoked are not processed and similarly, if DPs are bypassed as the result of callprocessing resuming at a different point in call, no processing of the bypassed DPs is done.This is illustrated in Figure
40、2 and Figure 3.d. Whether execution of an active SSF/CCF-executed feature may be interrupted for theinvocation of an SCF-executed feature is for further study.SCFBCM CCF FIM SBSL SCF SSFBasic Call Manager Call Control Function Feature Interaction Management Switch-Based Service Logic Service Control
41、 Function Service Switching FunctionLegendSSF/CCFFIMBCMSBSLjSBSLiTIA-41-750-EGeneral123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960750-4Figure 2 Effect of “Continue” Response to SSF /CCFDPDPBCSM PICBasic call process function (BCSM PIC)
42、SCFBCMSSF/CCFS I MF S L PF S L PResponse: “Resume” Query: Request instructionsDPBCSM PICLegendBCM BCSM CCF DP FIM FSLP PIC SCF SIM SSFBasic Call Manager Basic Call State Model Call Control Function Detection Point Feature Interactions Manager Feature Service Logic Program Point In Call Service Contr
43、ol Function Service Interactions Manager Service Switching FunctionIf: more criteria at this DP Then: resume processing criteria Else: go to PIC following this DPDP Processing Trigger CriteriaFIM Service Logic (SIM + FSLPs)1. xxx2. yyy3. zzzCriteriaResponsTIA-41-750-E12345678910111213141516171819202
44、1222324252627282930313233343536373839404142434445464748495051525354555657585960750-5 GeneralFigure 3 Effect of Returning to a Different PIC at the SSF/CCFDPDPBCSM PICSCFBCMFIMSSF/CCFResponse: “Call Processing instruction” DPBCSM PICDPBCSM PICLegendBCM BCSM CCF DP FIM FSLP PIC SCF SIM SSFBasic Call M
45、anager Basic Call State Model Call Control Function Detection Point Feature Interaction Management Feature Service Logic Program Point In Call Service Control Function Service Interactions Manager Service Switching FunctionResume call processing at this PIC. Do not process any further trigger criter
46、ia at exit DP. Do not process any trigger criteria at bypassed DPs. Basic call process function (BCSM PIC)Call Processing instructionDP Processing Trigger CriteriaService Logic (SIM + FSLPs)S I MF S L PF S L PQuery: Request instructions1. xxx2. yyy3. zzzCriteriaTIA-41-750-EGeneral1234567891011121314
47、15161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960750-61.1.3 Service Interactions Manager (SIM) - SCFThe service interactions manager (SIM) at the SCF coordinates the invocation of features applicablefor a subscriber at a given trigger at a Detection Point (
48、DP). The SIM has knowledge of the relevantSCF-executed features resident on the same SCF and an indication when another feature on aseparate SCF requires interaction at certain points in the SIM logic flow. When service logic isdistributed across multiple SCFs, the SIM is also distributed. The first
49、 SIM invoked by the triggermust coordinate the precedence and data changes that affect call processing within the SCF andbetween SCFs. This is illustrated in Figure 4.Figure 4 Service Interactions Manager at the SCFBasic rules include:a. Once an SCF-executed feature is given control, it must complete its task before returningcontrol to the SIM. The setting of Event Detection Point - Response (EDP-Rs) indicatesthe need for the feature to regain control at a future DP, but yields current control of servicelogic to other features.b. SIM rules include the actions to be taken based on t
