ETSI ETS 300 788 ed.1 (1997-07)

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.Digital Enhanced Cordless Telecommunications (DECT); Global System for Mobile communications (GSM); Integrated Services Digital Network (ISDN); DECT access to GSM via ISDN; Functional capabilities and information flows33.080Digitalno omrežje z integriranimi storitvami (ISDN)Integrated Services Digital Network (ISDN)33.070.50Globalni sistem za mobilno telekomunikacijo (GSM)Global System for Mobile Communication (GSM)33.070.30'(&7Digital Enhanced Cordless Telecommunications (DECT)ICS:Ta slovenski standard je istoveten z:ETS 300 788 Edition 13SIST ETS 300 788:2001en01-IHEUXDU-20013SIST ETS 300 788:2001SLOVENSKI
STANDARD



SIST ETS 300 788:2001



EUROPEANETS 300 788TELECOMMUNICATIONJuly 1997STANDARDSource: EP DECTReference: DE/DECT-010064ICS:33.020Key words:CTM, DECT, GSM, ISDN, mobility, radio, stage 2Digital Enhanced Cordless Telecommunications (DECT);Global System for Mobile communications (GSM);Integrated Services Digital Network (ISDN);DECT access to GSM via ISDN;Functional capabilities and information flowsETSIEuropean Telecommunications Standards InstituteETSI SecretariatPostal address: F-06921 Sophia Antipolis CEDEX - FRANCEOffice address: 650 Route des Lucioles - Sophia Antipolis - Valbonne - FRANCEX.400: c=fr, a=atlas, p=etsi, s=secretariat - Internet: secretariat@etsi.frTel.: +33 4 92 94 42 00 - Fax: +33 4 93 65 47 16Copyright Notification: No part may be reproduced except as authorized by written permission. The copyright and theforegoing restriction extend to reproduction in all media.© European Telecommunications Standards Institute 1997. All rights reserved.SIST ETS 300 788:2001



Page 2ETS 300 788: July 1997Whilst every care has been taken in the preparation and publication of this document, errors in content,typographical or otherwise, may occur. If you have comments concerning its accuracy, please write to"ETSI Editing and Committee Support Dept." at the address shown on the title page.SIST ETS 300 788:2001



Page 3ETS 300 788: July 1997ContentsForeword.51Scope.72Normative references.83Definitions and abbreviations.83.1Definitions.83.2Abbreviations.104Mobility management features.104.1Functional model.104.1.1Functional model description.104.1.2Description of functional entities.114.1.2.1Mobile user's MM agent, FE1.114.1.2.2Currently visited DECT access network MM control, FE2.114.1.2.3Global network MM control, FE3.114.1.2.4Previously visited DECT access network MM control, FE4.114.1.3Relationship of functional model to basic call functional model.114.2Information flows.114.2.1Definition of information flows.114.2.1.1ra-detach.124.2.1.2ra-identity-request.124.2.1.3ra-location-registration.134.2.1.4ra-temporary-identity-assign.144.2.1.5ra-temporary-identity-result.144.2.1.6ra-authenticate.144.2.1.7ra-ciphering-setting.154.2.1.8rb-detach.154.2.1.9rb-identity-request.154.2.1.10rb-location-update.164.2.1.11rb-temporary-identity-assign.164.2.1.12rb-temporary-identity-accept.164.2.1.13rb-authenticate.174.2.1.14rb-authenticate-reject.174.2.1.15rb-ciphering-setting.174.2.1.16rc-location-delete.174.2.2Relationship of information flows to basic call information flows.174.2.3Examples of information flow sequences.174.2.3.1Normal operation of MM features.184.2.3.2Exceptional operation of MM features.214.3Functional entity actions.214.3.1Functional entity actions of FE1.214.3.2Functional entity actions of FE2.224.3.3Functional entity actions of FE3.244.3.4Functional entity actions of FE4.254.4Functional entity behaviour.254.4.1Behaviour of FE1.254.4.2Behaviour of FE2.294.4.3Behaviour of FE3.324.4.4Behaviour of FE4.344.5Allocation of functional entities to physical equipment.344.6Interworking considerations.345Call handling.355.1Functional model.355.1.1Functional model description.35SIST ETS 300 788:2001



