hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
17250281ac36b9d402e66d0077cd67fd | 100 974 | 21.8.3 Process in the VLR for Remote User Free | The MAP process in the VLR to handle Remote User Free is shown in figure 21.8/4. The MAP process invokes a macro not defined in this subclause; the definitions of this macro can be found as follows: Check_Confirmation see subclause 25.2.2; Successful outcome (Recall accepted) When the MAP process receives a MAP_REMOTE_... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 22 Supplementary services procedures | The following application contexts exist for handling of supplementary services: - accessUnstructuredSsContext; - accessFunctionalSsContext. The accessUnstructuredSsContext refers to a simple MAP users, for which the corresponding MAP process can be identified by the MAP-Provider directly. However, the accessFunctional... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 22.1 Functional supplementary service processes | |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 22.1.1 Functional supplementary service process co-ordinator for MSC | Upon receipt of a CM-Service request with CM-service type = SS, the MSC initiates the process access request procedure towards the VLR as described in clause 25 of the present document. Once a CM connection is established, the MSC can handle supplementary service indications from the MS. Table 22.1/1 shows the co-ordin... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 22.1.2 Functional supplementary service process co-ordinator for VLR | Any functional SS process in the VLR starts by the VLR receiving the MAP_PROCESS_ACCESS_REQUEST indication. The VLR then acts as described in clause 25 of the present document. If the Process Access Request was successful, the VLR can handle supplementary service indications from the MSC. Table 22.1/2 shows the co-ordi... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 22.1.3 Functional supplementary service process co-ordinator for HLR | Any functional SS process in the HLR starts by the HLR receiving a MAP-OPEN service indication. If that service is successful, the HLR can handle supplementary service indications from the VLR. Table 22.1/3 shows the co-ordinating process' reaction on receipt of specific SS service indications from the VLR. After the r... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 22.1.4 Call completion supplementary service process co-ordinator for HLR | The MAP co-ordinating process in the HLR to handle a dialogue opened with the callCompletion application context is shown in figure 22.1/4. The MAP process invokes a macro not defined in this subclause; the definition of this macro can be found as follows: Receive_Open_Ind see subclause 25.1.1. Any call completion SS p... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 22.2 Registration procedure | |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 22.2.1 General | The registration procedure is used to register data related to a supplementary service in the HLR. The registration procedure is a fully transparent communication between the MS and the HLR, except that some services may be invoked as a result of the procedure, as described in the subclauses below. The registration pro... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 22.2.2 Procedures in the MSC | Supplementary service registration The A_REGISTER_SS service indication received by the MAP user in the MSC contains the SS-Code and any parameters that are related to the supplementary service. The MAP user transfers the received information to the VLR in the MAP_REGISTER_SS request without checking the contents of th... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 22.2.3 Procedures in the VLR | Supplementary service registration When receiving the MAP_REGISTER_SS indication, the MAP user in the VLR transfers the information to the HLR in the MAP_REGISTER_SS request without checking the contents of the service indication. The VLR then awaits the receipt of the MAP_REGISTER_SS confirm from the HLR. The MAP user... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 22.2.4 Procedures in the HLR | The procedure in the HLR is initiated when it receives a MAP_REGISTER_SS indication. The HLR acts as follows: - if the operator has barred the subscriber from access to supplementary services, the Call Barred error should be returned to the VLR. The parameter "operatorBarring" shall be included with the error. The supp... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 22.3 Erasure procedure | |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 22.3.1 General | The erasure procedure is used to erase data related to a supplementary service in the HLR. The erasure procedure is a fully transparent communication between the MS and the HLR, except that some services may be invoked as a result of the procedure, as described in the subclauses below. The erasure procedure is shown in... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 22.3.2 Procedures in the MSC | The MSC procedures for erasure are identical to those specified for registration in subclause 22.2.2. The text and diagrams in subclause 22.2.2 apply with all references to registration changed to erasure. ETSI ETSI TS 100 974 V7.3.0 (2000-02) 619 (GSM 09.02 version 7.3.0 Release 1998) |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 22.3.3 Procedures in the VLR | The VLR procedures for erasure are identical to those specified for registration in subclause 22.2.3. The text and diagrams in subclause 22.2.3 apply with all references to registration changed to erasure. |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 22.3.4 Procedures in the HLR | The HLR procedure for erasure is identical to those specified for registration in subclause 22.2.4. The text and diagrams in subclause 22.2.4 apply with all references to registration changed to erasure. |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 22.4 Activation procedure | |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 22.4.1 General | The activation procedure is used to activate a supplementary service in the HLR. The activation procedure is a fully transparent communication between the MS and the HLR, except that some services may be invoked as a result of the procedure, as described in the subclauses below. The activation procedure is shown in fig... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 22.4.2 Procedures in the MSC | The A_ACTIVATE_SS service indication received by the MAP user in the MSC contains the SS-Code and any parameters related to the supplementary service. The MSC transfers the received information to the VLR in the MAP_ACTIVATE_SS request without checking the contents of the service indication. Rules for the mapping are d... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 22.4.3 Procedures in the VLR | Supplementary service activation When receiving the MAP_ACTIVATE_SS indication, the MAP user in the VLR transfers the information to the HLR in the MAP_ACTIVATE_SS request without checking the contents of the service indication. The VLR may then receive the MAP_GET_PASSWORD indication. This information is transferred t... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 22.4.4 Procedures in the HLR | The procedure in the HLR is initiated when it receives a MAP_ACTIVATE_SS indication. The HLR acts as follows: - if the operator has barred the subscriber from access to supplementary services, the Call Barred error should be returned to the VLR. The parameter "operatorBarring" shall be included with the error. The supp... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 22.5 Deactivation procedure | |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 22.5.1 General | The deactivation procedure is used to deactivate a supplementary service in the HLR. The deactivation procedure is a fully transparent communication between the MS and the HLR, except that some services may be invoked as a result of the procedure, as described in the subclauses below. The deactivation procedure is show... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 22.5.2 Procedures in the MSC | The MSC procedures for deactivation are identical to those specified for activation in subclause 22.4.2. The text and diagrams in subclause 22.4.2 apply with all references to activation changed to deactivation. |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 22.5.3 Procedures in the VLR | The VLR procedures for deactivation are identical to those specified for activation in subclause 22.4.3. The text and diagrams in subclause 22.4.3 apply with all references to activation changed to deactivation. |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 22.5.4 Procedures in the HLR | The HLR procedures for deactivation are identical to those specified for activation in subclause 22.4.4. The text and diagrams in subclause 22.4.4 apply with all references to activation changed to deactivation. |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 22.6 Interrogation procedure | |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 22.6.1 General | The interrogation procedure is used to retrieve information related to a supplementary service from the VLR or the HLR. It is the VLR which decides whether an interrogation request should be forwarded to the HLR or not. Some non- supplementary service related services may be invoked as a result of the procedure, as des... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 22.6.2 Procedures in the MSC | The MSC procedures for interrogation are identical to those specified for registration in subclause 22.2.2. The text and diagrams in subclause 22.2.2 apply with all references to registration changed to interrogation. |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 22.6.3 Procedures in the VLR | Supplementary service interrogation When receiving the MAP_INTERROGATE_SS indication, the MAP user acts as follows: - if the operator has barred the subscriber from access to supplementary services, the error Call Barred is returned to the MSC. The parameter "operatorBarring" shall be included with the error. The inter... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 22.6.4 Procedures in the HLR | When receiving the MAP_INTERROGATE_SS indication, the MAP user acts as follows: - if the operator has barred the subscriber from access to supplementary services, the error Call Barred is returned to the MSC. The parameter "operatorBarring" shall be included with the error; - if the supplementary service is not support... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 22.7 Invocation procedure | |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 22.7.1 General | The invocation procedure is used to check subscription data in the VLR for certain supplementary services which are invoked after the call set-up phase is finished. For invocation of supplementary services which are invoked during the call set-up phase, please refer to the Call Handling procedure descriptions. The invo... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 22.7.2 Procedures in the MSC | Process access request Before the Call Hold or Multi-Party supplementary services can be invoked, a CC connection must be established between the MS and the MSC as described in GSM 04.08 and the Call Handling procedure descriptions within the present document. When an A_INVOKE_SS request message arrives at the MSC duri... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 22.7.3 Procedures in the VLR | Process Access Request When receiving the MAP_PROCESS_ACCESS_REQUEST indication, the VLR acts as described in clause 25 of the present document. Supplementary service invocation When receiving the MAP_INVOKE_SS indication, the MAP user acts as follows: - if the operator has barred the subscriber from access to suppleme... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 22.8 Password registration procedure | |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 22.8.1 General | The password registration procedure is used to register a password in the HLR. The password registration procedure is a fully transparent communication between the MS and the HLR, except that some services may be invoked as a result of the procedure, as described below. The password registration procedure is shown in f... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 22.8.2 Procedures in the MSC | The password registration procedure in the MSC is identical to that for activation specified in subclause 22.4.2. All the text and diagrams in subclause 22.4.2 apply with all references to activation changed to password registration. |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 22.8.3 Procedures in the VLR | The password registration procedure in the VLR is identical to that for activation specified in subclause 22.4.3. All the text and diagrams in subclause 22.4.3 apply with all references to activation changed to password registration. |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 22.8.4 Procedures in the HLR | The procedure in the HLR is initiated when it receives a MAP_REGISTER_PASSWORD indication. The HLR acts as follows: - if the operator has barred the subscriber for access to supplementary services, the Call Barred error is returned to the VLR. The parameter "operatorBarring" shall be included with the error; - if any i... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 22.9 Mobile Initiated USSD procedure | |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 22.9.1 General | The procedure supports supplementary service signalling procedures which can allow PLMN specific services to be introduced. The message flow for the procedure can be found in GSM 03.90. The following services may be used: MAP_PROCESS_ACCESS_REQUEST (defined in clauses 8 and 25); MAP_TRACE_SUBSCRIBER_ACTIVITY (defined i... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 22.9.2 Procedures in the MSC | Before the Process Unstructured SS Request service can be invoked, a call independent CM connection must be created between the MS and the MSC. Once a CM-connection is established, the MSC may handle the A_PROCESS_UNSTRUCTURED_SS_REQUEST from the MS. This message contains information input by the user, the message may ... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 22.9.3 Procedures in the VLR | The initiation of the process is shown in subclause 22.1.2. Once a MAP dialogue is established, the VLR may handle the MAP_PROCESS_UNSTRUCTURED_SS_REQUEST from the MSC. This message contains information input by the user, the message may be fed to an application contained locally in the VLR or to the HLR. The rules for... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 22.9.4 Procedures in the HLR | The initiation of the process is shown in subclause 22.1.3. Once a MAP dialogue is established, the HLR may handle the MAP_PROCESS_UNSTRUCTURED_SS_REQUEST from the VLR. This message contains information input by the user. If the alphabet used for the message is understood then the message shall either be fed to an appl... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 22.10 Network initiated USSD procedure | 22.10.1 General The procedure supports supplementary service signalling procedures which can allow PLMN specific services to be introduced. The message flow for the procedure can be found in GSM 03.90. The following services may be used: MAP_PAGE (defined in clauses 8 and 25); MAP_SEARCH_FOR_MOBILE_SUBSCRIBER (defined ... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 22.11 Common macros for clause 22 | The following macros are used for the description of more than one of the supplementary service processes described in clause 22: ETSI ETSI TS 100 974 V7.3.0 (2000-02) 680 (GSM 09.02 version 7.3.0 Release 1998) 22.11.1 SS Password handling macros Macro Get_Password_MSC This macro is used by the MSC to relay a request f... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 22.12 Supplementary Service Invocation Notification procedure | 22.12.1 General The Supplementary Service Invocation Notification procedure is used to notify a gsmSCF about the invocation of a GSM Supplementary Service. The password registration procedure is shown in figure 22.12.1/1. The following services may be used: MSC gsmSCF (1) -----------------------------------------------... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 22.13 Activation of a CCBS request | 22.13.1 General The message flow to activate a CCBS request is shown in figure 22.13.1/1. VLR HLR MAP_REGISTER_CC_ENTRY ---------------------------------------------------------------> MAP_REGISTER_CC_ENTRY ack <--------------------------------------------------------------- Figure 22.13.1/1: Message flow to activate a... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 22.14 Deactivation of a CCBS request | 22.14.1 General The message flow to deactivate a CCBS request is shown in figure 22.14.1/1. VLR HLR MAP_ERASE_CC_ENTRY ---------------------------------------------------------------> MAP_ERASE_CC_ENTRY ack <--------------------------------------------------------------- Figure 22.14.1/1: Message flow to deactivate a C... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 23 Short message service procedures | |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 23.1 General | The short message service procedures are used to control both mobile originated and mobile terminated short message transfer. Four procedures exist for short message services: - mobile originated short message service transfer; - mobile terminated short message service transfer; - short message alert procedure; - short... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 23.1.1 Mobile originated short message service Co-ordinator for the MSC | The A_CM_SERV_REQ message (GSM 04.08) is received from the A-interface containing the CM service type. This parameter indicates mobile originated short message service. The service MAP_PROCESS_ACCESS_REQUEST is started. If the MAP_PROCESS_ACCESS_REQUEST service ends successfully, the MS initiates mobile originated shor... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 23.1.2 Short message Gateway Co-ordinator for the HLR | The MAP_OPEN indication opens a dialogue for the short message procedure between the gateway MSC and the HLR when the application context shortMessageGatewayContext is received. If that service is successful, the Co-ordinator can receive the first service primitive from the MAP_PM. Depending on the received primitive, ... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 23.1.3 Mobile originated short message service Co-ordinator for the SGSN | The MS initiates mobile originated short message transfer or alerting indication. Depending on the situation, the appropriate process is initiated as follows: - if the A_RP_MO_DATA indication is received, the process MOSM_SGSN is initiated (see subclause 23.2.4); - if the A_RP_SM_MEMORY_AVAILABLE indication is received... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 23.2 The mobile originated short message transfer procedure | The mobile originated short message service procedure is used to forward short message from a mobile subscriber to a Service Centre. The mobile originated short message service procedure is shown in figure 23.2/1. (B:":< (7(#:... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 23.2.1 Procedure in the servicing MSC | The activation of the MAP_PROCESS_ACCESS_REQUEST service is described in the subclause 25.4.1. When receiving the short message from the A-interface, the MSC sends the MAP_SEND_INFO_FOR_MO_SMS request to the VLR. As a response the MSC will receive the MAP_SEND_INFO_FOR_MO_SMS confirmation from VLR indicating that: - th... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 23.2.2 Procedure in the VLR | The MAP_PROCESS_ACCESS_REQUEST indication starts the MAP_PROCESS_ACCESS_REQUEST service in the VLR. The application context in the MAP_OPEN indication is mobile originated short message transfer. If the service MAP_PROCESS_ACCESS_REQUEST is successful, the VLR waits for the next message from the MSC. When receiving the... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 23.2.3 Procedure in the interworking MSC | This procedure applies only when the IWMSC is not the servicing MSC or SGSN. When receiving a MAP_OPEN indication primitive that is not associated with any MAP service indication primitive and if the dialogue is accepted, the MAP service-user in the interworking MSC issues a MAP_DELIMITER request primitive in order to ... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 23.2.4 Procedure in the servicing SGSN | When receiving the short message from the MS, the SGSN acts as follows: - if there is incompatibility in the subscription check, the RP_ERROR cause requested facility not subscribed is provided to the mobile station; - if the short message transfer would contravene operator determined barring, the RP_ERROR cause operat... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 23.3 The mobile terminated short message transfer procedure | The mobile terminated short message transfer procedure is used for forwarding a short message or several short messages from a Service Centre to a mobile subscriber. The mobile terminated short message procedure for a single short message transfer is shown in figure 23.3/1. ... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 23.3.1 Procedure in the Servicing MSC | When initiating the dialogue with the servicing MSC, the SMS Gateway MSC must provide the IMSI of the subscriber to whom the short message is directed. The IMSI can be included either in the Destination Reference of the MAP_OPEN indication received from the SMS Gateway MSC or in the sm-RP-DA information field of the MA... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 23.3.2 Procedures in the VLR | When receiving the MAP_SEND_INFO_FOR_MT_SMS indication, the VLR will act as follows: - the parameters and data in the primitive are checked by the macro "Check_Indication". A data failure is reported as an unexpected data value error or a data missing error depending on the nature of the failure; - for mobile terminate... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 23.3.3 Procedures in the HLR | The MAP_SEND_ROUTING_INFO_FOR_SM indication is received from the GMSC. The following error cases are reported to the GMSC in the MAP_SEND_ROUTING_INFO_FOR_SM response as an unsuccessful outcome of the procedure: - if the necessary parameters and data are not present in the primitive or they are badly formatted, the dat... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 23.3.4 Procedures in the gateway MSC | The short message handling function of the GMSC will request routing information when a mobile terminated short message is received from a Service Centre. The GMSC sends the MAP_SEND_ROUTING_INFO_FOR_SM request to the HLR containing the subscriber data of the mobile subscriber and the indication that the SMS-GMSC suppo... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 23.3.5 Procedure in the Servicing SGSN | When initiating the dialogue with the servicing SGSN, the SMS Gateway MSC must provide the IMSI of the subscriber to whom the short message is directed. The IMSI is included in the sm-RP-DA information field of the MAP_MT_FORWARD_SHORT_MESSAGE indication. When receiving a MAP_OPEN indication primitive that is not assoc... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 23.4 The Short Message Alert procedure | The Short Message Alert procedure is used for alerting the Service Centre when the mobile subscriber is active after a short message transfer has failed because the mobile subscriber is not reachable or when the MS has indicated that it has memory capacity to accept a short message. The Short Message Alert procedure fo... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 23.4.1 Procedures in the Servicing MSC | The activation of the MAP_PROCESS_ACCESS_REQUEST service is described in the subclause 23.6.2. After receiving the SM memory capacity available indication, the servicing MSC sends the MAP_READY_FOR_SM request to the VLR indicating memory available. The outcome of that procedure is one of the following: - successful ack... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 23.4.2 Procedures in the VLR | |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 23.4.2.1 The Mobile Subscriber is present | When receiving the MAP_PROCESS_ACCESS_REQUEST indication, MAP_UPDATE_LOCATION_AREA indication while the MS not reachable flag (MNRF) is set, the VLR will send the MAP_READY_FOR_SM request towards the HLR. The Alert Reason is set to indicate that the mobile subscriber is present for non GPRS. If the authentication proce... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 23.4.2.2 The Mobile Equipment has memory available | The MAP_PROCESS_ACCESS_REQUEST indication starts the MAP_PROCESS_ACCESS_REQUEST service in the VLR. The application context in the MAP_OPEN indication refers to the short message alerting procedure. If the service MAP_PROCESS_ACCESS_REQUEST is successful, the VLR waits for the next message from the MSC. When receiving ... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 23.4.3 Procedures in the HLR | When receiving the MAP_READY_FOR_SM indication, the HLR will check the contents. Data errors are reported to the VLR as an unexpected data value or a data missing error depending on the error. If the HLR does not support the MNRF or MNRG, MCEF, and MWD a facility not supported error is reported to the VLR or SGSN. If t... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 23.4.4 Procedures in the Interworking MSC | When a MAP_ALERT_SERVICE_CENTRE indication is correctly received by the IWMSC, the IWMSC will forward the alerting to the given Service Centre if possible. Data errors are reported to the HLR as an unexpected data value or a data missing error depending on the error. The short message alert procedure is shown in figure... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 23.4.5.1 The Mobile Subscriber is present | When receiving Page response, Attach request or Routing area update request messages (TS GSM 04.08), while the MS not reachable for GPRS (MNRG) flag is set, the SGSN will send the MAP_READY_FOR_SM request towards the HLR. The Alert Reason is set to indicate that the mobile subscriber is present for GPRS. When receiving... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 23.4.5.2 The Mobile Equipment has memory available | After receiving the SM memory capacity available indication, the servicing SGSN sends the MAP_READY_FOR_SM request to the HLR indicating memory available for GPRS. The outcome of that procedure is one of the following: - successful acknowledgment. The SGSN sends the corresponding message to the MS; - negative acknowled... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 23.5 The SM delivery status report procedure | The SM delivery status report procedure is used to set the Service Centre address into the message waiting list in the HLR because the subscriber is absent or unidentified or the memory capacity is exceeded. The procedure sets - the memory capacity exceeded flag in the HLR if the MS memory does not have room for more m... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 23.5.1 Procedures in the HLR | When the HLR receives a MAP_REPORT_SM_DELIVERY_STATUS indication, it acts as described in the subclause 23.6, macro Report_SM_Delivery_Stat_HLR. The short message delivery status report process in the HLR is shown in figure 23.5/2. ETSI ETSI TS 100 974 V7.3.0 (2000-02) 778 (GSM 09.02 version 7.3.0 Release 1998) Figure ... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 23.5.2 Procedures in the gateway MSC | The GMSC invokes the short message delivery status report procedure if an absent subscriber_SM indication, unidentified subscriber indication, SM delivery failure error indicating MS memory capacity exceeded or both are received from the servicing MSC, SGSN or both during a mobile terminated short message transfer, and... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 23.6 Common procedures for the short message clause | |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 23.6.1 The macro Report_SM_Delivery_Stat_HLR | This macro is used when the HLR receives a MAP_REPORT_SM_DELIVERY_STATUS indication from the GMSC. The HLR responses to the indication as follows: - if the flag « GPRS Support Indicator » is absent then if the subscriber is a GPRS subscriber and a non-GPRS susbcsriber with the option « transfer of SM via the SGSN when ... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 24 GPRS process description | |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 24.1 General | The MAP GPRS procedures are used for the Network Requested PDP-Context Activation procedures. The stage 2 specification for General Packet Radio Service (GPRS) is in GSM 03.60 [100]. 24.1.1 Process in the HLR for Send Routing Information for GPRS The MAP process in the HLR to provide routing information for a network-r... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 24.1.2 Process in the GGSN for Send Routing Information for GPRS | Successful Outcome When the MAP process receives a Send Routing Info For Gprs request from the GPRS application process in the GGSN, it requests a dialogue with the HLR whose identity is contained in the Send Routing Info For Gprs request by sending a MAP_OPEN service request, requests routeing information using a MAP_... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 24.2.2 Process in the GGSN for Failure Report | Successful Outcome When the MAP process receives a Failure Report request from the GPRS application process in the GGSN, it requests a dialogue with the HLR whose identity is contained in the Failure Report request by sending a MAP_OPEN service request, sending failure information using a MAP_FAILURE_REPORT service req... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 24.3.1 Process in the GGSN for Note Ms Present For Gprs | The MAP process in the GGSN to inform that the subscriber is present for GPRS again is shown in figure 24.3/1. The MAP process invokes a macro not defined in this subclause; the definition of this macro can be found as follows: Receive_Open_Ind see subclause 25.1.1; Check_Indication see subclause 25.2.1. Successful out... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 24.3.2 Process in the HLR for Note Ms Present For Gprs | Successful Outcome When the MAP process receives a Note Ms Present For Gprs request from the GPRS application process in the HLR, it requests a dialogue with the GGSN whose identity is contained in the Note Ms Present For Gprs request by sending a MAP_OPEN service request, sending necessary information using a MAP_NOTE... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 25 General macro description | |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 25.1 MAP open macros | |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 25.1.1 Macro Receive_Open_Ind | This macro is used by a MAP service-user procedure when a peer entity requests opening of a dialogue. If the application context received in the MAP-OPEN indication primitive indicates a context name of the MAP version one context set, the macro takes the Vr exit.. If an application-context different from version 1 is ... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 25.1.2 Macro Receive_Open_Cnf | This macro is used by a user procedure after it requested opening of a dialogue towards a peer entity. On receipt of a MAP_OPEN Confirmation with a "Result" parameter indicating "Dialogue Accepted", the macro takes the OK exit. If the "Result" parameter indicates "Dialogue Refused", the "Refuse-reason" parameter is exa... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 25.2.1 Macro Check_Indication | If a parameter required by the application is missing from the indication, the macro takes the error exit, with a user error of "Data Missing". If a parameter not expected by the application is present in the indication, or an expected parameter has a value not in the set of values permitted by the application, the mac... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 25.2.2 Macro Check_Confirmation | If the confirmation contains a provider error the macro issues a MAP CLOSE request and takes the provider error exit. Otherwise, if the confirmation contains a user error the macro takes the user error exit. Otherwise, if a parameter required by the application is missing from the confirmation, or a parameter not expec... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 25.3 The page and search macros | |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 25.3.1 Macro PAGE_MSC | This macro (see figure 25.3/1) is called if a mobile terminating call set-up, an unstructured SS notification, a network- initiated unstructured SS request or a mobile terminating short message is to be delivered to the MS and the current location area identity of the MS is known in the VLR. When the MSC receives a MAP... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 25.3.2 Macro Search_For_MS_MSC | This macro (see figure 25.3/2) is called if a mobile terminating call set-up, an unstructured SS notification, a network- initiated unstructured SS request or a mobile terminating short message is to be delivered to the MS and the current location area identity of the MS is not known in VLR. When the MSC receives a MAP... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 25.4 Macros for handling an Access Request | These macros are invoked when a MS accesses the network, e.g. to set up an outgoing call or when responding to paging. The macro handles identification and authentication of the mobile subscriber as well as invocation of security related features (see GSM 02.09). |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 25.4.1 Macro Process_Access_Request_MSC | This macro is invoked by any procedure receiving an access request from the MS, e.g. the page response at mobile terminating call set-up or the request for outgoing call set-up. If no dialogue with the VLR exists (e.g. within the procedure for outgoing call set-up), the MSC will open a dialogue towards the VLR by sendi... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 25.4.2 Macro Process_Access_Request_VLR | When the VLR receives a MAP_PROCESS_ACCESS_REQUEST indication, the VLR will check this indication first (macro Check_Indication, see subclause 25.2). In case of negative outcome, the macro will proceed with the error handling described below. If the indication data are correct, it is checked first whether the subscribe... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 25.4.3 Macro Identification Procedure | This macro is invoked by the macro Process_Access_Request_VLR in case the subscribers identity is not known in the VLR. If the identity received from the MS is an IMSI, the error Unidentified Subscriber will be set and reported back to the calling macro (to be sent in the MAP_PROCESS_ACCESS_REQUEST response). The same ... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.