hash
stringlengths 32
32
| doc_id
stringlengths 7
13
| section
stringlengths 3
121
| content
stringlengths 0
3.82M
|
|---|---|---|---|
e20bfd5f2facbd115bc6c2064c7898e3
|
122 034
|
6 Interworking requirements
|
.....................................................................................................................13
|
e20bfd5f2facbd115bc6c2064c7898e3
|
122 034
|
6.1 Service interworking
|
............................................................................................................................................. 13
|
e20bfd5f2facbd115bc6c2064c7898e3
|
122 034
|
6.1.1 Interworking with supplementary services
|
...................................................................................................... 13
|
e20bfd5f2facbd115bc6c2064c7898e3
|
122 034
|
6.1.2 Interworking with other services
|
..................................................................................................................... 13 ETSI ETSI TS 122 034 V3.2.1 (2000-04) 4 3G TS 22.034 version 3.2.1 Release 1999
|
e20bfd5f2facbd115bc6c2064c7898e3
|
122 034
|
6.2 Network interworking
|
........................................................................................................................................... 13 Annex A (informative): Change history...............................................................................................14 ETSI ETSI TS 122 034 V3.2.1 (2000-04) 5 3G TS 22.034 version 3.2.1 Release 1999 Foreword This Technical Specification (TS) 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 TS 122 034 V3.2.1 (2000-04) 6 3G TS 22.034 version 3.2.1 Release 1999 1 Scope The present document specifies the Stage 1 description of High Speed Circuit Switched Data (HSCSD). HSCSD is a feature that introduce General Bearer Services and a multislot mechanism is used for user rates that can be achieved with one or more TCH/F. Multislot also defines a flexible use of air interface resources which makes efficient and flexible use of higher user rates feasible. The Multislot mechanism is only applicable to GERAN. At UTRAN radio access parameters used for GBS user data are specified at TS 23.107. 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] GSM 01.04: "Digital cellular telecommunications system (Phase 2+); Abbreviations and acronyms". [2] TS 22.002: "Bearer Services (BS) supported by a Public Land Mobile Network (PLMN)". [3] TS 22.004: "General on supplementary services". [4] GSM 02.06: "Digital cellular telecommunications system (Phase 2+); Types of Mobile Stations (MS)". [5] GSM 05.02: "Digital cellular telecommunications system (Phase 2+); Multiplexing and multiple access on the radio path". [6] TR 21.905: "Vocabulary for 3GPP Specifications". 3 Abbreviations and definitions 3.1 Abbreviations For the purposes of the present document, the following abbreviations apply: AIUR Air Interface User Rate EDGE Enhanced Data rates for GSM Evolution FNUR Fixed Network User Rate GBS General Bearer Services GERAN GSM/EDGE radio access network HSCSD High Speed Circuit Switched Data MO Mobile Originated MT Mobile Terminated NT Non Transparent T Transparent UE User Equipment (same as MS in GSM specifications) Additional GSM related abbreviations can be found in GSM 01.04 [1] ] and TS 22.905 [6]. ETSI ETSI TS 122 034 V3.2.1 (2000-04) 7 3G TS 22.034 version 3.2.1 Release 1999 3.2 Definitions For the purposes of the present document, the following terms and definitions apply: Fixed Network User Rate: user rate between IWF and the fixed network. Air Interface User Rate: user rate between Mobile Termination and IWF. For T services it is the maximum possible AIUR not including padding. For NT services it is the maximum possible AIUR. maximum possible GERAN AIUR: highest possible GERAN AIUR that the multiple TCH/F can provide, e.g. 2 TCH/F using TCH/F9.6 provides a maximum possible AIUR of 19,2 kbit/s. padding: fill bits needed to adapt the maximum possible AIUR supported by a given number of TCH/F with a given channel coding to a FNUR that is lower than the maximum possible AIUR. 4 Description 4.1 General HSCSD is a feature that introduce General Bearer Services (GBS) and a multislot mechanism is used for user rates that can be achieved with one or more TCH/F. HSCSD also defines mechanisms for the use of air interface resources which makes efficient and flexible use of higher user rates feasible. The Multislot mechanism is only applicable to GERAN. 4.2 Applicability GBS shall provide flexible ways of supporting GSM Phase 2, T and NT data services and new data services at the higher rates. Data compression shall be applicable to NT GBS. Supplementary Services applicable to the General Bearer Services are specified at TS 22.004, [3]. 4.3 General Bearer Services The General Bearer Services are defined in TS 22.002 [2]. The General Bearer Services (GBS) consist of two Bearer Services, and they are as follows: - asynchronous; - synchronous. 4.4 Parameters to be indicated and negotiated 4.4.1 Call set-up The parameters to be indicated, and negotiated, if applicable, during the call set-up shall include: - FNUR; - GERAN Channel coding(s) acceptable (for the call); - maximum number of GERAN TCH/F (that the mobile user can accept); - wanted AIUR (desired rate that the mobile user wants the network to allocate). The wanted AIUR is applicable to NT services only; - indication if the user initiated modification is required, and if so, the network resource needs; - channel coding asymmetry indication. ETSI ETSI TS 122 034 V3.2.1 (2000-04) 8 3G TS 22.034 version 3.2.1 Release 1999 Some of the parameters are only utilised by GERAN. When UTRAN radio access bearer is allocated the values are ignored. The GERAN channel coding(s) acceptable shall be indicated by the mobile at call set-up and is not negotiable. It indicates the GERAN channel coding(s) that may be chosen by the network for the call. The maximum number of GERAN TCH/F shall be indicated at call set-up. It enables the mobile user to limit the number of GERAN TCH/F used and thus to control an essential parameter for charging. It sets the upper limit of number of TCH/F that the network may allocate to the mobile. The wanted AIUR (applicable to NT services only) indicates the AIUR that the mobile user wants and which the network shall try to reach but which it is not allowed to exceed. The exception where the network is allowed to exceed the wanted AIUR is when the network can achieve the GERAN AIUR with a lower number of TCH/F, e.g. wanted GERAN AIUR indicated by the mobile is 14,4 kbit/s, GERAN channel codings acceptable are both TCH/F9.6 and TCH/F4.8 and maximum number of TCH/F are 3, then the network shall choose 2 x 9,6 over 3 x 4,8 if a channel coding of TCH/F9.6 is available on two TCH/F. If the user wishes to make use of the user initiated modification procedure, this shall be indicated at the call set-up. It shall be possible to reserve a different FNUR than the AIUR. Channel coding asymmetry indication is only applicable to NT calls where the user has indicated acceptance for channel coding(s) based on enhanced modulation. In this case the user may indicate preference for channel coding symmetry, downlink biased channel coding asymmetry, or uplink biased channel coding asymmetry. The channel coding asymmetry indication is only applicable in direction UE to network. 4.4.1.1 T services The ME or the network may propose to modify the FNUR. The calling entity may accept or release the call. Autobauding is not allowed. The AIUR is always equal to the FNUR. Fax Group 3 can make use of HSCSD. The GERAN channel coding selected must be one of the channel coding(s) indicated in the channel coding(s) acceptable parameter, the number of TCH/F selected shall not exceed the maximum number of TCH/F parameter, and the combination of the two shall result in an AIUR that is equal to the FNUR. 4.4.1.2 NT services The ME or the network may propose to modify the FNUR. The calling entity may accept or release the call. Autobauding is allowed. The wanted AIUR is indicated by the mobile at call set-up. 4.4.2 Network initiated modification 4.4.2.1 T services For transparent calls the radio resource parameters must remain within limits that allow the transparent call to maintain it is characteristics of fixed end to end throughput and delay. This means that in GERAN the channel coding and the number of TCH/F used may change during the call as long as a channel coding indicated in the channel coding(s) acceptable parameter is used, the maximum number of TCH/F is not exceeded and the AIUR is kept constant. 4.4.2.2 NT services For NT calls the network may modify the number of TCH/F and the channel coding used at GERAN and thus also the AIUR during the call as long as the maximum number of TCH/F, and the channel coding(s) acceptable are all respected. The network shall try to reach the wanted GERAN AIUR indicated, as long as the resource situation allows it. ETSI ETSI TS 122 034 V3.2.1 (2000-04) 9 3G TS 22.034 version 3.2.1 Release 1999 4.4.3 User initiated modification The in-call modification feature shall be supported in case of alternate services. 4.4.3.1 T services The user initiated modification is not applicable to T services. 4.4.3.2 NT services The user may indicate a change of the parameters maximum number of GERAN TCH/F, wanted AIUR, and channel coding asymmetry. No other parameters may be modified. The user initiated modification is only applicable to the data phase of alternate services. 4.5 Air Interface Resource Allocation 4.5.1 Minimum GERAN Air Interface Resource Allocation and Allocation Increment Air interface resources shall be allocated to HSCSD calls at TCH/F increments. The minimum air interface resource allocation for HSCSD calls shall be one TCH/F. 4.5.2 Flexible Air Interface Resource Allocation Flexible air interface resource allocation enables: - the network to allocate dynamically resources related to the air interface usage according to the network operator's strategy, within the limits negotiated at the call set-up or during a user initiated modification. 4.6 Symmetric and asymmetric connections 4.6.1 Symmetric connections For symmetric connections, air interface resources are allocated symmetrically. 4.6.2 Asymmetric connections There are two types of asymmetry, asymmetric air interface connection and channel coding asymmetry. Asymmetric air interface connection implies that more time slots are used in the downlink than in the uplink at GERAN. Channel coding asymmetry implies that one channel coding is used in the uplink and another channel coding is used in the downlink at GERAN. 4.6.2.1 Asymmetric air interface connection The provision of the asymmetric air interface connections allows simple ME (of Type 1, Reference GSM 05.02, [5]) to receive at higher AIUR than otherwise would be possible with a symmetric connection. Asymmetric air interface connections that are a subset of the symmetric HSCSD, and support different user rates at uplink and downlink, shall be provided. Asymmetric air interface connections are only applicable to the downlink-biased asymmetry, i.e., where the ME is receiving at a higher rate than it is transmitting. Asymmetric air interface connections shall only be applicable to NT GBS. ETSI ETSI TS 122 034 V3.2.1 (2000-04) 10 3G TS 22.034 version 3.2.1 Release 1999 4.6.2.2 Channel coding asymmetry Channel coding asymmetry may be set up by the network in three cases: - if the UE only supports enhanced modulation in the downlink; - if the UE supports enhanced modulation in both links, but the user indicates preference for uplink or downlink biased channel coding asymmetry; - if the UE supports enhanced modulation in both links, and the user indicates preference for channel coding symmetry, but the link conditions justifies different channel codings in up- and downlink. In the case when preference of uplink or downlink biased channel coding asymmetry is indicated by the user, and a asymmetric channel coding connection is set up based on this indication, the network shall always assign a TCH/F14.4 channel at GERAN on the unbiased link. Channel coding asymmetry shall only be applicable to NT services applying the GERAN channel codings TCH/F14.4, TCH/F28.8 and TCH/F43.2. In case a symmetric channel coding connection is set up, the link adaptation mechanism may change a symmetric channel coding connection to an asymmetric channel coding connection. 4.6.3 Network choice of connection symmetry When the network has a choice of allocating either a symmetric or an asymmetric air interface connection it shall proceed as follows: - in the case where the wanted AIUR is smaller than or equal to the AIUR supported symmetrically by the ME, or asymmetric air interface connection is not supported by the network, then a symmetric air interface connection is established; - in the case where the wanted AIUR exceeds the AIUR supported symmetrically by the ME, the network shall assign the maximum AIUR supported by the ME in the down-link at GERAN, upper-bounded by the maximum number of TCH/F indicated by the mobile user, and the number of TCH/F supported by the network, maintaining the minimum of one TCH/F. 4.7 User Equipment/Mobile Equipment requirements The general UE capabilities is applicable to HSCSD. A ME that supports multislot mechanism shall support one or more of the GERAN channel types TCH/F at or above 4,8 kbit/s. Given that the ME supports a certain GERAN channel coding, the network shall be able to assume that the ME can support this channel coding in any multislot configuration allowed by its multislot class (Reference GSM 05.02, [5]). 4.8 Mobility Management HSCSD shall be provided for within the existing supported Mobility Management. 4.9 Roaming Roaming shall be possible. ETSI ETSI TS 122 034 V3.2.1 (2000-04) 11 3G TS 22.034 version 3.2.1 Release 1999 4.10 Quality of Service 4.10.1 Bit error rate 4.10.1.1 GERAN TCH/F Bit Error Rate The bit error rate performance of each TCH/F of a multiple TCH/F HSCSD call shall be the same as that of a single TCH/F data call for the same channel coding. 4.10.1.2 Overall GBS Bit Error Rate Any increase in the bit error rate caused by the splitting and combining of multiple GERAN TCH/F shall be kept to a minimum. 4.10.2 GERAN Radio resource management The multislot mechanism shall be provided for within the existing Radio Resource management control functions, including the relevant handover types. The handover shall be simultaneous for all air interface timeslots making up the call. The multislot mechanism shall be provided with full mobility. 4.10.3 Call set-up delay Any increase in call set-up delay of the GBS calls compared to GSM Phase 2 data services shall be kept to a minimum. 4.10.4 End-to-end delay Any increase in end-to-end delay of the GBS calls compared to GSM Phase 2 data services shall be kept to a minimum. 4.10.5 Throughput The throughput for GBS T calls shall remain constant for the duration of the call except for the interruption of transmission at handover. 4.10.6 Network planning and interference levels The impact of multislot mechanism on network planning and interference levels shall be kept to a minimum. 4.11 Mapping of FNUR to GERAN TCH/F for T services For some FNUR padding is required to adapt the maximum possible AIUR to the FNUR. 4.12 Mapping of GERAN AIUR to GERAN TCH/F for NT services The following table indicates the mapping of AIUR to the number of TCH/F for NT services. ETSI ETSI TS 122 034 V3.2.1 (2000-04) 12 3G TS 22.034 version 3.2.1 Release 1999 Table 1/GSM 02.34: Mapping of AIUR to TCH/F for NT services AIUR TCH/F4.8 TCH/F9.6 TCH/F14.4 TCH/F28.8 TCH/F43.2 4,8 kbit/s 1 N/A N/A N/A N/A 9,6 kbit/s 2 1 N/A N/A N/A 14,4 kbit/s 3 N/A 1 N/A N/A 19,2 kbit/s 4 2 N/A N/A N/A 28,8 kbit/s N/A 3 2 1 N/A 38,4 kbit/s N/A 4 N/A N/A N/A 43,2 kbit/s N/A N/A 3 N/A 1 57,6 kbit/s N/A N/A 4 2 N/A N/A Not applicable. For Fixed Network User Rates (FRUR) see GSM 02.02. NOTE: GERAN TCH/F28.8 and GERAN TCH/F43.2 require EDGE capability. 4.13 GBS MMI aspects It shall be possible to configure the parameters negotiated and indicated at GBS call set-up and during user initiated modification. 4.14 GBS Subscription aspects HSCSD is not subscribed to. Users wanting to use multislot mechanism must subscribe to the General Bearer Services. 4.15 GBS charging aspects To allow accurate charging of multislot calls, a record of start and stop timestamps versus the number of TCH/F, for each change in TCH/F allocation, shall be provided. NOTE: For MO multislot calls, the A party is liable for the use of all the TCH/F in her PLMN. For MT multislot calls, the B party may have to pay for one or more of the TCH/F in her PLMN. In case the originating or terminating subscriber is a fixed network subscriber, there should be no additional charge (in respect of the changing allocation of GERAN TCH/F) for the originating or terminating fixed network subscriber. 4.16 O and M aspects For GBS call, there are several new and modified parameters compared to GSM Phase 2 data calls. For GBS, the air interface resource allocation may change several times during the call (network initiated and user initiated changes). It shall be possible to limit the frequency of changes per call, separately for network initiated and user initiated changes. Multislot calls can occupy multiple TCH/F. It shall dynamically be possible to limit the maximum number of GERAN TCH/F allowed for GBS calls per cell. 4.17 Multislot security aspects Authentication and ciphering are applicable to multislot calls with no or minimal reduction in the security of the air interface. ETSI ETSI TS 122 034 V3.2.1 (2000-04) 13 3G TS 22.034 version 3.2.1 Release 1999 5 Exceptional procedures or unsuccessful outcome When a GBS call is offered to an entity (either ME or network) unable to support the offered GBS call, it shall be possible, within the limitations of the service, to revert the call: - to an GBS call the entity can support; or - at GERAN to a GSM Phase 2 data service. 6 Interworking requirements 6.1 Service interworking 6.1.1 Interworking with supplementary services Supplementary Services that are applicable to the General Bearer Services can be used (Reference TS 22.004, [3]). 6.1.2 Interworking with other services The simultaneous use of multislot mechanism and SMS MO/PP, and multislot mechanism and SMS MT/PP services shall be possible. Interworking should be possible to all networks which are covered by GSM Phase 2 bearer services: - PSTN; - ISDN. ETSI ETSI TS 122 034 V3.2.1 (2000-04) 14 3G TS 22.034 version 3.2.1 Release 1999 Annex A (informative): Change history Change history TSG SA# SA Doc. SA1 Doc Spec CR Rev Rel Cat Subject/Comment Old New Jun 1999 02.34 Transferred to 3GPP SA1 8.1.0 3.0.0 SA#04 02.34 Transferred to 3GPP SA1 8.1.0 3.0.0 SP-05 SP-99479 S1-99615 22.034 001 R99 D Editorial changes for alignment 3.0.0 3.1.0 SP-05 SP-99448 S1-99706 22.034 002 R99 B Channel coding asymmetry for ECSD 3.0.0 3.1.0 SP-07 SP-000057 S1-000052 22.034 003 R99 C CR on HSCSD changes for 3GPP 3.1.0 3.2.0 Version Date Information about changes V3.0.0 July 1999 Transferred to TSG SA at ETSI SMG#29. Under TSG TSG SA Change Control. V3.1.0 October 1999 Inclusion of CRs at SA#05. V3.2.0 March 2000 Inclusion of CRs at SA#07. V3.2.1 April 2000 Editorial correction to title (Release 1999, not Release 2000) 15 ETSI ETSI TS 122 034 V3.2.1 (2000-04) 3G TS 22.034 version 3.2.1 Release 1999 History Document history V3.2.1 April 2000 Publication
|
1b2e466422f9168c75e4655878524e36
|
122 001
|
0 Scope
|
........................................................................................................................................................6
|
1b2e466422f9168c75e4655878524e36
|
122 001
|
0.1 References
|
............................................................................................................................................................... 6
|
1b2e466422f9168c75e4655878524e36
|
122 001
|
0.2 Abbreviations
|
.......................................................................................................................................................... 6
|
1b2e466422f9168c75e4655878524e36
|
122 001
|
1 Framework for the description of telecommunication services
|
...............................................................7
|
1b2e466422f9168c75e4655878524e36
|
122 001
|
1.1 The attribute method of characterization of circuit telecommunication services
|
.................................................... 7
|
1b2e466422f9168c75e4655878524e36
|
122 001
|
2 Description of circuit telecommunication services by the attribute method
|
............................................7
|
1b2e466422f9168c75e4655878524e36
|
122 001
|
2.1 General
|
.................................................................................................................................................................... 7
|
1b2e466422f9168c75e4655878524e36
|
122 001
|
2.2 Categorisation of telecommunication services
|
........................................................................................................ 7
|
1b2e466422f9168c75e4655878524e36
|
122 001
|
3 Characterization of circuit telecommunication services
|
..........................................................................7
|
1b2e466422f9168c75e4655878524e36
|
122 001
|
3.1 General
|
.................................................................................................................................................................... 7
|
1b2e466422f9168c75e4655878524e36
|
122 001
|
3.2 Bearer services
|
........................................................................................................................................................ 8
|
1b2e466422f9168c75e4655878524e36
|
122 001
|
3.3 Teleservices
|
............................................................................................................................................................. 8
|
1b2e466422f9168c75e4655878524e36
|
122 001
|
4 Provision of telecommunication services
|
................................................................................................8
|
1b2e466422f9168c75e4655878524e36
|
122 001
|
4.1 Subscription checking for Basic Services
|
................................................................................................................ 9
|
1b2e466422f9168c75e4655878524e36
|
122 001
|
4.2 Subscription checking for Supplementary Services
|
.............................................................................................. 10 Annex A (normative): List of definition of attributes and values used for bearer services..........11 A.1 Information transfer attributes ...............................................................................................................11 A.1.1 Information transfer capability ........................................................................................................................ 11 A.1.2 Information transfer mode ............................................................................................................................... 11 A.1.3 Information transfer rate.................................................................................................................................. 11 A.1.4 Structure........................................................................................................................................................... 11 A.1.5 Establishment of communication..................................................................................................................... 12 A.1.6 Communication configuration ......................................................................................................................... 12 A.1.7 Symmetry......................................................................................................................................................... 12 A.1.8 Data compression............................................................................................................................................. 13 A.2 Attributes describing the access at the user equipment..........................................................................13 A.2.1 Signalling access.............................................................................................................................................. 13 A.2.2 Information access........................................................................................................................................... 13 A.2.2.1 Rate.................................................................................................................................................................. 13 A.2.2.2 Interface........................................................................................................................................................... 13 A.3 Interworking attribute ............................................................................................................................14 A.3.1 Type of terminating network ........................................................................................................................... 14 A.3.2 Terminal to terminating network interface ...................................................................................................... 14 A.4 General attributes...................................................................................................................................14 A.4.1 Supplementary services provided .................................................................................................................... 14 A.4.2 Quality of service............................................................................................................................................. 14 A.4.3 Commercial and operational............................................................................................................................ 15 A.4.4 Service interworking........................................................................................................................................ 15 Annex B (normative): List of definitions of attributes and values used for teleservices...............16 B.1 High layer attributes...............................................................................................................................16 B.1.1 Type of user information ................................................................................................................................. 16 B.1.2 Layer 4 protocol functions............................................................................................................................... 16 B.1.3 Layer 5 protocol functions............................................................................................................................... 16 B.1.4 Layer 6 protocol functions............................................................................................................................... 16 B.1.5 Layer 7 protocol functions............................................................................................................................... 16 ETSI ETSI TS 122 001 V3.2.0 (2000-03) 4 3G TS 22.001 version 3.2.0 Release 1999 B.2 Low layer attribute (bearer capabilities)................................................................................................16 B.3 General attributes...................................................................................................................................16 Annex C (normative): Definition of "busy" in a PLMN..................................................................17 C.1 Scope......................................................................................................................................................17 C.2 Network Determined User Busy (NDUB) condition.............................................................................17 C.3 User Determined User Busy (UDUB) condition ...................................................................................17 C.4 Mobile subscriber busy..........................................................................................................................17 Annex D (normative): Call set-up procedures ..................................................................................18 D.1 Scope......................................................................................................................................................18 D.2 Mobile Originated Call Set-up...............................................................................................................18 D.2.1 Called Party Address ....................................................................................................................................... 18 D.2.2 Calling/Called Party Sub-address .................................................................................................................... 18 D.2.3 Type of Number............................................................................................................................................... 18 D.2.4 Number Plan Indicator..................................................................................................................................... 18 D.2.5 Bearer Capability............................................................................................................................................. 19 D.2.6 Calling Line Indication Restriction Override................................................................................................... 19 D.2.7 Action of the Network on Call Set-up ............................................................................................................. 19 D.3 Mobile Terminated Call Set-up .............................................................................................................19 D.3.1 Bearer Type ..................................................................................................................................................... 20 D.3.2 Response of the UE.......................................................................................................................................... 20 D.3.3 Description of Call Re-establishment .............................................................................................................. 20 Annex E (normative): Automatic calling repeat call attempt restrictions .....................................21 Annex F(informative): Procedures for call progress indications .....................................................23 F.1 General...................................................................................................................................................23 F.2 Supervisory tones...................................................................................................................................23 F.2.1 General............................................................................................................................................................. 23 F.2.2 Method............................................................................................................................................................. 23 F.2.3 Standard tones.................................................................................................................................................. 23 F.2.4 Applicability .................................................................................................................................................... 24 F.2.5 Comfort tones .................................................................................................................................................. 24 F.3 Recorded announcements ......................................................................................................................25 F.4 Application of call control cause information elements to supervisory tones .......................................26 Annex G (informative): Change history...............................................................................................27 ETSI ETSI TS 122 001 V3.2.0 (2000-03) 5 3G TS 22.001 version 3.2.0 Release 1999 Foreword This Technical Specification (TS) has been produced by the 3rd Generation Partnership Project (3GPP). The present document defines the telecommunication services supported by a GSM PLMN within the digital cellular telecommunications system (Phase 2+). 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 TS 122 001 V3.2.0 (2000-03) 6 3G TS 22.001 version 3.2.0 Release 1999 0 Scope The present document covers the definition of the circuit telecommunication services supported by a PLMN. The purpose of the present document is to provide a method for the characterization and the description of these telecommunication services. TS 22.101 describes overall service principles of a PLMN. 0.1 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] GSM 01.04: "Digital cellular telecommunications system (Phase 2+); Abbreviations and acronyms". [2] ITU-T Recommendation I.221: "Common specific characteristics of services". [3] ITU-T Recommendation X.200: "Information technology - Open Systems Interconnection - Basic reference model: The basic model". [4] TS 22.101: "UMTS Service Principles". [5] TS 22.002: "Bearer services supported by a PLMN". [6] TS 22.003: "Teleservices supported by a PLMN".[7] TS 22.004: "General on Supplementary Services". [8] TS 27.001: "General on Terminal Adaptation Functions (TAF) for Mobile Stations (MS)". [9] TS 22.030: "Man-Machine Interface (MMI) of the User equipment (MS)". [10] TS 22.081: "Line Identification Supplementary Servicess; Stage 1". [11] TS 22.135: "Multicall; Stage 1". [12] TR 21.905: "Vocabulary for 3GPP Specifications". [13] GSM 04.08: "Digital cellular telecommunications system (Phase 2+); Mobile radio interface layer 3 specification". 0.2 Abbreviations Abbreviations used in the present document are listed in GSM 01.04 and TR 21.905 [12]. ETSI ETSI TS 122 001 V3.2.0 (2000-03) 7 3G TS 22.001 version 3.2.0 Release 1999 1 Framework for the description of telecommunication services 1.1 The attribute method of characterization of circuit telecommunication services This characterization is made by using a set of attributes. A telecommunication service attribute is a specific characteristic of that service whole values distinguish it from other telecommunication services. Particular values are assigned to each attribute when a given telecommunication service is described and defined. A list of definitions of attributes and values used for bearer services and teleservices is contained in, respectively, annex A and annex B. 2 Description of circuit telecommunication services by the attribute method 2.1 General Telecommunication services are described by attributes which define service characteristics as they apply at a given reference point where the customer accesses the service. The description of a telecommunication service by the method of attributes is composed of: - technical attributes as seen by the customer; and - other attributes associated with the service provision, e.g. operational and commercial attributes. 2.2 Categorisation of telecommunication services The concepts introduced in the present document are illustrated in table1. Table 1: Categorisation of telecommunication services TELECOMMUNICATION SERVICES BEARER SERVICE TELESERVICE Basic Bearer Service Basic Bearer service + supplementary services Basic Teleservice Basic Teleservice + supplementary service 3 Characterization of circuit telecommunication services 3.1 General A telecommunication service supported by a PLMN is characterized and described by service attributes. There are two groups of service attributes applicable to user information flow: - low layer attributes; - high layer attributes. ETSI ETSI TS 122 001 V3.2.0 (2000-03) 8 3G TS 22.001 version 3.2.0 Release 1999 Bearer services are characterized only by low layer attributes. Teleservices are characterized by both low layer attributes and high layer attributes. The basic characteristics of a telecommunication service are described by the basic service attributes. The additional characteristics associated with a supplementary service which modify or supplement a basic telecommunication service are described in Specification TS 22.004 [7]. 3.2 Bearer services Bearer services are characterized by a set of low layer attributes in Specification GSM 02.02. These attributes are classified into four categories: - information transfer attributes; - access attributes; - interworking attributes; - general attributes, including operational and commercial attributes. The bearer capability defines the technical features of a bearer service as they appear to the user at the appropriate access point. For the time being, the bearer capability is characterized by information transfer, access and interworking attributes. A bearer capability is associated with every bearer service. 3.3 Teleservices Circuit teleservices provide the full capacity for communication by means of terminals and network functions and possibly functions provided by dedicated centres. Circuitteleservices are specified in TS 22.003 [6].Teleservices are characterized by a set of low layer attributes, a set of high layer attributes and operational and commercial attributes. Low layer attributes are those used to characterize the bearer capability. High layer attributes are used in Specification TS 22.003 [6] to describe high layer (i.e. layer 4-7) information transfer related characteristics. They refer to functions and protocols of layers 4-7 in the ITU-T Recommendation X.200 framework which are concerned with the transfer, storage and processing of user messages (provided by a subscriber's terminal, a retrieval centre or a network service centre). Therefore, not all attributes can be applied directly at the user to terminal interface as they represent two kinds of features, the bearer capability and the terminal features, that are not directly perceived by the user. 4 Provision of telecommunication services Specifications GSM 02.10 and GSM 02.11 define some aspects of the provisions of telecommunication services by a GSM PLMN. The provision of telecommunication services implies: - subscription of basic services and possibly subscription to supplementary services; - registration into a service directory; - compatibility between terminals; - interworking capabilities (see GSM 09 series of specifications). The user's subscription to a Basic or Supplementary service is normally verified by the network prior to completion of Call Establishment and/or Supplementary Service operation. This subscription checking shall be performed in accordance with the following subclauses. ETSI ETSI TS 122 001 V3.2.0 (2000-03) 9 3G TS 22.001 version 3.2.0 Release 1999 4.1 Subscription checking for Basic Services General Subscription checking is the function/process to ascertaining whether a subscriber has the authorization to use the particular Basic Service deduced from the call set-up parameters. It is the responsibility of the HPLMN to transfer, to the VPLMN, only the subscription data corresponding to those services a given subscriber is entitled to use in that VPLMN. For mobile originated calls, subscription checking is performed in the VLR, whilst for mobile terminated calls it is performed in either the HLR or the VLR (determined as described below). The prerequisite for executing the subscription check is a successful deduction of a Basic Service from the Compatibility Information contained in the call set up, i.e. Bearer Capability Information Element and, in some cases, also the Low Layer and High Layer Compatibility Information elements. For mobile originated calls an UE shall indicate the requested service by appropriate compatibility information elements according to GSM 27.001 [8]. This information is mapped to an individual Basic Service code (i.e. the MAP representation) by the MSC in order to be compared with the subscriber data available in the VLR. An equivalent process is required in the HLR for mobile terminated calls, where the caller's requested service is indicated to the HLR (by the ISDN) by exhaustive compatibility information consisting of ISDN Bearer Capability Information Elements and in some cases - depending on the service requested - also of Low Layer and High layer Compatibility information elements. In case the compatibility information is not exhaustive, e.g. when the call is originated/transited by a PSTN, no Basic Service can be deduced and subscription checking cannot be performed in the "normal" way. Instead, rules for the Single and Multi Numbering Schemes apply. In the Multi Numbering Scheme the Basic Service can be deduced by information stored in the HLR against the called number and hence an implicit subscription check is performed. In the Single Numbering Scheme, the Basic Service cannot be deduced until the UE has responded to the set up and therefore the HLR cannot perform subscription check. Instead, the VLR/MSC will perform the subscription check or calls are passed "unfiltered" (as regards subscription check), at the network operators' discretion. Bearer Services GSM 02.02 lists the Bearer Services, each of them with a specific "BS number". Single services defined independent of the fixed network user rate are called General Bearer Services. These distinct [numbered] services may individually be provided to a subscriber.Whichever the subscription arrangements are, all PLMNs (MSCs, VLRs and HLRs) shall be able to allow - as regards subscription checking - the use of individually subscribed-to Basic Services, within the range of services supported by the PLMN. That is, whenever it is possible to deduce the Basic Service from a call set up, subscription check shall be performed at the granularity of that particular Basic Service or the group to which it belongs. TeleServices TS 22.003 [6] lists the TeleServices, each of them with a specific "TS number". These may be provided to subscribers individually or combined, to the operators' discretion, however TS 12 (Emergency calls) and TS 23 (CBS) are not subscribable. But, as for Bearer Services, networks shall be able to handle subscription checking at the granularity of individual TeleServices. Table 2 summarizes the basis on which a successful subscription checking will result. It also describes on which basis Supplementary Service handling for a given call set-up should be performed. ETSI ETSI TS 122 001 V3.2.0 (2000-03) 10 3G TS 22.001 version 3.2.0 Release 1999 Table 2 Set Up Subscription Check SS handling BS 20 BS 20 BS Group 2x BS 30 BS 30 BS Group 3x TS 11 TS 11, TS Group 1x or TS Group All TS Group 1x TS 12 N.A. TS 21 TS 21, TS Group 2x or TS Group All TS Group 2x TS 22 TS 22, TS Group 2x or TS Group All TS Group 2x TS 23 N.A. TS 61 TS 61, TS Group 6x or TS Group All TS Group 6x TS 62 TS 61, 62, Group 6x or TS Group All TS Group 6x TS 91 TS 91, TS Group 9x or TS Group All TS Group 9x TS 92 TS 92, TS Group 9x or TS Group All TS Group 9x Legend: - set-up: The Basic Service which is set up for the call; - subscription check: Required VLR or HLR data for successful subscription check; - SS handling: Against which VLR or HLR data SS handling should be performed. For example; a call set-up indicating BS61 and Asynchronous mode should be treated for SS purposes in accordance with the SS-data stored against BS group 2x. When TS61 is requested in a call set-up and the subscription check for TS61 is negative, but a subscription check for TS62 is positive, then the call shall proceed according to the TS 22.003 [6]and TS 27.001 [8]. If a subscription check for both TS61 and TS62 is negative, then the call shall be released. This is described in GSM 02.04 and the GSM 03.8x series of specifications. ETSI ETSI TS 122 001 V3.2.0 (2000-03) 11 3G TS 22.001 version 3.2.0 Release 1999 Annex A (normative): List of definition of attributes and values used for bearer services A.1 Information transfer attributes A.1.1 Information transfer capability This attribute describes the capability associated with the transfer of different types of information through a PLMN and another network or through a PLMN. Values: - unrestricted digital information; transfer of information sequence of bits at its specified bit rate without alteration; this implies bit sequence independence, digit sequence integrity and bit integrity. - speech; digital representation of speech information and audible signalling tones of the PSTN coded according to the encoding rule defined in the GSM 06 series of specifications. - 3,1 kHz Ex PLMN; unrestricted digital information transfer within the PLMN and 3.1 kHz audio restricted within the ISDN. - group 3 Fax; transfer of Group 3 Fax information. A.1.2 Information transfer mode This attribute describes the operational mode of transferring (transportation and switching) through a PLMN. Values: - circuit. A.1.3 Information transfer rate This attribute describes the bit rate (circuit mode. It refers to the transfer of digital information between two access points or reference points. Values: - appropriate bit rate, throughput rate. A.1.4 Structure This attribute refers to the capability of the PLMN and if involved other networks to deliver information to the destination access point or reference point in a structure NOTE: This attribute has not been utilised in TS 22.002 [5] or TS 22.003 [6]. Values: - not applicable. ETSI ETSI TS 122 001 V3.2.0 (2000-03) 12 3G TS 22.001 version 3.2.0 Release 1999 A.1.5 Establishment of communication This attribute associated with a telecommunication service describes the mode of establishment used to establish and a given communication. In every telecommunication service communication may be between users within the PLMN or between a user in the PLMN and a user in another network. Values: - demand Mobile Originated (MO) only; - demand Mobile Terminated (MT) only; - demand Mobile Originated or Terminated (MO, MT). A.1.6 Communication configuration This attribute describes the spatial arrangement for transferring information between two or more access points. It completes the structure associated to a telecommunication services as it associates the relationship between the access points involved and the flow of information between these access points. Values: - point-to-point communication; this value applies when there are only two access points. - multipoint communication; this value applies when more than two access points (1) are provided by the service. The exact characteristics of the information flows must be specified separately based on functions provided by the PLMN. NOTE 1: The number of access points can be undefined. - broadcast communication; this value applies when more than two access points (2) are provided by the service. The information flows are from a unique point (source) to the others (destination) in only one direction. NOTE 2: The number of destination access points can be undefined. A.1.7 Symmetry This attribute describes the relationship of information flow between two (or more) access points or reference points involved in a communication. It characterizes the structure associated to a communication service. Values: - unidirectional; this value applies when the information flow is provided only in one direction. - bidirectional symmetric; this value applies when the information flow characteristics provided by the service are the same between two (or more) access points or reference points in the forward and backward directions. - bidirectional asymmetric; this value applies when the information flow characteristics provided by the service are different in the two directions. ETSI ETSI TS 122 001 V3.2.0 (2000-03) 13 3G TS 22.001 version 3.2.0 Release 1999 A.1.8 Data compression This attribute indicates whether use of a data compression function is desired (and accepted) between an MT and IWF. Values: - use of data compression requested/not requested; - use of data compression accepted/not accepted. A.2 Attributes describing the access at the user equipment A.2.1 Signalling access This attribute characterized the protocol on the signalling channel at a given access point or reference point Values: - manual; - appropriate V-series protocol; - appropriate X-series protocol; - I-series stack of signalling protocols. A.2.2 Information access A.2.2.1 Rate This attribute describes either the bit rate (circuit mode including transparent access to a PSPDN) or variable bit rate (packet mode) used to transfer the user information at a given access point or reference. Values: - appropriate bit rate; - variable bit rate. A.2.2.2 Interface This attribute describes the interface according to the protocol used to transfer user information at a given access point or reference. Values: - appropriate V-series DTE/DCE interface; - appropriate X-series interface; - S interface; - analogue 4-Wire interface. ETSI ETSI TS 122 001 V3.2.0 (2000-03) 14 3G TS 22.001 version 3.2.0 Release 1999 A.3 Interworking attribute A.3.1 Type of terminating network Communication can be established between a UE in a PLMN (originating network) and a terminal in a network (terminating network) including the same PLMN or another PLMN. The attribute designates the terminating network. NOTE 1: The terms "originating" and "terminating" do not indicate the direction of communication establishment. NOTE 2: This attribute does not reflect whether there is none, one or several transit networks between the originating and terminating networks. Values: - PSTN; - ISDN; - PSPDN; - PDN; - PLMN; - direct access networks. A.3.2 Terminal to terminating network interface This attribute describes the interface between a terminal equipment and the terminating network. Values: - appropriate V-series (DTE/DCE) interface; - appropriate X-series interface; - analogue 2 resp. 4 wire interface; - S interface (D+B+B). A.4 General attributes A.4.1 Supplementary services provided This attribute refers to the supplementary services to a given telecommunication service. Values: - appropriate supplementary services. A.4.2 Quality of service The Bearer Services use the Quality of Service attribute to indicate one of the following values: - transparent; service characterized by constant throughput, constant transit delay and variable error rate. - non-transparent; service characterized by an improved error rate with variable transit delay and throughput. ETSI ETSI TS 122 001 V3.2.0 (2000-03) 15 3G TS 22.001 version 3.2.0 Release 1999 A.4.3 Commercial and operational A.4.4 Service interworking ETSI ETSI TS 122 001 V3.2.0 (2000-03) 16 3G TS 22.001 version 3.2.0 Release 1999 Annex B (normative): List of definitions of attributes and values used for teleservices B.1 High layer attributes B.1.1 Type of user information This attribute describes the type of information which the communication offered to the user by the teleservice is based on. Values: - speech; - short message; - facsimile. B.1.2 Layer 4 protocol functions B.1.3 Layer 5 protocol functions B.1.4 Layer 6 protocol functions B.1.5 Layer 7 protocol functions B.2 Low layer attribute (bearer capabilities) The low layer attributes describe the bearer capabilities which support the teleservice. These low layer attributes and their values are the same as presented in Annex A: List of definitions of attributes and values used for bearer services. B.3 General attributes The general attributes are the same as presented in annex A: List of definitions and values used for bearer services. ETSI ETSI TS 122 001 V3.2.0 (2000-03) 17 3G TS 22.001 version 3.2.0 Release 1999 Annex C (normative): Definition of "busy" in a PLMN C.1 Scope This annex describes the conditions under which a given mobile subscriber (station) is considered as "busy". In general, this occurs whenever the resources associated with that UE (and needed to successfully complete the call) exist but are not available for that call. The description is based on the busy definition in the ISDN (CCITT Recommendation I.221). In addition, the operation of some Supplementary Services occurs when certain of these resources are busy. Therefore, these "resources busy" are also described herein. This annex does not cover the cases, when network resources not associated with a given destination are unavailable, or when such resources are out-of-service or otherwise non-functional. C.2 Network Determined User Busy (NDUB) condition This condition occurs, when a call is about to be offered, if the information (i.e. traffic) channel is busy and the maximum number of total calls has been reached (see note). This condition also occurs, when a call is about to be offered and an already on-going call attempt (incoming or outgoing) is in the establishing phase, i.e. not yet active. When NDUB condition occurs, the PLMN will clear the call and indicate "busy" back towards the calling subscriber (see also clause 4). NOTE: The value of the maximum number of calls is 1 for the basic call. When the supplementary service "Call Waiting" is applicable the value is n+1 where n is the maximum number of calls that can be waiting. TS 22.135 [11] defines NDUB for Multicall environment. C.3 User Determined User Busy (UDUB) condition This condition occurs when a call is offered to a user equipment and the UE responds "user busy" because the subscribers resources (terminal or person using them) are busy. Then the PLMN will clear the call with the indication "busy" back towards the calling subscriber (see also clause 4). C.4 Mobile subscriber busy A mobile subscriber is considered to be busy if either a "Network Determined User Busy" or a "User Determined User Busy" condition occurs. Some supplementary services (e.g. Call Forwarding on Busy) may cause the call not to be cleared when a busy condition occurs. ETSI ETSI TS 122 001 V3.2.0 (2000-03) 18 3G TS 22.001 version 3.2.0 Release 1999 Annex D (normative): Call set-up procedures D.1 Scope This annex specifies the service requirements for call set-up, both Mobile originated and mobile terminated, in a network, including the establishment of radio contact. D.2 Mobile Originated Call Set-up When an UE wishes to start a call and there is no existing radio connection, it requests a signalling channel. When such a signalling channel has been allocated to the UE, the UE can transfer the call set-up information. A traffic channel may be allocated at any time before the network informs the UE that the remote user has answered. For a call to be set up, certain information needs to be sent by the UE to the network, defining the call. This information may be provided as default by the MS, it may be derived from the SIM or be entered by the user either directly into the UE or from a DTE by using the DTE/DCE Interface. The following information is sent. Where necessary, default values will generally be inserted by the UE if not directly specified by the user. The Teleservice Emergency Calls are set up using a special procedure not using the fields described in this clause (except for the Bearer Capability). D.2.1 Called Party Address This is the address of the called party, generally as defined in GSM 03.03, using the TON/NPI specified below. In the case of Dedicated PAD or Packet Access, if NPI is set to PNP, the called party address field may be used to specify the profile to be used. In that case, the address of the called DTE will be given in-band as the second part of two-stage call set-up. D.2.2 Calling/Called Party Sub-address This is the sub-address of the calling/called party, as defined in GSM 03.03, in order to provide interworking with ISDN. This is described in more detail in ETS 300 059. Support and use of these fields are optional. D.2.3 Type of Number This indicates the format of the called party address. The selection procedure is given in TS 22.030 [9]. The following Types of Number are commonly used: - International Format; - Open Format ("Unknown"); - Dedicated PAD/Packet Access. D.2.4 Number Plan Indicator This indicates the number plan of the called party address. Either of the following number plans may be the "default", depending on the contents of the Called Party Address (see TS 22.030 [9]): - ISDN/Telephony E.164; ETSI ETSI TS 122 001 V3.2.0 (2000-03) 19 3G TS 22.001 version 3.2.0 Release 1999 - unknown. Alternatively, one of these number plans may be specified if appropriate: - data network X.121; - telex network F.69; - National Numbering Plan; - Private Numbering Plan. D.2.5 Bearer Capability This is used to define the type of call to be set up (telephony, data, rate etc.) For most applications, the UE will use a set of default conditions, generally on the assumption of a telephony call, unless otherwise set. These may be overridden by the user (or DTE via the DTE/DCE Interface) if desired except for the determination of the channel mode (full or half rate, speech codec conversion). The UE shall indicate to the network its channel mode capability in terms of the data channels and the speech codec versions supported. The network decides which mode to use on the basis of the requested bearer or teleservice, the available network resources and the channel mode capability of the UE: - for the "alternate" and "followed-by" services, the same principle applies (with the exception of TS61, where a Full Rate or an Enhanced Full Rate channel shall be provided); - for the full set of parameters and values, refer to GSM 04.08; - for data services see the GSM 07 series. Lower Layer Compatibility and Higher Layer Compatibility Information Elements may also be included. D.2.6 Calling Line Indication Restriction Override If the user wishes to override the calling line identification restriction, he may indicate this on a per-call basis as described in TS 22.030 [9] and TS 22.081 [10]. D.2.7 Action of the Network on Call Set-up On receipt of the call set-up message, the network shall attempt to connect the call. However, if insufficient information has been provided by the UE to indicate the exact Bearer Capability requirements (e.g. due to missing or optional values or for rate adaptation for data), the network may insert the missing information, if this is possible, and the call set-up shall proceed using the new information. If the call set-up is unsuccessful, the network shall notify the UE of the cause. D.3 Mobile Terminated Call Set-up Using the procedures described in TS 22.011, the network knows the location area where the UE is positioned. If the UE is not already in two way radio communication with the network, the network pages the MS. Upon receiving its page message, the UE establishes communication with the selected cell. The network then allocates a channel which is used for signalling and sends call set-up information to the UE. A traffic channel may be allocated at any instant until just after the call is answered by the UE. The network indicates to the UE that it wishes to offer the UE a call. This notification includes the proposed bearer capability information, where available (see subclause D.2.5). ETSI ETSI TS 122 001 V3.2.0 (2000-03) 20 3G TS 22.001 version 3.2.0 Release 1999 D.3.1 Bearer Type If the calling party specifies the required bearer capability this shall be used for the call set-up attempt. If the calling party does not specify the required bearer capability (e.g. because the call originated in the PSTN), the network shall attempt to determine the bearer capability to be used as described below. The network may use a multi-numbering scheme to define the bearer capability by the MSISDN. In a multi-numbering scheme several MSISDNs are associated with one IMSI. Each MSISDN is used for a different bearer capability. If the network uses a multi-numbering scheme and the calling party has not specified the required bearer capability then the network shall use the bearer capability associated with the called party MSISDN. The network may use a single-numbering scheme, in which one MSISDN is associated with each IMSI. If the network uses a single-numbering scheme and the calling party has not specified the required service then the network shall omit the bearer capability information. D.3.2 Response of the UE On receipt of the call set-up request from the network, the UE shall check that it is able to support the type of call requested and that it is not User Determined User Busy (see annex C). The UE then alerts the user. If the UE is unable to support the type of call requested, or the information is incomplete, the UE shall, if possible and not restricted by requirements in other ETSs, reply to the network proposing an alternative set of parameters, indicating those that are different from those proposed by the network. The network then either accepts this new proposal or terminates the call attempt. D.3.3 Description of Call Re-establishment Call re-establishment allows the user equipment to attempt to reconnect a call following the loss of radio coverage between the UE and the network while a call is in progress. Call re-establishment may be initiated by the UE when it detects this situation, if supported in the network. Call re-establishment is mandatory in the ME and optional in the network. ETSI ETSI TS 122 001 V3.2.0 (2000-03) 21 3G TS 22.001 version 3.2.0 Release 1999 Annex E (normative): Automatic calling repeat call attempt restrictions Call set up attempts referred to in this annex are assumed to be initiated from peripheral equipment or automatically from the MT itself. A repeat call attempt may be made when a call attempt is unsuccessful for the reasons listed below (as defined in GSM 04.08 [12]). These reasons are classified in three major categories: 1) "Busy destination": - cause number 17 User busy. 2) "Unobtainable destination - temporary": - cause number 18 No user responding; 19 User alerting, no answer; 27 Destination out of order; 34 No circuit/channel available; 41 Temporary failure; 42 Switching Equipment congestion; 44 Requested circuit/channel not available; 47 Resources unavailable, unspecified. 3) "Unobtainable destination - permanent/long term": - cause number 1 Unassigned (unallocated) number; 3 No route to destination; 22 Number changed; 28 Invalid number format (uncompleted number); 38 Network out of order. NOTE 1: Optionally, it is allowed to implement cause number 27 in Category 3, instead of Category 2, as this is desirable already in Phase 1. The table below describes a repeat call restriction pattern to any B number. This pattern defines a maximum number (n) of call repeat attempts; when this number n is reached, the associated B number shall be blacklisted by the MT until a manual re-set at the MT is performed in respect of that B number. When a repeat attempt to anyone B number fails, or is blacklisted, this does not prevent calls being made to other B numbers. ETSI ETSI TS 122 001 V3.2.0 (2000-03) 22 3G TS 22.001 version 3.2.0 Release 1999 For the categories 1 and 2 above, n shall be 10; for category 3, n shall be 1. call attempts Minimum duration between Call attempt Initial call attempt - 1st repeat attempt 5 sec 2nd repeat attempt 1 min 3rd repeat attempt 1 min 4th repeat attempt 1 min 5th repeat attempt 3 min nth repeat attempt 3 min The number of B numbers that can be held in the blacklist is at the manufacturers discretion but there shall be at least 8. However, when the blacklist is full the MT shall prohibit further automatic call attempts to any one number until the blacklist is manually cleared at the MT in respect of one or more B numbers. When automatic calling apparatus is connected to an MT1 or MT2, or where an MTO is capable of auto-calling, then the MT shall process the call requests in accordance with the sequence of repeat attempts defined above, i.e. requests for repeat attempts with less than the minimum allowed duration between them shall be rejected by the MT. A successful call attempt to a number which has been subject to the call restrictions shown above (i.e. an unsuccessful call set up attempt has previously occurred) shall reset the "counter" for that number. The "counter" for an unsuccessfully attempted B number shall be maintained in 24 hours or until the MT is switched off. The automatic calling repeat call attempt restrictions apply to speech and data services. NOTE 2: The restrictions only apply to unsuccessful Call Control activity, not to Radio Resource Management or to Mobility Management, so multiple attempts at radio channel access are not limited by this mechanism. ETSI ETSI TS 122 001 V3.2.0 (2000-03) 23 3G TS 22.001 version 3.2.0 Release 1999 Annex F(informative): Procedures for call progress indications F.1 General Indications of call progress, such as ringing, engaged, unobtainable, and no radio channel, may in principle be verbal message, tones, displayed text or graphical symbols. Which combination of these applies may depend on the message, the UE and selection by the user or PLMN operator. However, verbal announcements will generally be reserved for situations which are peculiar to a mobile network, where users may be unfamiliar with any tone chosen to indicate conditions such as "call diversion" or "subscriber not available". It may also be desirable to add comfort indications (e.g. tones, noise, music, clicks) while a call is being connected, since silence may cause an unfamiliar user to believe that nothing is happening. Generally, on data calls, and on the data part of alternate speech/data or speech-followed-by-data calls, PLMN generated network tones and announcements should be muted. F.2 Supervisory tones F.2.1 General Supervisory Tones, indicating primarily ringing, engaged and unobtainable numbers, may be generated by both the PLMN and PSTN. Except for ring tone, all tones indicating call progress to a user shall be generated in the UE, on the basis of signals from the network where available, and are according to the standard defined in the present document. Tones sent to a caller to a UE will be generated in the network, generally local to the caller, and will be to the standard of his local exchange, except for mobile to mobile calls, where the tones will be generated in the calling UE. For mobile terminated calls, the ring tone will be generated in the called MSC (except OACSU). F.2.2 Method In the interests of early release of the traffic channel on failure to succeed in setting up a (mobile originated) call, where possible supervisory tones should be indicated over signalling channels. The UE will then generate the required tones. However, if the network generates an in-band announcement this will be indicated to the UE. In this case the UE shall connect the user to the announcement until instructed to release the call, either by the user or by the network. An alternate procedure may apply for UE able to generate appropriate announcements internally. The ring tone will be sent over the traffic channel, since this channel must be available for traffic immediately it is answered (exception: Off Air Call Set Up). The Ring Tone is therefore generated by the PLMN or PSTN supporting the called phone. On failed mobile terminated call attempts, the called MSC will either signal to the caller, if this is possible, or else will generate the required supervisory tones. "Alert" is not a supervisory tone. The indication is signalled, and the UE may generate any form of indication to the user that the UE is being called. F.2.3 Standard tones UE generated tones will be generally in accordance with CEPT (GSM), ANSI T1.607 (PCS 1900), or Japan recommendations, where appropriate, and are listed in table 1. Any network originated tones will be according to PLMN or PSTN choice. ETSI ETSI TS 122 001 V3.2.0 (2000-03) 24 3G TS 22.001 version 3.2.0 Release 1999 F.2.4 Applicability This method will apply in all cases where signalling is capable of indicating the supervisory tone required. However, for connection to certain fixed networks where this signalling is not possible, fixed network tones will be carried over the traffic channel. User equipment may employ any suitable technique to indicate supervisory information. However, if tones are employed, they shall be in accordance with the present document. The use of these tones in the MSC is preferred. NOTE 1: The tones and/or announcement to the calling party should not be provided if the Information transfer capability is set to UDI. NOTE 2: For a call with information transfer capability set to 3.1 kHz, the use of tones and/or announcement may cause the expiry of an awaiting answer timer in a modem or fax machine. F.2.5 Comfort tones If desired by the PLMN operator, the network may optionally introduce "comfort tones" while the call is being connected, during what would otherwise be silence. This would be overridden by indication of a supervisory tone, an announcement or by traffic. PLMNs may offer this feature optionally to incoming or outgoing callers. The "comfort tones" may take the form of tones, clicks, noise, music or any other suitable form, provided that they cannot be confused with other indications that might be expected. This feature is intended to indicate to the user that his call is progressing, to prevent him terminating the call prematurely. ETSI ETSI TS 122 001 V3.2.0 (2000-03) 25 3G TS 22.001 version 3.2.0 Release 1999 Table 1: Supervisory tones in UEs Tone Frequency Tolerance Type CEPT ANSI Japan CEPT ANSI Japan CEPT ANSI Japan 1 Dial tone (optional) 425 Hz 350 Hz added to 440 Hz 400 Hz 15 Hz 20Hz Conti- nuous Continuous Conti- nuous 2 * Subscriber Busy (Called Number) 425 Hz 480 Hz added to 620 Hz 400 Hz 15 Hz 20Hz Tone on 500ms Silence 500ms Tone on 500ms Silence 500ms Tone on 500ms Silence 500ms 3 * Congestion 425 Hz 480 Hz added to 620 Hz Optional 15 Hz Optional Tone on 200ms Silence 200ms Tone on 250ms Silence 250ms Optional 4 Radio Path Acknowledgeme nt (Mobile Originated only) (optional) 425 Hz 425 Hz 400 Hz 15 Hz 20 Hz Single tone 200ms Single tone 200ms Tone on 1 Sec Silence 2 Sec 5 {Radio Path Not Available {Call Dropped – Mobile originated only 425 Hz 425 Hz Optional 15 Hz Optional 200ms} On/off 200ms} for 3 burst 200ms} On/off 200ms} for 3 burst Optional 6 * Error/Special Information} Number Unobtainable } Authentication Failure } 950 Hz 1400 Hz 1800 Hz 950 Hz 1400 Hz 1800 Hz Optional 50 Hz 50 Hz 50 Hz Optional {Triple Tone {Tones on 330ms {Silence 1.0s Triple Tone {Tones on 330ms {Silence 1.0s Optional 7 Call Waiting Tone (CEPT) 425 Hz (tolerance 15 Hz), on for 200 ms, off for 600 ms on for 200 ms, off for 3 s, on for 200 ms, off for 600 ms on for 200 ms. This tone is superimposed on the audio traffic received by the called user. Alternate tones are acceptable but not preferred. 7 Call Waiting Tone (ANSI) 440 Hz, on for 300 ms, 9,7 s off followed by (440 Hz, on for 100 ms off for 100 ms, on for 100 ms, 9,7s off and repeated as necessary) This tone is superimposed on the audio traffic received by the called user. 7 Call Waiting Tone (Japan) Optional Definition of these and other tones, together with advice on announcements, may be found in CEPT T/CS 20-15 and in T/SF 23. NOTE: *: The duration of these tones is an implementation option. However, in each case, the UE should be returned immediately to the idle state, and will be able to originate/receive calls, which will override these tones. Ringing Tone (Alternative National options permitted) 425Hz 440 Hz added to 480 Hz Option al 15 Hz Optional Tone on 1 s Silence 4 s Tone on 2 s Silence 4 s Optional For application of Call Control Cause Information Elements to these tones, see F.4. F.3 Recorded announcements In present networks, both fixed and cellular, the language of recorded announcements and displayed information is invariably that of the country of origin. However, this is generally undesirable in a multi-lingual environment such as is encountered on a global network with international roaming. It is therefore probably desirable to minimise the number of such announcements. Advanced UEs may be designed which have the ability to generate announcements in the form desired by the user, e.g. in the language preferred by the user. In this case, it becomes necessary to block any verbal announcements sent from the network towards the UE, to avoid clashes with those generated by the UE. The UE may be allowed to block in-band announcements in case appropriate announcements according to the Cause Information Elements (F.3) can be generated. The default setting of the UE shall be "non blocking", which could be set by MMI command to "blocking". ETSI ETSI TS 122 001 V3.2.0 (2000-03) 26 3G TS 22.001 version 3.2.0 Release 1999 Announcements generated by the PLMN and sent to callers to that PLMN will generally be in the language of the PLMN. However, on some fixed networks it will be possible for the message to be signalled back to the caller's local exchange, which will then generate the announcement in its local language. F.4 Application of call control cause information elements to supervisory tones The Cause Information Elements are listed and defined in GSM 04.08 [13]. This annex lists these elements and indicates which supervisory tone should be generated in response. It should be noted that some conditions (e.g. radio path not available, dropped call) may be deduced by the UE, rather than signalled explicitly over the air interface. All causes not listed below should result in the generation of tone 6. In case of multiple calls a tone should only be generated if it does not disturb an ongoing active call. "-" indicates no tone required. Cause Tone CC (see table 1) 16 Normal Clearing 1 17 User Busy 2 22 Number Changed - 30 Response to STATUS ENQUIRY - 31 Normal, unspecified - 34 No circuit/channel available 3 41 Temporary Failure 3 42 Switching Equipment Congestion 3 44 Requested circuit/channel not available 3 49 Quality of Service Unavailable 3 58 Bearer Capability not available 3 ETSI ETSI TS 122 001 V3.2.0 (2000-03) 27 3G TS 22.001 version 3.2.0 Release 1999 Annex G (informative): Change history Change history TSG SA# SA Doc. SA1 Doc Spec CR Rev Rel Cat Subject/Comment Old New Dec 1999 02.01 Transferred to 3GPP SA1 8.1.0 3.0.0 SP-06 SP-99519 S1-991076 22.001 001 R99 D Mainly an editorial update for GSM/3GPP use 3.0.0 3.1.0 SP-07 SP-000069 S1-000124 22.001 002 R99 D Editorial modification for change of SMS-CB to CBS 3.1.1 3.2.0 SP-07 SP-000053 S1-000133 22.001 003 R99 C Procedure for call progress indications 3.1.1 3.2.0 Version Date Information about changes V3.0.0 December 1999 Transferred to TSG SA at 3GPP SA#6. Under TSG TSG SA Change Control. V3.1.0 December 1999 Implemented CRs approved at SA #06. V3.2.0 March 2000 Implemented CRs approved at SA #07. 28 ETSI ETSI TS 122 001 V3.2.0 (2000-03) 3G TS 22.001 version 3.2.0 Release 1999 History Document history V3.2.0 March 2000 Publication
|
f6ec10375c84d952b769ca7d3f59d51a
|
122 024
|
1.1 References
|
.......................................................................................................................................................... 5
|
f6ec10375c84d952b769ca7d3f59d51a
|
122 024
|
1.2 Definitions and abbreviations
|
............................................................................................................................ 5
|
f6ec10375c84d952b769ca7d3f59d51a
|
122 024
|
4.2.1 The Current Call Meter (CCM)
|
.................................................................................................................... 9
|
f6ec10375c84d952b769ca7d3f59d51a
|
122 024
|
4.2.2 The Accumulated Call Meter (ACM)
|
.......................................................................................................... 9
|
f6ec10375c84d952b769ca7d3f59d51a
|
122 024
|
4.2.3 The ACM Maximum Value (ACMmax)
|
.................................................................................................... 10
|
f6ec10375c84d952b769ca7d3f59d51a
|
122 024
|
4.2.4 The Price per Unit and Currency Table (PUCT)
|
........................................................................................ 10
|
f6ec10375c84d952b769ca7d3f59d51a
|
122 024
|
4.3 Special processing
|
........................................................................................................................................... 10
|
f6ec10375c84d952b769ca7d3f59d51a
|
122 024
|
5 Functional operation in PLMN
|
..............................................................................................................11
|
f6ec10375c84d952b769ca7d3f59d51a
|
122 024
|
5.1 Outgoing calls
|
.................................................................................................................................................. 11
|
f6ec10375c84d952b769ca7d3f59d51a
|
122 024
|
5.2 Incoming calls
|
.................................................................................................................................................. 11 Annex A: Change history.................................................................................................................................13 History..............................................................................................................................................................14 ETSI TS 122 024 V3.0.1 (2000-01) ETSI TS 122 024 V3.0.1 (2000-01) ETSI (3G TS 22.024 version 3.0.1 Release 1999) 3GPP 3G TS 22.024 V3.0.1 (1999-10 4 3G TS 22.024 version 3.0.1 Foreword This Technical Specification 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: 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; ETSI TS 122 024 V3.0.1 (2000-01) ETSI (3G TS 22.024 version 3.0.1 Release 1999) 3GPP 3G TS 22.024 V3.0.1 (1999-10 5 3G TS 22.024 version 3.0.1 1 Scope The charging supplementary service is described in TS 22.086 [2]. These services are designed to supply to a mobile user sufficient information to allow a real-time estimate to be made of the bill which will eventually be levied in the home PLMN on the Mobile Station (MS) subscriber. In the case of certain MS uses, for example a mobile payphone, this estimate could be subject to further processing (e.g. to present the charges in currency, rather than units, this may include an additional mark up). This additional processing is not described in this document in order to avoid constraining the evolution of the MS product in this area. This document gives an overall view of how this supplementary service shall operate both in the PLMN and within the MS. Text given in this document is required to define functionality and is not intended to constrain implementation. 1.1 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. • For this Release 1999 document, references to GSM documents are for Release 1999 versions (version 8.x.y). [1] GSM 01.04: "Digital cellular telecommunications system (Phase 2+); Abbreviations and acronyms". [2] TS 22.086: "Advice of Charge (AoC) Supplementary Services - Stage 1". [3] TR 21.905: "Vocabulary for 3GPP Specifications". 1.2 Definitions and abbreviations In addition to the following, abbreviations used in the present document are listed in GSM 01.04 [1] and TS 21.905 [3]. Mark up (MU): An increase over the basic charge e.g. to provide extra revenue or to cover additional costs. Service Provider (SP): The organization through which the subscriber obtains PLMN services. This may be the network operator or possibly a separate body. Home Units (HU): The published basic telecommunication unit as published by the HPLMN. This has a published value expressed in the currency of the Home country. Local PLMN (LPLMN): The LPLMN is the HPLMN or VPLMN depending on the location of the MS at the time and is the PLMN with which the MS is interworking via the radio interface. Local Units (LU): ETSI TS 122 024 V3.0.1 (2000-01) ETSI TS 122 024 V3.0.1 (2000-01) ETSI TS 122 024 V3.0.1 (2000-01) ETSI (3G TS 22.024 version 3.0.1 Release 1999) 3GPP 3G TS 22.024 V3.0.1 (1999-10 6 3G TS 22.024 version 3.0.1 The published basic telecommunication unit as published by the LPLMN. This has a published value expressed in the currency of the local country. Price per Unit and Currency Table (PUCT): The PUCT is the value of the Home unit in a currency chosen by the subscriber. The PUCT is stored in the SIM. The value of the PUCT can be set by the subscriber and may exceed the value published by the HPLMN. The PUCT value does not have any impact on the charges raised by the HPLMN. Current Call Meter (CCM): The accumulated charge as computed by the MS, expressed in terms of Home units. Accumulated Call Meter (ACM): The accumulated charge for both the current call and all preceding calls as computed by the MS, expressed in terms of Home units. The ACM is stored in the SIM/USIM. ACM Maximum value (ACMmax): The ACMmax sets the upper limit for the ACM. The ACMmax is stored in the SIM/USIM. The value of the ACMmax can be set by the subscriber. Charging point (CHP): The time at which charging commences i.e. at the point when the called party answers or the equivalent. End of charge point (CEND): The time at which the calling, or called, party stops charging by the termination of the call or by an equivalent procedure invoked by the network or by failure of the radio path. Advice of Charge (AOC): The charge as computed by the MS, expressed in terms of Home Units. Segment: A charging element as defined by ITU-T, in octets (up to 64).
|
f6ec10375c84d952b769ca7d3f59d51a
|
122 024
|
2 Introduction
|
The principle of this service is that the MS shall be capable of indicating the cost of a call in home units as a basic service. This is the Advice of Charge (AOC). The ability for the MS to perform further processing on AOC is not precluded. If the subscriber wishes, the MS shall indicate the value of CCM, ACM, ACMmax in the currency she has indicated using the PUCT. At the charging point, the MS is informed of the charging rate. The MS shall then use its independent internal clock to time the call from the charging point to the end of call i.e. the chargeable duration (CDUR) is measured by the MS. In the case of multiple calls this applies separately for each call (see subclause 4.3 l). The time taken attempting to perform call reestablishment is not included in CDUR (see subclause 4.3 m). By using the calculations described in clause 4, the MS shall be able to derive the number of home units used. Due to the independence of the calculated value, an exact one-to-one relation with the bill cannot be guaranteed. This discrepancy is due to the short delays in signalling between the MS and the network, e.g. transmission of charging point and end of call signals. In deriving the present document the following principles are assumed: ETSI TS 122 024 V3.0.1 (2000-01) ETSI TS 122 024 V3.0.1 (2000-01) ETSI TS 122 024 V3.0.1 (2000-01) ETSI (3G TS 22.024 version 3.0.1 Release 1999) 3GPP 3G TS 22.024 V3.0.1 (1999-10 7 3G TS 22.024 version 3.0.1 i) For mobile originated calls, the mobile user pays for the connection to the dialled number, as per the published tariff of the Local PLMN, plus a mark-up defined by the HPLMN to cover additional administration costs, when roaming. It is assumed that the MS subscriber will not be charged for the forwarded leg if the dialled number has set call forwarding. If additional charging is required for this forwarded leg, then it is assumed that such charging will be applied only to the called party. This follows current telecommunications practice. ii) For mobile terminated calls, any charge set for incoming calls is that based on the tariff as published by the HPLMN. The tariff as published for the roaming extension charges is assumed to be time and date invariant. For the avoidance of doubt, this assumption does not preclude routine tariff changes. iii) Charge rates for calls originating within a PLMN vary depending upon, for example, location, destination, service, time of day, type of day and any mark ups. iv) The units indicated in the advice of charge are always given in terms of Home units, the value of which is defined and published by the HPLMN, regardless of the PLMN in which they were incurred or the call direction or the type of call including supplementary service and data calls.
|
f6ec10375c84d952b769ca7d3f59d51a
|
122 024
|
3 Charge Advice Information
|
The MS is supplied with the necessary Charge Advice Information (CAI) at the charging point on a per call basis, in a signalling message over the radio interface. The MS uses the CAI elements to compute the AOC value for the relevant call. Thus the signalling CAI not only provides charging information, but indicates the charging point and hence initiates the timing of the chargeable duration. The information sent to the MS from the MSC consists of seven elements as follows: Table 1: Information elements Element Dimensions Description MIN MAX RES e1 u/i Units per interval 0 819.1 0.1 e2 t/i Seconds/time interval 0 819.1 0.1 e3 - Scaling Factor 0 81.91 0.01 e4 u Unit increment 0 819.1 0.1 e5 u/d Units per data interval 0 819.1 0.1 e6 seg/d Segments/data interval 0 8191 1 e7 t/i Initial secs/t interval 0 819.1 0.1 where: u = units; t = time; i = interval; seg = segments; d = data interval. The CAI Message need only contain those elements required for the particular situation. If elements are missing from the initial CAI message of a call, they shall be treated as zero. Element e1 - This element defines the number of units incremented per interval. It is set in terms of LPLMN units/interval to a resolution as defined in the table above under RES. Element e2 - This element defines the time interval for unitization, and is specified in seconds, to a resolution as defined in the table above under RES. Element e3 - ETSI TS 122 024 V3.0.1 (2000-01) ETSI TS 122 024 V3.0.1 (2000-01) ETSI TS 122 024 V3.0.1 (2000-01) ETSI (3G TS 22.024 version 3.0.1 Release 1999) 3GPP 3G TS 22.024 V3.0.1 (1999-10 8 3G TS 22.024 version 3.0.1 This element defines the scaling factor to convert from LPLMN units to HPLMN units. It is a dimensionless multiplier given to a resolution as defined in the table above under RES. Element e4 - This element defines the number of units to be incremented on receipt of the message containing the CAI elements. It is specified in units of the LPLMN to a resolution as defined in the table above under RES. Element e5 - This element defines the number of units incremented per data interval. It is set in terms of LPLMN units/interval, to a resolution as defined in the table above under RES. Element e6 - This element defines the data usage interval for unitization, and is specified in segments (SEG), to a resolution as defined in the table above under RES., for Dedicated Access to the PSPDN (whether directly or via Dedicated PAD). It does not apply to circuit switched access to modems or PADs, (except Dedicated PAD's) or MS to MS calls. Element e7 - This element defines the initial time interval for unitization, and is specified in seconds, to a resolution as defined in the table above under RES.
|
f6ec10375c84d952b769ca7d3f59d51a
|
122 024
|
4 Functional operation in MS
|
Simple operation in the MS is described by the equation:- AoC = e3 * { e4 + e1*INT(CDUR/(e7,e2)) + e5*INT(SEG/e6)} = scaling * { constant + time related + data related } where: AoC is the Advice of Charge in home units. CDUR is the Chargeable DURation as measured by the MS. SEG is the SEGment count as counted by the MS. INT(v)is the function to take the INTeger value of v. * indicates multiply operator. e7,e2 indicate first e7 then e2 selected as described below.
|
f6ec10375c84d952b769ca7d3f59d51a
|
122 024
|
4.1 Handling of the CAI elements
|
For the detailed mechanisms, the conditions given under subclause 4.3 (Special Processing) must be observed. The following therefore describes the process for a simple single call scenario, for either an incoming or outgoing call for the MS in any PLMN, including HPLMN:- On receipt of the CAI message, charging computation commences. INITIAL/FIXED CHARGE: Element e4*e3 defines the number of HPLMN units to be incremented in the Current Call Meter (CCM, see below) on receipt of the CAI message. INITIAL TIME RELATED CHARGE: On first receipt of the CAI message, timing commences immediately and MS timer CDUR is incremented, from zero, with a precision of at least 0.1 seconds. When CDUR reaches e7 (see special processing for the case where ETSI TS 122 024 V3.0.1 (2000-01) ETSI TS 122 024 V3.0.1 (2000-01) ETSI TS 122 024 V3.0.1 (2000-01) ETSI (3G TS 22.024 version 3.0.1 Release 1999) 3GPP 3G TS 22.024 V3.0.1 (1999-10 9 3G TS 22.024 version 3.0.1 e7 is equal to zero) i.e. a full interval has been timed, then e1*e3 HPLMN units are added to the CCM. CDUR is then reset to zero to allow timing of the next interval to commence based on CAI element e2. Element e7 is not used further, unless it is updated via a new CAI message. TIME RELATED CHARGE: On expiry of the interval defined by e7; e2 is applied and timing re-commences immediately. MS timer CDUR is incremented, from zero, with a precision of at least 0.1 seconds. When CDUR reaches e2 i.e. a full interval has been timed, then e1*e3 HPLMN units are added to the CCM. CDUR is then reset to zero to allow timing of the next interval to commence, based on e2. DATA RELATED CHARGE: On first receipt of non-zero element e6, data segment counting commences immediately and MS counter SEG is incremented, from zero, by unity for each segment transferred. When SEG reaches e6 i.e. a full data interval has been counted, then e5*e3 HPLMN units are added to the CCM. SEG is then reset to zero to allow counting of the next data interval to commence. NOTE 1: Elements e1, e7 and e2 have no effect on the initial charge or fixed charges applied i.e. are independent of e4. NOTE 2: It should be noted that e1 in conjunction with e2 increases charging range compared to a regime based on e2 only. (i.e. e1 fixed at unity). This benefit is secondary to the support of call charging for roamers, which is the main function of e1. NOTE 3: e1 improves the precision for high cost calls, where the interval, as defined by e2, may need to be excessively small, e.g. long haul international calls or INMARSAT. i.e. e1 can be increased instead of reducing e2, with some loss of accuracy of correlation with the actual bill. NOTE 4: Element e5, for data usage charging, is equivalent to e1 (time related charging) and provides similar benefits for the support of data usage charges for roamers and high cost data calls. NOTE 5: Rules for handling of CAI elements in the case of multiple calls are given in subclause 4.3 l.
|
f6ec10375c84d952b769ca7d3f59d51a
|
122 024
|
4.2 Handling of call meters
|
Two meters are defined. 4.2.1 The Current Call Meter (CCM) This is required to accumulate the charging units generated by the current call and is capable of advising: a) The current charge due for the call(s) in progress. b) At the end of the call(s), the charge equivalent to the current call record in an itemized bill. The CCM shall hold the value of the last call AOC, until the initiation of an outgoing call or acceptance of an incoming call, at which point it shall be reset to zero, regardless of the success of the initiation/acceptance attempt. This information is deleted when the MS is switched off or the SIM/USIM is removed. The CCM is essential for the correct functioning of AOC, see subclauses 4.1 and 4.3, and is a component of the Mobile Equipment. The charging computation shall cease immediately on termination of a call, as indicated by the user or the network, or on failure of the call. For multiple calls, CCM will advise the total charge of all the calls made and/or received during occupation of a traffic channel. 4.2.2 The Accumulated Call Meter (ACM) The Accumulated Call Meter accumulates the total units for both the current call and all preceding calls. The ACM is a function contained within the SIM/USIM. It is optional, but is essential for certain applications. ETSI TS 122 024 V3.0.1 (2000-01) ETSI TS 122 024 V3.0.1 (2000-01) ETSI TS 122 024 V3.0.1 (2000-01) ETSI (3G TS 22.024 version 3.0.1 Release 1999) 3GPP 3G TS 22.024 V3.0.1 (1999-10 10 3G TS 22.024 version 3.0.1 For security reasons, the SIM/USIM only allows the value of the ACM to be incremented, not decremented. Resetting of the ACM shall only be possible after presentation of PIN2. If the ACMmax (see subclause 4.2.3) is valid, and the ACM becomes equal to or exceeds the value of the ACMmax, then all calls in progress, chargeable to the user (i.e. those calls that have a non-zero AoC associated with them), shall be terminated by the ME once the chargeable interval determined by the CAI has elapsed. The ACM will be updated with the new value, which may be greater than the ACMmax value. The reason why the call has terminated shall be given to the user by means of an appropriate indication given to the user. If the ACMmax is valid and the ACM is equal to or greater than the value of ACMmax, then no outgoing calls can be placed, except Emergency calls. If the ACMmax is valid and the ACM is equal to or greater than the value of ACMmax, and an incoming call is received and subsequently a non-zero CAI is received for that call, then the call shall be terminated by the ME with an appropriate indication given to the user. 4.2.3 The ACM Maximum Value (ACMmax) This is the value that the subscriber can set, to limit the units which may be consumed by a user. The MS may provide for the means to set or update the ACMmax, using PIN2. The ACMmax is not valid if set to zero. NOTE: The network operator should make clear to the subscriber that the ACMmax must not be set to a value close to the maximum value possible in the encoding of ACMmax . The network operators should provide guidance as to what the maximum value for the ACMmax may be. 4.2.4 The Price per Unit and Currency Table (PUCT) This is intended to enable the MS to calculate the cost of a call in a currency chosen by the subscriber. The subscriber may set the value of the home unit in the PUCT differently to the value of the unit published by the HPLMN in order to cover extra cost. An indication of the currency in use is part of the PUCT . 4.3 Special processing a) If e7 is zero or not sent in the CAI message, e2 applies and e7 is not used. b) If e2 or e6 are set to zero, the relevant INT function shall handle the singularity by returning zero, thus disabling the relevant unitization process (call or data part). c) On receipt of a subsequent e4, the MS shall transfer the value of e4*e3 to the CCM, by addition of e4*e3 to the current contents of the CCM. d) When CDUR reaches e2 (or e7 as appropriate), e1*e3 is added to the CCM and CDUR is reset to zero, except when conditions given in (a) and (b) above, apply. e) On receipt of new e1, e2 or e7 during a call, these new values are held in abeyance, until the value of the associated MS timer CDUR has reached the current e2 or e7 value as appropriate, and the processing as described in special processing item d) above has been completed. The new e1, e2 and/or e7 are then brought into operation. e7 is applied followed by e2, conditions a) and b) above determining the detailed processing. Any update of e1, e2 and/or e7 during the time before CDUR is reset, shall supersede any values already held in abeyance. If CDUR is not actively timing (i.e. due to e2 being zero, e7 being zero or the processing of e7 has been completed), then a new value of e2 and/or e7 is applied immediately as per a normal new call. f) When SEG reaches e6, e5*e3 is added to the CCM and SEG is reset to zero, except where e6 is zero, where condition (b) above applies. g) On receipt of a new e5 or e6 during the call, these new elements are held in abeyance, until the value of the associated MS counter SEG has reached the old e6 value, and the processing as described in special processing item (f) above has been completed. The resulting zero SEG and new e5 and e6 are then brought into operation. Any update of e5 or e6 during the time before SEG is reset, shall supersede any values already held in abeyance. ETSI TS 122 024 V3.0.1 (2000-01) ETSI TS 122 024 V3.0.1 (2000-01) ETSI TS 122 024 V3.0.1 (2000-01) ETSI (3G TS 22.024 version 3.0.1 Release 1999) 3GPP 3G TS 22.024 V3.0.1 (1999-10 11 3G TS 22.024 version 3.0.1 If the old value of e6 was zero, then the new value of e5 and e6 is applied immediately. h) The ACM shall be incremented when the CCM is incremented or once every 5 seconds, which ever is the longer period. Although the CCM is maintained with an accuracy of three places of decimals, the ACM shall be incremented and stored as integer units (i.e. no decimal places). The ACM shall be incremented by the difference between the present value of the CCM (rounded up) and the value of the CCM (rounded up) at the previous ACM incrementation. i) A zero value for any of the CAI elements is valid and dealt with as described above. j) Free calls should be implemented by sending a CAI message with appropriate zero elements. k) On receipt of any CAI message from the network, provided the MS supports AoC, the MS it shall confirm receipt of the CAI message. An MS not supporting AoC as defined in TS 22.24 and TS 22.086 [2] shall not confirm receipt of the message. l) During multiple calls the network shall send, and the MS shall receive, CAI elements for each call separately. The CCM shall record the sum of all the charges for the services being used currently. m) If the MS detects a radio link failure the MS shall suspend CDUR. If a subsequent call reestablishment is successful, CDUR shall be resumed when call reestablishment is complete. 5 Functional operation in PLMN For applicable calls, the PLMN shall send the CAI message to the MS immediately the called party answers. The PLMN derives the values of the elements to be sent in the CAI message in the following way: 5.1 Outgoing calls The local PLMN, be it the HPLMN or the VPLMN, always sets values of e1, e2, e4, e5, e6 and e7 in terms of units of the LPLMN and according to its own tariff structure. Element e3 is set according to variables of the LPLMN and the relevant HPLMN. If the LPLMN is the HPLMN (i.e. the MS is in its Home PLMN) then e3 shall be simplified to unity. There shall be only one value of e3 for a given combination of HPLMN and VPLMN. This value may be simply loaded into the VMSC of the LPLMN using the Man Machine Interface commands, since it is not expected to vary frequently and is independent of the type of outgoing call. 5.2 Incoming calls For incoming calls the HPLMN determines the tariff and this tariff is dependent on the LPLMN of the MS. Therefore all the CAI elements are set according to the HPLMN tariff as a function of LPLMN. In the case of the LPLMN being the HPLMN these elements may be set to zero assuming the HPLMN does not charge for incoming calls. For roaming (i.e. where the LPLMN is not the HPLMN), in order to charge for incoming calls, the VPLMN must be provided with specific CAI values as defined by each HPLMN (e1i through e7i inclusive). This may be achieved by loading the offered HPLMN derived values via the VPLMN MMI. Each VPLMN will require a set of 7 values per HPLMN with which the VPLMN has a roaming agreement i.e.: e1i(h), e2i(h), e3(h), e4i(h), e5i(h), e6i(h) and e7i(h). ETSI TS 122 024 V3.0.1 (2000-01) ETSI TS 122 024 V3.0.1 (2000-01) ETSI TS 122 024 V3.0.1 (2000-01) ETSI (3G TS 22.024 version 3.0.1 Release 1999) 3GPP 3G TS 22.024 V3.0.1 (1999-10 12 3G TS 22.024 version 3.0.1 These are derived by: e1i(h)=e1H(h)/e3(h); e4i(h)=e4H(h)/e3(h); e5i(h)=e5H(h)/e3(h); where : h represents the 'h'th HPLMN with a roaming relationship with the VPLMN; i indicates the CAI element as determined by the 'h'th HPLMN, for the charging of incoming calls; the same value of e3 is used for both incoming and outgoing calls; exH(h) represents the value of the element x, given in terms of HPLMN units; exi(h) represents the value of the element x as handled by the VPLMN. ETSI TS 122 024 V3.0.1 (2000-01) ETSI TS 122 024 V3.0.1 (2000-01) ETSI TS 122 024 V3.0.1 (2000-01) ETSI (3G TS 22.024 version 3.0.1 Release 1999) 3GPP 3G TS 22.024 V3.0.1 (1999-10 13 3G TS 22.024 version 3.0.1 Annex A: Change history Change history TSG SA# Spec Versi on CR <Phase> New Version Subject/Comment Jun 1999 GSM 02.24 7.0.0 Transferred to 3GPP SA1 SA#04 22.024 3.0.0 SA#05 22.024 3.0.0 001 R99 3.0.1 Editorial update of references for GSM/3GPP use ETSI TS 122 024 V3.0.1 (2000-01) ETSI TS 122 024 V3.0.1 (2000-01) ETSI TS 122 024 V3.0.1 (2000-01) ETSI (3G TS 22.024 version 3.0.1 Release 1999) 14 ETSI ETSI TS 122 024 V3.0.1 (2000-01) (3G TS 22.024 version 3.0.1 Release 1999) History Document history V3.0.1 January 2000 Publication
|
225cf9c9633d392f7d3beb5ed1519d85
|
104 072
|
1 Scope
|
The present document specifies a facility layer service for providing parking space availability and intention information from vehicular ITS-Stations to other ITS-Stations.
|
225cf9c9633d392f7d3beb5ed1519d85
|
104 072
|
2 References
| |
225cf9c9633d392f7d3beb5ed1519d85
|
104 072
|
2.1 Normative 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. Referenced documents which are not found to be publicly available in the expected location might be found in the ETSI docbox. 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 are necessary for the application of the present document. [1] ETSI TS 103 836-4-1: "Intelligent Transport Systems (ITS); Vehicular Communications; GeoNetworking; Part 4: Geographical addressing and forwarding for point-to-point and point-to- multipoint communications; Sub-part 1: Media-Independent Functionality; Release 2". [2] ETSI TS 103 097: "Intelligent Transport Systems (ITS); Security; Security header and certificate formats; Release 2". [3] ETSI TS 102 894-2: "Intelligent Transport Systems (ITS); Users and applications requirements; Part 2: Applications and facilities layer common data dictionary; Release 2". [4] Recommendation ITU-T X.691 (2021-02): 'Information technology - ASN.1 encoding rules: Specification of Packed Encoding Rules (PER)'. [5] ETSI TS 102 965: "Intelligent Transport Systems (ITS); Application Object Identifier (ITS-AID); Registration; Release 2".
|
225cf9c9633d392f7d3beb5ed1519d85
|
104 072
|
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] ETSI TS 103 916: "Intelligent Transport Systems (ITS); Parking Availability Service; Release 2". [i.2] ETSI TS 103 898: "Intelligent Transport Systems (ITS); Communications Architecture; Release 2". [i.3] ETSI TS 103 938: "Intelligent Transport Systems (ITS); Vehicular Communications; Basic Set of Applications; Local Dynamic Map (LDM); Release 2". [i.4] ETSI EN 302 890-1: "Intelligent Transport Systems (ITS); Facilities layer function; Part 1: Services Announcement (SA) specification". ETSI ETSI TS 104 072 V2.1.1 (2025-07) 8 [i.5] ETSI TS 102 940: "Intelligent Transport Systems (ITS); Security; ITS communications security architecture and security management; Release 2". [i.6] ETSI TS 103 141: "Intelligent Transport Systems (ITS); Facilities layer function; Multi-Channel Operation (MCO) for Cooperative ITS (C-ITS); Release 2".
|
225cf9c9633d392f7d3beb5ed1519d85
|
104 072
|
3 Definition of terms, symbols and abbreviations
| |
225cf9c9633d392f7d3beb5ed1519d85
|
104 072
|
3.1 Terms
|
For the purposes of the present document, the following terms apply: parking space: physical space where it can be reasonably expected that parking and/or stopping is possible for a defined set of vehicle types
|
225cf9c9633d392f7d3beb5ed1519d85
|
104 072
|
3.2 Symbols
|
For the purposes of the present document, the following symbols apply: IF.Control Interface required by the PI service to management plane entity(ies) IF.Security Interface required by the PI service to security plane entity(ies) IF.DataCollect Interface provided by the PI service for making collected PIMs available IF.DataOut Interface required by the PI service to disseminate PIM IF.DataIn Interface required by the PI service to gather PIMs and other service data
|
225cf9c9633d392f7d3beb5ed1519d85
|
104 072
|
3.3 Abbreviations
|
For the purposes of the present document, the following abbreviations apply: API Application Programming Interface ASN.1 Abstract Syntax Notation One DDP Device Data Provider DE Data Element DF Data Frame FoV Field of View GNSS Global Navigation Satellite System ITS Intelligent Transport Systems ITS-S Intelligent Transport Systems Station LDM Local Dynamic Map MCI MCO Control Information MCO Multi Channel Operation MIB Management Information Base MTU Maximum Transmission Unit PCI Protocol Control Information PI Parking Information PIM Parking Information Message PI service Parking Information service POTI Position and Time management SA Service Announcement UPER Unaligned Packed Encoding Rule V-ITS-S Vehicular ITS Station VEI V2X Exchanged Information ETSI ETSI TS 104 072 V2.1.1 (2025-07) 9
|
225cf9c9633d392f7d3beb5ed1519d85
|
104 072
|
4 PI service contextual introduction
| |
225cf9c9633d392f7d3beb5ed1519d85
|
104 072
|
4.1 Background
|
Vehicular mobility is a key element in our current society. Due to the large number of cars and trucks, the parking of these vehicles became an increasing challenge. In urban areas, especially in historical districts, the available space on streets is limited. Allocating parking spaces on the narrow streets further limits the available space. As a result, the number of parking spaces are limited in typical urban environments, while the demand for parking is persistent. The high number of one-way streets, the limited number of opportunities to turn around and the low number of available spaces result that many drivers need to spend additional time to circle around its destination while trying to find an empty parking space. A similar situation occurs in the case of large open-air parking facilities. In these parking lots there are usually a low number of entrance points to the nearby facility. For example, in the case of airports, the shuttle bus only has a limited number of stops. A train station or a mall has only a small number of entrances. Thus, finding a space near the subject point of interest is sometimes cumbersome, since most of the users of the parking facility try to get a space near the entrance area in order to limit the distance to be walked. As a result, drivers need to either walk more if they have decided to take a remote parking space or they need to make multiple circles in order to find a space close to the destination. Any of these cases makes finding a parking space frustrating, time-consuming and unpredictable.
|
225cf9c9633d392f7d3beb5ed1519d85
|
104 072
|
4.2 Application specification
|
To address the challenges listed in the clause 4.1, the present document suggests the following application. Each vehicle implementing this service collaborates with each other by sharing their detected parking spaces and optionally the parking space they intend to occupy as well. The vehicles are equipped with the necessary sensors to detect empty parking spaces and with the necessary communication units that help to share this information. Vehicles may also incorporate additional data, like the location of the available (but not necessarily empty) parking spaces that increase the overall performance of the application. Then, vehicles exchange the parking space information so that with this information they can all implement a function that helps the driver to find a parking space near his/her destination. To avoid race conditions, where multiple drivers are about to occupy the same space, the service implements a method to indicate the parking space someone is about to occupy. With this approach, other vehicles can avoid attempting to park to a location that is at the moment empty but will be occupied by the time the vehicle arrives at the parking space. The present document describes how to implement the messaging, as well as how to select the parking spaces subject to dissemination, how to prioritize them and how to handle cases when not all spaces can be sent. The details can be found in the following clauses. In the next subclauses, some key technical challenges and their resolution were listed.
|
225cf9c9633d392f7d3beb5ed1519d85
|
104 072
|
4.3 Sharing parking information
|
Today's vehicles are equipped with numerous sensors, including GNSS, cameras, radars and ultrasonic sensors. Using sensors of the vehicles it became possible to detect empty parking spaces. For example, a vehicle can use its ultrasonic sensors on its side to detect an empty location. The detected parking spaces can then easily be localized via combining the absolute position of the vehicle (calculated by the GNSS) and the relative position of the parking space to the vehicle. However, restricted parking spaces, garage entrances and similar open spaces may pose challenges to the detector systems. Luckily, the location information of the parking spaces is more or less static. This means that static preloaded data can be used on a vehicle to validate the detected empty parking space. Using this method the number of false positive detections can be reduced. For example, a garage entrance may look like an empty space from the ultrasonic sensor's perspective, but it can be filtered out using the available parking space data. On top of the pure detection the sensors can gather additional features of the parking space such as size and charging availability. ETSI ETSI TS 104 072 V2.1.1 (2025-07) 10
|
225cf9c9633d392f7d3beb5ed1519d85
|
104 072
|
4.4 Competition for the same parking space
|
In case only empty parking space information is distributed; vehicles will tend to compete for the same parking spaces typically located near the entrance of a facility. This would result that in many cases vehicles will not be able to park at the desired location because by the time the vehicle arrives at the parking space, it will be already occupied by a different vehicle. In order to mitigate this issue, vehicles can share their intended location so that other vehicles can aim for a different unoccupied space.
|
225cf9c9633d392f7d3beb5ed1519d85
|
104 072
|
4.5 Managed facilities with PAS
|
In some cases, the infrastructure is capable of detecting empty parking spaces and share this information with the drivers. For example, some sensors built under the concrete pavement can detect if a car parked above it, or an ultrasonic sensor mounted to the ceiling can detect if a vehicle parked beneath it. This information can be shared with the vehicles by other means then the PI service as well, for example, using the Parking Availability Service [i.1]. In case the vehicle enters a managed facility where the free parking space information is available; the PI service may adapt its behaviour and only reports the found misalignments so that the parking lot operator can detect sensory errors on its own side.
|
225cf9c9633d392f7d3beb5ed1519d85
|
104 072
|
4.6 Scalability
|
In order to improve scalability, in case a certain location has many empty parking spaces, the PI service will not send individual empty space information. Instead, it will distribute general emptiness information (e.g. via the segment-based approach).
|
225cf9c9633d392f7d3beb5ed1519d85
|
104 072
|
4.7 Service triggering options
|
On the V-ITS-S side, PI service may activate the generation of PIMs in case the vehicle reaches a speed where the sensor detection is available and road conditions allow the parking space detection (for example, the vehicle drives in the rightmost lane).
|
225cf9c9633d392f7d3beb5ed1519d85
|
104 072
|
5 PI service functional description
| |
225cf9c9633d392f7d3beb5ed1519d85
|
104 072
|
5.1 PI service in the ITS communication architecture
|
The PI service is a facility layer entity of the ITS-S architecture as defined in ETSI TS 103 898 [i.2]. It may interface with other entities of the facilities layer and with the ITS-S application layer to collect relevant information to generate the necessary messages to implement the service and to forward the consumed message content for further processing. The PI service within the ITS-S architecture and the logical interfaces to other layers and potentially to entities within the facility layer are presented in Figure 1. ETSI ETSI TS 104 072 V2.1.1 (2025-07) 11 Figure 1: PIS within the ITS-S communication architecture In a vehicle ITS-S the entities for the collection of data may be the Device Data Provider (DDP) and the Position and Time management (PoTi) and for the consumed data the Local Dynamic Map (LDM). The DDP may be connected to the vehicle network and provides the vehicle status information and parking detection information. The PoTi provides the position of the ITS-S and time information. The LDM as outlined in ETSI TS 103 938 [i.3] is a database in the ITS-S, which may be updated with the consumed data. ITS-S applications may retrieve information from the LDM for further processing. The PI service may also interface with the Service Announcement (SA) Service [i.4] to indicate the ITS-S's ability to generate PIMs and to provide details about the communication technology used. The PI service may also interface with resource management entities (specified in ETSI TS 103 141 [i.6]). The PI service interfaces through the IF.N&T with the networking & transport layer for exchanging of messages with other ITS-Ss, the IF.Security with the Security entity to access security services for message transmission and, the IF.Control with the Management entity and the IF.DataCollect with the application layer if consumed data are provided directly to the applications. The functionalities of the PI service are defined in clause 5.2, and the interfaces in clause 5.3.
|
225cf9c9633d392f7d3beb5ed1519d85
|
104 072
|
5.2 PI service functional architecture
|
Figure 2: Functional block diagram of the PI service For sending and receiving PIMs, the PI service shall provide the following sub-functions, as depicted in Figure 2: • Encode PIM: - This sub-function constructs the PIM according to the format specified in Annex A. • Decode PIM: - This sub-function decodes the consumed PIMs. ETSI ETSI TS 104 072 V2.1.1 (2025-07) 12 • PIM dissemination management: - This sub-function implements the protocol operation of the originating ITS-S, as specified in clause 6.1, including in particular: Activating and terminating the PIM dissemination operation. Determining the PIM generation frequency. Triggering the generation of PIM. Collecting and assembling the data for a PIM. • PIM collection management: - This sub-function implements the protocol operation of the receiving ITS-S, including in particular: Triggering the "decode PIM" function upon the reception of a PIM. Providing the consumed PIM data to LDM and/or ITS-S applications of the receiving ITS-S. Optionally, checking the information of consumed PIMs. • PIM Database: - This sub-function implements the protocol operation of storing and updating an internal list of parking spaces, including in particular: Storing the parking spaces (both locally perceived and received ones). Determining if two parking space detection from different sources are identical. Updating the parking space list based on the most recent information from one or multiple sources. The interfaces to other entities and layers are defined in clause 5.3. NOTE 1: The PIM Database has in some sense a similar functionality as the LDM. However, LDM typically handles messages, whereas the PIM database handles individual parking spaces. NOTE 2: The PI service may use additional data sources, e.g. static maps or other communication services to improve the overall application performance. However, that information is normally not exchanged as part of the PI service.
|
225cf9c9633d392f7d3beb5ed1519d85
|
104 072
|
5.3 Interfaces of the PI service
| |
225cf9c9633d392f7d3beb5ed1519d85
|
104 072
|
5.3.1 Interface to ITS-S applications
|
An ITS-S application is an application layer entity that implements the logic for cooperative parking space sharing use cases. An informative list of design requirements is provided in Annex E. For the provision of consumed data the PI service provides the interface IF.DataCollect to LDM or to ITS-S application layer, as illustrated in Figure 2. NOTE: The interface to the ITS-S application layer may be implemented as an API and data are exchanged between the PI service and ITS-S applications via this API.
|
225cf9c9633d392f7d3beb5ed1519d85
|
104 072
|
5.3.2 Interface to management plane entities
|
The PI service may exchange primitives within the entity(ies) in the ITS management plan via the interface IF.Control as depicted in Figure 1. Such primitive may include e.g. configuration parameters used by the service. NOTE: The specifications of the interface between the PI service and the management entity is out of scope of the present document. ETSI ETSI TS 104 072 V2.1.1 (2025-07) 13
|
225cf9c9633d392f7d3beb5ed1519d85
|
104 072
|
5.3.3 Interface to security plane entities
|
The PI service may exchange primitives with the security entity of the ITS-S via the IF.Security interface as depicted in Figure 1 using the IF.Security interface provided by the security entity as depicted in Figure 2. NOTE 1: Specifications of the interface between the PI service and the security entity is out of scope of the present document. In case the facility layer security is used, for ITS stations that use the trust model according to ETSI TS 102 940 [i.5] and ITS certificates according to ETSI TS 103 097 [2] and that are of type [Itss_WithPrivacy] as defined in ETSI TS 102 940 [i.5], the PI service shall interact with the ID management functionality of the Security entity to set the actual value of the ITS-S ID in the ITS PDU Header of the PIM. When the Security entity is triggering an Authorization Ticket change, the PI service shall change the value of the ITS-ID in the component ItsPduHeader.stationId accordingly and shall not send PIMs with the previous ID anymore. The PIM shall also stop sending any detections that already existed in the PIM database by the time of the pseudonym change. NOTE 2: Due to priority mechanisms implemented at lower layers, the sending ITS-S may apply reordering of the messages contained in its buffer. Queued messages which are identified with the old ITS-ID are discarded as soon as a message with the new ITS-ID is sent. Implementers should be aware that whether or not messages previously queued prior to an ID change event get transmitted or not is implementation dependent. NOTE 3: ITS stations of type [Itss_NoPrivacy] as defined in ETSI TS 102 940 [i.5] and ITS stations that do not use the trust model according to ETSI TS 102 940 [i.5] and ITS certificates according to ETSI TS 103 097 [2] do not need to implement functionality that changes ITS-S IDs (pseudonyms). To avoid similarities between successive PIMs, all detected parking spaces shall be reported as newly detected ones in the PIM following a pseudonym change.
|
225cf9c9633d392f7d3beb5ed1519d85
|
104 072
|
5.3.4 Interface DataIn, DataOut and DataCollect
|
The PI service shall pass the PIM for dissemination via the IF.DataOut to either another facilities layer entity such as Resource Management or a lower layer functionality such as the Networking & Transport layer as specified in Table 1. The PI service shall gather PIM via the IF.DataIn from either another facility layer entity such as Resource Management or a lower layer functionality such as the Networking & Transport layer as specified in Table 1. Table 1: PIM exchanged over Interfaces In and Out Category Data Data requirement Mandatory/Optional Data passed from the PI service to the ITS networking & transport layer PIM {pim} as specified in Annex A Mandatory SCI Security Control Information: ITS-AID and SSP that shall be listed in the Authorization Ticket that is associated to the private key that signs the message at the Networking & Transport layer. Optional, present only if ETSI ITS security ETSI TS 103 097 [2] at the network layer is used. PCI Protocol Control Information, depending on the protocol stack applied in the networking and transport layer. Optional Data passed from the ITS networking & transport layer to the PI service Received PIM {pim} as specified in Annex A Mandatory SCI Security Control Information: ITS-AID and SSP that are listed in the Authorization Ticket attached to the message, and the result of the security check at Networking & Transport layer. Optional, present only if ETSI ITS security ETSI TS 103 097 [2] at the network layer is used. The PI service may request data from the PoTi service using the IF.DataIn. NOTE 1: The specifications of the interface between the PI service and the PoTi service is out of scope of the present document. The PI service may request data from the DDP using the IF.DataIn. ETSI ETSI TS 104 072 V2.1.1 (2025-07) 14 NOTE 2: The specifications of the interface between the PI service and the DDP is out of scope of the present document. The PI service may provide PIMs to the LDM using the IF.DataCollect. NOTE 3: The specifications of the interface between the PI service and the LDM is out of scope of the present document.
|
225cf9c9633d392f7d3beb5ed1519d85
|
104 072
|
6 PIM dissemination requirements
| |
225cf9c9633d392f7d3beb5ed1519d85
|
104 072
|
6.1 PIM dissemination concepts
| |
225cf9c9633d392f7d3beb5ed1519d85
|
104 072
|
6.1.1 PI service activation and termination
| |
225cf9c9633d392f7d3beb5ed1519d85
|
104 072
|
6.1.1.1 Overview
|
The PI service supports multiple means for service activation and termination. The exact method applied for activation and termination shall be configured via the ActivationTerminationMethod configuration parameter (a default configuration set is provided in Annex F). The value of the configuration parameter refers to the respective subclause below. As long as the PI service is active, the PIM generation shall be triggered and managed by the PI service. NOTE: The detection functionality has a separate lifecycle from the service itself (represented via the DDP in Figure 2). This means that even if the service is activated, the vehicle may not add any new parking spaces, e.g. due to driving with too high speeds.
|
225cf9c9633d392f7d3beb5ed1519d85
|
104 072
|
6.1.1.2 Simple PI service activation and termination
|
If ActivationTerminationMethod is set to 1, then this activation and termination method shall be used. For vehicle ITS-S, if enabled by configuration, the PI service shall be activated upon the ITS-S activation. NOTE: SA messages may help finding the ITS stations with enabled PI service.
|
225cf9c9633d392f7d3beb5ed1519d85
|
104 072
|
6.1.1.3 Request-based PI service activation and termination
|
If ActivationTerminationMethod is set to 2, then the activation and termination method detailed in this clause shall be used. The ITS-S operating the PI service shall advertise the PI service (via e.g. the SA service (ETSI EN 302 890-1 [i.4])). The advertising message shall contain the channel where the PI service is available. NOTE 1: The usage of service advertisement does not necessarily imply that the PI service and the service advertisement are operating on separate channels. The advertising message shall contain an application-specific data field which shall be filled with the UPER-encoded PimAdvertiseApplicationData data structure defined in Annex A. NOTE 2: If SA service (ETSI EN 302 890-1 [i.4]) is used, then the application-specific data corresponds to the SAMapplicationData service info extension in the chOptions.extensions field in the related ServiceInfo entry. An application layer entity may indicate its need to find a parking space (via IF.DataIn). The ITS-S implementing the PI service may receive a request for parking space information from other remote ITS-Ss. The request for parking space is indicated via an advertisement message containing the PI service info where the request field of the PimAdvertiseApplicationData embedded into the SAMapplicationData data element is set to true. The PI service shall be active if there is an active request from an application layer entity to find a parking space or if at least one request for parking space has arrived in the last ActivationTerminationMethod2RequestTimeout. In any other cases the PI service shall be in terminated state. ETSI ETSI TS 104 072 V2.1.1 (2025-07) 15 If the PI service is requested by an application layer entity to find a parking space, then it shall set the request field of the PimAdvertiseApplicationData embedded into the application-specific advertisement data element to true in its advertisement service messages. In any other cases the request value shall be set to false. The advertisement service operation details, such as the repetition rate are out of the scope of the present document.
|
225cf9c9633d392f7d3beb5ed1519d85
|
104 072
|
6.1.2 PIM generation management
| |
225cf9c9633d392f7d3beb5ed1519d85
|
104 072
|
6.1.2.1 PIM generation rules for vehicle ITS-S
|
The PI service disseminates the PIMs in generation cycles. During a PIM generation cycle, zero, one or more messages are generated and sent out by the PI service. Each PIM in a generation cycle contains different parking space information. The union of the messages in a generation cycle contain all parking spaces subject for dissemination. The method for selection of parking spaces for dissemination is detailed below. Figure 3: PIM generation state diagram Regarding the PIM generation, the following constraints shall apply: • Minimum time elapsed between two consecutive PIMs ≥ T_GenPimIntervalMin. • Duration of a PIM generation cycle ≤ T_GenPimCycleMax. • Duration of a PIM generation cycle ≥ T_GenPimCycleMin. Generation cycle preparation phase Query T_GenPimRm Select and prioritize parking spaces for dissemination Calculate NumberOfGeneratedMessages Calculate EffectiveCycleDuration and EffectiveMessageIntervalDuration Message transmission phase Generate next message Wait until EffectiveCycleDuration has passed from the beginning First and intention available? Add intention and respective parking space Y N Wait EffectiveMessageIntervalDuration Last message or no more spaces available? Y N Add parking spaces in decreasing priority fitting into MTU ETSI ETSI TS 104 072 V2.1.1 (2025-07) 16 • _ ≤ _ . • _ ≤ _ . Within these limits the duration of the PIM generation cycle and the effective duration of the PIM generation cycle and the interval between two consecutive PIMs during the cycle is calculated the following way: 1) The PI service queries the T_GenPimRm from resource management. T_GenPimRm shall be set in a way that _ ≤ _ and _ ≤ _ . If T_GenPimRm is outside of these limits, then T_GenPimRm shall be updated with the respective limit. T_GenPimRm shall determine the minimum duration between two consecutive PIM generations in order to reduce the PIM generation according to the channel usage requirements of the resource management, if implemented. This facilitates the adjustment of the PIM generation rate to the remaining capacity of the radio channel in case of channel congestion. 2) The PI service selects the parking spaces subject of dissemination. The selection algorithm is specified by the configuration parameter ParkingSpaceSelectionAlgorithm. The configured selection algorithm shall be used for the selection of parking spaces detailed in Annex G. The selection algorithm may run before each message is generated. The PI service prioritizes the selected parking spaces. The prioritization algorithm is specified by the configuration parameter ParkingSpacePrioritizationAlgorithm. The configured prioritization algorithm shall be used for prioritizing the parking spaces detailed in Annex H. If any new detection is obtained during the generation cycle, it shall be also prioritized and added to the selected parking spaces list subject for dissemination. Minimum requirements, such as size, detection probability, plausibility checks, are out of scope of the present document and are to be added to the profile document. 3) The PI service determines the maximum number of packets that can be sent during the message generation cycle. The maximum number of messages to be sent is calculated the following way: = _ _ The number of messages required to send all selected parking spaces shall be estimated respecting the MTU on the specific channel (NumberOfRequiredMessages). The number of generated messages shall be calculated using the following formula. If possible within the constraints defined above, one additional message is allocated to disseminate new messages consumed during the current PIM generation cycle: = ! + 1 NOTE 1: A communication profile may set up limitation for the length of each generated parking space detection in order to optimize the operation of the service. NOTE 2: The association of the parking spaces to the messages is equivalent to the bin packing problem, which is an NP-complete optimization problem. The present document does not require the parking space - message association to be optimal. 4) The effective cycle time shall be calculated using the following formula: " = max _ _ _ ∗ NOTE 3: As a consequence of Step 3 and 4, _ ≥ " always applies. The effective message interval duration is calculated using the following formula. " = " ETSI ETSI TS 104 072 V2.1.1 (2025-07) 17 5) If there are any generated messages, then the first generated message shall be sent out immediately. Each other messages shall be sent out subsequentially with a wait duration of EffectiveMessageIntervalDuration. The messages shall be assembled the following way: a) If the PI service maintains an active intent for the ITS-S, then it shall be put it to the first PIM in the generation cycle. The parking space intended to be occupied shall also be included in the first PIM. If the intended space is not stored in the individual parking space format, then a new individual detection shall be generated and added to the subjectParkingSpace optional field of the intent indication. b) Then, parking spaces shall be attempted to be added, respecting the MTU of the current channel in decreasing priority order. Before adding a particular parking space to the message, the selection criteria for that parking space shall be reevaluated and the space shall only be added if the selection algorithm still selects it for dissemination. 6) The next generation event shall start after EffectiveCycleDuration measured from the current generation event. NOTE 4: In the worst case for scheduling, the same information is repeated each 2 ∗ _ , if the parking space is still considered to be selected. NOTE 5: In some cases, lower priority messages will be sorted out and not be sent, especially if _ is low, the channel congestion is high, and there are many detected parking spaces.
|
225cf9c9633d392f7d3beb5ed1519d85
|
104 072
|
6.2 PIM dissemination constraints
| |
225cf9c9633d392f7d3beb5ed1519d85
|
104 072
|
6.2.1 Security constraints
| |
225cf9c9633d392f7d3beb5ed1519d85
|
104 072
|
6.2.1.1 Introduction
|
Clause 6.2.1 is applicable to ITS stations that use the trust model according to ETSI TS 102 940 [i.5] and ITS certificates according to ETSI TS 103 097 [2]. NOTE: For other scenarios, the trust model and the mechanisms for trust enforcement for inter-connected ITS stations can be agreed among participating actors. The security mechanisms for ITS consider the authentication of messages transferred between ITS-Ss with certificates. A certificate indicates its holder's permissions to send a certain set of messages and optional privileges for specific data elements within these messages. The format for the certificates is specified in ETSI TS 103 097 [2]. Within the certificate, the permissions and privileges are indicated by an identifier (the ITS-AID) and optional attributes of a given AID, allowing for definition of different levels of permissions/rights (the SSP). The ITS-Application Identifier (ITS-AID) as given in ETSI TS 102 965 [5] indicates the overall type of permissions being granted. For example, there is an ITS-AID indicating that the sender is entitled to send PIMs. The Service Specific Permissions (SSP) is a field that indicates specific sets of permissions within the overall permissions indicated by the ITS-AID: for example, there may be an SSP value associated with the ITS-AID for PIM that indicates that the sender is entitled to send PIMs for a specific role. The following security objectives and required security services are identified: • For establishing PIM secure communications, the Message Signature service as specified in ETSI TS 103 097 [2] shall be supported by ITS-S sending/receiving PIM. • A PIM shall be accepted by a receiving ITS-S if it is consistent with the ITS-AID and SSP of the signing certificate (authorization ticket). • Signed message shall use the ITS-AID as specified in ETSI TS 102 965 [5]. ETSI ETSI TS 104 072 V2.1.1 (2025-07) 18
|
225cf9c9633d392f7d3beb5ed1519d85
|
104 072
|
6.2.1.2 Service Specific Permissions (SSP)
|
PIMs shall be signed using private keys associated to Authorization Tickets that contain SSPs of type BitmapSsp as specified in ETSI TS 103 097 [2]. The SSP for the PIM shall be of CHOICE BitmapSsp. It is defined by a variable number of octets and shall correspond to the octet scheme illustrated in Figure 4. This octet scheme allows the SSP format to accommodate current and future versions of the present document. 0 0 1 2 3 4 5 6 7 Octet 0 Figure 4: Format for SSP Octet Scheme (BitMapSsp) The SSP has a maximum length as specified in ETSI TS 103 097 [2]. The first octet shall reflect the version of the SSP (see Table 2). In the current version of the present document, the SSP field contains only the SSP version byte. Table 2: Octet Scheme for PIM SSPs Octet # Description Value 0 SSP version control 1 At reception of a message, the ITS-S shall check whether the message content is consistent with the ITS-AID and SSP contained in the Authorization Ticket in its signature. If the consistency check fails, the message shall be discarded.
|
225cf9c9633d392f7d3beb5ed1519d85
|
104 072
|
6.2.2 General priority constraints
|
If the GeoNetworking/BTP stack is used, the priority constraint shall be as given by the Traffic Class as specified in ETSI TS 103 836-4-1 [1]. 7 Format Specification General Structure of a PIM PDU
|
225cf9c9633d392f7d3beb5ed1519d85
|
104 072
|
7.1 PIM structure
| |
225cf9c9633d392f7d3beb5ed1519d85
|
104 072
|
7.1.1 General structure of a PIM
|
A PIM is a PDU composed of one common ITS PDU header, a management container, a detections container and two intent indication containers (arrival and departure). The general structure of a PIM is illustrated in Figure 5. ETSI ETSI TS 104 072 V2.1.1 (2025-07) 19 Figure 5: General Structure of PIM The header is a common header for facility layer PDUs. The pisParameters represent the payload in the PI service PDU. It includes the managementContainer, the detections and the arrivalIndication and departureIndication containers.
|
225cf9c9633d392f7d3beb5ed1519d85
|
104 072
|
7.1.2 The management container
|
The managementContainer component holds the message segmentation information. The PI service may distribute the information selected for transmission to multiple packets. The total and number of these packets and the ordinal number of the actual packet are present in the segmentation information component.
|
225cf9c9633d392f7d3beb5ed1519d85
|
104 072
|
7.1.3 The detections
|
The detections component contains information about detected parking spaces. There are multiple possible ways of describing detected parking spaces. The possible representation options of the detections are detailed in Annex C. PIMs with zero total number of detected parking spaces are allowed if an intent is shared in the message.
|
225cf9c9633d392f7d3beb5ed1519d85
|
104 072
|
7.1.4 The arrival indication
|
The arrivalIndication component points to a parking space that the sender vehicle intends to occupy in the future. The spaceId and the reporter fields identify the parking space described in the detections component of a particular PIM. The intent indication may also include information regarding the estimated arrival time of the sender vehicle (estimatedCompletionTime field).
|
225cf9c9633d392f7d3beb5ed1519d85
|
104 072
|
7.1.5 The departure indication
|
The departureIndication component points to a parking space that the sender vehicle intends to leave in the future. The spaceId and the reporter fields identify the parking space described in the detections component of a particular PIM. The intent indication may also include information regarding the estimated departure time of the sender vehicle (estimatedCompletionTime field). header pisParameters managementContainer detections intentIndication … individualParkingSpaces segmentsOfParkingSpaces … IndividualParkingSpace [0..31] ParkingSpaceSegment [0..31] ETSI ETSI TS 104 072 V2.1.1 (2025-07) 20
|
225cf9c9633d392f7d3beb5ed1519d85
|
104 072
|
7.2 PIM format specification
|
The PIM format shall be as specified in ASN.1 in Annex A of the present document. DEs and DFs that are not defined in the present document shall be imported from the common data dictionary ETSI TS 102 894-2 [3] as specified in Annex A. Detailed descriptions of all components of PIM are in Annex B of the present document. Unaligned Packed Encoding Rules (UPER) as defined in Recommendation ITU-T X.691 [4] shall be used for PIM encoding and decoding. ETSI ETSI TS 104 072 V2.1.1 (2025-07) 21 Annex A (normative): Link to the ASN.1 specification This clause provides the normative ASN.1 modules containing the syntactical definitions of the PIM PDU, its containers, and the data frames, and data elements defined in the present document. The semantical specification of the PIM components, its containers, the data frames, and data elements is contained in the same module, in the form of ASN.1 comments. For readability, the same semantical specification is presented in a different format in Annex B. The PIM-PDU-Descriptions module is identified by the Object Identifier {itu-t (0) identified-organization (4) etsi (0) itsDomain (5) wg1 (1) pisPduRelease2 (104072) pim (1) major-version-2 (2) minor-version-1(1)}. The module can be downloaded as a file as indicated in Table A.1. The associated SHA-256 cryptographic hash digest of the referenced file offers a means to verify the integrity of that file. Table A.1: PIM-PDU-Descriptions ASN.1 module information Module Name PIM-PDU-Descriptions OID {itu-t (0) identified-organization (4) etsi (0) itsDomain (5) wg1 (1) pisPduRelease2 (104072) pim (1) major-version-2 (2) minor-version-1 (1)} Link https://forge.etsi.org/rep/ITS/asn1/cp_ts104072/-/raw/v2.1.1/asn/PIM-PDU-Descriptions.asn SHA-256 hash 88fad57f0e956d3999ecd446f69c1084d9f67b3d897bbaa3a969fc69cb63fd19 The PIM-SA-Application-Data-Descriptions module is identified by the Object Identifier {itu-t (0) identified- organization (4) etsi (0) itsDomain (5) wg1 (1) pisPduRelease2 (104072) saApplicationData (2) major-version-2 (2) minor-version-1 (1)}. The module can be downloaded as a file as indicated in Table A.2. The associated SHA-256 cryptographic hash digest of the referenced file offers a means to verify the integrity of that file. Table A.2: PIM-SA-Application-Data-Descriptions ASN.1 module information Module Name PIM-SA-Application-Data-Descriptions OID {itu-t (0) identified-organization (4) etsi (0) itsDomain (5) wg1 (1) pisPduRelease2 (104072) saApplicationData (2) major-version-2 (2) minor-version-1 (1)} Link https://forge.etsi.org/rep/ITS/asn1/cp_ts104072/-/raw/v2.1.1/asn/PIM-SA-Application-Data- Descriptions.asn SHA-256 hash 15bcbdda4be0fc8aa7fdcd4d614bf1cffb12c963d80d67c15d83117a39d62af7 ETSI ETSI TS 104 072 V2.1.1 (2025-07) 22 Annex B (informative): Specification of PIM in readable format The present document provides the specification of PIM containers, data elements and data frames at the following URL: • https://forge.etsi.org/rep/ITS/asn1/cp_ts104072/-/tree/v2.1.1/docs ETSI ETSI TS 104 072 V2.1.1 (2025-07) 23 Annex C (informative): Diagrams About the Parking Space Location Description Figure C.1: Subsequent Parking Spaces On The Right Figure C.1 shows the description of subsequent parking spaces on the right. The Unknown section represents a location where data is not available. Occupied and free shows the beginning of an occupied or free section, respectively. Multiple spaces can be grouped this way. As depicted on the last Occupied point, the spaces may be grouped. Figure C.2: Determining the size of the parking space Figure C.2 shows how the receivers can decide if it fits to a parking space. In case of segment-based description (depicted by light green), the distance between the two segment markings shows the nominal width. The observed width is perpendicular to the direction of the parking space, and it measures the smallest width where the parking vehicle needs to fit. In case of parallel parking spaces, the observed length is the same as the segment size for a single empty space. In case of perpendicular parking spaces, the observed width is the same as the segment size for a single empty space. Unknown d=0 Occupied d=2m Free d=6m Occupied d=6m ETSI ETSI TS 104 072 V2.1.1 (2025-07) 24 Annex D (normative): Metrics definition for the parking space detection data structures D.1 Distance of detection to a certain point For the distance between a certain point and a parking space, the following metric shall be used: • The distance between the position described in the field "position" and the point shall be used for an IndividualParkingSpace. • The closest distance between the path and the point shall be used for a ParkingSpaceSegment. D.2 Time of detection For the time of detection, the following metric shall be used: • The endTime for an IndividualParkingSpace (described in the detectionMetaData field). • The endTime (described in the detectionMetaData field) plus the maximum of the sum of timeDeltas in spacesOnTheLeft and spacesOnTheRight for a ParkingSpaceSegment. This effectively defines time of the latest detection. ETSI ETSI TS 104 072 V2.1.1 (2025-07) 25 Annex E (informative): Assumed user needs In this informative annex, a list of assumed user needs is provided. These requirements are listing features that the service should support. The service should support the transmission and dissemination of information about a parking space detected by a sender vehicle. The service should support both centralized and decentralized operation. In the centralized operation mode, the parking facility or area is monitored by infrastructure sensors or other appropriate means, in a way that empty parking space information is recognized and shared with the vehicles implementing the service and vehicles only play a minor role as additional sensors (e.g. to correct false detections by the central system). In the decentralized operation individual vehicles should be able to implement the service without any infrastructure support. The vehicles should be able to detect empty parking spaces via e.g. sensors and share this information via their communication unit. The service should support special parking attributes, for example, electric vehicle charging spaces. The service should support sharing the intent of individual vehicles. Using this information, the service can implement an optimization algorithm, which allocates the ideal parking space for a certain vehicle. ITS-Ss can also request a parking space automatically or after a user input if no optimized allocation is active. In this case ITS-Ss can send out an intent and spaces are virtually allocated to them for a short period. The service should support the cancellation of its previously shared intent. The service should keep empty spaces broadcasting even if the originating ITS-S of the parking space information already left the proximity. As a result, the service should maintain a local distributed database, a.k.a a local dynamic map (empty space list). Therefore, the system should delete occupied or defective spaces after a certain amount of time, which can be configured on application layer. The broadcasting frequency should consider the information update events. The local distributed map (empty space list) should be updated in a way that: • Detections from the same spaces should be fused • The physical information should be fused with the regulatory information (if available) • Freshly allocated empty spaces should be marked as allocated • A timestamp should provide details about the age of the information • False Detections or state changes can be corrected by newer data • Vehicles can flag parking spaces or equipment as defective in case using the space or its features was not possible The local distributed map should be limited within a certain location, the list propagated by an ITS-S should not contain parking spaces further away than a certain distance. The service should support detection error reporting in order to indicate if the space was not free or it is an unavailable/invalid location. The service should have interfaces to the driver and/or to the ADAS to indicate the possible invalidity of a certain parking space. The service should support reinforcement of the detection of a certain empty parking space. The service should be aware of the number of other participants in the vicinity and may stay active even though the car has been switched off in case it is the only participating station to avoid a loss of information. ETSI ETSI TS 104 072 V2.1.1 (2025-07) 26 Annex F (informative): Default configuration set for the service Default parameters settings for PIM generation are specified in Table F.1. Table F.1: Default parameter settings for PIM generation Parameter Value T_GenPimIntervalMin 100 ms T_GenPimCycleMin 100 ms T_GenPimCycleMax 2 s MTU 1 200 Bytes ParkingSpaceSelectionAlgorithm 1 ParkingSpacePrioritizationAlgorithm 1 SelectionAlgorithm1RelevanceDistance 2 km SelectionAlgorithm1MaxDetectionAge 5 min ActivationTerminationMethod 1 ActivationTerminationMethod2RequestTimeout 30 s SegmentNewPathPointHeadingThreshold 10 deg SegmentNewPathPointLateralDistanceThreshold 2 m PriorizationAlgorithm2MaxDetectionAge 5 min ETSI ETSI TS 104 072 V2.1.1 (2025-07) 27 Annex G (normative): Parking space selection algorithm G.1 Simple parking space selection algorithm This parking space selection algorithm shall be used if the configuration parameter ParkingSpaceSelectionAlgorithm is set to 1. A parking space shall be selected by this algorithm if all of the following conditions apply: • The detected parking space is closer to the disseminating ITS-S than SelectionAlgorithm1RelevanceDistance. • The detection time of the parking space is not older than SelectionAlgorithm1MaxDetectionAge. • If the parking space was not detected by the disseminating ITS-S, and the disseminating ITS-S did not consume the same parking space detection from any other remote ITS-S since T_GenPimCycleMax. This condition shall run before each message is generated. NOTE: The operation of this algorithm implicitly requires the ITS-S to listen for and store parking spaces from other ITS-Ss. ETSI ETSI TS 104 072 V2.1.1 (2025-07) 28 Annex H (normative): Parking space prioritization algorithm H.1 Simple parking space prioritization algorithm This parking space prioritization algorithm shall be used if the configuration parameter ParkingSpacePrioritizationAlgorithm is set to 1. The parking space priority shall be determined based on the time of detection defined for the particular parking space in ascending order. The latest message shall have the highest priority. NOTE: This algorithm does not differentiate whether the parking space is a remote or a local one. H.2 Advanced parking space prioritization algorithm H.2.1 Overview This parking space prioritization algorithm shall be used if the configuration parameter ParkingSpacePrioritizationAlgorithm is set to 2. This parking space prioritization algorithm requires that the configuration parameters are selected in a way that always exactly one message shall be generated in each message generation cycle ( = 1), if there is at least 1 available parking space. H.2.2 General aspects The following procedure aims to use the available communication resources, optimizing the usefulness of the shared information for the receiving ITS-Ss. This shall be done by evaluating the metrics defined in the following subclauses. Some metrics compare the information available in the Local Environment Model (LEM) of the transmitting ITS-S to the information potential receiving ITS-Ss are assumed to already have. The knowledge already available to the potential receiving ITS-Ss is referred to as V2X Exchanged Information (VEI). The VEI shall be estimated as the union of information which the transmitting ITS-S received from other ITS-Ss and information shared by the transmitting ITS-Ss itself. After calculating the single priority metrics as defined in the following subclauses, the overall priority to disseminate the respective parking space shall be calculated as the mean value of the single values: # = $ # + % & + & + '(# ) 4 The calculation of priority coefficients are detailed below. H.2.3 Intermediate Step for Segment-based Parking Space Information In case the parking space information to be prioritized does not represent individual parking spaces but segments of parking spaces, the segments shall be cut into sub-segments in a way that each sub-segment is either completely free or completely occupied. Each individual sub-segment shall then be evaluated in the way described in this annex. After prioritization, neighbouring sub-segments selected for dissemination may be re-combined to larger segments. ETSI ETSI TS 104 072 V2.1.1 (2025-07) 29 H.2.4 Occupancy Deviation Priority To prioritize the dissemination of parking spaces with an occupancy status different to the status recorded in the VEI, the OccupancyDeviationPriority shall be calculated as: # = * # ( ≠ # ( : 1 : 0 . H.2.5 VEI Information Age Priority To prioritize the dissemination of parking spaces with a higher information age in the VEI, i.e. parking spaces that no update was transmitted about by any ITS-S for a longer period of time, the VeiInformationAgePriority shall be calculated as: % & = & & AoI shall be the time since the last update about the respective parking space was either transmitted by the ego ITS-S itself or received from any other ITS-S. MaxAoI shall be the maximum AoI calculated for any of the parking spaces currently evaluated for dissemination. H.2.6 Detection Age Priority To prioritize the dissemination of parking spaces which were detected more recently by the transmitting ITS-S, the DetectionAgePriority shall be calculated as: & = +1 − & & , 0 ≤ & ≤ & 0, & > & DetectionAge shall be the time since the parking space was last detected by the sensor system of the transmitting ITS-S. MaxDetectionAge shall be configured by the , & ℎ2 & configuration parameter. PriorizationAlgorithm2MaxDetectionAge shall be the maximum acceptable detection age before the information is considered outdated and shall be set as indicated in Annex F. NOTE: Usually , & ℎ2 & = ( & ℎ1 & applies. H.2.7 Free Space Priority To prioritize the transmission of free parking spaces over occupied parking spaces, the FreeSpacePriority shall be calculated as: '(# = #(# - # ) p(parking space free) shall be the probability, as indicated by the transmitting ITS-S's sensor system, that the respective parking spot is free. ETSI ETSI TS 104 072 V2.1.1 (2025-07) 30 History Document history V2.1.1 July 2025 Publication
|
f007f46b47c7aca93cf16c00c4eb9e20
|
103 029
|
1 Scope
|
The present document provides a set of interoperability use cases to be tested in order to validate an interconnection between IMS and EPC subsystems. For each use case there are conformance criteria and Test Descriptions (TD) detailed. The target of the present document is to provide the boiler-plate for verifing interoperability between the IMS and EPC subsystems based on the exemplary scenarios network attachment, IMS registration and IMS session management. Verifying basic protocol interoperability or NNI interoperability between two peer EPC systems is out of scope of the present document.
|
f007f46b47c7aca93cf16c00c4eb9e20
|
103 029
|
2 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. Referenced documents which are not found to be publicly available in the expected location might be found at http://docbox.etsi.org/Reference. NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee their long term validity.
|
f007f46b47c7aca93cf16c00c4eb9e20
|
103 029
|
2.1 Normative references
|
The following referenced documents are necessary for the application of the present document. [1] ETSI TS 123 228: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; IP Multimedia Subsystem (IMS); Stage 2 (3GPP TS 23.228 Release 10)". [2] ETSI TS 124 229: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3 (3GPP TS 24.229 Release 10)". [3] ETSI TS 123 401: "LTE; General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access (3GPP TS 23.401 Release 10)". [4] ETSI TS 123 402: "Universal Mobile Telecommunications System (UMTS); LTE; Architecture enhancements for non-3GPP accesses (3GPP TS 23.402 Release 10)". [5] ETSI TS 129 214: "Universal Mobile Telecommunications System (UMTS); LTE; Policy and charging control over Rx reference point (3GPP TS 29.214 Release 10)". [6] ETSI TS 129 212: "Universal Mobile Telecommunications System (UMTS); LTE; Policy and charging control over Gx reference point (3GPP TS 29.212 Release 10)". [7] ETSI TR 121 905: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Vocabulary for 3GPP Specifications (3GPP TR 21.905)".
|
f007f46b47c7aca93cf16c00c4eb9e20
|
103 029
|
2.2 Informative references
|
The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area. [i.1] IETF RFC 3588: "Diameter Base Protocol"; P. Calhoun et all, September 2003. ETSI ETSI TS 103 029 V3.1.1 (2011-11) 7 [i.2] ETSI TS 186 011-1 (V4.1.1): "IMS Network Testing (INT); IMS NNI Interoperability Test Specifications; Part 1: Test Purposes for IMS NNI Interoperability". [i.3] ETSI TS 186 011-2 (V4.1.1): "IMS Network Testing (INT); IMS NNI Interoperability Test Specifications; Part 2: Test Descriptions for IMS NNI Interoperability". [i.4] ETSI TS 123 008: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Organization of subscriber data (3GPP TS 23.008 Release 10)". [i.5] ETSI TS 123 203: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Policy and charging control architecture (3GPP TS 23.203 Release 10)". [i.1] 3GPP TS 23.203: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Policy and charging control architecture (Release 11)".
|
f007f46b47c7aca93cf16c00c4eb9e20
|
103 029
|
3 Definitions and abbreviations
| |
f007f46b47c7aca93cf16c00c4eb9e20
|
103 029
|
3.1 Definitions
|
For the purposes of the present document, the terms and definitions given in TS 123 203 [i.5], TS 124 229 [2], TS 123 401 [3], TS 123 402 [4], TS 129 214 [5] and the following apply: authorised QoS: the maximum QoS that is authorised for a service data flow. NOTE: In case of an aggregation of multiple service data flows within one IP-CAN bearer (e.g. for GPRS a PDP context), the combination of the "Authorised QoS" information of the individual service data flows is the "Authorised QoS" for the IP-CAN bearer. It contains the QoS class identifier and the data rate binding: the association between a service data flow and the IP-CAN bearer (for GPRS the PDP context) transporting that service data flow binding mechanism: the method for creating, modifying and deleting bindings default bearer: the EPS bearer which is first established for a new PDN connection and remains established throughout the lifetime of the PDN connection dynamic PCC Rule: PCC rule for which the definition is provided into the PCEF via the Gx reference point event report: notification, possibly containing additional information, of an event which occurs that corresponds with an event trigger. NOTE: Also, an event report is a report from the PCRF to the AF concerning transmission resources or requesting additional information event trigger: rule specifying the event reporting behaviour of a PCEF or BBERF. Also, a trigger for credit management events gating control: the process of blocking or allowing packets, belonging to a service data flow, to pass through to the desired endpoint initial registration: the registration procedure for a public user identity initiated by the UE in the absence of any valid registration IP-CAN bearer: IP transmission path of defined capacity, delay and bit error rate, etc. See TR 121 905 [7] for the definition of bearer ETSI ETSI TS 103 029 V3.1.1 (2011-11) 8 IP-CAN session: the association between a UE and an IP network. NOTE: The association is identified by one IPv4 and/or an IPv6 prefix together with UE identity information, if available, and a PDN represented by a PDN ID (e.g. an APN). An IP-CAN session incorporates one or more IP-CAN bearers. Support for multiple IP-CAN bearers per IP-CAN session is IP-CAN specific. An IP-CAN session exists as long as UE IP addresses/prefix are established and announced to the IP network PDN connection: the association between a UE represented by one IPv4 address and/or one IPv6 prefix and a PDN represented by an APN policy control: the process whereby the PCRF indicates to the PCEF how to control the IP-CAN bearer. Policy control includes QoS control and/or gating control QoS class identifier (QCI): scalar that is used as a reference to a specific packet forwarding behaviour (e.g. packet loss rate, packet delay budget) to be provided to a SDF. NOTE: This may be implemented in the access network by the QCI referencing node specific parameters that control packet forwarding treatment (e.g. scheduling weights, admission thresholds, queue management thresholds, link layer protocol configuration, etc.), that have been pre-configured by the operator at a specific node(s) (e.g. eNodeB) QoS rule: set of information enabling the detection of a service data flow and defining its associated QoS parameters resource reservation: mechanism for reserving bearer resources that is required for certain access technologies service information: set of information conveyed from the AF to the PCRF over the Rx interface to be used as a basis for PCC decisions at the PCRF, including information about the AF session (e.g. application identifier, type of media, bandwidth, IP address and port number)
|
f007f46b47c7aca93cf16c00c4eb9e20
|
103 029
|
3.2 Abbreviations
|
For the purposes of the present document, the abbreviations given in TS 124 229 [2], TS 123 401 [3], TS 123 402 [4], TS 123 203 [i.5] and the following apply: ACK Session Acknowledge Message Type AF Application Function ANDSF Access Network Discovery and Selection Function AN-GW Access Network Gateway APN Access Point Name AVP Attribute-Value Pair BBERF Bearer Binding and Event Reporting Function CS Circuit Switch CSCF Call Session Control Function DHCP Dynamic Host Configuration Protocol DNS Domain Name System DV Dragos Vingarzan EPC Evolved Packet Core ePDG Evolved Packet Data Gateway EPS Evolved Packet System FQDN Fully Qualified Domain Name GBR Guaranteed Bitrate GPRS General Packet Radio Service GTP GPRS Tunneling Protocol GW Gateway HSS Home Subscriber Server IMPI IP Multimedia Private Identity IMPU IP Multimedia Public Identity IMS IP Multimedia core network Subsystem IOP Interoperability IP Internet Protocol IP-CAN IP-Connectivity Access Network IPv4 Internet Protocol version 4 IPv6 Internet Protocol version 6 ETSI ETSI TS 103 029 V3.1.1 (2011-11) 9 ISIM IM Subscriber Identity Module IUT Interface Under Test MGW Media Gateway NGN Next Generation Network NNI Network to Network Interface OK/ACK Session Acknowledge Message Type PCC Policy and Charging Control PCEF Policy and Charging Enforcement Function PCRF Policy and Charging Rules Function P-CSCF Proxy CSCF PDN Packet Data Network PDP Packet Data Protocol P-GW PDN Gateway PMIP Proxy Mobile IP PO Point of Observation PO_UE Point of Observation on UE PSTN Pbulica Switch Telephone Network QCI QoS Class Identifier QoS Quality of Service RAN Radio Access Network RAT Radio Access Technology RTP Real Time Protocol S-CSCF Serving CSCF SDF Service Data Flow SDP Session Description Protocol SIP Session Initiation Protocol SPR Subscription Profile Repository SUT System - Under Test TD Test Description TLS Transport Layer Security TP Test Purpose UA User Agent UDR User Data Request UE User Equipment UE_A User Equipemnt A UE_B User Equipment B UNI User-Network Interface URI Uniform Resource Identifier USIM Universal Subscriber Identity UTRAN UMTS Terrestrial Radio Access Network ETSI ETSI TS 103 029 V3.1.1 (2011-11) 10 4 Overview of the EPC and IMS Architecture, in the scope of LTE/SAE The IP Multimedia Subsystem defined in TS 123 228 [1] and TS 124 229 [2] describes the control and service delivery architecture standardized by 3GPP. It was initially started in 3GPP Release 5 as an all-IP core network for providing IP services in the context of the mobile domain evolution. Over the subsequent releases, various other standardization bodies have adopted the same principles and core network architecture for providing IP services, each complementing with requirements and specifics for their respective access network type of interest. Starting with 3GPP Release 8 onwards, the efforts converged into the Common-IMS specifications. Mb SGi Mn Mg ISC Sh Gm SGi Mw Mw Mw Cx Cx Rx S14 Gxb Gxa Gxc Gx Sp Sp SWn SWn SWm STa S6b SWx S2c S2c S2b S5/S8 S6d S12 Iub Iub IuPS S4 S3 S6a S11 S10 E‐UTRAN (LTE) S1‐MME S1‐U eNodeB S1‐MME S1‐U X2 MME SGw Trusted Non‐3GPP Access ANGw ePDG SPR UTRAN (UMTS) SGSN RNC eNodeB NodeB NodeB Untrusted Non‐3GPP Access UE Uu LTE‐Uu WiMAX WiFi SWu S2a PGw 3GPP AAA Server PCRF ANDSF P‐CSCF I‐CSCF S‐CSCF HSS AS MGCF Softswitch PSTN MGW 3GPP Access Non‐3GPP Access EPS EPC UTRAN/E‐UTRAN IM S Untrusted Access Trusted Access Figure 1: The EPC and IMS Core Network Architectures ETSI ETSI TS 103 029 V3.1.1 (2011-11) 11 At its core, IMS comprises of a set of specialized Call Session Control Functions (CSCF), which route and process SIP signalling between the IMS User Endpoints (UE), the IMS Application Servers (AS) and a set of Media Gateways (MGW) interfacing with the Public Switched Telephony Network (PSTN). The subscriber data is stored in a central database, the Home Subscriber Server (HSS). The HSS as well as the additional Authentication, Authorization and Accounting services use for signalling the Diameter protocol. The main target of the IMS architecture is to provide service control for an extensible set of applications. It features an open-ended model, where a set of operations are defined as basic building blocks (e.g. authentication and registration, session set-up/tear-down, messaging, etc). These building blocks can later be re-used and re-combined by ASs in order to realize a future-proof Service Delivery Platform. This model is set to replace the currently obsolete silo-model approach for services of the legacy systems. As IMS was adopted for the non-mobile access, the underlying network and attachment architectures and procedures started to diverge such that various types of fixed network could be supported. This prompted a split between the strict IMS standardization and that of the underlying Access Network. The LTE path started an evolution of both the Radio Access Network (E-UTRAN) and its supporting GPRS Core Network architecture (Evolved Packet Core TS 123 401 [3], into a consolidated Evolved Packet System, as part of the System Architecture Evolution. Additionally to the 3GPP RAN, comes the All-IP Network as well as integration with less reliable yet more cost efficient Access Network solutions (non-3GPP Access TS 123 402 [4]). The main targets of the EPC architecture are to provide a flexible and efficient IP-connectivity layer, capable of handling Inter-System Handovers, Policy and Charging Control as well as security for transparent IP services. The approach is more generalized than with IMS which requires SIP signalling for services. EPC is capable of supporting not only an IMS architecture on top, but also has a potential for generic Over-The-Top services. The EPC and IMS architectures are not meant to compete or replace each-other. They are built as to complement each- other in an efficient manner, which abstracts services in the EPC as IP data flows, while providing transparent handling of both horizontal and vertical hand-over's without complex IMS signalling. The EPC architectural nodes can be grouped, based on functionality, as following: • Core Network Mobility - a 2-layer gateway model allowing vertical hand-over's; uses GTP for legacy and PMIP for non-3GPP access. • Policy and Charging Control - split into Policy and Charging rules functions (PCRF), enforcement functions (PCEF, part of the P-GW) and access network specific functions (BBERF). • Access Network Discovery and Selection Function - provides AN discovery and Inter-System Mobility policies directly to the mobile devices, helping in establishing the operator policies for AN selection and use. • Subscription Profiles Repository - accessible from the (E-)UTRAN, PCC and ANDSF components, such that network attachments are secured with authentication and authorization procedures, while also providing per- subscriber customized service levels. For EPC to support the IMS services requirements and for IMS to fully take advantage of the EPC provides IP connectivity, the inter-architecture interfacing is of critical importance. Unlike in the individual IMS or EPC cases, it is foreseen that in real life deployments the multi-vendor setups from different IMS and EPC providers will be much more common. The present standard aims at providing a set of test purposes and descriptions for testing the base inter-operability between the IMS and EPC systems, on the most common scenarios. ETSI ETSI TS 103 029 V3.1.1 (2011-11) 12
|
f007f46b47c7aca93cf16c00c4eb9e20
|
103 029
|
4.1 Scope of the IMS-EPC Interoperability
|
The interoperability in scope for testing here covers all the interactions on the border interfaces between the IMS and the EPC systems. It has to be noted that this is a bi-directional resource negotiation, event propagation and IP transport interaction point. EPC PCRF IMS P‐CSCF Rx PGw Gm UE‐B UE‐A SGi IMS‐EPC IOP Figure 2: IMS-EPC Interoperability in scope
|
f007f46b47c7aca93cf16c00c4eb9e20
|
103 029
|
4.1.1 Reference Points in Scope
|
The SGi interface transports the User-Plane data from the UEs towards IMS as well as other Application Functions. This a generic reference point, for the transport of the IP User Plane data belonging to different more specific reference points, like Gm for SIP signalling or Mb for RTP media. These transported reference points though are end-to-end, such that the EPC system tunnels the IP packets through GTP and PMIP specific procedures, while the IMS processes the data itself, whether it is signalling or media. The Rx interface uses the Diameter protocol [i.1] to push from IMS to EPC the communication bearer establishment requirements, as derived by the P-CSCF from the SIP and SDP signalling that passes through, for the scope of establishing well-ruled communication paths in the Evolved Packet Core and the UTRAN/E-UTRAN systems. The EPC Policy and Charging Control concepts encompass Gating, QoS and Charging Rules which constitute the operator's (per subscriber dynamic) policies. The Rx interface is also used as a feedback path for events and notifications pertaining to the status of the network attachments and communication bearers, to be delivered from the EPC system to the IMS one. ETSI ETSI TS 103 029 V3.1.1 (2011-11) 13
|
f007f46b47c7aca93cf16c00c4eb9e20
|
103 029
|
4.1.2 Out of Scope Inter-domain Interactions
|
In a realistic exploitation scenario, beside the architectural components and reference points presented in Figure 1, the multi-domain situation will have to be considered. As the aforementioned figure is quite complex and encompassing both architectures, these details have been previously omitted on purpose. The present document will limit itself, at least in this first version, to the interfaces between IMS and EPC, considered in the simplest scenarios, without NNI interactions. When considering the multi-domain situation, besides the IMS-EPC intra-domain interactions, IMS NNI is addressed in TS 186 011-1 [i.2] and TS 186 011-2 [i.3], although the respective specification abstracts from the Access Network situation. EPC A V‐PCRF IMS A P‐CSCF Rx PGw SGi SGi EPC B H‐PCRF IMS B S‐CSCF S9 I‐CSCF Mw V‐ANDSF H‐ANDSF UE‐B (roam) UE‐A UE‐B EPC NNI IOP here IMS NNI IOP here IMS‐EPC IOP here Figure 3: Complete IMS/EPC Interoperability (NNI out of scope) Considering the EPC NNI communication, this will need to be addressed in the future for a complete coverage, as depicted in Figure 3. The respective inter-working reference points are still early in their standardization to be significantly addressed in implementations, while also the functional parts of the EPC architecture has to be addressed first. For these reasons, in the present document these NNI interactions are out of scope and will not be addressed.
|
f007f46b47c7aca93cf16c00c4eb9e20
|
103 029
|
5 Test Prerequisites
| |
f007f46b47c7aca93cf16c00c4eb9e20
|
103 029
|
5.1 IP Version
|
Whether the EPC system uses IPv4 or IPv6 to transport (i.e. tunnelling method) the User Plane data inside the EPS is irrelevant to the outcome of the tests. Options for encapsulating either IPv4 or IPv6 packets into both IPv4 and IPv6 transported tunnels exist. There are no differences in the User Plane provided services by the EPC platform relevant to the used IP transport version, such that this decision can be taken by the EPC vendors as to maximize performance and optimize their platforms. The UE attachment to the EPS is assumed to be a dual IPv4 and IPv6. It is assumed that for the test purposes, the IMS client software will be capable of SIP signalling and media transport over both protocol version. The choice will be a configuration parameter (e.g. P-CSCF provisioned address in ISIM, DHCP or DNS). The SDP media should use the same IP version protocol as discovered for SIP signalling. ETSI ETSI TS 103 029 V3.1.1 (2011-11) 14 The IMS-EPC IOP Test Suite will be executed once for IMS clients using IPv4 and once for IMS clients using IPv6. After testing all the use cases, the IMS system should be re-configured and the execution repeated.
|
f007f46b47c7aca93cf16c00c4eb9e20
|
103 029
|
5.2 Protocols, Security and Points of Observation
|
The IMS-EPC IOP tests employ SIP and Diameter protocol signalling, as well as transparent media (e.g. RTP). Figure 4: Points of Observation for Test Protocols User Plane data as SIP and media is to be transported transparently between the UE and the P-CSCF, respectively MGW/correspondent-UE. The Point of Observation (PO) for SIP signalling be the Gm interface, which for observability reasons will not be secured. The PO for media happens at 2 points: • the SGi interface between the P-GW and a generic IP router, positioned between IMS and EPC; all traffic, including direct UE to UE traffic, will be redirected and proxied through this IP router; • the UE device's interface towards EPC. The Rx Diameter interface is to be observed and as such not secured with encryption between the IMS and EPC systems. Basic Diameter connectivity is a pre-requisite for the tests, such that the P-CSCF and PCRF nodes should be correctly configured to establish and maintain (Capabilities-Exchange, Diameter-Watchdogs) stateful connectivity, as well as both declaring support for the Rx interface, such that Diameter Rx messages will be successfully routed and processed.
|
f007f46b47c7aca93cf16c00c4eb9e20
|
103 029
|
5.3 Test Infrastructure
|
This clause covers the list of relevant components and interfaces used for testing interoperability between EPC and AF represented by IMS. For components that are not present, standard functionality is assumed.
|
f007f46b47c7aca93cf16c00c4eb9e20
|
103 029
|
5.3.1 HSS/SPR
|
Subscriber data (TS 123 008 [i.4]) such as profile, location and subscriptions are located for IMS in the central database Home Subscriber Server/Universal Profile Server Function (HSS/UPSF), while EPC uses as a central database the Subscription Profile Repository (SPR). The data between the HSS and SPR has to be correlated, such that service functionality and charging will happen in a unitary manner. ETSI ETSI TS 103 029 V3.1.1 (2011-11) 15 As no reference point is envisioned here for Release 10, the HSS/UPSF/SPR can be regarded as a common node, exposing different interfaces towards different domains. As for example the HSS exposes the Sh interface for IMS applications and the Cx interface of the IMS Call Session Control Functions, a HSS/UPSF/SPR component will additionally expose interfaces like Sp towards EPC or S6a/d towards E-UTRAN/UTRAN. In Release 11 (3GPP TS 23.203 [i.1]), a similar approach appears, with the introduction of an Universal Data Repository (UDR), which would constitute the common back-end between the HSS/UPSF/SPR/etc data retrieval components. This goes in the same direction as in our assumption for Release 10, of providing a common data back-end for all systems, with customized interfaces. For practical deployment reasons, we have to observe that the 2 systems, IMS and EPC, in many situations would not share a common subscriber database. When performing IOP tests between IMS and EPC from different vendors, the following situations are possible: a) two separate HSS entities, common data initially duplicated and later synchronized between them; b) single HSS, as part of the IMS system, which will export SPR type interfaces as Sp, S6a/d, SWx a.s.o. interfaces towards the EPC system; c) single SPR, as part of the EPC system, which will export HSS type interfaces as Cx and Sh towards the IMS system. To simplify the architecture and generalize the practical usability of the interoperability tests to be specified here, case a) will be the only one considered. Interoperability between and IMS and EPC on the HSS interfaces is out of scope and will not be analyzed here. This is also in line with the aforementioned Release 11 evolution, which introduces a common data back-end. The HSS and SPR entities will be provisioned for the test purposes with the required information for UE A and B, at both the EPS and IMS levels. 5.3.2 The P-CSCF (IMS) as the Application Function (AF) Interface to EPC In EPC terms, the Application Function (AF) is an abstraction of the service provider plane, which communicates with the PCRF to enable Policy and Charging Control of the application layer and IMS session level services. The AF may be a single third party service, a complex operator controlled service delivery platform or an IP Multimedia Subsystem. When the AF in the EPC architecture is represented by IMS, the inter-working function is provided by the P-CSCF. Based on the SIP signalling and the transported SDP payloads, the P-CSCF is able to derive QoS and charging requirements for the EPC system to provide. Also the P-CSCF will follow the status of the respectively provided communication bearers, such that it can act on events (e.g. loss of bearer, QoS changes, etc). For all these purposes the Rx reference point is used to communicate with the PCRF component in the EPC system. The P-CSCF acts also as the Session Border Controller for the SIP User-to-Network Interface, Gm. From the perspective of EPC, the SIP signalling is transparently delivered between the UE and the P-CSCF. From the IMS perspective, the P-CSCF employs ciphering and integrity protection procedures, in order to further route and process the SIP signalling.
|
f007f46b47c7aca93cf16c00c4eb9e20
|
103 029
|
5.3.3 PCRF (EPC)
|
The Policy and Charging Control (PCC) is ensured through the Policy Decision Point, namely the Policy Charging and Rules Function (PCRF) and several Policy Enforcement Points located in the EPC gateways (TS 123 203 [i.5]). The PCRF interfaces with the AF (P-CSCF in our IMS case) over the Rx reference point. The service requests are processed through a policy engine designed to allow for operator based control of gating, QoS and charging. The decisions are also taking as input the profiles of the respective subscribers, such that the provided policies are subscriber dynamically customized. The resulting policies are pushed to be enforced towards the P-GW for gating and charging control, as well as towards the access specific gateway (S-GW, AN-GW, ePDG) for gating and QoS on the radio links. These resulting policies, as well as feedback from the charging and RAN systems, are passed back upstream over the Rx reference point to the AF (P-CSCF component in the case of IMS). ETSI ETSI TS 103 029 V3.1.1 (2011-11) 16
|
f007f46b47c7aca93cf16c00c4eb9e20
|
103 029
|
5.3.4 P-GW (EPC)
|
The Packet Data Network (PDN) Gateway provides transparent IP connectivity between the AF over multiple gateways and a radio link to the UE. The P-GW acts as IPv6 mobility anchor between trusted and un-trusted 3GPP and non-3GPP technologies and performs packet filtering, charging as well as IP address allocation.
|
f007f46b47c7aca93cf16c00c4eb9e20
|
103 029
|
5.3.5 User Endpoints
|
The test infrastructure must contain also User Endpoints. These are represented by client devices or simulators, capable of performing the EPC and IMS procedures. The Use Cases and Test Descriptions have been developed such that during execution, only one client dev ice has to be observed. The counterpart UE in calls for example can be places either as a full EPC and IMS client, or only as IMS client, or even as a stand-alone SIP UA. In all cases the main requirement is that IP and SIP traffic would be observable for test validation. For this purpose, the Test Description refer to PO_SGi interface.
|
f007f46b47c7aca93cf16c00c4eb9e20
|
103 029
|
5.4 Reference Points and Protocols
| |
f007f46b47c7aca93cf16c00c4eb9e20
|
103 029
|
5.4.1 The SGi reference point (IP)
|
The SGi reference point, performs User-Plane generic IP interfacing, breaking out the user IP data from the EPC plane towards the Application Functions (IMS, Internet, etc). Towards the UTRAN/E-UTRAN or non-3GPP access, this data is transported always as tunnelled and not merely routed on IP principles, such that the SGi correspondent node is provided with direct IP connectivity to the UE device. The SIP signalling as well as the IMS media are transported over this interface. Packet data network may be an operator-external public or private packet data network or an intra-operator packet data network, e.g. for provision of IMS services. This reference point corresponds to Gi for GERAN/UTRAN accesses.
|
f007f46b47c7aca93cf16c00c4eb9e20
|
103 029
|
5.4.1.1 The Gm reference point (SIP)
|
The Gm reference point represents the 1st hop in SIP signalling between the UE and the IMS network represented by the P-CSCF. Its scope is to provide a secure SIP signalling channel, independent of the access network level security. As such, with the exception of initial security negotiations, all signalling should be regarded as un-interceptable. However, for the interoperability purposes here in scope, intercepting this interface is critical for verifying the correct test scenario functionality, without requiring proprietary signalling tapping alternatives. Security measures as 3GPP- IPsec or TLS will be disabled on the Gm interface during the interoperability testing. Nevertheless, security is still to be regarded as mandatory when testing IMS UNI interoperability.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.