Page 4ETS 300 788: July 19975.1.2Description of FEs.355.2Information flows.355.2.1Definition of information flows.355.2.2Examples of information flow sequences.355.3Functional entity actions.355.4Functional entity behaviour.355.5Allocation of functional entities to physical equipment.365.6Interworking considerations.36History.37SIST ETS 300 788:2001



Page 5ETS 300 788: July 1997ForewordThis European Telecommunication Standard (ETS) has been produced by the Digital Enhanced CordlessTelecommunications (DECT) Project of the European Telecommunications Standards Institute (ETSI).Transposition datesDate of adoption:20 June 1997Date of latest announcement of this ETS (doa):31 October 1997Date of latest publication of new National Standardor endorsement of this ETS (dop/e):30 April 1998Date of withdrawal of any conflicting National Standard (dow):30 April 1998SIST ETS 300 788:2001



Page 6ETS 300 788: July 1997Blank pageSIST ETS 300 788:2001



Page 7ETS 300 788: July 19971ScopeThis European Telecommunication Standard (ETS) defines the functional capabilities and informationflows for the scenarios where Global System for Mobile communications (GSM) basic services areprovided via the Digital Enhanced Cordless Telecommunications System (DECT) air interface for the casethat the DECT network elements are interconnected with the GSM Public Land Mobile Network (PLMN)via Integrated Services Digital Network (ISDN) interfaces.The general description of the service requirements are specified in ETS 300 787 [1].The following core features are covered by this ETS:-outgoing calls;-emergency calls;-incoming calls;-location updating, location cancellation;-IMSI attach/detach;-TMSI reallocation procedure (temporary identity assign);-IMSI authentication;-ciphering;-identity request.Handover, which is another Mobility Management (MM) service, is outside the scope of this ETS.The service is produced in three stages according to the method specified inCCITT Recommendation I.130 [6]. Stage 2 identifies the Functional Entities (FEs) involved in the serviceand the information flows between them. This ETS is specified according to the methodology specified inCCITT Recommendation Q.65 [7].The purpose of the stage 2 specification is to guide and constrain the work on signalling protocols atstage 3, while fulfilling the requirements of stage 1. Stage 1 and stage 3 are defined in separatestandards.This ETS distinguishes DECT access networks from the global network. The DECT access networkprovides the point of attachment for the served user and ensures a transparent access to the GSMservices. The global network is the GSM PLMN or network of GSM PLMNs which provides the serveduser with the global service specified in this ETS. The specification of information flows within the globalnetwork (e.g. between Mobile Switching Centres (MSCs), Home Location Register (HLR) and VisitorLocation Register (VLR)) is beyond the scope of this ETS.Furthermore, conformance to this ETS is met by conforming to the stage 3 standards which fulfil therequirements of this ETS that are relevant to the equipment for which the stage 3 standard applies.Therefore no method of testing is provided for this ETS.SIST ETS 300 788:2001



