hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
a49e477e846d725703395e7c1abc4db0 | 101 393 | 6.1.6.7 Event time stamps | These fields contain the event time stamps relevant for each of the individual record types. All time-stamps include a minimum of date, hour, minute, and second. |
a49e477e846d725703395e7c1abc4db0 | 101 393 | 6.1.6.8 GGSN address/GGSN address used | These fields contain one IP address of GGSN. The S-CDR fields contain a single address of current GGSN used. The G-CDR fields contain an address of current GGSN. |
a49e477e846d725703395e7c1abc4db0 | 101 393 | 6.1.6.9 List of traffic data volumes | This list includes one or more containers, which each include the following fields: Data volume uplink, data volume downlink, change condition and change time. Data volume includes the number of octets transmitted during the use of packet data services. ETSI TS 101 393 V6.2.0 (1999-05) 28 (GSM 12.15 version 6.2.0 Relea... |
a49e477e846d725703395e7c1abc4db0 | 101 393 | 6.1.6.10 Message reference | This field contains a unique message reference number allocated by the mobile station when transmitting a short message to the service centre. This field corresponds to the TP-Message-Reference element of the SMS_SUBMIT PDU defined in GSM 03.40. ETSI TS 101 393 V6.2.0 (1999-05) 29 (GSM 12.15 version 6.2.0 Release 1997) |
a49e477e846d725703395e7c1abc4db0 | 101 393 | 6.1.6.11 Mobile station classmark | This MS classmark field contains the mobile station classmark 4 employed by the served MS on PDP context activation or on GPRS attachment as defined in GSM 04.08 [16]. |
a49e477e846d725703395e7c1abc4db0 | 101 393 | 6.1.6.12 Network initiated PDP context | This field indicates that PDP context is network initiated. The field is missing in case of mobile activated PDP context. |
a49e477e846d725703395e7c1abc4db0 | 101 393 | 6.1.6.13 Node ID | This field contains an optional operator configurable identifier string for the node which generated the CDR. |
a49e477e846d725703395e7c1abc4db0 | 101 393 | 6.1.6.14 PDP Type | This field defines the PDP type, e.g. X.25 or IP (see GSM 09.60 for exact format). |
a49e477e846d725703395e7c1abc4db0 | 101 393 | 6.1.6.15 QoS Requested/QoS Negotiated | Quality of Service Requested contains the QoS wanted by MS at PDP context activation. QoS Negotiated indicates the applied QoS accepted by the network. The QoS profile consists of 5 attributes: reliability, delay, precedence, peak throughput and mean throughput. See GSM 03.60 [8] for more details. |
a49e477e846d725703395e7c1abc4db0 | 101 393 | 6.1.6.16 Record extensions | The field enables network operators and/or manufacturers to add their own extensions to the standard record definitions. This field contains a set of "management extensions" as defined in CCITT X.721 [5]. |
a49e477e846d725703395e7c1abc4db0 | 101 393 | 6.1.6.17 Record opening time | This field contains the time stamp when the record is opened (see GSM 12.05 for exact format). Record opening reason does not have a separate field. For G-CDR and M-CDR it can be derived from the field "Sequence number" i.e. missing field or value one means activation of PDP context and GPRS attachment. For S-CDR also ... |
a49e477e846d725703395e7c1abc4db0 | 101 393 | 6.1.6.18 Record Sequence number | This field contains a running sequence number employed to link the partial records generated in the SGSN/GGSN for a particular PDP context (characterised with same the Charging ID and GGSN address pair). In the S-CDR the sequence number is always started from one after inter-SGSN routing area update, see field "SGSN ch... |
a49e477e846d725703395e7c1abc4db0 | 101 393 | 6.1.6.19 Record type | The field identifies the type of the record e.g. S-CDR, G-CDR, M-CDR, S-SMO-CDR and S-SMT-CDR. |
a49e477e846d725703395e7c1abc4db0 | 101 393 | 6.1.6.20 Recording entity number | This field contains the ITU-T E.164 number assigned to the entity that produced the record. For further details see GSM 03.03. |
a49e477e846d725703395e7c1abc4db0 | 101 393 | 6.1.6.21 Remote PDP address | Remote PDP address may be used if PDP type is X.25. This parameter is not used if the PDP type is IP. Itemised volume billing is available per Access Point Name. This field contains a list of connected remote PDP addresses. ETSI TS 101 393 V6.2.0 (1999-05) 30 (GSM 12.15 version 6.2.0 Release 1997) |
a49e477e846d725703395e7c1abc4db0 | 101 393 | 6.1.6.22 Routing Area Code/Cell Identity/Change of location | The location information contains a combination of the Routing Area Code (RAC) and optionally Cell Identity (CI) of the routing area and cell in which the served party is currently located. Any change of location (i.e. Routing area change) may be recorded in the change of location field including the time at which the ... |
a49e477e846d725703395e7c1abc4db0 | 101 393 | 6.1.6.23 Served IMEI | This field contains the international mobile equipment identity (IMEI) of the equipment served. The term "served" equipment is used to describe the ME involved in the transaction recorded e.g. the called ME in the case of a network initiated PDP context. The structure of the IMEI is defined in GSM 03.03 [14]. |
a49e477e846d725703395e7c1abc4db0 | 101 393 | 6.1.6.24 Served IMSI | This fields contains the international mobile subscriber identity (IMSI) of the served party. The term "served" party is used to describe the mobile subscriber involved in the transaction recorded e.g. the calling subscriber in case of a mobile initiated PDP context . The structure of the IMSI is defined in GSM 03.03 [... |
a49e477e846d725703395e7c1abc4db0 | 101 393 | 6.1.6.25 Served MSISDN | This fields contains the mobile station ISDN number (MSISDN) of the served party. The term "served" party is used to describe the mobile subscriber involved in the transaction recorded e.g. the called subscriber in case of an MTC record. In case of multi-numbering the MSISDN stored in a MOC record will be the primary M... |
a49e477e846d725703395e7c1abc4db0 | 101 393 | 6.1.6.26 Served PDP address | This field contains the PDP address of the served IMSI. This is a network layer address e.g. of type IP version 4, IP version 6 or X.121. The address for each PDP type is allocated either temporarily or permanently, see field "Dynamic Address Flag". |
a49e477e846d725703395e7c1abc4db0 | 101 393 | 6.1.6.27 Service centre address | This field contains a CCITT E.164 number identifying a particular service centre e.g. short message service centre (see GSM 03.40). |
a49e477e846d725703395e7c1abc4db0 | 101 393 | 6.1.6.28 SGSN address | These fields contain one or several IP addresses of SGSN. The S-CDR fields contain single address of current SGSN and GGSN used. The G-CDR fields contains the address of the current GGSN and a list of SGSNs, which have been connected during the record (SGSN change due to inter SGSN routing area update). The M-CDR only ... |
a49e477e846d725703395e7c1abc4db0 | 101 393 | 6.1.6.29 SGSN change | This field is present only in the S-CDR to indicate that this is the first record after an inter-SGSN routing area update. ETSI TS 101 393 V6.2.0 (1999-05) 31 (GSM 12.15 version 6.2.0 Release 1997) |
a49e477e846d725703395e7c1abc4db0 | 101 393 | 6.1.6.30 Short message service result | This field contains the result of an attempt to deliver a short message either to a service centre or to a mobile subscriber (see GSM 09.02). Note that this field is only provided if the attempted delivery was unsuccessful |
a49e477e846d725703395e7c1abc4db0 | 101 393 | 7 Charging Protocols | For Future Study. |
a49e477e846d725703395e7c1abc4db0 | 101 393 | 8 Charging Data Record Structure | |
a49e477e846d725703395e7c1abc4db0 | 101 393 | 8.1 ASN.1 definitions for CDR information | Within the current GSM 12-series of specifications the ASN.1 definitions are based on X.208 [40] which has been superseded by X.680. This newer version not only includes new features but also removes some that were present in X.208. It was agreed that where possible, the GPRS work would be based on those ASN.1 features... |
aecd38669c16f5c33001893d647b0d16 | 101 788 | 1 Scope | The present document is accompanied by a compressed archive containing a pro-forma for systems reference document which is intended to be used as the basis for co-operation with the European Radiocommunications Committee (ERC) of the European Conference of Post and Telecommunications Administrations (CEPT), under the M... |
aecd38669c16f5c33001893d647b0d16 | 101 788 | 2 References | ..............................................................................................................................................11 |
aecd38669c16f5c33001893d647b0d16 | 101 788 | 3 Definitions, symbols and abbreviations | .................................................................................................11 |
aecd38669c16f5c33001893d647b0d16 | 101 788 | 3.1 Definitions | ........................................................................................................................................................11 |
aecd38669c16f5c33001893d647b0d16 | 101 788 | 3.2 Symbols | ............................................................................................................................................................11 |
aecd38669c16f5c33001893d647b0d16 | 101 788 | 3.3 Abbreviations | ...................................................................................................................................................11 |
aecd38669c16f5c33001893d647b0d16 | 101 788 | 4 Executive summary | ................................................................................................................................12 |
aecd38669c16f5c33001893d647b0d16 | 101 788 | 5 Main conclusions | ....................................................................................................................................12 Annex A (informative): Detailed market information ................................................................................13 A.1 Range of applications............................. |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 1 Scope | It is necessary to transfer between entities of a Public Land Mobile Network (PLMN) information specific to the PLMN in order to deal with the specific behaviour of roaming Mobile Stations (MS)s. The Signalling System No. 7 specified by CCITT is used to transfer this information. The present document describes the requ... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 2 References | The following documents contain provisions which, through reference in this text, constitute provisions of the present document. • References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. • For a specific reference, subsequent revisions do not apply. • Fo... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 3 Abbreviations | Abbreviations used in the present document are listed in GSM 01.04. |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 4 Configuration of the mobile network | |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 4.1 The entities of the mobile system | To provide the mobile service as it is defined, it is necessary to introduce some specific functions. These functional entities can be implemented in different equipments or integrated. In any case, exchanges of data occur between these entities. |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 4.1.1 The Home Location Register (HLR) | This functional entity is a data base in charge of the management of mobile subscribers. A PLMN may contain one or several HLRs; it depends on the number of mobile subscribers, on the capacity of the equipment and on the organization of the network. All subscription data are stored there. The main information stored th... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 4.1.2 The Visitor Location Register (VLR) | An MS roaming in an MSC area is controlled by the Visitor Location Register in charge of this area. When an MS appears in a location area it starts a location updating procedure. The MSC in charge of that area notices this registration and transfers to the Visitor Location Register the identity of the location area whe... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 4.1.3 The Mobile-services Switching Centre (MSC) | The Mobile-services Switching Centre is an exchange which performs all the switching functions for MSs located in a geographical area designated as the MSC area. The main difference between an MSC and an exchange in a fixed network is that the MSC has to take into account the impact of the allocation of radio resources... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 4.1.4 The Base Station System (BSS) | The BSS is the sub-system of Base Station equipment (transceivers, controllers, etc...) which is viewed - by the MSC through an interface (A-interface) with the functionality described in GSM 08.02; - by the SGSN through an interface (Gb-interface) with the functionality described in GSM 03.60. |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 4.1.5 The Gateway MSC (GMSC) | In the case of incoming calls to the PLMN, if the fixed network is unable to interrogate the HLR, the call is routed to an MSC. This MSC will interrogate the appropriate HLR and then route the call to the MSC where the MS is located. The MSC which then performs the routing function to the actual location of the mobile ... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 4.1.6 The SMS Gateway MSC | The SMS GMSC is the interface between the Mobile Network and the network which provides access to the Short Message Service Centre, for short messages to be delivered to MSs. The choice of which MSCs can act as SMS Gateway MSCs is a network operator matter (e.g. all MSCs or some designated MSCs). |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 4.1.7 The SMS Interworking MSC | The SMS IWMSC is the interface between the Mobile Network and the network which provides access to the Short Message Service Centre, for short messages submitted by MSs. The choice of which MSCs can act as SMS Interworking MSCs is a network operator matter (e.g. all MSCs or some designated MSCs). ETSI ETSI TS 100 974 V... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 4.1.8 The VBS/VGCS Anchor MSC | The voice broadcast/group call anchor MSC obtains from the associated GCR all relevant attributes and controls in turn all cells in its area, VBS/VGCS Relay-MSCs and dispatchers belonging to a given group call. |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 4.1.9 The Equipment Identity Register (EIR) | This functional unit is a data base in charge of the management of the equipment identities of the MSs; see also GSM 02.16. |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 4.1.10 The GSM Service Control Function (gsmSCF) | This functional entity contains the CAMEL service logic to implement OSS. It interfaces with the gsmSSF and the HLR; see also TS GSM 03.78. |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 4.1.11 The VBS/VGCS Relay MSC | The voice broadcast/group call relay MSC obtains from the associated anchor MSC all relevant attributes and controls in turn all cells in its area belonging to a given group call. |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 4.1.12 The Group Call Register (GCR) | This functional unit is a data base in charge of the management of attributes related to the establishment of Voice Broadcast Calls and Voice Group Calls. |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 4.1.13 The Shared InterWorking Function Server (SIWFS) | A Shared Inter Working Function is a network function that may be used by any MSC in the same PLMN to provide interworking for a data/fax call. Whereas an IWF can only be used by its MSC, the SIWF can be used by several other network nodes e.g. any MSC within the same PLMN (the concept is not limited to a certain numbe... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 4.1.14 The Serving GPRS Support Node (SGSN) | This functional unit keeps track of the individual MSs' location and performs security functions and access control; see also GSM 03.60. |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 4.1.15 The Gateway GPRS Support Node (GGSN) | This functional unit provides interworking with external packet-switched networks, network screens and routing of the Network Requested PDP-context activation;see also GSM 03.60.4.2 "Configuration of a Public Land Mobile Network (PLMN)". ETSI ETSI TS 100 974 V7.3.0 (2000-02) 35 (GSM 09.02 version 7.3.0 Release 1998) Th... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 4.1.17 The Serving Mobile Location Center (SMLC) | An SMLC is a database and processing entity that manages the procedures for obtaining the geographic location of a target MS in the coverage area served by the SMLC. In managing the location procedures, the SMLC chooses the positioning method and provides data and instructions to the LMUs or target MS that perform the ... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 4.1.18 The Gateway Mobile Location Center (GMLC) | The GMLC provides access to location services (LCS) for LCS clients external to a PLMN. A GMLC may also support access to location services from LCS clients internal to its own PLMN. The GMLC allows an LCS client to issue location requests for certain target MSs; it then conveys these requests to the VMSC currently ser... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 4.1.19 The Location Measurement Unit (LMU) | The LMU is the logical network entity that performs location measurements in the VPLMN in order to either position a target MS or provide assistance data to be used in conjunction with other location measurements. An LMU is controlled by an SMLC in the VPLMN from which location commands can be received and to which any... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 4.3 Interconnection between PLMNs | Since the configuration of a PLMN does not have any impact on other PLMNs, the signalling interfaces specified can be implemented both between the entities within a PLMN and between different PLMNs. |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 4.4 The interfaces within the mobile service | |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 4.4.1 Interface between the HLR and the VLR (D-interface) | This interface is used to exchange the data related to the location of the MS and to the management of the subscriber. The main service provided to the mobile subscriber is the capability to set up or to receive calls within the whole service area. To support that purpose the location registers have to exchange data. T... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 4.4.2 Interface between the HLR and the gsmSCF (J-interface) | This interface is used by the gsmSCF to request information from the HLR (via the Any-time Interrogation function) or to allow call independent related network- or user-initiated interaction between an MS and the gsmSCF (via the USSD function). Support of the gsmSCF-HLR interface is a network operator option. As a netw... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 4.4.3 Interface between the VLR and its associated MSC(s) (B-interface) | The VLR is the location and management data base for the MSs roaming in the area controlled by the associated MSC(s). Whenever the MSC needs data related to a given MS currently located in its area, it interrogates the VLR. When a MS initiates a location updating procedure with an MSC, the MSC informs its VLR which sto... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 4.4.4 Interface between VLRs (G-interface) | When an MS initiates a location updating using TMSI, the VLR can fetch the IMSI and authentication set from the previous VLR. |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 4.4.5 Interface between the HLR and the MSC (C-interface) | When the fixed network is not able to perform the interrogation procedure needed to set up a call to a mobile subscriber, the Gateway MSC has to interrogate the HLR of the called subscriber to obtain the roaming number of the called MS (see GSM 03.04). To forward a short message to a mobile subscriber, the SMS Gateway ... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 4.4.6 Interface between the MSC and the gsmSCF (L-interface) | When one of the following Supplementary Services, CD, ECT or MPTY, is invoked in the MSC a notification shall be sent towards the gsmSCF. ETSI ETSI TS 100 974 V7.3.0 (2000-02) 38 (GSM 09.02 version 7.3.0 Release 1998) |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 4.4.7 Interface between MSCs (E-interface) | When a MS moves from one MSC area to another during a call, a handover procedure has to be performed in order to continue the communication. For that purpose the MSCs involved have to exchange data to initiate and then to realize the operation. This interface is also used to forward short messages, to perform location ... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 4.4.8 Interface between the MSC and Base Station Systems (A-interface) | The description of this interface is contained in the GSM 08-series of MSs. The BSS-MSC interface carries information concerning: - BSS management; - call handling; - location management. |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 4.4.9 Interface between MSC and EIR (F-interface) | This interface is used when an MSC wants to check an IMEI. 4.4. 10 Interface between VBS/VGCS Anchor MSC and GCR (I-interface) This is an internal interface. |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 4.4.11 Interface between the MSC and the SIWF server (K-interface) | When a MSC detects that it can not provide the requested IW function, resources from an SIWF server can be used. This interface is used to allocate resources in that SIWF server and establish required physical connections to that server. |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 4.4.12 Interface between SGSN and HLR (Gr-interface) | The description of this interface is contained in the GSM 03.60. 4.4.13 Interface between SGSN and SMS-GMSC or SMS-IWMSC (Gd- interface) The description of this interface is contained in the GSM 03.60. |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 4.4.14 Interface between GGSN and HLR (Gc-interface) | The description of this interface is contained in the GSM 03.60. |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 4.4.15 Interface between SGSN and EIR (Gf-interface) | The description of this interface is contained in the GSM 03.60. ETSI ETSI TS 100 974 V7.3.0 (2000-02) 39 (GSM 09.02 version 7.3.0 Release 1998) |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 4.4.16 Interface between SGSN and BSC (Gb-interface) | The description of this interface is contained in the GSM 03.60. |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 4.4.17 Interface between SGSN and MSC/VLR (Gs-interface) | The description of this interface is contained in the GSM 09.18. 4.4.17A Interface between SMLC and BSC (Lb interface) This interface is used by a BSC when an SMLC is BSS based to request either the initiation of location procedures or the retrieval of location assistance data for a particular target MS in the coverage... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 4.4.18 Interface between SMLC and MSC (Ls interface) | This interface is used by the MSC when an SMLC is NSS based to request either the initiation of location procedures or the retrieval of location assistance data for a particular target MS in the coverage area served by the SMLC. The interface is also used to transfer LCS measurement and O&M information between an SMLC ... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 4.4.19 Void | |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 4.4.20 Interface between GMLC and HLR (Lh interface) | This interface is used by the GMLC to request the address of the visited MSC for a particular target MS whose location has been requested. |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 4.4.21 Interface between GMLC and MSC (Lg interface) | This interface is used by the GMLC to convey a location request to the MSC currently serving a particular target MS whose location was requested. The interface is used by the MSC to return location results to the GMLC. |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 4.4.22 Interface between LCS Client and GMLC (Le interface) | This interface is used by a client of the Location Services (LCS) to request location information from a GMLC for certain target MSs. The interface is used by the GMLC to provide location information to an LCS client. This interface is external to a PLMN and is not defined within GSM. |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 4.5 Splitting of the data storage | The data attached to each MS management, operation and location are stored in the Location Registers. Some data are duplicated in the HLR and in the VLR, but others may be stored only in one place. The data associated with any client that uses a particular GMLC to access location services is stored in the GMLC. A detai... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 5 Overload and compatibility overview | |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 5.1 Overload control | There is a requirement for an overload/congestion control for all entities of the Public Land Mobile Network and the underlying Signalling System No. 7. |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 5.1.1 Overload control for MSC (outside MAP) | For the entity MSC the following two procedures (outside MAP) may be applied to control the processor load: - ISDN CCITT Recommendation Q.764 (Automatic Congestion Control), applicable to reduce the mobile terminating traffic; - BSSAP GSM 08.08 (A-interface Flow Control), applicable to reduce the mobile originating tra... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 5.1.2 Overload control for MAP entities | For all MAP entities, especially the HLR, the following overload control method is applied: If overload of a MAP entity is detected requests for certain MAP operations (see tables 5.1/1, 5.1/2, 5.1/3 and 5.1/4) may be ignored by the responder. The decision as to which MAP Operations may be ignored is made by the MAP se... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 5.1.3 Congestion control for Signalling System No. 7 | The requirements of SS7 Congestion control have to be taken into account as far as possible. Means which could be applied to achieve the required traffic reductions are described in subclauses 5.1.1 and 5.1.2. Responder = MSC/VLR Initiating Entity Priority high Handover handoverControl MSC (prepareHandover/v2), (perfor... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 5.2 Compatibility | |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 5.2.1 General | The present document of the Mobile Application Part is designed in such a way that an implementation which conforms to it can also conform to the Mobile Application Part operational version 1 specifications, except on the MSC-VLR interface. A version negotiation mechanism based on the use of an application-context-name... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 5.2.2 Strategy for selecting the Application Context (AC) version | A method should be used to minimize the number of protocol fall-backs which would occur sometimes if the highest supported AC-Name were always the one selected by GSM entities when initiating a dialogue. The following method is an example which can be used mainly at transitory phase stage when the network is one of mix... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 5.2.2.1 Proposed method | A table (table 1) may be set up by administrative action to define the highest application context (AC) version supported by each destination; a destination may be another node within the same or a different PLMN, or another PLMN considered as a single entity. The destination may be defined by an E.164 number or an E.2... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 5.2.2.2 Managing the version look-up table | WHEN it receives a MAP-OPEN ind the MAP-User determines the originating entity number either using the originating address parameter or the originating reference parameter or retrieving it from the subscriber data using the IMSI or the MSISDN. IF the entity number is known THEN It updates (if required) the associated l... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 5.2.2.3 Optimizing the method | A table look-up may be avoided in some cases if both the HLR and the VLR or both the HLR and the SGSN store for each subscriber the version of the AC-name used at location updating. Then: - for procedures which make use of the same application-context, the same AC-name (thus the same version) can be selected (without a... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 6 Requirements concerning the use of SCCP and TC | |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 6.1 Use of SCCP | The Mobile Application Part makes use of the services offered by the Signalling Connection Control Part of signalling System No. 7. CCITT Blue Book or ITU-T (03/93) Recommendations Q.711 to Q.716 should be consulted for the full specification of SCCP. In North America (World Zone 1) the national version of SCCP is used... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 6.1.1 SCCP Class | MAP will only make use of the connectionless classes (0 or 1) of the SCCP. |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 6.1.2 Sub-System Number (SSN) | The Application Entities (AEs) defined for MAP consist of several Application Service Elements (ASEs) and are addressed by sub-system numbers (SSNs). The SSN for MAP are specified in GSM 03.03 [17]. When the SGSN emulates MSC behavior for processing messages (MAP-MO-FORWARD-SHORT-MESSAGE, MAP_CHECK_IMEI) towards entiti... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 6.1.3 SCCP addressing | |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 6.1.3.1 Introduction | Within the GSM System there will be a need to communicate between entities within the same PLMN and in different PLMNs. Using the Mobile Application Part (MAP) for this function implies the use of Transaction Capabilities (TC) and the Signalling Connection Control Part (SCCP) of CCITT Signalling System No. 7. ETSI ETSI... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 6.1.3.2 The Mobile-services Switching Centre (MSC) | There are several cases where it is necessary to address the MSC. |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 6.1.3.2.1 MSC interaction during handover | The address is derived from the target Cellid. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.