ETSI EN 301 143 V1.1.4 (1999-09)

Intelligent Network (IN); Intelligent Network Application Protocol (INAP); Capability Set 2 (CS2); Cordless Terminal Mobility (CTM); Stage 3 specifications for Service Control Function (SCF); SCF and Call Unrelated Service Function (CUSF)/Service Switching Function (SSF); SCF interface

DEN/SPS-03061

Inteligentno omrežje (IN) – Aplikacijski protokol inteligentnega omrežja (INAP) – Nabor zmogljivosti 2 (CS2) – Mobilnost brezvrvičnega terminala (CTM) – Specifikacija funkcije krmiljenja storitev (SCF), stopnja 3 – SCF in funkcija klicno neodvisnih storitev (CUSF)/funkcija komutacije storitev (SSF) – Vmesnik SCF

General Information

• Status: Published
• Publication Date: 19-Sep-1999
• Technical Committee: SPS 3 4 - Intelligent Network
• Current Stage: 12 - Completion
• Due Date: 17-Sep-1999
• Completion Date: 20-Sep-1999
• Ref Project: SIST EN 301 143 V1.1.4:2005 - Intelligent Network (IN); Intelligent Network Application Protocol (INAP); Capability Set 2 (CS2); Cordless Terminal Mobility (CTM); Stage 3 specifications for Service Control Function (SCF); SCF and Call Unrelated Service Function (CUSF)/Service Switching Function (SSF); SCF interface

Standards Content (Sample)

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.Intelligent Network (IN); Intelligent Network Application Protocol (INAP); Capability Set 2 (CS2); Cordless Terminal Mobility (CTM); Stage 3 specifications for Service Control Function (SCF); SCF and Call Unrelated Service Function (CUSF)/Service Switching Function (SSF); SCF interface33.040.35Telefonska omrežjaTelephone networksICS:Ta slovenski standard je istoveten z:EN 301 143 Version 1.1.4SIST EN 301 143 V1.1.4:2005en01-januar-2005SIST EN 301 143 V1.1.4:2005SLOVENSKI
STANDARD
ETSIETSI EN 301 143 V1.1.4 (1999-09)2ReferenceDEN/SPS-03061 (al000ieo.PDF)KeywordsCCS, CS2, CTM, INAP, ISDN, protocol, SS7, INETSIPostal addressF-06921 Sophia Antipolis Cedex - FRANCEOffice address650 Route des Lucioles - Sophia AntipolisValbonne - FRANCETel.: [phone]
Fax: [phone]Siret N° 348 623 562 00017 - NAF 742 CAssociation à but non lucratif enregistrée à laSous-Préfecture de Grasse (06) N° 7803/[e-mail] copies of this ETSI deliverablecan be downloaded fromhttp://www.etsi.orgIf you find errors in the present document, send yourcomment to: [e-mail] NotificationNo part may be reproduced except as authorized by written permission.The copyright and the foregoing restriction extend to reproduction in all media.© European Telecommunications Standards Institute 1999.All rights reserved.SIST EN 301 143 V1.1.4:2005

ETSIETSI EN 301 143 V1.1.4 (1999-09)3ContentsIntellectual Property Rights.7Foreword.7Introduction.71Scope.82References.83Definitions and abbreviations.93.1Definitions.93.2Abbreviations.104General.114AProposed functional models for the CTM procedures.135CTM procedures.165.1Model.165.2Addressing.175.2.1General.175.2.2Addressing the SCF.185.2.2.1During incoming call set-up.185.2.2.2At location registration.195.2.2.3At outgoing call set-up.195.3Subscription registration in SCFmmSubscription.195.3.1Procedure description.195.3.1.1Introduction.195.3.1.2Normal operation.195.3.1.3Exceptional procedure.205.3.2SDL application procedures.205.4Key allocation.205.5Subscription deregistration.205.6Network authentication.215.7Terminal authentication.215.8Network initiated ciphering.215.9Location registration in the SCFmmVisited.215.10Location update in the SCFmmHome.215.10.1Procedure description.215.10.1.1Introduction.215.10.1.2Normal operation.225.10.1.3Exceptional procedure.225.10.2SDL application procedures.235.11Location cancellation in SCFmmVisited.235.12Location cancellation in the FT.235.13Restoration of location data in the SCFmmHome.235.13.1Procedure description.235.13.1.1Introduction.235.13.1.2Normal operation.235.13.1.3Exceptional procedure.245.13.2SDL application procedures.245.14Terminal authentication and/or ciphering.245.15Download of security data.245.15.1Procedure description.245.15.1.1Introduction.245.15.1.2Normal operation.255.15.1.3Exceptional procedure.255.15.2SDL application procedures.25SIST EN 301 143 V1.1.4:2005