Page 8ETS 300 788: July 19972Normative referencesThis ETS incorporates, by dated or undated reference, provisions from other publications. Thesenormative references are cited at the appropriate places in the text and the publications are listedhereafter. For dated references, subsequent amendments to or revisions of any of these publicationsapply to this ETS only when incorporated in it by amendment or revision. For undated references the latestedition of the publication referred to applies.[1]ETS 300 787: "Digital Enhanced Cordless Telecommunications / Global Systemfor Mobile communications (DECT/GSM); DECT access to GSM via IntegratedServices Digital Network (ISDN); General description of service requirements".[2]ETS 300 444: "Digital European Cordless Telecommunications (DECT); GenericAccess Profile (GAP)".[3]ETS 300 370: "Digital Enhanced Cordless Telecommunications / Global Systemfor Mobile communications (DECT/GSM) inter-working profile; Access andmapping (Protocol/procedure description for 3,1 kHz speech service)".[4]ETS 300 557: "Digital cellular telecommunications system (Phase 2); Mobile radiointerface layer 3 specification (GSM 04.08)".[5]ITU-T Recommendation Q.71 (1993): "ISDN circuit mode switched bearerservices".[6]CCITT Recommendation I.130 (1988): "Method for the characterization oftelecommunication services supported by an ISDN and network capabilities ofan ISDN".[7]CCITT Recommendation Q.65 (1988): "Stage 2 of the method for thecharacterization of services supported by an ISDN".[8]ETS 300 434-1: "Digital Enhanced Cordless Telecommunications (DECT) andIntegrated Services Digital Network (ISDN) interworking for end systemconfiguration; Part 1: Interworking specification".[9]ITU-T Recommendation Z.100: "CCITT Specification and description language(SDL)".3Definitions and abbreviations3.1DefinitionsFor the purposes of this ETS, the following definitions apply:DECT access network: Physical entity that contains all of the elements of a DECT Fixed Part (FP) andthat is attached to a GSM MSC.NOTE 1:A DECT access network provides a transparent access to the services of the GSMPLMN. This does however not exclude that it may in addition provide services andswitching capabilities to its own users.DECT Fixed Part (FP): A physical grouping that contains all of the elements in the DECT networkbetween the local network and the DECT air interface.NOTE 2:A DECT FP contains the logical elements of at least one fixed radio termination, plusadditional implementation specific elements.DECT location area: The domain in which a DECT Portable Part (PP) may receive and/or make calls asa result of a single location registration in the DECT access network.SIST ETS 300 788:2001



Page 9ETS 300 788: July 1997global network: The GSM PLMN or network of GSM PLMNs which provides the served user with theglobal service specified in this ETS.GSM location area: The domain in which a DECT PP may receive and/or make calls as a result of asingle location updating in the GSM network.NOTE 3:A GSM location area may cover more than one DECT location area.GSM service provider: An administration which offers global mobile telecommunication services to itssubscribers.GSM services: Services which are offered to the subscriber/user by a GSM Service Provider and whichare defined by the appropriate GSM specifications.location area: The domain in which a DECT PP may receive and/or make calls as a result of a singlelocation registration/updating in the network.location registration: The process whereby the position of a PP is determined to the level of one locationarea, and this position is updated in the network.location updating: The process whereby the position of a PP is determined to the level of one locationarea, and this position is updated in the network.NOTE 4:DECT and GSM respectively use the terms location registration and location updatingfor corresponding processes.MSC area: The MSC area is the part of the network covered by a MSC. A MSC area may consist of oneor several GSM location areas. A MSC area may also consist of one or several BSC areas and/or one orseveral DECT location areas.network: The totality of GSM and DECT access network elements through which the GSM serviceprovider provides its services to the served user.Public Land Mobile Network (PLMN): A PLMN is established and operated by an administration or forthe specific purpose of providing land mobile telecommunication services to the public. A PLMN may beregarded as an extension of a network (e.g. ISDN); it is a collection of MSC areas within a commonnumbering plan (e.g. same national destination code) and a common routeing plan. The MSCs are thefunctional interfaces between the fixed networks and a PLMN for call set-up. Functionally the PLMNs maybe regarded as independent telecommunication entities even though different PLMNs may beinterconnected through the ISDN/PISN and PDNs for forwarding of calls or network information. A similartype of interconnection may exist for the interaction between the MSCs of one PLMN.served user: The user of a DECT PP who has a subscription with the GSM service provider. The DECTPP accepts the GSM Subscriber Identity Module (SIM) and optionally the DECT DAM with a GSMapplication.NOTE 5:For the purpose of this ETS no distinction is made between the served user and itsassociated DECT PP.SIST ETS 300 788:2001



