Change Requests to GSM Corrections and alignments

Transcription

1 ETSI TC SMG # 22 Plenary Meeting Kristiansand, Norway 9th - 13th June 1997 Tdoc SMG 376/ 97 Source: SMG3 Agenda Item: 6.3 Change Requests to GSM Corrections and alignments Introduction: The following change requests cater for corrections to the 96 release of MAP. CR A086 is a correction of an editing mistake by PT SMG and appears here for the reason of transparency. SPEC VERS CR R E V PHAS E CA T SUBJECT STC_DOC strat egic A F Handling of Unknown Operation 97C245 No A D Editorial clarification of handling of parameters for 97C101 No optional features A F Any Time Interrogation process description in HLR 97C222 No A F Alignment with CAMEL specs and C223 No A F Transmission of gsmscf-address to HLR 97C188 No A F New Maximum value for Age of Loc. Info 97C179 No A D Editorial correction of AC table 97C177 No A F Using TC-Relsult-NL to segment the SRI-ACK 97C247 No A F Deletion of errors in PSI 97C249 No A D SCCP addressing for MAP 97C159 No A D Correction of editing mistake by PT SMG No The following CR is presented for information only and put on hold for the 97 release A089 [97] D Correction of references 97P302 No Other Comments: Number of Pages:

2 Blank Page

3 ETSI SMG3 WPC 97C April - 2 May 1997 Bath, U.K. CHANGE REQUEST No. A072r2 Tdoc Technical Specification GSM version Submitted to SMG for approval without presentation ("non-strategic") [ ] with presentation ("strategic") [ ] Status at SMG [ ]: Approved [ ] Rejected [ ] Postponed [ ] Phase 1: [ ] Phase 2: [ ] Phase 2+: [X] Work item: TEI Other phase(s) affected: [ ] If yes, linked CR(s): Proposed change affects: SIM [ ] ME [ ] Network [X] Source: SMG3 WPC Date: 30/04/97 Subject: Handling of Unknown operations Category: F - Correction [ x ] Reason for change: A - Corresponds to a Phase 2 correction [ ] B - Addition of Feature [ ] C - Functional modification of Feature [ ] D - Editorial modification [ ] This is a correction of the changes introduced by CR A064r1. To increase the flexibility of the MAP Protocol in order to allow for the introduction of new operations, standard or private, in the future in a backwards compatible way. Sections affected, and additional explanation of details of change (if needed): Section , , , Figure 13.2/4 Attached revised pages: Page(s): If other core Specifications are affected, necessary (and attached) Joint CRs: Affects (possibly): MS Test Specifications [ ] BSS Test Specifications [ ] O&M Specifications [ ] Attached CRs?: Cross Phase Compatibility: Change affects operation of: Phase 1 MS in Phase 2(+) NW [ ] Phase 2(+) MS in Phase 1 NW [ ]

4 CR to attached: Change affects operation of: Phase 1 SIM in Phase 2(+) ME[ ] CR to attached: Phase 2(+) SIM in Phase 1 ME [ ] CR to attached: Other comments:

5 Handling of unknown operations Unknown operations (i.e. a standard operation introduced in a later version of or a private operation) can be introduced in MAP in a backwards compatible way. This means, that the receiver of an unknown operation shall, if the dialogue state allows it, send a TC-REJECT component to the sender of the operation indicating unrecognised operation and continue with the processing of further components or messages exchanged within the dialogue as if the unknown operation had not been received. The standardisedcurrent structure of a MAP dialogues shall not be affected by the invocation of unknown operations, i.e. if a dialogue uses only a TC-BEGIN message which is acknowledged by and TC-END message, then a TC-CONTINUE message shall cannot be used to invoke or reject an unknown operation. However the standardised structure of a MAP dialogue may be affected by the rejection of unknown operations, i.e. if a dialogue uses only a TC-BEGIN message which is acknowledged by a TC-END message, a TC-CONTINUE message followed by a TC-END message may be used to carry the rejection of an unknown operation and the response to the standardised operation. The entity which initiated a dialogue whose standardised structure is a TC-BEGIN message which is acknowledged by a TC-END message shall not send any messages in that dialogue after the TC-BEGIN. Note that if the dialogue structure is affected as described in this paragraph the TC- CONTINUE shall include the dialogue portion required to confirm the acceptance of the dialogue. Unknown operations can be invoked in the following types of messages (there is no restriction as to how many unknown operations can be invoked in a message): - TC-BEGIN the component to invoke the unknown operation shall follow the component of the standard operation that is included in this message. - TC-CONTINUE: the component to invoke the unknown operation may be transported as the only component in a stand-alone message or can be grouped with existing operations. In the latter case a specific sequencing of components is not required. - TC-END: if the component to invoke the unknown operation is grouped with an existing operation a specific sequencing of components is not required The TC-REJECT component may be sent in the following messages: - TC-CONTINUE or TC-END: either as the only component of the message or grouped with an existing component. The choice is up to the MAP-Service User.

6 If the received message contains only unknown operations the MAP-Service User shall send the TC-REJECT components in a TC-CONTINUE message to the peer entity, if the dialogue state allows it. If the received message contains unknown operations and standard operations and the standardised structure of the dialogue requires the response to the standard operation to be sent within a TC-END message, then the MAP-Service User may send the response to the standard operations and the TC-REJECT components for the unknown operations in a TC-CONTINUE message followed by a TC-END message. A specific distribution of the components to the TC messages or a specific sequencing of components is not required. The sending of the TC-REJECT shall be done in a type of message that is currently used by the given dialogue,i.e. if the dialogue does not use TC-CONTINUE messages the TC-REJECT component shall be sent in a TC-END. Note that SDLs of chapters do not show the report to the MAP-Service User about the reception of the unknown operation. This has been done for the sake of simplicity of description; the MAP PM may inform the MAP-Service User. The sender of the unknown operation shall ensure that there is enough room in the used message for the unknown operation. In addition, it shall also make sure that it is possible for the dialogue responder to add a TC-REJECT component in the response message even in the worst case scenario for the response to the standard operation.