ETSIETSI EN 301 143 V1.1.4 (1999-09)45.16Provide roaming number.255.16.1Procedure description.255.16.1.1Introduction.255.16.1.2Normal operation.265.16.1.3Exceptional procedure.265.16.2SDL application procedures.266Extensions of INAP.276.1SCF-SCF service to service extensions.276.1.1ASN.1 module.276.1.2Data types.276.1.3Error types.276.1.4Operation codes.276.1.5Error codes.286.1.6Classes.286.1.7Object identifiers.286.1.8Operations and arguments.296.1.9SSI-SCF-SCF interface.306.1.10TransferSTSIInformation operation.326.1.10.1Procedure descriptions.326.1.10.1.1General description.326.1.10.1.2Invoking entity (controlling SCF).336.1.10.1.2.1Normal procedure.336.1.10.1.2.2Error handling.336.1.10.1.3Invoking entity (supporting SCF).336.1.10.1.3.1Normal procedure.336.1.10.1.3.2Error handling.336.1.10.1.4Responding entity (supporting SCF).336.1.10.1.4.1Normal procedure.336.1.10.1.4.2Error handling.346.1.10.1.5Responding entity (controlling SCF).346.1.10.1.5.1Normal procedure.346.1.10.1.5.2Error handling.346.2Mapping of CTM operations to the extended INAP.347ASN.1 specification for CTM application.357.1Mobility Management Application Timers.387.2Application Timers.388Interworking with DSS1.388.1Description.388.1.1Detection point processing.398.1.2Receipt of DSS1+ messages.398.1.3Receipt of INAP operations.398.1.4Coding requirements.398.2Generic procedures.398.2.1USI handling procedures.408.2.1.1GFT-control input and output for CTM.408.2.1.2Receiving of DSS1+ operations / sending of UTSI information.408.2.1.3Receiving of STUI information / sending of DSS1+ operations.408.2.2INAP component handling procedures.418.3Call related issues.418.3.1Outgoing call.418.3.2Emergency call.418.3.3Incoming call.428.3.4Call release.428.4Call unrelated issues.428.4.1User initiated association.428.4.2Network initiated association.438.4.3Information exchange during the association.438.4.4Association release.43SIST EN 301 143 V1.1.4:2005