Page 10ETS 300 788: July 19973.2AbbreviationsFor the purposes of this ETS, the following abbreviations apply:CCCall Control (functional entity)CCACall Control Agent (functional entity)DECTDigital Enhanced Cordless TelecommunicationsFEFunctional EntityFPFixed PartGSMGlobal System for Mobile communicationsHLRHome Location RegisterIMEIInternational Mobile Equipment IdentityIMEISVIMEI Software Version numberIMSIInternational Mobile Subscriber Identity (GSM)IPEIInternational Portable Equipment IdentityIPUIInternational Portable User Identity (DECT)ISDNIntegrated Services Digital NetworkMMMobility ManagementMSCMobile Switching CentrePABXPrivate Automatic Branch ExchangePDNPacket Data NetworkPISNPrivate Integrated Services NetworkPLMNPublic Land Mobile NetworkPPPortable PartRANDRandom numberRESA Response calculated by a PPSDLSpecification and Description LanguageSIMSubscriber Identity ModuleSRESA GSM specific authentication RES calculated by the GSM SIM or the DAMTETerminal EquipmentTMSITemporary Mobile Subscriber Identity (GSM)TPUITemporary Portable User IdentityVLRVisitor Location Register4Mobility management features4.1Functional model4.1.1Functional model descriptionThe functional model for the MM features shall be as shown in figure 1.FE1FE2rarbFE3FE4rcFigure 1: Functional model for MM featuresThe FEs for the MM features shall be as follows:FE1:Mobile user's MM agent;FE2:Currently visited DECT access network MM control;FE3:Global network MM control;FE4:Previously visited DECT access network MM control.The following functional relationships shall exist between these functional entities:rabetween FE1 and FE2;rbbetween FE2 and FE3;rcbetween FE3 and FE4.SIST ETS 300 788:2001



Page 11ETS 300 788: July 19974.1.2Description of functional entities4.1.2.1Mobile user's MM agent, FE1This FE performs the user specific part of the MM features. It initiates and/or performs MM procedures onbehalf of the mobile user. FE1 is also responsible for passing information to the mobile user, if applicable.4.1.2.2Currently visited DECT access network MM control, FE2FE2 performs the DECT access network specific part of the MM features at the current location of theserved user. If involvement of the global network is required, FE2 cooperates with FE3 in providing therequired feature.FE2 receives information from FE1 when a MM procedure has been invoked. FE2 also can trigger FE1 toperform actions for MM procedures initiated by the network (either by FE2 itself or on initiative of FE3).NOTE:The possible information transfer within sub-entities in FE2 (e.g. when FE2 consists ofmore than one DECT location area) is out of the scope of this ETS.4.1.2.3Global network MM control, FE3FE3 performs the global network specific part of the MM features, i.e. the mobility actions which are ofglobal significance.FE3 receives information from FE2 that a MM procedure has been invoked. FE3 also can trigger FE1/FE2to perform actions for network initiated MM procedures.NOTE:The possible information transfer within sub-entities in FE3 (e.g. between MSC's, HLRand VLR) is out of the scope of this ETS.4.1.2.4Previously visited DECT access network MM control, FE4FE4 performs the DECT access network specific part of the MM features at the previous location of theserved user. FE4 receives information from FE3 that a served user is no longer in the domain controlledby FE4. On receipt of such information, FE4 will delete all temporary data stored for that user.NOTE:The possible information transfer within sub-entities in FE4 (e.g. when FE4 consists ofmore than one DECT location area) is out of the scope of this ETS.4.1.3Relationship of functional model to basic call functional modelThe functional model for MM features is independent of the functional model for basic call.4.2Information flows4.2.1Definition of information flowsIn the tables listing the elements in information flows, the column headed "Request" indicates which ofthese elements are mandatory (M) and which are optional (O) in a request/indication information flow, andthe column headed "Confirm" (confirmed information flows only) indicates which of these elements aremandatory (M) and which are optional (O) in a response/confirmation information flow.SIST ETS 300 788:2001