7 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 diagnostic parameter set to "abnormal event received from the peer"; - if the operation code does not correspond to an operation supported by the applicationcontext, request the transfer of a reject component using the TC-U-REJECT request primitive, with the appropriate problem code (unrecognized operation), and -if the dialogue version is lower than 3- issue a MAP-NOTICE indication primitive with a diagnostic parameter set to abnormal event received from the peer ; - if a linked ID is included, perform the following checks: If the operation referred to by the linked ID does not allow linked operations or if the operation code does not correspond to a permitted linked operation, issue a TC-U-REJECT request primitive with the appropriate problem code (linked response unexpected or unexpected linked operation) and issue a MAP-NOTICE indication primitive with an appropriate diagnostic "abnormal event received from the peer"; - if the type of the argument is not the one defined for the 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 MAP-NOTICE indication primitive with a diagnostic parameter set to "abnormal event from the peer"; Receipt of a TC-INVOKE indication A TC-INVOKE indication primitive is considered as carrying a possible response to a specific service if the linked ID refers to an active specific service and the associated operation is a class 4 operation. Note that the presence of a linked ID parameter in a TC-INVOKE primitive requesting a non class 4 operation indicates a child service whose procedures are the same as the procedures for the parent service. On receipt of a TC-INVOKE indication confirming an active service, the MAP PM shall: - if the operation code is not defined for MAP and the dialogue version is at least 3, issue a TC-U-REJECT request primitive with the appropriate problem code (unrecognized operation). - if the operation code is not defined for MAP and the dialogue version is lower than 3, or if the operation referred to by the linked ID does not allow linked operations or if the operation code does not correspond to an allowed linked operation, issue a TC-U- REJECT request primitive with the appropriate problem code (unrecognized operation, linked response unexpected or unexpected linked operation). If the service is confirmed, the MAP shall also issue a Confirm primitive with provider error indication "unexpected response from the peer", otherwise it may issue a MAP-NOTICE indication primitive with an appropriate diagnostic "abnormal event received from the peer". - otherwise issue a confirm primitive mapping the operation argument parameter to the user specific parameters and setting the result parameter according to the operation code of the linked operation.

8 Procedure PROCESS_COMPONENTS 132_42(4) WAIT_FOR_ COMPONENTS TC_INVOKE_ IND (OP_CODE) INVOKEID_ ASS FALSE 4 TRUE LINKEDID_ PRES FALSE 2 TRUE LINKEDID_ ASS FALSE FALSE and SSM active OP_EXIST for this AC MAP_NOTICE_ IND_VIA_USER2 TRUE TRUE 2 TC_U_REJECT_ REQ_VIA_TC1 Operation Class 4 'Set_problem_ code = unrecognized operation' 1,2,3 LINKED_SERVICE_ INVOKED_VIA_ INTERN2 LINKED_REQUEST_ RECEIVED_VIA INTERN2 PERFORMING_ MAP_SSM TC_U_ REJECT_REQ_ VIA_TC1 SERVICE_ 4 INVOCATION_ RECEIVED_VIA_ INTERN1 FALSE v3-dialogue or higher TRUE LAST_ 3 MAP_NOTICE IND_VIA_USER2 COMPONENT FALSE TRUE 1 3

9 ETSI STC SMG3 WP C Sophia Antipolis, FRANCE 3-7 March 1997 Tdoc SMG3 97C101 Supercedes Tdoc SMG3 97C095 CHANGE REQUEST No. A073r1 Technical Specification GSM 09.02, version Submitted to SMG for approval without presentation ("non-strategic") [x] with presentation ("strategic") [ ] Status at SMG [ ]: Approved [ ] Rejected [ ] Postponed [ ] Phase 1: [ ] Phase 2: [ ] Phase 2+: [x] Work item: TEI Other phase(s) affected [ ] If yes, linked CR(s): Proposed change affects: SIM [ ] ME [ ] Network [x] Source: Vodafone Date: 8-Feb-01 Subject: Editorial clarification of handling of parameters for optional features Category: F - Correction [ ] A - Corresponds to a phase 2 correction [ ] B - Addition of Feature [ ] C - Functional modification of Feature [ ] D - Editorial modification [x] Reason for change: To clarify the use of parameters which are required exclusively for the CAMEL and SOR features Sections affected, and additional explanation of details of change (if needed): 8 Attached revised pages: If other core Specifications are affected, necessary (and attached) Joint CRs: Affects (possibly): Attached CRs?: MS Test Specifications [ ] BSS Test Specifications [ ] O&M Specifications [ ] Cross Phase Compatibility: Change affects operation of: Phase 1 MS in Phase 2(+) NW [ ] Phase 2(+) MS in Phase 1 NW [ ] CR to attached: Change affects operation of: Phase 1 SIM in Phase 2(+) ME[ ] CR to attached: Phase 2(+) SIM in Phase 1 ME [ ] CR to attached: Other comments: The pagination of section 8 has been cleaned up so that each second level subclause begis on a new page.

10 Page 115 Draft prets (GSM Version 5.5.0): March Call handling services 8.1 MAP_SEND_ROUTING_INFORMATION service Definition This service is used between the Gateway MSC and the HLR. The service is invoked by the Gateway MSC to perform the interrogation of the HLR in order to route a call towards the called MS. This is a confirmed service using the primitives listed in table 8.1/ Service primitives Parameter name Request Indication Response Confirm Invoke Id M M(=) M(=) M(=) Interrogation Type M M(=) GMSC Address M M(=) MSISDN M M(=) OR Interrogation C C(=) OR Capability C C(=) CUG Interlock C C(=) C C(=) CUG Outgoing Access C C(=) C C(=) Number of Forwarding C C(=) Network Signal Info C C(=) Supported CAMEL Phases C C(=) Suppress T-CSI C C(=) Suppression of Announcement C C(=) Call Reference Number C C(=) Forwarding Reason C C(=) Basic Service Group C C(=) IMSI C C(=) MSRN C C(=) Forwarding Data C C(=) Forwarding Interrogation Required C C(=) VMSC address C C(=) GMSC Camel Subscription Info C C(=) Location Information C C(=) Subscriber State C C(=) Basic Service Code C C(=) CUG Subscription Flag C C(=) User error C C(=) SS-List U C(=) Provider error O Table 8.1/1: MAP_SEND_ROUTING_INFORMATION parameters Parameter use See subclause 5.6 for a definition of the parameters used in addition to the following. Note that: - a conditional parameter whose use is defined only in GSM shall be absent if the sending entity does not support CAMEL; - a conditional parameter whose use is defined only in GSM shall be absent if the sending entity does not support optimal routeing; - a conditional parameter whose use is defined only in GSM & GSM shall be absent if the sending entity supports neither CAMEL nor optimal routeing. Interrogation Type See GSM [99] for the use of this parameter. GMSC address