ETSIETSI EN 301 143 V1.1.4 (1999-09)5Annex A (informative):Message Sequence Charts.44A.1Subscription registration.45A.2Subscription deregistration.49A.3Location registration in the SCFmmVisited.52A.4Location update in the SCFmmHome.54A.5LocationCancellation in the SCFmmVisited.56A.6LocationCancellation in the FT.57A.7Download of security data.59A.8Restoration of location data in the SCFmmHome.60A.9Terminal authentication ciphering.62A.10Network Authentication.64Annex B (informative):Call control Message Sequence Charts.65B.1Outgoing call.65B.2Incoming call.70Annex C (informative):SDL model.73C.1System Type scf_scf_network.73C.2Block Type SCFVisCTM.79C.3Process Type SCF_SCF_CUSF_ASE_Visited.81C.4Procedure DetermineCtmArg.86C.5Procedure GetInvokeID.87C.6Process Type SCFmmVisitedApplication.88C.7Procedure LocationRegistrationSCF.89C.8Procedure LocationCancellationFT.91C.9Procedure DownloadSecurityData.93C.10Procedure TerminalAuthentication.95C.11Procedure Ciphering.97C.12Procedure IdentityRequest.99C.13Procedure SubscriptionRegistration.101C.14Procedure LocationRegistration.105C.15Procedure LocationRegistrationSuggest.108C.16Process Type SCFslVisitedApplication.110C.17Procedure ProvideRoamingNumber.111C.18Process Type SCF_SCF_ASE_Visited.112C.19Procedure DetermineCtmArg_SCFVis.117C.20Block Type SCFHomCTM.119C.21Process Type SCFmmHomeApplication.120C.22Procedure LocationRegistration_SCF.121SIST EN 301 143 V1.1.4:2005

ETSIETSI EN 301 143 V1.1.4 (1999-09)6C.23Procedure SubscriptionDeregistration_SCF.122C.24Procedure RestoreData_SCF.125C.25Procedure TerminalAuthentication_SCF.126C.26Procedure Ciphering_SCF.128C.27Procedure NetworkAuthentication_SCF.129C.28Procedure KeyAllocate_SCF.130C.29Procedure LocationCancellation_SCF.132C.30Procedure SubscriptionRegistration_SCF.134C.31Procedure DownloadSecurityData_SCF.136C.32Process Type SCFslHomeApplication.137C.33Procedure ProvideRoamingNumber_SCF.138Bibliography.140History.141SIST EN 301 143 V1.1.4:2005

