hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
17250281ac36b9d402e66d0077cd67fd | 100 974 | 17.3.2 Application context definitions | |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 17.3.2.1 Void | |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 17.3.2.2 Location Updating | This application context is used between HLR and VLR for location updating procedures. networkLocUpContext-v3 APPLICATION-CONTEXT -- Responder is HLR if Initiator is VLR INITIATOR CONSUMER OF { LocationUpdatingPackage-v3, DataRestorationPackage-v3} RESPONDER CONSUMER OF { SubscriberDataMngtPackage-v3 TracingPackage-v3}... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 17.3.2.3 Location Cancellation | This application context is used between HLR and VLR or between HLR and SGSN for location cancellation procedures. For the HLR - SGSN interface only version 3 of this application context is applicable. locationCancellationContext-v3 APPLICATION-CONTEXT -- Responder is VLR or SGSN if Initiator is HLR INITIATOR CONSUMER ... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 17.3.2.4 Roaming number enquiry | This application context is used between HLR and VLR for roaming number enquiry procedures. roamingNumberEnquiryContext-v3 APPLICATION-CONTEXT -- Responder is VLR if Initiator is HLR INITIATOR CONSUMER OF { RoamingNumberEnquiryPackage-v3} ::= {map-ac roamingNbEnquiry(3) version3(3)} The following application-context-na... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 17.3.2.5 Void | |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 17.3.2.6 Location Information Retrieval | This application-context is used between GMSC and HLR or between GMSC and NPLR when retrieving location information. For the GMSC - NPLR interface version 1, version 2 and version 3 of this application context are applicable. locationInfoRetrievalContext-v3 APPLICATION-CONTEXT -- Responder is HLR or NPLR if Initiator i... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 17.3.2.7 Call control transfer | This application context is used for the call control transfer procedure between the VMSC and the GMSC. callControlTransferContext-v4 APPLICATION-CONTEXT -- Responder is GMSC if Initiator is VMSC INITIATOR CONSUMER OF { CallControlTransferPackage-v4} ::= {map-ac callControlTransfer(6) version4(4)} The following applica... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 17.3.2.11 Location registers restart | This application context is used between HLR and VLR or between HLR and SGSN for location register restart procedures. For the HLR - SGSN interface version 1 and version 2 of this application context are applicable. resetContext-v2 APPLICATION-CONTEXT -- Responder is VLR or SGSN if Initiator is HLR INITIATOR CONSUMER O... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 17.3.2.12 Handover control | This application context is used for handover procedures between MSCs. handoverControlContext-v2 APPLICATION-CONTEXT -- Responder is MSCB if Initiator is MSCA INITIATOR CONSUMER OF { HandoverControlPackage-v2} ::= {map-ac handoverControl(11) version2(2)} The following application-context-name is assigned to the v1-equi... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 17.3.2.13 IMSI Retrieval | This application context is used for IMSI retrieval between HLR and VLR. imsiRetrievalContext-v2 APPLICATION-CONTEXT -- Responder is HLR if Initiator is VLR INITIATOR CONSUMER OF { IMSIRetrievalPackage-v2} ::= {map-ac imsiRetrieval(26) version2(2)} This application-context is v2 only. |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 17.3.2.14 Equipment Management | This application context is used for equipment checking between MSC and EIR or between SGSN and EIR. For the SGSN - EIR interface version 1 and version 2 of this application context are applicable: equipmentMngtContext-v2 APPLICATION-CONTEXT -- Responder is EIR if Initiator is MSC -- Responder is EIR if Initiator is SG... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 17.3.2.15 Information retrieval | This application context is used for authentication information retrieval between HLR and VLR or between HLR and SGSN. For the HLR - SGSN interface version 1 and version 2 of this application context are applicable. infoRetrievalContext-v2 APPLICATION-CONTEXT -- Responder is HLR if Initiator is VLR -- Responder is HLR ... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 17.3.2.16 Inter-VLR information retrieval | This application context is used for information retrieval between VLRs. interVlrInfoRetrievalContext-v2 APPLICATION-CONTEXT -- Responder is VLR if Initiator is VLR INITIATOR CONSUMER OF { InterVlrInfoRetrievalPackage-v2} ::= {map-ac interVlrInfoRetrieval(15) version2(2)} The v1-equivalent application-context is: -- Re... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 17.3.2.17 Stand Alone Subscriber Data Management | This application context is used for stand alone subscriber data management between HLR and VLR or between HLR and SGSN. For the HLR - SGSN interface only version 3 of this application context is applicable: subscriberDataMngtContext-v3 APPLICATION-CONTEXT -- Responder is VLR or SGSN if Initiator is HLR INITIATOR CONSU... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 17.3.2.18 Tracing | This application context is used between HLR and VLR or between HLR and SGSN for stand alone tracing control procedures: For the HLR - SGSN interface version 1, version 2 and version 3 of this application context are applicable. tracingContext-v3 APPLICATION-CONTEXT -- Responder is VLR or SGSN if Initiator is HLR INITI... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 17.3.2.19 Network functional SS handling | This application context is used for functional-like SS handling procedures between VLR and HLR. networkFunctionalSsContext-v2 APPLICATION-CONTEXT -- Responder is HLR, Initiator is VLR INITIATOR CONSUMER OF { FunctionalSsPackage-v2} ::= {map-ac networkFunctionalSs(18) version2(2)} ETSI ETSI TS 100 974 V7.3.0 (2000-02) ... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 17.3.2.20 Network unstructured SS handling | This application context is used for handling stimuli-like procedures between HLR and VLR, and between the HLR and gsmSCF. networkUnstructuredSsContext-v2 APPLICATION-CONTEXT -- Responder is HLR, Initiator is VLR -- Responder is VLR, Initiator is HLR -- Responder is gsmSCF, Initiator is HLR -- Responder is HLR, Initiat... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 17.3.2.21 Short Message Gateway | This application context is used for short message gateway procedures. shortMsgGatewayContext-v3 APPLICATION-CONTEXT -- Responder is HLR if Initiator is GMSC INITIATOR CONSUMER OF { ShortMsgGatewayPackage-v3} ::= {map-ac shortMsgGateway(20) version3(3)} The following application-context-name is assigned to the v2-equiv... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 17.3.2.22 Mobile originating Short Message Relay | This application context is used between MSC and IWMSC or between SGSN and IWMSC for mobile originating short message relay procedures. For the SGSN - IWMSC interface version 1, version 2 and version 3 of this application context are applicable. shortMsgMO-RelayContext-v3 APPLICATION-CONTEXT -- Responder is IWMSC if In... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 17.3.2.23 Void | |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 17.3.2.24 Short message alert | This application context is used for short message alerting procedures. shortMsgAlertContext-v2 APPLICATION-CONTEXT -- Responder is IWMSC if Initiator is HLR INITIATOR CONSUMER OF { AlertingPackage-v2} ::= {map-ac shortMsgAlert(23) version2(2)} The following application-context-name is symbolically assigned to the v1-e... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 17.3.2.25 Short message waiting data management | This application context is used between VLR and HLR or between SGSN and HLR for short message waiting data management procedures. For the SGSN - HLR interface only version 3 of this application context is applicable. mwdMngtContext-v3 APPLICATION-CONTEXT -- Responder is HLR if Initiator is SGSN -- Responder is HLR if ... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 17.3.2.26 Mobile terminating Short Message Relay | This application context is used between GMSC and MSC or between GMSC and SGSN for mobile terminating short message relay procedures. For the GMSC - SGSN interface version 2and version 3 of this application context and the equivalent version 1 application context are applicable. shortMsgMT-RelayContext-v3 APPLICATION-C... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 17.3.2.27 MS purging | This application context is used between HLR and VLR or between HLR and SGSN for MS purging procedures. For the SGSN - HLR interface only version 3 of this application context is applicable. msPurgingContext-v3 APPLICATION-CONTEXT -- Responder is HLR if Initiator is VLR -- Responder is HLR if Initiator is SGSN INITIATO... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 17.3.2.28 Subscriber information enquiry | This application context is used between HLR and VLR for subscriber information enquiry procedures. subscriberInfoEnquiryContext-v3 APPLICATION-CONTEXT -- Responder is VLR if Initiator is HLR INITIATOR CONSUMER OF { SubscriberInformationEnquiryPackage-v3} ::= {map-ac subscriberInfoEnquiry(28) version3(3)} This applicat... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 17.3.2.29 Any time information enquiry | This application context is used between gsmSCF and HLR for any time information enquiry procedures. anyTimeInfoEnquiryContext-v3 APPLICATION-CONTEXT -- Responder is HLR if Initiator is gsmSCF INITIATOR CONSUMER OF { AnyTimeInformationEnquiryPackage-v3} ::= {map-ac anyTimeInfoEnquiry(29) version3(3)} This application-c... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 17.3.2.30 Group Call Control | This application context is used between anchor MSC and relay MSC for group call and broadcast call procedures. groupCallControlContext-v3 APPLICATION-CONTEXT -- Responder is relay MSC if Initiator is anchor MSC INITIATOR CONSUMER OF { GroupCallControlPackage-v3} ::= {map-ac groupCallControl(31) version3(3)} This appli... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 17.3.2.31 Provide SIWFS Number | This application context is used for activation or modification of SIWF resources. sIWFSAllocationContext-v3 APPLICATION-CONTEXT -- Responder is SIWF if Initiater is VMSC INITIATOR CONSUMER OF { ProvideSIWFSNumberPackage-v3, SIWFSSignallingModifyPackage-v3} ::= {map-ac sIWFSAllocation (12) version3(3)} This application... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 17.3.2.32 Gprs Location Updating | This application context is used between HLR and SGSN for gprs location updating procedures. gprsLocationUpdateContext-v3 APPLICATION-CONTEXT -- Responder is HLR if Initiator is SGSN INITIATOR CONSUMER OF { GprsLocationUpdatingPackage-v3} RESPONDER CONSUMER OF { SubscriberDataMngtPackage-v3 TracingPackage-v3} ::= {map-... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 17.3.2.33 Gprs Location Information Retreival | This application context is used between HLR and GGSN when retrieving gprs location information. gprsLocationInfoRetrievalContext-v3 APPLICATION-CONTEXT -- Responder is HLR if Initiator is GGSN INITIATOR CONSUMER OF { GprsInterrogationPackage-v3} ::= {map-ac gprsLocationInfoRetrieval(33) version3(3)} This application-c... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 17.3.2.34 Failure Reporting | This application context is used between HLR and GGSN to inform that network requested PDP-context activation has failed. failureReportContext-v3 APPLICATION-CONTEXT -- Responder is HLR if Initiator is GGSN INITIATOR CONSUMER OF { FailureReportingPackage-v3} ::= {map-ac failureReport(34) version3(3)} This application-c... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 17.3.2.35 GPRS Notifying | This application context is used between HLR and GGSN for notifying that GPRS subscriber is present again. gprsNotifyContext-v3 APPLICATION-CONTEXT -- Responder is GGSN if Initiator is HLR INITIATOR CONSUMER OF { GprsNotifyingPackage-v3} ::= {map-ac gprsNotify(35) version3(3)} This application-context is v3 only. |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 17.3.2.36 Supplementary Service invocation notification | This application context is used between MSC and gsmSCF for Supplementary Service invocation notification procedures. ss-InvocationNotificationContext-v3 APPLICATION-CONTEXT -- Responder is gsmSCF, Initiator is MSC INITIATOR CONSUMER OF { SS-InvocationNotificationPackage-v3} ::= {map-ac ss-InvocationNotification(36) ve... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 17.3.2.37 Reporting | This application context is used between HLR and VLR for reporting procedures. reportingContext-v3 APPLICATION-CONTEXT -- Responder is VLR if Initiator is HLR -- Responder is HLR if Initiator is VLR INITIATOR CONSUMER OF { SetReportingStatePackage-v3, StatusReportPackage-v3, RemoteUserFreePackage-v3} RESPONDER CONSUMER... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 17.3.2.38 Call Completion | This application context is used between VLR and the HLR for subscriber control of call completion services. callCompletionContext-v3 APPLICATION-CONTEXT -- Responder is HLR if Initiator is VLR INITIATOR CONSUMER OF { CallCompletionPackage-v3} ::= {map-ac callCompletion(8) version3(3)} This application-context is v3 on... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 17.3.2.39 Location Service Gateway | This application context is used for location service gateway procedures. locationSvcGatewayContext-v3 APPLICATION-CONTEXT -- Responder is HLR if Initiator is GMLC INITIATOR CONSUMER OF { locationSvcGatewayPackage-v3} ::= {map-ac locationSvcGateway(37) version3(3)} 17.3.2.40 Location Service Enquiry This application co... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 17.3.2.41 Void | |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 17.3.2.42 Void | |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 17.3.2.43 Void | |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 17.3.3 ASN.1 Module for application-context-names | The following ASN.1 module summarizes the application-context-name assigned to MAP application-contexts. MAP-ApplicationContexts { 1 ccitt identified-organization (4) etsi (0) mobileDomain (0) 2 gsm-Network (1) modules (3) map-ApplicationContexts (2) version5 (5)} 3 4 DEFINITIONS 5 6 ETSI ETSI TS 100 974 V7.3.0 (2000-0... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 17.4 MAP Dialogue Information | MAP-DialogueInformation { 1 ccitt identified-organization (4) etsi (0) mobileDomain (0) 2 gsm-Network (1) modules (3) map-DialogueInformation (3) version5 (5)} 3 4 DEFINITIONS 5 6 IMPLICIT TAGS 7 8 ::= 9 10 BEGIN 11 12 EXPORTS 13 map-DialogueAS, 14 MAP-DialoguePDU 15 ; 16 17 IMPORTS 18 gsm-NetworkId, 19 as-Id 20 FROM M... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 17.5 MAP operation and error codes | MAP-Protocol { 1 ccitt identified-organization (4) etsi (0) mobileDomain (0) 2 gsm-Network (1) modules (3) map-Protocol (4) version5 (5)} 3 4 DEFINITIONS 5 6 ::= 7 8 BEGIN 9 10 IMPORTS 11 UpdateLocation, 12 CancelLocation, 13 PurgeMS, 14 SendIdentification, 15 UpdateGprsLocation, 16 PrepareHandover, 17 SendEndSignal, 1... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 17.6 MAP operation and error types | |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 17.6.1 Mobile Service Operations | MAP-MobileServiceOperations { 1 ccitt identified-organization (4) etsi (0) mobileDomain (0) 2 gsm-Network (1) modules (3) map-MobileServiceOperations (5) 3 version5 (5)} 4 5 DEFINITIONS 6 7 ::= 8 9 BEGIN 10 11 EXPORTS 12 13 -- location registration operations 14 UpdateLocation, 15 CancelLocation, 16 PurgeMS, 17 SendIde... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 17.6.2 Operation and Maintenance Operations | MAP-OperationAndMaintenanceOperations { 1 ccitt identified-organization (4) etsi (0) mobileDomain (0) 2 gsm-Network (1) modules (3) map-OperationAndMaintenanceOperations (6) 3 version5 (5)} 4 5 DEFINITIONS 6 7 ::= 8 9 BEGIN 10 11 EXPORTS 12 ActivateTraceMode, 13 DeactivateTraceMode, 14 SendIMSI 15 ; 16 17 IMPORTS 18 OP... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 17.6.3 Call Handling Operations | MAP-CallHandlingOperations { 1 ccitt identified-organization (4) etsi (0) mobileDomain (0) 2 gsm-Network (1) modules (3) map-CallHandlingOperations (7) 3 version5 (5)} 4 5 DEFINITIONS 6 7 ::= 8 ETSI ETSI TS 100 974 V7.3.0 (2000-02) 283 (GSM 09.02 version 7.3.0 Release 1998) 9 BEGIN 10 11 EXPORTS 12 SendRoutingInfo, 13 ... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 17.6.4 Supplementary service operations | MAP-SupplementaryServiceOperations { 1 ccitt identified-organization (4) etsi (0) mobileDomain (0) 2 gsm-Network (1) modules (3) map-SupplementaryServiceOperations (8) 3 version5 (5)} 4 5 DEFINITIONS 6 7 ::= 8 9 BEGIN 10 11 EXPORTS 12 RegisterSS, 13 EraseSS, 14 ActivateSS, 15 DeactivateSS, 16 InterrogateSS, 17 ProcessU... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 17.6.5 Short message service operations | MAP-ShortMessageServiceOperations { 1 ccitt identified-organization (4) etsi (0) mobileDomain (0) 2 gsm-Network (1) modules (3) map-ShortMessageServiceOperations (9) 3 version5 (5)} 4 5 DEFINITIONS 6 7 ::= 8 9 BEGIN 10 11 EXPORTS 12 SendRoutingInfoForSM, 13 MO-ForwardSM, 14 MT-ForwardSM, 15 ReportSM-DeliveryStatus, 16 ... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 17.6.6 Errors | MAP-Errors { 1 ccitt identified-organization (4) etsi (0) mobileDomain (0) 2 gsm-Network (1) modules (3) map-Errors (10) version5 (5)} 3 4 DEFINITIONS 5 6 ::= 7 8 BEGIN 9 10 EXPORTS 11 12 -- generic errors 13 SystemFailure, 14 DataMissing, 15 UnexpectedDataValue, 16 FacilityNotSupported, 17 IncompatibleTerminal, 18 Res... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 17.6.7 Group Call operations | MAP-Group-Call-Operations { 1 ccitt identified-organization (4) etsi (0) mobileDomain (0) 2 gsm-Network (1) modules (3) map-Group-Call-Operations (22) 3 version5 (5)} 4 5 DEFINITIONS 6 7 ::= 8 9 BEGIN 10 11 EXPORTS 12 PrepareGroupCall, 13 SendGroupCallEndSignal, 14 ForwardGroupCallSignalling, 15 ProcessGroupCallSignall... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 17.7 MAP constants and data types | |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 17.7.1 Mobile Service data types | MAP-MS-DataTypes { 1 ccitt identified-organization (4) etsi (0) mobileDomain (0) 2 gsm-Network (1) modules (3) map-MS-DataTypes (11) version5 (5)} 3 4 DEFINITIONS 5 6 IMPLICIT TAGS 7 8 ::= 9 10 BEGIN 11 12 EXPORTS 13 14 -- location registration types 15 UpdateLocationArg, 16 UpdateLocationRes, 17 CancelLocationArg, 18 ... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 17.7.2 Operation and maintenance data types | MAP-OM-DataTypes { 1 ccitt identified-organization (4) etsi (0) mobileDomain (0) 2 gsm-Network (1) modules (3) map-OM-DataTypes (12) version5 (5)} 3 4 DEFINITIONS 5 6 IMPLICIT TAGS 7 8 ::= 9 10 BEGIN 11 12 ETSI ETSI TS 100 974 V7.3.0 (2000-02) 314 (GSM 09.02 version 7.3.0 Release 1998) EXPORTS 13 ActivateTraceModeArg, ... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 17.7.3 Call handling data types | MAP-CH-DataTypes { 1 ccitt identified-organization (4) etsi (0) mobileDomain (0) 2 gsm-Network (1) modules (3) map-CH-DataTypes (13) version5 (5)} 3 4 DEFINITIONS 5 6 IMPLICIT TAGS 7 8 ::= 9 10 BEGIN 11 12 EXPORTS 13 SendRoutingInfoArg, 14 SendRoutingInfoRes, 15 ProvideRoamingNumberArg, 16 ProvideRoamingNumberRes, 17 R... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 17.7.4 Supplementary service data types | MAP-SS-DataTypes { 1 ccitt identified-organization (4) etsi (0) mobileDomain (0) 2 gsm-Network (1) modules (3) map-SS-DataTypes (14) version5 (5)} 3 4 DEFINITIONS 5 6 IMPLICIT TAGS 7 8 ::= 9 10 BEGIN 11 12 EXPORTS 13 RegisterSS-Arg, 14 SS-Info, 15 SS-Status, 16 SS-SubscriptionOption, 17 SS-ForBS-Code, 18 InterrogateSS-... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 17.7.5 Supplementary service codes | MAP-SS-Code { 1 ccitt identified-organization (4) etsi (0) mobileDomain (0) 2 gsm-Network (1) modules (3) map-SS-Code (15) version5 (5)} 3 4 DEFINITIONS 5 6 ::= 7 8 BEGIN 9 10 ETSI ETSI TS 100 974 V7.3.0 (2000-02) 325 (GSM 09.02 version 7.3.0 Release 1998) SS-Code ::= OCTET STRING (SIZE (1)) 11 -- This type is used to ... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 17.7.6 Short message data types | MAP-SM-DataTypes { 1 ccitt identified-organization (4) etsi (0) mobileDomain (0) 2 gsm-Network (1) modules (3) map-SM-DataTypes (16) version5 (5)} 3 4 DEFINITIONS 5 6 IMPLICIT TAGS 7 8 ::= 9 10 BEGIN 11 12 EXPORTS 13 RoutingInfoForSM-Arg, 14 RoutingInfoForSM-Res, 15 MO-ForwardSM-Arg, 16 MO-ForwardSM-Res, 17 MT-ForwardS... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 17.7.7 Error data types | MAP-ER-DataTypes { 1 ccitt identified-organization (4) etsi (0) mobileDomain (0) 2 gsm-Network (1) modules (3) map-ER-DataTypes (17) version5 (5)} 3 4 DEFINITIONS 5 6 IMPLICIT TAGS 7 8 ::= 9 10 BEGIN 11 12 EXPORTS 13 RoamingNotAllowedParam, 14 CallBarredParam, 15 CUG-RejectParam, 16 SS-IncompatibilityCause, 17 PW-Regis... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 17.7.8 Common data types | MAP-CommonDataTypes { 1 ccitt identified-organization (4) etsi (0) mobileDomain (0) 2 gsm-Network (1) modules (3) map-CommonDataTypes (18) version5 (5)} 3 4 DEFINITIONS 5 6 IMPLICIT TAGS 7 8 ::= 9 10 BEGIN 11 12 EXPORTS 13 14 -- general data types and values 15 AddressString, 16 ISDN-AddressString, 17 maxISDN-AddressLe... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 17.7.9 Teleservice Codes | MAP-TS-Code { 1 ccitt identified-organization (4) etsi (0) mobileDomain (0) 2 gsm-Network (1) modules (3) map-TS-Code (19) version5 (5)} 3 4 DEFINITIONS 5 6 ::= 7 8 BEGIN 9 10 TeleserviceCode ::= OCTET STRING (SIZE (1)) 11 -- This type is used to represent the code identifying a single 12 -- teleservice, a group of tel... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 18 General on MAP user procedures | |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 18.1 Introduction | Clauses 18 to 25 describe the use of MAP services for GSM signalling procedures. GSM signalling procedures may involve one or several interfaces running one or several application protocols. The present document addresses only the signalling procedures which require at least the use of one MAP service. When a signallin... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 18.2 Common aspects of user procedure descriptions | |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 18.2.1 General conventions | For each signalling procedure the present document provides a brief textual overview accompanied by a flow diagram which represent the functional interactions between system components. Functional interactions are labelled using the MAP service name when the interaction results from a service request or by this service... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 18.2.2 Naming conventions | Events related to MAP are represented by MAP service primitives. The signal names used in the SDL diagrams are derived from the service primitive names defined in clauses 7 to 12, with some lexical transformations for readability and parsability purposes (blanks between words are replaced by underscores, the first lett... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 18.2.3 Convention on primitives parameters | |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 18.2.3.1 Open service | When the originating and destination reference parameters shall be included in the MAP-OPEN request primitive, their value are indicated as a comment to the signal which represents this primitive. |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 18.2.3.2 Close service | When a pre-arranged released is requested, a comment is attached to the signal which represents the MAP-CLOSE request primitive. In the absence of comment, a normal release is assumed. ETSI ETSI TS 100 974 V7.3.0 (2000-02) 353 (GSM 09.02 version 7.3.0 Release 1998) |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 18.2.4 Version handling at dialogue establishment | Unless explicitly indicated in subsequent subclauses, the following principles regarding version handling procedures at dialogue establishment are applied by the MAP-user: |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 18.2.4.1 Behaviour at the initiating side | When a MAP user signalling procedure has to be executed, the MAP-user issues a MAP-OPEN request primitive with an appropriate application-context-name. If several names are supported (i.e. several versions) a suitable one is selected using the procedures described in clause 5. If version 2 is selected and a MAP-CLOSE C... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 18.2.4.2 Behaviour at the responding side | On receipt of a MAP-OPEN indication primitive, the MAP-User analyses the application-context-name. If it refers to a version one context, the associated V1 procedure is executed; if it refers to a version two context, the associated V2 procedure is executed, otherwise the associated V3 procedure is executed. |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 18.2.5 Abort Handling | Unless explicitly indicated in subsequent subclauses, the following principles are applied by the MAP-user regarding abort handling procedures: On receipt of a MAP-P-ABORT indication or MAP-U-ABORT Indication primitive from any MAP-provider invocation, the MAP-User issues a MAP-U-ABORT Request primitive to each MAP-pro... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 18.2.6 SDL conventions | The MAP SDLs make use of a number of SDL concepts and conventions, where not all of them may be widely known. Therefore, this subclause outlines the use of a few concepts and conventions to improve understanding of the MAP SDLs. The MAP User SDLs make use of SDL Processes, Procedures and Macros. Processes are independe... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 18.3 Interaction between MAP Provider and MAP Users | Each MAP User is defined by at least one SDL process. On the dialogue initiating side the MAP User will create a new instance of a MAP Provider implicit by issuing a MAP-OPEN request. This instance corresponds to a TC Dialogue and lives as long as the dialogue exists (see also subclause 14.3). There is a fix relation b... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 19 Mobility procedures | |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 19.1 Location management Procedures | For non-GPRS subscribers, this subclause comprises a number of processes to handle the mobile nature of the subscriber. The processes will be addressed by SCCP Sub-System Number (MSC, VLR or HLR) and the Application Context. The following processes are defined in this subclause: Process Update Location Area: Initiator:... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 19.1.1 Location updating | |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 19.1.1.1 General | The location updating procedure is used to update the location information held in the network. For GPRS subscribers, this procedure describes also updating of the SGSN and, if Gs interface is installed, updating of the VLR in combination with an attach/routing area updating in the SGSN. This location information is us... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 19.1.1.2 Detailed procedure in the MSC | Figure 19.1.1/4 shows the MSC process for location register updating, containing macro calls for: Receive_Open_Cnf subclause 25.1; Authenticate_MSC subclause 25.5; Check_IMEI_MSC subclause 25.6; Obtain_IMSI_MSC subclause 25.8; Trace_Subscriber_Activity_MSC subclause 25.9. For structuring purposes, the second part of th... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 19.1.1.3 Detailed procedure in the VLR | Figure 19.1.1/6 shows the process for location updating in the VLR. The following general macros are used: Receive_Open_Ind subclause 25.1; Receive_Open_Cnf subclause 25.1; Authenticate_VLR subclause 25.5; Check_IMEI_VLR subclause 25.6; Insert_Subscriber_Data_VLR subclause 25.7; Obtain_IMSI_VLR to request the IMSI for ... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 19.1.1.4 Detailed procedure in the HLR | When addressed by the VLR, the following macros are used by the process Update_Location_HLR: - Receive_Open_Ind, defined in subclause 25.1; - Check_indication, defined in subclause 25.2; - Insert_Subs_Data_Framed_HLR, described in subclause 19.4.1; - Control_Tracing_HLR, described in subclause 25.9; and the processes C... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 19.1.1.5 Send Identification | |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 19.1.1.5.1 General | This service is invoked by a VLR when it receives a MAP_UPDATE_LOCATION_AREA indication containing a LAI indicating that the subscriber was registered in a different VLR (henceforth called the Previous VLR, PVLR). If the identity of the PVLR is derivable for the VLR (usually if both are within the same network), the IM... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 19.1.1.5.2 Detailed procedure in the VLR | The VLR procedure is part of the location area updating process described in subclause 19.1.1.3, see also figure 19.1.1/6 sheet 3. |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 19.1.1.5.3 Detailed procedure in the PVLR | On receipt of a dialogue request for the Send Identification procedure, (see Receive_Open_Ind macro in subclause 25.1), the PVLR will: - terminate the procedure in case of parameter problems; - revert to the MAP version Vr procedure in case the VLR indicated version Vr protocol; or - continue as below, if the dialogue ... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 19.1.1.6 The Process Update Location VLR | This process is started by some other MAP user process in case the HLR need to be updated due to previous network failure. It is invoked when the subscriber accesses the network, e.g. for mobile originated call set-up, response to paging or supplementary services handling. Here, location updating consists only of invok... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 19.1.1.7 The Process Subscriber Present HLR | The process Subscriber Present HLR is started by the location updating process in HLR to perform actions required for short message alerting. The process checks the Message Waiting Data flag, and if this is set, the macro Alert_Service_Centre_HLR defined in subclause 25.10 is invoked. This macro will alert all service ... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 19.1.1.8 Detailed procedure in the SGSN | Figure 19.1.1/20 shows the MAP process for updating of the SGSN. The following general macros are used: Receive_Open_Cnf subclause 25.1; Insert_Subscriber_Data_SGSN subclause 25.7; Activate_Tracing_SGSN subclause 25.9; The location updating process The MAP process receives an « Update HLR request » from the relevant pr... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 19.1.2 Location Cancellation | |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 19.1.2.1 General | The purpose of this process is to delete a subscriber's record from a previous visitor location register after she has registered with a new visitor location register. Also this process is used to delete a subscriber's record from a old SGSN after she has registered with a SGSN. The procedure may also be used if the su... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 19.1.2.2 Detailed procedure in the HLR | The location cancellation process is started by an external process as stated above. The HLR opens a dialogue with the VLR or with the SGSN whose identity is contained in the HLR table (MAP_OPEN request without any user specific parameters), sending the MAP_CANCEL_LOCATION request primitive (see figures 16.1.2/2 and 16... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 19.1.2.3 Detailed procedure in the VLR | Opening of the dialogue is described in the macro Receive_Open_Ind in subclause 25.1, with outcomes: - reversion to version Vr procedure; - procedure termination; or - dialogue acceptance, with processing as below. If the VLR process receives a MAP_NOTICE indication, it terminates the dialogue by sending a MAP_CLOSE re... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 19.1.2.4 Detailed procedure in the SGSN | Opening of the dialogue is described in the macro Receive_Open_Ind in subclause 25.1, with outcomes: - procedure termination; or - dialogue acceptance, with processing as below. If the SGSN process receives a MAP_NOTICE indication, it terminates the dialogue by sending a MAP_CLOSE request. If the SGSN process receives ... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 19.1.3 Detach IMSI | |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 19.1.3.1 General | On receipt of an A_LU_REQUEST (DETACH IMSI) indication from the radio interface this procedure invokes the MAP_DETACH_IMSI service described in subclause 8.1.5 in order to inform the visitor location register that a subscriber is no longer reachable (see figure 19.1.3/1), e.g. due to switched off station. This informat... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 19.1.3.2 Detailed procedure in the MSC | The MAP_DETACH_IMSI service is invoked by the MSC when receiving an A_LU_Request (DETACH IMSI) for a subscriber (see figure 19.1.3/2). The MSC will open the dialogue to the VLR with a MAP_OPEN request containing no user specific parameters. The MAP_DETACH_IMSI request will contain the following parameter received from ... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 19.1.3.3 Detailed procedure in the VLR | When the VLR receives a MAP_DETACH_IMSI indication (see figure 19.1.3/3), it first checks the indication data (macro Check_Indication, see subclause 25.2). Thereafter it is checked whether the subscriber is known: - if the subscriber is unknown the VLR ignores the indication; - if the subscriber is known in the VLR, th... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 19.1.4 Purge MS | |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 19.1.4.1 General | When the VLR or the SGSN receives an indication on the O&M interface that the MS record is to be purged (either because of administrative action or because the MS has been inactive for an extended period), this procedure invokes the MAP_PURGE_MS service described in subclause 8.1.6 to request the HLR to set the "MS pur... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.