hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
17250281ac36b9d402e66d0077cd67fd | 100 974 | 19.1.4.2 Detailed procedure in the VLR | When the VLR receives an indication from O&M that an MS record is to be purged, it invokes the MAP_PURGE_MS service (see figure 19.1.4/2). The VLR opens the dialogue to the HLR with a MAP_OPEN request containing no user specific parameters. The MAP_PURGE_MS request contains the IMSI of the MS which is to be purged and ... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 19.1.4.3 Detailed procedure in the HLR | Opening of the dialogue is described in the macro Receive_Open_Ind in subclause 25.1. The possible outcomes are: - termination of the procedure if the AC indicates a version 1 dialogue, as this procedure is not defined for version 1; - termination of the procedure if there is an error; - dialogue acceptance, in which c... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 19.1.4.4 Detailed procedure in the SGSN | When the SGSN receives an indication from O&M that an MS record is to be purged, it invokes the MAP_PURGE_MS service (see figure 19.1.4/4). The SGSN opens the dialogue to the HLR with a MAP_OPEN request containing no user specific parameters. The MAP_PURGE_MS request contains the IMSI of the MS which is to be purged an... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 19.2 Handover procedure | |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 19.2.1 General | The handover between different MSCs is called Inter-MSC handover. The interfaces involved for Inter-MSC handover are shown in figure 19.2/1. Following two Inter-MSC handover procedures apply: 1) Basic Inter-MSC handover: The call is handed over from the controlling MSC, called MSC-A to another MSC, called MSC-B (figure... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 19.2.2 Handover procedure in MSC-A | This subclause describes the handover procedure in MSC-A, including the request for a basic handover to another MSC (MSC-B), subsequent handover to a third MSC (MSC-B') or back to the controlling MSC (MSC-A). |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 19.2.2.1 Basic handover | When MSC-A has decided that a call has to be handed over to MSC-B, the Handover Control Application in MSC-A requests the MAP application to initiate the MAP_PREPARE_HANDOVER request to MSC-B. MSC-A opens the dialogue to MSC-B with a MAP_OPEN request containing no user specific parameters and sends a MAP_PREPARE_HANDOV... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 19.2.2.2 Handling of access signalling | If required, the Handover Control Application in MSC-A requests the MAP application to invoke the MAP_FORWARD_ACCESS_SIGNALLING request containing the information to be transferred to the A-interface of MSC-B (e.g. call control information). MAP_FORWARD_ACCESS_SIGNALLING is a non-confirmed service. MSC-B will then forw... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 19.2.2.3 Other procedures in stable handover situation | During a call and after handover, a number of procedures between MSC-A and BSS-B controlled by or reported to MSC-A may be initiated in both directions by invoking a MAP_FORWARD_ACCESS_SIGNALLING request and reception of a MAP_PROCESS_ACCESS_SIGNALLING indication. |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 19.2.2.4 Subsequent handover | When MSC-A receives a MAP_PREPARE_SUBSEQUENT_HANDOVER request, it will start the procedure of handing the call over to a third MSC (MSC-B'), or back to the controlling MSC (MSC-A). If the new handover procedure towards MSC-B' or MSC-A is successful, the handover control application in MSC-A will request the release of ... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 19.2.2.5 SDL Diagrams | The SDL diagrams on the following pages describe the user processes in MSC-A for the procedures described in this subclause. The services used are defined in subclause 8.4. NOTE: The message primitives HO_CA_MESSAGE used in the SDL-Diagrams are used to show the internal co- ordination between the MAP application and th... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 19.2.3 Handover procedure in MSC-B | This subclause describes the handover procedure in MSC-B, including the request for a handover from another MSC (MSC-A), subsequent handover to a third MSC (MSC-B') or back to the controlling MSC (MSC-A). |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 19.2.3.1 Basic handover | Opening of the dialogue is described in the macro Receive_Open_Ind in subclause 25.1. When MSC-B process receives a MAP_PREPARE_HANDOVER indication from MSC-A, MSC-B requests its associated VLR to provide a handover number, unless the parameter HO-NumberNotRequired is received in the indication. When the connection bet... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 19.2.3.2 Allocation of handover number | When a handover number is required, a MAP_ALLOCATE_HANDOVER_NUMBER request will be sent to the VLR. The handover number is received in the MAP_SEND_HANDOVER_REPORT request, and will be included in the MAP_PREPARE_HANDOVER response to MSC-A. As soon as the call from MSC-A using the handover number arrives in MSC-B, MSC-... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 19.2.3.3 Handling of access signalling | If required by the Handover Control Application, MSC-B invokes the MAP_PROCESS_ACCESS_SIGNALLING request containing the information received on the A-interface that should be transferred to MSC-A (e.g. call control information). MAP_PROCESS_ACCESS_SIGNALLING is a non-confirmed service and any response from MSC-A will r... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 19.2.3.4 Other procedures in stable handover situation | During a call and after handover, a number of procedures between MSC-A and BSS-B controlled by or reported to MSC-A may be initiated by involving access signalling transfer in both directions. |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 19.2.3.5 Subsequent handover | The procedure is used when the Handover Control Application in MSC-B has decided that a call is to be handed over to another MSC (either back to the controlling MSC (MSC-A) or to a third MSC (MSC-B')). After the MAP_PREPARE_SUBSEQUENT_HANDOVER response is received from MSC-A, MSC-B will await the disconnection of the c... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 19.2.3.6 SDL Diagrams | The SDL diagrams on the following pages describe the user process in MSC-B for the procedures described in this subclause. The services used are defined in subclause 8.4. ETSI ETSI TS 100 974 V7.3.0 (2000-02) 439 (GSM 09.02 version 7.3.0 Release 1998) NOTE 1: The message primitives HO_CA_MESSAGE in the SDL-diagrams are... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 19.2.4 Handover error handling macro | This macro is used for the handover procedures to receive errors from the MSCs and from the Handover Control Application at any state of a handover process. If a MAP_NOTICE indication is received, the Handover Control Application is informed and the actual situation is kept and the Handover Control Application decides ... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 19.2.5 Handover procedure in VLR | |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 19.2.5.1 Allocation of handover number | When receiving the MAP_ALLOCATE_HANDOVER_NUMBER indication, the VLR will determine whether a handover number is available. If no handover number is available, this will be indicated by a MAP_ALLOCATE_HANDOVER_NUMBER response with the appropriate error. The handover number allocated will otherwise be returned to MSC-B i... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 19.2.5.2 SDL Diagrams | The SDL diagrams on the following pages describe the user processes in VLR for the procedures described in this subclause. The services used are defined in subclause 8.4. ETSI ETSI TS 100 974 V7.3.0 (2000-02) 454 (GSM 09.02 version 7.3.0 Release 1998) Figure 19.2.5/1 Process VLR_B_HO 19.2.5_1.1(2) NULL Receive_Open_ind... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 19.3 Fault recovery procedures | After a fault of a location register, the fault recovery procedures ensure that the subscriber data in the VLR or in the SGSN become consistent with the subscriber data that are stored in the HLR for the MS concerned and that the location information in HLR , VLR and SGSN reflect accurately the current location of the ... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 19.3.1 VLR fault recovery procedures | The following processes are involved with the restoration of one IMSI record in the VLR: - In case of a location registration request from the MS: Update_Location_Area_VLR subclause 19.1.1.3; Update_Location_HLR subclause 19.1.1.4. - In case of a mobile terminated call: PRN_VLR subclause 21.2.4; RESTORE_DATA_VLR subcla... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 19.3.2 HLR fault recovery procedures | The following processes are involved with the restart of the HLR: - HLR_RESTART subclause 19.3.2; - REC_RESET_IN_VLR subclause 19.3.2; - REC_RESET_IN_SGSN subclause 19.3.2. In the case of a location registration request from the MS, the following processes are involved with the HLR restoration procedure: - Update_Locat... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 19.3.3 VLR restoration: the restore data procedure in the HLR | The MAP_RESTORE_DATA procedure in the HLR (Process RESTORE_DATA_HLR) is described in this subclause; the corresponding procedure in the VLR (RESTORE_DATA_VLR) is described in subclause 21.2.4. The process RESTORE_DATA_HLR makes use of the following macros: - Receive_Open_Ind subclause 25.1.1; - Check_Indication subclau... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 19.4 Macro Insert_Subs_Data_Framed_HLR | This macro is used by any procedure invoked in HLR which requires the transfer of subscriber data by means of the InsertSubscriberData operation (e.g. Update Location or Restore Data). The invocation of the operation is done in a dialogue already opened by the framing procedure. Therefore the latter is the one that han... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 20 Operation and maintenance procedures | |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 20.1 General | The Operation and Maintenance procedures are needed for operating and maintaining the GSM PLMN network. The following procedures exist for operation and maintenance purposes: i) Tracing procedures; ii) Subscriber Data Management procedures; iii) Subscriber Identity procedures. The following application contexts refer t... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 20.1.1 Tracing Co-ordinator for the VLR | The MAP_OPEN indication opens the dialogue for the stand-alone tracing procedure when the application context tracingContext is received. If that service is successful, the Co-ordinator can receive the firs service primitive from the MAP_PM. Depending on the received primitive, the user process is created as follows: -... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 20.1.2 Subscriber Data Management Co-ordinator for the VLR | The MAP_OPEN indication opens the dialogue for the stand-alone subscriber data management procedure when the application context subscriberDataManagementContex is received. If that service is successful, the Co-ordinator can receive the firs service primitive from the MAP_PM. Depending on the received primitive, the us... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 20.1.3 Tracing Co-ordinator for the SGSN | The MAP_OPEN indication opens the dialogue for the stand-alone tracing procedure when the application context tracingContext is received. If that service is successful, the Co-ordinator can receive the firs service primitive from the MAP_PM. Depending on the received primitive, the user process is created as follows: -... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 20.1.4 Subscriber Data Management Co-ordinator for the SGSN | The MAP_OPEN indication opens the dialogue for the stand-alone subscriber data management procedure when the application context subscriberDataManagementContext 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, the ... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 20.2 Tracing procedures | Three type of tracing procedures exist: i) Subscriber tracing management procedures; ii) Subscriber tracing procedures; iii) Event tracing procedures. The subscriber tracing management procedures are used for management of the status and the type of the tracing. The subscriber tracing activation procedure is used at lo... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 20.2.1 Procedures in the HLR | |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 20.2.1.1 Subscriber tracing activation procedure | When receiving the subscriber tracing mode activation command for a subscriber from the OMC, the HLR will activate tracing, if the subscriber is known and registered in the HLR and the subscriber is roaming in the home PLMN area. The MAP_ACTIVATE_TRACE_MODE request is sent to the VLR or to the SGSN where the subscriber... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 20.2.1.2 Subscriber tracing deactivation procedure | When receiving the subscriber trace mode deactivation command for a subscriber from the OMC, the HLR will send the MAP_DEACTIVATE_TRACE_MODE request to the VLR or to the SGSN where the subscriber is registered, if the trace mode activation has been carried out. The subscriber tracing in HLR is set to a deactive state. ... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 20.2.2 Procedures in the VLR | The VLR is involved in the following tracing procedures: i) Subscriber tracing activation procedure; ii) Subscriber tracing deactivation procedure; iii) Subscriber tracing procedure. |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 20.2.2.1 Subscriber tracing activation procedure | When receiving a MAP_ACTIVATE_TRACE_MODE indication, the VLR will check the parameters and data in the primitive. Data errors are reported as an unexpected data value error or as a data missing error depending on the nature of the error. If the subscriber is known, the tracing facility is supported and the tracing capa... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 20.2.2.2 Subscriber tracing deactivation procedure | When receiving a MAP_DEACTIVATE_TRACE_MODE indication, the VLR will check the parameters and data in the primitive. Data errors are reported as an unexpected data value error or as a data missing error depending on the nature of the error. If the subscriber is known and the tracing facility is supported, the successful... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 20.2.2.3 Subscriber tracing procedure | When the VLR receives a MAP_PROCESS_ACCESS_REQUEST or MAP_UPDATE_LOCATION_AREA indication related to any subscriber activity from the MSC, the subscriber tracing procedure may be carried out. The macro Trace_Subscriber_Activity_VLR is shown in figure 25.9/2. |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 20.2.3 Procedures in the MSC | The MSC is involved in the following tracing procedure: i) Subscriber tracing procedure. |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 20.2.3.1 Subscriber tracing procedure | When receiving the MAP_TRACE_SUBSCRIBER_ACTIVITY indication from the VLR, the MSC stores trace reference, trace type and the identity of the OMC in charge of the trace, and the MSC starts to collect the trace information. The MSC will send the trace record to the OMC. The macro Trace_Subscriber_Activity_MSC is shown in... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 20.2.4 Procedures in the SGSN | The SGSN is involved in the following tracing procedures: i) Subscriber tracing activation procedure; ii) Subscriber tracing deactivation procedure; |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 20.2.4.1 Subscriber tracing activation procedure | When receiving a MAP_ACTIVATE_TRACE_MODE indication, the SGSN will check the parameters and data in the primitive. Data errors are reported as an unexpected data value error or as a data missing error depending on the nature of the error. If the subscriber is known, the tracing facility is supported and the tracing cap... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 20.2.4.2 Subscriber tracing deactivation procedure in SGSN | When receiving a MAP_DEACTIVATE_TRACE_MODE indication, the SGSN will check the parameters and data in the primitive. Data errors are reported as an unexpected data value error or as a data missing error depending on the nature of the error. If the subscriber is known and the tracing facility is supported, the successfu... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 20.3 Subscriber data management procedures | Two types of subscriber data management procedures exist in the Mobile Application Part i) Subscriber Deletion; ii) Subscriber Data Modification. No requirements have been identified for the Subscriber creation and subscriber data interrogation procedures. The subscriber deletion and subscriber data modification proced... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 20.3.1 Procedures in the HLR | |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 20.3.1.1 Subscriber deletion procedure | When the subscriber deletion request is received from the OMC, the HLR shall delete the subscriber data from the HLR and initiate the MAP_CANCEL_LOCATION request to the VLR or to the SGSN where the subscriber is registered. The subscriber deletion procedure in the HLR is shown in the figure 20.3/3. ETSI ETSI TS 100 974... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 20.3.1.2 Subscriber data modification procedure | The OMC can modify the subscriber data in several different ways. The modifications can be categorized in following groups: a) no effect in the VLR; b) data shall be modified in both the HLR and the VLR; c) withdrawal of a basic service or a supplementary service requiring change to VLR data; d) modification affects on... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 20.3.2 Procedures in the VLR | |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 20.3.2.1 Subscriber deletion procedure | The subscriber deletion procedure in the VLR is described in the subclause 19.1. |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 20.3.2.2 Subscriber data modification procedure | When receiving either the MAP_INSERT_SUBSCRIBER_DATA indication or the MAP_DELETE_SUBSCRIBER_DATA indication, the VLR check the parameters and data in the primitive. Data errors are reported as an unexpected data value error or a data missing error depending on the nature of the error. After receiving the first MAP_INS... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 20.3.3 Procedures in the SGSN | |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 20.3.3.1 Subscriber deletion procedure | The subscriber deletion procedure in the SGSN is described in the subclause 19.1. |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 20.3.3.2 Subscriber data modification procedure | When receiving either the MAP_INSERT_SUBSCRIBER_DATA indication or the MAP_DELETE_SUBSCRIBER_DATA indication, the SGSN check the parameters and data in the primitive. Data errors are reported as an unexpected data value error or a data missing error depending on the nature of the error. After receiving the first MAP_IN... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 20.4 Subscriber Identity procedure | In the subscriber identity procedure the IMSI of the subscriber is retrieved from the HLR. The procedure is shown in figure 20.4/1. $ &... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 20.4.1 Subscriber identity procedure in the HLR | Opening of the dialogue is described in the macro Receive_Open_Ind in subclause 25.1, with outcomes: - procedure termination; or - dialogue acceptance, with proceeding as below. When receiving the MAP_SEND_IMSI indication, the HLR will check the parameters and data in the primitive. Data errors are reported as an unexp... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 20.4.2 Subscriber identity procedure in the VLR | When the IMSI request is received from the OMC, the VLR will send the MAP_SEND_IMSI request to the HLR. The contents of the response is sent to the OMC. The subscriber identity procedure in the VLR is shown in figure 20.4/3. ETSI ETSI TS 100 974 V7.3.0 (2000-02) 517 (GSM 09.02 version 7.3.0 Release 1998) Figure20.4/3: ... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 21 Call handling procedures | |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 21.1 General | The MAP call handling procedures are used: - to retrieve routeing information to handle a mobile terminating call; - to transfer control of a call back to the GMSC if the call is to be forwarded; - to retrieve and transfer information between anchor MSC and relay MSC for inter MSC group calls / broadcast calls; - to al... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 21.2 Retrieval of routing information | |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 21.2.1 General | The message flows for successful retrieval of routeing information for a mobile terminating call are shown in figure 21.2/1 (mobile terminating call which has not been optimally routed) and 21.2/2 (mobile-to-mobile call which has been optimally routed). 7(#%! 7!89 ... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 21.2.2 Process in the GMSC | The MAP process in the GMSC to retrieve routeing information for a mobile terminating call is shown in figure 21.2/3. The MAP process invokes macros not defined in this subclause; the definitions of these macros can be found as follows: Receive_Open_Cnf see subclause 25.1.2; Check_Confirmation see subclause 25.2.2. ETS... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 21.2.3 Procedures in the HLR | The MAP process in the HLR to retrieve routeing information for a mobile terminating call is shown in figure 21.2/4. The MAP process invokes macros not defined in this subclause; the definitions of these macros can be found as follows: Receive_Open_Ind see subclause 25.1.1; Receive_Open_Cnf see subclause 25.1.2; Check_... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 21.2.4 Process in the VLR to provide a roaming number | The MAP process in the VLR to provide a roaming number for a mobile terminating call is shown in figure 21.2/5. 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; Successful outcome When the MAP process receives a M... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 21.2.5 Process in the VLR to restore subscriber data | The MAP process in the HLR to restore subscriber data is shown in figure 21.2/6. The MAP process invokes macros not defined in this subclause; the definitions of these macros can be found as follows: Receive_Open_Cnf see subclause 25.1.2; Check_Confirmation see subclause 25.2.2; Insert_Subs_Data_VLR see subclause 25.7.... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 21.2.7 Process in the HLR for Any Time Interrogation | The message flows for successful retrieval of subscriber information related to an any time interrogation from the CAMEL server are shown in figure 21.2/8. <)= 9 $ ... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 21.2.7.1 Process in the gsmSCF | Out of the scope of the MAP specification. |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 21.2.3 Process in the HLR | The MAP process in the HLR to provide subscriber information in response to an interrogation from the CAMEL server is shown in figure 21.2/8. The MAP process invokes macros not defined in this subclause; the definitions of these macros can be found as follows: Receive_Open_Ind see subclause 25.1.1; Receive_Open_Cnf see... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 21.3 Transfer of call handling | |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 21.3.1 General | The message flow for successful transfer of call handling to forward a call is shown in figure 21.3/1. %! 7!8 :): ; (7!(; ; $ ... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 21.3.2 Process in the VMSC | The MAP process in the VMSC to retrieve routeing information for a mobile terminating call is shown in figure 21.3/2. The MAP process invokes macros not defined in this subclause; the definitions of these macros can be found as follows: Receive_Open_Cnf see subclause 25.1.2; Check_Confirmation see subclause 25.2.2. Suc... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 21.3.3 Process in the GMSC | The MAP process in the GMSC to handle a request for the GMSC to resume call handling is shown in figure 21.3/3. 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; Successful outcome When the MAP process receives a M... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 21.4 Inter MSC Group Call Procedures | |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 21.4.1 General | The message flows for successful inter MSC group call / broadcast call setup is shown in figure 21.4/1. ETSI ETSI TS 100 974 V7.3.0 (2000-02) 545 (GSM 09.02 version 7.3.0 Release 1998) 7(#"?( 2!8 ... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 21.4.2 Process in the Anchor MSC | The MAP process in the Anchor MSC to retrieve and transfer information from / to the Relay MSC for VBS and VGCS calls is shown in figure 21.4/2. The MAP process invokes macros not defined in this subclause; the definitions of these macros can be found as follows: Receive_Open_Cnf see subclause 25.1.2; Check_Indication ... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 21.4.3 Process in the Relay MSC | The MAP process in the Relay MSC to receive and transfer information from / to the Anchor MSC for VBS and VGCS calls is shown in figure 21.4/3. The MAP process invokes macros not defined in this subclause; the definitions of these macros can be found as follows: Receive_Open_Ind see subclause 25.1.2; Check_Indication s... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 21.5 Allocation and modifications of resources in an SIWFS | |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 21.5.1 General | The message flow for successful allocation and modification of resources in an SIWFS is shown in figure 21.5/1 (mobile originating call non-loop method), 21.5/2 (mobile originating call loop method) and 21.5/3 (mobile terminating call loop method). ETSI ETSI TS 100 974 V7.3.0 (2000-02) 557 (GSM 09.02 version 7.3.0 Rele... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 21.5.2 Process in the VMSC | The MAP process in the VMSC to allocate and modify resources in an SIWFS for a mobile call is shown in figure 21.5/4. The MAP process invokes macros not defined in this subclause; the definitions of these macros can be found as follows: Receive_Open_Cnf see subclause 25.1.2; Check_Confirmation see subclause 25.2.2. |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 21.5.2.1 Allocation of SIWFS resources | Successful Outcome When the MAP process receives a Provide SIWFS Number request from the call handling process in the VMSC, it requests a dialogue with the SIWF whose identity is contained in the Provide SIWFS Number request by sending a MAP_OPEN service request, requests resources in the SIWFS using a MAP_PROVIDE_SIWF... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 21.5.2.2 Modification of SIWFS resources initiated by the user | Successful Outcome When the MAP process receives an SIWFS Signalling Modify request from the call handling process in the VMSC, it requests a dialogue with the SIWFS whose identity is contained in the SIWFS Signalling Modify request by sending a MAP_SIWFS_SIGNALLING_MODIFY service request and waits for a response from ... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 21.5.2.3 Modification of SIWFS resources initiated by the SIWFS | Successful outcome If a MAP_SIWFS_SIGNALLING_MODIFY service indication is received, the MAP process sends an SIWFS signalling modify Info request to the call handling process in the VMSC, and waits for a response. The SIWFS ETSI ETSI TS 100 974 V7.3.0 (2000-02) 562 (GSM 09.02 version 7.3.0 Release 1998) signalling modi... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 21.5.3 Process in the SIWFS | The MAP process in the SIWFS to allocate and modify SIWFS resources for a mobile call is shown in figure 21.5/5. The MAP process invokes macros not defined in this subclause; the definitions of these macros can be found as follows: Receive_Open_Ind see subclause 25.1.1. Check_Confirmation see subclause 25.2.2. |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 21.5.3.1 Procedures for allocation of SIWFS resources | Successful outcome When the MAP process receives a MAP_OPEN indication with the application context locInfoRetrieval, it checks it by invoking the macro Receive_Open_Ind. If the macro takes the OK exit, the MAP process waits for a service indication. If a MAP_PROVIDE_SIWFS_NUMBER service indication is received, the MAP... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 21.5.3.2 Process for modification of SIWFS resources initiated by the user | Successful outcome If a MAP_SIWFS_SIGNALLING_MODIFY service indication is received, the MAP process sends an SIWFS signalling modify Info request to the call handling process in the SIWFS, and waits for a response. The SIWFS signalling modify request contains the parameters received in the MAP_SIWFS_SIGNALLING_MODIFY s... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 21.5.3.3 Process for modification of SIWFS resources initiated by the SIWFS | Successful Outcome When the MAP process receives an SIWFS Signalling Modify request from the call handling process in the SIWF, it requests a dialogue with the VMSC whose identity is contained in the VMSC Signalling Modify request by sending a MAP_DELIMITER service request, requests resources in the VMSC using a MAP_SI... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 21.6 Setting of Reporting State | |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 21.6.1 General | The message flow for setting the reporting state in a stand-alone dialogue is shown in figure 21.6.1/1. VLR HLR MAP_SET_REPORTING_STATE <--------------------------------------------------------------- MAP_SET_REPORTING_STATE ack ---------------------------------------------------------------> Figure 21.6/1: Message Flo... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 21.6.2 Process in the HLR for Set Reporting State stand-alone | The MAP process in the HLR to set the reporting state in the VLR in a separate stand-alone dialogue is shown in figure 21.6/2. The MAP process invokes macros not defined in this subclause; the definitions of these macros can be found as follows: Receive_Open_Cnf see subclause 25.1.2; Check_Confirmation see subclause 25... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 21.6.3 Reporting co-ordinator process in the VLR | The MAP co-ordinating process in the VLR to handle a dialogue opened with the reporting application context is shown in figure 21.6/3. 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 reporting process in the ... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 21.6.4 Process in the VLR to set the reporting state | The MAP process in the VLR to set the reporting state is shown in figure 21.6/4. The co-ordinator opens the process. The macro Receive_Set_Reporting_State_VLR handles the receipt of the request from the HLR, and the possible response from the CCBS application process in the VLR. When the macro exits, a MAP CLOSE is sen... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 21.7 Status Reporting | |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 21.7.1 General | The message flows for reporting the status of a subscriber are shown in figures 21.7/1 and 21.7/2. VLR HLR MAP_STATUS_REPORT ---------------------------------------------------------------> MAP_STATUS_REPORT ack <--------------------------------------------------------------- Figure 21.7/1: Status reporting, when monin... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 21.7.2 Process in the VLR for Status Reporting | The MAP process in the VLR to send a status report to the HLR is shown in figure 21.7/3. The MAP process invokes macros not defined in this subclause; the definitions of these macros can be found as follows: Receive_Open_Cnf see subclause 25.1.2; Check_Confirmation see subclause 25.2.2. Successful Outcome When the MAP ... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 21.7.3 Process in the HLR for Status Reporting | The MAP process in the HLR to handle a status report is shown in figure 21.7/4. The MAP process invokes macros not defined in this subclause; the definitions of these macros can be found as follows: Receive_Open_Ind see subclause 25.1.1; Check_Confirmation see subclause 25.2.2; Successful outcome When the MAP process r... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 21.8 Remote User Free | |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 21.8.1 General | The message flows for handling remote user free are shown in figures 21.8/1 and 21.8/2. VLR HLR MAP_REMOTE_USER_FREE <--------------------------------------------------------------- MAP_REMOTE_USER_FREE ack ---------------------------------------------------------------> Figure 21.8/1: Remote User Free: recall not acce... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 21.8.2 Process in the HLR for Remote User Free | The MAP process in the HLR to handle Remote User Free is shown in figure 21.8/3. The MAP process invokes macros not defined in this subclause; the definitions of these macros can be found as follows: Receive_Open_Cnf see subclause 25.1.2; Check_Confirmation see subclause 25.2.2; ETSI ETSI TS 100 974 V7.3.0 (2000-02) 59... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.