ETSIETSI EN 301 143 V1.1.4 (1999-09)7Intellectual Property RightsIPRs essential or potentially essential to the present document may have been declared to ETSI. The informationpertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be foundin SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respectof ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web server(http://www.etsi.org/ipr).Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guaranteecan be given as to the existence of other IPRs not referenced in SR 000 314 (or the updates on the ETSI Web server)which are, or may be, or may become, essential to the present document.ForewordThis European Standard (Telecommunications series) has been produced by ETSI Technical Committee SignallingProtocols and Switching (SPS).National transposition datesDate of adoption of this EN:3 September 1999Date of latest announcement of this EN (doa):31 December 1999Date of latest publication of new National Standardor endorsement of this EN (dop/e):30 June 2000Date of withdrawal of any conflicting National Standard (dow):30 June 2000IntroductionThe Cordless Terminal Mobility (CTM) service phase 1 allows subscribers of cordless terminals to be mobile within andbetween networks. Where radio coverage is provided and the cordless terminal has appropriate access rights thesubscriber will be able to make calls from, and to receive calls at, any location within the fixed public and/or privatenetworks.The signalling procedures provided in the present document are supporting features required for CTM phase 1 on theSCF-SCF, SSF-SCF, and CUSF-SCF interfaces. The service to service capability extensions to the core IntelligentNetwork Application Part (INAP) CS2 SCF-SCF interface provided in the present document are used to support thefeatures required for CTM phase 1.SIST EN 301 143 V1.1.4:2005

ETSIETSI EN 301 143 V1.1.4 (1999-09)81ScopeThe present document analyses what the Cordless Terminal Mobility (CTM) specific specifications are within thegeneric parameters on the Service Control Function (SCF)-SCF, Call Unrelated Service Function (CUSF)-SCF andService Switching Function (SSF)-SCF interfaces of the ETSI core Intelligent Network Application Part (INAP). Thesespecifications ensure internetworking between CTM networks and the establishment of a multi-vendor environment forCTM.The generic INAP protocol contains generic parameters that can convey application specific information, such as for theCTM application. Detailed CTM specifications are described by the present document using the INAP SCF-SCF,CUSF-SCF and SSF-SCF interface capabilities. The SCF-Service Data Point (SDF) and SDF-SDF interfaces are notconsidered in the present document.2ReferencesThe following documents contain provisions which, through reference in this text, constitute provisions of the presentdocument.· References are either specific (identified by date of publication, edition number, version number, etc.) ornon-specific.· For a specific reference, subsequent revisions do not apply.· For a non-specific reference, subsequent revisions do apply.· A non-specific reference to an ETS shall also be taken to refer to later versions published as an EN with the samenumber.[1]EN 301 140-1 (V1.3): "Intelligent Network (IN); Intelligent Network Capability Set 2 (CS2);Intelligent Network Application Protocol (INAP); Part 1: Protocol specification".[2]EN 301 144-1: "Integrated Services Digital Network (ISDN); Digital Subscriber Signalling SystemNo. one (DSS1) protocol and Signalling System No.7 protocols; Signalling application for themobility management service on the alpha interface; Part 1: Protocol specification".[3]ITU-T Recommendation E.164: "The international public telecommunication numbering plan".[4]ETS 300 175-7 (1995): "Digital Enhanced Cordless Telecommunications (DECT); CommonInterface (CI); Part 7: Security features".[5]ETS 300 009-1: "Integrated Services Digital Network (ISDN); Signalling System No.7; SignallingConnection Control Part (SCCP) (connectionless and connection-oriented class 2) to supportinternational interconnection; Part 1: Protocol specification [ITU-T Recommendations Q.711 toQ.714 and Q.716 (1993), modified]".[6]ITU-T Recommendation E.212: "Identification plan for land mobile stations".[7]ITU-T Recommendation E.214: "Structure of the land mobile global title for the signallingconnection control part (SCCP)".SIST EN 301 143 V1.1.4:2005

ETSIETSI EN 301 143 V1.1.4 (1999-09)93Definitions and abbreviations3.1DefinitionsFor the purpose of the present document, the following terms and definitions apply:Authentication Code (AC): AC may be held in non-volatile memory within the PP or it may be manually entered bythe user when required for an authentication service. This depends on the application; see ETS 300 175-7 [4].access rights: indication that the cordless terminal has appropriate permission to use the CTM service.Access Rights Identity (ARI): identity which is globally unique to a service provider and which shows the access rightsrelated to the service provider.authentication: security mechanism allowing the verification of the provided identity.cordless terminal mobility: ability of a cordless terminal to be mobile within and between Fixed Parts. The mobilitymay be continuous while the terminal is accessing and using the telecommunication services offered by the network, andit may include the capability of the networks to keep track of the cordless terminal's location throughout the entirenetwork.CTM identity: identity by which a user is known to the CTM service providers and networks supporting CTM, and it isused for flexibility and security purposes. The CTM identity identifies a user unambiguously. The CTM identity doesnot need to be known by users.CTM number: number that uniquely and unambiguously identifies each CTM user. It is used by a calling party to reachthe CTM user. The number is independent of the calling terminal, network or service used and conforms to ITU-TRecommendation E.164 [3].DECT Paging: DECT procedure which establishes a link on DECT interface.Fixed Part (FP): physical grouping that contains all elements in the cordless network between the local network and thecordless terminal air interface.Fixed Termination (FT): logical group of functions that contains all of the Cordless Terminal (CT) Network specificprocesses and procedures on the fixed side of the air interface. A Fixed Radio Termination only includes elements thatare defined in the relevant CT specifications. This includes radio transmission elements (layer1) together with aselection of layer 2 and layer 3 elements.FT Address: address of the FT (i.e. an E.164 address).Portable Part (PP): physical grouping that contains all elements between the user and air interface. Portable Part is ageneric term that may describe one or several physical pieces.Portable Termination: logical group of functions that contains all of the CT processes and procedures on the portableside of the CT air interface. A Portable radio Termination only includes elements that are defined in the relevant CTspecification.RANDom challenge: this parameter is used for authentication (see ETS 300 175-7 [4]).RES1: see ETS 300 175-7 [4].RES2: see ETS 300 175-7 [4].RS: value used to establish authentication session keys, as defined in subclause 4.4.3 of ETS 300 175-7 [4].roaming: movement of the cordless terminal without a call in progress from one location area to another location areawithin the same and/or between different networks supporting the CTM service.service feature: specific aspect of a telecommunication service that can also be used in conjunction with othertelecommunication services as part of a commercial offering. It is either a core part of a telecommunication service or anoptional part offered as an enhancement to a telecommunication service.SIST EN 301 143 V1.1.4:2005

ETSIETSI EN 301 143 V1.1.4 (1999-09)10service profile: record containing all the service information related to a user.User Authentication Key (UAK): secret authentication data contained within the subscriber's registration data. It isuniquely associated with the particular subscriber (user) and the subscription. The UAK is held in non-volatile memorywithin the PP (or within a detachable DECT Authentication Module (DAM); see ETS 300 175-7 [4].3.2AbbreviationsFor the purposes of the present document, the following abbreviations apply:ACAllocation CodeACMAddress Complete MessageALSApplication Layer StructureARCAccess Right ClassARDAccess Right DetailsARIAccess Right IdentityASEApplication Service EntityBCSMBasic Call State MachineBCUSMBasic Call Unrelated State MachineCCAFCall Control Agent FunctionCCFCall Control FunctionCFNRCall Forwarding on No ReplyCLIRCalling Line Identification RestrictionCS2IN Capability Set No 2CTMCordless Terminal MobilityCTMidCTM identityCUCFCall Unrelated Control FunctionCUSFCall Unrelated Service FunctionDCKDerived Cipher KeyDECTDigital Enhanced Cordless TelecommunicationDNDistinguished NameDPDetection PointDSS1Digital Subscriber Signalling System 1ENEuropean NormFEFunctional EntityFSMFinite State MachineFPFixed PartFTFixed TerminationGAPGeneric Access ProfileGFPGeneric Functional ProtocolGFTGeneric Functional TransportGTAIGlobal Title Address IndicatorIAMInitial Address MessageIPEIInternational Portable Equipment IdentityIPUIInternational Portable User IdentityINIntelligent NetworkINAPIN Application ProtocolISUPISDN User PartLALocation AreaLALLocation Area LevelLCELink Control EntityLELocal ExchangeMCIDMalicious Call IDentificationMMMobility ManagementMMFMobility Management FunctionMSCMessage Sequence ChartNCICSNetworked Call Independent Connection-Oriented SignallingNFENetwork Facility ExtensionOCBOutgoing Call BarrityPARKPortable Access Right KeySIST EN 301 143 V1.1.4:2005

ETSIETSI EN 301 143 V1.1.4 (1999-09)11PIDProcess Instance IdentifierPLIPARK Length IndicatorPPPortable PartPTPortable TerminalPUNPortable User NumberPUTPortable User TypeRANDRANDom challengeRESRESponseRFPIRadio Fixed Part IdentityRSa value used to establish authentication session keysSACFSingle Association Control FunctionSCCPSignalling Connection Control PartSCFService Control FunctionSCFmmSCF mobility managementSCFmmHomeSCF mobility management HomeSCFmmVisitedSCF mobility management VisitedSCFslSCF service logicSCFslHomeSCF service logic HomeSCFslVisitedSCF service logic VisitedSCPService Control PointSDFService Data FunctionSDFmmService Data Function mobility managementSDFslService Data Function service logicSDLSpecification Description LanguageSDPService Data PointSLPIService Logic Program InstanceSMFService Management FunctionSSFService Switching FunctionSSIService to Service InformationSSPService Switching PointST"end of address" delimiter Sending TerminationSTUIService To User InformationTCAPTransaction Capabilities Application ProtocolTDPTrigger Detection PointTMNTelecommunications Management NetworkUAKUser Authentication KeyUSIUser to Service InformationUTSIUser To Service Information4GeneralIn this stage 3 description it is considered to separate the mobility management from the service control function. In thisrespect the SCF mobility management (SCFmm) (Visited and Home) handles the Mobility Management (MM)procedures in connection with the Call Unrelated Service Function (CUSF), and the SCF service logic (SCFsl) (Visitedand Home) handles the Call Control (e.g. provide roaming number) and CTM supplementary services (e.g. CTM-CLIR,CTM-MCID) in connection with the Service Switching Function (SSF).To optimize the hierarchical distribution of location information and authentication data across 3 levels (see figure 1), itshould be noted that in the figure the SCFmm to SDFsl and SCFsl and SDFmm interface are not required. Foroptimizing the hierarchical distribution of mobility management and Call Control information, it should be noted that forphase 1 SDFmm (Visited and Home) and SDFsl (Visited and Home) are assumed to be located in one node (SDFv andSDFh), and that SCFmm (Visited and Home) and SCFsl (Visited and Home) are assumed to be located in one node(SCFv and SCFh).SIST EN 301 143 V1.1.4:2005

ETSIETSI EN 301 143 V1.1.4 (1999-09)12 SDFslH SDFmmH SCFmmH SCFslH CTMslH MMFh SDFslV SDFmmV SCFmmV SCFslV CTMslV MMFv - MMFv Add ress - secret key - CTM service profile - FT Address - precalculated set of authentication parameters - user status CCF CUSF SSF FT - authentication data - cipher key SCFh SCFv SDFh SDFv seenoteseenoteNOTE:This interface is optional for phase 1, so it is not considered in this Stage 3 Description.Figure 1: CTM phase 1 architectureWith regard to the architecture to be considered, it is proposed to support in a first phase the topology for one singleoperator but it must be ensured that easy introduction of inter-networking between operators is accomplished withoutmajor impact in the network at the introduction of interworking. This principle will entail that the procedures are to beharmonized so that it can be avoided that extra procedures are required for knowing whether the ongoing procedure (e.g.location registration, call establishment, etc.) is handled as an intra- or inter-operator procedure; this should only be anaddressing issue.SIST EN 301 143 V1.1.4:2005

ETSIETSI EN 301 143 V1.1.4 (1999-09)134AProposed functional models for the CTM proceduresFigures 2, 3 and 4 propose the functional model for the CTM mobility management (see figure 2), outgoing CTM call(see figure 3) and incoming CTM call (see figure 4).SDFmmHSCFmmHMMFhSDFmmVSCFmmVMMFvCCFCUSFFTSDFmmVSCFmmVMMFvCCFCUSFFTCTM Mobility ManagementHome CTM domainVisited CTM domain 1 (old)Visited CTM domain 2 (new)abcfdeFigure 2: CTM mobility management functional domainsThe following procedures are examples of the use of the indicated interfaces:a)NCICS connection with CTM mobility management information (e.g. location registration).b)User to Service Information (USI) mechanism containing CTM mobility management information (e.g. locationregistration).c)Static triggering (e.g. subscription registration) or triggering based on International Portable User Identity (IPUI)(e.g. location update), Service to Service Information (SSI) mechanism containing CTM mobility managementinformation.d)Triggering of SCFmmVisited by SCFmmHome, SSI mechanism containing CTM mobility managementinformation (e.g. location cancellation).e)USI mechanism containing CTM mobility management information (e.g. location cancellation).f)NCICS connection with CTM mobility management information (e.g. location cancellation).SIST EN 301 143 V1.1.4:2005