11 Page 116 Draft prets (GSM Version 5.5.0): March 1997 The E.164 address of the GMSC. MSISDN This is the Mobile Subscriber ISDN number assigned to the called subscriber. OR Interrogation See GSM [99] for the use of this parameter and the conditions for its presence. OR Capability See GSM [99] for the use of this parameter and the conditions for its presence. CUG Interlock See GSM [97] for the use of this parameter and the conditions for its presence. CUG Outgoing Access See GSM [97] for the use of this parameter and the conditions for its presence. Number of Forwarding See GSM [97] for the use of this parameter and the conditions for its presence. Network Signal Info See GSM [97] for the conditions for the presence of the components of this parameter. Supported CAMEL Phases The use of this parameter and the requirements for its presence are specified in GSM T-CSI Suppression The use of this parameter and the requirements for its presence are specified in GSM Suppression Of Announcement The use of this parameter and the requirements for its presence are specified in GSM Call Reference Number The use of this parameter and the conditions for its presence are specified in GSM [98] and GSM [99], respectively. Forwarding Reason See GSM [99] for the use of this parameter and the conditions for its presence. Basic Service Group See GSM [99] for the use of this parameter and the conditions for its presence. IMSI See GSM [97] for the use of this parameter and the conditions for its presence. MSRN See GSM [97] and GSM [99] for the use of this parameter and the conditions for its presence.

12 Page 117 Draft prets (GSM Version 5.5.0): March 1997 Forwarding Data This parameter includes the forwarded-to number, the forwarding option Notification to calling party and the forwarding reason, and can include the forwarded-to subaddress. See GSM [97] and GSM [99] for the conditions for the presence of its components. Forwarding Interrogation Required See GSM [99] for the use of this parameter and the conditions for its presence. VMSC address See GSM [99] for the use of this parameter and the conditions for its presence. GMSC CAMEL Subscription Info The use of this parameter and the requirements for its presence are specified in GSM Location Information The use of this parameter and the requirements for its presence are specified in GSM Subscriber State The use of this parameter and the requirements for its presence are specified in GSM CUG Subscription Flag The use of this parameter and the requirements for its presence are specified in GSM SS-List This parameter includes SS-codes and will be returned as an operator option. The HLR shall not send PLMN-specific SS-codes across PLMN boundaries. However if the GMSC receives PLMN-specific SScodes from a foreign PLMN s HLR it shall not reject them, although this may lead to unpredictable behaviour. Basic Service Code The use of this parameter and the requirements for its presence are specified in GSM If the CAMEL service is not involved, this parameter includes the basic service code and will be returned as an operator option. The HLR shall not send a PLMN-specific Basic Service Code across PLMN boundaries. However if the GMSC receives a PLMN-specific Basic Service Code from a foreign PLMN s HLR it shall not reject it, although this may lead to unpredictable behaviour. User error This parameter is sent by the responder when an error is detected and if present, takes one of the following values: - Unknown Subscriber; - Number changed; - Call Barred; This error will indicate that either incoming calls are barred for this MS or that calls are barred due to Operator Determined Barring (see GSM for a definition of this network feature). - CUG Reject; The value of this error cause will indicate the reason for CUG Reject.

13 Page 118 Draft prets (GSM Version 5.5.0): March Bearer Service Not Provisioned; - Teleservice Not Provisioned; A subscription check has been performed and the call has not passed the check due to incompatibility with regard to the requested service. Depending on the nature of the incompatibility, either of these messages will be returned. - Facility Not Supported; - Absent Subscriber; This indicates that the location of the MS is not known (either the station is not registered and there is no location information available or the Provide Roaming Number procedure fails due to IMSI detached flag being set), or the GMSC requested forwarding information with a forwarding reason of not reachable, and the call forwarding on MS not reachable service is not active. - Busy Subscriber; This indicates that Call Forwarding on Busy was not active for the specified basic service group when the GMSC requested forwarding information with a forwarding reason of busy. - No Subscriber Reply; This indicates that Call Forwarding on No Reply was not active for the specified basic service group when the GMSC requested forwarding information with a forwarding reason of no reply. - OR Not Allowed; This indicates that the HLR is not prepared to accept an OR interrogation from the GMSC, or that calls to the specified subscriber are not allowed to be optimally routed. - Forwarding Violation; - System Failure; - Data Missing; - Unexpected Data Value. See subclause 5.6 for a definition of these errors. Provider error These are defined in subclause 5.6.

14 8.2 MAP_PROVIDE_ROAMING_NUMBER service Definition Page 119 Draft prets (GSM Version 5.5.0): March 1997 This service is used between the HLR and VLR. The service is invoked by the HLR to request a VLR to send back a roaming number to enable the HLR to instruct the GMSC to route an incoming call to the called MS. This is a confirmed service which uses the Primitives described in table 8.2/ Service primitives Parameter name Request Indication Response Confirm Invoke Id M M(=) M(=) M(=) IMSI M M(=) MSC Number M M(=) MSISDN U C(=) LMSI C C(=) GSM Bearer Capability C C(=) Network Signal Info C C(=) Suppression Of Announcement C C(=) Call Reference Number C C(=) GMSC Address C C(=) OR Interrogation C C(=) Roaming Number C C(=) User error C C(=) Provider error O Table 8.2/1: MAP_PROVIDE_ROAMING_NUMBER parameters Parameter use See subclause 5.6 for a definition of the parameters used, in addition to the following. Note that: - a conditional parameter whose use is defined only in GSM shall be absent if the sending entity does not support CAMEL; - a conditional parameter whose use is defined only in GSM shall be absent if the sending entity does not support optimal routeing; - a conditional parameter whose use is defined only in GSM & GSM shall be absent if the sending entity supports neither CAMEL nor optimal routeing. IMSI This is the IMSI of the called Subscriber. MSC Number This is the ISDN number assigned to the MSC currently serving the MS. The MSC number will have been stored in the HLR as provided at location updating. MSISDN See GSM [97] for the use of this parameter and the conditions for its presence. LMSI See GSM [97] for the use of this parameter and the conditions for its presence. GSM Bearer Capability See GSM [97] for the use of this parameter and the conditions for its presence. This information is passed according to the rules specified in TS GSM

