hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
e20bfd5f2facbd115bc6c2064c7898e3 | 122 034 | 4.10.4 End-to-end delay | .............................................................................................................................................. 11 |
e20bfd5f2facbd115bc6c2064c7898e3 | 122 034 | 4.10.5 Throughput | ...................................................................................................................................................... 11 |
e20bfd5f2facbd115bc6c2064c7898e3 | 122 034 | 4.10.6 Network planning and interference levels | ....................................................................................................... 11 4.11 Mapping of FNUR to GERAN TCH/F for T services ..................................................................................... 11 4.12 Mapping of GERAN AIUR to GERAN TCH/F for NT services .................. |
e20bfd5f2facbd115bc6c2064c7898e3 | 122 034 | 4.13 GBS MMI aspects | ............................................................................................................................................ 12 |
e20bfd5f2facbd115bc6c2064c7898e3 | 122 034 | 4.14 GBS Subscription aspects | ................................................................................................................................ 12 |
e20bfd5f2facbd115bc6c2064c7898e3 | 122 034 | 4.15 GBS charging aspects | ...................................................................................................................................... 12 |
e20bfd5f2facbd115bc6c2064c7898e3 | 122 034 | 4.16 O and M aspects | ............................................................................................................................................... 12 |
e20bfd5f2facbd115bc6c2064c7898e3 | 122 034 | 4.17 Multislot security aspects | ................................................................................................................................. 12 |
e20bfd5f2facbd115bc6c2064c7898e3 | 122 034 | 5 Exceptional procedures or unsuccessful outcome | .................................................................................13 |
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... |
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 ....................................................................................... |
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........... |
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... |
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 th... |
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... |
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 computat... |
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... |
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 a... |
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 i... |
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... |
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 Trans... |
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 lim... |
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 nec... |
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 the... |
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 ... |
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 info... |
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 consum... |
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 consume... |
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, ... |
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 o... |
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 sco... |
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 lay... |
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 ... |
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 a... |
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 subje... |
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... |
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... |
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... |
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... |
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 ... |
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 departu... |
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 documen... |
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 inte... |
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 a... |
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: "Di... |
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): ... |
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 flow... |
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 ... |
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 Fi... |
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... |
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 prese... |
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 servic... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.