Page 12ETS 300 788: July 19974.2.1.1ra-detachra-detach is an unconfirmed information flow across ra from FE1 to FE2 to achieve a deactivation of theuser's terminal in the network.Table 1: Contents of ra-detachService elementRequestNotesPortable identityM-Contains the user's DECT identity.-If "temporary identity" is not available, the onlyallowed value of "portable identity" shall be of typeIPUI, with IPUI-type R, i.e. the IPUI shallincorporate an IMSI.-Other allowed values (of type TPUI, IPEI) may beused in the non-DECT/GSM interworking case orwhen "mobile identity" is also included.Temporary identityO-Contains the user's GSM temporary identity.-Allowed value is of type GSM TMSI.-Shall be included if previously received from thenetwork before.IPEI:International Portable Equipment Identity.IPUI:International Portable User Identity.TPUI:Temporary Portable User Identity.TMSI:Temporary Mobile Subscriber Identity.4.2.1.2ra-identity-requestra-identity-request is a confirmed information flow across ra between FE2 and FE1 which is used by FE2to obtain one of the user's terminal identities.Table 2: Contents of ra-identity-requestService elementRequestConfirmNotesIdentity typeM--This service element indicates thetype of identity requested by thenetwork.-For the scope of this ETS the onlyvalues of relevance are the types"Temporary identity (TMSI)", "user'sportable identity (IPUI)" and "portableequipment identity (IPEI)".Portable identity-O-Contains either the user's or theequipment's DECT identity (i.e. IPUIor IPEI).-If the requested Identity type is"User's portable identity", then thisservice element shall include a valueof type IPUI with IPUI-type R, i.e.shall include an IMSI.-If the requested Identity type is"Portable equipment identity", thisservice element shall include anIPEI-value.Temporary identity-O-Contains the user's temporary GSMidentity, the TMSI.-Shall be included if the requestedIdentity type is "Temporary identity",and if this identity is available.SIST ETS 300 788:2001



Page 13ETS 300 788: July 19974.2.1.3ra-location-registrationra-location-registration is a confirmed information flow across ra between FE1 and FE2 which is used toinform FE2 that the served user has roamed to another DECT location area or that a non-roaming serveduser is now able to receive incoming calls.Table 3: Contents of ra-location-registrationService elementRequestConfirmNotesPortable identityM--Contains the user's DECT identity.-Allowed value is of type IPUI, TPUI.The IPUI-type shall be R, i.e. the IPUIshall incorporate an IMSI.Fixed identityO-DECT specific identity which is not ofrelevance for DECT/GSM interworkingcase, and therefore out of the scope of thisETS.Location area identityOM-Can contain the DECT location areaidentity and the GSM location areaidentity.-In the "request/indication" thiselement may include the previousDECT location area. If available, alsothe GSM location area identity shallbe included.-In the "resp/conf" this element shallinclude the current DECT locationarea identity, and, if applicable andavailable, also the GSM location areaidentity.Use TPUI-OTo mandate the use of the temporaryidentity.Temporary identityOO-Contains the user's GSM temporaryidentity, the GSM TMSI.-This identity shall be included in the"request/indication" if previouslyreceived from the network.-It shall be included in the "resp/conf"if a new identity has been provided bythe global network.Cipher key sequence numberM-This parameter gives information to FE2 onthe ciphering key that is intended to be usedby FE1.Terminal / setup capabilitiesand model identifierO-May be needed to generate an IMEISV lateron.Result-MThis takes the values "accepted" and"rejected".Cause of rejection-O-Only present if result is "rejected".-At least the following values areallowed: "user identity not known","served user not permitted to registerin the current location area", "serveduser failed authentication", "locationregistration temporarily not possible".Duration-OIf present this element defines for how longat least the location registration andtemporary identity (if provided) are valid.SIST ETS 300 788:2001