15 Page 120 Draft prets (GSM Version 5.5.0): March 1997 There may be two GSM Bearer Capabilities supplied. Network Signal Info See GSM [97] for the conditions for the presence of the components of this parameter. Suppression Of Announcement The use of this parameter and the requirements for its presence are specified in GSM Call Reference Number The use of this parameter and the conditions for its presence are specified in GSM [98] and GSM [99], respectively. GMSC Address See GSM [99] for the use of this parameter and the conditions for its presence. OR Interrogation See GSM [99] for the use of this parameter and the conditions for its presence. Roaming Number See GSM [97] for the use of this parameter and the conditions for its presence. User error This parameter is sent by the responder when an error is detected and if present, takes one of the following values: - Absent Subscriber; This error will be returned if the IMSI detach flag is set. - No Roaming Number Available; - OR Not Allowed; This indicates that the MAP_PROVIDE_ROAMING_NUMBER indication included the OR interrogation indicator, but the VLR does not support optimal routeing. - Facility Not Supported; - System Failure; - Data Missing; - Unexpected Data Value. See subclause 5.6 for a definition of these reasons. Provider error These are defined in subclause 5.6.

16 8.3 MAP_RESUME_CALL_HANDLING service Definition Page 121 Draft prets (GSM Version 5.5.0): March 1997 This service is used between the terminating VMSC and the GMSC. The service is invoked by the terminating VMSC to request the GMSC to resume handling the call and forward it to the specified destination. This is a confirmed service which uses the Primitives listed in table 8.3/ Service primitives Parameter name Request Indication Response Confirm Invoke Id M M(=) M(=) M(=) Call Reference Number M M(=) Basic Service Group M M(=) IMSI M M(=) Forwarding Data M M(=) CUG Interlock C C(=) CUG Outgoing Access C C(=) O-CSI C C(=) User error C C(=) Provider error O Parameter use Table 8.3/1: MAP_RESUME_CALL_HANDLING parameters See subclause 5.6 for a definition of the parameters used, in addition to the following. Call Reference Number See GSM [99] for the use of this parameter. Basic Service Group See GSM [99] for the use of this parameter. IMSI This is the IMSI of the forwarding Subscriber. Forwarding Data Includes the forwarded-to number, the forwarding reason, an indication of whether the calling party is to be notified that the call has been forwarded and possibly a forwarded-to subaddress. CUG Interlock See GSM [99] for the use of this parameter and the conditions for its presence. CUG Outgoing Access See GSM [99] for the use of this parameter and the conditions for its presence. O-CSI See GSM [99] for the use of this parameter and the conditions for its presence. User error

17 Page 122 Draft prets (GSM Version 5.5.0): March 1997 This parameter is sent by the responder when an error is detected and if present, takes one of the following values: - Optimal Routeing not allowed; - Forwarding failed. Provider error These are defined in subclause 5.6.

18 ETSI STC SMG3 WPC Tdoc SMG3 97C222 Bath UK (revision of Tdoc 97C191) 28 April - 2 May 1997 CHANGE REQUEST No. A074 Technical Specification GSM version5.5.0 Submitted to SMG for approval without presentation ("non-strategic") [ ] with presentation ("strategic") [x] Status at SMG [ ]: Approved [ ] Rejected [ ] Postponed [ ] Phase 1: [ ] Phase 2: [ ] Phase 2+: [x] Work item: TEI Other phase(s) affected: [ ] If yes, linked CR(s): Proposed change affects: SIM [ ] ME [ ] Network [x] Source: SMG3-WPC Date: 28 April 1997 Subject: Any Time Interrogation process description in HLR Category: F - Correction [x] A - Corresponds to a Phase 2 correction [ ] B - Addition of Feature [ ] C - Functional modification of Feature [ ] D - Editorial modification [ ] Reason for change: Any Time Interrogation process is not described in version of MAP. Sections affected, and additional explanation of details of change (if needed): New section , and new Figures 18.2/71 and 18.2/8 to be added. If other core Specifications are affected, necessary (and attached) Joint CRs: Affects (possibly): MS Test Specifications [ ] BSS Test Specifications [ ] O&M Specifications [ ] Attached CRs?: Cross Phase Compatibility: Change affects operation of: Phase 1 MS in Phase 2(+) NW [ ] Phase 2(+) MS in Phase 1 NW [ ] CR to attached: Change affects operation of: Phase 1 SIM in Phase 2(+) ME[ ] CR to attached: Other comments: Phase 2(+) SIM in Phase 1 ME [ ] CR to attached:

19 Page 2 CR to GSM??.?? Version 5.x.x: MMMM yyyy Process in the HLR for Any Time Interrogation (New Section) The message flows for successful retrieval of subscriber information related to an any time interrogation from the CAMEL server are shown in figure 18.2/7. gsmscf HFFFI HFFFI HFFFI MSCFLFFFFFFFFFFFFFFMHLRLFFFFFFFFFFFFFFFFMVLRG JFNFK JFNFK JFNFK GMAP_ANY TIME G G i GINTERROGATION G G i LFFFFFFFFFFFFFFFFF>G G i M GMAP_PROVIDE_SUBSCRI-G i G G BER INFORMATION G i G LFFFFFFFFFFFFFFFFFFF>G i G GMAP_PROVIDE_SUBSCRI-G i G G BER INFORMATION ackg i G MAP_ANY TIME _G<FFFFFFFFFFFFFFFFFFFM i GINTERROGATION ack G G i G<FFFFFFFFFFFFFFFFFM G i G G G i Figure 18.2/7: Message flow for any time interrogation The following MAP services are used to retrieve routing information: MAP_ANY_TIME_INTERROGATION see subclause ; MAP_PROVIDE_SUBSCRIBER_INFO see subclause ; Process in the gsmscf Out of the scope of the MAP specification 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 18.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 ; Receive_Open_Cnf see subclause ; Check_Confirmation see subclause Successful outcome When the MAP process receives a MAP_OPEN indication with the application context anytimeinterrogationenquiry, 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_ANY_TIME_INTERROGATION service indication is received, the MAP process sends an Any Time Interrogation request to the call handling process in the HLR (described in GSM 03.78), and waits for a response. The Any Time Interrogation request contains the parameters received in the MAP_ ANY_TIME_INTERROGATION service indication. If the call handling process in the HLR returns an Any Time Interrogation response, the MAP process constructs a MAP_ANY_TIME_INTERROGATION service response containing the subscriber information contained in the Any Time Interrogation response, constructs a MAP_CLOSE service request, sends them to the CAMEL server and returns to the idle state. If the call handling process in the HLR returns a Provide Subscriber Info request, the MAP process requests a dialogue with the VLR whose identity is contained in the Provide Subscriber Info request by

