hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
17250281ac36b9d402e66d0077cd67fd | 100 974 | 11.9.3 Parameter use | Invoke id See subclause 7.6.1 for the use of this parameter. USSD Data Coding Scheme: See subclause 7.6.4 for the use of this parameter. The presence of the parameter in the response is dependent on the unstructured supplementary service application. If this parameter is present, then the USSD String parameter has to b... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 11.10 MAP_UNSTRUCTURED_SS_REQUEST service | 11.10.1 Definitions This service is used between the gsmSCF and the HLR, the HLR and the VLR and between the VLR and the MSC when the invoking entity requires information from the mobile user, in connection with unstructured supplementary service handling. The MAP_UNSTRUCTURED_SS_REQUEST service is a confirmed service ... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 11.11 MAP_UNSTRUCTURED_SS_NOTIFY service | 11.11.1 Definitions This service is used between the gsmSCF and the HLR, the HLR and the VLR and between the VLR and the MSC when the invoking entity requires a notification to be sent to the mobile user, in connection with unstructured supplementary services handling. The MAP_UNSTRUCTURED_SS_NOTIFY service is a confir... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 11.12 MAP_SS_INVOCATION_NOTIFY | 11.12.1 Definition This service is used between the MSC and the gsmSCF when the subscriber invokes one of the following supplementary services; CD, ECT or MPTY. 11.12.2 Service primitives The service primitives are shown in table 11.12/1. Table 11.12/1: SS_INVOCATION_NOTIFY parameters Parameter name Request Indication ... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 11.13 MAP_REGISTER_CC_ENTRY service | 11.13.1 Definition This service is used between the MSC and the VLR and between the VLR and the HLR to register data for a requested call completion supplementary service. The VLR will relay the message to the HLR. The service is a confirmed service and uses the service primitives shown in table 11.13/1. ETSI ETSI TS 1... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 11.14 MAP_ERASE_CC_ENTRY service | 11.14.1 Definition This service is used between the MSC and the VLR and between the VLR and the HLR to erase data related to a call completion supplementary service. The VLR will relay the message to the HLR. The service is a confirmed service and uses the service primitives shown in table 11.14/1. 11.14.2 Service prim... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 12 Short message service management services | |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 12.1 MAP-SEND-ROUTING-INFO-FOR-SM service | |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 12.1.1 Definition | This service is used between the gateway MSC and the HLR to retrieve the routing information needed for routing the short message to the servicing MSC. The MAP-SEND-ROUTING-INFO-FOR-SM is a confirmed service using the primitives from table 12.1/1. |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 12.1.2 Service primitives | The service primitives are shown in table 12.1/1. Table 12.1/1: MAP-SEND-ROUTING-INFO-FOR-SM Parameter name Request Indication Response Confirm Invoke Id M M(=) M(=) M(=) MSISDN M M(=) SM-RP-PRI M M(=) Service Centre Address M M(=) SM-RP-MTI C C(=) SM-RP-SMEA C C(=) GPRS Support Indicator C C(=) IMSI C C(=) Network Nod... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 12.1.3 Parameter use | Invoke id: See definition in subclause 7.6.1. MSISDN: See definition in subclause 7.6.2. SM-RP-PRI: See definition in subclause 7.6.8. Service Centre Address: See definition in subclause 7.6.2. SM-RP-MTI: See definition in subclause 7.6.8. This parameter shall be present when the feature « SM filtering by the HPLMN » i... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 12.2 MAP-MO-FORWARD-SHORT-MESSAGE service | |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 12.2.1 Definition | This service is used between the serving MSC or the SGSN and the gateway MSC to forward mobile originated short messages. The MAP-MO-FORWARD-SHORT-MESSAGE service is a confirmed service using the service primitives given in table 12.2/1. |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 12.2.2 Service primitives | The service primitives are shown in table 12.2/1. Table 12.2/1: MAP-MO-FORWARD-SHORT-MESSAGE Parameter name Request Indication Response Confirm Invoke Id M M(=) M(=) M(=) SM RP DA M M(=) SM RP OA M M(=) SM RP UI M M(=) C C(=) IMSI User error C C(=) C C(=) Provider error O |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 12.2.3 Parameter use | Invoke id: See definition in subclause 7.6.1. SM RP DA: See definition in subclause 7.6.8. In the mobile originated SM transfer this parameter contains the Service Centre address received from the mobile station. SM RP OA: See definition in subclause 7.6.8. The MSISDN received from the VLR or from the SGSN is inserted ... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 12.3 MAP-REPORT-SM-DELIVERY-STATUS service | |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 12.3.1 Definition | This service is used between the gateway MSC and the HLR. The MAP-REPORT-SM-DELIVERY-STATUS service is used to set the Message Waiting Data into the HLR or to inform the HLR of successful SM transfer after polling. This service is invoked by the gateway MSC. The MAP-REPORT-SM-DELIVERY-STATUS service is a confirmed serv... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 12.3.2 Service primitives | The service primitives are shown in table 12.3/1. ETSI ETSI TS 100 974 V7.3.0 (2000-02) 180 (GSM 09.02 version 7.3.0 Release 1998) Table 12.3/1: MAP-REPORT-SM-DELIVERY-STATUS Parameter name Request Indication Response Confirm Invoke Id M M(=) M(=) M(=) MSISDN M M(=) Service Centre Address M M(=) SM Delivery Outcome M M... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 12.3.3 Parameter use | Invoke id: See definition in subclause 7.6.1. MSISDN: See definition in subclause 7.6.2. Service Centre Address: See definition in subclause 7.6.2. SM Delivery Outcome: See definition in subclause 7.6.8. This parameter indicates the status of the mobile terminated SM delivery. Absent Subscriber Diagnostic SM: See defin... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 12.4 MAP-READY-FOR-SM service | |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 12.4.1 Definition | This service is used between the MSC and VLR and as well between the VLR and the HLR. The MSC initiates this service if a subscriber indicates memory available situation. The VLR uses the service to indicate this to the HLR. The VLR initiates this service if a subscriber, whose message waiting flag is active in the VLR... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 12.4.2 Service primitives | The service primitives are shown in table 12.4/1. Table 12.4/1: MAP-READY-FOR-SM Parameter name Request Indication Response Confirm Invoke Id M M(=) M(=) M(=) IMSI C C(=) TMSI C C(=) Alert Reason M M(=) Alert Reason Indicator C C(=) User error C C(=) Provider error O |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 12.4.3 Parameter use | Invoke id: See definition in subclause 7.6.1. See definition in subclause 7.6.2. The IMSI is used always between the VLR and the HLR and between the SGSN and the HLR. Between the MSC and the VLR the identification can be either IMSI or TMSI. TMSI: See definition in subclause 7.6.2. The identification can be either IMSI... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 12.5 MAP-ALERT-SERVICE-CENTRE service | |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 12.5.1 Definition | This service is used between the HLR and the interworking MSC. The HLR initiates this service, if the HLR detects that a subscriber, whose MSISDN is in the Message Waiting Data file, is active or the MS has memory available. The MAP-ALERT-SERVICE-CENTRE service is a confirmed service using the primitives from table 12.... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 12.5.2 Service primitives | The service primitives are shown in table 12.5/1. Table 12.5/1: MAP-ALERT-SERVICE-CENTRE Parameter name Request Indication Response Confirm Invoke Id M M(=) M(=) M(=) MSIsdn-Alert M M(=) Service Centre Address M M(=) User error C C(=) Provider error O |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 12.5.3 Parameter use | Invoke id: See definition in subclause 7.6.1. MSIsdn-Alert: See definition in subclause 7.6.2. The provided MSISDN shall be the one which is stored in the Message Waiting Data file. ETSI ETSI TS 100 974 V7.3.0 (2000-02) 183 (GSM 09.02 version 7.3.0 Release 1998) Service Centre Address: See definition in subclause 7.6.2... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 12.6 MAP-INFORM-SERVICE-CENTRE service | |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 12.6.1 Definition | This service is used between the HLR and the gateway MSC to inform the Service Centre which MSISDN number is stored in the Message Waiting Data file. If the stored MSISDN number is not the same than the one received from the gateway MSC in the MAP-SEND-ROUTING-INFO-FOR-SM service primitive the stored MSISDN number is i... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 12.6.2 Service primitives | The service primitives are shown in table 12.6/1. Table 12.6/1: MAP-INFORM-SERVICE-CENTRE Parameter name Request Indication Invoke Id M M(=) MSIsdn-Alert C C(=) MWD Status C C(=) |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 12.6.3 Parameter use | Invoke id: See definition in subclause 7.6.1. MSIsdn-Alert: See definition in subclause 7.6.2 This parameter refers to the MSISDN stored in a Message Waiting Data file in the HLR. MWD Status: See definition in subclause 7.6.8. This parameter indicates the status of the MCEF, MNRF and MNRG flags and the status of the pa... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 12.7 MAP-SEND-INFO-FOR-MT-SMS service | |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 12.7.1 Definition | This service is used between the MSC and the VLR. The service is invoked by the MSC receiving an mobile terminated short message to request subscriber related information from the VLR. The MAP-SEND-INFO-FOR-MT-SMS service is a confirmed service using the primitives from table 12.7/1. |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 12.7.2 Service primitives | The service primitives are shown in table 12.7/1. Table 12.7/1: MAP-SEND-INFO-FOR-MT-SMS Parameter name Request Indication Response Confirm Invoke Id M M(=) M(=) M(=) SM RP DA M M(=) MSISDN C C(=) User error C C(=) Provider error O |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 12.7.3 Parameter use | Invoke id: See definition in subclause 7.6.1. SM RP DA: See definition in subclause 7.6.8. This parameter shall contain either an IMSI or a LMSI. MSISDN: See definition in subclause 7.6.2. User error: The following errors defined in subclause 7.6.1 may be used, depending on the nature of the fault: - Unknown subscriber... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 12.8 MAP-SEND-INFO-FOR-MO-SMS service | |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 12.8.1 Definition | This service is used between the MSC and the VLR. The service is invoked by the MSC which has to handle a mobile originated short message request to request the subscriber related information from the VLR. The MAP-SEND-INFO-FOR-MO-SMS service is a confirmed service using the primitives from table 12.8/1. |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 12.8.2 Service primitives | The service primitives are shown in table 12.8/1. Table 12.8/1: MAP-SEND-INFO-FOR-MO-SMS Parameter name Request Indication Response Confirm Invoke Id M M(=) M(=) M(=) Service Centre Address M M(=) MSISDN C C(=) User error C C(=) Provider error O |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 12.8.3 Parameter use | Invoke id: See definition in subclause 7.6.1. Service Centre Address: See definition in subclause 7.6.2. MSISDN: See definition in subclause 7.6.2. User error: The following errors defined in subclause 7.6.1 may be used, depending on the nature of the fault: - Teleservice Not Provisioned; - Call Barred; - Unexpected Da... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 12.9 MAP-MT-FORWARD-SHORT-MESSAGE service | |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 12.9.1 Definition | This service is used between the gateway MSC and the servicing MSC or the SGSN to forward mobile mobile terminated short messages. The MAP-MT-FORWARD-SHORT-MESSAGE service is a confirmed service using the service primitives given in table 12.9/1. |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 12.9.2 Service primitives | The service primitives are shown in table 12.9/1. Table 12.9/1: MAP-MT-FORWARD-SHORT-MESSAGE Parameter name Request Indication Response Confirm Invoke Id M M(=) M(=) M(=) SM RP DA M M(=) SM RP OA M M(=) SM RP UI M M(=) C C(=) More Messages To Send C C(=) User error C C(=) Provider error O |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 12.9.3 Parameter use | Invoke id: See definition in subclause 7.6.1. SM RP DA: See definition in subclause 7.6.8. This parameter can contain either an IMSI or a LMSI. The use of the LMSI is an operator option. The LMSI can be provided if it is received from the HLR. The IMSI is used if the use of the LMSI is not available. This parameter is ... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 13 Network-Requested PDP Context Activation services | |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 13.1 MAP_SEND_ROUTING_INFO_FOR_GPRS service | |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 13.1.1 Definition | This service is used by the GGSN to request GPRS routing information from the HLR. |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 13.1.2 Service primitives | Table 13.1/1: MAP_SEND_ROUTING_INFO_FOR_GPRS Parameter name Request Indication Response Confirm Invoke id M M(=) M(=) M(=) IMSI M M(=) GGSN address C C(=) C C(=) GGSN number M M(=) SGSN address C C(=) Mobile Not Reachable Reason C C(=) User error C C(=) Provider error O ETSI ETSI TS 100 974 V7.3.0 (2000-02) 188 (GSM 09... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 13.1.3 Parameter definition and use | Invoke Id See definition in subclause 7.6.1. IMSI See definition in subclause 7.6.2. GGSN address This parameter shall be present if the protocol-converting GSN is used between the GGSN and the HLR. GGSN number See definition in subclause 7.6.2. SGSN address This parameter shall be present if the outcome of the Send Ro... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 13.2 MAP_FAILURE_REPORT service | |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 13.2.1 Definition | This service is used by the GGSN to inform the HLR that network requested PDP-context activation has failed. ETSI ETSI TS 100 974 V7.3.0 (2000-02) 189 (GSM 09.02 version 7.3.0 Release 1998) |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 13.2.2 Service primitives | Table 13.2/1: MAP_FAILURE_REPORT Parameter name Request Indication Response Confirm Invoke id M M(=) M(=) M(=) IMSI M M(=) GGSN address C C(=) C C(=) GGSN number M M(=) User error C C(=) Provider error O |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 13.2.3 Parameter definition and use | Invoke Id See definition in subclause 7.6.1. IMSI See definition in subclause 7.6.2. GGSN address This parameter shall be present if the protocol-converting GSN is used between the GGSN and the HLR. GGSN number See definition in subclause 7.6.2. User error This parameter is sent by the responder when an error is detect... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 13.3 MAP_NOTE_MS_PRESENT_FOR_GPRS service | |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 13.3.1 Definition | This service is used by the HLR to inform the GGSN that the MS is present for GPRS again. ETSI ETSI TS 100 974 V7.3.0 (2000-02) 190 (GSM 09.02 version 7.3.0 Release 1998) |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 13.3.2 Service primitives | Table 13.3/1: MAP_NOTE_MS_PRESENT_FOR_GPRS Parameter name Request Indication Response Confirm Invoke id M M(=) M(=) M(=) IMSI M M(=) GGSN address C C(=) SGSN address M M(=) User error C C(=) Provider error O |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 13.3.3 Parameter definition and use | Invoke Id See definition in subclause 7.6.1. IMSI See definition in subclause 7.6.2. GGSN address This parameter shall be present if the protocol-converting GSN is used between the GGSN and the HLR. SGSN address See definition in subclause 7.6.2. User error This parameter is sent by the responder when an error is detec... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 13A Location Service Management Services | |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 13A.1 MAP-SEND-ROUTING-INFO-FOR-LCS Service | 13A.1.1 Definition This service is used between the GMLC and the HLR to retrieve the routing information needed for routing a location service request to the servicing VMSC. The MAP-SEND-ROUTING-INFO-FOR-LCS is a confirmed service using the primitives from table A.1/1. 13A.1.2 Service Primitives The service primitives ... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 13A.2 MAP-PROVIDE-SUBSCRIBER-LOCATION Service | 13A.2.1 Definition This service is used by a GMLC to request the location of a target MS from the visited MSC at any time. This is a confirmed service using the primitives from table 13A.2/1. 13A.2.2 Service Primitives Table 13A.2/1: Provide_Subscriber_Location Parameter name Request Indication Response Confirm Invoke ... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 13A.3 MAP-SUBSCRIBER-LOCATION-REPORT Service | 13A.3.1 Definition This service is used by a VMSC to provide the location of a target MS to a GMLC when a request for location is either implicitly administered or made at some earlier time. This is a confirmed service using the primitives from table 13A.3/1. 13A.3.2 Service Primitives Table 13A.3/1: Subscriber_Locatio... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 13A.4 Void | ETSI ETSI TS 100 974 V7.3.0 (2000-02) 196 (GSM 09.02 version 7.3.0 Release 1998) 13A.4.1 ÷ 13A.4.3 Void |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 13A.5 Void | 13A.5.1 ÷ 13A.5.3 Void |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 13A.6 Void | 13A.6.1 ÷ 13A.6.3 Void |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 13A.7 Void | 13A.7.1 ÷ 13A.7.3 Void |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 13A.8 Void | 13A.8.1 ÷ 13A.8.3Void |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 13A.9 Void | 13A.9.1 ÷ 13A.9.3Void |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 14 General | |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 14.1 Overview | Clause 14 to 17 specify the protocol elements to be used to provide the MAP services described in clause 7. Clause 15 specifies the elements of procedures for the MAP protocol. Clause 16 specifies the mapping on to TC service primitives. Clause 17 specifies the application contexts, operation packages and abstract synt... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 14.2 Underlying services | The MAP protocol relies on the services provided by the Transaction Capabilities (TC) of signalling system number 7, as referenced in clause 6. |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 14.3 Model | The MAP Protocol Machine (MAP PM) can be modelled as a collection of service state machines (SSMs) - one per MAP specific service invoked - coordinated by a MAP dialogue control function with its one state machine: MAP dialogue state machine (DSM). There are two types of Service State Machines: Requesting Service State... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 14.4 Conventions | The behaviour of the MAP PM depends on the application-context-name associated with the dialogue. One major difference is that the MAP requests the transfer of the application-context-name by TC only for those contexts which do not belong to the so-called "version one context set". The "version one context set" is a se... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 15 Elements of procedure | |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 15.1 Dialogue establishment | The establishment of a MAP dialogue involves two MAP-service-users, one that is the dialogue-initiator and one that is the dialogue-responder. This procedure is driven by the following signals: - a MAP-OPEN request primitive from the dialogue-initiator; - a TC-BEGIN indication primitive occurring at the responding side... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 15.1.2 Receipt of a MAP-OPEN request primitive | On receipt of a MAP-OPEN request primitive the behaviour of the MAP PM shall be as follows: The MAP PM shall accept zero, one or several user request primitives until a MAP-DELIMITER request primitive is received. For each user request primitive, the MAP PM shall request the invocation of the associated operation using... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 15.1.3 Receipt of a TC-BEGIN indication | On receipt of a TC-BEGIN indication primitive, the MAP PM shall: - if no application-context-name is included in the primitive and if the "Components present" indicator indicates "no components", issue a TC-U-ABORT request primitive (note 2). The local MAP-User is not informed. - if no application-context-name is inclu... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 15.1.4 Receipt of a MAP-OPEN response | On receipt of a MAP-OPEN response primitive indicating that the dialogue is accepted, the MAP PM shall build a MAP-Accept PDU if the user-information parameter is included in the response primitive and accept any MAP specific service request or service response until a MAP-DELIMITER request or a MAP-CLOSE request is re... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 15.1.5 Receipt of the first TC-CONTINUE ind | On receipt of the first TC-CONTINUE indication primitive for a dialogue, the MAP PM shall check the value of the application-context-name parameter. If this value matches the one used in the MAP-OPEN request primitive, the MAP PM shall issue a MAP-OPEN confirm primitive with the result parameter indicating "accepted", ... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 15.1.6 Receipt of a TC-END ind | On receipt of a TC-END indication primitive in the dialogue initiated state, the MAP PM shall check the value of the application-context-name parameter. If this value does not match the one used in the MAP-OPEN request primitive, the ETSI ETSI TS 100 974 V7.3.0 (2000-02) 202 (GSM 09.02 version 7.3.0 Release 1998) MAP P... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 15.1.7 Receipt of a TC-U-ABORT ind | On receipt of a TC-U-ABORT indication primitive in the "Dialogue Initiated" state with an abort-reason parameter indicating "ApplicationContextNotSupported", the MAP PM shall issue a MAP-OPEN confirm primitive with the result parameter indicating "Dialogue Refused" and the refuse-reason parameter indicating "Applicatio... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 15.1.8 Receipt of a TC-P-ABORT ind | On receipt of a TC-P-ABORT indication primitive in the "Dialogue Initiated" state with a P-abort parameter indicating "Incorrect Transaction Portion", the MAP PM shall issue a MAP-OPEN confirm primitive with the result parameter indicating "Dialogue Refused" and the refuse reason parameter indicating "Potential Version... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 15.2 Dialogue continuation | Once established the dialogue is said to be in a continuation phase. Both MAP users can request the transfer of MAP APDUs until one of them requests the termination of the dialogue. |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 15.2.1 Sending entity | The MAP PM shall accept any MAP specific service request or response primitives and process them as described in subclause 15.6. On receipt of a MAP-DELIMITER request primitive, the MAP PM shall issue a TC-CONTINUE request primitive. |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 15.2.2 Receiving entity | On receipt of a TC-CONTINUE indication primitive the MAP PM shall accept zero, one or several TC component handling indication primitives and process them as described in subclause 15.6. ETSI ETSI TS 100 974 V7.3.0 (2000-02) 203 (GSM 09.02 version 7.3.0 Release 1998) |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 15.3 Dialogue termination | Both the dialogue-initiator and the dialogue-responder have the ability to request the termination of a dialogue after it has been established. The dialogue termination procedure is driven by the following events: - a MAP-CLOSE request primitive; - a TC-END indication primitive. |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 15.3.1 Receipt of a MAP-CLOSE request | On receipt of a MAP-CLOSE request primitive, the MAP PM shall issue a TC-END request primitive and, if applicable, return to idle the associated active SSMs. Note that if the release method parameter of the MAP-CLOSE request indicates "normal" the TC-END request primitive will trigger the transmission of components ass... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 15.3.2 Receipt of a TC-END indication | On receipt of a TC-END indication primitive, the MAP shall accept any component handling indication primitives and process them as described in subclause 15.6. Once all the received primitives have been processed, the MAP PM shall return to idle the associated SSMs and issue a MAP-CLOSE indication primitive. |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 15.4 User Abort | Both the dialogue-initiator and the dialogue-responder have the ability to abort a dialogue at any time. The user abort procedure is driven by one of the following events: - a MAP-U-ABORT request primitive; - a TC-U-ABORT indication primitive carrying a MAP-user-abort PDU. |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 15.4.1 MAP-U-ABORT request | On receipt of a MAP-U-ABORT request the MAP PM shall construct a MAP-user-abort PDU from the user-reason and diagnostic parameters and issue a TC-U-ABORT request primitive. All state machines associated with the dialogue are returned to idle. |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 15.4.2 TC-U-ABORT ind | On receipt of a TC-U-ABORT indication carrying a MAP-user-abort PDU, the MAP PM shall issue a MAP-U-ABORT indication primitive. The user-reason and diagnostic information elements are mapped to the corresponding parameters of the MAP-U-ABORT indication primitive. All state machines associated with the dialogue are retu... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 15.5 Provider Abort | The MAP has the ability to abort a dialogue at both the dialogue-initiator side and the dialogue-responder side. The provider abort procedure is driven by one of the following events: - a MAP PM error situation; - a TC-P-ABORT indication primitive; ETSI ETSI TS 100 974 V7.3.0 (2000-02) 204 (GSM 09.02 version 7.3.0 Rele... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 15.5.1 MAP PM error situation | In the case of an abnormal situation detected at the MAP level during an established dialogue, the MAP PM shall: - issue a MAP-P-ABORT indication primitive with the appropriate value of the provider-reason parameter; - construct a MAP-abort PDU from the value of these parameters and request its transfer using a TC-U-AB... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 15.5.2 TC-P-ABORT ind | On receipt of a TC-P-ABORT indication, the MAP PM shall issue a MAP-P-ABORT indication primitive. All state machines associated with the dialogue are returned to idle. |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 15.5.3 TC-U-ABORT ind | On receipt of a TC-U-ABORT indication carrying a MAP-abort PDU, the MAP PM shall issue a MAP-P-ABORT indication primitive, with the appropriate value of the provider-reason parameter. The source parameter shall indicate "MAP-provider". All state machines associated with the dialogue are returned to idle. |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 15.6 Procedures for MAP specific services | This subclause describes the MAP procedures for MAP specific services. These procedures are driven by the following types of events: - a MAP specific request or a MAP specific MAP response primitive; - a component handling primitive from TC. A Service State Machine is activated on receipt of one of the following signal... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 15.6.1 Service invocation | The MAP specific procedures are initiated by the MAP request primitives. On receipt of a MAP request primitive, the MAP PM shall build an operation argument from the parameters received in the request primitive and request the invocation of the associated operation using the TC-INVOKE procedure. If a linked ID paramete... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 15.6.2 Service invocation receipt | On receipt of a TC-INVOKE indication primitive, the MAP PM shall: - if the invoke ID is already in use by an active service, request the transfer of a reject component using the TC-U- REJECT request primitive with the appropriate problem code (duplicated invokeID) and issue a MAP-NOTICE indication primitive with a diag... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 15.6.3 Service response | For user confirmed services, the MAP PM shall accept a MAP response primitive and shall: - if no error indication is included in the primitive and the service maps on to a class 1 or 3 operation, construct a result information element from the parameters received and request its transfer using the TC-RESULT-L service a... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 15.6.4 Receipt of a response | A component handling indication primitive is considered as driving a response for a confirmed service if the invoke ID parameter value matches the one stored for the service, or if the linked ID parameter value matches the one stored for the service and the operation invoked is a class 4 operation. On receipt of a resp... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 15.6.4.1 Receipt of a TC-RESULT-NL indication | If the type of the partial result parameter is not compatible with the one defined for the complete result of this operation, request the transfer of a reject component using the TC-U-REJECT request primitive, with the appropriate problem code (mistyped parameter) and issue a confirm primitive with the provider error p... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 15.6.4.2 Receipt of a TC-RESULT-L indication | If the type of the result parameter is not the one defined for the result of this operation, request the transfer of a reject component using the TC-U-REJECT request primitive, with the appropriate problem code (mistyped parameter), and issue a confirm primitive with the provider error parameter set to "invalid respons... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.