hash
stringlengths 32
32
| doc_id
stringlengths 7
13
| section
stringlengths 3
121
| content
stringlengths 0
3.58M
|
|---|---|---|---|
2c9d130f4599201b7ff29ffb2e9ae502
|
100 528
|
6.1.2 Radio Link Protocol
|
The Radio Link Protocol (RLP) is a layer 2 LAPB based protocol which performs grouping of user data for the purpose of implementing error control and retransmission mechanisms in the case of non-transparent low layer capabilities. The RLP layer is in charge of the transmission of the data compression parameters to the peer RLP entity and to the L2R layer, when those parameters have to be negotiated. The function that realizes the implementation of the protocol (described in GSM 04.22) takes place at both ends of the GSM connection in the MT and the IWF/MSC. ETSI ETSI TS 100 528 V7.0.1 (1999-07) 17 (GSM 03.10 version 7.0.1 Release 1998)
|
2c9d130f4599201b7ff29ffb2e9ae502
|
100 528
|
6.1.3 Layer 2 Relay function
|
The Layer 2 Relay function (L2R) performs protocol conversion between the user data structure (e.g. characters or X.25 Layer 2 frames) and a structure more adapted to the radio link protocol. This function is described in the relevant GSM 07-series specifications. The L2R function includes the data compression function.
|
2c9d130f4599201b7ff29ffb2e9ae502
|
100 528
|
6.1.4 Resources allocated by the GSM network
|
Part of the GSM connection concerns the resources allocated by the GSM network on the basis of the attribute values of the connection elements. For the speech calls, the GSM codec is allocated. For data calls, resources are provided at the IWF/MSC such as: - V.110 based rate adaptation for such channel codings as TCH/F 4,8 and TCH/F9,6 and GSM specific rate adaption for channel coding TCH/F14.4 (GSM 04.21, 08.20); - filtering of status bits (GSM 07.01); - RLP for non-transparent services (GSM 04.22); - Data compression (GSM 04.22, 07.02). These are sufficient for data services such as: - asynchronous circuit (bearer service series 20), used with unrestricted digital information transfer capability; - synchronous circuit (bearer service series 30), used with unrestricted digital information transfer capability when interworking with circuit switched digital networks. In addition to the above listed resources, further resources are allocated in the other cases: - modems for asynchronous circuit (bearer service series 20) or synchronous circuit (bearer service series 30) used with 3.1 kHz information transfer capability; - fax adaptor for the fax group 3 (teleservice series 60); - PAD for asynchronous PAD (bearer service series 40), Packet handler and flag stuffing for synchronous packet (bearer service series 50) used with unrestricted digital information transfer capability; - flag stuffing for synchronous packet using bearer service series 30 with unrestricted digital information transfer capability when interworking with packet switched networks.
|
2c9d130f4599201b7ff29ffb2e9ae502
|
100 528
|
6.2 GSM PLMN connection elements
|
The radio interface connection element is the portion of the connection spanning from the Mobile Termination to an appropriate internal reference point within the Base Station System. The A interface connection element is the portion of the connection from the above internal reference point within the base station to an appropriate internal reference point within the interworking function (IWF) of the MSC. By using connection elements and attributes which have a layered nature the construction of a connection type is more easily viewed. The use of different values for the same attribute allows a greater degree of description and flexibility. 6.3 Rules of association for the attribute values of connection elements and connection types This subclause describes the relationship between the attribute values of connection elements and connection types. For each attribute the various possible values recommended are listed. The definitions of the attributes and attribute values are contained in the annex A. In addition to the (possible) attribute values applicable to the connection elements, an ETSI ETSI TS 100 528 V7.0.1 (1999-07) 18 (GSM 03.10 version 7.0.1 Release 1998) association law is given (where appropriate) for each attribute to show how the value of the attribute for the overall connection type is obtained from the values of the attribute applicable to the connection elements.
|
2c9d130f4599201b7ff29ffb2e9ae502
|
100 528
|
6.3.1 Information transfer mode
|
Attribute values for connection elements: Circuit. Attribute values for overall connection type: Circuit. Association Law: Circuit.
|
2c9d130f4599201b7ff29ffb2e9ae502
|
100 528
|
6.3.2 Information transfer rate (kbit/s)
|
Attribute values for connection elements: 3.6 or 6.0 or 12.0 or 13.0 or 14.5 or 64.0 or n × 6.0 ( 1 ≤ n ≤ 4 ) or n × 12.0 ( 1 ≤ n ≤ 6 ) or n x 14.5 ( 1 ≤ n ≤ 5 ) Attribute values for overall connection type: 3.6 or 6.0 or 12.0 or 13.0 or 14.5 or 64.0; or n × 6.0 ( 1 ≤ n ≤ 4 ) or n × 12.0 ( 1 ≤ n ≤ 6 ) or n x 14.5 ( 1 ≤ n ≤ 5 ). Association Law: The value for the overall connection type will be equal to the lowest value of any of its connection elements.
|
2c9d130f4599201b7ff29ffb2e9ae502
|
100 528
|
6.3.3 Information transfer susceptance
|
Attribute values for connection elements: Speech processing functions (e.g. GSM Speech Coding/A Law conversion, Discontinuous Transmission) and/or Echo suppression functions and/or Multiple satellite hops or null. Attribute values for overall connection types: Unrestricted Digital Information or Speech. Association Law: For an overall connection type to have the value Unrestricted digital no connection element may contain speech processing functions or echo suppression functions. Connection elements containing speech processing devices having the flexibility to change operation between speech and unrestricted digital would on the other hand be allowed to be part of a number of different connection types. For an overall connection type to have the value speech it must contain GSM Speech Coding/A Law conversion equipment and echo suppression functions when appropriate.
|
2c9d130f4599201b7ff29ffb2e9ae502
|
100 528
|
6.3.4 Establishment of connection
|
Attribute values for connection elements: Demand. Attribute values for overall connection type: Demand. ETSI ETSI TS 100 528 V7.0.1 (1999-07) 19 (GSM 03.10 version 7.0.1 Release 1998) Association Law: If any of the connection elements are Demand, then the overall connection type is Demand.
|
2c9d130f4599201b7ff29ffb2e9ae502
|
100 528
|
6.3.5 Symmetry
|
Attribute values for connection elements: Bidirectional Symmetric. Bidirectional Asymmetric (Multislot connections for data). Attribute values for overall connection type: Bidirectional Symmetric. Bidirectional Asymmetric (Multislot connections for data). Association Law: The overall symmetry can only be generated from the connection elements by analysis of the connection element values in the context of the architecture of the connection.
|
2c9d130f4599201b7ff29ffb2e9ae502
|
100 528
|
6.3.6 Connection configuration Topology
|
Attribute values for connection elements: Point-to-point. Attribute values for the overall connection type: Not applicable. Association Law: Not applicable.
|
2c9d130f4599201b7ff29ffb2e9ae502
|
100 528
|
6.3.7 Structure
|
Attribute values for connection elements: Unstructured or Service Data Unit Integrity. Attribute values for the overall connection type: As per values for connection elements. Association Law: Unspecified.
|
2c9d130f4599201b7ff29ffb2e9ae502
|
100 528
|
6.3.8 Channels
| |
2c9d130f4599201b7ff29ffb2e9ae502
|
100 528
|
6.3.8.1 Information channel (rate)
|
Attribute values for connection elements: Radio interface connection element: Full rate TCH or Full rate TCHs or Half rate TCH. A interface connection element: 64.0 kbit/s. Attribute values for the overall connection type: Not applicable. ETSI ETSI TS 100 528 V7.0.1 (1999-07) 20 (GSM 03.10 version 7.0.1 Release 1998)
|
2c9d130f4599201b7ff29ffb2e9ae502
|
100 528
|
6.3.8.2 Signalling channel (rate)
|
Attribute values for connection elements: Radio interface connection element: Dm. A interface connection element: Common channel signalling system (64.0 kbit/s). Attribute values for the overall connection type: Not applicable.
|
2c9d130f4599201b7ff29ffb2e9ae502
|
100 528
|
6.3.9 Connection control protocol
|
Attribute values for connection elements: Radio interface connection element: Layer 1: GSM 04.03 and GSM 05-series. Layer 2: GSM 04.05 and 04.06. Layer 3: GSM 04.07 and 04.08, 04.11. A interface connection element: Layer 1: GSM 08.04. Layer 2: GSM 08.06. Layer 3: GSM 04.07, 04.08 and 08.08. Attribute values for the overall connection type: Not applicable.
|
2c9d130f4599201b7ff29ffb2e9ae502
|
100 528
|
6.3.10 Information transfer coding/protocol
|
Attribute values for connection elements: Radio interface connection elements: Layer 1: GSM 04.21, GSM 05-series and 06-series. Layer 2: GSM 04.06, 04.22 and GSM 07.02 or GSM 04.22 and GSM 07.03 or transparent. Layer 3: Transparent, GSM 04.11. A interface connection element: Layer 1: GSM 08.04 and GSM 08.20. Layer 2: GSM 04.22 and GSM 07.02 or GSM 04.22 and GSM 07.03 or transparent. Layer 3: Transparent. Attribute values for the overall connection type: Not applicable.
|
2c9d130f4599201b7ff29ffb2e9ae502
|
100 528
|
6.3.11 Further attributes and attribute values
|
This subclause has outlined the relationships between those attributes values presently existing, the possibility for new values being added remains. Table 4 summarizes the attributes values for GSM PLMN connection elements. ETSI ETSI TS 100 528 V7.0.1 (1999-07) 21 (GSM 03.10 version 7.0.1 Release 1998) Table 4: Values for attributes for GSM PLMN connection elements Attributes Values for attributes Radio interface connection element A interface connection element 1 Information Transfer Mode Circuit Circuit 2 Information Transfer Rate Layer 1 3.6 or 6.0 or 12.0 or 13.0 or 14.5 or n × 6.0 ( 1 ≤ n ≤ 4 ) or n × 12.0 ( 1 ≤ n ≤ 6 ) or n x 14.5 ( 1 ≤ n ≤ 5 ) kbit/s 64.0 kbit/s 3 Information Transfer Susceptance Speech processing equipment, Echo suppression equipment, Null Speech processing equipment, Echo suppression equipment, Null 4 Establishment of Connection Demand Demand 5 Symmetry Bidirectional symmetric Bidirectional asymmetric Bidirectional symmetric Bidirectional asymmetric 6 Connection Configuration Topology Point-to-point Point-to-point 7 Structure Unstructured SDU integrity Unstructured SDU integrity 8 Channel Rate Information Channel Signalling Channel TCH/F(s) or TCH/H Dm 64.0 kbit/s Common channel signalling system 9 Connection Control Protocol Layer 1 Layer 2 Layer 3 GSM 04.03 and 05 series GSM 04.05 and 04.06 GSM 04.07, 04.08, 04.11 GSM 08.04 GSM 08.06 GSM 04.07, 04.08, 08.08 10 Information Transfer Coding/Protocol Layer 1 Layer 2 Layer 3 GSM 04.21 05 and 06 series GSM 04.22 and 07.02 or 04.22 and 07.03 04.06 or transparent Transparent, 04.11 GSM 08.04 and 08.20 GSM 04.22 and 07.02 or 04.22 and 07.03 or transparent Transparent 6.4 Limited set of GSM PLMN connection types (all channel codings excluding TCH/F14.4) From the two connection elements defined in subclause 6.2, the list of attributes and their possible values given in subclause 6.3, and from the service requirements defined in GSM 02.02 and 02.03, a limited set of GSM PLMN connection types have been identified (see also table 5 and table 6 for the relationship between connection elements and telecommunication services). Figure 6 gives the information transfer protocol models for the identified set of GSM PLMN connection types. The S bits correspond to status bits and the D bits to data bits (GSM 04.21); S* indicates that S bits are used only when 3.1 kHz audio ex PLMN. D' bits corresponds to user bits passed in the place of status bits in the non transparent case Moreover, it should be noted that the RLP rate of 6 and 12 kbit/s correspond to the 8 and 16 Kbit/s intermediate rate in the transparent case. Protocol Models 1 a and b are the models for asynchronous data transmission in the transparent mode. Models 1d and 1e are for multislot transparent asynchronous data configurations. Protocol Models 2 a and b are the models for synchronous data transmission in the transparent mode. Models 2d and 2e are for multislot transparent synchronous data. ETSI ETSI TS 100 528 V7.0.1 (1999-07) 22 (GSM 03.10 version 7.0.1 Release 1998) Protocol Models 3 a and b are the models for character "asynchronous" mode data transmission in the non-transparent mode. In this case, L2RCOP represents the protocol used between the Layer 2 Relay functions (L2R) to convey characters between the MS and the IWF (see GSM 07.02). The data compression function is located in the L2R COP function. Models 3d and 3e are for multislot character "asynchronous" data transmission in the non-transparent mode. Protocol Models 4 a, b, and c are the models for synchronous data transmission using the CCITT Recommendation X.25 PSPDN access protocol in the non-transparent mode. In this case, L2RBOP represents the protocol used between the Layer 2 Relay functions (L2R) to convey the LAP-B information between the MS and the IWF (see GSM 07.03). Models 4d, 4e, and 4f are for multislot synchronous data transmission using the CCITT Recommendation X.25 PSPDN access protocol in the non-transparent mode. In all the above models, the a, d and b, e variants indicate alternative access arrangements at the MS, i.e. access at the S interface or at the R interface. The c and f variants indicate a further alternative access arrangement where rate adaptation at the S interface is performed by flag stuffing as defined in CCITT Recommendation X.31. Protocol Model 5a is the model for the transparent support of group 3 facsimile transmission. Model 5b is for transparent support of group 3 facsimile transmission in multislot data configurations. Protocol Models 6 a and b are the models for speech transmission. As in models 1-4, the a and b variants indicate alternative access arrangements at the MS, i.e. access at the S interface or direct access of the telephony teleservice. Protocol model 7 a is the model for the non-transparent support of group 3 facsimile transmission. Model 7b is for non- transparent support of group 3 facsimile transmission in multislot data configurations. In the multislot-data models the data is split into parallel substreams between the Split/Combine-functions (S/C). These substreams are transmitted through parallel TCH/Fs which are treated as independent channels. Between the S/C- functions parallel RA- and FEC-functions are used. For all the models, only the minimum functionality of the IWF is shown. Additional functions will be required for various interworking situations. These additional functions are described in specifications GSM 09.04, GSM 09.05, GSM 09.06 and GSM 09.07. It should be noted that, in Figure 6, the representation of the transcoding and rate adaptation from the intermediate rate on the radio interface to the 64 kbit/s rate required by the MSC is not intended to indicate a particular implementation. The annex B to GSM 03.10 identifies alternative arrangements. 6.5 Limited set of GSM PLMN connection types (for TCH/F14.4 channel coding) Figure 7 provides the information transfer protocol models for the identified set of GSM PLMN connection types for support of TCH/F14.4. The description of models given in subclause 6.4 applies also to figure 7. ETSI ETSI TS 100 528 V7.0.1 (1999-07) 23 (GSM 03.10 version 7.0.1 Release 1998) MS BSS MSC/IWF S I/F RADIO I/F BSS-MSC I/F RA0 RA1 RA2 RA2 RA1 RA1' FEC RA1' RA1 FEC RA2 RA1 RA2 RA2 status D RA1 RA1' FEC FEC RA1' RA1 RA2 status D RA0 status D RA1 RA2 RA2 RA1 D S RA0 D D' RA1' FEC FEC RA1' RA1 RA2 RA2 RA1 D D' D S L2 D S* D' D RA1 RA2 RA2 RA1 RA1' FEC FEC RA1' L2 RA1 RA2 RA2 RA1 D status L2 L3 Model 2a Model 1a Model 3a Model 4a Transparent asynchronous data Transparent synchronous data characters asynch. L2R COP Radio Link Protocol X.25 Packet Layer Protocol L2RBOP Radio Link Protocol LAPB LAPB char. D S D' D TE1 or TA MT1 asynch. (optionally including D ata Compression) RA0 RA2 RA1 S D RA2 RA1 S D Figure 6: Information transfer protocol models for GSM PLMN connections ETSI ETSI TS 100 528 V7.0.1 (1999-07) 24 (GSM 03.10 version 7.0.1 Release 1998) MS BSS MSC/IWF R I/F RADIO I/F BSS-MSC I/F FEC RA1' RA1 FEC RA2 FEC FEC RA1' RA1 RA2 D S D D' RA1' FEC FEC RA1' RA1 RA2 RA2 RA1 D D' D S L2 D S* D' D RA1 RA2 RA2 RA1 RA1' FEC FEC RA1' L2 L2 L3 Model 2b Model 1b Model 3b Model 4b Transparent asynchronous data Transparent synchronous data char.async. L2R CO P (optionally including Data Com pression) Radio Link Protocol X.25 Packet Layer Protocol L2RBO P Radio Link Protocol LAPB LAPB char. D S D' D I/Fcct I/Fcct RA0 RA1' D S I/Fcct I/Fcct RA1' I/Fcct I/Fcct L L1 1 D S TE2 MT2 async RA0 RA2 RA1 S D RA2 RA1 S D Figure 6 (continued): Information transfer protocol models for GSM PLMN connections ETSI ETSI TS 100 528 V7.0.1 (1999-07) 25 (GSM 03.10 version 7.0.1 Release 1998) MS BSS MSC/IWF S I/F RADIO I/F BSS-MSC I/F FEC RA1' RA1 FEC RA2 FEC FEC RA1' RA1 RA2 FEC FEC Model 5 Model 4c Model 6a Model 6b RA1' I/Fcct I/Fcct RA1' D D L2 D' D RA1 RA2 LAPB D Radio Link Protocol L2RBOP X.25 Packet Layer Protocol LAPB D' 64 kbit/s L2 L1 L1 L3 FAX FA D S FA protocol RA2 RA1 FA T.30 R I/F S I/F FEC MPX MPX GSM 06-series CCITT A-LAW CCITT A-LAW A LAW A LAW SPEECH FEC MPX MPX GSC GSC A LAW GSC A LAW GSC MT0 SPEECH GSM 06-series CCITT A-LAW TE1 MT1 MT2 MT1 TE1 Figure 6 (continued): Information transfer protocol models for GSM PLMN connections ETSI ETSI TS 100 528 V7.0.1 (1999-07) 26 (GSM 03.10 version 7.0.1 Release 1998) R I/F D S Model 7 L2RBOP Radio Link Protocol I/Fcct I/Fcct FAX FA LAPB FA protocol L2 L2R RLP L2 RLP L2R FA T.30 D S MT2 RADIO I/F BSS-MSC I/F FOR FURTHER STUDY BSS MS MSC/IWF D' D RA1' FEC FEC RA1' RA1 RA2 RA2 RA1 D D' Figure 6 (continued): Information transfer protocol models for GSM PLMN connections ETSI ETSI TS 100 528 V7.0.1 (1999-07) 27 (GSM 03.10 version 7.0.1 Release 1998) MS BSS MSC/IWF asynch. LAPB L2 D S* L2 D status L2 L3 Model 4d X.25 Packet Layer Protocol L2RBOP Radio Link Protocol LAPB D S D' D D' D RA1 RA2 RA2 RA1 RA0 status D RA1 RA2 RA2 RA1 D S RA0 D D' D D' D S Model 3d characters asynch. L2R COP Radio Link Protocol char. (optionally including Data Compression) FEC FEC RA1' RA1 MUX MUX RA1 S/C S/C RA1' S/C S/C RA1 MUX MUX RA1 RA1' FEC FEC RA1' RA1 S I/F RADIO I/F BSS-MSC I/F RA0 RA2 status D Model 1d Transparent asynchronous data TE1 or MT1 RA2 RA1 RA1' S/C FEC RA1' RA1 FEC RA1 MUX RA0 MUX RA1 RA2 status D Model 2d Transparent synchronous data RA2 RA1 RA1' FEC RA1' RA1 FEC RA1 MUX S/C MUX S/C Model 2d Transparent synchronous data 48, 56, 64 kbit/s FEC FEC RA1’’ RA1 RA1' S/C RA1’ RA1 S/C RA1’’ status D RA1’’ adaptation is not applied to user rate 64 kbit/s S/C S D S D Figure 6 (continued): Information transfer protocol models for GSM PLMN connections ETSI ETSI TS 100 528 V7.0.1 (1999-07) 28 (GSM 03.10 version 7.0.1 Release 1998) MS BSS MSC/IWF R I/F RADIO I/F BSS-MSC I/F Model 1e Transparent asynchronous data I/Fcct I/Fcct RA0 D S TE2 MT2 RA0 RA1' RA1 FEC RA1 MUX S/C MUX D S D D' D D' D S Model 3e char.async. L2R COP (optionally including Data Compression) Radio Link Protocol char. I/Fcct I/Fcct async FEC FEC RA1' RA1 MUX MUX RA1 RA1' S/C S/C L2 D S* L2 L2 L3 Model 4e X.25 Packet Layer Protocol L2RBOP LAPB LAPB D S L L1 1 Radio Link Protocol D' D' D D S/C RA1 MUX MUX RA1 RA1' FEC FEC RA1' S/C Model 2e Transparent synchronous data I/Fcct RA1' RA1 FEC RA1 S/C MUX MUX Model 2e Transparent synchronous data 48, 56, and 64 kbit/s I/Fcct RA1' RA1 FEC D S S/C RA1' I/Fcct D S I/Fcct FEC S/C RA1' FEC RA1’’ S/C RA1’’ adaptation is not applicable to user rate 64 kbit/s. S/C RA1' FEC S D S D Figure 6 (continued): Information transfer protocol models for GSM PLMN connections ETSI ETSI TS 100 528 V7.0.1 (1999-07) 29 (GSM 03.10 version 7.0.1 Release 1998) MS BSS MSC/IWF S I/F RADIO I/F BSS-MSC I/F Model 4f D L2 LAPB D L2RBOP X.25 Packet Layer Protocol LAPB 64 kbit/s L2 L1 L1 L3 TE1 MT1 Radio Link Protocol Model 5b I/Fcct I/Fcct FAX FA D S FA protocol FA T.30 R I/F MT2 S/C D' D' D D MUX RA1 FEC FEC S/C L2 FEC RA1' RA1 FEC RA1 MUX MUX S/C RA1' RA1 RA1' MUX S/C RA1' Figure 6 (continued): Information transfer protocol models for GSM PLMN connections ETSI ETSI TS 100 528 V7.0.1 (1999-07) 30 (GSM 03.10 version 7.0.1 Release 1998) D R I/F D S Model 7b L2RBOP Radio Link Protocol I/Fcct I/Fcct FAX FA LAPB FA protocol L2 L2R RLP L2 RLP L2R FA T.30 S MT2 RADIO I/F BSS-MSC I/F FOR FURTHER STUDY BSS MS MSC/IWF D' D' D D MUX MUX RA1 FEC FEC S/C RA1' S/C RA1' RA1 Figure 6 (concluded): Information transfer protocol models for GSM PLMN connections Legend to Figure 6: FA = Fax Adaptor GSC = GSM Speech Codec FEC = Forward Error Correction MPX = Multiplex/Demultiplex MUX = Multiplex/Demultiplex S/C = Split/ Combine ETSI ETSI TS 100 528 V7.0.1 (1999-07) 31 (GSM 03.10 version 7.0.1 Release 1998) RA2 RA2 RA2 RA2 RA2 RA2 RA2 RA2 MS BSS MSC/IWF S I/F RADIO I/F BSS-MSC I/F RA0 RA1 RA2 RA2 RA1 RA1' FEC RA1' RAA’ FEC RA1 RA2 RA2 status D RA1 RA1' FEC FEC RA1' RAA’ status D L2 D S* RAA’ RA1' FEC FEC L2 RA1 RA2 RA2 RA1 D status L2 L3 Model 2a Model 1a Model 4a Transparent asynchronous data Transparent synchronous data X.25 Packet Layer Protocol L2RBOP Radio Link Protocol LAPB LAPB D S TE1 or MT1 RA0 status D RA1 RA2 RA2 RA1 D S RA0 FEC FEC RA1' RAA’ D S Model 3a characters asynch. L2R COP Radio Link Protocol char. asynch. (optionally including Data Compression) RAA’ RAA’’ RA0 RAA’ RAA’’ RAA’ RAA’ RAA’’ RAA’’ S D S D Figure 7: Information transfer protocol models for GSM PLMN connections using 14.4 channels ETSI ETSI TS 100 528 V7.0.1 (1999-07) 32 (GSM 03.10 version 7.0.1 Release 1998) RA2 RA2 RA2 RA2 RA2 RA2 RA2 RA2 MS BSS MSC/IWF R I/F RADIO I/F BSS-MSC I/F FEC RA1' RAA’ FEC FEC FEC RA1' RAA’ D S FEC FEC RA1' RAA’ D S L2 D S* RAA’ RA1' FEC FEC L2 L2 L3 Model 2b Model 1b Model 3b Model 4b Transparent asynchronous data Transparent synchronous data char.async. L2R COP (optionally including Data Compression) Radio Link Protocol X.25 Packet Layer Protocol L2RBOP Radio Link Protocol LAPB LAPB char. D S I/Fcct I/Fcct RA0 RA1' D S I/Fcct I/Fcct RA1' I/Fcct I/Fcct L L1 1 D S TE2 MT2 async RAA’ RAA’’ RA0 RAA’ RAA’’ RAA’ RAA’’ RAA’ RAA’’ S D S D Figure 7 (continued) : Information transfer protocol models for GSM PLMN connections using 14.4 channels ETSI ETSI TS 100 528 V7.0.1 (1999-07) 33 (GSM 03.10 version 7.0.1 Release 1998) RA2 RA2 RA2 RA2 MS BSS MSC/IWF S I/F RADIO I/F BSS-MSC I/F FEC RA1' RAA’ FEC FEC FEC RA1' RAA’ FEC FEC Model 5 Model 4c Model 6a Model 6b I/Fcct I/Fcct RA1' D L2 LAPB D Radio Link Protocol L2RBOP X.25 Packet Layer Protocol LAPB 64 kbit/s L2 L1 L1 L3 FAX FA D S FA protocol FA T.30 R I/F S I/F FEC MPX MPX GSM 06-series CCITT A-LAW CCITT A-LAW A LAW A LAW SPEECH FEC MPX MPX GSC GSC A LAW GSC A LAW GSC MT0 SPEECH GSM 06-series CCITT A-LAW TE1 MT1 MT2 MT1 TE1 RAA’ RAA’’ RAA’ RAA’’ Figure 7 (continued) : Information transfer protocol models for GSM PLMN connections using 14.4 channels ETSI ETSI TS 100 528 V7.0.1 (1999-07) 34 (GSM 03.10 version 7.0.1 Release 1998) RA2 RA2 RAA’’ RAA’ D R I/F D S Model 7a L2RBOP Radio Link Protocol I/Fcct I/Fcct FAX FA LAPB FA protocol L2 L2R RLP L2 RLP L2R FA T.30 S MT2 RADIO I/F BSS-MSC I/F FOR FURTHER STUDY BSS MS MSC/IWF D' D RAA’ FEC FEC RA1' Figure 7 (continued) : Information transfer protocol models for GSM PLMN connections using 14.4 channels ETSI ETSI TS 100 528 V7.0.1 (1999-07) 35 (GSM 03.10 version 7.0.1 Release 1998) MS BSS MSC/IWF asynch. LAPB L2 D S* L2 D status L2 L3 Model 4d X.25 Packet Layer Protocol L2RBOP Radio Link Protocol LAPB D S RA1 RA2 RA2 RA1 RA0 status D RA1 RA2 RA2 RA1 D S RA0 D S Model 3d characters asynch. L2R COP Radio Link Protocol char. (optionally including Data Compression) FEC FEC RA1' RAA’ S/C S/C S/C S/C MUX RAA’ RA1' FEC FEC RA1 S I/F RADIO I/F BSS-MSC I/F RA0 RA2 status D Model 1d Transparent asynchronous data TE1 or MT1 RA2 RA1 RA1' S/C FEC RA1' RAA’ FEC RA0 RA1 RA2 status D Model 2d Transparent synchronous data RA2 RA1 RA1' FEC RA1' RAA’ FEC S/C Model 2d Transparent synchronous data 64 kbit/s FEC FEC RA1 RA1' S/C RA1’ RA1 S/C D RAA’’ S/C RAA’ MUX MUX RAA’’ S/C RAA’ MUX MUX MUX RAA’’ RAA’ MUX RAA’’ RAA’ MUX S D S D Figure 7 (continued) : Information transfer protocol models for GSM PLMN connections using 14.4 channels ETSI ETSI TS 100 528 V7.0.1 (1999-07) 36 (GSM 03.10 version 7.0.1 Release 1998) MS BSS MSC/IWF R I/F RADIO I/F BSS-MSC I/F Model 1e Transparent asynchronous data I/Fcct I/Fcct RA0 D S TE2 MT2 RA0 FEC D S D S Model 3e char.async. L2R COP (optionally including Data Compression) Radio Link Protocol char. I/Fcct I/Fcct async FEC FEC RA1' RAA’ S/C S/C L2 D S* L2 L2 L3 Model 4e X.25 Packet Layer Protocol L2RBOP LAPB LAPB D S L L1 1 Radio Link Protocol S/C RAA’ RA1' FEC FEC S/C Model 2e Transparent synchronous data I/Fcct RA1' RAA’ FEC Model 2e Transparent synchronous data 64 kbit/s I/Fcct RA1' RA1 FEC D S S/C RA1' I/Fcct D S I/Fcct FEC S/C RA1' FEC S/C S/C RA1' FEC RAA’’ S/C RAA’ MUX MUX RAA’’ S/C RAA’ MUX MUX MUX RAA’’ RAA’ MUX MUX RAA’’ RAA’ MUX RA1’ RAA’ S D S D Figure 7 (continued) : Information transfer protocol models for GSM PLMN connections using 14.4 channels ETSI ETSI TS 100 528 V7.0.1 (1999-07) 37 (GSM 03.10 version 7.0.1 Release 1998) MS BSS MSC/IWF S I/F RADIO I/F BSS-MSC I/F Model 4f D L2 D L2RBOP X.25 Packet Layer Protocol LAPB 64 kbit/s L2 L1 L1 L3 TE1 MT1 Radio Link Protocol Model 5b I/Fcct I/Fcct FAX FA D S FA protocol FA T.30 R I/F MT2 RAA’ FEC FEC S/C L2 FEC RA1' RAA’ FEC S/C RA1' S/C RA1' RAA’’ S/C RAA’ MUX MUX MUX RAA’’ RAA’ MUX Figure 7 (continued) : Information transfer protocol models for GSM PLMN connections using 14.4 channels ETSI ETSI TS 100 528 V7.0.1 (1999-07) 38 (GSM 03.10 version 7.0.1 Release 1998) MUX RAA’’ RAA’ MUX D R I/F D S Model 7b L2RBOP Radio Link Protocol I/Fcct I/Fcct FAX FA LAPB FA protocol L2 L2R RLP L2 RLP L2R FA T.30 S MT2 RADIO I/F BSS-MSC I/F FOR FURTHER STUDY BSS MS MSC/IWF D' D RAA’ FEC FEC S/C RA1' S/C Figure 7 (concluded) : Information transfer protocol models for GSM PLMN connections using 14.4 channels Legend to Figure 7: FA = Fax Adaptor GSC = GSM Speech Codec FEC = Forward Error Correction MPX = Multiplex/Demultiplex MUX = Multiplex/Demultiplex S/C = Split/ Combine ETSI ETSI TS 100 528 V7.0.1 (1999-07) 39 (GSM 03.10 version 7.0.1 Release 1998) 7 Relationship between Telecommunication services and connection types
|
2c9d130f4599201b7ff29ffb2e9ae502
|
100 528
|
7.1 General
|
Given a request for a telecommunication service at the initiation of a call, the GSM PLMN must establish a connection of a connection type that supports the attributes of the service requested. This establishment of a connection is effected at the time of call set up. It should be noted that GSM PLMN connection types represent the technical capabilities of a GSM PLMN and provide a basis for the definition of performance and interworking with other networks. Telecommunication services supported by a GSM PLMN are the packages offered to customers and the definition of their attributes is the means to standardize the service offerings in all GSM PLMNs. Quality of service and commercial attributes are relevant to telecommunication services whereas connection types are characterized by network performance, network operations and maintenance attributes.
|
2c9d130f4599201b7ff29ffb2e9ae502
|
100 528
|
7.2 Relationship between Bearer services and connection types
|
Table 5 shows the relationship between Bearer services and GSM PLMN connection types. In table 5, the connection elements for each connection type related to a Bearer service are shown. Dominant attributes of the connection elements, such as information transfer mode, information transfer rate, information transfer capability and structure are indicated. The type of radio traffic channel used is also shown (half rate and full rate). In the multislot cases the minimum number of timeslots per connection (n) is 1.
|
2c9d130f4599201b7ff29ffb2e9ae502
|
100 528
|
7.3 Relationship between Teleservices and connection types
|
Table 6 shows the relationship between teleservices and connection type elements, for those teleservices having a GSM PLMN connection type which does not correspond to the GSM PLMN connection type of a bearer service. As in table 5/GSM 03.10, dominant attributes of the connection elements and the type of radio traffic channel are shown. In the multislot cases the minimum number of timeslots per connection (n) is 1.
|
2c9d130f4599201b7ff29ffb2e9ae502
|
100 528
|
7.4 Network capability to support in-call modification
|
Specifications GSM 02.02 and 02.03 identify a particular need for a GSM PLMN to support the Alternate speech/data (3.1 kHz audio ex PLMN), Alternate speech and group 3 facsimile, and Speech followed by data (3.1 kHz audio). These services allow the use of in-call modification to change the mode of service. The network capability to support in- call modification is described in GSM 04.08. An in-call modification of the service mode is not possible for other services.
|
2c9d130f4599201b7ff29ffb2e9ae502
|
100 528
|
7.5 Network capability to support channel mode modification
|
Specification GSM 03.45 (Technical Realization of the Group 3 Facsimile Teleservice) identifies a need for a GSM PLMN to support channel mode modification within the facsimile phase of the alternate speech and facsimile group 3 service. The network capability to support channel modification is described in GSM 04.08. Channel mode modification is not possible for other services. A channel mode modification results in a change of connection element over the radio interface with resultant change in access at the mobile station. ETSI ETSI TS 100 528 V7.0.1 (1999-07) 40 (GSM 03.10 version 7.0.1 Release 1998) Table 5: Relationship between Bearer services and GSM PLMN Connection elements Connection description Bearer service user data rate Radio interface connection element Intermediate rate at the BSS- MSC interface BSS-MSC connection element Protocol model in figure 6 or 7 Circuit mode unstructured with unrestricted digital capability transparent. Data circuit duplex async n × 4 800 (n ≤ 4) or n × 9 600 bit/s (n ≤ 4). Data circuit duplex sync n × 4 800 (n ≤ 4) or n × 9 600 bit/s (n ≤ 5) or n × 1 1200 bit/s (n = 5 or 6). cct mode unstructured unrestricted n × 6 kbit/s (n ≤ 4) or n × 12 kbit/s (n ≤ 6) on n full rate channels. 8 or 16 kbit/s per TCH/F. For data connections using 5 or 6 TCH/Fs no intermediaterate( s) . cct mode unstructured unrestricted 64 kbit/s. Fig 6 :1 d, 1 e, 2 d, 2 e Data circuit duplex async n × 14 400 bit/s ( n ≤ 3). Data circuit duplex sync n × 14 400 bit/s (n ≤ 5) cct mode unstructured unrestricted n x 14.5 kbit/s (n ≤ 5) on n full rate channels 16 kbit/s per TCH/F. Fig 7 : 1 d, 1 e, 2 d, 2 e Data circuit duplex async 14 400 bit/s Data circuit duplex sync 14 400 bit/s cct mode unstructured unrestricted 14.5 kbit/s on full rate Channel 16 kbit/s cct mode unstructured unrestricted 64 kbit/s. Fig 7 : 1 a, 1 b 2 a, 2 b Data circuit duplex async 9 600 bit/s. Data circuit duplex sync 9 600 bit/s. cct mode unstructured unrestricted 12 kbit/s on full rate channel. 16 kbit/s. cct mode unstructured unrestricted 64 kbits/s. Fig 6 :1 a, 1 b Fig 6 2 a, 2 b Data circuit duplex async 4 800 bit/s. Data circuit duplex sync 4 800 bit/s. cct mode unstructured unrestricted 6 kbit/s on full rate channel and half rate channel. 8 kbit/s. cct mode unstructured unrestricted 64 kbits/s. Fig 6 1 a, 1 b Fig 6 2 a, 2 b Data circuit duplex async 300. Data circuit duplex async 1 200. Data circuit duplex async 1 200/75. Data circuit duplex async 2 400. Data circuit duplex sync 1 200. Data circuit duplex sync 2 400. cct mode unstructured unrestricted 3.6 kbit/s on full rate channel and half rate channel. 8 kbit/s. cct mode unstructured unrestricted 64 kbits/s. Fig 6 : 1 a, 1 b Fig 6 1 a, 1 b Fig 6 1 a, 1 b Fig 6 1 a, 1 b Fig 6 2 a, 2 b Fig 6 2 a, 2 b Circuit mode unstructured with unrestricted digital capability non transparent. Data circuit duplex async n × 4 800 (n ≤ 4) or n × 9 600 bit/s (n ≤ 4). cct mode SDU unrestricted n × 6 kbit/s (n ≤ 4) or n × 12 kbit/s (n ≤ 4) on full rate channels. 8 or 16 kbit/s per TCH/F. cct mode unstructured unrestricted 64 kbit/s. Fig 6 3 d, 3 e Data circuit duplex async n × 14 400 bit/s (n ≤ 4). cct mode SDU unrestricted n × 14.5 kbit/s (n ≤ 4) on full rate channels. 16 kbit/s Fig 7 : 3 d, 3e Data circuit duplex async 14 400 bit/s cct mode SDUunrestricted 14.5 kbit/s on full rate channel 16 kbit/s Fig 7 : 3 a, 3 b Data circuit duplex async 9 600 bit/s. cct mode SDU unrestricted 12 kbit/s on full rate channel. 16 kbit/s. cct mode unstructured unrestricted 64 kbits/s. Fig 6 : 3 a, 3 b Data circuit duplex async 4 800 bit/s. cct mode SDU unrestricted full rate channel, 12 kbit/s or half rate channel, 6 kbit/s. 16 kbit/s FR 8 kbit/s HR. cct mode unstructured unrestricted 64 kbits/s. Fig 6 : 3 a, 3 b (continued) ETSI ETSI TS 100 528 V7.0.1 (1999-07) 41 (GSM 03.10 version 7.0.1 Release 1998) Table 5 (continued): Relationship between Bearer services and GSM PLMN Connection elements Connection description Bearer service user data rate Radio interface connection element Intermediate rate at the BSS- MSC interface BSS-MSC connection element Protocol model in figure 6 or 7 Data circuit duplex async 300. Data circuit duplex async 1 200. Data circuit duplex async 1 200/75. Data circuit duplex async 2 400. cct mode SDU unrestricted full rate channel, 12 kbit/s or half rate channel, 6 kbit/s. 16 kbit/s FR 8 kbit/s HR. cct mode unstructured unrestricted 64 kbits/s. Fig 6: 3 a, 3 b Fig 6 : 3 a, 3 b Fig 6 3 a, 3 b Fig 6 3 a, 3 b Circuit mode unstructured with 3.1 kHz audio ex PLMN transparent. Data circuit duplex async n × 4 800 bit/s (n ≤ 4) or n × 9 600 bit/s (n ≤ 3). Data circuit duplex sync n × 4 800 bit/s (n ≤ 4) or n × 9 600 bit/s (n ≤ 3). cct mode unstructured unrestricted n × 6 kbit/s (n ≤ 4) or n × 12 kbit/s (n ≤ 3) on n full rate channels. 8 or 16 kbit/s TCH/F. cct mode unstructured unrestricted 64 kbit/s. Fig 6 : 1 d, 1 e, 2 d, 2 e Data circuit duplex async n × 14 400 bit/s (n ≤ 2). Data circuit duplex sync n × 14 400 bit/s (n ≤ 2) cct mode unstructured unrestricted x 14.5 kbit/s (n ≤ 2) on n full rate channels 16 kbit/s per TCH/F Fig 7 : 1 d, 1 e, 2 d, 2e Data circuit duplex asynch 14 400 bit/s synch 14 400 bit/s cct mode unstructured unrestricted 14.5 kbit/s on full rate channels 16 kbit/s Fig 7 : 1 a, 1 b for async Fig 7 2 a 2 b for synch Data circuit duplex async 9.6 kbit/s sync 9.6 kbit/s. cct mode unstructured unrestricted 12 kbit/s full rate channel. 16 kbit/s. Data circuit duplex async 4.8 kbit/s sync 4.8 kbit/s. cct mode unstructured unrestricted 6 kbit/s full and half rate channel. 8 kbit/s. Fig 6 : 1 a, 1 b for asynch. Fig 6 : 2 a, 2 b for synch. Data circuit duplex async ≤ 2 400 sync ≤ 2 400. cct mode unstructured unrestricted 3.6 kbit/s full and half rate channel. 16 kbit/s. Circuit mode unstructured with 3.1 kHz audio ex PLMN non transparent. Data circuit duplex async n × 4 800 (n ≤ 4) or n × 9 600 (n ≤ 4) bit/s. Data circuit duplex sync n × 4 800 (n ≤ 4) or n × 9 600 bit/s (n ≤ 4). cct mode SDU unrestricted n × 6 kbit/s (n ≤ 4) or n × 12 kbit/s (n ≤ 4) on full rate channels. 8 or 16 kbit/s per TCH/F. cct mode unstructured unrestricted 64 kbits/s. Fig 6 : 3 d, 3 e for async. Fig 6 : 4 d, 4 e, 4 f for sync. Data circuit duplex async n × 14 400 bit/s (n ≤ 4). Data circuit duplex sync n × 14 400 bit/s (n ≤ 4) cct mode SDU unrestricted n x 14.5 kbit/s (n ≤ 4) on n full rate channels 16 kbit/s per TCH/F Fig 7 : 3 d, 3 e for asynch Fig 7 : 4 d, 4 e 4 f for synch (continued) ETSI ETSI TS 100 528 V7.0.1 (1999-07) 42 (GSM 03.10 version 7.0.1 Release 1998) Table 5 (continued): Relationship between Bearer services and GSM PLMN Connection elements Connection description Bearer service user data rate Radio interface connection element Intermediate rate at the BSS- MSC interface BSS-MSC connection element Protocol model in figure 6 or 7 Data circuit duplex asynch 14 400 bit/s synch 14 400 bit/s cct mode SDU unrestricted 14.5 kbit/s full rate channel 16 kbit/s Fig 7 : 3a, 3b for asynch Fig 7 : 4 a, 4 b, 4 c for synch Data circuit duplex async 9.6 kbit/s sync 9.6 kbit/s. cct mode SDU unrestricted 12 kbit/s full rate channel. 16 kbit/s. Data circuit duplex async 4.8 kbit/s sync 4.8 kbit/s. cct mode SDU unrestricted half rate channel, 6 kbit/s or full rate channel, 12 kbit/s. 16 kbit/s FR 8 kbit/s HR. cct mode unstructured unrestricted 64 kbit/s. Fig 6 : 3 a, 3 b for asynch. Fig 6 : 4 a, 4 b, 4 c for synch. Data circuit duplex async ≤ 2 400 sync ≤ 2 400. cct mode SDU unrestricted half rate channel, 6 kbit/s or full rate channel, 12 kbit/s. Pad access transparent. PAD access circuit async 300. PAD access circuit async 1 200. PAD access circuit async 1 200/75. PAD access circuit async 2 400. cct mode unstructured unrestricted 3.6 kbit/s on full rate channel and half rate channel. 8 kbit/s. cct mode unstructured unrestricted 64 kbit/s. Fig 6 : 1 a, 1 b Fig 6 : 1 a, 1 b Fig 6 : 1 a, 1 b Fig 6 : 1 a, 1 b PAD access circuit async 4 800. cct mode unstructured unrestricted 6 kbit/s on half rate channel and full rate channel. Fig 6 : 1 a, 1 b PAD access circuit async 9 600. cct mode unstructured unrestricted 12 kbit/s on full rate channel. 16 kbit/s. Fig 6 :1 a, 1 b PAD access circuit asynch 14 400 bit/s cct mode unstructured unrestricted 14.5 kbit/s on full rate channel 16 kbit/s Fig 7 : 1 a, 1 b PAD access circuit async n × 4 800 (n ≤ 4) or n × 9 600 bit/s (n ≤ 4). cct mode unstructured unrestricted n × 6 kbit/s (n ≤ 4) or n × 12 kbit/s (n ≤ 4) on n full rate channels. 8 or 16 kbit/s per TCH/F. Fig 6 : 1 d, 1 e PAD access circuit async n × 14 400 bit/s (n ≤ 3). cct mode unstructured unrestricted n × 14.5 kbit/s (n ≤ 3) on n full rate channels. 16 kbit/s per TCH Fig 7 : 1 d, 1 e Pad access non transparent. PAD access circuit async 300. PAD access circuit async 1 200. PAD access circuit async 1 200/75. PAD access circuit async 2 400. cct mode SDU unrestricted half rate channel, 6 kbit/s or full rate channel, 12 kbit/s. 16 kbit/s FR 8 kbit/s HR. cct mode unstructured unrestricted 64 kbit/s. Fig 6 : 3 a, 3 b Fig 6 : 3 a, 3 b Fig 6 : 3 a, 3 b Fig 6: 3 a, 3 b PAD access circuit async 4 800. cct mode SDU unrestricted half rate channel, 6 kbit/s or full rate channel, 12 kbit/s. Fig 6 : 3 a, 3 b PAD access circuit async 14 400 bit/s cct mode SDU unrestricted 14.5 kbit/s on full rate channel 16 kbit/s Fig 7 : 3 a, 3 b PAD access circuit async 9 600. cct mode SDU unrestricted 12 kbit/s on full rate channel. 16 kbit/s. Fig 6 : 3 a, 3 b PAD access circuit async n × 4 800 (n ≤ 4) or n × 9 600 bit/s (n ≤ 4). cct mode SDU unrestricted n × 6 kbit/s (n ≤ 4) or n × 12 kbit/s (n ≤ 4) on full rate channels. 8 or 16 kbit/s per TCH/F. Fig 6 : 3 d, 3 e (continued) ETSI ETSI TS 100 528 V7.0.1 (1999-07) 43 (GSM 03.10 version 7.0.1 Release 1998) Table 5 (continued): Relationship between Bearer services and GSM PLMN Connection elements Connection description Bearer service user data rate Radio interface connection element Intermediate rate at the BSS- MSC interface BSS-MSC connection element Protocol model in figure 6 or 7 PAD access circuit async n × 14 400 bit/s (n ≤ 4). cct mode SDU unrestricted n × 14.5 kbit/s (n ≤ 4) on full rate channels. 16 kbit/s per TCH/F. Fig 7 : 3 d, 3 e Packet services, dedicated access, non transparent. Data packet duplex sync 2 400. cct mode SDU unrestricted half rate channel, 6 kbit/s or full rate channel, 12 kbit/s. 16 kbit/s FR 8 kbit/s HR. cct mode unstructured unrestricted 64 kbit/s. Fig 6 : 4 a, 4 b, 4 c Data packet duplex sync 4 800. cct mode SDU unrestricted half rate channel, 6 kbit/s or full rate channel, 12 kbit/s. Fig 6 : 4 a, 4 b, 4 c Data packet duplex sync 9 600. cct mode SDU unrestricted 12 kbit/s on full rate channel. 16 kbit/s. Fig 6 : 4 a, 4 b, 4 c Data packet duplex synch 14 400 bit/s cct mode SDU unrestricted 14.5 kbit/s on full rate channel 16 kbit/s. Fig 7 : 4 a, 4 b, 4 c Data packet duplex sync n × 4 800 (n ≤ 4) or n × 9 600 bit/s (n ≤ 4). cct mode SDU unrestricted n × 6 kbit/s (n ≤ 4) or n × 12 kbit/s (n ≤ 4) on full rate channels. 8 or 16 kbit/s per TCH/F. Fig 6 : 4 d, 4 e, 4 f Data packet duplex sync n × 14 400 bit/s (n ≤ 4). cct mode SDU unrestricted n × 14.5 kbit/s (n ≤ 4) on full rate channels. 16 kbit/s per TCH/F Fig 7 : 4 d, 4 e, 4 f Packet services basic access transparent. Data circuit duplex sync n × 4 800 (n ≤ 4) or n × 9 600 bit/s (n ≤ 5) or n × 11200 bit/s (n = 5 or 6). cct mode unstructured unrestricted n × 6 kbit/s (n ≤ 4) or n × 12 kbit/s (n ≤ 6) on n full rate channels. 8 or 16 kbit/s per TCH/F. For data connections using 5 or 6 TCH/Fs no intermediate rate(s). cct mode unstructured unrestricted 64 kbit/s. Fig 6 : 2 d, 2 e Data circuit duplex sync n × 14 400 bit/s (n ≤ 5) cct mode unstructured unrestricted n × 14.5 kbit/s (n ≤ 5) on n full rate channels. 16 kbit/s per TCH/F Fig 7 : 2 d, 2 e Data circuit duplex synch 14 400 bit/s cct mode unstructured unrestricted 14.5 kbit/s on full rate channel. 16 kbit/s. cct mode unstructured unrestricted 64 kbit/s. Fig 7 : 2 a, 2 b Data circuit duplex sync 9 600 bit/s. cct mode unstructured unrestricted 12 kbit/s on full rate channel. 16 kbit/s. cct mode unstructured unrestricted 64 kbit/s. Fig 6 : 2 a, 2 b Data circuit duplex sync 4 800 bit/s. cct mode unstructured unrestricted 6 kbit/s on full rate channel and half rate channel. 8 kbit/s. cct mode unstructured unrestricted 64 kbit/s. Fig 6 : 2 a, 2 b Data circuit duplex sync 2 400 bit/s. cct mode unstructured unrestricted 3.6 kbit/s on full rate channel and half rate channel. 8 kbit/s. cct mode unstructured unrestricted 64 kbit/s. Fig 6 : 2 a, 2 b Packet services basic access non transparent. Data circuit duplex sync n × 4 800 (n ≤4 ) or n × 9 600 bit/s (n ≤ 4). cct mode SDU unrestricted n × 6 kbit/s (n ≤ 4) or n × 12 kbit/s (n ≤ 4) on full rate channels. 8 or 16 kbit/s per TCH/F. cct mode unstructured unrestricted 64 kbits/s. Fig 6 : 4 d, 4 e, 4 f Data circuit duplex sync n × 14 400 bit/s (n ≤ 4). cct mode SDU unrestricted n × 14.5 kbit/s (n ≤ 4) on full rate channels 16 kbit/s per TCH/F Fig 7 : 4 d, 4 e, 4 f Data circuit duplex synch 14 400 bit/s cct mode SDU unrestricted 14.5 kbit/s on full rate channel 16 kbit/s Fig 7 : 4 a, 4 b, 4 c Data circuit duplex sync 9 600 bit/s. cct mode SDU unrestricted 12 kbit/s on full rate channel. 16 kbit/s. cct mode unstructured unrestricted 64 kbit/s. Fig 6 : 4 a, 4 b, 4 c (continued) ETSI ETSI TS 100 528 V7.0.1 (1999-07) 44 (GSM 03.10 version 7.0.1 Release 1998) Table 5 (continued): Relationship between Bearer services and GSM PLMN Connection elements Connection description Bearer service user data rate Radio interface connection element Intermediate rate at the BSS- MSC interface BSS-MSC connection element Protocol model in figure 6 or 7 Data circuit duplex sync 4 800 bit/s. cct mode SDU unrestricted full rate channel, 12 kbit/s or half rate channel, 6 kbit/s. 16 kbit/s FR 8 kbit/s HR. cct mode unstructured unrestricted 64 kbit/s. 4 a,b,c Data circuit duplex sync 2 400 bit/s. cct mode SDU unrestricted full rate channel, 12 kbit/s or half rate channel, 6 kbit/s. 16 kbit/s FR 8 kbit/s HR. cct mode unstructured unrestricted 64 kbit/s. 4 a,b,c Circuit mode unstructured with alternate speech and 3.1 Khz audio ex PLMN transparent. Alternate speech and data duplex async n × 4 800 bit/s (n ≤ 4) or n × 9 600 bit/s (n ≤ 3). Alternate speech and data duplex sync n × 4 800 bit/s (n ≤ 4) or n × 9 600 bit/s (n ≤ 3). cct mode speech alternating with cct mode unstructured unrestricted n × 6 kbit/s (n ≤ 4) or n × 12 kbit/s (n ≤ 3) on n full rate channels. Speech NA 8 or 16 kbit/s per TCH/F. cct mode alternate speech and unstructured unrestricted 64 kbit/s. Fig 6 :, 6 b, 1 d, 1 e, 2 d, 2 e Alternate speech and data duplex async n × 14 400 bit/s (n ≤ 2). Alternate speech and data duplex sync n × 14 400 bit/s (n ≤ 2). cct mode speech alternating with cct mode unstructured unrestricted n × 14.5 kbit/s (n ≤ 2) on n full rate channels. Speech NA 16 kbit/s per TCH/F. cct mode alternate speech and unstructured unrestricted 64 kbit/s Fig 7 : 6 b and 1d, 1e, 2d, 2e Alternate speech and data duplex async 14 400 cct mode speech alternating with cct mode unstructured unrestricted 14.5 kbit/s on full rate channel. Speech NA 16 kbit/s cct mode alternate speech and unstructured unrestricted 64 kbit/s Fig 7 : 6 b and 1 a, 1 b Alternate speech and data duplex sync 14 400 cct mode speech alternating with cct mode unstructured unrestricted 14.5 kbit/s on full rate channel. Speech NA 16 kbit/s. cct mode alternate speech and unstructured unrestricted 64 kbit/s. Fig 7 : 6 b and 2 a, 2 b Alternate speech and data duplex async 9 600. cct mode speech alternating with cct mode unstructured unrestricted 12 kbit/s on full rate channel. Speech NA 16 kbit/s. cct mode alternate speech and unstructured unrestricted 64 kbit/s. Fig 6 : 6b and 1 a, 1 b Alternate speech and data duplex sync 9 600. Fig 6 : 6b and 2 a, 2 b Alternate speech and data duplex async 4 800. cct mode speech alternating with cct mode unstructured unrestricted 6 kbit/s Speech NA 8 kbit/s. cct mode alternate speech and unstructured unrestricted 64 kbit/s. Fig 6 : 6 b and 1 a, 1 b Alternate speech and data duplex sync 4 800. on full rate channel or half rate channel. Fig 6 : 6 b and 2 a, 2 b Alternate speech and data duplex async ≤ 2 400. cct mode speech alternating with cct mode unstructured unrestricted 3.6 kbit/s. Speech NA 8 kbit/s. cct mode alternate speech and unstructured unrestricted 64 kbit/s. Fig 6 : 6b and 3 a, 3 b Alternate speech and data duplex sync ≤ 2 400. on full rate channel or half rate channel. Fig 6 : 6 b and 4 a, 4 b, 4 c Circuit mode unstructured with alternate speech and 3.1 Khz audio ex PLMN non transparent. Alternate speech and data duplex async n × 4 800 (n ≤ 4) or n × 9 600 (n ≤ 4) bit/s. cct mode speech alternating with cct mode SDU unrestricted n × 6 kbit/s (n ≤ 4) or n × 12 kbit/s (n ≤ 4) on full rate channels. Speech NA 8 or 16 kbit/s per TCH/F. cct mode alternate speech and unstructured unrestricted 64 kbit/s. Fig 6 : 6b and 3d, 3e (continued) ETSI ETSI TS 100 528 V7.0.1 (1999-07) 45 (GSM 03.10 version 7.0.1 Release 1998) Table 5 (continued): Relationship between Bearer services and GSM PLMN Connection elements Connection description Bearer service user data rate Radio interface connection element Intermediate rate at the BSS- MSC interface BSS-MSC connection element Protocol model in figure 6 or 7 Alternate speech and data duplex async n × 14 400 (n ≤ 4) bit/s. cct mode speech alternating with cct mode SDU unrestricted n × 14.5 kbit/s (n ≤ 4) on full rate channels Speech NA 16 kbit/s per TCH/F cct mode alternate speech and unstructured unrestricted 64 kbit/s. Fig 7 : 6 b and 3 d, 3 e Alternate speech and data duplex async 14 400. cct mode speech alternating with cct mode SDU unrestricted 14.5 kbit/s on full rate channel Speech NA 16 kbit/s. cct mode alternate speech and unstructured unrestricted 64 kbit/s. Fig 7 : 6 b and 3a, 3b Alternate speech and data duplex async 9 600. cct mode speech alternating with cct mode SDU unrestricted 12 kbit/s on full rate channel. Speech NA 16 kbit/s. cct mode alternate speech and unstructured unrestricted 64 kbit/s. Fig 6 6 b and 3 a, 3 b Alternate speech and data duplex async 4 800. cct mode speech alternating with cct mode SDU unrestricted half rate channel, 6 kbit/s or full rate channel, 12 kbit/s. Speech NA 16 kbit/s FR 8 kbit/s HR. cct mode alternate speech and unstructured unrestricted 64 kbit/s. Fig 6 : 6 b and 3 a, 3 b Alternate speech and data duplex async ≤ 2 400. cct mode speech alternating with cct mode SDU unrestricted full rate channel, 12 kbit/s or half rate channel, 6 kbit/s. Speech NA 16 kbit/s FR 8 kbit/s HR. cct mode alternate speech and unstructured unrestricted 64 kbit/s. Fig 6 : 6 b and 3 a, 3 b Circuit mode unstructured with speech followed by 3.1 Khz audio ex PLMN transparent. Speech followed by data duplex async n × 4 800 bit/s (n ≤ 4) or n × 9 600 bit/s (n ≤ 3). Speech followed by data duplex sync n × 4 800 bit/s (n ≤ 4) or n × 9 600 bit/s (n ≤ 3). cct mode speech followed by cct mode unstructured unrestricted n × 6 kbit/s (n ≤ 4) or n × 12 kbit/s (n ≤ 3) on n full rate channels. Speech NA 8 or 16 kbit/s per TCH/F. cct mode speech followed by unstructured unrestricted 64 kbit/s. Fig 6 : 6 a 6 b then1 e or 2 e Speech followed by data duplex async n × 14 400 bit/s (n ≤ 2). Speech followed by data duplex sync n × 14 400 bit/s (n ≤ 2). cct mode speech followed by cct mode unstructured unrestricted n × 14.5 kbit/s (n ≤ 2) on n full rate channels. Speech NA 16 kbit/s per TCH/F. Fig 7 : 6 a or 6 b then 1 e or 2 e Speech followed by 14 400 bit/s data duplex async cct mode speech followed by cct mode unstructured unrestricted 14.5 kbit/s on full rate channel Speech NA 16 kbit/s. cct mode speech followed by cct mode unstructured unrestricted 64 kbit/s. Fig 7 : 6 a or 6 b then 1 b Speech followed by 14 400 bit/s data duplex sync cct mode speech followed by cct mode unstructured unrestricted 14.5 kbit/s on full rate channel Speech NA 16 kbit/s. cct mode speech followed by cct mode unstructured unrestricted 64 kbit/s. Fig 7 : 6 a or 6 b then 2 b Speech followed by 9.6 kbit/s data duplex async. cct mode speech followed by cct mode unstructured unrestricted 12 kbit/s on full rate channel. Speech NA 16 kbit/s. cct mode speech followed by cct mode unstructured unrestricted 64 kbit/s. Fig 6 : 6a or 6b then 1 b Speech followed by 9.6 kbit/s data duplex sync. Fig 6: 6a or 6b then 2b Speech followed by 4.8 kbit/s data duplex async. cct mode speech followed by cct mode unstructured unrestricted 6 kbit/s on full rate and half rate channel. Speech NA 8 kbit/s. cct mode speech followed by cct mode unstructured unrestricted 64 kbit/s. Fig 6 : 6a or 6b then 1b (continued) ETSI ETSI TS 100 528 V7.0.1 (1999-07) 46 (GSM 03.10 version 7.0.1 Release 1998) Table 5 (concluded): Relationship between Bearer services and GSM PLMN Connection elements Connection description Bearer service user data rate Radio interface connection element Intermediate rate at the BSS- MSC interface BSS-MSC connection element Protocol model in figure 6 or 7 Speech followed by 4.8 kbit/s data duplex sync. Fig 6 : 6a or 6b then 2b Speech followed by ≤ 2.4 kbit/s data duplex async. cct mode speech followed by cct mode unstructured unrestricted 3.6 kbit/s on full rate and half rate channel. Speech NA 8 kbit/s. cct mode speech followed by cct mode unstructured unrestricted 64 kbit/s. Fig 6 : 6a or 6b then 1b Speech followed by ≤ 2.4 kbit/s data duplex sync. Fig 6 : 6a or 6b then 2b Circuit mode unstructured with speech followed by 3.1 Khz audio ex PLMN non transparent. Speech followed by data duplex async n × 4 800 (n ≤ 4) or n × 9 600 (n ≤ 4) bit/s. cct mode speech followed by cct mode SDU unrestricted n × 6 kbit/s (n ≤ 4) or n × 12 kbit/s (n ≤ 4) on full rate channels. Speech NA 8 or 16 kbit/s per TCH/F. cct mode speech followed by unstructured unrestricted 64 kbit/s. Fig 6 : 6a or 6b then3e Speech followed by data duplex async n × 14 400 bit/s (n ≤ 4). cct mode speech followed by cct mode SDU unrestricted n × 14.5 kbit/s (n ≤ 4) on n full rate channels. Speech NA 16 kbit/s per TCH/F. Fig 7 : 6 a or 6 b then 3 e Speech followed by 9.6 kbit/s data duplex async. cct mode speech followed by cct mode SDU unrestricted 12 kbit/s on full rate and half rate channel. Speech NA 16 kbit/s. cct mode speech followed by cct mode unstructured unrestricted 64 kbit/s. Fig 6 : 6a or 6b then 3b Speech followed by 14.4 kbit/s data duplex async. cct mode speech followed by cct mode SDU unrestricted 14.5 kbit/s on full rate channel. Speech NA 16 kbit/s. cct mode speech followed by cct mode unstructured unrestricted 64 kbit/s. Fig 7 : 6a or 6b then 3b Speech followed by 4.8 kbit/s data duplex async. cct mode speech followed by cct mode SDU unrestricted half rate channel, 6 kbit/s or full rate channel, 12 kbit/s. Speech NA 8 kbit/s HR 16 kbit/s FR. cct mode speech followed by cct mode unstructured unrestricted 64 kbit/s. Fig 6 : 6a or 6b then 3b Speech followed by ≤ 2.4 kbit/s data duplex async. cct mode speech followed by cct mode SDU unrestricted half rate channel, 6 kbit/s or full rate channel, 12 kbit/s. Speech NA 8 kbit/s 16 kbit/s FR. cct mode speech followed by cct mode unstructured unrestricted 64 kbit/s. Fig 6 : 6a or 6b then 3b ETSI ETSI TS 100 528 V7.0.1 (1999-07) 47 (GSM 03.10 version 7.0.1 Release 1998) Table 6: Relationship between Teleservices and GSM PLMN connection types Teleservice in GSM PLMN Access at mobile station Radio interface connection element Intermediate rate at the BSS-MSC interface BSS-MSC connection element Protocol model in figure 6 or 7 Telephony. cct mode speech. NA. cct mode structured 64 kbit/s speech. Fig 6 : 6 a or 6 b Emergency calls. cct mode speech. NA. cct mode structured 64 kbit/s speech. Fig 6 : 6 a or 6 b Alternate Speech/ Facsimile Group 3. Data cct duplex synchronous access alternate speech/ group 3 fax. cct mode speech alternating with unstructured unrestricted 3.6 or 6 or 12 kbit/s or n × 6 kbit/s (n ≤ 3) or n × 12 kbit/s (n ≤ 2) on FR transparent. Speech NA 8 or 16 kbit/s per TCH/F. cct mode structured 64 kbit/s alternate speech/unrestricted. Fig 6 : 5, 5b and 6 a or 6 b cct mode speech alternating with unstructured unrestricted 14.5 kbit/s or n × 14.5 kbit/s (n ≤ 2) on FR transparent Speech NA 16 kbit/s per TCH/F. Fig 7 : 5 and 5 b and 6 a or 6 b Automatic Facsimile Group 3. Data cct duplex synchronous access group 3 fax. cct mode unstructured unrestricted 3.6 or 6 or 12 kbit/s or n × 6 kbit/s (n ≤ 3) or n × 12 kbit/s (n ≤ 2) on FR transparent. 8 or 16 kbit/s per TCH/F. cct mode structured 64 kbit/s unrestricted. Fig 6 : 5, 5b cct mode unstructured unrestricted 14.5 kbit/s or n × 14.5 kbit/s (n ≤ 2) on FR transparent 16 kbit/s per TCH/F. Alternate speech/ Facsimile Group 3. Data cct duplex synchronous access alternate speech/ group 3 fax. cct mode speech alternating with SDU unrestricted 6 or 12 kbit/s or n × 6 kbit/s (n ≤ 3) or n × 12 kbit/s (n ≤ 2) on FR non transparent. Speech NA 8 or 16 kbit/s per TCH/F. cct mode structured 64 kbit/s alternate speech/unrestricted. Fig 6 : 6 a or 6 b, 7 a and 7 b cct mode speech alternating with SDU unrestricted 14.5 kbit/s or n × 14.5 kbit/s (n ≤ 2) on FR non transparent. 16 kbit/s per TCH/F. Fig 7 : 6 a or 6 b and 7 a and 7 b Automatic Facsimile Group 3. Data cct duplex synchronous access group 3 fax. cct mode SDUunrestricted 6 or 12 kbit/s or n × 6 kbit/s (n ≤ 3) or n × 12 kbit/s (n ≤ 2) on FR non transparent. 8 or 16 kbit/s per TCH/F. cct mode structured 64 kbit/s unrestricted. Fig 6 : 7 a and 7 b cct mode SDU unrestricted 14.5 kbit/s or n × 14.5 kbit/s (n ≤ 2) on FR non transparent. 16 kbit/s per TCH/F. Fig 7 : 7 a and 7 b NA: Not Applicable NOTE: The multislot data connections and the connections using TCH/F14.4 coding belong to the General Bearer Services (Classes 20, 30, 40, and 50 in GSM 02.02). ETSI ETSI TS 100 528 V7.0.1 (1999-07) 48 (GSM 03.10 version 7.0.1 Release 1998) Annex A (informative): List of definitions of GSM PLMN connection type attributes and values A.1 Attribute definition and their values Information transfer mode: This attribute describes the operational mode for transferring (transportation and switching) user information through a GSM PLMN connection in the network. Value: - Circuit Information transfer capability: This attribute describes the capability associated with the transfer of different types of information through a GSM PLMN connection. Values: - Unrestricted digital information - Speech - Group 3 facsimile - 3.1 kHz audio ex PLMN - Restricted digital information (Note: this value is signalled in the "Other ITC" element, due to a lack of further code points in the "ITC" element.) Information transfer rate: This attribute describes either the bit rate (circuit mode) or the throughput (packet mode, for further study). It refers to the transfer of digital information on a GSM PLMN connection. Values: - Appropriate bit rate - Throughput rate Establishment of connection: This attribute describes the mode of establishment used to establish and release GSM PLMN connections. Value: - Demand Symmetry: This attribute describes the relationship of information flow between two (or more) access points or reference points involved in a GSM PLMN connection. Values: - Bidirectional symmetric - Bidirectional asymmetric (Multislot configurations for data) Connection configuration: This attribute describes the spatial arrangement for transferring information on a given GSM PLMN connection. Value: - Point-to-point Structure: ETSI ETSI TS 100 528 V7.0.1 (1999-07) 49 (GSM 03.10 version 7.0.1 Release 1998) This attribute refers to the capability of a GSM PLMN connection to deliver information to the destination access point or reference point in a structure that was presented in a corresponding signal structured at the origin (access point or reference point). Values: - Service data unit integrity (see note 1) - Unstructured (see note 2) NOTE 1: Applicable for connection element "non transparent". NOTE 2: Applicable for connection element "transparent". Channel rate: This attribute describes the channels and their bit rate used to transfer the user information and/or signalling information. Value: - Name of channel (designation) and/or the corresponding bit rate NOTE 3: This attribute can be used several times for connection characterization. Connection control protocol, information transfer coding/protocol (layer 1 to 3): These attributes characterize the protocols on the connection control and/or user information transfer channel. Value: - Appropriate protocol for each layer NOTE 4: This attribute can be used several times for connection characterization. Synchronous/Asynchronous: This attribute describes the type of transmission between the reference access points. Values: - Synchronous - Asynchronous Negotiation: This attribute describes the possibility of inband parameter exchange (according to V.110) between reference access points. Value: - In band negotiation not possible User Rate: This element is relevant between the IWF and the fixed network. Values: - 0.3 kbit/s - 1.2 kbit/s - 1 200/75 bit/s - 2.4 kbit/s - 4.8 kbit/s - 9.6 kbit/s Intermediate rate: This attribute defines the intermediate rate (according to GSM 08.20 and CCITT V.110) at the A interface connection element part. Values: - 8 kbit/s - 16 kbit/s ETSI ETSI TS 100 528 V7.0.1 (1999-07) 50 (GSM 03.10 version 7.0.1 Release 1998) Fixed network user rate FNUR (Multislot configurations for data): This element is relevant between the IWF and the fixed network. Values: - 9.6 kbit/s - 14.4 kbit/s - 19.2 kbit/s - 28.8 kbit/s - 38.4 kbit/s - 48.0 kbit/s - 56.0 kbit/s - 64.0 kbit/s Acceptable channel coding(s) ACC (Multislot configurations for data): This attribute indicates the channel codings acceptable to the MS. This parameter is given at call set-up and it is non negotiable. Values: 4.8 kbit/s and/or 9.6 kbit/s and/or 14.4 kbit/s Maximum number of TCH/Fs (Multislot configurations for data): This attribute is given at call set-up and it enables the mobile user to limit the number of TCH/Fs used during the call. Values: 1 2 3 4 5 6 7 (note 5) 8 (note 5) NOTE 5: Not used by the currently specified services. Wanted air interface user rate (AIUR) (Multislot configurations for data): This attribute is applicable to non-transparent services only, and it gives the AIUR that the mobile user wants and which the network tries to achieve but which it is not allowed to exceed. Values: Not applicable 9.6 kbit/s 14.4 kbit/s 19.2 kbit/s 28.8 kbit/s ETSI ETSI TS 100 528 V7.0.1 (1999-07) 51 (GSM 03.10 version 7.0.1 Release 1998) 38.4 kbit/s 43.2 kbit/s 57.6 kbit/s User initiated modification indication (Multislot configurations for data): This element is relevant between the MT and the IWF. Values: - User initiated modification not requested - User initiated modification up to 1 TCH/F requested - User initiated modification up to 2 TCH/F requested - User initiated modification up to 3 TCH/F requested - User initiated modification up to 4 TCH/F requested The parameters where it is indicated that they are related to Multislot configurations for data are optional. For multislot configuration, the following applies to the parameters contained in the BC-IE: - Half rate channels are not supported. The MS shall code the radio channel requirement as "Full rate support only MS" or "Dual rate support MS, full rate preferred". In the second case, the network shall assign full rate channel(s) only. - The "fixed network user rate" and "other modem type" take precedence over the "user rate" and "modem type". - The "intermediate rate" parameter is overridden. The intermediate rate used per each TCH/F is derived from the chosen channel type: channel type IR per TCH/F TCH/F4.8 8 kbit/s TCH/F9.6 16 kbit/s TCH/F14.4 16 kbit/s (on the A interface but 32 kbit/s inside the MS) - The user rate per TCH is derived from the chosen channel type: channel type user rate per TCH TCH/F4.8 4.8 kbit/s TCH/F9.6 9.6 kbit/s TCH/F14.4 14.4 kbit/s For CE: T, the padding procedure described in GSM 03.34 can be applied. Network independent clocking on Tx: This attribute defines the usage of NIC at the reference access point in the transmit direction. Values: - Not required - Required Network independent clocking on Rx: This attribute defines the usage of NIC at the reference access point in the receive direction. Values: - Not accepted ETSI ETSI TS 100 528 V7.0.1 (1999-07) 52 (GSM 03.10 version 7.0.1 Release 1998) - Accepted Number of stop bits: This attribute describes the number of stop bits for the asynchronous type of transmission between reference access points. Values: - 1 bit - 2 bit Number of data bits excluding parity if present: This attribute describes the number of data bits for a character oriented mode of transmission between reference access points. Values: - 7 bit - 8 bit Parity information: This attribute describes the type of parity information for a character oriented mode of transmission between the reference access points. Values: - Odd - Even - None - Forced to 0 - Forced to 1 Duplex mode: This attribute describes the kind of transmission of the GSM PLMN between reference access points. Value: - Full duplex Modem type: This attribute describes the modem allocated by the IWF/MSC in the case of a 3.1 kHz audio used outside the GSM PLMN information transfer capability. Values: - V.21 - V.22 - V.22bis - V.23 - V.26ter - V.32 - Autobauding type 1 - None Other Modem Type (OMT): This element is relevant between the MS and IWF. Values: - No other modem type ETSI ETSI TS 100 528 V7.0.1 (1999-07) 53 (GSM 03.10 version 7.0.1 Release 1998) - V.32bis - V.34 Compression This attribute describes the possible usage of data compression between the reference access points. In the network to MS direction, it indicates the possibility of using data compression. In the MS to network direction, it indicates the allowance of data compression. Values: - Data compression not possible/not allowed - Data compression possible/allowed (see note 6) NOTE 6: Only applicable for the asynchronous transmission between the reference access points, if connection element is "non transparent". Radio channel requirement: This attribute describes the available channels for the transfer of the user information between the reference access points. Values: - Full rate channel (Bm) - Half rate channel (Lm) - dual rate/full rate preferred - Dual rate/half rate preferred Negotiation of Intermediate Rate Requested (NIRR) This attribute indicates if 6 kbit/s radio interface rate is requested. Values: - NIRR not requested/not accepted - NIRR requested/accepted Connection element: This attribute describes the possible usage of GSM layer 2 protocol between the reference access points. Values: - Transparent - Non-transparent (RLP) - Both, transparent preferred - Both, non transparent preferred User information layer 2 protocol: This attribute describes the layer 2 relay protocol used between the reference access points in non-transparent transmissions. Values: - ISO 6429, code set 0 - X.25 - Character oriented protocol with no flow control ETSI ETSI TS 100 528 V7.0.1 (1999-07) 54 (GSM 03.10 version 7.0.1 Release 1998) Signalling access protocol: This attribute characterizes the protocol on the signalling or user information transfer channel at the mobile reference access point. Values: - I.440/450 - X.21 - X.28, dedicated PAD, individual NUI - X.28, dedicated PAD, universal NUI - X.28, non dedicated PAD - X.32 Rate adaptation: This attribute describes the rate adaptation used at the fixed reference access point. Values: - V.110/X.30 - X.31 flag stuffing - No rate adaptation - V.120 (Note: This value is signalled in the "Other Rate Adaption" element, due to a lack of further code points in the "Rate Adaptation" element.) Coding standard: This attribute refers to the structure of the BC-IE defined in the GSM 04.08. Value: - GSM User information layer 1 protocol: This attribute characterizes the layer 1 protocol to be used at the Um interface according to the GSM 05.01. Value: - Default Rate adaption header/no header: This attribute is relevant between IWF and the fixed network. It is only applicable for V.120 rate adaptation. Values: - Rate adaption header not included - Rate adaption header included Multiple frame establishment support in data link: This attribute is relevant between IWF and the fixed network. It is only applicable for V.120 rate adaptation. Values: - Multiple frame establishment not supported. Only UI frames allowed - Multiple frame establishment supported Mode of operation: This attribute is relevant between IWF and the fixed network. It is only applicable for V.120 rate adaptation. Values: - Bit transparent mode of operation - Protocol sensitive mode of operation Logical link identifier negotiation: ETSI ETSI TS 100 528 V7.0.1 (1999-07) 55 (GSM 03.10 version 7.0.1 Release 1998) This attribute is relevant between IWF and the fixed network. It is only applicable for V.120 rate adaptation. Values: - Default, LLI=256 only - Full protocol negotiation (note 7) NOTE 7: A connection over which protocol negotiation will be executed is indicated in the "In-band/out-band negotiation" parameter. Assignor/assignee: This attribute is relevant between IWF and the fixed network. It is only applicable for V.120 rate adaptation. Values: - Message originator is "default assignee" - Message originator is "assignor only" In-band/out-band negotiation: This attribute is relevant between IWF and the fixed network. It is only applicable for V.120 rate adaptation. Values: - Negotiation is done with USER INFORMATION messages on a temporary signalling connection - Negotiation is done in-band using logical link zero. A.2 Definition of values Unrestricted digital data information: Transfer of information sequence of bits at its specified bit rate without alteration. This implies: - bit sequence independence; - digit sequence integrity; - bit integrity. Speech: Digital representation of speech coded according to a specified encoding rule (e.g. A Law, GSM 06-series). Demand connection: A GSM PLMN connection is set up at any time on demand via a digital channel in response to signalling information received from subscriber, other MSCs or other networks, i.e. on a per call basis. Bidirectional symmetric: This value applies when the information flow characteristics provided by the GSM PLMN connection are the same between two (or more) access points or reference points in the forward and backward directions. Bidirectional asymmetric (Multislot configurations for data): This value applies when the information flow characteristics provided by the GSM PLMN connection differ between two (or more) access points or reference points in the forward and backward directions on one or more TCH/Fs. In Multislot configurations for data the asymmetry is downlink biased, i.e. the MS may receive at a greater rate than it transmits. Point-to-point connection: This value applies when only two end points are provided by the connection. Service data unit integrity: This value applies when: ETSI ETSI TS 100 528 V7.0.1 (1999-07) 56 (GSM 03.10 version 7.0.1 Release 1998) i) at each user-network interface, protocols provide a mechanism for identifying the boundaries of service data units (e.g. X.25 complete packet sequence); and ii) all bits submitted within a single service data unit are delivered in a corresponding service data unit. Unstructured: This value is applicable when the GSM PLMN connection neither provides structural boundaries nor preserves structural integrity. ETSI ETSI TS 100 528 V7.0.1 (1999-07) 57 (GSM 03.10 version 7.0.1 Release 1998) Annex B (informative): Location of the transcoding, multiplexing and RA2 functions The location of the transcoding and data rate adaptation functions used to convert from the data rate used on the radio interface to the 64 kbits/s required by the MSC, is considered in this annex B. There are four alternatives which are equally valid from a connection type point of view. The selection of which alternative to use is not considered in GSM 03.10. The alternatives are shown in figure 8. Alternative 1 assumes that all the transcoding and data rate adaptation is located at the BSS end of the A interface. Alternative 2 assumes that all the transcoding and data rate adaptation is located at the MSC end of the A interface and gives no indication how the information is carried on the link. Alternative 3 assumes that the information is transferred on the A interface in 8 or 16 kbit/s channels using one of the sub-multiplexing schemes described in CCITT Recommendation I.460. The same sub-multiplexing scheme is used for both speech and data. Alternative 4 illustrates a multislot connection in which the information is transferred on the A-interface in 64 kbit/s channel into which up to four channels of intermediate rate 16 kbit/s have been multiplexed (refer to GSM 08.20). Alternative 4 also shows a situation in which a multislot connection of 5 or 6 TCH/Fs is used; the rate between the RA1’/RA1- and RA1’’-functions is 64 kbit/s. Alternatives 1b, 2b, 3b, and 4b show similar approaches for channel coding TCH/F14.4 (The alternatives explained above correspond to all other channel codings). It should be noted that in all of the alternatives the transcoding and data rate adaptation are performed on the BSS side of the A-interface and is therefore considered to be a function of the BSS. In the first three alternatives, the interface at the MSC is always based on 64 kbit/s without sub-multiplexing. ETSI ETSI TS 100 528 V7.0.1 (1999-07) 58 (GSM 03.10 version 7.0.1 Release 1998) MS BSS MSC RADIO I/F BSS-MSC I/F FEC RA1' RA1 FEC RA2 FEC FEC RA1' RA1 RA2 FEC MPX GSM 06-series Speech GSC A LAW BSS-MSC LINK Speech RA1' RA1 FEC MPX MPX GSM 06-series MPX RA2 Speech Data Data Data GSC A LAW ALTERNATIVE 1 ALTERNATIVE 2 ALTERNATIVE 3 GSC A LAW n x 8/16 kbit/s n x 8/16 kbit/s Figure 8: Location of transcoding and rate adaptation ETSI ETSI TS 100 528 V7.0.1 (1999-07) 59 (GSM 03.10 version 7.0.1 Release 1998) MS BSS MSC RADIO I/F BSS-MSC I/F BSS-MSC LINK ALTERNATIVE 4 FEC RA1' RA1 8 or 16kbit/s intermediate rates multiplexed/ demultiplexed Data RA1’’ 8 or 16kbit/s intermediate rates multiplexed/ demultiplexed FEC RA1' RA1 Data S/C Figure 8 (continued): Location of transcoding and rate adaptation RA2 RA2 RAA’ MS BSS MSC RADIO I/F BSS-MSC I/F FEC FEC RA1' RAA’ BSS-MSC LINK FEC RA1' RAA’ RA1' MPX MPX RAA’ Data Data Data ALTERNATIVE 1b ALTERNATIVE 2b ALTERNATIVE 3b n x 8/16 kbit/s RAA’ RAA’ RA2 Figure 8 (concluded): Location of transcoding and rate adaptation ETSI ETSI TS 100 528 V7.0.1 (1999-07) 60 (GSM 03.10 version 7.0.1 Release 1998) Legend to Figure 8 GSC = GSM Speech Codec FEC = Forward Error Correction MPX = Multiplex/Demultiplex MS BSS MSC RADIO I/F BSS-MSC I/F BSS-MSC LINK ALTERNATIVE 4b FEC RA1' RAA’ 16kbit/s intermediate rates multiplexed/ demultiplexed Data 16kbit/s intermediate rates multiplexed/ demultiplexed FEC RA1' RA1 Data S/C RAA’ Figure 8 (concluded): Location of transcoding and rate adaptation ETSI ETSI TS 100 528 V7.0.1 (1999-07) 61 (GSM 03.10 version 7.0.1 Release 1998) History Document history V6.0.0 April 1999 Publication V7.0.1 July 1999 Publication ISBN 2-7437-3208-3 Dépôt légal : Juillet 1999
|
d487d8f8c47c92f6dee9f0152353d268
|
133 902
|
1 Scope
|
........................................................................................................................................................5
|
d487d8f8c47c92f6dee9f0152353d268
|
133 902
|
2 References
|
................................................................................................................................................5
|
d487d8f8c47c92f6dee9f0152353d268
|
133 902
|
3 Definitions and Abbreviations
|
.................................................................................................................5
|
d487d8f8c47c92f6dee9f0152353d268
|
133 902
|
4 Formal analyses
|
.......................................................................................................................................5
|
d487d8f8c47c92f6dee9f0152353d268
|
133 902
|
4.1 Formal analysis of the 3G authentication protocol with modified sequence number management
|
................... 5
|
d487d8f8c47c92f6dee9f0152353d268
|
133 902
|
4.2 Formal analysis of the 3G authentication and key agreement protocol
|
............................................................. 5 Annex A: Formal Analysis of the 3G Authentication Protocol with Modified Sequence Number Management ............................................................................................................6 Annex B: Formal analysis of 3G authentication and key agreement protocol ................................37 Annex C: Change history......................................................................................................................45 ETSI TR 133 902 V3.1.0 (2000-01) (3G TR 33.902 version 3.1.0 Release 1999) ETSI 3GPP 3G TR 33.902 V3.1.0 (2000-01) 4 3G TR 33.902 version 3.1.0 Release 1999 Foreword This Technical Report has been produced by the 3GPP. The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of this TS, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: Version 3.y.z where: 3 the first digit: 3 Indicates TSG approved document under change control. y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. z the third digit is incremented when editorial only changes have been incorporated in the specification. ETSI TR 133 902 V3.1.0 (2000-01) (3G TR 33.902 version 3.1.0 Release 1999) ETSI 3GPP 3G TR 33.902 V3.1.0 (2000-01) 5 3G TR 33.902 version 3.1.0 Release 1999 1 Scope This report contains formal analyses of the authentication and key agreement (AKA) protocol specified in 3G TS 33.102. These analyses are carried out using various means of formal logic suitable for demonstrating security and correctness properties of the AKA protocol. The structure of this technical specification is as follows: clause 2 lists the references used in this specification; clause 3 lists the definitions and abbreviations used in this specification; clause 4 refers to the main body of this report. The main body is only referred to because it is not available in Word-, but only in pdf-format. The corresponding .pdf-documents are attached to this document. 2 References The following documents contain provisions which, through reference in this text, constitute provisions of the present document. All references are specific (identified by date of publication, edition number, version number, etc.) and are contained in the subsections of section 4 of this document. 3 Definitions and Abbreviations All definitions and abbreviations are contained in the subsections of section 4 of this document. 4 Formal analyses 4.1 Formal analysis of the 3G authentication protocol with modified sequence number management Annex A (TR_33902_Annex_A.pdf) contains a formal analysis of the 3GPP mechanism using a technique called Temporal Logic of Actions (TLA). The analysis seeks to prove that the 3GPP mechanism, if correctly implemented, will not "crash" or fall into failure scenarios. 4.2 Formal analysis of the 3G authentication and key agreement protocol The formal analysis contained in Annex B (TR_33902_Annex_B.pdf) complements the TLA-based formal analysis contained in Annex A. An enhanced BAN logic is used to prove that the 3GPP authentication and key agreement protocol meets the required security goals. ETSI TR 133 902 V3.1.0 (2000-01) (3G TR 33.902 version 3.1.0 Release 1999) ETSI 3GPP 3G TR 33.902 V3.1.0 (2000-01) 3G TR 33.902 version 3.1.0 Release 1999 Annex A: Formal Analysis of the 3G Authentication Protocol with Modified Sequence Number Management 6 ETSI TR 133 902 V3.1.0 (2000-01) (3G TR 33.902 version 3.1.0 Release 1999) ETSI 3GPP 3G TR 33.902 V3.1.0 (2000-01) 3G TR 33.902 version 3.1.0 Release 1999 Annex B: Formal analysis of 3G authentication and key agreement protocol 7 ETSI TR 133 902 V3.1.0 (2000-01) (3G TR 33.902 version 3.1.0 Release 1999) ETSI 3GPP 3G TR 33.902 V3.1.0 (2000-01) 3G TR 33.902 version 3.1.0 Release 1999 Annex C: Change history Change history TSG SA # Version CR Tdoc SA New Version Subject/Comment SA#05 0.1.0 3.0.0 Approved at SA#5 and placed under TSG SA Change Control SA#06 3.0.0 001 SP-99589 3.1.0 Formal analysis of the 3G authentication protocol 8 ETSI TR 133 902 V3.1.0 (2000-01) (3G TR 33.902 version 3.1.0 Release 1999) ETSI 9 ETSI ETSI TR 133 902 V3.1.0 (2000-01) (3G TR 33.902 version 3.1.0 Release 1999) History Document history V3.1.0 January 2000 Publication
|
bcc622d5a32ec685216fad82284345d7
|
127 903
|
1 Scope
|
........................................................................................................................................................5
|
bcc622d5a32ec685216fad82284345d7
|
127 903
|
2 References
|
................................................................................................................................................5
|
bcc622d5a32ec685216fad82284345d7
|
127 903
|
3 Definitions and Abbreviations
|
.................................................................................................................6
|
bcc622d5a32ec685216fad82284345d7
|
127 903
|
3.1 Definitions
|
..........................................................................................................................................................6
|
bcc622d5a32ec685216fad82284345d7
|
127 903
|
3.2 Abbreviations
|
.....................................................................................................................................................7
|
bcc622d5a32ec685216fad82284345d7
|
127 903
|
4 Summary of Standards Activities
|
.............................................................................................................7
|
bcc622d5a32ec685216fad82284345d7
|
127 903
|
4.1 IrMC
|
...................................................................................................................................................................7
|
bcc622d5a32ec685216fad82284345d7
|
127 903
|
4.2 Bluetooth
|
............................................................................................................................................................7
|
bcc622d5a32ec685216fad82284345d7
|
127 903
|
4.3 WAP
|
...................................................................................................................................................................7
|
bcc622d5a32ec685216fad82284345d7
|
127 903
|
4.4 Other Standards Activities
|
..................................................................................................................................7
|
bcc622d5a32ec685216fad82284345d7
|
127 903
|
4.4.1 MNCRS
|
........................................................................................................................................................7
|
bcc622d5a32ec685216fad82284345d7
|
127 903
|
4.4.2 Synchronisation
|
............................................................................................................................................8
|
bcc622d5a32ec685216fad82284345d7
|
127 903
|
4.4.3 MDSP
|
...........................................................................................................................................................8
|
bcc622d5a32ec685216fad82284345d7
|
127 903
|
5 Overview of Synchronisation Standards
|
..................................................................................................8
|
bcc622d5a32ec685216fad82284345d7
|
127 903
|
5.1 Introduction
|
........................................................................................................................................................8
|
bcc622d5a32ec685216fad82284345d7
|
127 903
|
5.2 IrMC Overview
|
..................................................................................................................................................8
|
bcc622d5a32ec685216fad82284345d7
|
127 903
|
5.3 IrMC 1.1 Limitations for Wide Area Synchronisation
|
.......................................................................................9
|
bcc622d5a32ec685216fad82284345d7
|
127 903
|
5.3.1 Level 4 Dependent on Connection-based Transport Protocol
|
......................................................................9
|
bcc622d5a32ec685216fad82284345d7
|
127 903
|
5.3.2 Inefficient Data Exchange
|
............................................................................................................................9
|
bcc622d5a32ec685216fad82284345d7
|
127 903
|
6 Recommendations
|
....................................................................................................................................9 History..............................................................................................................................................................10 (3G TR 27.903 version 3.0.0 Release 1999) ETSI TR 127 903 V3.0.0 (2000-01) ETSI 3GPP 3G TR 27.903 V 3.0.0 (1999-10) 4 3G TR 27.903 version 3.0.0 Foreword This Technical Report has been produced by the 3GPP. The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of this TR, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: Version 3.y.z where: x the first digit: 1 presented to TSG for information; 2 presented to TSG for approval; 3 Indicates TSG approved document under change control. y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. z the third digit is incremented when editorial only changes have been incorporated in the specification; (3G TR 27.903 version 3.0.0 Release 1999) ETSI TR 127 903 V3.0.0 (2000-01) ETSI 3GPP 3G TR 27.903 V 3.0.0 (1999-10) 5 3G TR 27.903 version 3.0.0 1 Scope The present document provides information on existing synchronisation protocols. It summarises proprietary and standard protocols relevant to current and future mobile communication devices. The present document covers only synchronisation between end-user devices, desktop applications, and server-based information services. It does not refer to replication or synchronisation between enterprise databases. 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. • For a non-specific reference, the latest version applies. • A non-specific reference to an ETS shall also be taken to refer to later versions published as an EN with the same number. [1] Bluetooth: Bluetooth SIG, Bluetooth Specifications, version 1.0, July 1999. (http://www.bluetooth.com/) [2] Generic Binary Object: Infrared Data Association, "IrWW IrDA for Wrist Watches", "Generic Binary Object" Chapter 4, version 0.5, 12 July 1999. (members section of ftp://ftp.irda.org/) [3] ICNIRP: "Guidelines for limiting exposure to time-varying electric, magnetic, and electromagnetic fields (up to 300 GHz)", International Commission on Non-Ionizing Radiation Protection (ICNIRP), Health Physics, vol. 74, pp 494-522, April 1998. [4] IrLAP: Infrared Data Association, "Serial Infrared Link Access Protocol (IrLAP)", version 1.1, 16 June 1996, plus all applicable errata. (http://www.irda.org/) [5] IrLMP, Infrared Data Association, "Link Management Protocol", version 1.1, 23 January 1996, plus all applicable errata. (http://www.irda.org/) [6] IrMC, Infrared Data Association, "Specifications for Ir Mobile Communications (IrMC)", version 1.1, 01 March 1999, plus all applicable errata. (http://www.irda.org/) [7] IrOBEX, Infrared Data Association, "Ir Object Exchange Protocol IrOBEX", version 1.2, April 1999, plus all applicable errata. (http://www.irda.org/) [8] MNCRS, Mobile Network Computing Reference Specification Consortium, Mobile Network Computing Reference Specification, Data Synchronisation Work Group, Application Programmer's Guide to Mobile Network Computer Data Synchronisation, version 1.1, March 1999. (http://www.oadg.or.jp/activity/mncrs/mncrs03-99.html) [9] MDSP - Mobile Data Synchronisation Protocol. [10] Tiny TP, Infrared Data Association, "'Tiny TP': A Flow-Control Mechanism for use with LrLMP", version 1.1, 20 October 1996, plus all applicable errata. (http://www.irda.org/) [11] Various documents produced for "Synchronisation". [12] vCalendar, the Internet Mail Consortium, "vCalendar - The Electronic Calendaring and Scheduling Exchange Format - Version 1.0", 18 September 1996. (http://www.imc.org/pdi/vcal- 10.doc) (3G TR 27.903 version 3.0.0 Release 1999) ETSI TR 127 903 V3.0.0 (2000-01) ETSI 3GPP 3G TR 27.903 V 3.0.0 (1999-10) 6 3G TR 27.903 version 3.0.0 [13] vCard, the Internet Mail Consortium, "vCard - The Electronic Business Card - Version 2.1", 18 September 1996.(http://www.imc.org/pdi/vcard-21.doc) [14] WAP, WAP Forum, "WAP Technical Specifications Suite", version 1.1, June 1999. (http://www.wapforum.com/) 3 Definitions and Abbreviations 3.1 Definitions For the purposes of the present document, the following terms and definitions apply: Bluetooth: a technology specification [1] for short range radio links between mobile PCs, mobile phones and other portable devices. (http://www.bluetooth.com/) bvCalendar: a compressed version of vCalendar as defined in the IrDA Generic Binary Object proposal [2]. bvCard: a compressed version of vCard as defined in the IrDA Generic Binary Object proposal [2]. GET: the operation of requesting that the server returns an object from to the client as defined in the IrDA IrOBEX specification [7]. IrDA: an industry consortium set up to define a set of short range Ir communications standards. (http://www.irda.org/) Latency: time delay associated with the process of information exchange in a network. Level 1: minimum level support defined in the IrDA IrMC set of specifications [6]. Level 2: Access Level support defined in the IrDA IrMC set of specifications [6]. Level 3: Index Level support defined in the IrDA IrMC set of specifications [6]. Level 4: Sync Level support defined in the IrDA IrMC set of specifications [6]. Personal Area Network: a short range wireless connection between two or more devices for the purpose of transferring information. Short range is typically defined as fifty meters or less in distance. PUT: the operation of sending one object from the client to the server as defined in the IrDA IrOBEX specification [7]. Radio Frequency (RF): the frequency range between 300 Hz and 300 GHz (ICNIRP definition [3]). Synchronisation: the process of exchanging information between multiple physical or virtual locations for the purpose of ensuring that each location's copy of that information reflects the same information content. Ultra: a connectionless information transfer mechanism defined as part of the IrDA IrMC set of specifications [6]. vCalendar: a format defined by the IMC for electronic calendaring and scheduling exchange [12] with extensions as defined in the IrDA IrMC set of specifications [6]. vCard: a format defined by the IMC for electronic business card exchange [13] with extensions as defined in the IrDA IrMC set of specifications [6]. WAP: an industry consortium set up to define a set of standards [14] to empower mobile users with wireless devices to easily access and interact with information and services. (http://www.wapforum.com/) Wide Area Devices: devices intended for use in 3G systems. Wide Area Network: a geographically-large range wireless connection between two or more devices for the purpose of transferring information. Large geographical range is typically defined as one kilometer or more in distance. Wireless Information Devices: wide area and short range devices intended for information transfer. (3G TR 27.903 version 3.0.0 Release 1999) ETSI TR 127 903 V3.0.0 (2000-01) ETSI 3GPP 3G TR 27.903 V 3.0.0 (1999-10) 7 3G TR 27.903 version 3.0.0 3.2 Abbreviations For the purposes of the present document, the following abbreviations apply: DID Database IDentifier IAS Information Access Service IBM International Business Machines ICNIRP International Commission on Non-Ionizing Radiation Protection IETF Internet Engineering Task Force IMC Internet Mail Consortium Ir Infrared IrDA Infrared Data Association IrLAP Infrared Link Access Protocol IrLMP Infrared Link Management Protocol IrMC Ir Mobile Communications IrOBEX Ir Object EXchange LUID Unique object IDentifier MDSP Mobile Data Synchronisation Protocol MNCRS Mobile Network Computer Reference Specification OBEX Object Exchange PDA Personal Digital Assistant PIM Personal Information Manager TTP Tiny TP WAP Wireless Application Protocol 4 Summary of Standards Activities 4.1 IrMC The IrMC standard [6] was developed as an extension to the IrDA standard for the purpose of providing an open standard for data exchange between mobile devices or between mobile devices and desktops or PDAs. Among other things, IrMC defines four levels of support for information exchange. By definition, each higher level must support all of the preceding levels. The four levels are: Level 1 (Minimum Level), Level 2 (Access Level), Level 3 (Index Level), and Level 4 (Sync Level). (Level 4 does not require Level 3) Level 2 and Level 4 are the most relevant for synchronisation. IrMC has been adopted by the IrDA and Bluetooth initiatives and has wide industry support. 4.2 Bluetooth Bluetooth has adopted the IrMC standard [6] as the basis for their synchronisation specification. 4.3 WAP WAP [14] has not specified a synchronisation standard. Attempts to form a work group last year were abandoned. 4.4 Other Standards Activities 4.4.1 MNCRS The MNCRS [8] (Mobile Network Computer Reference Specification) specifies an application programming interface (API) providing data-synchronisation services focused on Java-enabled devices. MNCRS is promoted by a number of companies but has not been adopted by any formal standards body. (3G TR 27.903 version 3.0.0 Release 1999) ETSI TR 127 903 V3.0.0 (2000-01) ETSI 3GPP 3G TR 27.903 V 3.0.0 (1999-10) 8 3G TR 27.903 version 3.0.0 4.4.2 Synchronisation A group met informally in early 1999 for the purpose of defining a synchronisation specification [11] to be presented to the 3GPP or WAP bodies. The parties involved - Symbian, Puma, Ericsson, Nokia, Motorola, Starfish, and Lotus - disbanded before any agreement was reached. 4.4.3 MDSP MDSP [9] (Mobile Data Synchronisation Protocol) is a data synchronisation and data exchange protocol for networked devices promoted by IBM. It is designed primarily for use between mobile devices that are sporadically connected to the network and servers that are continuously connected to the network. In particular, MDSP is designed to handle the case where the server and device store the data they are synchronizing in different formats, using different software systems. MDSP can be used to exchange data elements, without attempting to synchronize the containers as used in a one-way synchronisation to a device with no editing capabilities. MDSP has not been adopted by any formal standards body. 5 Overview of Synchronisation Standards 5.1 Introduction 3G Wireless Information Devices will enable unprecedented access to information regardless of location. Information will continue to be stored on personal computers or servers, however users will also expect to be able to have access to that same information on handheld or palm-size devices and wireless devices. To date, there is only one adopted standard that addresses synchronisation: IrMC. The IrMC standard [6] is also referenced in the Bluetooth specification. 3GPP has not yet adopted a standard for synchronisation. The IrMC standard [6] is defined for personal area networks running either low or high bandwidth wireless links and may be used in connection-oriented or connectionless links such as IrDA or Bluetooth. It does not currently support a specifically optimized mode for wide area network synchronisation. Wide area network synchronisation presents a unique set of problems for efficient and accurate synchronisation. 5.2 IrMC Overview The IrMC version 1.1 specification [6] was driven by leading handset manufacturers to provide a standard means for exchanging data between mobile devices and between mobile devices and desktop, handheld PCs, and Printers of various kinds. The focus of the original specification was to extend the IrDA standard to include extensions for transferring Personal Information Manager (PIM) data, files, and isochronous voice between co-operating IrMC devices. The current IrMC specification [6] supports data exchange with Phone Book, Calendar, Messaging and Note applications on mobile devices. The specification was recently updated (version 1.1 [6]) to better support synchronisation features requested by the Bluetooth initiative, which is also committed to using IrMC version 1.1 [6] and its supporting IrOBEX [7] object exchange layer for satisfying its data exchange needs over short-distance radio links. The scope of the IrMC specification [6] encompasses more than synchronisation. Components of IrMC deal with Call Control (for mobile handsets), real time audio transmission, and permissions for getting and setting the real time clock on the mobile device. IrMC also defines four (4) distinct levels of support for information exchange, where each higher level is expected to support the preceding levels (with some exceptions, see above). For purposes of synchronisation, Level 2 (Access Level) and Level 4 (Sync Level) are the only information exchange levels required to address our stated requirements. The IrMC specification [6] and its supporting IrOBEX [7] object exchange layer is layered on top of the pre-existing IrDA stack. Since the IrMC synchronisation component requires either the Connection Oriented Service or the Connectionless Oriented Service, this means that IrMC and IrOBEX, when used in an IrDA application, sit atop of the IrDA layers IrLAP [4], IrLMP [5], and possibly TTP [10] and IAS [5]. Thus, the IrMC specification [6] is a natural (3G TR 27.903 version 3.0.0 Release 1999) ETSI TR 127 903 V3.0.0 (2000-01) ETSI 3GPP 3G TR 27.903 V 3.0.0 (1999-10) 9 3G TR 27.903 version 3.0.0 extension of the IrDA stack. When used in Bluetooth, IrMC and IrOBEX sit atop the Bluetooth equivalent of these layers. The object is to swap transport and below layers while keeping a common set of applications. The information exchange levels of IrMC prescribe the text-based data formats that must be exchanged between two mobile devices. Wherever possible, industry-standard data formats are used. Where no pre-existing data format exists, IrMC defines new formats that must be supported by implementers. Required data formats include IMC's vCard [13] and vCalendar [12] plus the similarly defined constructs vMessage [6] and vNote [6]. In addition, custom data formats are prescribed for exchanging data objects (such as change logs, information logs, error logs and device information). IrMC is currently evaluating allowing the use of the IETF versions of these constructs, the binary versions called bvCard [2] and bvCalendar [2], plus a completely generic Generic Binary Object [2]. IrMC effectively addresses the synchronisation needs of PIM applications residing on mobile devices, and operating in a connected or connectionless environment. At the highest level (Level 4), IrMC specifies core functionality such as database identifiers (DID), unique object identifiers (LUID), change logs and change counters or time stamps which are essential to ensure fast and reliable synchronisation. The specification also includes a rich set of features for exchanging PIM data. Included in this is an Information Log that describes the characteristics of each database, a Device Information block that identifies each device with capabilities, an optional Error Log that returns record-level error codes, a mechanism for detecting new items entered while synchronisation is in progress, and a means for detecting device resets. 5.3 IrMC 1.1 Limitations for Wide Area Synchronisation IrMC was written to address the exchange of PIM data in a personal area network or peer-to-peer environment. However, the current IrMC specification [6] has not yet addressed synchronisation in a wide area wireless network environment such as that which would exist in a 3GPP scenario. The limitations of IrMC in a 3G environment are as follows: 5.3.1 Level 4 Dependent on Connection-based Transport Protocol IrMC Level 4 (Sync Level) requires either a Connection Oriented Service, when using IrDA involves components such as IrLAP [4] and IrLMP [5]. By its nature, IrOBEX [7] involves establishing an explicit connection between devices, performing the necessary data exchange, and then disconnecting. A persistent connection between devices is difficult to maintain in some Wide Area Network environments. Latency can slow the transactions to an unacceptable level, or worse, cause synchronisation to be stopped due to timeouts. 5.3.2 Inefficient Data Exchange Data exchanges between an IrMC client and server tend to be chatty and quite inefficient. In particular, each object sent between devices requires a separate request/response pair using IrOBEX [7] commands. For example, GET operations entail a request and response for each object. PUT Operations can be more efficient in an Ultra [6] environment since no response is expected. To address the limitations of IrMC Level 4 synchronisation in a Wide Area Network, one of two actions must occur. a) Modifications to the IrMC Level 4 to address the above limitations within the Wide Area Network must be made. b) An extension to IrMC Level 4 for Wide Area Network Synchronisation must be created. Ideally, this extension would operate on top of existing stacks and would use as much existing code base as possible. (3G TR 27.903 version 3.0.0 Release 1999) ETSI TR 127 903 V3.0.0 (2000-01) ETSI 10 ETSI ETSI TR 127 903 V3.0.0 (2000-01) (3G TR 27.903 version 3.0.0 Release 1999) History Document history V3.0.0 January 2000 Publication
|
884138cb53bcd8f30ecc584e1b0fed4c
|
126 912
|
1 Scope
|
........................................................................................................................................................6
|
884138cb53bcd8f30ecc584e1b0fed4c
|
126 912
|
2 References
|
................................................................................................................................................6
|
884138cb53bcd8f30ecc584e1b0fed4c
|
126 912
|
3 Definitions and abbreviations
|
..................................................................................................................6
|
884138cb53bcd8f30ecc584e1b0fed4c
|
126 912
|
3.1 Definitions
|
............................................................................................................................................................... 6
|
884138cb53bcd8f30ecc584e1b0fed4c
|
126 912
|
3.2 Abbreviations
|
.......................................................................................................................................................... 6
|
884138cb53bcd8f30ecc584e1b0fed4c
|
126 912
|
4 3GPP Configuration of H.324 annex C
|
...................................................................................................8
|
884138cb53bcd8f30ecc584e1b0fed4c
|
126 912
|
5 Performance
|
.............................................................................................................................................9
|
884138cb53bcd8f30ecc584e1b0fed4c
|
126 912
|
5.1 Audio
|
....................................................................................................................................................................... 9
|
884138cb53bcd8f30ecc584e1b0fed4c
|
126 912
|
5.1.1 Introduction
|
........................................................................................................................................................ 9
|
884138cb53bcd8f30ecc584e1b0fed4c
|
126 912
|
5.1.2 Results
|
............................................................................................................................................................... 9
|
884138cb53bcd8f30ecc584e1b0fed4c
|
126 912
|
5.2 Video
|
..................................................................................................................................................................... 11
|
884138cb53bcd8f30ecc584e1b0fed4c
|
126 912
|
5.2.1 Introduction
|
...................................................................................................................................................... 11
|
884138cb53bcd8f30ecc584e1b0fed4c
|
126 912
|
5.2.2 Test environment
|
............................................................................................................................................. 11
|
884138cb53bcd8f30ecc584e1b0fed4c
|
126 912
|
5.2.3 Results
|
............................................................................................................................................................. 11
|
884138cb53bcd8f30ecc584e1b0fed4c
|
126 912
|
5.2.3.1 Subjective results
|
............................................................................................................................................. 12
|
884138cb53bcd8f30ecc584e1b0fed4c
|
126 912
|
5.2.3.2 Objective results
|
.............................................................................................................................................. 14 Annex A Quality degradation as a function of the FER and RBER in presence of background noise..................................................................................................................17 A.1 Results in Car Noise: .............................................................................................................................17 A.2 Results in Street Noise:..........................................................................................................................17 A.3 Results in Office Noise..........................................................................................................................18 Annex B: Simulation test of a video multimedia codec .....................................................................19 B.1 Introduction............................................................................................................................................19 B.2 Test Procedure .......................................................................................................................................19 B.2.1 Simulation Model ............................................................................................................................................ 19 B.2.2 Source materials............................................................................................................................................... 21 B.2.3 Source encoding............................................................................................................................................... 21 B.2.3.1 Speech.............................................................................................................................................................. 21 B.2.3.2 Video ............................................................................................................................................................... 21 B.2.4 Multiplexing .................................................................................................................................................... 22 B.2.5 Bit error injection............................................................................................................................................. 22 B.2.5.1 Error pattern files............................................................................................................................................. 22 B.2.5.2 Error pattern segments to be used at the simulation ........................................................................................ 23 B.2.5.3 Injection of bit errors ....................................................................................................................................... 23 B.2.6 De-multiplexing............................................................................................................................................... 23 B.2.7 Video decoding................................................................................................................................................ 24 B.2.8 Constraints and regulations.............................................................................................................................. 24 B.2.8.1 Delay................................................................................................................................................................ 24 B.2.8.1.1 Video.......................................................................................................................................................... 24 B.2.9 Statistical data to be reported........................................................................................................................... 24 B.2.9.1 Video coding bitrate [%6.2f kbps] and MUX overhead [%6.2f kbps]............................................................. 25 B.2.9.2 Speech coding bitrate [%6.2f kbps] and frame length [%d ms]....................................................................... 25 B.2.9.3 Video initial delay [%6.1f ms]......................................................................................................................... 25 B.2.9.4 PSNR related data............................................................................................................................................ 25 B.2.9.4.1 Total average PSNR, i.e., PSNRtotal [%6.2f dB]......................................................................................... 25 B.2.9.4.2 Average PSNR for representative run, i.e., PSNRk* [%6.2f dB] ................................................................ 25 B.2.9.4.3 Average PSNR in error-free case, i.e., PSNRfree [%6.2f dB] ..................................................................... 25 B.2.9.4.4 Standard deviation of PSNR, i.e., Sigma [%6.2f dB]................................................................................. 25 ETSI ETSI TR 126 912 V3.0.0 (2000-03) 4 3G TR 26.912 version 3.0.0 Release 1999 B.2.9.5 Coding frame rate [%5.2f frames/sec]............................................................................................................. 26 B.2.9.6 Average dropframe rate [%6.2f %].................................................................................................................. 26 B.2.9.7 Out of delay constraints rate [%6.2f %]........................................................................................................... 26 B.2.9.8 Definition of video stationary delay................................................................................................................. 26 B.2.9.9 Decoded video of representative run ............................................................................................................... 27 B.3 Subjective quality evaluation.................................................................................................................27 B.3.1 Structure of test................................................................................................................................................ 27 B.3.1.1 Program ........................................................................................................................................................... 27 B.3.1.2 Training session............................................................................................................................................... 27 B.3.1.3 Scoring session ................................................................................................................................................ 27 B.3.1.4 Video sequence................................................................................................................................................ 27 B.3.1.5 Structure of program........................................................................................................................................ 27 B.3.2 Editing process................................................................................................................................................. 28 B.3.2.1 Producing training session............................................................................................................................... 28 B.3.2.2 Randomization................................................................................................................................................. 28 B.3.3 Assessment ...................................................................................................................................................... 28 B.3.3.1 Test subjects .................................................................................................................................................... 28 B.3.3.2 Facilities and equipment for test...................................................................................................................... 29 B.3.3.3 Score sheet....................................................................................................................................................... 29 B.3.4 Data processing................................................................................................................................................ 29 B.3.4.1 MOS [%4.2f] ................................................................................................................................................... 30 B.3.4.2 Standard deviation of OS, i.e., 1os [%4.2f] ...................................................................................................... 30 B.4 Test results and observations .................................................................................................................30 B.4.1 Test results....................................................................................................................................................... 30 B.4.2 Observations .................................................................................................................................................... 30 B.5 List of video/speech codecs and multiplexers employed in the simulation...........................................31 B.6 Test results.............................................................................................................................................32 Annex C: Change history......................................................................................................................37 ETSI ETSI TR 126 912 V3.0.0 (2000-03) 5 3G TR 26.912 version 3.0.0 Release 1999 Foreword This Technical Report (TR) has been produced by the 3rd Generation Partnership Project (3GPP). The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: Version x.y.z where: x the first digit: 1 presented to TSG for information; 2 presented to TSG for approval; 3 or greater indicates TSG approved document under change control. y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. z the third digit is incremented when editorial only changes have been incorporated in the document. ETSI ETSI TR 126 912 V3.0.0 (2000-03) 6 3G TR 26.912 version 3.0.0 Release 1999 1 Scope The present document is meant to function as guidance in the work of other 3GPP work groups or work items. Such work may include conclusion on how to achieve detailed Stage 1 service requirements or suggestion of a set of recommended RAB parameters giving satisfactory user-to-user quality for a circuit switched multimedia service using 3G-324M. 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. • For a non-specific reference, the latest version applies. [1] "Volume 3; Specifications of air-interface for 3G mobile system (Version 1.0-0.3)", IMT-2000 Study Committee, Air-Interface WG/SWG2, Nov. 18th, 1998. [2] "Volume 8; Codec specification for use in a 3G mobile system (Version 0.5.2)", IMT-2000 Study Committee, Codec WG (ARIB), July 21st, 1998. [3] International Standard ISO/IEC 14494-2: "Information technology — Generic coding of audio- visual object — Part 2: Visual, 1999". [4] ITU-T Recommendation H.263: "Video coding for low bit rate communication". [5] ITU-T Recommendation H.245: "Control protocol for multimedia communication". [6] ITU-T Recommendation H.223: "Multiplexing protocol for low bitrate multimedia communication". [7] ITU-T Recommendation H.324: "Terminal for low bit rate multimedia communication". 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the following terms and definitions apply. Codec: a single media coder/decoder, or a multimedia system specific coder & decoder system. For example, 3GPP AMR (speech codec), ITU-T H.263 (video codec) or ITU-T H.32x (multimedia system with included media codecs) are understood to fulfil the definition of a codec. TS 21.905 "Vocabulary for 3G Specifications" provides the definitions not listed in this section. 3.2 Abbreviations For the purposes of the present document, the following abbreviations apply: 3G Third Generation Mobile Network 5DQS 5 step Discrete Quality Scale AC/DC Alternate Current/Direct Current AL1-AL3 Adaptation Layer 1-3 ETSI ETSI TR 126 912 V3.0.0 (2000-03) 7 3G TR 26.912 version 3.0.0 Release 1999 AL-SDU Adaptation Layer – Service Data Unit ARIB Association of Radio Industries and Businesses BER residual Bit Error Ratio BT 500-8 ITU-R Recommendation, "Methodology for the subjective assessment of the quality of television pictures" CCSRL Control Channel Segmentation and Reassembly Layer CIF Common Image Format (352x288 pixel) CRC Cyclic Redundancy Code FEC Forward Error Correction FER Frame Error Ratio GSM Global System for Mobile-communications AMR Adaptive Multi-Rate Speech Codec H.223 ITU-T Recommendation, "Multiplexing protocol for low bit rate multimedia communication" H.245 ITU-T Recommendation, "Control protocol for multimedia communication" H.324 ITU-T Recommendation, "Terminal l for low bit rate multimedia communication" IEC International Electrotechnical Commission IMT-2000 International Mobile Telecommunications - 2000 ISO International Organization for Standardization ITU-R International Telecommunication Union – Radiocommunications Standardisation Sector ITU-T International Telecommunication Union – Telecommunications Standardisation Sector I-VOP Intra Video Object Plane kbps Kilo bits per second (used in Annex B) LAPM Link Access Procedure for Modem LCD Liquid Crystal Panel MOS Mean Opinion Score MPEG Moving Picture Expert Group MUX-PDU MUltipleX – Protocol Data Unit PLMN Public Land Mobile Network PSNR Peak Signal to Noise Ratio P-VOP Predicted Video Object Plane QCIF Quarter Common Image Format (176x144 pixel) QoS Quality of Service SS Single Stimulus TM-5 Test Model 5 WCDMA Wideband Code Division Multiple Access VLC Variable Length Code ETSI ETSI TR 126 912 V3.0.0 (2000-03) 8 3G TR 26.912 version 3.0.0 Release 1999 4 3GPP Configuration of H.324 annex C Figure 1 Figure 1 shows the main building block of a 3G-324M terminal. The standards inside […] are not mandatory. The configuration actually used for each of the four performances evaluations (Audio, Video, Control and Data) will be described under each heading. Video I/O Equipment Video Codec H.263, [MPEG-4, Audio I/O Equipment Speech Codec AMR, [G.723.1 …] Optional Receive Path Delay Multiplex/ Demultiplex H.223, H.223 Annex A, H.223 Annex B, [H.223 Annex C, H.223 Annex D] User Data Application s Data Protocols [V.14, LAPM, …] Syste m Contro l H.245 3GPP Network CCSRL NSRP [LAPM/V.4 Scope of TS 26.111 Call Set-up Scope of TS 26.112 ETSI ETSI TR 126 912 V3.0.0 (2000-03) 9 3G TR 26.912 version 3.0.0 Release 1999 5 Performance 5.1 Audio 5.1.1 Introduction This section provides a subset of the AMR Characterisation test results expressed as speech quality degradation (in ∆MOS or ∆DMOS) compared to the EFR speech codec in error free conditions, as a function of the FER (Frame Error Rate) and RBER( Residual Bit Error Rate as defined for GSM). It is believed that these results would also apply to H.324M channel with equivalent error conditions. Additional results are provided in Annex A for test conditions under background noise (Car noise, Street noise and Office noise). The original test results are included in the AMR characterisation report (TR 26.975). They relate to a channel condition GSM TU3 IFH (Typical Urban 3 km/h Ideal Frequency Hopping). These results could be updated once the AMR 3G Characterisation tests are completed. Quality performances of audio codecs in H.324M channels should be included in future versions of this document, as these results become available. 5.1.2 Results The following diagrams present the speech quality degradation in clean speech (expressed in ∆MOS) for the different AMR codec modes, as a function of the FER and RBER, when compared to the EFR speech codec in error free condition. In all cases, the results represent the average scores obtained over all tests performed for each experiment as compiled in the GSM AMR Characterization report (TR 26.975). The EFR reference is taken from the score obtained by the EFR speech codec in error free in the same experiment. The actual results were slightly altered to smoothen the curves’ shape. Finally, it should also be noted that the diagrams function of the FER are actually affected by the Residual Bit Error Rate for each test condition, while the diagrams function of the RBER are also function of the FER present for each test condition. The two sets of diagrams cannot be considered totally independent. They are a reflection of the channel coding scheme selected for the GSM radio channels. Finally, it should be pointed out that the FER and RBER estimates used to derive these diagrams are based on the limited number of error patterns used for the AMR characterization phase. These could be affected by some inaccuracies that could explain the difference in shapes between the different speech codec modes. WARNING: These results are representative of the test conditions used for the GSM AMR characterization phase and may not be representative of the codec performances in other test conditions. When analyzing the original experiments, it was usually found that a difference in MOS lower than 0.2 was not statistically significant. For the following results, the confidence interval should also be increased by the uncertainty introduced in the estimation of the FER or RBER. Perceived quality (MOS) degradation as a function of the FER (FR Tests in Clean Speech) -3.00 -2.50 -2.00 -1.50 -1.00 -0.50 0.00 0.50 0.001% 0.010% 0.100% 1.000% 10.000% 100.000% FER ∆ M OS 12.2 10.2 7.95 FR 7.4 FR 6.7 FR 5.9 FR 5.15 FR 4.75 FR Perceived quality (MOS) degradation as a function of the RBER (FR Tests in Clean Speech) -3.00 -2.50 -2.00 -1.50 -1.00 -0.50 0.00 0.50 0.001% 0.010% 0.100% 1.000% 10.000% RBER ∆ M OS 12.2 10.2 7.95 FR 7.4 FR 6.7 FR 5.9 FR 5.15 FR 4.75 FR ETSI ETSI TR 126 912 V3.0.0 (2000-03) 10 3G TR 26.912 version 3.0.0 Release 1999 Figure 2a: Quality Degradation function of FER Figure 2b: Quality Degradation function of RBER ETSI ETSI TR 126 912 V3.0.0 (2000-03) 11 3G TR 26.912 version 3.0.0 Release 1999 Comments on the previous results: In clean speech, it appears that all AMR codec modes do not show any significant quality degradation when the Frame Erasure Rate is lower than 0.5%. In some instances, the range can even be extended to 1% FER without any quality degradation. It is also interesting to note that at 1% FER degradation, the highest codec modes (12.2 and 10.2) are still equivalent to the second tier of codec modes (7.95 to 5.9) in error free. Similarly, the middle range codec modes (7.95 to 5.9) present the same quality at 1% FER than the lower rate codec modes (5.15 and 4.75) in error free conditions. The results as a function of the RBER are quite similar with a different range of acceptable RBER. The AMR codec modes do not present any significant quality degradation when the RBER is below 0.1%. Similar results under background noise conditions are provided in Annex A. 5.2 Video 5.2.1 Introduction Qualitative evaluation of H.324 Annex C over a simulated WCDMA Channel was carried out by ARIB (Association of Radio Industries and Businesses) IMT-2000 Study committee March 1999. The purpose of the test was to clarify the relationship between source/channel codec parameters and the channel bit-error conditions. A short description of the evaluation and a presentation of the results are included. The full test report is included in Annex B. 5.2.2 Test environment The ARIB simulation was carried out as follows: 1) source video sequences come into a video encoder; 2) speech dummy data and video bitstreams are generated; 3) the bitstreams are multiplexed into a single multiplexed bitstream in the form of MUX-PDU; 4) bit errors are injected into the multiplexed bitstream ('1' in error pattern file represents error); 5) contaminated bitstream is de-multiplexed into speech and video bitstreams; 6) de-multiplexed video bitstream is decoded by a video decoder; 7) decoded video sequences are evaluated subjectively. A layered overview of the test set up is shown in table 1. Table 1 Layer Entity Instance Video Codec ISO MPEG-4 Simple Profile or ITU-T H.263 Ver.2 Application Layer Speech Codec Dummy data Mux Layer Multiplexer De-multiplexer H.223/M (mobile extension of ITU-T H.223 multiplexing protocol) Physical Layer Simulated Wideband CDMA-channel Error pattern files bitrate: 32 Kbit/s, 64 Kbit/s and 128 Kbit/s channel error condition BER: 1e-3, 1e-4 and 1e-6 velocity (model): 3km/h (Vehicular-A) and 120km/h (Vehicular-A) 5.2.3 Results The results presented below should be used carefully. The subjective evaluation performed by ARIB provides good insight into the quality aspects of 3G-324M. However, attention should be paid to the following shortcomings: the test lacks a well known reference which makes it hard to asses the absolute picture quality furthermore the test methodology for low quality video is not very well developed which might be the reason for the high deviation in the results. ETSI ETSI TR 126 912 V3.0.0 (2000-03) 12 3G TR 26.912 version 3.0.0 Release 1999 The objective results presented should also be used carefully. It is very hard to map objective measurements to subjective quality. However high objective quality generally does mean that the subjective quality is good and vice versa. 5.2.3.1 Subjective results The following graphs are built from a subset of the data found in table in Clause B.6 of Annex B. Each codecs shown in the graphs had been tested for every error cases for each channel bit-rate. Since the evaluation lacked a known reference the MOS-values should be used very carefully. It is not the absolute value that is interesting but more the tendency. For all three of the following graphs are the error channel described in the following way: M64-10-3 where: M means Mobile-to-Mobile Channel, it could also be an F for a Fix-to-Mobile channel 64 stands for the total bitrate on the channel i.e. 64 Kbit/s, 128 means 128 Kbit/s 10 is the interleaving depth in ms, other possibilities is 20 and 80 ms 3 bit-error-rate i.e. 10e-3, other tested bit-error-rates are 10e-4 and 10e-6 Results from two different sequences are shown: Overtime and Australia. Overtime is a typical "head and shoulder" scene while Australia is a multi-person conference scene with camera motion. The later is known, from the MPEG4 verification tests, to be difficult to code. The Overtime sequence has QCIF and the Australia CIF resolution. The coded video frame rate was not fixed in the test, however most of the experimenter used a frame rate around 10 Hz. Full information about the test to be found in Annex B. MOS versus bit-error-rate, 64kps, Overtime 1 1,5 2 2,5 3 3,5 4 4,5 5 F64-10-6 M64-10-6 F64-20-4 M64-20-4 F64-10-3 M64-10-3 MPEG4 simple profile, H.223 Level 1, 8kbps Audio MPEG4 Simple profile, H.223 Level 2, 8kbps Audio H.263 Annex D, F, I, J, N, T, H.223 Level 2, 7.6 kbps Audio MPEG4 simple profile, H.223 Level 2, 7.6 kbps Audio H.263 Annex D, F, N, R, H.223 Level 2, 6.4 kbps Audio MPEG4 simple profile, H223 Level 3, 8.12 kbps Audio Figure 3 ETSI ETSI TR 126 912 V3.0.0 (2000-03) 13 3G TR 26.912 version 3.0.0 Release 1999 Mos versus bit-error-rate, 64kps, Australia 1 1,5 2 2,5 3 3,5 4 4,5 5 F64-10-6 M64-10-6 F64-20-4 M64-20-4 F64-10-3 M64-10-3 H.263 Annex D, F, I, J, N, T, H.223 Level 2, 7.6 kbps Audio MPEG4 simple profile, H.223 Level 2, 7.6 kbps MPEG4 simple profile, H.223 Level 3wRS, 8 kbps Figure 4 MOS versus bit-error-rate, 128 kps, Australia 1 1,5 2 2,5 3 3,5 4 4,5 5 F128-10.-6 M128-10-6 F128-20-4 M128-20-4 F120-10-3 M128-10-3 MPEG4 simple profile,H.223 Level 2, 8 kbps Audio MPEG4 simple profile,H.223 Level 3wRS, 8 kbps Audio Figure 5 ETSI ETSI TR 126 912 V3.0.0 (2000-03) 14 3G TR 26.912 version 3.0.0 Release 1999 As a comparison to the subjective results above, some objective data are presented for the same test cases. The tested sequence is Australia, two different bitrates are used (64 and 128 Kbit/s). Graphs for both Fix-to-Mobile and Mobile-to- Mobile are shown. In these results, three different multiplex levels of H.223 were used for each condition. The description of the error channel is the same as 5.3.2.1. Additional description for multiplex levels is as following: Lv2o: Level 2 with optional header, Lv3r4: Level 3 with FEC (convolutional code with a rate of 8/12), Lv3rs8: Level 3 with FEC (Reed Solomon code with 8 symbol correction). 28 29 30 31 32 33 34 35 36 37 38 1.E-06 1.E-05 1.E-04 1.E-03 1.E-02 BER PS N R [d B] F64-lv2o F64-lv3r4 F64-lv3rs8 Figure 6: BER vs. PSNR performance (64 Kbit/s, Fix-to-Mobile) ETSI ETSI TR 126 912 V3.0.0 (2000-03) 15 3G TR 26.912 version 3.0.0 Release 1999 28 29 30 31 32 33 34 35 36 37 38 1.E-06 1.E-05 1.E-04 1.E-03 1.E-02 BER PSNR [dB F128-lv2o F128-lv3r4 F128-lv3rs8 Figure 7: BER vs. PSNR performance (128 Kbit/s, Fix-to-Mobile) 28 29 30 31 32 33 34 35 36 37 38 1.E-06 1.E-05 1.E-04 1.E-03 1.E-02 BER PSNR [dB M64-lv2o M64-lv3r4 M64-lv3rs8 Figure 8: BER vs. PSNR performance (64 Kbit/s, Mobile-to-Mobile) ETSI ETSI TR 126 912 V3.0.0 (2000-03) 16 3G TR 26.912 version 3.0.0 Release 1999 28 29 30 31 32 33 34 35 36 37 38 1.E-06 1.E-05 1.E-04 1.E-03 1.E-02 BER PSNR [dB M128-lv2o M128-lv3r4 M128-lv3rs8 Figure 9: BER vs. PSNR performance (128 Kbit/s, Mobile-to-Mobile) ETSI ETSI TR 126 912 V3.0.0 (2000-03) 17 3G TR 26.912 version 3.0.0 Release 1999 Annex A: Quality degradation as a function of the FER and RBER in presence of background noise The following diagrams are provided in complement to the AMR speech codec quality performance included in subclause 5.1. They show the quality degradation induced by the different speech codec modes as a function of the FER and RBER in presence of background noise (car noise in Figures A1a & A1b, street noise in Figures A2a & A2b and Office noise in Figures A3a & A3b). The same comments on the origin of the test results as provided in subclause 5.1 also apply to the following diagrams. A.1 Results in Car Noise: Perceived quality (DMOS) degradation as a function of the FER (FR Tests in Car Noise) -3.00 -2.50 -2.00 -1.50 -1.00 -0.50 0.00 0.50 0.001% 0.010% 0.100% 1.000% 10.000% 100.000% FER ∆ DM OS 12.2 10.2 7.95 FR 7.4 FR 6.7 FR 5.9 FR 5.15 FR 4.75 FR Perceived quality (DMOS) degradation as a function of the RBER (FR Tests in Car Noise) -3.00 -2.50 -2.00 -1.50 -1.00 -0.50 0.00 0.50 0.001% 0.010% 0.100% 1.000% 10.000% RBER ∆ DM OS 12.2 10.2 7.95 FR 7.4 FR 6.7 FR 5.9 FR 5.15 FR 4.75 FR Figure A.1a: Quality Degradation function of FER Figure A.1b: Quality Degradation function of RBER In car noise, no significant degradation is observed when the FER stays below 1% and the difference in quality between the different codecs is slightly amplified compared to the results clean speech. A.2 Results in Street Noise: Perceived quality (DMOS) degradation as a function of the FER (FR Tests in Street Noise) -3.00 -2.50 -2.00 -1.50 -1.00 -0.50 0.00 0.50 0.001% 0.010% 0.100% 1.000% 10.000% 100.000% FER ∆ DM OS 12.2 10.2 7.95 FR 7.4 FR 6.7 FR 5.9 FR 5.15 FR 4.75 FR Perceived quality (DMOS) degradation as a function of the RBER (FR Tests in Street Noise) -3.00 -2.50 -2.00 -1.50 -1.00 -0.50 0.00 0.50 0.001% 0.010% 0.100% 1.000% 10.000% RBER ∆ DM OS 12.2 10.2 7.95 FR 7.4 FR 6.7 FR 5.9 FR 5.15 FR 4.75 FR Figure A.2a: Quality Degradation function of FER Figure A.2b: Quality Degradation function of RBER The results in street noise are in line with the previous results. ETSI ETSI TR 126 912 V3.0.0 (2000-03) 18 3G TR 26.912 version 3.0.0 Release 1999 A.3 Results in Office Noise Perceived quality (DMOS) degradation as a function of the FER (FR Tests in Office Noise) -3.00 -2.50 -2.00 -1.50 -1.00 -0.50 0.00 0.50 0.001% 0.010% 0.100% 1.000% 10.000% 100.000% FER ∆ DM OS 12.2 10.2 7.95 FR 7.4 FR 6.7 FR 5.9 FR 5.15 FR 4.75 FR Perceived quality (DMOS) degradation as a function of the RBER (FR Tests in Office Noise) -3.00 -2.50 -2.00 -1.50 -1.00 -0.50 0.00 0.50 0.001% 0.010% 0.100% 1.000% 10.000% RBER ∆ DM OS 12.2 10.2 7.95 FR 7.4 FR 6.7 FR 5.9 FR 5.15 FR 4.75 FR Figure A.3a: Quality Degradation function of FER Figure A.3b: Quality Degradation function of RBER Same comment for the results in Office Noise ETSI ETSI TR 126 912 V3.0.0 (2000-03) 19 3G TR 26.912 version 3.0.0 Release 1999 Annex B: Simulation test of a video multimedia codec B.1 Introduction This Annex describes the simulation test of a real time, bi-directional video multimedia codec. It is a shorter version of the "Report of ARIB IMT-2000 Video Multimedia Codec Simulation Test" found in reference [2]. The purpose of the test is to clarify the relationship between source/channel codec parameters and the channel QoS (Quality of Service) parameters of available bearer channel set. While the source and channel codecs are specified with algorithms, tools, options and parameters, the channel QoS parameters include bitrate, BER (bit error rate) and delay. Resulting video associated with a certain combination of source/channel codec parameters and the channel QoS parameters is subjectively evaluated in terms of quality. Twelve experimenters, that is, companies conducted the simulations. The experimenters individually and independently carry out the simulation using video codec and multiplexer prepared by each organization. B.2 Test Procedure B.2.1 Simulation Model The system configuration of the simulation model for these experiments is depicted in Figure B.1. ETSI ETSI TR 126 912 V3.0.0 (2000-03) 20 3G TR 26.912 version 3.0.0 Release 1999 Multiplexer (MUX) Simulated Channel Error Injector (1e-3/1e-4/1e-6, 1 Radio Link/2 Radio Links) De-Multiplexer (DEMUX) Adaptation Layer (AL2) Dummy Speech Data Generator Adaptation Layer (AL2) De-Multiplexed Speech Data Speech Application Layer Application Layer MUX Layer MUX Layer Physical Layer Video Encoder MPEG-4 SP/ H.263 Ver. 2 Adaptation Layer (AL3) Video Source Sample Adaptation Layer (AL3) Video Decoder MPEG-4 SP/ H.263 Ver. 2 Decoded Video Sample Video back Figure B.1: System configuration of simulation model This model is a typical example of mobile multimedia communication systems, and consists of the following three layers as shown in Table B.1. Table B.1: Layer structure of simulation model Layer Entity Instance Video Codec ISO MPEG-4 Simple Profile or ITU-T H.263 Ver.2 Application Layer Speech Codec dummy data Mux Layer Multiplexer De-multiplexer H.223/M (mobile extension of ITU-T H.223 multiplexing protocol) Physical Layer IMT-2000 Air- Interface spec. (Vol. 3 Ver. 0.5) error pattern files - bitrate: 32kbps, 64kbps and 128kbps - channel error condition BER: 1e-3, 1e-4 and 1e-6 - velocity (model): 3km/h (Vehicular-A) and 120km/h (Vehicular-A) The simulation is generally carried out as follows: 1) source video sequences come into a video encoder, 2) speech dummy data and video bitstreams are generated, ETSI ETSI TR 126 912 V3.0.0 (2000-03) 21 3G TR 26.912 version 3.0.0 Release 1999 3) the bitstreams are multiplexed into a single multiplexed bitstream in the form of MUX-PDU, 4) bit errors are injected into the multiplexed bitstream ('1' in error pattern file represents error), 5) contaminated bitstream is de-multiplexed into speech and video bitstreams, 6) de-multiplexed video bitstream is decoded by a video decoder, 7) decoded video sequences are evaluated subjectively. B.2.2 Source materials In the simulation two video sequences as shown in Table B.2 are used. Table B.2: Video source material Feature Name Provider Spatial Resolution Temporal Resolution Length [sec] Service assumed Motion Scene Change Overtime NTT DoCoMo QCIF*1 30 fps 60 video telephony low no Australia France Telecom QCIF*1 or CIF*2 25 fps 60 (72*3) video conference middle twice NOTE *1 QCIF: 176 (width) x 144 (height), 4:2:0 chroma format. *2 CIF : 352 (width) x 288 (height), 4:2:0 chroma format. *3 Australia is handled as 60 sec sequence of 30 fps, though it's originally 72 sec of 25 fps. B.2.3 Source encoding Clause B.5 shows the list of video/speech codecs and multiplexers employed by experimenters for the simulation. B.2.3.1 Speech Dummy random data, which are generated by each experimenter, are used to simulate encoded speech bitstream. The assumed coding bitrate and frame lengths of dummy speech data are left at the experimenter's discretion. B.2.3.2 Video Either ISO MPEG-4 Video Simple Profile or ITU-T H.263 Ver. 2 is employed as a video codec. There are some optional tools and parameters that can be set at the encoder for both specifications. Each experimenter taking speech coding bitrate and MUX overhead into account shall decide the bitrate allocated to video coding. A typical example is 8 kbps speech, 48 kbps video and 8 kbps MUX overhead, which results in 64 kbps in total. Some coding parameters are fixed to facilitate the simulation and demonstration by reducing the number of simulation conditions: 1) coding bitrate; 32 kbps and 64 kbps for Overtime, 64 kbps and 128 kbps for Australia, 2) spatial resolution of test sequence; QCIF for Overtime, CIF for Australia 128 kbps coding, and QCIF or CIF for Australia 64 kbps coding, 3) initial frame alignment; the 1st frame of test sequence shall be encoded as 1st intra-coded frame. It is noted that coding frame rate is left at the experimenter’s discretion. ETSI ETSI TR 126 912 V3.0.0 (2000-03) 22 3G TR 26.912 version 3.0.0 Release 1999 B.2.4 Multiplexing ITU-T H.223/M (mobile extension) with its annexes namely Annex A, Annex B, Annex C and Annex D is used as a multiplexing protocol. As for the adaptation layer, AL3 is used for video and AL2 for speech. The use of the optional tools like control field, re-transmission and the optional header field in the Annex B is up to the experimenters. B.2.5 Bit error injection B.2.5.1 Error pattern files The bit error patterns are generated based on Vol. 3 Ver. 0.5 (ARIB IMT-2000 A/IF specification) [1] issued on Nov. 18 th, 1998 [Ed. Note, This is a WCDMA channel]. The frame structure of the bit error file is shown in Figure B.2, which is identical to the air channel frame assumed. The frame is in 10-msec unit, and each frame is composed of CRC (16 bits) and INFO bits (10-msec worth of user bitrate). The multiplexed or encoded bitstream is assumed to be transmitted as INFO bits on a frame basis. The 16-bit CRC is originally designed to detect errors in the corresponding INFO bits at the physical layer. It can, however, be exploited at the application layer (e.g., source codec and MUX). In this simulation, the CRC is not used, hence, the 16-bit CRC should be merely discarded. It shall be noted that the CRC may be able to improve the performance of use applications. This is left for further study. CRC 16 INFO Nch_info CRC 16 INFO Nch_info CRC 16 INFO Nch_info Frame unit (10ms) given Bit Error Pattern Ncodec_info Ncodec_info INFO Ncodec_info INFO Ncodec_info Bit Errors added to Encoded bit- stream. Figure B.2: Frame structure of bit error pattern file The bit error patterns in binary format are then provided as summarized in Table B.3. Among them, the error pattern files of Vehicular-A, 120km/h propagation model are used for the test of mobile-to-land mode. The mobile-to-mobile (M2M) error pattern files weren't provided. M2M files was thus generated by XORing (exclusive OR) forward link and reverse link appropriately. Unfortunately reverse link files are available only for 32kbps, 1e-3 case. Therefore, error pattern of M2M mode are synthesized by XORing two forward link files that are the same in bitrate, BER and interleave length but only differ in propagation model. The two propagation models used are 3km/h and 120km/h of vehicular-A. Table B.3: Bit error pattern files Radio Channel Type Ref. File Name FL/ RL Bitrate [kbps] Interleave Size [msec] BER File Length [sec] Speed [km/h] Propagation model Eb/Io [dB] SG4/VMG File# F32-10-3-V3a FL 32 10 1e-3 300 3 Veh-A 2.57 SG4-7 F32-10-3-V120a 120 Veh-A 3.93 SG4-10 F32-20-4-V3 20 1e-4 300 3 Veh-A 2.59 VMG-1 F32-20-4-V120 120 Veh-A 3.90 VMG-2 F32-10-6-V3 10 1e-6 5000 3 Veh-A 3.96 SG4-41 F32-10-6-V120a 120 Veh-A 5.63 SG4-43 F32-80-6-V3 80 3 Veh-A 2.42 SG4-45 F32-80-6-V120a 120 Veh-A 3.66 SG4-47 F64-10-3-V3a 64 10 1e-3 300 3 Veh-A 2.18 SG4-13 F64-10-3-V120a 120 Veh-A 3.39 SG4-16 F64-20-4-V3 20 1e-4 300 3 Veh-A 2.16 VMG-3 F64-20-4-V120 120 Veh-A 3.47 VMG-4 ETSI ETSI TR 126 912 V3.0.0 (2000-03) 23 3G TR 26.912 version 3.0.0 Release 1999 Radio Channel Type Ref. File Name FL/ RL Bitrate [kbps] Interleave Size [msec] BER File Length [sec] Speed [km/h] Propagation model Eb/Io [dB] SG4/VMG File# F64-10-6-V3 10 1e-6 5000 3 Veh-A 3.63 SG4-25 F64-10-6-V120a 120 Veh-A 5.06 SG4-27 F64-80-6-V3 80 3200 3 Veh-A 2.00 SG4-29 F64-80-6-V120a 120 Veh-A 3.28 SG4-31 F128-10-3-V3 128 10 1e-3 300 3 Veh-A 0.93 VMG-5 F128-10-3-V120 120 Veh-A 2.21 VMG-6 F128-20-4-V3 20 1e-4 300 3 Veh-A VMG-7 F128-20-4-V120 120 Veh-A VMG-8 F128-10-6-V3 10 1e-6 3000 3 Veh-A 2.24 SG4-49 F128-10-6-V120a 120 Veh-A 3.91 SG4-51 F128-80-6-V3 80 1600 3 Veh-A 0.99 SG4-53 F128-80-6-V120a 120 Veh-A 1.98 SG4-55 R32-10-3-V3 RL 32 10 1e-3 300 3 Veh-A 2.48 VMG-9 R32-10-3-V120 120 Veh-A 3.86 VMG-10 B.2.5.2 Error pattern segments to be used at the simulation Multiple-run simulation leads to more reliable results. Therefore it was decided to use 20 runs per error pattern file, i.e., parent file. It should be noted that the successive processes namely de-multiplexing and source decoding are repeated 20 times accordingly. An extracted file is denoted "error pattern segment", so 20 error pattern segments (denoted as seg#0 - seg#19) are extracted from each error pattern file. Note that duration of error pattern segments must be identical to that of test sequence, hence, 60 seconds for both Overtime and Australia. These error pattern segments, which shall represent respective test condition, are extracted as follows. • In case of 1e-3 and 1e-4 BERs, 20 error pattern segments, initial frame of which are equally distributed over 5-min error pattern file, are extracted. Each segment is composed of successive frames in an error pattern file. The initial frame number of seg#0 is zero, and those of the following segments fall with fixed interval; 1200 frames (12 seconds). • In case of 1e-6 BER, an intermediate file of 20 segments worth length, whose actual BER is as close to 1e-6 as possible, is sought over an error pattern file. Then 20 segments are extracted from the intermediate file. The initial frame of seg#0 collocates that of the intermediate file. As to the rest, they are extracted in the way that seg#N (where N=1,...,19) immediately follows seg#N-1. • Firstly, 20 error pattern segments are extracted for each propagation model. The M2M error pattern segments are generated by XORing these extracted segments. In this process segment number must be matched, that is, XORing seg#N (where N=0,...,19) of 3km/h model and seg#N of 120km/h model yields seg#N of M2M model. B.2.5.3 Injection of bit errors To simulate the noisy channel, those bit errors are injected into multiplexed bitstream. This process is done by XOR in bit-wise fashion. But the initial error free period is tailored to protect the important part of the bitstream, since errors on such portion probably cause fatal damages in the source decoding process. Therefore the initial 100 bytes from the beginning of the multiplexed bitstream, which is denoted error-free period, are enforced to be error-free. So bit errors are injected immediately after the error-free period in multiplexed bitstream (Precisely the 1st bit of error patterns shall collocate 801st bit (both counting from one) of the multiplexed bitstream). If multiplexed bitstream is longer than error pattern segment plus 100 bytes, no error is applied to the tail part of the bitstream exceeding the length of error pattern segment plus 100 bytes. ITU-T H.245 Version 5 [5] is designed to perform a capability exchange prior to the transmission of data streams. With this technique, the initial error-free period can be realized by means of re- transmission. B.2.6 De-multiplexing The multiplexed bitstream is de-multiplexed at the receiver side. This process comes out with de-multiplexed speech bitstream and de-multiplexed video bitstream in the form of AL-SDU. Errors may be detected in some units of those bitstream with error detection capability of the multiplexing protocol. In that case it is up to the experimenter to decide ETSI ETSI TR 126 912 V3.0.0 (2000-03) 24 3G TR 26.912 version 3.0.0 Release 1999 whether erroneous AL-SDUs are delivered to the AL user, i.e., video decoder, or simply discarded. When erroneous AL-SDUs are delivered to respective AL user, it is possible that the AL user is notified of the presence of errors in delivered AL-SDU by the de-multiplexer B.2.7 Video decoding The de-multiplexed video bitstream is decoded. The video decoder has less freedom in selecting optional tools compared to the encoder, but has more freedom of operation outside of the standard, e.g., error detection, error recovery, error concealment and post processing. The use of these non-normative tools and proprietary schemes is up to the experimenters. To align the spatial resolution at subjective evaluation test, "Australia" sequence encoded at QCIF size shall be up-sampled to CIF size. Then "Overtime" and "Australia" sequences are displayed at the size of QCIF and CIF, respectively. For QCIF-to-CIF conversion, the up-sampling filter [FILTER] employed at MPEG-4 experiments is used. B.2.8 Constraints and regulations B.2.8.1 Delay In considering adequate combination of bearer radio channel and codec parameters, both channel and codec affect the delay. Therefore the delay constraints shall be investigated in both aspects simultaneously. Table B.4 summarizes the delay constraints to meet. It shall be noted that delay due to multiplexing/de-multiplexing heavily depends on the system configuration. Given that processing power of MUX related components are high enough, the delay at MUX layer can be absorbed into the video delay. So in the simulation, it is assumed that the delay at MUX layer is negligible, i.e., zero. Table B.4: Delay constraints Total allowable delay Allowable delay for air interface, network Allowable delay for codec and MUX Associated BER 10x2*,50 330 1e-3, 1e-6 20x2*,50 310 1e-4 400 ms 80x2*,50 190 1e-6 NOTE: * Multiplying by 2 means two links for mobile-to-mobile. B.2.8.1.1 Video The video delay is classified into two; initial delay and stationary delay. The former is defined with coding bits consumed at the 1st intra-coded frame, and is quantified by the coding bits divided by video coding bitrate. In the subjective test, when the initial delay exceeds 600 ms, mid-gray background is displayed with duration identical to the initial delay before presenting decoded video sequence. The latter is the one calculated based on the delay model described in B.2.9.8. It is, however, found difficult and impractical to always keep the stationary delay below the prescribed values shown in Table B.4 considering a variety of natures of input video sequences. While the experimenters are yet strongly encouraged to obey the above constraints, they are exceptionally allowed not to do. It is noted that such violation is admitted only when it is essential and rather practical than obeying the constraints. B.2.9 Statistical data to be reported The following items shall be reported on a test condition basis, i.e., one per error pattern file. ETSI ETSI TR 126 912 V3.0.0 (2000-03) 25 3G TR 26.912 version 3.0.0 Release 1999 B.2.9.1 Video coding bitrate [%6.2f kbps] and MUX overhead [%6.2f kbps] B.2.9.2 Speech coding bitrate [%6.2f kbps] and frame length [%d ms] B.2.9.3 Video initial delay [%6.1f ms] The video initial delay is calculated as coding bits for initial intra-coded frame divided by video coding bitrate B.2.9.4 PSNR related data The PSNRk,l (peak signal-to-noise ratio) of l-th frame at k-th run is defined as; ( ) ( ) ( ) = ∑ − = ∑ − = ∑ − = ∑ − = − + ∑ − = ∑ − = − + − 1 0 1 0 1 2 0 1 2 0 2 1 2 0 1 2 0 2 2 2 255 5 1 10 M i N j / M i / N j ) j ,i( b Cˆ ) j ,i( Cb / M i / N j ) j ,i(r Cˆ ) j ,i( Cr ) j ,i( Yˆ ) j ,i( Y ) ( * N * M * . log PSNR l k, where , , and , , indicate the three channels of the original and decoded frames, respectively, and M and N indicate the Y channel support for 4:2:0. Practically, M = 176 and N = 144 for QCIF format and M = 352 and N = 288 for CIF format B.2.9.4.1 Total average PSNR, i.e., PSNRtotal [%6.2f dB] Now at the decoder, let is_decoded(k, l) be a function which returns '1' if l-th frame at k-th run is decoded, and otherwise returns '0' representing "dropframe" (e.g., it occurs when a frame can't be reconstructed due to errors). Total average PSNR denoted by PSNRtotal is defined as; B.2.9.4.2 Average PSNR for representative run, i.e., PSNRk* [%6.2f dB] Firstly average PSNR at k-th run denoted by PSNRk is obtained; The representative run k* is chosen from among 20 candidates PSNRk, where k=0,...,19. The selection criterion is that PSNRk* is the one closest to PSNRtotal. B.2.9.4.3 Average PSNR in error-free case, i.e., PSNRfree [%6.2f dB] The average PSNR in error-free case represented by PSNRfree is obtained in the similar way above. To precisely define the term, it is the average PSNR calculated when decoding error-free video bitstream. B.2.9.4.4 Standard deviation of PSNR, i.e., Sigma [%6.2f dB] The Sigma is represented as; ∑ ∑ = = × × = 1799 0 19 0 20 l l, k k total ) l, k ( decoded _ is PSNR ) l, k ( decoded _ is PSNR ∑ = − = 19 0 2 19 k k total ) PSNR PSNR ( Sigma ∑ = × = 1799 0 l l, k k ) l, k ( decoded _ is PSNR ) l, k ( decoded _ is PSNR ETSI ETSI TR 126 912 V3.0.0 (2000-03) 26 3G TR 26.912 version 3.0.0 Release 1999 B.2.9.5 Coding frame rate [%5.2f frames/sec] Like is_decoded(k, l), let is_encoded( l) denote a function which returns '1' if l-th frame is encoded at the encoder, and otherwise returns '0'. The coding frame rate is expressed as; B.2.9.6 Average dropframe rate [%6.2f %] The average dropframe rate is defined as; B.2.9.7 Out of delay constraints rate [%6.2f %] Let is_outofdelay(l) represent a function which returns '1' if the delay constraints can not be observed at l-th frame, and otherwise returns '0'. Note is_outofdelay(l) is meaningful only when the l-th frame is encoded, i.e., is_encoded(l)=1. Now the out of delay constraints rate is defined as; B.2.9.8 Definition of video stationary delay The video stationary delay, Dn, for the n-th (n = 1, 2, ...) coded frame in the transmitted sequence is defined as follows (the delay model defined has no relation between the buffering model described in the MPEG-4 [3] or H.263 [4] specification): Dn = Tn - On, where On denotes the time when the n-th coded frame occurs, and Tn denotes the time when the last bit of the coded information related to the n-th coded frame is transmitted from the transmitting side. For example, when the video information is coded at the fixed bitrate of R bits/s, Dn is defined as follows: , where Bn is the number of transmitted bits for the n-th coded frame. The encoder shall encode a frame which occurred before the transmission of the information related to the previous coded frame is finished. This condition is described as: On ≤ Tn-1 . In the fixed bitrate case, this equation is rewritten as: R B O O n i i n ∑ − = + ≤ 1 1 1 . ∑ = = 1799 0 60 l ) l( encoded _ is rate _ frame _ coding ∑ ∑ = = − × = 1799 0 19 0 100 l k ) l( encoded _ is ) l, k ( decoded _ is ) l( encoded _ is rate _ dropframe _ average ∑ = × = 1799 0 100 l ) l( encoded _ is ) l( outofdelay _ is & ) l( encoded _ is rate _ s int constra _ delay _ of _ out ETSI ETSI TR 126 912 V3.0.0 (2000-03) 27 3G TR 26.912 version 3.0.0 Release 1999 B.2.9.9 Decoded video of representative run The decoded video sequence shall ideally be displayed as it is demonstrated using actual real time codec. It is, however, found difficult for all experimenters to tailor such real time codec. Therefore, experimenters shall submit the decoded video of representative run. For simplicity sake, the decoded video is displayed according to the time stamp of encoded frames, assuming the time stamp is not so much deviated from presentation time at decoder. B.3 Subjective quality evaluation The video subjective quality evaluation test is performed based on so-called SS-5DQS, that is, single stimulus (SS) method with a 5-point discrete quality scale (5DQS) referred to as ITU-R BT 500-8. However, the test is not designed to be fully compliant to SS-5DQS, but is rather simplified. There are five grades; excellent, good, fair, poor and bad. It shall be noted that the grading is made under the assumption that those video sequences, hence, associated video codecs are employed for prospective IMT-2000 mobile terminals. In this context, LCD monitors are employed as display since the mobile terminal for video related services will most likely be equipped with LCD monitors. B.3.1 Structure of test B.3.1.1 Program The subjective test is composed of several programs. A program is designed to be 20-40 minute long taking account of concentration duration of test subjects. A program is comprised of a training session followed by a scoring session. "Overtime" and "Australia" are handled separately in this level. B.3.1.2 Training session In order for test subjects to establish their own criteria on video subjective quality, a training session is tailored prior to actual evaluation. A training session consists of five video sequences, and there are two training sessions; one for "Overtime" and another for "Australia". These two are commonly used to every program in respective category. No score is put to sequences in a training session. A training session begins with 5-second indication notifying the beginning of the session. 5-second break is inserted between video sequences. B.3.1.3 Scoring session A scoring session is composed of multiple sequences, all of which are to be subjectively assessed. 10-second break is inserted between successive sequences. Test subject should mark a grade to a sequence during break which immediately follow the said sequence. B.3.1.4 Video sequence A video sequence, or sequence, represents a series of decoded images which is of 1-minute long. B.3.1.5 Structure of program A structure of a program is given in Table B.5. ETSI ETSI TR 126 912 V3.0.0 (2000-03) 28 3G TR 26.912 version 3.0.0 Release 1999 Table B.5: Structure of program Session Components Contents Duration [s] Time elapsed Indication training session 5 training #1 video sequence 60 Break gray image 5 training #2 video sequence 60 Break gray image 5 Training training #5 video sequence 60 5’25" indication scoring session 10 evaluation #1 video sequence 60 score and break gray image 10 evaluation #2 video sequence 60 score and break gray image 10 evaluation #23* video sequence 60 Scoring score gray image 10 32’25" NOTE The total number of sequences in a scoring session ranges from 21 to 23 depending on program. B.3.2 Editing process The decoded video sequences submitted by experimenters are to be edited, i.e., re-organized complying with a simplified SS-5DQS method. B.3.2.1 Producing training session Five sequences, each for "Overtime" and "Australia", are to be picked up. Two extremes, one in the best quality class and one in the worst quality class shall be included in a training session. The other three are to be picked up covering various classes in video quality. B.3.2.2 Randomization "Overtime" and "Australia" sequences are dealt with separately, and those related programs are denoted like "O1" which represents the first program of "Overtime". Firstly the number of programs are determined taking account of the total number of sequences. Since there are 91 and 64 sequences for "Overtime" and "Australia", respectively, 4 programs for "Overtime" and 3 programs for "Australia" are generated. Secondly sequential number is put to sequences properly. Then video sequences are classified into those programs using random numbers. B.3.3 Assessment B.3.3.1 Test subjects According to an ITU-R recommendation, reliable MOS data can be obtained with 10 expert test subjects or with 20 non-expert test subjects or more. In this test, 15 (12 experts, 1 semi-expert and 2 non-experts)and 14 (11 experts, 2 semi-experts and 1 non-expert) test subjects are employed for evaluation of Overtime and Australia sequences, respectively. ETSI ETSI TR 126 912 V3.0.0 (2000-03) 29 3G TR 26.912 version 3.0.0 Release 1999 Table B.6: Time schedule of test Time Test Subject Group A Test Subject Group B Test Administrators 09:20 – 10:10 Equipment Set-up 10:10 – 10:30 Explanation of the Test Preparation for O1 10:33 – 11:06 Evaluation (Program O1) Break 11:06 – 11:12 Break Preparation for A1 11:12 – 11:44 Evaluation (Program A1) 11:44 – 11:52 Lunch Break Preparation for O2 11:52 – 12:25 Evaluation (Program O2) 12:25 – 13:00 Lunch Break Preparation for A2 /XQFK 13:00 – 13:33 Evaluation (Program A2) 13:33 – 13:40 Break Preparation for O3 13:40 – 14:13 Evaluation (Program O3) 14:13 – 14:20 Break Preparation for A3 14:20 – 14:53 Evaluation (Program A3) 14:53 – 15:00 Dismissal (after above) Preparation for O4 15:00 – 15:33 Evaluation (Program O4) Dismissal (after above) 15:33 – 16:00 Equipment Take-down B.3.3.2 Facilities and equipment for test As many as 15 test subjects shall conduct the evaluation at the same time in the subjective test. From among several possible solutions the following equipment is deployed for the test. One set capable of handing four LCD monitors (including one parent PC) is composed of; 1) one high-performance PC, 2) one Dsub15-to-BNC video interface (Umezawa, ITF-400), 3) one 1BNC-to-3BNC video splitter (Umezawa, UM-4700A), 4) three BNC-to-Dsub15 conversion boxes (Umezawa, ADA-400) and 5) three LCD monitors. Given that two test subjects share an LCD, two sets of above are necessary and can synchronously display video on up to 8 LCDs (including two parent PCs). B.3.3.3 Score sheet Score sheet is made on a program basis, and given to test subjects prior to each program. The format of score sheet is depicted in Figure B.3, which exemplifies the case of "A1-01" marked "Good" and "A1-02" marked "Fair". No. Excellent Good Fair Poor Bad A1-01 A1-02 Figure B.3: Format of score sheet (example of "A1-01" marked "Good" and "A1-02" marked "Fair" The following instruction is described on a score sheet; "Test subject shall subjectively judge how well quality of video sequence meets the quality test subject expects for IMT-2000 real time video communication services assumed. The best and worst quality sequences don't necessarily correspond to the grades excellent and bad, respectively." B.3.4 Data processing MOS (mean opinion score) and its standard deviation denoted by 1os are calculated and to be reported as subjective test results. ETSI ETSI TR 126 912 V3.0.0 (2000-03) 30 3G TR 26.912 version 3.0.0 Release 1999 B.3.4.1 MOS [%4.2f] Let M and OS[i] denote the number of test subjects and the opinion score of i-th test subject. Note that OS[i] is associated with integers as below and so converted. Excellent: 5 / Good: 4 / Fair: 3 / Poor: 2 / Bad: 1 Now the MOS is calculated as; B.3.4.2 Standard deviation of OS, i.e., os [%4.2f] The standard deviation of OS (opinion score) is expressed as; B.4 Test results and observations B.4.1 Test results The test results including both opinion scores and statistical data are shown in the table of in clause B.6. Both the subjective test results and statistical data obtained through the simulation test are tabulated there in terms of channel type. B.4.2 Observations The characteristics of the residual errors on the simulated channels are considerably different from that of the ARIB IMT-2000 first video multimedia codec simulation test conducted in May-June 1998. The error density in the residual error burst is significantly lower this time probably due to the use of Turbo Codes [OBSERVE]. The effects of the used error correcting code, the residual error characteristic and its influence on the multimedia codec system have to be further investigated. ∑ = = M i M ] i[ OS MOS 1 ∑ = − − = M i M ) MOS ] i[ OS ( 1 2 os 1 σ ETSI ETSI TR 126 912 V3.0.0 (2000-03) 31 3G TR 26.912 version 3.0.0 Release 1999 B.5 List of video/speech codecs and multiplexers employed in the simulation Item Sub-item A B C D E F Algorithm/profile MPEG-4 Simple Profile MPEG-4 Simple Profile MPEG-4 Simple Profile MPEG-4 Simple Profile MPEG-4 Simple Profile MPEG-4 Simple Profile tools/options I-VOP P-VOP AC/DC Prediction Reversible VLC Slice Resynch Data Partitioning I-VOP P-VOP AC/DC Prediction Reversible VLC Slice Resynch Data Partitioning I-VOP P-VOP AC/DC Prediction Reversible VLC Slice Resynch Data Partitioning Header Extension Code I-VOP P-VOP AC/DC Prediction Reversible VLC Slice Resynch Data Partitioning Header Extension Code I-VOP P-VOP AC/DC Prediction Reversible VLC Slice Resynch Data Partitioning Header Extension Code I-VOP P-VOP AC/DC Prediction Reversible VLC Slice Resynch Data Partitioning Video coding rate control MPEG-2 TM-5 step2 used (variable frame rate) used Used used ITU-T H.263 tmn8 based Algorithm/level ITU-T H.223 Level 2/3 ITU-T H.223 Level 2 ITU-T H.223 Level 1/2*1 ITU-T H.223 Level 3 ITU-T H.223 Level 2 ITU-T H.223 Level 2 tools/options optional header optional header optional header optional header interleave (for Annex C) no optional header no optional header Multiplexing Back channel model N/A N/A N/A N/A N/A N/A Speech coding (dummy data) bit rate/frame length 6.4kbps/30ms 8.0kbps/20ms 4.0kbps/20ms 8.0kbps/10ms 7.67, 7.94, 8.09, 8.12kbps, /10ms 8.0kbps/30ms 6.4kbps/30ms Item Sub-item G H I J K L Algorithm/profile H.263 Ver.2 MPEG-4 Simple Profile MPEG-4 Simple Profile H.263 Ver.2 MPEG-4 Simple Profile MPEG-4 Simple Profile tools/options Annexes: D, F, I, J, N, T I-VOP P-VOP AC/DC Prediction Reversible VLC Slice Resynch Data Partitioning I-VOP P-VOP AC/DC Prediction Reversible VLC Slice Resynch Data Partitioning Header Extension Code Annexes: D, F, N, R I-VOP P-VOP AC/DC Prediction Reversible VLC Slice Resynch Data Partitioning Header Extension Code I-VOP P-VOP AC/DC Prediction Reversible VLC Slice Resynch Data Partitioning Header Extension Code Video coding rate control ITU-T H.263 TMN 5 ITU-T H.263 TMN 5 TMN5 H.263 TMN-6 used used Algorithm/level ITU-T H.223 Level 2 ITU-T H.223 Level 2 ITU-T H.223 Level 3wRS ITU-T H.223 Level 2 ITU-T H.223 Level 1/2*1 ITU-T H.223 Level 2/3/3wRS tools/options no optional header no optional header optional header no optional header optional header optional header Multiplexing Back channel model H.245 videoFastUpdateGOB and videoFastUpdatePicture H.245 videoFastUpdatePicture N/A H.263 Annex N separate logical channel mode*2 N/A N/A Speech coding (dummy data) bit rate/frame length 7.6kbps/20ms 7.6kbps/20ms 8.0kbps/20ms 6.4kbps/30ms 8.0kbps/10ms 6.4kbps/30ms Note: *1: EI (error indication) is generated at AL3 and sent to video decoder together with video bitstream assuming AL-SDU is of fixed length and the length is known to both video encoder and decoder. *2: Error pattern of forward-channel is hypothetically applied to back-channel. The separate logical channel mode specified in H.223 Annex N option delivers the back-channel message through the dedicated logical channel. As to the delay due to the back-channel, it is almost zero at the codec, and is assumed to be the duration to transmit the maximum MUX-PDU considering the worst case at multiplexer. ETSI ETSI TR 126 912 V3.0.0 (2000-03) 32 3G TR 26.912 version 3.0.0 Release 1999 B.6 Test results subjective test results experimenter's choice statistical data at encoder/multiplexer statistical data at decoder/de-multiplexer Channel type MUX audio bitrate audio frame length MUX overhead picture spatial resolution video bitrate coding frame rate video initial delay out of delay constraints PSNRfree PSNRtotal PSNRk* Sigma average drop frame rate Video Sequence LinkRate- IL-BER MOS •os H.223 Level [kbps] [ms] [kbps] QCIF or CIF [kbps] [frames/s] [ms] [%] [dB] [dB] [dB] [dB] [%] Overtime F32-10-3 1.33 0.49 2 4.00 20 4.01 QCIF 24.01 8.02 489.0 0.00 33.72 32.02 31.98 0.47 2.37 1.60 0.63 2 6. 40 30 6. 58 QCIF 19. 02 8.40 591.6 0.02 31.86 31.34 31.35 0.09 0.00 R32-10-3 1.87 0.52 2 4.00 20 4.01 QCIF 24.01 8.02 489.0 0.00 33.72 30.55 30.51 0.50 4.68 M32-10-3 1.13 0.52 2 4.00 20 4.01 QCIF 24.01 8.02 489.0 0.00 33.72 31.92 31.93 0.45 2.12 1.00 0.00 2 6.40 30 6.58 QCIF 19.02 8.34 591.6 0.02 31.86 30.92 30.91 0.15 0.00 F32-20-4 1.47 0.52 2 6.40 30 2.60 QCIF 20.67 7.50 454.0 0.00 31.56 28.68 28.42 2.72 0.10 2.33 0.72 2 4.00 20 4.01 QCIF 24.01 8.02 489.0 0.00 33.72 33.50 33.49 0.17 0.26 1.87 0.35 2 6.40 30 6.59 QCIF 19.01 8.47 591.6 0.03 31.86 31.78 31.78 0.05 0.00 M32-20-4 1.33 0.49 2 6.40 30 2.60 QCIF 20.67 7.50 454.0 0.00 31.56 28.17 28.52 3.17 1.05 2.13 0.64 2 4.00 20 4.01 QCIF 24.01 8.02 489.0 0.00 33.72 33.32 33.32 0.25 0.64 1.80 0.56 2 6.40 30 6.59 QCIF 19.01 8.46 591.6 0.03 31.86 31.71 31.71 0.08 0.00 F32-10-6 2.53 0.52 1 4.00 20 3.17 QCIF 25.05 8.33 469.4 0.00 33.83 33.83 33.83 0.00 0.00 2.20 0.41 2 6.40 30 2.60 QCIF 20.69 7.50 454.0 0.00 31.57 31.56 31.57 0.04 0.00 2.33 0.62 2 6.40 30 6.59 QCIF 19.01 8.45 591.6 0.02 31.86 31.86 31.86 0.01 0.00 F32-80-6 2.47 0.64 1 4.00 20 3.16 QCIF 25.03 10.58 469.4 0.00 33.15 33.15 33.15 0.01 0.01 1.93 0.70 2 6.40 30 2.60 QCIF 20.61 7.50 454.0 0.01 31.52 31.22 31.44 1.29 0.35 1.93 0.46 2 6.40 30 6.59 QCIF 19.01 8.45 591.6 0.06 31.86 31.85 31.86 0.02 0.00 M32-10-6 2.33 0.49 1 4.00 20 3.17 QCIF 25.05 8.33 469.4 0.00 33.83 33.83 33.83 0.01 0.01 2.60 0.63 2 6.40 30 2.60 QCIF 20.69 7.50 454.0 0.00 31.57 31.56 31.57 0.04 0.00 1.93 0.59 2 6.40 30 6.59 QCIF 19.01 8.46 591.6 0.02 31.86 31.86 31.86 0.01 0.00 M32-80-6 2.53 0.74 1 4.00 20 3.16 QCIF 25.03 10.58 469.4 0.00 33.15 33.15 33.15 0.01 0.02 1.93 0.46 2 6.40 30 2.60 QCIF 20.61 7.50 454.0 0.01 31.52 30.91 31.38 1.82 0.70 1.87 0.64 2 6.40 30 6.59 QCIF 19.01 8.45 591.6 0.06 31.86 31.85 31.86 0.03 0.00 F64-10-3 2.80 0.77 2 8.00 20 3.20 QCIF 52.80 9.65 384.0 0.86 35.02 32.55 32.52 1.06 0.04 2.53 0.99 2 8.00 10 8.03 QCIF 48.06 11.63 475.0 0.00 35.40 33.90 33.89 0.29 2.66 1.67 0.62 2 7.60 20 7.06 QCIF 49.34 9.31 463.8 0.21 36.77 32.88 32.94 0.77 1.65 1.93 0.46 2 7.60 20 8.63 QCIF 47.77 9.11 482.8 0.43 34.90 32.86 32.85 0.46 1.96 1.87 0.64 2 6.40 30 6.56 QCIF 51.04 9.06 300.4 0.00 36.04 34.87 34.86 0.19 0.00 1.60 0.51 2 6.40 30 5.08 QCIF 46.88 7.48 582.08 0.01 31.58 28.54 28.28 1.34 0.70 ETSI ETSI TR 126 912 V3.0.0 (2000-03) 33 3G TR 26.912 version 3.0.0 Release 1999 subjective test results experimenter's choice statistical data at encoder/multiplexer statistical data at decoder/de-multiplexer Channel type MUX audio bitrate audio frame length MUX overhead picture spatial resolution video bitrate coding frame rate video initial delay out of delay constraints PSNRfree PSNRtotal PSNRk* Sigma average drop frame rate Video Sequence LinkRate- IL-BER MOS •os H.223 Level [kbps] [ms] [kbps] QCIF or CIF [kbps] [frames/s] [ms] [%] [dB] [dB] [dB] [dB] [%] 1.87 0.64 3 8.12 10 32.65 QCIF 24.27 6.25 599.0 11.47 33.39 31.86 31.85 0.60 6.99 1.40 0.51 3 6.40 30 20.10 QCIF 34.07 7.42 561.371 0.07 30.69 28.11 28.46 1.31 0.29 1.60 0.63 3wRS 6.40 30 20.33 QCIF 34.07 7.42 561.371 0.07 30.69 28.41 28.39 1.33 0.30 M64-10-3 1.87 0.64 2 8.00 20 3.20 QCIF 52.80 9.65 384.0 1.21 35.02 30.99 30.89 1.00 0.00 1.53 0.52 2 8.00 10 8.03 QCIF 48.06 11.63 475.0 0.00 35.40 32.91 32.90 0.28 4.99 1.33 0.49 2 7.60 20 7.04 QCIF 49.36 9.30 463.5 0.22 36.77 31.57 31.55 0.83 2.80 1.13 0.35 2 7.60 20 8.53 QCIF 47.87 9.14 465.4 0.41 34.90 31.08 30.97 1.13 3.03 1.60 0.51 2 6.40 30 6.56 QCIF 51.04 9.06 300.4 0.00 36.04 34.20 34.20 0.15 0.00 1.47 0.64 2 6.40 30 5.08 QCIF 46.88 7.48 582.0 0.01 31.58 25.90 25.42 1.49 1.25 1.60 0.63 3 8.12 10 32.65 QCIF 24.27 6.25 599.0 11.47 33.39 31.85 31.89 0.55 6.89 1.27 0.59 3 6.40 30 20.10 QCIF 34.07 7.42 561.371 0.07 30.69 26.31 26.68 1.36 0.46 1.40 0.51 3wRS 6.40 30 20.33 QCIF 34.07 7.42 561.371 0.07 30.69 27.77 28.17 1.29 0.48 F64-20-4 3.33 0.62 2 8.00 20 3.20 QCIF 52.80 9.65 384.0 1.21 35.02 34.60 34.54 0.66 0.00 2.87 0.92 2 8.00 10 8.03 QCIF 48.06 11.63 475.0 0.00 35.40 35.20 35.20 0.13 0.31 3.67 0.72 2 8.00 30 7.35 QCIF 48.07 10.40 545.3 1.44 38.74 37.58 37.41 0.81 0.06 2.93 0.88 2 7.60 20 6.84 QCIF 49.56 9.38 461.6 0.18 36.77 35.25 35.24 0.36 0.19 2.87 0.83 2 7.60 20 8.17 QCIF 48.23 9.23 473.6 0.33 34.90 34.40 34.38 0.78 0.47 3.47 0.64 2 6.40 30 6.57 QCIF 51.03 9.05 300.4 0.00 36.04 35.89 35.89 0.09 0.00 3.40 0.74 2 6.40 30 5.08 QCIF 46.88 7.48 582.0 0.04 31.58 31.38 31.37 0.40 0.14 2.73 0.70 3 6.40 30 24.60 QCIF 32.39 7.50 325.0 0.00 33.87 31.32 32.81 3.18 2.80 2.80 0.68 3 8.12 10 32.50 QCIF 24.25 6.30 598.3 11.38 33.45 33.38 33.39 0.14 1.44 2.53 0.52 3 6.40 30 19.30 QCIF 33.00 7.40 561.371 0.11 30.83 30.70 30.67 0.39 0.06 2.60 0.63 3wRS 6.40 30 19.70 QCIF 33.00 7.40 561.371 0.11 30.83 30.81 30.81 0.14 0.00 M64-20-4 2.73 0.88 2 8.00 20 3.20 QCIF 52.80 9.65 384.0 2.76 35.02 34.21 34.25 0.82 0.00 3.07 0.88 2 8.00 10 8.03 QCIF 48.06 11.63 475.0 0.00 35.40 35.05 35.07 0.15 0.69 3.33 0.72 2 8.00 30 7.35 QCIF 48.07 10.40 545.3 1.44 38.74 36.08 36.24 1.75 0.17 2.73 0.70 2 7.60 20 6.95 QCIF 49.45 9.35 462.7 0.18 36.77 34.75 34.74 0.81 0.35 3.20 1.01 2 7.60 20 8.90 QCIF 47.50 9.08 485.6 0.35 34.90 34.32 34.35 0.22 0.72 3.40 0.74 2 6.40 30 6.56 QCIF 51.04 9.05 300.4 0.00 36.04 35.73 35.74 0.09 0.00 3.20 0.94 2 6.40 30 5.08 QCIF 46.88 7.48 582.0 0.04 31.58 30.64 30.81 1.05 0.19 2.60 0.51 3 6.40 30 24.60 QCIF 32.39 7.50 325.0 0.00 33.87 29.69 29.27 3.17 4.95 2.80 0.77 3 8.12 10 32.50 QCIF 24.25 6.30 598.3 11.38 33.45 33.22 33.19 1.88 2.20 2.07 0.96 3 6.40 30 19.30 QCIF 33.00 7.40 561.371 0.11 30.83 30.57 30.60 0.43 0.10 ETSI ETSI TR 126 912 V3.0.0 (2000-03) 34 3G TR 26.912 version 3.0.0 Release 1999 subjective test results experimenter's choice statistical data at encoder/multiplexer statistical data at decoder/de-multiplexer Channel type MUX audio bitrate audio frame length MUX overhead picture spatial resolution video bitrate coding frame rate video initial delay out of delay constraints PSNRfree PSNRtotal PSNRk* Sigma average drop frame rate Video Sequence LinkRate- IL-BER MOS •os H.223 Level [kbps] [ms] [kbps] QCIF or CIF [kbps] [frames/s] [ms] [%] [dB] [dB] [dB] [dB] [%] 2.87 0.74 3wRS 6.40 30 19.70 QCIF 33.00 7.40 561.371 0.11 30.83 30.72 30.71 0.28 0.01 F64-10-6 3.67 0.82 1 8.00 10 6.31 QCIF 50.04 15.63 490.2 0.00 34.42 34.35 34.35 0.00 0.01 3.60 0.99 2 8.00 20 3.20 QCIF 52.80 9.65 384.0 0.86 35.02 35.02 35.02 0.01 0.03 4.40 0.83 2 7.60 20 7.04 QCIF 49.37 9.53 500.8 0.17 36.77 36.73 36.74 0.09 0.00 3.87 1.06 2 7.60 20 8.17 QCIF 48.23 9.23 461.9 0.32 34.90 34.84 34.85 0.09 0.29 3.47 0.99 2 6.40 30 6.56 QCIF 51.04 9.05 300.4 0.00 36.04 36.04 36.04 0.01 0.00 3.20 0.77 3 6.40 30 24.60 QCIF 32.41 7.50 325.0 0.00 33.88 33.52 33.88 1.64 0.35 3.67 0.72 3 8.12 10 17.28 QCIF 39.50 6.53 530.5 8.42 36.49 36.49 36.49 0.03 0.00 F64-80-6 3.60 0.91 1 8.00 10 6.31 QCIF 50.04 15.63 490.2 0.00 34.42 34.35 34.35 0.01 0.01 3.67 0.90 2 8.00 20 3.20 QCIF 52.80 9.65 384.0 9.67 35.02 35.01 35.02 0.05 0.01 4.33 0.82 2 7.60 20 6.81 QCIF 49.59 9.58 498.5 1.67 36.77 36.65 36.65 0.17 0.12 3.93 0.80 2 7.60 20 8.45 QCIF 47.95 9.17 470.0 5.08 34.90 34.83 34.82 0.09 0.35 3.73 0.70 2 6.40 30 6.57 QCIF 51.03 9.05 300.4 0.00 36.04 36.03 36.04 0.03 0.00 2.60 0.63 3 6.40 30 24.60 QCIF 32.33 7.50 325.0 0.03 33.84 33.84 33.84 0.01 0.00 4.07 0.59 3 7.94 10 16.28 QCIF 39.30 6.65 518.6 16.79 36.31 36.31 36.31 0.00 0.00 M64-10-6 3.53 0.99 1 8.00 10 6.31 QCIF 50.04 15.63 490.2 0.00 34.42 34.35 34.35 0.01 0.01 4.40 0.83 2 8.00 20 3.20 QCIF 52.80 9.65 384.0 1.21 35.02 35.02 35.02 0.02 0.00 4.33 0.72 2 7.60 20 6.95 QCIF 49.45 9.55 499.9 0.17 36.77 36.74 36.73 0.07 0.01 3.87 0.74 2 7.60 20 8.67 QCIF 47.73 9.13 472.5 0.28 34.90 34.83 34.82 0.07 0.28 3.87 0.74 2 6.40 30 6.57 QCIF 51.03 9.05 300.4 0.00 36.04 36.04 36.03 0.01 0.00 3.13 0.74 3 6.40 30 24.60 QCIF 32.41 7.50 325.0 0.00 33.88 33.52 33.88 1.64 0.35 3.67 0.90 3 8.12 10 17.28 QCIF 39.50 6.53 530.5 8.42 36.49 36.46 36.48 0.08 0.00 M64-80-6 3.33 0.90 1 8.00 10 6.31 QCIF 50.04 15.63 490.2 0.00 34.42 34.35 34.35 0.02 0.02 3.60 0.99 2 8.00 20 3.20 QCIF 52.80 9.65 384.0 56.13 35.02 35.01 35.01 0.05 0.00 3.67 0.72 2 7.60 20 6.85 QCIF 49.55 9.58 498.9 1.47 36.77 36.37 36.29 0.65 0.02 3.80 0.94 2 7.60 20 8.39 QCIF 48.01 9.17 481.2 5.14 34.90 34.78 34.78 0.18 0.35 3.87 0.99 2 6.40 30 6.57 QCIF 51.03 9.05 300.4 0.00 36.04 36.01 36.03 0.05 0.00 2.53 0.64 3 6.40 30 24.60 QCIF 32.33 7.50 325.0 0.03 33.84 33.84 33.84 0.01 0.00 4.00 0.93 3 7.94 10 16.28 QCIF 39.30 6.65 518.6 16.79 36.31 36.30 36.31 0.02 0.00 Australia F64-10-3 1.21 0.43 2 6.40 30 4.65 CIF 52.38 6.45 389.0•. 0.0 33.49 29.40 29.99 2.00 1.52 1.64 0.63 2 7.60 20 7.01 QCIF 49.39 9.23 251.8 0.09 36.39 32.91 32.88 0.69 1.71 1.50 0.52 2 7.60 20 8.32 QCIF 48.08 9.13 228.8 0.23 35.05 32.31 32.31 1.14 1.89 1.50 0.52 3 7.67 10 30.39 QCIF 24.29 6.18 503.0 11.32 34.15 31.95 31.98 0.65 5.35 ETSI ETSI TR 126 912 V3.0.0 (2000-03) 35 3G TR 26.912 version 3.0.0 Release 1999 subjective test results experimenter's choice statistical data at encoder/multiplexer statistical data at decoder/de-multiplexer Channel type MUX audio bitrate audio frame length MUX overhead picture spatial resolution video bitrate coding frame rate video initial delay out of delay constraints PSNRfree PSNRtotal PSNRk* Sigma average drop frame rate Video Sequence LinkRate- IL-BER MOS •os H.223 Level [kbps] [ms] [kbps] QCIF or CIF [kbps] [frames/s] [ms] [%] [dB] [dB] [dB] [dB] [%] 1.93 0.62 3wRS 8.00 20 13.80 QCIF 42.01 9.92 237.3 0.00 34.73 33.12 33.02 1.06 0.01 M64-10-3 1.21 0.43 2 6.40 30 4.72 CIF 52.40 6.43 388.9 0.0 33.48 27.75 27.95 1.49 3.76 1.57 0.85 2 7.60 20 6.78 QCIF 49.62 9.29 250.5 0.13 36.39 31.30 31.25 0.68 2.90 1.57 0.65 2 7.60 20 8.37 QCIF 48.04 9.13 225.5 0.24 35.05 30.52 30.58 1.34 4.51 1.21 0.43 3 7.67 10 30.39 QCIF 24.29 6.18 503.0 11.32 34.15 31.72 31.71 0.63 5.60 1.57 0.65 3wRS 8.00 20 13.80 QCIF 42.01 9.92 237.3 0.00 34.73 32.25 32.29 1.03 0.15 F64-20-4 2.07 0.62 2 6.40 30 4.68 CIF 52.39 6.53 389.0 0.00 33.59 33.11 33.12 0.40 0.15 2.43 0.65 2 7.60 20 6.89 QCIF 49.51 9.26 251.1 0.07 36.39 35.37 35.39 0.33 0.30 2.43 0.65 2 7.60 20 8.17 QCIF 48.23 9.15 228.0 0.33 35.05 34.35 34.56 1.01 0.60 2.50 0.52 2 8.00 10 8.00 QCIF 48.29 9.80 441.8 1.36 36.88 34.09 34.14 1.92 0.40 2.07 0.62 3 8.09 10 32.42 QCIF 24.24 6.37 501.7 10.21 34.10 34.03 34.03 1.08 4.87 2.64 0.63 3wRS 8.00 20 13.80 QCIF 42.01 9.92 237.3 0.00 34.73 34.63 34.64 0.10 0.01 M64-20-4 1.79 0.58 2 6.40 30 4.71 CIF 52.36 6.45 389.2 0.00 33.58 32.53 32.54 0.76 0.34 2.79 0.58 2 7.60 20 6.72 QCIF 49.68 9.30 250.3 0.10 36.39 35.16 35.14 0.32 0.57 2.43 0.51 2 7.60 20 8.42 QCIF 47.98 9.13 229.2 0.18 35.05 34.38 34.38 0.41 0.79 2.07 0.73 2 8.00 10 8.00 QCIF 48.29 9.80 441.8 1.36 36.88 32.06 32.09 1.89 0.77 1.93 0.73 3 8.09 10 32.42 QCIF 24.24 6.37 501.7 10.21 34.10 33.91 33.91 1.35 6.24 2.14 0.86 3wRS 8.00 20 13.80 QCIF 42.01 9.92 237.3 0.00 34.73 34.52 34.51 0.14 0.05 F64-10-6 3.43 0.51 1 8.00 10 6.00 QCIF 50.37 9.98 524.4 0.17 37.93 37.75 37.84 0.78 0.01 3.29 0.61 2 7.60 20 6.86 QCIF 49.54 9.27 250.9 0.11 36.39 36.22 36.23 0.23 0.18 3.21 0.58 2 7.60 20 8.44 QCIF 47.96 9.12 234.5 0.18 35.05 35.05 35.06 0.09 0.26 2.43 0.51 3wRS 8.00 20 13.80 QCIF 42.01 9.92 237.3 0.00 34.73 34.73 34.73 0.00 0.00 F64-80-6 3.36 0.63 1 8.00 10 6.00 QCIF 48.52 9.82 544.5 5.94 37.79 37.74 37.79 0.16 0.00 3.00 0.68 2 7.60 20 6.87 QCIF 49.54 9.26 251.0 1.72 36.39 36.17 36.19 0.24 0.05 2.93 0.62 2 7.60 20 8.10 QCIF 48.30 9.17 235.7 4.46 35.05 35.05 35.05 0.08 0.46 2.43 0.51 3wRS 8.00 20 13.80 QCIF 42.01 9.92 237.3 0.00 34.73 34.73 34.73 0.00 0.00 M64-10-6 3.21 0.70 1 8.00 10 6.00 QCIF 50.37 9.98 524.4 0.17 37.93 37.73 37.76 0.78 0.01 3.21 0.70 2 7.60 20 6.75 QCIF 49.65 9.29 250.4 0.10 36.39 36.29 36.29 0.13 0.01 2.79 0.58 2 7.60 20 8.29 QCIF 48.11 9.12 232.2 0.36 35.05 35.03 35.05 0.09 0.60 2.57 0.65 3wRS 8.00 20 13.80 QCIF 42.01 9.92 237.3 0.00 34.73 34.73 34.73 0.00 0.00 M64-80-6 3.29 0.99 1 8.00 10 6.00 QCIF 48.52 9.82 544.5 5.94 37.79 37.54 37.51 0.56 0.03 3.50 0.52 2 7.60 20 6.66 QCIF 49.75 9.31 249.9 2.99 36.39 36.17 36-23 0.37 0.10 3.07 0.83 2 7.60 20 8.46 QCIF 47.94 9.12 232.9 4.86 35.05 35.02 35.01 0.09 0.32 ETSI ETSI TR 126 912 V3.0.0 (2000-03) 36 3G TR 26.912 version 3.0.0 Release 1999 subjective test results experimenter's choice statistical data at encoder/multiplexer statistical data at decoder/de-multiplexer Channel type MUX audio bitrate audio frame length MUX overhead picture spatial resolution video bitrate coding frame rate video initial delay out of delay constraints PSNRfree PSNRtotal PSNRk* Sigma average drop frame rate Video Sequence LinkRate- IL-BER MOS •os H.223 Level [kbps] [ms] [kbps] QCIF or CIF [kbps] [frames/s] [ms] [%] [dB] [dB] [dB] [dB] [%] 2.43 0.65 3wRS 8.00 20 13.80 QCIF 42.01 9.92 237.3 0.00 34.73 34.73 34.73 0.00 0.00 F128-10- 2.36 0.50 2 8.00 20 5.60 CIF 114.4000 7.42 394.0 1.57 34.65 31.72 31.42 2.25 0.00 1.50 0.52 2 6.40 30 11.17 CIF 110.51 9.62 184.4 0.00 35.30 30.19 30.23 1.55 0.98 2.14 0.53 3wRS 8.00 20 26.36 CIF 93.01 9.33 287.7 0.00 34.39 32.95 33.08 0.49 0.13 M128-10- 1.57 0.51 2 8.00 20 5.60 CIF 114.4000 7.42 394.0 2.02 34.65 30.06 29.82 1.62 0.00 1.21 0.43 2 6.40 30 7.85 CIF 111.97 9.63 182.0 0.00 35.39 28.71 29.11 1.67 1.44 1.64 0.50 3wRS 8.00 20 26.36 CIF 93.01 9.33 287.7 0.00 34.39 31.38 31.31 1.10 0.21 F128-20- 3.07 0.83 2 8.00 20 5.60 CIF 114.4000 7.42 394.0 2.02 34.65 33.89 33.47 0.73 0.00 2.57 0.51 2 6.40 30 7.86 CIF 112.03 9.73 181.9 0.00 35.48 34.52 34.54 0.39 0.11 2.36 0.84 2 8.00 10 8.00 CIF 112.70 9.72 495.3 2.06 36.27 30.27 30.25 1.77 0.79 3.36 0.84 3wRS 8.00 20 26.36 CIF 93.01 9.33 287.7 0.00 34.39 34.22 34.22 0.18 0.08 M128-20- 2.79 0.70 2 8.00 20 5.60 CIF 114.4000 7.42 394.0 6.74 34.65 33.43 33.16 0.68 0.00 2.50 0.76 2 6.40 30 7.92 CIF 112.00 9.68 181.9 0.00 35.43 33.66 33.91 0.49 0.21 1.36 0.50 2 8.00 10 8.00 CIF 112.70 9.72 495.3 2.06 36.27 28.23 28.23 2.02 1.68 3.36 0.74 3wRS 8.00 20 26.36 CIF 93.01 9.33 287.7 0.00 34.39 34.01 34.01 0.23 0.12 F128-10- 4.07 0.62 1 8.00 10 6.00 CIF 114.67 9.62 486.7 2.08 36.77 36.55 36.71 0.68 0.01 3.86 0.77 2 8.00 20 5.60 CIF 114.4000 7.42 394.0 1.57 34.65 34.64 34.63 0.05 0.00 3.50 0.65 3wRS 8.00 20 26.36 CIF 93.01 9.33 287.7 0.00 34.39 34.38 34.39 0.03 0.00 F128-80- 4.00 0.78 1 8.00 10 6.00 CIF 108.33 9.63 515.3 7.61 36.56 36.03 35.93 1.37 0.04 3.86 0.95 2 8.00 20 5.60 CIF 114.4000 7.42 394.0 29.44 34.65 34.62 34.59 0.10 0.00 3.29 0.73 3wRS 8.00 20 26.36 CIF 93.01 9.33 287.7 2.68 34.39 34.39 34.39 0.00 0.00 M128-10- 3.93 1.00 1 8.00 10 6.00 CIF 114.67 9.62 486.7 2.08 36.77 36.52 36.71 0.70 0.01 3.86 0.53 2 8.00 20 5.60 CIF 114.4000 7.42 394.0 2.02 34.65 34.64 34.63 0.05 0.00 3.29 0 3wRS 8.00 20 26.36 CIF 93.01 9.33 287.7 0.00 34.39 34.38 34.39 0.03 0.00 M128-80- 4.57 0.65 1 8.00 10 6.00 CIF 108.33 9.63 515.3 7.61 36.56 35.04 34.98 2.48 0.09 3.64 0.50 2 8.00 20 5.60 CIF 114.4000 7.42 394.0 91.69 34.65 34.61 34.61 0.10 0.00 3.57 0.65 3wRS 8.00 20 26.36 CIF 93.01 9.33 287.7 2.68 34.39 34.39 34.39 0.00 0.00 ETSI ETSI TR 126 912 V3.0.0 (2000-03) 37 3G TR 26.912 version 3.0.0 Release 1999 Annex C: Change history Change history TSG SA# Version CR Tdoc SA New Version Subject/Comment SA07 3.0.0 - SP-000019 3.0.0 Approved at TSG SA #7 and placed under Change Control 38 ETSI ETSI TR 126 912 V3.0.0 (2000-03) 3G TR 26.912 version 3.0.0 Release 1999 History Document history V3.0.0 March 2000 Publication
|
d07bfdf3244e1962a4c6191f126aee07
|
123 930
|
1 Scope
|
........................................................................................................................................................5
|
d07bfdf3244e1962a4c6191f126aee07
|
123 930
|
2 References
|
................................................................................................................................................5
|
d07bfdf3244e1962a4c6191f126aee07
|
123 930
|
3 Definitions, symbols and abbreviations
|
...................................................................................................5
|
d07bfdf3244e1962a4c6191f126aee07
|
123 930
|
3.1 Definitions
|
......................................................................................................................................................... 5
|
d07bfdf3244e1962a4c6191f126aee07
|
123 930
|
3.2 Symbols
|
............................................................................................................................................................. 6
|
d07bfdf3244e1962a4c6191f126aee07
|
123 930
|
3.3 Abbreviations
|
..................................................................................................................................................... 6
|
d07bfdf3244e1962a4c6191f126aee07
|
123 930
|
4 Iu requirements
|
........................................................................................................................................6
|
d07bfdf3244e1962a4c6191f126aee07
|
123 930
|
4.1 General Requirements
|
........................................................................................................................................ 6
|
d07bfdf3244e1962a4c6191f126aee07
|
123 930
|
4.2 UMTS Terrestrial Radio Access Network (UTRAN)
|
........................................................................................ 7 4.2.1 SRNS-Relocation....................................................................................................................................................... 8 4.2.2 Position for header compression................................................................................................................................ 8
|
d07bfdf3244e1962a4c6191f126aee07
|
123 930
|
4.3 UMTS Satellite Radio Access Network (USRAN)
|
........................................................................................... 8
|
d07bfdf3244e1962a4c6191f126aee07
|
123 930
|
4.4 Broadband Radio Access Network (BRAN)
|
..................................................................................................... 9
|
d07bfdf3244e1962a4c6191f126aee07
|
123 930
|
5 Access stratum vs. Non-access stratum
|
...................................................................................................9
|
d07bfdf3244e1962a4c6191f126aee07
|
123 930
|
6 Working Assumptions
|
.............................................................................................................................9
|
d07bfdf3244e1962a4c6191f126aee07
|
123 930
|
6.1 General
|
............................................................................................................................................................... 9
|
d07bfdf3244e1962a4c6191f126aee07
|
123 930
|
6.2 Interface and protocols over Iu for UTRAN purposes
|
....................................................................................... 9 History..............................................................................................................................................................10 ETSI TR 123 930 V3.0.0 (2000-01) (3G TR 23.930 version 3.0.0 Release 1999) ETSI 3GPP 3G TR 23.930 V3.0.0 (1999-07) 4 3G TR 23.930 version 3.0.0 Foreword This Technical Report has been produced by the 3GPP. The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of this TR, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: Version 3.y.z where: x the first digit: 1) presented to TSG for information; 1) presented to TSG for approval; 1) Indicates TSG approved document under change control. y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. z the third digit is incremented when editorial only changes have been incorporated in the specification; Introduction The Iu reference point of UMTS is defined to be at the boundary of the URAN and the IWU [1]. In case the IWU is null, the Iu is between URAN and CN. The purpose of this document is to analyze the basic issues related to the Iu before starting the actual standardisation of the related interface(s). ETSI TR 123 930 V3.0.0 (2000-01) (3G TR 23.930 version 3.0.0 Release 1999) ETSI 3GPP 3G TR 23.930 V3.0.0 (1999-07) 5 3G TR 23.930 version 3.0.0 1 Scope This report identifies the requirements on the Iu and studies relevant principles to guide further standardisation of the related interface(s). The different instances of the UMTS radio access currently identified are the following: UMTS radio access network (URAN) UMTS Terrestrial Radio Access Network (UTRAN) Broadband Radio Access Network (BRAN) UMTS satellite radio access network 2 References The following documents contain provisions which, through reference in this text, constitute provisions of the present document. 1) 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. For a non-specific reference, the latest version applies. A non-specific reference to an ETS shall also be taken to refer to later versions published as an EN with the same number. [1] UMTS 23.101: “Universal Mobile Telecommunications System (UMTS): General Architecture”. [2] UMTS 23.110: “UMTS Access Stratum, Services and Functions” 3 Definitions, symbols and abbreviations 3.1 Definitions Iu Interconnection point between the RNS and Core Network. It is also considered as a reference point. The Iu will be implemented as one or more physical interfaces. Iu-CS The physical instance of Iu towards the CS-Service Domain of the core network. Iu-PS The physical instance of Iu towards the PS-Service Domain of the core network. ETSI TR 123 930 V3.0.0 (2000-01) (3G TR 23.930 version 3.0.0 Release 1999) ETSI 3GPP 3G TR 23.930 V3.0.0 (1999-07) 6 3G TR 23.930 version 3.0.0 RAN CS-Service Domain PS-Service Domain Iu-CS" hysical instance of Iu owards the CS- ervice domain "Iu-PS" Physical instance of Iu towards the PS-Service domain u Reference Point Core Network Figure 1 – Iu Reference point, and the Iu-CS and Iu-PS physical instances 3.2 Symbols For the purposes of the present document, the following symbols apply: TBD 3.3 Abbreviations For the purposes of this document, the following abbreviations apply: TBD 4 Iu requirements 4.1 General Requirements 1) The Iu shall support all service capabilities offered to UMTS users Iu shall particularly cater for a variety of services e.g. classical telephony, internet-based services (www, e-mail etc.), and multimedia services. This implies that Iu supports efficiently: • dedicated circuits, especially for voice • best-effort packet services (e.g. Internet/IP) • real-time multimedia services requiring a higher degree of QoS. These real time services may be based on real-time packet data or circuit-switched data. • UMTS signalling and backward compatibility towards GSM signalling scheme. 2) The Iu shall support separate evolution of O&M facilities 3) The Iu shall support separation of each User Equipment (UE) on the protocol level for mobile specific signalling management. 4) The Iu shall support transfer of transparent non-access signalling between UE and CN. 5) The Iu shall support procedures to establish, maintain and release various types of Iu bearers. 6) The Iu shall support procedures for Intersystem handover, and the CN shall support corresponding switching ETSI TR 123 930 V3.0.0 (2000-01) (3G TR 23.930 version 3.0.0 Release 1999) ETSI 3GPP 3G TR 23.930 V3.0.0 (1999-07) 7 3G TR 23.930 version 3.0.0 capability. 7) The Iu shall support mechanisms for resource reservation for packet data streams (e.g. IP) 8) The specifications, for the Control and User planes, of the IU shall be such that the Radio Network Layer and the Transport Layer are independent, allowing either layer to change without impacting the other layer. 9) The Transport Layer Protocols and the Radio Network Layer Protocols, for the Control and User planes, of the IU shall be specified in separate documents, allowing for either document to change without impacting the other document. 4.2 UMTS Terrestrial Radio Access Network (UTRAN) 1) (Not used) 2) The design of Iu shall support connection of UTRAN via IWF to A and Gb interfaces of GSM. 3) The Iu shall support connection of various manufacturers’ URANs to various manufacturers’ IWF/CN 4) The Iu shall support separate evolution of URAN and IWF/CN 5) “The specification of the Iu shall cater for both the circuit switched (GSM) and packet (GPRS) domains. In order to enable each domain to develop according to their specific characteristics, Iu shall allow different protocol stacks towards the PSTN/ISDN domain and the IP domain. 6) The Iu shall support the combined process of relocating the SRNS role to another RNS and changing the Iu connection point for a specific UE (streamlining) and the CN shall support switching capability. 7) As long as the Iu connection point is not modified, the UTRAN can be requested by the CN to prevent all loss of data (i.e. independently of the handovers on the radio interface). 8) In case the Iu connection point is changed (e.g. SRNS relocation, streamlining), the CN is not supposed to buffer packets in view of ensuring a high data reliability. Hence, at SRNC relocation, for high reliability Radio Access Bearers, the old SRNC has to send downstream packets not yet acknowledged by UE to the new SRNC. Furthermore, no flow control between CN and UTRAN needs to be defined in order to control the IP domain user plane downstream flow. 9) A single set of radio access bearer services shall be offered by the UTRAN to the Core Network. 10) There shall be a single functional split between the UTRAN and the Core Network. 11) A single Access Stratum signalling protocol between the UTRAN and the Core Network over Iu shall be defined to access the services provided by UTRAN. Note: The statements 9, 10 and 11 apply regardless of the scenario applied for the Core Network. 12) If the GSM/UMTS Core Network consists of different core network node types, UTRAN shall support simultaneous access to these node types for one UE. 13) The Iu shall support general procedures that are not related to a specific UE. Such procedures may be used e.g. in failure situations, for flow control in procedure level, or in the initialisation phase (this does not refer to O&M procedures). 14) (Not used) 15) The Iu shall support a set of general UTRAN procedures from the Core Network such as paging –notification 16) (Not used) 17) The Iu shall support procedures to establish, maintain and release various types of UTRAN Radio Access Bearers. 18) The Iu shall enable the CN node to request UTRAN to obtain and send the location information for a specific UE located in the coverage of the present UTRAN. The location information consists of both a geographic area identity and a set of global co-ordinates with uncertainty parameters 19) AAL2 is used as the data transport bearer for the user plane towards the PSTN/ISDN domain. ETSI TR 123 930 V3.0.0 (2000-01) (3G TR 23.930 version 3.0.0 Release 1999) ETSI 3GPP 3G TR 23.930 V3.0.0 (1999-07) 8 3G TR 23.930 version 3.0.0 20) The AAL Type signalling protocol 2 (q.aal2) Capability Set 1 (CS1) developed by ITU SG11 is used to establish the AAL2 connections towards the PSTN/ISDN domain 21) To ensure the necessary load sharing on the Iu_PS interface, • When the CN requests the establishment of a Radio Access Bearer (associated with a PDP context) or at SRNS relocation for all Radio Access Bearers (associated with PDP contexts) of an UE, the CN specifies the IP address of the packet processing function allocated to this / each of these PDP context(s) in the CN. • In the response to the CN request, the RNC specifies the IP address of the packet processing function allocated to this / each of these Radio Access Bearer(s) in the RNC. When it sends downstream traffic in a RAB, the packet processing function in the CN sends the packet to the RNC IP address received from the SRNC at RAB establishment or at SRNS relocation. When it sends upstream traffic in this RAB, the packet processing function in the RNC sends the packet to the CN IP address received from the CN at RAB establishment or at SRNS relocation.
|
d07bfdf3244e1962a4c6191f126aee07
|
123 930
|
4.2.1 SRNS-Relocation
|
To carry out SRNS relocation, the source SRNC must launch the SRNS relocation procedure, since it is not the target SRNC but the source SRNC that knows the current services of an user. This is done only when this procedure has the least adverse effect on user traffic, The SRNC relocation procedures shall ensure that there is only one Serving RNC for an user even if this user has services through more than one (IP or ISDN) domain. The SRNS relocation procedure is split in 2 phases. In the first one resources are reserved on the new Iu interfaces and (if needed) inside the CN. Only when this first phase has been successfully carried out for all domains on which the user has currently some services, the source SRNC can launch the second phase i.e. hand-over the role of SRNC to the target SRNC.
|
d07bfdf3244e1962a4c6191f126aee07
|
123 930
|
4.2.2 Position for header compression
|
Header compression function is allocated at RNC because: • differential header compression algorithms work better if they are located in the place where packets are more likely to be discarded (after having discarded packets the compression algorithm can send a packet with full header ). This place is the RNC (where the queues for downstream packets waiting for radio resources are located). • The compression entity is as close as possible to the reliable link (as in 2G) which in this case is the RLC. Therefore it can be stated that a faster recovery of packets is possible after loss of packets in the radio interface and this solution will therefore minimize the amount of buffering in the UE and network. • the compression can be optimized for the used RAN. • It increases the possible data rates that can be achieved: Locating the compression function in the RAN defers the SGSN from the task of opening and processing packets • efficient inter-system hand-over can be supported 4.3 UMTS Satellite Radio Access Network (USRAN) 1) The Iu shall support connection to UMTS Satellite Radio Access Network (USRAN) 2) The Iu shall support low rate source encoded speech; 3) [The Iu shall support radio access and link control protocols that are tolerant to changes in delay at handovers.] 4) (Editorial, Requirement 3 is currently put into brackets since Iu related requirements related to handover scenarios including Satellite based access are for further study) ETSI TR 123 930 V3.0.0 (2000-01) (3G TR 23.930 version 3.0.0 Release 1999) ETSI 3GPP 3G TR 23.930 V3.0.0 (1999-07) 9 3G TR 23.930 version 3.0.0 5) The Iu shall ensure that location information wherever and whenever present, shall support global co- ordinate formats. 6) The Iu shall support connection establishment protocols working over radio resources of different power and penetration levels such as to request the user to move to a more favourable location to complete the establishment of the connection. 7) The Iu shall support low rate data services. 4.4 Broadband Radio Access Network (BRAN) 1) The Iu shall support connection of an EP BRAN HIPERLAN 2 radio access network. 2) The Iu shall support high data rates according to the capability of HIPERLAN2. 3) The Iu shall support UMTS QoS mechanisms also for high data rate services according to the capability of HIPERLAN2. 4) The Iu shall support handover within/between HIPERLAN2 radio access networks. 5) The Iu shall support handover between HIPERLAN 2 and UTRAN. Other systems are ffs. 5 Access stratum vs. Non-access stratum The Access Stratum (AS) offers its services to the Nonaccess Stratum through SAPs in the UE and CN. These services are described in [2]. The Access Stratum contains a set of UE – RAN protocols and a set of RAN – CN protocols ref. [1]. RAN UE CN Access Stratum Non-Access Stratum Radio (Uu) Iu 6 Working Assumptions 6.1 General 1) Source dependent coding (e.g. voice) shall be located in the core network domain, and logically belong outside the Access Stratum. For release 99 the location is expected to be the visited MSC. However the release 99 standard shall facilitate the evolution of the codec into the gateway/interworking MSC; i.e., at the PLMN border. To do this, it is (at least) required that the interface between RNC and the transcoder is fully standardised in release 99. 2) Transport protocol across the Iu interface for UTRAN shall be based on ATM. 6.2 Interface and protocols over Iu for UTRAN purposes 1) The UMTS standard shall allow for both separated and combined MSC/VLR and SGSN configurations ETSI TR 123 930 V3.0.0 (2000-01) (3G TR 23.930 version 3.0.0 Release 1999) ETSI 3GPP 3G TR 23.930 V3.0.0 (1999-07) 10 3G TR 23.930 version 3.0.0 2) The UTRAN shall support two logically separate signalling flows via Iu to combined or separate network nodes of different types (MSC and SGSN) 3) The UE shall be able to handle separated or combined MSCs and SGSNs. 4) There can be several user planes to these CN nodes. 5) Addressing in RANAP should follow the following principles (subject to evaluation of performance impact): 5a) Addressing for signalling messages on the Iu interface (in RANAP) should be independent of underlying layers allowing for independent evolution of the underlying layers. 5b) Addressing for signalling messages on the Iu interface (in RANAP) should use the same addressing scheme for both the PS-domain and the CS-domain History Document History August 1997 Scope agreed November 1997 0.1.0 Version 0.1.0 mailed to SMG3 SA delegates prior to SMG3 SA meeting in Stockholm. November 1997 0.1.1 Version 0.1.1 presented at SMG3 SA in Stockholm August 1998 0.2.0 Version 0.2.0 with the changes agreed in the Sophia Antipolis meeting. September 1998 0.3.0 Version 0.3.0 with the changes agreed in the Rome meeting October 1998 0.4.0 Added req. due to Td 98S853. Added section “Access Stratum vs. Non-Access Stratum due to Td 98S864 December 1998 0.5.0 Restructured to handle different types of the UMTS radio access network December 1998 0.6.0 New USRAN and BRAN sections. New working assumptions. February 1999 1.0.0 Based on decisions in Walnut Creek and Kista meetings March 1999 1.1.0 Section 6.1, Working assumption on Transcoder Location included March 1999 1.2.0 Changes from Nynäshamn (S2-99148) April 1999 1.2.1 Change to 3GPP format June 1999 1.3.0 Changes from Sophia Antipolis (S2-99345, S2-99404) June 1999 1.3.1 Editorial changes in section 4.2 (Editor : Bo Axerud, e- mail:[email protected]) June 1999 2.0.0 Version 1.3.1 has been approved by e-mail and agreed to be updated to version 2.0.0, for submission to TSG SA ETSI TR 123 930 V3.0.0 (2000-01) (3G TR 23.930 version 3.0.0 Release 1999) ETSI 3GPP 3G TR 23.930 V3.0.0 (1999-07) 11 3G TR 23.930 version 3.0.0 for approval July 1999 3.0.0 Template changed, clauses and sub-clauses numbering corrected, administrative clauses added. ETSI TR 123 930 V3.0.0 (2000-01) (3G TR 23.930 version 3.0.0 Release 1999) ETSI 12 ETSI ETSI TR 123 930 V3.0.0 (2000-01) (3G TR 23.930 version 3.0.0 Release 1999) History Document history V3.0.0 January 2000 Publication
|
80fdf3a3ce1a5e984582bc005dba2f5f
|
119 479-2
|
1 Scope
|
The present document proposes an extended validation mechanism leveraging on the existing OID4VP protocol. Its primary aim is to support the secure and interoperable validation of electronic attestations by identifying standardization needs in the context of the attestation rulebook and attribute catalogues. Key focus areas include: • introduction of attestation refreshing and attestation encryption mechanisms; • description of embedded disclosure policies and support for pricing policies; • further considerations on the extension of attestation metadata structures to include policy-related parameters.
|
80fdf3a3ce1a5e984582bc005dba2f5f
|
119 479-2
|
2 References
| |
80fdf3a3ce1a5e984582bc005dba2f5f
|
119 479-2
|
2.1 Normative references
|
Normative references are not applicable in the present document.
|
80fdf3a3ce1a5e984582bc005dba2f5f
|
119 479-2
|
2.2 Informative references
|
References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long-term validity. The following referenced documents may be useful in implementing an ETSI deliverable or add to the reader's understanding, but are not required for conformance to the present document. [i.1] BIP-0032. [i.2] ETSI TS 119 312: "Electronic Signatures and Trust Infrastructures (ESI); Cryptographic Suites". [i.3] ETSI TR 119 476 (V1.2.1): "Electronic Signatures and Trust Infrastructures (ESI); Analysis of selective disclosure and zero-knowledge proofs applied to Electronic Attestation of Attributes". [i.4] European Digital Identity Wallet Architecture and Reference Framework v1.8 (ARF). [i.5] IETF draft-demarco-oauth-status-assertions-03: "OAuth Status Assertions". [i.6] IETF draft-ietf-oauth-sd-jwt-vc-09: "SD-JWT-based Verifiable Credentials (SD-JWT VC)". [i.7] IETF RFC 7516: "JSON Web Encryption (JWE)". [i.8] ISO/IEC 18013-5: "Personal identification - ISO-compliant driving licence - Part 5: Mobile driving licence (mDL) application". [i.9] NIST SP 800-56A Rev. 3: "Recommendation for Pair-Wise Key-Establishment Schemes Using Discrete Logarithm Cryptography". [i.10] OpenID Foundation: "OpenID for Verifiable Credential Issuance - draft 15", 2024. [i.11] OpenID Foundation: "OpenID for Verifiable Presentations - draft 24", 2025. [i.12] Regulation (EU) 2024/1183 of the European Parliament and of the Council of 11 April 2024 amending Regulation (EU) No 910/2014 as regards establishing the European Digital Identity Framework. ETSI ETSI TR 119 479-2 V1.1.1 (2025-07) 7 [i.13] SOG-IS Crypto Working Group: "SOG-IS Crypto Evaluation Scheme Agreed Cryptographic Mechanisms". [i.14] W3C® Recommendation 3 March 2022: "Verifiable Credentials Data Model v1.1".
|
80fdf3a3ce1a5e984582bc005dba2f5f
|
119 479-2
|
3 Definition of terms, symbols and abbreviations
| |
80fdf3a3ce1a5e984582bc005dba2f5f
|
119 479-2
|
3.1 Terms
|
For the purposes of the present document, the terms given in [i.4], [i.12], [i.14] and the following apply: attestation provider: natural or legal person who provides QEAA, PuB-EAA, or (non-qualified) EAA issuance services attribute: feature characteristic or quality of a natural or legal person or of an entity, in electronic form Electronic Attestation of Attributes (EAA): attestation in electronic form that allows attributes to be authenticated Electronic Attestation of Attributes issued by or on behalf of a Public sector body (PuB-EAA): electronic attestation of attributes issued by a public sector body that is responsible for an authentic source or by a public sector body that is designated by the Member State to issue such attestations of attributes on behalf of the public sector bodies responsible for authentic sources EU Digital Identity (EUDI) Wallet: initiative by the European Union aimed at providing citizens and businesses with a secure and convenient way to manage and use their digital identities NOTE: The EU Digital Identity Wallet allows users to store and control their personal data in a digital format, enabling them to prove their identity and other attributes in various online and offline situations. Person Identification Data (PID): set of data that is issued in accordance with Union or national law and that enables the establishment of the identity of a natural or legal person, or of a natural person representing another natural person or a legal person PID provider: natural or legal person responsible for issuing and revoking the person identification data and ensuring that the person identification data of a user is cryptographically bound to a Wallet Unit presentation: data derived from one or more attestations, issued by one or more Attestation Providers, that is shared with a specific verifier Qualified Electronic Attestation of Attributes (QEAA): electronic attestation of attributes which is issued by a qualified trust service provider and meets the requirements laid down in Annex V of European Digital Identity Wallet Architecture and Reference Framework [i.4] Relying Party (RP): natural or legal person that relies upon electronic identification, European Digital Identity Wallets or other electronic identification means, or upon a trust service (Wallet-) Relying Party: Relying Party that intends to rely upon Wallet Units for the provision of public or private services by means of digital interaction selective disclosure: capability enabling the user to present a subset of the attributes included in a PID or attestation unlinkability: lack of information required to connect the user's selectively disclosed attributes beyond what is disclosed NOTE: The unlinkability definition has different shapes, refer to clause 3 of ETSI TR 119 476 [i.3] for further information. user: natural or legal person, or natural person representing another natural person or legal person, that uses trust services or electronic identification means provided in accordance with Regulation (EU) 2024/1183 [i.12] (Wallet) User: user who is in control of the Wallet Unit ETSI ETSI TR 119 479-2 V1.1.1 (2025-07) 8 Wallet Solution: combination of software, hardware, services, settings, and configurations, including Wallet Instances, one or more Wallet Secure Cryptographic Applications, and one or more Wallet Secure Cryptographic Devices Wallet Unit: unique configuration of a Wallet Solution that includes Wallet instances, Wallet Secure Cryptographic Applications, and Wallet Secure Cryptographic Devices provided by a Wallet Provider to an individual Wallet User
|
80fdf3a3ce1a5e984582bc005dba2f5f
|
119 479-2
|
3.2 Symbols
|
Void.
|
80fdf3a3ce1a5e984582bc005dba2f5f
|
119 479-2
|
3.3 Abbreviations
|
For the purposes of the present document, the following abbreviations apply: ARF Architecture and Reference Framework CRQC Cryptographically Relevant Quantum Computers EAA Electronic Attestation of Attributes ECC Elliptic Curve Cryptography EUDI European Union Digital Identity HD Hierarchical Deterministic JWE JSON Web Encryption KID Key IDentifier OID4VCI OpenID for Verifiable Credential Issuance OID4VP OpenID for Verifiable Presentation PID Personal Identification Data QEAA Qualified Electronic Attestation of Attribute RP(s) Relying Party(-ies) URL Uniform Resource Locator VP Verifiable Presentation
|
80fdf3a3ce1a5e984582bc005dba2f5f
|
119 479-2
|
4 Extended Validation Service(s)
| |
80fdf3a3ce1a5e984582bc005dba2f5f
|
119 479-2
|
4.1 Overview
|
The present clause presents an extension to the digital attestation validation framework. This advancement enables the development of diverse business models associated with attestations, encompassing issuance, validation, and unrestricted free usage. At present, only issuance and free usage are achievable without the proposed approach. The proposal discussed in the present document does not require changes to the existing attestation issuance process. It is format-agnostic, maintaining compatibility with all the available. The concept involves two steps: 1) Attestation Refreshing: the attestations are refreshed before being presented, to guarantee their validity without the need for the RP to undertake additional controls, except for integrity of the attestations. 2) Cyphered Attestation Presentation: the attestations are encrypted by the User's Wallet using a mechanism described later in the present document, before being shared with a RP. The RP can only access the attestation(s) through direct communication with the User and with the Attestation Provider. This communication occurs without revealing any information about the User and allows the Attestation Provider to count the number of verifications performed by each RP. These two steps are described more thoroughly in the following clauses. ETSI ETSI TR 119 479-2 V1.1.1 (2025-07) 9
|
80fdf3a3ce1a5e984582bc005dba2f5f
|
119 479-2
|
4.2 Attestation Refreshing
|
Attestation refreshing consists of periodically refreshing attestation(s) by communicating directly with the Attestation Provider. This could be achieved through two different approaches: • Linked credentials: the Attestation Provider provides the User with a Status Assertion [i.5], which is linked to an attestation. This enables the User to present both the attestation and its Status Assertion to RP as a proof of the attestation's validity status. • Credential reissuance: it is based on multiple access to the RP endpoint, as described in clause 13.5 in OID4VCI [i.10]. It is possible to refresh an issued attestation, the Wallet can retrieve an updated attestation using a valid Access Token or refresh it with a valid Refresh Token, without interaction with the User. If the Wallet lacks both a valid Access and Refresh Token, the Attestation Provider should reissue the attestation by initiating the issuance process from the beginning, which requires interaction with the User. Re-issuance means the replacement of a PID or attestation that already exists in a Wallet Unit by a PID or attestation having the same document type. For formal definitions of re-issuance, refer to ARF Topic B [i.4]. • Batch Issuance: it means that instead of issuing a single PID or attestation to a Wallet User, a PID Provider or Attestation Provider issues a batch of them. If the original PID or attestation was issued in a batch, then the PID Provider or Attestation Provider re-issues that PID or attestation in a batch as well. For formal definitions of batch issuance, refer to ARF Topic B [i.4]. This Attestation Refreshing could be done when the Wallet starts up, or on demand, or just before presenting the attestation. These approaches should apply only to attestations that require refreshing. For example, it would not be useful for static attestations. RP can implement their own policies based on the type of service provided. For instance, they could accept an attestation refreshed within the last N hours or, for more critical services, only accept an attestation refreshed within the last minute. This ensures for a non-complex validation mechanism, since the attestation is refreshed directly by the Attestation Provider, third parties are not required to validate it.
|
80fdf3a3ce1a5e984582bc005dba2f5f
|
119 479-2
|
4.3 Cyphered Attestation Presentation
|
The attestation, once refreshed, is encrypted by the User's Wallet. The RP should then contact the Attestation Provider to retrieve the decryption key in order to verify the attestation. This adds an additional layer of security by ensuring that the RP cannot access the attestation directly, without interaction with the Wallet User and the Attestation Provider. As previously mentioned, the protocol doesn't imply any change to the current attestation issuance process (described in OID4VCI [i.10]). The Attestation Provider creates and signs the attestation, embedding relevant identity or attribute information for the User (e.g. identity, access rights, etc.). Then the attestation is transmitted to the User's Wallet over a secure channel using TLS, as described in OID4VCI [i.10]. The proposed method involves encrypting the attestation at the time of presentation, leveraging the properties of Elliptic Curve Cryptography (ECC) and, more specifically, the Hierarchical Deterministic (HD) Key Derivation. In particular, the method takes advantage of the properties of Hierarchical Deterministic structures, where each derived private key is generated in such a way that the corresponding public key can be computed without knowing the private key itself. When a Wallet initiates the presentation of an attestation (which could be in various formats, such as SD-JWT VC [i.6] or mdoc [i.8]), the attestation is encrypted according to the JSON Web Encryption (JWE) standard [i.7]. The encryption key for the attestation is generated at the time of the new presentation; it is derived from the Attestation Provider's public key. In order for the RP to decrypt the JWE, the Wallet should also send them additional information along with the JWE. This will be forwarded to the Attestation Provider. Upon receiving the necessary information, the Attestation Provider retrieves the cryptographic material which the RP can use to obtain the attestation. More in detail, the expected flow of messages is listed below, subdivided into two phases: Refreshing and Presentation. ETSI ETSI TR 119 479-2 V1.1.1 (2025-07) 10 Refreshing: 1) The Wallet sends the Attestation Provider a request to refresh the attestation, as described in the previous clause. 2) The Attestation Provider sends an updated attestation back to the Wallet, notifying the Wallet in case the attestation is not valid anymore. Cyphered Attestation Presentation: 1) The Wallet generates a transaction-specific symmetric encryption key K which it uses to encrypt the attestation A. The result of the encryption process is denoted here as K(A). 2) The Wallet generates the JWE of the attestation as follows: - The JWE contains all the necessary information for decrypting the body of the JWE itself; this includes: X: a concatenation between a timestamp and a random nonce generated by the Wallet; KID: a Key Identifier, needed to identify the correct Attestation Provider and then ask this Attestation Provider to decrypt CP(K) (see below); CP(K), i.e. the key K encrypted using an asymmetric public key CP belonging to the Attestation Provider and derived from a master public key of the same Attestation Provider. - The body of the JWE contains K(A), that is the attestation A encrypted using the symmetric key K (see step 1). 3) The RP receives the JWE and sends CP(K) and X to the Attestation Provider, asking the Attestation Provider to use the derived private key linked to X in order to decrypt CP(K). 4) The Attestation Provider retrieves from X which private key to use in order to decrypt CP(K); after doing so, it obtains K and sends K to the RP. 5) The RP uses K to decrypt K(A), thus retrieving A. Figure 1 below schematizes the above steps 1) - 5) with regards to Cyphered Attestation Presentation. Figure 1: Cyphered Attestation Presentation Scheme
|
80fdf3a3ce1a5e984582bc005dba2f5f
|
119 479-2
|
5 Central Rulebook for Attributes
| |
80fdf3a3ce1a5e984582bc005dba2f5f
|
119 479-2
|
5.1 Overview
|
The EUDI Wallet ecosystem is governed by a range of policies that address various aspects of user interaction, data security, attestation management and user privacy. These policies are designed to safeguard users' personal information and ensure that the ecosystem functions smoothly across EU boundaries. ETSI ETSI TR 119 479-2 V1.1.1 (2025-07) 11 The EUDI Wallet is designed to comply with eIDAS 2.0 [i.12], ensuring compliance with strict privacy and security standards. Each interaction of the Wallet undergoes rigorous certification to meet high security requirements. For instance, the user consent policy guarantees that users retain full control over their data. When a RP requests access to specific attributers, the user should explicitly approve or deny the request. Attestation disclosure policies define which types of RP are allowed by Attestation Provider to access specific attributes from attestation. While these existing policies effectively address user rights, consent, and security, there is a noticeable gap in the area of business-related policies, which are crucial for ensuring the long-term sustainability of the ecosystem. To address this gap, the Pricing Policy is introduced in the present document, a guideline that outlines how Service Providers should determine the costs associated with their services or products. The Pricing Policy would complement existing frameworks by providing clarity and fairness in the pricing of Wallet User's attestation-related services or PID-related services, such as the presentation of attestation. Furthermore, to regulate and organize the market for these attestations, the usage of Attestation Rulebooks catalogue [i.4] is leveraged. This catalogue would serve as a standardized reference for the structure and pricing of different attestations, aligning with broader industry practices and helping to prevent fragmentation in implementation. The proposed Attestation Cyphered Presentation protocol does not require changes to the existing attestation issuance processes. It is format-agnostic, maintaining compatibility with all available attestation formats. A key advantage of this protocol is its flexibility in supporting various Pricing Policy options. For instance, it enables the selection between various approaches, like: 1) Free-to use attributes 2) Issuance-based fee 3) Verification-based fee
|
80fdf3a3ce1a5e984582bc005dba2f5f
|
119 479-2
|
5.2 Attestation metadata extension
|
Attestation Providers could utilize the Attestation Rulebooks catalogue to publish their attributes when necessary. This catalogue mitigates the risks of uncontrolled implementation practices that could degrade system quality, increase complexity and maintenance costs. It facilitates the integration of the encrypted attestations approach with verification fees into the OID4VP [i.11] protocol. This ensures a more organized, cost-effective, and interoperable ecosystem. This catalogue would serve as a comprehensive repository of attestation-related information, including attestation Metadata, which provides essential details for identifying, verifying, and contextualizing attestations, as well as information on any associated policies. Additionally, a new "pricing_policy" parameter could be introduced. An attestation often includes embedded disclosure policy, which consists of a set of rules, embedded in the attestation by its provider, that indicates the conditions that a RP should meet to access the attestation. The pricing policy could originate from the embedded disclosure policy, meaning that the conditions for access to the attestation could include pricing-related criteria. This pricing policy would allow to specify all relevant details regarding the applied policy, including pricing model, price, currency, and URI linking to the Attestation Provider's detailed policy page. The following is an example snippet of attestation Metadata, where the metadata for a specific attestation includes a newly proposed parameter "pricing_policy". ETSI ETSI TR 119 479-2 V1.1.1 (2025-07) 12 Figure 2: Attestation Metadata The proposed solution could also allow to apply different price models: 1) Static price, which refers to a pricing strategy where the cost of the service remains unchanged; in practice, a static price is fixed and does not undergo frequent updates. This could be embedded directly into the attribute schema, clearly exposing the unit price per verification. This transparency allows the RP to quickly assess whether they are willing to accept the price or opt not to use the attribute, simplifying decision-making. 2) Dynamic price, which refers to a pricing strategy where the cost of the service fluctuates based on various factors. This approach allows businesses to maximize revenue by adjusting prices in real-time or at regular intervals. The affected stakeholders should check a specific URL, periodically updated, where prices are listed. This also allows Attestation Providers to better manage the attributes offering on a daily-basis and/or based on different agreements with several RPs. ETSI ETSI TR 119 479-2 V1.1.1 (2025-07) 13 The OID4VP protocol can be extended to enable interaction with the central registry in the following manner: Figure 3: OID4VP extension for payment scenario 1) Discovery Phase: Before a Relying Party (RP) requests a Verifiable Presentation (VP), it queries the central registry to understand the available attributes, Attestation Providers, and associated costs. The RP includes the selected attributes in the request, specifying the willingness to pay associated verification fees. 2) Attestations Exchange as extension of OID4VP: Using the Encrypted attestations exchange described in clause 4.3 of the present document. 3) Verification Cost Exchange: During the Attestation Provider-RP interaction for decryption and verification, the Attestation Provider verifies whether the payment conditions (if any) are met. A secure payment protocol (e.g. token-based) could be used to process the fee.
|
80fdf3a3ce1a5e984582bc005dba2f5f
|
119 479-2
|
6 Security Considerations
|
1) An overarching issue when dealing with the security of cryptographic systems in use today is the advent of quantum computers, more precisely Cryptographically Relevant Quantum Computers (CRQCs). This kind of computers could break the entire stack on which security is based today, by easily solving the mathematical problems that underpin classical cryptography. This applies both to the well-established RSA scheme and to the Elliptic Curve Cryptography, due to the presence of Shor's Algorithm. Currently this applies to all of the infrastructures providing trust, such as PKIs, and is a general threat that can be faced only through the replacement of the obsolete algorithms used today with quantum-safe ones, such as those approved by NIST in recent times. One well-known attack strategy is the "harvest now, decrypt later", which involves acquiring and stage currently encrypted data within the intention of decrypting it later, once advancements in decryption technology, like the quantum computing, make it accessible. This problem concerns all types of current cryptographic schemes, including the JWE with the cyphered attestation, highlighting the need for a transition to quantum-resistant cryptographic solutions to mitigate these threats. 2) Regardless of considerations about the future advent of quantum computers, a practical security consideration is that only approved curves and parameters should be used, such as those contained in NIST SP 800-56A Rev. 3 [i.9] or other recognized suits are described in ETSI TS 119 312 V1.5.1 [i.2] or in SOG-IS [i.13]. 3) The general security of the described mechanism is guaranteed, without taking into account the potential advent CRQCs, by the Discrete Logarithm Problem over Elliptic Curves and by the non-reversibility of the used hash functions. 4) An issue could be the fact that the mechanism of HD keys is not formally standardized (by a formal SDO) but is described in clause 4.4.4.2 of ETSI TR 119 476 [i.3]. ETSI ETSI TR 119 479-2 V1.1.1 (2025-07) 14 5) The mechanism described does not suffer from the well-known weakness of leakage of the private key of the Attestation Provider, as described in BIP 32 [i.1], because this key is never exposed to the public.
|
80fdf3a3ce1a5e984582bc005dba2f5f
|
119 479-2
|
7 Privacy Considerations
|
The mechanism set up so far brings about some considerations regarding privacy, described below: 1) With regard to clause 4.3 about Cyphered Attestation Presentation, it should be highlighted that the Attestation Provider and the RP could collude in order to decrypt the JWE: this is due to the possibility to share the entire JWE with the Attestation Provider. 2) In principle, the Attestation Provider could generate a new private-public key couple for each request of a new attestation. This fact would allow a tracking of the Wallet User's activity by the Attestation Provider, resulting in a concern for the privacy. Therefore, it would be advisable to control the number of public keys available for the Attestation Provider: if the number of public keys increases over time, this could be an indicator of potentially malicious Attestation Provider's behaviour. 3) The entire mechanism allows for the Users' privacy because: - The cryptographic material (e.g. the public key CP in clause 4.3) is not directly generated by the Attestation Provider. It is, instead, derived by the Wallet starting from one of the Attestation Provider's public keys in such a way that the Attestation Provider is not aware of this generation; moreover, several "child" public keys can be generated starting from the same "parent" public key belonging to the Attestation Provider. - The Attestation Provider never gets the attestation in plain, unless the RP explicitly shares it with the Attestation Provider, without the User's consent. 4) In the worst-case scenario where the Attestation Provider has issued only one attestation, it would be possible to link the attestation to the Wallet User. ETSI ETSI TR 119 479-2 V1.1.1 (2025-07) 15 Annex A: Hierarchical Deterministic (HD) Key Derivation The present clause describes the details of the key derivation already mentioned in clause 4.3 using the well-known "Alice and Bob" scenario, described in clause 4.4.4.2 of ETSI TR 119 476 [i.3]. At first, each of Alice and Bob choose their private-public key pair. They agree on an elliptic curve of order n over a finite field and with generator G = (Gx, Gy). Alice has her master private key MS (which is a scalar value) and the corresponding master public key is MP (which is a point on the elliptic curve). The equation that links MS and MP is the following: MP = MS ∙G where retrieving MS only from MP is deemed to be computationally hard due to the discrete logarithm problem over elliptic curves. Bob wants to derive "child" public keys CP1, CP2, … from MP, without having access to MS and in such a way that Alice can derive the same keys starting from the corresponding "child" private keys CS1, CS2, …, each of them derived from MS. The starting point is the idea, outlined in BIP 32 [i.1], according to which these keys are grouped into a hierarchical structure, for instance a tree, originating from one master key. This applies to private keys and to their public counterparts as well. More precisely, the mechanism goes as follows: • The master private key MS is generated in a random way starting from a seed. • The master public key MP is obtained as mentioned before. • Child public key CP1 is obtained from MP in the following way: CP = MP + HMAC MP, X ∗G where HMAC is a function that performs hashing through SHA512 algorithm, and successive children CP2, CP3, … are derived with the same mechanism but with different values of X, which is a combination of a random nonce produced by Bob and a timestamp; • Child private key CS1 is derived from MS using a similar mechanism: CS = MS + HMAC MP, X mod n where the only differences with the previous formula are the presence of MS instead of MP and the presence of the modulo operator. The described mechanism works because CP1 corresponds to CS1; in fact: CP = MP + HMAC MP, X ∗G = MS ∗G + HMAC MP, X ∗G = MS + HMAC MP, X ∗G = CS ∗G where: • the second equation derives from the definition of MP; • the operations in the third equation are performed mod n. The result shows that the public key CP1 is indeed corresponding to the private key CS1. Finally, in order to transpose the described mechanism into the EUDI Wallet ecosystem, it is necessary to recognize that Alice is the Attestation Provider, while Bob is the Wallet User; the RP is a generic third party interested in obtaining Bob's attestations. ETSI ETSI TR 119 479-2 V1.1.1 (2025-07) 16 The following diagram (Figure A.1) describes the aforementioned entire flow in the EUDI Wallet scenario. Figure A.1: Attestation Cyphered sequence diagram ETSI ETSI TR 119 479-2 V1.1.1 (2025-07) 17 History Document history V1.1.1 July 2025 Publication
|
f7d157762f0f1ce82de62a5fe14e2af8
|
101 640
|
1 Scope
|
A considerable amount of work has been conducted, mainly in the UK, to investigate the effect of wanted radio frequency transmissions from GSM MS and BTS on other equipment. The present document aims to summarize this work and to look at the implications for GSM. Since GSM EMC considerations extend outside the GSM arena, it is thought essential that GSM considers the implications of EMC and produces the present document.
|
f7d157762f0f1ce82de62a5fe14e2af8
|
101 640
|
1.1 Void
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.