20 Page 3 CR to GSM??.?? Version 5.x.x: MMMM yyyy sending a MAP_OPEN service request, requests the subscriber status using a MAP_PROVIDE_SUBSCRIBER_INFO service request, and invokes the macro Receive_Open_Cnf to wait for the response to the dialogue opening request. If the macro takes the OK exit, the MAP process waits for the response from the VLR. If the MAP process receives a MAP_PROVIDE_SUBSCRIBER_INFO service confirm, it invokes the macro Check_Confirmation to check the content of the confirm. If the Check_Confirmation macro takes the OK exit, the MAP process sends a Provide Subscriber Info ack containing the information received in the MAP_PROVIDE_SUBSCRIBER_INFO service confirm to the call handling process in the HLR, and waits for a response. The handling of the response from the call handling process in the HLR is described above. If the MAP_PROVIDE_SUBSCRIBER_INFO service confirm contains a provider error or a data error, the MAP process sends a Provide Subscriber Info negative response indicating the type of error to the call handling process in the HLR, and waits for a response. The handling of the response from the call handling process in the HLR is described above. NOTE: The User Error exit from the macro Check_Confirmation is shown for formal completeness; the MAP_PROVIDE_SUBSCRIBER_INFO_cnf primitive cannot contain a user error. Negative response from HLR call handling process If the call handling process in the HLR returns a negative response, either before or after a dialogue with the VLR to obtain subscriber information, the MAP process constructs a MAP_ANY_TIME_INTERROGATION service response containing the appropriate error, constructs a MAP_CLOSE service request, sends them to the CAMEL server and returns to the idle state. Failure of Provide Subscriber Info dialogue with the VLR If the Receive_Open_Cnf macro takes the Vr exit or the Error exit after the MAP process has requested opening of a Provide Subscriber Info dialogue with the VLR, the MAP process sends a Provide Subscriber Info negative response indicating system failure to the call handling process in the HLR, and waits for a response. The handling of the response from the call handling process in the HLR is described above. Failure of dialogue opening with the CAMEL server If the macro Receive_Open_Ind takes the Vr or Error exit, the MAP process returns to the idle state. If the MAP provider sends a MAP_P_ABORT while the MAP process is waiting for a service indication, the MAP process returns to the idle state. If the MAP provider sends a MAP_NOTICE while the MAP process is waiting for a service indication, the MAP process sends a MAP_CLOSE request to terminate the dialogue and returns to the idle state.

21 Page 4 CR to GSM??.?? Version 5.x.x: MMMM yyyy Figure 18.2/8 (sheet 1 of 2): Process ATI_HLR (New) Process ATI_HLR Figure 18.2/8: Process in the HLR to respond to a request for any time interrogation Signals to/from the are to/from the signals to/from the are to/from the unless specified 182_81(2) Idle Receive_ Open_Ind Section 21.1 OK Vr, Error Wait_For_ Service_ Indication Idle MAP_P_ ABORT_ind MAP_ANY_TIME_INTERROGATION_ind MAP_ NOTICE_ind Idle Any_Time Interrogation Request To HLR call handling (see GSM 03.78) MAP_ CLOSE_req Wait_For_ Call_Handling_ Response Idle Any_Time Interrogation Response From HLR call handling process Any_Time Interrogation negative response From HLR call handling process Set result Set error MAP_ANY_TIME_INTERROGATION_rsp Idle

22 Page 5 CR to GSM??.?? Version 5.x.x: MMMM yyyy Figure 18.2/8 (sheet 2 of 2): Process ATI_HLR (New) Process ATI_HLR 182_82(2) Figure 18.2/8: Process in the HLR to respond to a request for any time interrogation Wait_For_ Call_Handling_ Response Signals to/from the are to/from the signals to/from the are to/from the unless specified Provide Subscriber Info From HLR call handling process MAP_OPEN_req, MAP_PROVIDE_SUBSCRIBER_INFO_re MAP_DELIMITER_req Receive_ Open_Cnf Section 21.1 OK Vr, Error Provide Subscriber Info negative To HLR call handling process Wait_For_ PSI_Response Wait_For_ Call_Handling_ Response MAP_PROVIDE_SUBSCRIBER_INFO_c MAP_U_ABORT_ind MAP_P_ABORT_ind MAP_CLOSE_ind MAP_ NOTICE_ ind Check_ Confirmation Section 21.2 MAP_ CLOSE_ ind OK User Error, Provider Error, Data Error Provide Subscriber Info ack To HLR call handling process Provide Subscriber Info negative response To HLR call handling process Provide Subscriber Info negative response To HLR call handling process Wait_For_ Call_Handling_ Response