ETSIETSI EN 301 143 V1.1.4 (1999-09)14SDFslHSDFmmHSCFmmHSCFslHSDFslVSDFmmVSCFmmVSCFslVCCFCUSFSSFFTPTOutgoing CTM callTerminating domainHome CTM domainOriginating Visited CTM domain 1(ld)abchfgkdijeCCFtFigure 3: Outgoing CTM call functional domainsDetection and handling of emergency call setup will be completely handled in the SCFmmVisited.The following procedures are examples of the use of the indicated interfaces:a)call setup;b)line base triggering;c)(optionally) initiation of authentication and/or ciphering procedures;d)fetching and reception of authentication data (SSI mechanism);e)authentication and/or ciphering, initiated by SCFmmVisited (USI mechanism);f)authentication and/or ciphering procedures and the result;g)result of authentication and/or ciphering;h)(optionally) action on the call setup based on the result of authentication;i)subsequent triggering initiated by SCFslVisited;j)triggering of SCFslHome based on SCFid and check of CTM supplementary services, (see note 1);k)call establishment to the CTM user.NOTE:Interface j1/j2 can be used in an inter-network case, interface j can be used in an intra-network case.SIST EN 301 143 V1.1.4:2005

ETSIETSI EN 301 143 V1.1.4 (1999-09)15CCFSSFIncoming CTM callOriginating domainHome CTM domainVisiting CTM domainSDFslVSDFmmVSCFmmVSCFslVCCFCUSFSSFFTPTCCFoabchfgklmdinojepqrSDFslHSDFmmHSCFmmHSCFslHFigure 4: Incoming CTM call functional domainsFor the incoming call procedure only the roaming number case is used.The following procedures are examples of the use of the indicated interfaces:a)CTM call setup to CTM user using CTM-number;b)triggering based on CTM-number;c)request roaming number (SSI mechanism);d)(optionally) fetching of user status (e.g. not_reachable);e)roaming number and user status provided (SSI mechanism);f)call establishment to CTM user using roaming number;g)call setup to visiting domain using roaming number;h)triggering of SCFslVisited;i)(optionally) initiation of authentication and/or ciphering procedures;j)fetching and reception of authentication data;k)authentication and/or ciphering procedures, initiated by SCFmmVisited;l)authentication and/or ciphering procedures, and result;m)report of authentication and/or ciphering to SCFmmVisited;n)(optionally) action on call setup based on result of authentication and/or ciphering;o)call establishment to CTM user;SIST EN 301 143 V1.1.4:2005

