hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
17250281ac36b9d402e66d0077cd67fd | 100 974 | 15.6.4.3 Receipt of a TC-U-ERROR indication | If the error code is not defined for the MAP or is not one associated with the operation referred to by the invoke identifier, request the transfer of a reject component using the TC-U-REJECT request primitive, with the appropriate problem code (unrecognized error or unexpected error), and issue a confirm primitive wit... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 15.6.4.4 Receipt of a TC-INVOKE indication | A TC-INVOKE indication primitive is considered as carrying a possible response to a specific service if the linked ID refers to an active specific service and the associated operation is a class 4 operation. Note that the presence of a linked ID parameter in a TC-INVOKE primitive requesting a non class 4 operation indi... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 15.6.4.5 Receipt of a TC-U-REJECT indication | On receipt of a TC-U-REJECT indication primitive which affects a pending service, the MAP PM shall issue a MAP confirm primitive to the MAP-service-user with the appropriate value of the provider error or user error parameter. The mapping of TC invoke problem codes on to MAP Provider Error and MAP User Error parameter ... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 15.6.4.6 Receipt of a TC-L-REJECT indication | This event occurs when the local TC detects a protocol error in an incoming component which affects an active specific service. On receipt of a TC-L-REJECT indicating "return result problem, unexpected return result", the MAP shall issue a confirm primitive with the parameter provider error indicating "unexpected respo... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 15.6.4.7 Receipt of a TC-L-CANCEL indication | On receipt of a TC-L-CANCEL indication, the MAP PM shall: - if the associated operation is a class 1 operation, issue a confirm primitive with the provider error cause indicating "no response from the peer"; - if the associated operation is a class 2 operation and no linked operations are defined for this operation, is... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 15.6.4.8 Receipt of a TC-NOTICE indication | If a TC-NOTICE indication primitive is received before the dialogue has been confirmed (i.e. no backward message is received by the dialogue initiator node), the MAP PM shall issue a MAP-OPEN Cnf primitive with the result parameter indicating Refused and a refuse reason Remote node not reachable". If a TC-NOTICE indica... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 15.6.5 Other events | This subclause describes the behaviour of the MAP PM on receipt of a component handling indication primitive which cannot be related to any service or which does not affect a pending one. The MAP user is only informed that an abnormal event occurred during the associated dialogue. It is up to the MAP user to abort, con... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 15.6.5.1 Receipt of a TC-U-REJECT | On receipt of a TC-U-REJECT indication primitive which does not affect an active SSM (i.e. indicating a return result or return error problem), the MAP PM shall issue a MAP-NOTICE indication primitive with the diagnostic parameter set to "response rejected by the peer". This is also applicable for invoke problems relat... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 15.6.5.2 Receipt of a TC-R-REJECT indication | On receipt of a TC-R-REJECT indication (i.e. when a protocol error has been detected by the peer TC entity) which does not affect an active SSM, the MAP PM shall either discard this indication or issue a MAP-NOTICE indication primitive with the provider error indicating "abnormal event detected by the peer". In case of... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 15.6.5.3 Receipt of a TC-L-REJECT indication | On receipt of a TC-L-REJECT indication primitive (i.e. when a protocol error has been detected by the local TC entity) which cannot be related to an active SSM, the MAP PM shall either discard this indication or issue a MAP-NOTICE indication primitive with the provider error indicating "abnormal event received from the... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 15.6.6 Parameter checks | As described in the previous subclauses, the MAP PM performs a set of checks to ensure the correctness of the information elements received; these are: - check if the syntax and encoding (note) of the operation argument, result or error parameter are correct. NOTE: Depending on the implementation, encoding problems on ... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 15.6.7 Returning state machines to idle | Unlike TC invocation state machines, service state machines exist at both requestor and performer side. A service state machine at the requestor side is returned to idle when the MAP-specific confirm primitive is issued or when the dialogue terminates. ETSI ETSI TS 100 974 V7.3.0 (2000-02) 210 (GSM 09.02 version 7.3.0 ... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 15.6.8 Load control | As stated in the previous subclauses, before issuing a MAP-OPEN indication primitive the MAP PM performs a check to verify if there are sufficient resources to open the dialogue taking into account possible overload conditions. The decision is based on the priority allocated to the application-context whose name is exp... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 16 Mapping on to TC services | |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 16.1 Dialogue control | Dialogue control services are mapped to TC dialogue handling services. The TC-UNI service is not used by the MAP PM. |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 16.1.1 Directly mapped parameters | The following parameters of the MAP-OPEN request and indication primitives are directly mapped on to the corresponding parameters of the TC-BEGIN primitives: - destination address; - originating address. |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 16.1.2 Use of other parameters of dialogue handling primitives | |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 16.1.2.1 Dialogue Id | The value of this parameter is associated with the MAP PM invocation in an implementation dependent manner. |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 16.1.2.2 Application-context-name | The application-context-name parameter of a MAP primitive is mapped to the application-context-name parameter of TC dialogue handling primitives according to the rules described in subclause 15.1. |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 16.1.2.3 User information | The user information parameter of TC dialogue primitives is used to carry the MAP dialogue APDUs. |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 16.1.2.4 Component present | This parameter is used by the MAP PM as described in CCITT Recommendation Q.771. It is not visible to the MAP user. |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 16.1.2.5 Termination | The value of this parameter of the TC-END request primitive is set by the MAP PM on the basis of the release method parameter of the MAP-CLOSE request primitive, except when the dialogue state machine is in the state DIALOGUE INITIATED, in which case the Termination parameter shall always indicate "pre-arranged end". E... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 16.1.2.6 P-Abort-Cause | Values of the P-abort-cause parameter are mapped to the values of the provider-reason parameter of the MAP-P- ABORT indication primitive according to table 16.1/1, except in the dialogue initiated phase for the "incorrectTransactionPortion" and "noCommonDialoguePortion" values which are mapped to the "potential incompa... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 16.1.2.7 Quality of service | The quality of service of TC request primitives is set by the MAP as shown below. - Return option: "Return message on error" or "Discard message on error" as required by the network operator; - Sequence control: "Sequence guaranteed" or "Sequence result not guaranteed" as required by the network operator; "Sequence gua... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 16.2 Service specific procedures | Specific services are mapped to TC component handling services. |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 16.2.1 Directly mapped parameters | The Invoke Id parameter of the MAP request and indication primitive is directly mapped on to the Invoke Id parameter of the component handling primitives. |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 16.2.2 Use of other parameters of component handling primitives | |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 16.2.2.1 Dialogue Id | The value of this parameter is associated with the MAP PM invocation in an implementation dependent manner. ETSI ETSI TS 100 974 V7.3.0 (2000-02) 212 (GSM 09.02 version 7.3.0 Release 1998) |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 16.2.2.2 Class | The value of this parameter is set by the MAP PM according to the type of the operation to be invoked. |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 16.2.2.3 Linked Id | When a service response is mapped to a class 4 operation, the value of this parameter is set by the MAP PM and corresponds to the value assigned by the user to the initial service request (i.e. the value of the invoke ID parameter of the request primitive). Otherwise if such a parameter is included in MAP request/indic... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 16.2.2.4 Operation | When mapping a request primitive on to a Remote Operations PDU (invoke), the MAP PM shall set the operation code according to the mapping described in table 16.2/1. When mapping a response primitive on to a Remote Operations service, the MAP PM shall set the operation code of the TC-RESULT-L/NL primitive (if required) ... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 16.2.2.5 Error | The error parameter in a TC-U-ERROR indication primitive is mapped to the user error parameter in the MAP confirm primitive of the service associated with the operation to which the error is attached. The user error parameter in MAP response primitives is mapped to the error parameter of the TC-U-ERROR request primitiv... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 16.2.2.6 Parameters | The parameters of MAP specific request and indication primitives are mapped to the argument parameter of TC- INVOKE primitives. The parameters of MAP specific response and confirm primitives are mapped to the result parameter of TC-RESULT-L primitives, the parameter of TC-U-ERROR primitives or the argument of TC-INVOKE... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 16.2.2.7 Time out | The value of this parameter is set by the MAP PM according to the type of operation invoked. |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 16.2.2.8 Last component | This parameter is used by the MAP PM as described in CCITT Recommendation Q.711. It is not visible from the MAP user. |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 16.2.2.9 Problem code | |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 16.2.2.9.1 Mapping to MAP User Error | The following values of the user error parameter are mapped as follows to values of the TC problem code parameter. These values are generated by the MAP user. This mapping is valid from the TC-U-REJECT indication primitive to the MAP confirm service primitive and from the MAP response service primitive to the TC-U-REJE... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 16.2.2.9.2 Mapping to MAP Provider Error parameter | The following values of the TC problem code parameter of the TC-U-REJECT indication primitive are mapped as follows to values of the MAP Provider Error parameter of the MAP confirm primitive. Table 16.2/3: Mapping of TC problem code in TC-U-REJECT on to MAP Provider Error parameter TC problem code MAP Provider Error du... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 16.2.2.9.3 Mapping to diagnostic parameter | The following values of the problem code parameter of the TC-R-REJECT and TC-U-REJECT primitive are mapped to values of the diagnostic parameter of the MAP-NOTICE indication primitive as follows: Table 16.2/5: Mapping of TC problem code of TC-R-REJECT and TC-U-REJECT on to diagnostic parameter TC problem code MAP diagn... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 16.3 SDL descriptions | The following SDL specification describes a system which includes three blocks: MAP-user, MAP-provider and TC. Such a system resides in each network component supporting MAP and communicates with its peers via the lower layers of the signalling network which are part of the environment. Only the MAP-provider is fully d... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 17 Abstract syntax of the MAP protocol | |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 17.1 General | This subclause specifies the Abstract Syntaxes for the Mobile Application Part as well as the associated set of Operations and Errors, using the Abstract Syntax Notation One (ASN.1), defined in CCITT Recommendation X.208 (1988) or X.680 (1994) with additions as defined in subclause 17.1.4 on Compatibility Consideration... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 17.1.1 Encoding rules | The encoding rules which are applicable to the defined Abstract Syntaxes are the Basic Encoding Rules for Abstract Syntax Notation One, defined in CCITT Recommendation X.690 with the same exceptions as in CCITT Recommendation Q.773 section 4 Message Representation. When the definite form is used for length encoding, a ... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 17.1.2 Use of TC | The mapping of OPERATION and ERROR to TC components is defined in ETS 300 287 (version 2) which is based on CCITT Recommendation Q.773 (1992). NOTE 1: The class of an operation is not stated explicitly but is specified as well in the ASN.1 operation type definition. Class 1: RESULT and ERROR appear in ASN.1 operation t... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 17.1.2.1 Use of Global Operation and Error codes defined outside MAP | An entity supporting an application context greater than 2 shall be capable of receiving an operation or error code, within an application context defined in GSM 09.02, encoded as either an Object Identifier (as defined in CCITT Recommendation X.690 (1994)) or an integer value (as defined in section 17.5). Related rest... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 17.1.3 Use of information elements defined outside MAP | An information element or a set of information elements (messages) transparently carried in the Mobile Application Part but defined in other recommendation/technical specifications are handled in one of the following ways: i) The contents of each information element (without the octets encoding the identifier and the l... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 17.1.4 Compatibility considerations | The following ASN.1 modules conform to CCITT Recommendation X.208 (1988) or X.680 (1994) (the only module which makes use of X.680 is MAP-ExtensionDataTypes), but in addition Ellipsis Notation ("..." - notation) is used as described in ITU-T Recommendation X.680 Amendment 1 (1995) wherever future protocol extensions ar... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 17.1.5 Structure of the Abstract Syntax of MAP | For each MAP parameter which has to be transferred by a MAP Protocol Data Unit (MAP message), there is a PDU field (an ASN.1 NamedType) whose ASN.1 identifier has the same name as the corresponding parameter, except for the differences required by the ASN.1 notation (blanks between words are removed or replaced by hyph... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 17.1.6 Application Contexts | The following informative table lists the latest versions of the Application Contexts used in this specification, with the operations used by them and, where applicable, whether or not the operation description is exactly the same as for previous versions. Information in sections 17.6 and 17.7 relates only to the ACs i... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 17.2 Operation packages | |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 17.2.1 General aspects | This subclause describes the operation-packages which are used to build the application-contexts defined in subclause 17.3. Each operation-package is a specification of the roles of a pair of communicating objects (i.e. a pair of MAP-Providers), in term of operations which they can invoke of each other. The grouping of... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 17.2.2 Packages specifications | |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 17.2.2.1 Location updating | This operation package includes the operations required for location management procedures between HLR and VLR. LocationUpdatingPackage-v3 ::= OPERATION-PACKAGE -- Supplier is HLR if Consumer is VLR CONSUMER INVOKES { updateLocation} SUPPLIER INVOKES { forwardCheckSs-Indication} The v1-equivalent and v2-equivalent pack... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 17.2.2.2 Location cancellation | This operation package includes the operations required for location cancellation and MS purging procedures between HLR and VLR and between HLR and SGSN. LocationCancellationPackage-v3 ::= OPERATION-PACKAGE -- Supplier is VLR or SGSN if Consumer is HLR CONSUMER INVOKES { cancelLocation} The v1-equivalent and v2-equival... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 17.2.2.3 Roaming number enquiry | This operation package includes the operations required for roaming number enquiry procedures between HLR and VLR. RoamingNumberEnquiryPackage-v3 ::= OPERATION-PACKAGE -- Supplier is VLR if Consumer is HLR CONSUMER INVOKES { provideRoamingNumber} The v1-equivalent and v2-equivalent packages can be determined according ... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 17.2.2.4 Information retrieval | This operation package includes the operation required for the authentication information retrieval procedure between HLR and VLR and between HLR and SGSN. InfoRetrievalPackage-v2 ::= OPERATION-PACKAGE -- Supplier is HLR if Consumer is VLR -- Supplier is HLR if Consumer is SGSN CONSUMER INVOKES { sendAuthenticationInfo... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 17.2.2.5 Inter-VLR information retrieval | This operation package includes the operations required for inter VLR information retrieval procedures. InterVlrInfoRetrievalPackage-v2 ::= OPERATION-PACKAGE -- Supplier is VLR if Consumer is VLR CONSUMER INVOKES { sendIdentification} The v1-equivalent package is : InfoRetrievalPackage-v1 |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 17.2.2.6 IMSI retrieval | This operation package includes the operation required for the IMSI retrieval procedure between HLR and VLR. IMSIRetrievalPackage-v2 ::= OPERATION-PACKAGE -- Supplier is HLR if Consumer is VLR CONSUMER INVOKES { sendIMSI} This package is v2 only. |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 17.2.2.7 Call control transfer | This operation package includes the operation required for the call control transfer procedure between VMSC and GMSC. CallControlTransferPackage-v4 ::= OPERATION-PACKAGE -- Supplier is GMSC if Consumer is VMSC CONSUMER INVOKES { resumeCallHandling} The v3-equivalent package can be determined according to the rules desc... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 17.2.2.10 Interrogation | This operation package includes the operations required for interrogation procedures between MSC and HLR or NPLR. InterrogationPackage-v3 ::= OPERATION-PACKAGE -- Supplier is HLR or NPLR if Consumer is MSC CONSUMER INVOKES { sendRoutingInfo} The v1-equivalent and v2-equivalent packages can be determined according to th... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 17.2.2.11 Void | |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 17.2.2.12 Handover Control | This operation package includes the operations required for handover procedures between MSCs. HandoverControlPackage-v2 ::= OPERATION-PACKAGE -- Supplier is MSCB if Consumer is MSCA CONSUMER INVOKES { prepareHandover, forwardAccessSignalling} SUPPLIER INVOKES { sendEndSignal, processAccessSignalling, prepareSubsequentH... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 17.2.2.13 Subscriber Data management stand alone | This operation package includes the operations required for stand alone subscriber data management procedures between HLR and VLR or between HLR and SGSN. SubscriberDataMngtStandAlonePackage-v3 ::= OPERATION-PACKAGE -- Supplier is VLR or SGSN if Consumer is HLR CONSUMER INVOKES { insertSubscriberData, deleteSubscriberD... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 17.2.2.14 Equipment management | This operation package includes the operations required for equipment management procedures between EIR and MSC or between EIR and SGSN. EquipmentMngtPackage-v2 ::= OPERATION-PACKAGE -- Supplier is EIR if Consumer is MSC -- Supplier is EIR if Consumer is SGSN CONSUMER INVOKES { checkIMEI} The v1-equivalent package can ... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 17.2.2.15 Subscriber data management | This operation package includes the operations required for subscriber data management procedures between HLR and VLR or between HLR and SGSN. SubscriberDataMngtPackage-v3 ::= OPERATION-PACKAGE -- Supplier is VLR or SGSN if Consumer is HLR CONSUMER INVOKES { insertSubscriberData} The v1-equivalent and v2-equivalent pac... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 17.2.2.16 Location register restart | This operation package includes the operations required for location register restart procedures between HLR and VLR or between HLR and SGSN. ResetPackage-v2 ::= OPERATION-PACKAGE -- Supplier is VLR or SGSN if Consumer is HLR CONSUMER INVOKES { reset} The v1-equivalent package can be determined according to the rules d... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 17.2.2.17 Tracing stand-alone | This operation package includes the operations required for stand alone tracing procedures between HLR and VLR or between HLR and SGSN. TracingStandAlonePackage-v3 ::= OPERATION-PACKAGE -- Supplier is VLR or SGSN if Consumer is HLR CONSUMER INVOKES { activateTraceMode, deactivateTraceMode} The v1-equivalent and v2-equi... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 17.2.2.18 Functional SS handling | This operation package includes the operations required for functional supplementary services procedures between VLR and HLR. FunctionalSsPackage-v2 ::= OPERATION-PACKAGE -- Supplier is HLR if Consumer is VLR CONSUMER INVOKES { registerSS, eraseSS, activateSS, deactivateSS, registerPassword, interrogateSS} SUPPLIER INV... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 17.2.2.19 Tracing | This operation package includes the operations required for tracing procedures between HLR and VLR or between HLR and SGSN. TracingPackage-v3 ::= OPERATION-PACKAGE -- Supplier is VLR or SGSN if Consumer is HLR CONSUMER INVOKES { activateTraceMode} The v1-equivalent and v2-equivalent packages can be determined according... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 17.2.2.20 Binding | This operation package includes the operation required to initialize a supplementary service procedure between VLR and HLR or between gsmSCF and HLR. BindingPackage-v1 ::= OPERATION-PACKAGE -- Supplier is HLR if Consumer is VLR -- Supplier is gsmSCF if Consumer is HLR CONSUMER INVOKES { beginSubscriberActivity} This pa... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 17.2.2.21 Unstructured SS handling | This operation package includes the operations required for unstructured supplementary services procedures between VLR and HLR, and between the HLR and the gsmSCF. UnstructuredSsPackage-v2 ::= OPERATION-PACKAGE -- Supplier is HLR if Consumer is VLR -- Supplier is gsmSCF if Consumer is HLR CONSUMER INVOKES { processUnst... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 17.2.2.22 MO Short message relay services | This operation package includes the operations required for short message relay service procedures between IWMSC and VMSC or between GMSC and MSC or between SGSN and IWMSC. MOShortMsgRelayPackage-v3 ::= OPERATION-PACKAGE -- Supplier is IWMSC if Consumer is MSC -- Supplier is IWMSC if Consumer is SGSN CONSUMER INVOKES {... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 17.2.2.23 Short message gateway services | This operation package includes the operations required for short message service gateway procedures between MSC and HLR. ShortMsgGatewayPackage-v3 ::= OPERATION-PACKAGE -- Supplier is HLR if Consumer is GMSC CONSUMER INVOKES { sendRoutingInfoForSM, reportSM-DeliveryStatus} SUPPLIER INVOKES { informServiceCentre} The v... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 17.2.2.24 MT Short message relay services | This operation package includes the operations required for short message relay service procedures between GMSC and MSC or between GMSC and SGSN. MTShortMsgRelayPackage-v3 ::= OPERATION-PACKAGE -- Supplier is MSC or SGSN if Consumer is GMSC CONSUMER INVOKES { MT-forwardSM} The v2-equivalent package is: ShortMsgRelayPac... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 17.2.2.25 Void | |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 17.2.2.26 Message waiting data management | This operation package includes the operations required for short message waiting data procedures between HLR and VLR, between HLR and SGSN. MwdMngtPackage-v3 ::= OPERATION-PACKAGE -- Supplier is HLR if Consumer is SGSN -- Supplier is HLR if Consumer is VLR CONSUMER INVOKES { readyForSM} The v2-equivalent package can b... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 17.2.2.27 Alerting | This operation package includes the operations required for alerting between HLR and IWMSC. AlertingPackage-v2 ::= OPERATION-PACKAGE -- Supplier is IWMSC if Consumer is HLR CONSUMER INVOKES { alertServiceCentre} The v1-equivalent package is defined as follows. AlertingPackage-v1 ::= OPERATION-PACKAGE -- Supplier is IWM... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 17.2.2.28 Data restoration | This operation package includes the operations required for VLR data restoration between HLR and VLR. DataRestorationPackage-v3 ::= OPERATION-PACKAGE -- Supplier is HLR if Consumer is VLR CONSUMER INVOKES { restoreData} The v2-equivalent package can be determined according to the rules described in subclause 17.2.1. Th... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 17.2.2.29 Purging | This operation package includes the operations required for purging between HLR and VLR or between HLR and SGSN. PurgingPackage-v3 ::= OPERATION-PACKAGE -- Supplier is HLR if Consumer is VLR -- Supplier is HLR if Consumer is SGSN CONSUMER INVOKES { purgeMS} The v2-equivalent package can be determined according to the r... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 17.2.2.30 Subscriber information enquiry | This operation package includes the operations required for subscriber information enquiry procedures between HLR and VLR. SubscriberInformationEnquiryPackage-v3 ::= OPERATION-PACKAGE -- Supplier is VLR if Consumer is HLR CONSUMER INVOKES { provideSubscriberInfo} This package is v3 only. |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 17.2.2.31 Any time information enquiry | This operation package includes the operations required for any time information enquiry procedures between gsmSCF and HLR. AnyTimeInformationEnquiryPackage-v3 ::= OPERATION-PACKAGE -- Supplier is HLR if Consumer is gsmSCF CONSUMER INVOKES { anyTimeInterrogation} This package is v3 only. |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 17.2.2.32 Group Call Control | This operation package includes the operations required for group call and broadcast call procedures between MSCs. GroupCallControlPackage-v3 ::= OPERATION-PACKAGE -- Supplier is relay MSC if Consumer is anchor MSC CONSUMER INVOKES { prepareGroupCall, forwardGroupCallSignalling} SUPPLIER INVOKES { sendGroupCallEndSigna... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 17.2.2.33 Provide SIWFS number | This operation package includes the operations required between VMSC and SIWF for requesting resources from an SIWF. ProvideSIWFSNumberPackage-v3 ::= OPERATION-PACKAGE -- Supplier is SIWF if Consumer is VMSC CONSUMER INVOKES { provideSIWFSNumber} This package is v3 only. ETSI ETSI TS 100 974 V7.3.0 (2000-02) 255 (GSM 0... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 17.2.2.34 SIWFS Signalling Modify | This operation package includes the operations required for the modification of the resourses in an SIWF between the VMSC and SIWF. SIWFSSignallingModifyPackage-v3 ::= OPERATION-PACKAGE -- Supplier is SIWF if Consumer is VMSC CONSUMER INVOKES { sIWFSSignallingModify} This package is v3 only. |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 17.2.2.35 Gprs location updating | This operation package includes the operations required for the gprs location management procedures between HLR and SGSN. GprsLocationUpdatingPackage-v3 ::= OPERATION-PACKAGE -- Supplier is HLR if Consumer is SGSN CONSUMER INVOKES { updateGprsLocation} This package is v3 only. |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 17.2.2.36 Gprs Interrogation | This operation package includes the operations required for interrogation procedures between HLR and GGSN. GprsInterrogationPackage-v3 ::= OPERATION-PACKAGE -- Supplier is HLR if Consumer is GGSN CONSUMER INVOKES { sendRoutingInfoForGprs} This package is v3 only. |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 17.2.2.37 Failure reporting | This operation package includes the operations required for failure reporting between HLR and GGSN. FailureReportingPackage-v3 ::= OPERATION-PACKAGE -- Supplier is HLR if Consumer is GGSN CONSUMER INVOKES { failureReport} This package is v3 only. |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 17.2.2.38 GPRS notifying | This operation package includes the operations required for notifying that GPRS subscriber is present between HLR and GGSN. GprsNotifyingPackage-v3 ::= OPERATION-PACKAGE -- Supplier is GGSN if Consumer is HLR CONSUMER INVOKES { noteMsPresentForGprs} This package is v3 only. ETSI ETSI TS 100 974 V7.3.0 (2000-02) 256 (GS... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 17.2.2.39 Supplementary Service invocation notification | This operation package includes the operations required for Supplementary Service invocation notification procedures between MSC and gsmSCF. SS-InvocationNotificationPackage-v3 ::= OPERATION-PACKAGE -- Supplier is gsmSCF if Consumer is MSC CONSUMER INVOKES { ss-InvocationNotification} This package is v3 only. |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 17.2.2.40 Set Reporting State | This operation package includes the operation required for procedures between HLR and VLR to set the reporting state. SetReportingStatePackage-v3 ::= OPERATION-PACKAGE -- Supplier is VLR if Consumer is HLR CONSUMER INVOKES { setReportingState} This package is v3 only. |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 17.2.2.41 Status Report | This operation package includes the operation required for procedures between VLR and HLR to report call results and events. StatusReportPackage-v3 ::= OPERATION-PACKAGE -- Supplier is HLR if Consumer is VLR CONSUMER INVOKES { statusReport} This package is v3 only. |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 17.2.2.42 Remote User Free | This operation package includes the operation required by the HLR to indicate to the VLR that the remote user is free. RemoteUserFreePackage-v3 ::= OPERATION-PACKAGE -- Supplier is VLR if Consumer is HLR CONSUMER INVOKES { remoteUserFree} This package is v3 only. |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 17.2.2.43 Call Completion | This operation package includes the operations required for procedures between VLR and HLR for subscriber control of call completion services. CallCompletionPackage-v3 ::= OPERATION-PACKAGE -- Supplier is HLR if Consumer is VLR CONSUMER INVOKES { registerCC-Entry, eraseCC-Entry} This package is v3 only. |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 17.2.2.44 Location service gateway services | This operation package includes the operations required for location service gateway procedures between GMLC and HLR. ETSI ETSI TS 100 974 V7.3.0 (2000-02) 257 (GSM 09.02 version 7.3.0 Release 1998) LocationSvcGatewayPackage-v3 ::= OPERATION-PACKAGE -- Supplier is HLR if Consumer is GMLC CONSUMER INVOKES { sendRoutingI... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 17.2.2.45 Location service enquiry | This operation package includes the operations required for the location service enquiry procedures between GMLC and MSC. LocationSvcEnquiryPackage-v3 ::= OPERATION-PACKAGE -- Supplier is MSC if Consumer is GMLC CONSUMER INVOKES { provideSubscriberLocation} SUPPLIER INVOKES { subscriberLocationReport} This package is v... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 17.2.2.46 Void | |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 17.2.2.47 Void | |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 17.2.2.48 Void | |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 17.3 Application contexts | |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 17.3.1 General aspects | An application-context is assigned for each dialogue established by a MAP-user. In the present document each application-context is assigned a name which is supplied in the MAP-OPEN Req primitive by the MAP-User and transmitted to the peer under certain circumstances. The following ASN.1 MACRO is used to describe the m... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.