23 ETSI STC SMG3 WPC Bath UK 28 April - 2 May 1997 CHANGE REQUEST No. A075r1 Tdoc SMG3 97C223r1223 Technical Specification GSM version5.5.0 Submitted to SMG for approval without presentation ("non-strategic") [ ] with presentation ("strategic") [x] Status at SMG [ ]: Approved [ ] Rejected [ ] Postponed [ ] Phase 1: [ ] Phase 2: [ ] Phase 2+: [x] Work item: TEI Other phase(s) affected: [ ] If yes, linked CR(s): Proposed change affects: SIM [ ] ME [ ] Network [x] Source: SMG3 WPCAlcatel Date: 29 April 13 May1997 Subject: Alignment with CAMEL specifications and Category: F - Correction [x] A - Corresponds to a Phase 2 correction [ ] B - Addition of Feature [ ] C - Functional modification of Feature [ ] D - Editorial modification [ ] Reason for change: a) MAP error corresponding to the «Any Time Interrogation not accepted» error case specified in to be defined. b) Alignment of the MaxLocationNumberLength value with the MaxLocationNumberLength value defined in Sections affected, and additional explanation of details of change (if needed): Sections 14.5, , and for a), and for b). If other core Specifications are affected, necessary (and attached) Joint CRs: Affects (possibly): MS Test Specifications [ ] BSS Test Specifications [ ] O&M Specifications [ ] Attached CRs?: Cross Phase Compatibility: Change affects operation of: Phase 1 MS in Phase 2(+) NW [ ] Phase 2(+) MS in Phase 1 NW [ ] CR to attached: Change affects operation of: Phase 1 SIM in Phase 2(+) ME[ ] CR to attached: Other comments: Phase 2(+) SIM in Phase 1 ME [ ] CR to attached:

24 MAP-ANY-TIME-INTERROGATION service Definition This service is used by the gsmscf, to request information (e.g. subscriber state and location) from the HLR at any time Service primitives Parameter name Request Indication Response Confirm Invoke id M M(=) M(=) M(=) Requested Info M M(=) IMSI C C(=) MSISDN C C(=) Location C C(=) Information Subscriber State C C(=) User error C C(=) Provider error O Table 6.11/1: Any_Time_Interrogation Parameter definition and use All parameters are described in subclause 5.6. The use of these parameters and the requirements for their presence are specified in GSM User error This parameter is sent by the responder when an error is detected and if present, takes one of the following values: - System Failure; Any Time Interrogation Not Allowed; - Data Missing; - Unexpected Data Value; - Unknown Subscriber. Provider error These are defined in subclause NEXT MODIFIED SECTION 14.5 MAP operation and error codes SystemFailure, DataMissing, UnexpectedDataValue, FacilityNotSupported, UnknownSubscriber, NumberChanged, UnknownMSC, UnidentifiedSubscriber, UnknownEquipment, RoamingNotAllowed, IllegalSubscriber, IllegalEquipment,

25 BearerServiceNotProvisioned, TeleserviceNotProvisioned, NoHandoverNumberAvailable, SubsequentHandoverFailure, TracingBufferFull, OR-NotAllowed, NoRoamingNumberAvailable, AbsentSubscriber, BusySubscriber, NoSubscriberReply, CallBarred, ForwardingViolation, ForwardingFailed, CUG-Reject, ATI-NotAllowed, IllegalSS-Operation, SS-ErrorStatus, SS-NotAvailable, SS-SubscriptionViolation, SS-Incompatibility, UnknownAlphabet, USSD-Busy, PW-RegistrationFailure, NegativePW-Check, NumberOfPW-AttemptsViolation, SubscriberBusyForMT-SMS, SM-DeliveryFailure, MessageWaitingListFull, AbsentSubscriberSM FROM MAP-Errors { ccitt identified-organization (4) etsi (0) mobiledomain (0) gsm-network (1) modules (3) map-errors (10) version3 (3)} ; -- location registration operation codes updatelocation UpdateLocation ::= localvalue 2 cancellocation CancelLocation ::= localvalue 3 purgems PurgeMS ::= localvalue 67 sendidentification SendIdentification ::= localvalue call handling error codes noroamingnumberavailable NoRoamingNumberAvailable ::= localvalue 39 absentsubscriber AbsentSubscriber ::= localvalue 27 busysubscriber BusySubscriber ::= localvalue 45 nosubscriberreply NoSubscriberReply ::= localvalue 46 callbarred CallBarred ::= localvalue 13 forwardingfailed ForwardingFailed ::= localvalue 47 or-notallowed OR-NotAllowed ::= localvalue 48 forwardingviolation ForwardingViolation ::= localvalue 14 cug-reject CUG-Reject ::= localvalue any time interrogation error codes ati-notallowed ATI-NotAllowed :: = localvalue supplementary service error codes NEXT MODIFIED SECTION

26 Mobile Service Operations IMPORTS OPERATION FROM TCAPMessages { ccitt recommendation q 773 modules (2) messages (1) version2 (2)} SystemFailure, DataMissing, UnexpectedDataValue, UnknownSubscriber, UnknownMSC, UnidentifiedSubscriber, UnknownEquipment, RoamingNotAllowed, ATI-NotAllowed, NoHandoverNumberAvailable, SubsequentHandoverFailure FROM MAP-Errors { ccitt identified-organization (4) etsi (0) mobiledomain (0) gsm-network (1) modules (3) map-errors (10) version3 (3)} -- any time information enquiry operations AnyTimeInterrogation ::= OPERATION ARGUMENT anytimeinterrogationarg RESULT anytimeinterrogationres ERRORS { SystemFailure, ATI-NotAllowed, DataMissing, UnexpectedDataValue, UnknownSubscriber} -- handover operations AnyTimeInterrogationArg AnyTimeInterrogationRes --Timer m NEXT MODIFIED SECTION Errors MAP-Errors { ccitt identified-organization (4) etsi (0) mobiledomain (0) gsm-network (1) modules (3) map-errors (10) version3 (3)} DEFINITIONS ::= BEGIN EXPORTS -- generic errors SystemFailure, DataMissing, UnexpectedDataValue, FacilityNotSupported,

