hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
be78612ff8f67b9deea189a8b80762b8 | 125 101 | 7.4 Maximum input level | .......................................................................................................................22 |
be78612ff8f67b9deea189a8b80762b8 | 125 101 | 7.4.1 Minimum requirement | ................................................................................................................22 |
be78612ff8f67b9deea189a8b80762b8 | 125 101 | 7.5 Adjacent Channel Selectivity (ACS) | ...............................................................................................23 |
be78612ff8f67b9deea189a8b80762b8 | 125 101 | 7.5.1 Minimum requirement | ................................................................................................................23 |
be78612ff8f67b9deea189a8b80762b8 | 125 101 | 7.6 Blocking characteristics | ...................................................................................................................23 |
be78612ff8f67b9deea189a8b80762b8 | 125 101 | 7.6.1 Minimum requirement | ................................................................................................................23 |
be78612ff8f67b9deea189a8b80762b8 | 125 101 | 7.7 Spurious response | ............................................................................................................................24 ETSI TS 125 101 V3.1.0 (2000-01) (3G TS 25.101 version 3.1.0 Release 1999) ETSI PAGE 4 TS 25.101 v.x.x (1999-12) |
be78612ff8f67b9deea189a8b80762b8 | 125 101 | 7.7.1 Minimum requirement | ................................................................................................................24 |
be78612ff8f67b9deea189a8b80762b8 | 125 101 | 7.8 Intermodulation characteristics | ........................................................................................................24 |
be78612ff8f67b9deea189a8b80762b8 | 125 101 | 7.8.1 Minimum requirement | ................................................................................................................24 |
be78612ff8f67b9deea189a8b80762b8 | 125 101 | 7.9 Spurious emissions | ...........................................................................................................................25 |
be78612ff8f67b9deea189a8b80762b8 | 125 101 | 7.9.1 Minimum requirement | ................................................................................................................25 |
be78612ff8f67b9deea189a8b80762b8 | 125 101 | 8 Performance requirement | ........................................................................................................26 |
be78612ff8f67b9deea189a8b80762b8 | 125 101 | 8.1 General | .............................................................................................................................................26 |
be78612ff8f67b9deea189a8b80762b8 | 125 101 | 8.2 Demodulation in static propagation conditions | ................................................................................26 |
be78612ff8f67b9deea189a8b80762b8 | 125 101 | 8.2.1 Demodulation of Paging Channel (PCH) | ...................................................................................26 |
be78612ff8f67b9deea189a8b80762b8 | 125 101 | 8.2.2 Demodulation of Forward Access Channel (FACH) | ..................................................................28 |
be78612ff8f67b9deea189a8b80762b8 | 125 101 | 8.2.3 Demodulation of Dedicated Channel (DCH) | .............................................................................29 |
be78612ff8f67b9deea189a8b80762b8 | 125 101 | 8.3 Demodulation of DCH in multi-path fading propagation conditions | ...............................................30 |
be78612ff8f67b9deea189a8b80762b8 | 125 101 | 8.3.1 Single Link Performance | ............................................................................................................30 |
be78612ff8f67b9deea189a8b80762b8 | 125 101 | 8.4 Demodulation of DCH in moving propagation conditions | ..............................................................32 |
be78612ff8f67b9deea189a8b80762b8 | 125 101 | 8.4.1 Single link performance | .............................................................................................................32 |
be78612ff8f67b9deea189a8b80762b8 | 125 101 | 8.5 Demodulation of DCH in birth-death propagation conditions | .........................................................33 |
be78612ff8f67b9deea189a8b80762b8 | 125 101 | 8.5.1 Single link performance | .............................................................................................................33 |
be78612ff8f67b9deea189a8b80762b8 | 125 101 | 8.6 Demodulation of DCH in Base Station Transmit diversity modes | ..................................................34 |
be78612ff8f67b9deea189a8b80762b8 | 125 101 | 8.6.1 Demodulation of DCH in open-loop transmit diversity mode | ...................................................34 |
be78612ff8f67b9deea189a8b80762b8 | 125 101 | 8.6.2 Demodulation of DCH in closed loop transmit diversity mode | .................................................35 |
be78612ff8f67b9deea189a8b80762b8 | 125 101 | 8.6.3 Demodulation of DCH in Site Selection Diversity Transmission mode | ....................................36 |
be78612ff8f67b9deea189a8b80762b8 | 125 101 | 8.7 Demodulation in Handover conditions | ............................................................................................38 |
be78612ff8f67b9deea189a8b80762b8 | 125 101 | 8.7.1 Inter-Cell Soft Handover Performance | .......................................................................................38 8.8 Inner loop power control in downlink.............................................................................................40 |
be78612ff8f67b9deea189a8b80762b8 | 125 101 | 8.8.1 Inner loop power control in the downlink | ..................................................................................40 |
be78612ff8f67b9deea189a8b80762b8 | 125 101 | 8.9 Outer loop power control in downlink | .............................................................................................41 |
be78612ff8f67b9deea189a8b80762b8 | 125 101 | 8.9.1 Outer loop power control in the downlink | ..................................................................................41 8.10 Downlink compressed mode...........................................................................................................42 |
be78612ff8f67b9deea189a8b80762b8 | 125 101 | 8.10.1 Single link performance | .............................................................................................................42 Annex A (normative): Measurement channels..................................................................................43 A.1 General.......................................................................... |
be78612ff8f67b9deea189a8b80762b8 | 125 101 | 6.4.2.1 Power control steps | The power control step is the change in the UE transmitter output power in response to a single TPC command, TPC_cmd, derived at the UE. |
be78612ff8f67b9deea189a8b80762b8 | 125 101 | 6.4.2.1.1 Minimum requirement | The UE transmitter shall have the capability of changing the output power with a step sizeof 1, 2 and 3 dB according to the value of ∆TPC or ∆RP-TPC, in the slot immediately after the TPC_cmd can be derived (a) The transmitter output power step due to inner loop power control shall be within the range shown in Table 5.... |
be78612ff8f67b9deea189a8b80762b8 | 125 101 | 6.4.3.1 Minimum requirement | The minimum transmit power shall be better than –44 dBm measured with a filter that has a Root-Raised Cosine (RRC) filter response with a roll off α = 0.22 and a bandwidth equal to the chip rate. ETSI TS 125 101 V3.1.0 (2000-01) (3G TS 25.101 version 3.1.0 Release 1999) ETSI ETSI TS 125 101 V3.1.0 (2000-01) PAGE 16 TS ... |
be78612ff8f67b9deea189a8b80762b8 | 125 101 | 6.5.1.1 Minimum requirement | The requirement for the transmit OFF power shall be better than –50 dBm measured with a filter that has a Root-Raised Cosine (RRC) filter response with a roll off α = 0.22 and a bandwidth equal to the chip rate 6.5.2 Transmit ON/OFF Time mask The time mask for transmit ON/OFF defines the ramping time allowed for the UE... |
be78612ff8f67b9deea189a8b80762b8 | 125 101 | 6.5.2.1 Minimum requirement | The transmit power levels versus time should meet the mask specified in figure 1a Up-Link DPDCH Up-Link DPCCH Average ON Power Minimum Power OFF Power 50 µs 50 µs Figure 1a: Transmit ON/OFF template 6.5.3 Change of TFC A change of TFC (Transport Format Combination) in uplink means that the power in the uplink varies ac... |
be78612ff8f67b9deea189a8b80762b8 | 125 101 | 6.5.3.1 Minimum requirement | A change of output power is required when the TFC, and thereby the data rate, is changed. The ratio of the amplitude between the DPDCH codes and the DPCCH code will vary. The power step due to a change in TFC shall be calculated in the UE so that the power transmitted on the DPCCH shall follow the inner loop power cont... |
be78612ff8f67b9deea189a8b80762b8 | 125 101 | 6.5.4.1 Minimum requirement | A change of output power is required during uplink compressed frames since the transmission of data is performed in a shorter interval. The ratio of the amplitude between the DPDCH codes and the DPCCH code will also vary. The power step due to compressed mode shall be calculated in the UE so that the energy transmitted... |
be78612ff8f67b9deea189a8b80762b8 | 125 101 | 6.6.2.1 Spectrum emission mask | The spectrum emission mask of the UE applies to frequencies, which are between 2.5 MHz and 12.5 MHz away from the UE center carrier frequency. The out of channel emission is specified relative to the UE output power measured in a 3.84 MHz bandwidth. |
be78612ff8f67b9deea189a8b80762b8 | 125 101 | 6.6.2.1.1 Minimum requirement | The power of any UE emission shall not exceed the levels specified in Table 7 Table 7: Spectrum Emission Mask Requirement Frequency offset from carrier • f Minimum requirement Measurement bandwidth 2.5 - 3.5 MHz -35 -15*(∆f – 2.5) dBc 30 kHz * 3.5 - 7.5 MHz -35- 1*(∆f-3.5) dBc 1 MHz * 7.5 - 8.5 MHz -39 - 10*(∆f – 7.5) ... |
be78612ff8f67b9deea189a8b80762b8 | 125 101 | 6.6.2.2 Adjacent Channel Leakage power Ratio (ACLR) | Adjacent Channel Leakage power Ratio (ACLR) is the ratio of the transmitted power to the power measured after a receiver filter in the adjacent channel(s). Both the transmitted power and the received power are measured with a filter that has a Root- Raised Cosine (RRC) filter response with roll-off α =0.22 and a bandwi... |
be78612ff8f67b9deea189a8b80762b8 | 125 101 | 6.6.2.2.1 Minimum requirement | The ACLR shall be better than the value specified in Table 8 Table 8:UE ACLR Power Class UE channel ACLR limit 3 + 5 MHz or – 5 MHz 33 dB or –50 dBm which ever is higher 3 + 10 MHz or – 10 MHz 43 dB or –50 dBm which ever is higher 4 + 5 MHz or – 5 MHz 33 dB or –50 dBm which ever is higher 4 + 10 MHz or –10 MHz 43 dB or... |
be78612ff8f67b9deea189a8b80762b8 | 125 101 | 6.6.3.1 Minimum requirement | These requirements are only applicable for frequencies, which are greater than 12.5 MHz away from the UE center carrier frequency Table 9a: General spurious emissions requirements Frequency Bandwidth Resolution Bandwidth Minimum requirement 9 kHz ≤ f < 150 kHz 1 kHz -36 dBm 150 kHz ≤ f < 30 MHz 10 kHz -36 dBm 30 MHz ≤ ... |
be78612ff8f67b9deea189a8b80762b8 | 125 101 | 6.8.2.1 Minimum requirement | The modulation accuracy shall not exceed 17.5 % at the maximum output power 6.8.3 Peak code domain error The code domain error is computed by projecting the error vector power onto the code domain at the maximum spreading factor. The error vector for each power code is defined as the ratio to the mean power of the refe... |
be78612ff8f67b9deea189a8b80762b8 | 125 101 | 6.8.3.1 Minimum requirement | The peak code domain error shall not exceed [ ] dB ETSI TS 125 101 V3.1.0 (2000-01) (3G TS 25.101 version 3.1.0 Release 1999) ETSI ETSI TS 125 101 V3.1.0 (2000-01) PAGE 22 TS 25.101 v.x.x (1999-12) 7.0 Receiver characteristics 7.1 General Unless otherwise stated the receiver characteristics are specified at the antenna... |
be78612ff8f67b9deea189a8b80762b8 | 125 101 | 8.2.1.1 Minimum requirement | For the parameters specified in Table 19 the MER shall not exceed the piece-wise linear MER curve specified by the points in Table 20 ETSI TS 125 101 V3.1.0 (2000-01) (3G TS 25.101 version 3.1.0 Release 1999) ETSI ETSI TS 125 101 V3.1.0 (2000-01) PAGE 27 TS 25.101 v.x.x (1999-12) Table 19 PCH parameters in static propa... |
be78612ff8f67b9deea189a8b80762b8 | 125 101 | 8.2.2.1 Minimum requirement | For the parameters specified in Table 21 the MER shall not exceed the piece-wise linear MER curve specified by the points in table 22 Table 21: FACH parameters in static propagation conditions Parameter Unit Value or c I E _ DPCH dB or c I E SCCPCH _ dB oc or I Iˆ dB -1 oc I dBm/3.84 MHz -60 Control Data Rate ? t b N E... |
be78612ff8f67b9deea189a8b80762b8 | 125 101 | 8.2.3.1 Minimum requirement | For the parameters specified in Table 23 the BLER shall not exceed the piece-wise linear BLER curve specified by the points in table 24 Table 23: DCH parameters in static propagation conditions Parameter Unit Test 1 Test 2 Test 3 Test 4 Test 5 oc or I Iˆ dB -1 oc I dBm/3.84 MHz -60 Information Data Rate kbps 12.2 12.2 ... |
be78612ff8f67b9deea189a8b80762b8 | 125 101 | 8.3.1.1 Minimum requirement | For the parameters specified in Table 25, 27 and 29 the BLER shall not exceed the associated piece-wise linear BLER curves specified by the points in Table 26, 28 and 30 Table 25: Test Parameters for DCH in multi-path fading propagation conditions (Case 1) Parameter Unit Test 1 Test 2 Test 3 Test 4 Test 5 oc or I Iˆ dB... |
be78612ff8f67b9deea189a8b80762b8 | 125 101 | 8.4.1.1 Minimum requirement | For the parameters specified in Table 31 the BLER shall not exceed the piece-wise linear BLER curve specified in points in Table 32 Table 31: DCH parameters in moving propagation conditions Parameter Unit Test 1 Test 2 Test 3 oc or I Iˆ dB -1 oc I dBm/3.84 MHz -60 Information Data Rate kbps 12.2 12.2 64 TFCI - off on o... |
be78612ff8f67b9deea189a8b80762b8 | 125 101 | 8.5.1.1 Minimum requirement | For the parameters specified in Table 33, the BLER shall not exceed the piece-wise linear BLER curve in the points in Table 34 Table 33: DCH parameters in birth-death propagation conditions Parameter Unit Test 1 Test 2 Test 3 oc or I Iˆ dB -1 oc I dBm/3.84 MHz -60 Information Data Rate kbps 12.2 12.2 64 TFCI - off on o... |
be78612ff8f67b9deea189a8b80762b8 | 125 101 | 8.6.1.1 Minimum requirement | For the parameters specified in Table 35 the BLER shall not exceed the associated piece-wise linear BLER curve specified by the points in Table 36 Table 35: Test parameters for DCH reception in an open loop transmit diversity scheme. (Propagation condition: Case 1) Parameter Unit Test 1 oc or I Iˆ dB [ ] oc I dBm/3.84 ... |
be78612ff8f67b9deea189a8b80762b8 | 125 101 | 8.6.2.1 Minimum requirement | For the parameters specified in Table 37 the BLER shall not exceed the associated piece-wise linear BLER curves specified by the points in Table 38. Table 37: Test Parameters for DCH Reception in closed loop transmit diversity mode (Propagation condition: Case 1) Parameter Unit Test 1 (Mode 1) Test 2 (Mode 2) oc or I I... |
be78612ff8f67b9deea189a8b80762b8 | 125 101 | 8.7.1.1 Minimum requirement | For the parameters specified in Table 42, the BLER shall not exceed the piece-wise linear BLER curve specified by the points in Table 43 Table 42: DCH parameters in multi-path propagation conditions during Soft Handoff (Case 3) Parameter Unit Test 1 Test 2 Test 3 Test 4 Test 5 or c I E _ DPCH oc or I I 1 ˆ and oc or I ... |
be78612ff8f67b9deea189a8b80762b8 | 125 101 | 8.8.1.1 Minimum requirements | For the parameters specified in Table 44, the BLER and DPCH_Ec/Ior value shall not exceed the values specified in Table 45. Note 1. Power control is ON during the test. 2. Power control step size is 1 dB. Table 44: Test parameters for downlink inner loop power control Parameter Unit Test 1 Test 2 oc or I Iˆ dB 9 -1 oc ... |
be78612ff8f67b9deea189a8b80762b8 | 125 101 | 8.9.1.1 Minimum requirements | For the parameters specified in Table 46 the downlink or c I E DPCH _ power shall be below the specified value and the reported quality value shown in table 47. Note 1. Power control is ON during the test. 2. The averaging time T shall be long enough to minimize the previous quality target impact to the result. Table 4... |
be78612ff8f67b9deea189a8b80762b8 | 125 101 | 8.10.1.1 Minimum requirements | For the parameters specified in Table 48 the average downlink or c I E DPCH _ power shall be below the specified value for the reported BLER shown in table 49. The uplink DPDCH power shall be below the specified value. Note 1. Inner loop power control is ON during the test. Table 48: Test parameter for downlink compres... |
a49e477e846d725703395e7c1abc4db0 | 101 393 | 1 Scope | The GSM PLMN supports a wide range of voice and non-voice services in the same network. In order to enable operators the ability to provide a commercially viable service there is a need to provide charging functions. The present document describes the functionality of charging in GPRS needed to support the first phase ... |
a49e477e846d725703395e7c1abc4db0 | 101 393 | 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... |
a49e477e846d725703395e7c1abc4db0 | 101 393 | 3 Definitions abbreviations and symbols | |
a49e477e846d725703395e7c1abc4db0 | 101 393 | 3.1 Definitions | Refer to: GSM 02.60 [3]. In GSM 02.02 the bearer services are described. The general network configuration is described in GSM 03.02 and the GSM PLMN access reference configuration is defined in GSM 04.02. The various connection types used in the GSM PLMN are presented in GSM 03.10. Terminology used in the present docu... |
a49e477e846d725703395e7c1abc4db0 | 101 393 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply. Additional applicable abbreviations can be found in GSM 01.04 [1]. APN Access Point Name BG Border Gateway BS Billing System BSS Base Station Subsystem CDR Call Detail RecordC-ID Charging ID CG Charging Gateway CGF Charging Gateway Functionali... |
a49e477e846d725703395e7c1abc4db0 | 101 393 | 3.3 Symbols | For the purposes of the present document, the following Symbols apply: A Interface between an MSC and a BSC. Gb Interface between an SGSN and a BSC. Gc Interface between an GGSN and an HLR. Gd Interface between an SMS-GMSC and an SGSN, and between a SMS-IWMSC and an SGSN. Gf Interface between an SGSN and an EIR. Gi Ref... |
a49e477e846d725703395e7c1abc4db0 | 101 393 | 4 Architecture | The following figures 1 and 2 show the GPRS logical architecture and GPRS charging logical architecture. Gf D Gi Gn Gb Gc C E Gp Gs Signalling and Data Transfer Interface Signalling Interface MSC/VLR TE MT BSS TE PDN R Um Gr A HLR Other PLMN SGSN GGSN Gd SM-SC SMS-GMSC SMS-IWMSC GGSN EIR SGSN Gn Figure 1: Overview of t... |
a49e477e846d725703395e7c1abc4db0 | 101 393 | 4.1 Charging gateway functionality | The Charging Gateway Functionality (CGF) provides a mechanism to transfer charging information from the SGSN and GGSN nodes to the network operator’s chosen Billing Systems (BS). The Charging Gateway concept enables an operator to have just one logical interface between the CGF and the BS. The CGF may be supported in o... |
a49e477e846d725703395e7c1abc4db0 | 101 393 | 5 Charging Principles | |
a49e477e846d725703395e7c1abc4db0 | 101 393 | 5.1 Requirements | 1) Every GPRS operator collects and processes their own charging information. 2) GPRS charging shall support anonymous access to the GPRS bearer service. 3) As much as is possible the GPRS charging functions should support open interfaces for possible use in future cellular digital packet based networks. 4) It shall be... |
a49e477e846d725703395e7c1abc4db0 | 101 393 | 5.2 Charging Information | Charging information in the GPRS network is collected for each MS by the SGSNs and GGSNs which are serving that MS. The information that the operator uses to generate an invoice to the subscriber is operator-specific. Billing aspects, e.g., a regular fee for a fixed period, are outside the scope of the present document... |
a49e477e846d725703395e7c1abc4db0 | 101 393 | 5.3 Charging Data Collection Principles | Call data record generation and contents should be flexible and unnecessary redundancy in data should be avoided. 1. There are two main records types (one for the SGSN and one for the GGSN related to PDP contexts). Each PDP context generates its own record. A third record is provided for mobility management in the SGSN... |
a49e477e846d725703395e7c1abc4db0 | 101 393 | 5.5 Charging for SMS in GPRS | In GPRS the SMS transmission (MO or MT) can be done via SGSN. The SGSN shall provide an S-SMO-CDR when short message is mobile originated and an S-SMT-CDR when it is mobile terminated. In addition, also SMS-IWMSC (MO-SMS) and SMS-GMSC (MT-SMS) may provide SMS related CDRs as described in GSM 12.05. No active PDP contex... |
a49e477e846d725703395e7c1abc4db0 | 101 393 | 5.6 Charging for Anonymous Access | S-CDRs and G-CDRs are generated by the SGSNs and GGSNs in the case of Anonymous Access, and separately identified in the CDRs. The external Anonymous Access server is charged by the Operator based on the APN. ETSI TS 101 393 V6.2.0 (1999-05) 16 (GSM 12.15 version 6.2.0 Release 1997) 5.7 Charging Triggers – CDR Generati... |
a49e477e846d725703395e7c1abc4db0 | 101 393 | 5.7.1 Triggers for S-CDR Charging Information Collection | An S-CDR is used to collect charging information related to the packet data information for a GPRS mobile in the SGSN. An S-CDR shall be opened for each activated PDP context, and record details such as Record Type, Served IMSI, Sequence Number etc. Not all of the charging information to be collected is static, and oth... |
a49e477e846d725703395e7c1abc4db0 | 101 393 | 5.7.1.1 Triggers for S-CDR Charging Information Addition | The "List of traffic volumes" attribute of the S-CDR consists of a set of containers which are added when specific trigger conditions are met, and identify the volume count separated for uplink and downlink traffic on encountering that trigger condition. Table 1: Triggers for S-CDR charging information addition Trigger... |
a49e477e846d725703395e7c1abc4db0 | 101 393 | 5.7.1.2 Triggers for S-CDR Closure | The S-CDR shall be closed on encountering some trigger conditions. The following table identifies which conditions are supported to permit closures of the S-CDR. Table 2: Triggers for S-CDR closure Closure Conditions Description/Behaviour End of PDP context within the SGSN Deactivation of the PDP context in the SGSN sh... |
a49e477e846d725703395e7c1abc4db0 | 101 393 | 5.7.2 Triggers for M-CDR Charging Information Collection | An M-CDR is used to collect charging information related to the mobility management of a GPRS mobile in the SGSN. An M-CDR shall be opened for each GPRS mobile upon GPRS Attach, and record details such as Record Type, Served IMSI, Sequence Number etc. Not all of the charging information to be collected is static, and o... |
a49e477e846d725703395e7c1abc4db0 | 101 393 | 5.7.2.1 Triggers for M-CDR Charging Information Addition | The "Change of Location" attribute of the M-CDR consists of a set of containers which are added when specific trigger conditions are met, and identify the timestamped routing area on encountering that trigger condition. Table 3: Triggers for M-CDR Charging Information Addition Trigger Conditions Description/Behaviour M... |
a49e477e846d725703395e7c1abc4db0 | 101 393 | 5.7.2.2 Triggers for M-CDR Closure | The M-CDR shall be closed on encountering some trigger conditions. The following table identifies which conditions are supported to permit closures of the M-CDR. Table 4: Triggers for M-CDR closure Closure Conditions Description/Behaviour End of MM context within SGSN Deactivation of the MM context in the SGSN shall re... |
a49e477e846d725703395e7c1abc4db0 | 101 393 | 5.7.3 Triggers for G-CDR Charging Information Collection | A G-CDR is used to collect charging information related to the packet data information for a GPRS mobile in the GGSN. A G-CDR shall be opened for each activated PDP context, and record details such as Record Type, Served IMSI, Sequence Number etc. Not all of the charging information to be collected is static, and other... |
a49e477e846d725703395e7c1abc4db0 | 101 393 | 5.8 Example charging scenarios | This clause contains a number of example scenarios illustrating the purpose and practical usage of the various types of records defined in the previous subclauses. These examples are by no means exhaustive. For the purpose of these examples the following assumptions have been made: - the CDR records are sent to a CGF; ... |
a49e477e846d725703395e7c1abc4db0 | 101 393 | 5.8.1 GPRS Mobile to PDN Context | Figure 5 illustrates a simple outgoing GPRS context from a PLMN GPRS subscriber "A" to a mainframe "B" via a PDN (1). The respective PDP context is activated in the SGSN and GGSN and PDP PDUs are routed in MO and MT direction. The SGSN shall create a S-CDR and the GGSN shall create a G-CDR for subscriber "A". The recor... |
a49e477e846d725703395e7c1abc4db0 | 101 393 | 5.8.2 GPRS Mobile to Mobile Context | Figure 6 illustrates a simple GPRS mobile to mobile context within the same HPLMN. The respective A-party related PDP context is activated in the SGSN-A and the GGSN (1). After the location of subscriber "B" is determined, the B party related PDP context is activated (2) in the SGSN-B and the GGSN and PDP PDUs are rout... |
a49e477e846d725703395e7c1abc4db0 | 101 393 | 5.8.3 PDN to GPRS Mobile Context | Figure 7 illustrates a simple incoming GPRS context from a mainframe "A" to GPRS mobile subscriber "B" via a PDN (1). After the location of subscriber "B" is determined, the PDP context is activated (2). The GGSN receiving the PDUs shall generate a G-CDR whereas the SGSN currently serving subscriber "B" creates an S-CD... |
a49e477e846d725703395e7c1abc4db0 | 101 393 | 5.8.4 GPRS Mobile to PDN Context while roaming, GGSN in HPLMN | Figure 8 illustrates an outgoing GPRS context from a roaming GPRS mobile subscriber "A" to mainframe "B" via Boarder Gateway, inter PLMN backbone and GGSN of the HPLMN (1). The respective a-party related PDP context is activated in the SGSN and GGSN and PDUs are routed in MO and MT direction. The SGSN shall create an S... |
a49e477e846d725703395e7c1abc4db0 | 101 393 | 6 Charging Data Collection | |
a49e477e846d725703395e7c1abc4db0 | 101 393 | 6.1 Record contents | The following tables describe the contents of each of the call and event records generated by the GSNs. Each table contains the name of the field, a key indicating whether or not the field is mandatory, and a description of the contents. The key field has the following meaning: M This field is mandatory and always pres... |
a49e477e846d725703395e7c1abc4db0 | 101 393 | 6.1.1 GPRS charging data in SGSN (S-CDR) | If the collection of SGSN data is enabled then the following GPRS SGSN data shall be available for each PDP context. Table 5: GPRS SGSN PDP context data Field Description Record Type M GPRS SGSN PDP context record. Network initiated PDP context C Present if this is a network initiated PDP context. Anonymous Access Indi... |
a49e477e846d725703395e7c1abc4db0 | 101 393 | 6.1.2 GPRS charging data in GGSN (G-CDR) | If the collection of GGSN data is enabled then the following GPRS GGSN data shall be available for each PDP context. Table 6: GPRS GGSN PDP context data Field Description Record Type M GPRS GGSN PDP context record. Network initiated PDP context C Present if this is a network initiated PDP context. Anonymous Access Indi... |
a49e477e846d725703395e7c1abc4db0 | 101 393 | 6.1.3 GPRS mobile station mobility management data in SGSN (M-CDR) | If the collection of MS mobility management data is enabled then GPRS SGSN shall start collecting information each time the mobile is attached to the SGSN. Table 7: GPRS SGSN mobile station mobility management data Field Description Record Type M GPRS SGSN mobility management record. Served IMSI M IMSI of the MS. Serve... |
a49e477e846d725703395e7c1abc4db0 | 101 393 | 6.1.4 GPRS MO SMS data in SGSN (S-SMO-CDR) | If enabled, an S-SMO-CDR SGSN Mobile originated SMS record shall be produced for each short message sent by a mobile subscriber via SGSN. Table 8: SGSN Mobile originated SMS record Field Description Record Type M SGSN Mobile originated SMS. Served IMSI M The IMSI of the subscriber. Served IMEI O The IMEI of the ME, if ... |
a49e477e846d725703395e7c1abc4db0 | 101 393 | 6.1.5 GPRS MT SMS data in SGSN (S-SMT-CDR) | If enabled, an SGSN Mobile terminated SMS record shall be produced for each short message received by a mobile subscriber via SGSN. Table 9: SGSN Mobile terminated SMS record Field Description Record Type M SGSN Mobile terminated SMS. Served IMSI M The IMSI of the subscriber. Served IMEI O The IMEI of the ME, if availa... |
a49e477e846d725703395e7c1abc4db0 | 101 393 | 6.1.6 Description of Record Fields | This subclause contains a brief description of each field of the CDRs described in the previous subclause. |
a49e477e846d725703395e7c1abc4db0 | 101 393 | 6.1.6.1 Access Point Name | This field contains the logical Access Point Name used to determine the actual connected access point. APN comprises of mandatory network identifier and optional operator identifier. APN can also be a wildcard, in which case SGSN selects the access point address. See GSM 09.60 [22] and GSM 03.60 [8] for more informatio... |
a49e477e846d725703395e7c1abc4db0 | 101 393 | 6.1.6.2 Cause for record closing | This field contains a reason for the release of the CDR including the following: - normal release: PDP context release or GPRS detach; - partial record generation: data volume limit, time (duration) limit, SGSN change of maximum number of changes in charging conditions; - abnormal termination (PDP or MM context); manag... |
a49e477e846d725703395e7c1abc4db0 | 101 393 | 6.1.6.3 Charging ID | This field is a charging identifier which can be used together with GGSN address to identify all records produced in SGSN(s) and GGSN involved in a single PDP context. Charging ID is generated by GGSN at PDP context activation and transferred to context requesting SGSN. At inter-SGSN routing area update charging ID is ... |
a49e477e846d725703395e7c1abc4db0 | 101 393 | 6.1.6.4 Diagnostics | This field includes a more detailed technical reason for the release of the connection and may contain one of the following: - a MAP error from GSM 09.02 [17]; - a Cause from GSM 04.08 [16]; The diagnostics may also be extended to include manufacturer and network specific information. |
a49e477e846d725703395e7c1abc4db0 | 101 393 | 6.1.6.5 Duration | This field contains the relevant duration in seconds for PDP contexts (S-CDR, G-CDR, and attachment (M-CDR)). For partial records this is the duration of the individual partial record and not the cumulative duration. It should be noted that the internal time measurements may be expressed in terms of tenths of seconds o... |
a49e477e846d725703395e7c1abc4db0 | 101 393 | 6.1.6.6 Dynamic Address Flag | This field indicates that PDP address has been dynamically allocated for that particular PDP context. Field is missing if address is static i.e. part of PDP context subscription. Dynamic address allocation might be relevant for charging e.g. the duration of PDP context as one resource offered and possible owned by netw... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.