ETSIETSI EN 301 143 V1.1.4 (1999-09)16p)call setup to FT;q)report of call setup;r)report of events to SCFslHome to check CTM supplementary services.A CTM user to CTM user call shall be a combination of a CTM outgoing call and a CTM incoming call, as they arepresented in the figures.5CTM procedures5.1ModelThe SDL model of the CTM network is included to the present document as an informative part of the standard inannex C. This subclause provides a short introduction to the SDL model.The SDL diagrams reflect an Application Layer Structure (ALS) where the SACF performs the associationco-ordination function.The Visited SCF has four Application Service Entities (ASEs) namely:-SCFVis, having process type SCF_SSF_CUSF_ASE_Visited, for communication with the SSF / CUSF in theVisited Domain.-SCFmmVisApp, having process type SCFmmVisitedApplication, performing the service logic for the CTMPhase 1 mobility management call unrelated applications in the Visited SCF Domain.-SCFslVisApp, having process type SCFslVisitedApplication, performing the service logic for the CTM Phase 1call related applications in the Visited SCF Domain.-SCF_SCFVis, having process type SCF_SCF_ASE_Visited, for communication with the SCF in the HomeDomain.The Home Domain SCF has four Application Service Entities (ASEs) namely:-SCFHom, having process type SCF_SSF_CUSF_ASE_Home, for communication with the SSF / CUSF in theHome Domain.-SCFmmHomApp, having process type SCFmmHomeApplication, performing the service logic for the CTMPhase 1 mobility management call unrelated applications in the Home SCF Domain.-SCFslHomApp, having process type SCFslHomeApplication, performing the service logic for the CTM Phase 1call related applications in the Home SCF Domain.-SCF_SCFHom, having process type S
...