27 -- identification and numbering errors UnknownSubscriber, NumberChanged, UnknownMSC, UnidentifiedSubscriber, UnknownEquipment, -- subscription errors RoamingNotAllowed, IllegalSubscriber, IllegalEquipment, BearerServiceNotProvisioned, TeleserviceNotProvisioned, -- handover errors NoHandoverNumberAvailable, SubsequentHandoverFailure, -- operation and maintenance errors TracingBufferFull, -- call handling errors OR-NotAllowed, NoRoamingNumberAvailable, BusySubscriber, NoSubscriberReply, AbsentSubscriber, CallBarred, ForwardingViolation, ForwardingFailed, CUG-Reject, -- any time interrogation errors ATI-NotAllowed, -- supplementary service errors IllegalSS-Operation, SS-ErrorStatus, SS-NotAvailable, SS-SubscriptionViolation, SS-Incompatibility, UnknownAlphabet, USSD-Busy, PW-RegistrationFailure, NegativePW-Check, NumberOfPW-AttemptsViolation, ; -- short message service errors SubscriberBusyForMT-SMS, SM-DeliveryFailure, MessageWaitingListFull, AbsentSubscriberSM IMPORTS ERROR FROM TCAPMessages { ccitt recommendation q 773 modules (2) messages (1) version2 (2)} SS-Status FROM MAP-SS-DataTypes { ccitt identified-organization (4) etsi (0) mobiledomain (0) gsm-network (1) modules (3) map-ss-datatypes (14) version3 (3)} SS-IncompatibilityCause, PW-RegistrationFailureCause, SM-DeliveryFailureCause, SystemFailureParam, DataMissingParam, UnexpectedDataParam, FacilityNotSupParam, UnknownSubscriberParam, NumberChangedParam, UnidentifiedSubParam, RoamingNotAllowedParam, IllegalSubscriberParam, IllegalEquipmentParam, BearerServNotProvParam, TeleservNotProvParam,

28 TracingBufferFullParam, NoRoamingNbParam, OR-NotAllowedParam, AbsentSubscriberParam, BusySubscriberParam, NoSubscriberReplyParam, CallBarredParam, ForwardingViolationParam, ForwardingFailedParam, CUG-RejectParam, ATI-NotAllowedParam, SubBusyForMT-SMS-Param, MessageWaitListFullParam, AbsentSubscriberSM-Param FROM MAP-ER-DataTypes { ccitt identified-organization (4) etsi (0) mobiledomain (0) gsm-network (1) modules (3) map-er-datatypes (17) version3 (3)} ; -- generic errors -- call handling errors NoRoamingNumberAvailable ::= ERROR PARAMETER noroamingnbparam -- optional AbsentSubscriber ::= ERROR PARAMETER absentsubscriberparam -- optional NoRoamingNbParam AbsentSubscriberParam -- absentsubscriberparam must not be used in version <3 BusySubscriber ::= ERROR PARAMETER busysubscriberparam BusySubscriberParam -- optional NoSubscriberReply ::= ERROR PARAMETER nosubscriberreplyparam -- optional CallBarred ::= ERROR PARAMETER callbarredparam -- optional ForwardingViolation ::= ERROR PARAMETER forwardingviolationparam -- optional ForwardingFailed ::= ERROR PARAMETER forwardingfailedparam -- optional CUG-Reject ::= ERROR PARAMETER cug-rejectparam -- optional OR-NotAllowed ::= ERROR PARAMETER or-notallowedparam -- optional NoSubscriberReplyParam CallBarredParam ForwardingViolationParam ForwardingFailedParam CUG-RejectParam OR-NotAllowedParam

29 -- any time interrogation errors ATI-NotAllowed ::= ERROR PARAMETER ati-notallowedparam -- optional ATI-NotAllowedParam -- supplementary service errors NEXT MODIFIED SECTION Mobile Service data types LocationInformation ::= SEQUENCE { ageoflocationinformation AgeOfLocationInformation OPTIONAL, geographicalinformation [0] GeographicalInformation OPTIONAL, vlr-number [1] ISDN-AddressString OPTIONAL, locationnumber [2] LocationNumber OPTIONAL, cellidorlai [3] CellIdOrLAI OPTIONAL, extensioncontainer [4] ExtensionContainer OPTIONAL,...} AgeOfLocationInformation ::= INTEGER ( ) -- the value represents the elapsed time in minutes since the last -- network contact of the mobile station (i.e. the actuality of the -- location information). -- value 0 indicates that the MS is currently in contact with the -- network -- value indicates that the location information is at least minutes old GeographicalInformation ::= OCTET STRING (SIZE (9)) -- Refers to geographical Information defined in GSM Only the description of a circle (point;radius) as specified in GSM is allowed to be used -- The internal structure according to GSM is as follows: -- Element Identifier 1 octet -- Length Indicator/Type of shape (circle) 1 octet -- Point description -- Degrees of Longitude 3 octets -- Degrees of Latitude 3 octets -- Radius 1 octet LocationNumber ::= OCTET STRING (SIZE (2..160)) -- the internal structure is defined in CCITT Rec Q.763 SubscriberState ::= CHOICE { assumedidle camelbusy netdetnotreachable notprovidedfromvlr [0] NULL, [1] NULL, NotReachableReason, [2] NULL} NEXT MODIFIED SECTION

30 Error data types MAP-ER-DataTypes { ccitt identified-organization (4) etsi (0) mobiledomain (0) gsm-network (1) modules (3) map-er-datatypes (17) version3 (3)} DEFINITIONS IMPLICIT TAGS ::= BEGIN EXPORTS RoamingNotAllowedParam, CallBarredParam, CUG-RejectParam, SS-IncompatibilityCause, PW-RegistrationFailureCause, SM-DeliveryFailureCause, SystemFailureParam, DataMissingParam, UnexpectedDataParam, FacilityNotSupParam, OR-NotAllowedParam, UnknownSubscriberParam, NumberChangedParam, UnidentifiedSubParam, IllegalSubscriberParam, IllegalEquipmentParam, BearerServNotProvParam, TeleservNotProvParam, TracingBufferFullParam, NoRoamingNbParam, AbsentSubscriberParam, BusySubscriberParam, NoSubscriberReplyParam, ForwardingViolationParam, ForwardingFailedParam, ATI-NotAllowedParam, SubBusyForMT-SMS-Param, MessageWaitListFullParam, AbsentSubscriberSM-Param, AbsentSubscriberDiagnosticSM ; ForwardingViolationParam ::= SEQUENCE { extensioncontainer ExtensionContainer OPTIONAL,...} ForwardingFailedParam ::= SEQUENCE { extensioncontainer ExtensionContainer OPTIONAL,...} ATI-NotAllowedParam ::= SEQUENCE { extensioncontainer ExtensionContainer OPTIONAL,...} SubBusyForMT-SMS-Param ::= SEQUENCE { extensioncontainer ExtensionContainer OPTIONAL,...} MessageWaitListFullParam ::= SEQUENCE { extensioncontainer ExtensionContainer OPTIONAL,...} END