Page 14ETS 300 788: July 19974.2.1.4ra-temporary-identity-assignra-temporary-identity-assign is a confirmed information flow across ra between FE2 and FE1 which isused to assign or delete a temporary identity to/from the user's terminal.Table 4: Contents of ra-temporary-identity-assignService ElementRequestConfirmNotesPortable identityO-This service element is not relevant for theDECT/GSM interworking case.GSM location area identityM-Contains the GSM location area for whichthe newly assigned temporary identity isvalid.Temporary identityM-Contains the user's temporary GSM identity(TMSI). For the DECT/GSM interworkingcase, this element is mandatory.Result-MAccepted or rejected.Cause of rejection-OMay be included if the result is "rejected".4.2.1.5ra-temporary-identity-resultra-temporary-identity-result is an unconfirmed information flow across ra from FE1 to FE2 which is used toconfirm the allocation of a (new) temporary identity to the user's terminal as a result of a successfullocation registration procedure.Table 5: Contents of ra-temporary-identity-resultService ElementRequestNotesResultMAccepted or rejected.Cause of rejectionOMay be included if the result is "rejected".4.2.1.6ra-authenticatera-authenticate is a confirmed information flow across ra between FE2 and FE1 which is used toauthenticate the mobile user.Table 6: Contents of ra-authenticateService ElementRequestConfirmNotesAuthentication typeM-Indicates "GSM authentication".Random number (RAND)M-Contains a random number, which is usedfor the calculation of the authenticationresult (RAND).Cipher key sequence numberM-This number must be used by the terminalfor association with the calculated cipherkey, which results from the auth/cipheringkey generation algorithm.Result-MIndicates whether the request forauthentication is accepted or rejected.Authentication resultOIncluded if the result is "accepted", containsthe calculated result of the authentication(RES).Cause of rejection-OMay be included if Result is "rejected", andindicates the reason why the authenticationrequest could not be accepted.SIST ETS 300 788:2001



Page 15ETS 300 788: July 19974.2.1.7ra-ciphering-settingra-ciphering-setting is a confirmed information flow across ra between FE2 and FE1 which is used toestablish ciphering for the radio link.Table 7: Contents of ra-ciphering-settingService ElementRequestConfirmNotesCipher key sequence numberM-Contains the number of the cipher keywhich shall be used to encrypt the radio linkThe cipher key number has been receivedpreviously in one of the followingprocedures: DECT location registration,paging, PP initiated call establishment orthe value has been given from the MSCduring a previous authentication procedure.The latest received value is used.Result-MAccepted or rejected.Cause of rejection-OMay be included if the result is "rejected".4.2.1.8rb-detachrb-detach is an unconfirmed information flow across rb from FE2 to FE3 to achieve a deactivation of theuser's terminal in the global network.Table 8: Contents of rb-detachService ElementRequestNotesTerminal capabilitiesMShall indicate a revision level of Phase 2 orhigher and the support of encryption A 5/1.Mobile identityM-Contains the user's GSM identity-Allowed values: GSM TMSI or IMSI-If TMSI is available, then this shall beused instead of IMSI.4.2.1.9rb-identity-requestrb-identity-request is a confirmed information flow across rb between FE3 and FE2 which is used by FE3to obtain one of the user's terminal identities.Table 9: Contents of rb-identity-requestService ElementRequestConfirmNotesMobile identityO-Identification of the user from which anadditional identity is requested.Mobile identity typeM-This takes one of the values IMSI, TMSI,IMEI, IMEISV.Mobile identity-MContains the user's GSM identity of the typeas requested.IMEI:International Mobile Equipment Identity.IMEISV:IMEI Software Version number.IMSI:International Mobile Subscriber Identity.TMSI:Temporary Mobile Subscriber Identity.SIST ETS 300 788:2001



Page 16ETS 300 788: July 19974.2.1.10rb-location-updaterb-location-update is a confirmed information flow across rb between FE2 and FE3 which is used to informFE3 that the served user has roamed to another GSM location area or that a non-roaming served user isnow ready to receive incoming calls.Table 10: Contents of rb-location-updateService ElementRequestConfirmNotesLocation update typeM-This takes the values "normal updating","periodic updating" and "IMSI attach".Cipher key sequenc
...