31 ETSI STC SMG3 WP C Bath, UK 28 April - 2 May 1997 Tdoc SMG3 97C188 CHANGE REQUEST No. A077 Technical Specification GSM version Submitted to SMG for approval without presentation ("non-strategic") [ ] with presentation ("strategic") [ ] Status at SMG [ ]: Approved [ ] Rejected [ ] Postponed [ ] Phase 1: [ ] Phase 2: [ ] Phase 2+: [X] Work item: TEI Other phase(s) affected: [ ] If yes, linked CR(s): Proposed change affects: SIM [ ] ME [ ] Network [X] Source: SMG3 WPC Date: 09/04/97 Subject: Transmission of gsmscf-address to HLR for any time interrogation Category: F - Correction [ x ] A - Corresponds to a Phase 2 correction [ ] B - Addition of Feature [ ] C - Functional modification of Feature [ ] D - Editorial modification [ ] Reason for change: To allow the HLR to decide on MAP-user level whether or not an Any Time Interrogation request from a specific gsmscf shall be accepted or rejected. Sections affected, and additional explanation of details of change (if needed): Section Attached revised pages: Page(s): 1 page If other core Specifications are affected, necessary (and attached) Joint CRs: Affects (possibly): MS Test Specifications [ ] BSS Test Specifications [ ] O&M Specifications [ ] Attached CRs?: Cross Phase Compatibility: Change affects operation of: Phase 1 MS in Phase 2(+) NW [ ] Phase 2(+) MS in Phase 1 NW [ ] CR to attached: Change affects operation of: Phase 1 SIM in Phase 2(+) ME[ ] CR to attached: Other comments: Phase 2(+) SIM in Phase 1 ME [ ] CR to attached:

32 Page 260 Draft prets (GSM Version 5.5.0): May 1997 AnyTimeInterrogationArg ::= SEQUENCE { subscriberidentity [0] SubscriberIdentity, requestedinfo [1] RequestedInfo, gsmscf-address [3] ISDN-AddressString, extensioncontainer [2] ExtensionContainer OPTIONAL,...} AnyTimeInterrogationRes ::= SEQUENCE { subscriberinfo SubscriberInfo, extensioncontainer ExtensionContainer OPTIONAL,...} SubscriberIdentity ::= CHOICE { imsi [0] IMSI, msisdn } [1] ISDN-AddressString END

33 ETSI STC SMG3 WP C Bath, UK 28 April - 2 May 1997 Tdoc SMG3 97C179 CHANGE REQUEST No. A078 Technical Specification GSM 09.02, version Submitted to SMG for approval without presentation ("non-strategic") [x] with presentation ("strategic") [ ] Status at SMG [ ]: Approved [ ] Rejected [ ] Postponed [ ] Phase 1: [ ] Phase 2: [ ] Phase 2+: [x] Work item: TEI Other phase(s) affected [ ] If yes, linked CR(s): Proposed change affects: SIM [ ] ME [ ] Network [x] Source: SMG3 WPC Date: 8-Feb-01 Subject: New Maximum Value for Age of Location Info Category: F - Correction [x] A - Corresponds to a phase 2 correction [ ] B - Addition of Feature [ ] C - Functional modification of Feature [ ] D - Editorial modification [ ] Reason for change: To allow the integer Age of Location Information to be coded in two byte. Sections affected, and additional explanation of details of change (if needed): Attached revised pages: 1 page If other core Specifications are affected, necessary (and attached) Joint CRs: Affects (possibly): MS Test Specifications [ ] BSS Test Specifications [ ] O&M Specifications [ ] Attached CRs?: Cross Phase Compatibility: Change affects operation of: Phase 1 MS in Phase 2(+) NW [ ] Phase 2(+) MS in Phase 1 NW [ ] CR to attached: Change affects operation of: Phase 1 SIM in Phase 2(+) ME[ ] CR to attached: Other comments: Phase 2(+) SIM in Phase 1 ME [ ] CR to attached:

34 -- provide subscriber info types ProvideSubscriberInfoArg ::= SEQUENCE { imsi [0] IMSI, lmsi [1] LMSI OPTIONAL, requestedinfo [2] RequestedInfo, extensioncontainer [3] ExtensionContainer OPTIONAL,...} ProvideSubscriberInfoRes ::= SEQUENCE { subscriberinfo SubscriberInfo, extensioncontainer ExtensionContainer OPTIONAL,...} SubscriberInfo ::= SEQUENCE { locationinformation OPTIONAL, subscriberstate OPTIONAL, extensioncontainer OPTIONAL,...} RequestedInfo ::= SEQUENCE { locationinformation OPTIONAL, subscriberstate OPTIONAL, extensioncontainer OPTIONAL,...} LocationInformation ::= SEQUENCE { ageoflocationinformation OPTIONAL, geographicalinformation OPTIONAL, vlr-number OPTIONAL, locationnumber OPTIONAL, cellidorlai OPTIONAL, extensioncontainer OPTIONAL,...} [0] LocationInformation [1] SubscriberState [2] ExtensionContainer [0] NULL [1] NULL [2] ExtensionContainer AgeOfLocationInformation [0] GeographicalInformation [1] ISDN-AddressString [2] LocationNumber [3] CellIdOrLAI [4] ExtensionContainer AgeOfLocationInformation ::= INTEGER ( ) -- the value represents the elapsed time in minutes since the last -- network contact of the mobile station (i.e. the actuality of the -- location information). -- value 0 indicates that the MS is currently in contact with the -- network -- value indicates that the location information is at least minutes old GeographicalInformation ::= OCTET STRING (SIZE (9)) -- Refers to geographical Information defined in GSM Only the description of a circle (point;radius) as specified in GSM is allowed to be used -- The internal structure according to GSM is as follows: -- Element Identifier 1 octet -- Length Indicator/Type of shape (circle) 1 octet -- Point description -- Degrees of Longitude 3 octets -- Degrees of Latitude 3 octets -- Radius 1 octet