hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 7.4.7.5 Bearer control | In all types of call, the CCAS will assign appropriate bearers (unicast and/or multicast) to carry the media and media related signalling within the call as part of the call setup process. The process is outside the scope of the present document. Note that the CCAS may have a little more time available when acknowledge... |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 7.4.8 Conversion of an ongoing group call into an emergency group call | If the CCAS receives an emergency-level call request from a call participant during an ongoing open session group call, the CCAS may decide to provide discrete call sessions and emergency priority only to the talking party and specific nominated parties who may be required to acknowledge. These selected users may need ... |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 7.5 Push-to-talk management procedures | |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 7.5.0 General | The infrastructure controls the management of the transmission rights and implements PTT management procedures as detailed in the following clauses. NOTE: The following clauses apply both to individual and group streaming communications. |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 7.5.1 Initial allocation of right to transmit | The initial allocation of the right to transmit is defined by default behaviour according to the type of communication. However this behaviour may be overridden by the CCAS if it needs to modify the service. In a half-duplex call by default, the called party of an individual call with on/off hook signalling should be g... |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 7.5.2 Releasing the right to transmit | When a MU which has been granted transmission wants to release the floor, it shall send an indication of this release (MCP U-TX Ceased) and immediately stop the transmission of any media traffic, including buffered media whenever possible. ETSI ETSI TS 103 269-2 V1.2.1 (2017-06) 68 The CCAS should inform all MUs involv... |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 7.5.3 Requesting the right to transmit | The right to request the right to transmit may be denied to all MUs at call setup time for broadcast calls. Otherwise, a MU in the call hang time, or in a receiving state of a streaming communication may at any time request the right to transmit (MCP U-TX demand) and shall indicate a priority level for the processing o... |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 7.5.4 Interrupting a granted transmission | If an MU requests transmit permission whilst receiving media sourced from another user, but the priority level does not lead to an immediate allocation (pre-emption) and when the currently granted party has not released the floor, the request may be rejected or queued and the requesting party shall be notified of the s... |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 7.5.5 Suspending a transmission | The CCAS may decide to temporarily suspend the call by removing transmit permission from the talking party using the "MCP D-TX Interrupt" message without granting transmission rights to another user. This may be adopted if some critical resource or user (e.g. a dispatcher) becomes unavailable, or if the talking party i... |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 7.5.6 End of call | Following the last transmission, after the end of an appropriate timer, the call will be ended. The call may also be ended by the CCAS if the overall call time exceeds maximum permitted group call duration (see clause 9.4.3) or the CCAS's maximum permitted individual call or emergency call duration (see clause 9.6.2). ... |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 7.6 Call modification | A call may be modified at setup or whilst it is continuing. Call modifications include: • Half-duplex to full-duplex and vice versa (individual calls only). • Direct to hook signalling and vice versa (individual calls only). • Group to individual (e.g. call diversion when out of area). • Change in the priority of the c... |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 7.7 Management of priority and pre-emption | |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 7.7.0 General | The management of priority and pre-emption covers several aspects listed below. There are at least 8 possible priority levels for each type of priority. |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 7.7.1 Provisioned priority | Individual MUs and groups may each be provisioned with a relative priority level. The CCAS uses this provisioned priority to decide which calls to grant first and which calls to queue in the event of resource limitations. It may also be used to decide whether to pre-empt a user or a group when another user wishes to pl... |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 7.7.2 Setup priority | Each call set up request may include a priority value which can be determined either by the user or the application in the MU. This shall distinguish between at least: • Normal calls. • Broadcast calls (should have a higher priority than normal calls). • Urgent calls. • Imminent peril calls. • Emergency calls. Addition... |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 7.7.3 Push-to-talk priority | Each request for transmission using MCP includes a priority indication (with the same possibilities as the call setup priority). An authorized user may request the CCAS to change another user's priority for requesting permission to transmit. An imminent peril transmission request shall convert a non-emergency call into... |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 7.7.4 Scanning priority | A MU may receive several calls simultaneously and shall be able to select the calls to be presented to the user application based on a predefined set of priorities. The affiliation messages will include a parameter which indicates the relative priority of a group (the class of usage) to the CCAS. An authorized user may... |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 7.7.5 Resource allocation priority and resource retention | When queuing for resources, several queues may be organized for the different priorities and resources will be allocated based on relative priorities. However, a call with a non pre-emptive priority shall not lead to tear down of resources already allocated to another ongoing call. Pre-emptive communication shall be ab... |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 7.7.6 Priority attributes requests | The CCA user may send the CCAS an HTTP request (see IETF RFC 7230 [22]) for information about the attributes being used by the control server to determine the priority of the user's call requests and transmissions. The CCAS may then send the user an HTTP response listing the user's priorities relevant to call requests ... |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 7.8 Status and messaging | |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 7.8.0 Supported status and messaging types | The CCAS shall support both pre-defined status transmission and free format messaging. Both functions shall use the SIP MESSAGE facility [5], which will include an application dependent message body header within the message to identify status, pre-defined messages and free format messages, as well as other application... |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 7.8.1 Standard defined status | |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 7.8.1.0 Pre-defined status | Some statuses have a predefined meaning and a mandatory processing as defined in the following clauses. Further definitions are possible. |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 7.8.1.1 Emergency status | The emergency status is sent to the CCAS by a MU upon action of the user to signal an emergency condition or upon action of the user to request emergency PTT priority. The emergency status is then sent by the CCAS to a pre- programmed set or group of MUs which usually includes one or several wire-line connected units f... |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 7.8.1.2 Call alert | The call alert (or call back or request to speak) function allows the indication of a willingness to be called back at a later time without the need of trying a call which may fail. The call alerting message is routed to the "alerted" party and contains the address of the altering party in order to allow a simple call-... |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 7.8.1.3 Urgent call back | The urgent call back status provides the same facility as the call alert status, i.e. a desire to enter into a communication, but with an increased degree of urgency. The urgent call back status message shall indicate the level of urgency ("urgent" or "most urgent"). The alerted party shall record the time at which the... |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 7.8.1.4 Ambience listening call request | The ambience listening call request provides a similar function to the call alert request; except that the user desires the recipient (usually a dispatcher) to activate ambience listening on the user's terminal. The called party shall record the time at which the ambience listening call request was received. Both the c... |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 7.8.1.5 Ambience listening urgent call request | The ambience listening call request is similar to the ambience listening call request, but indicates an increase degree of urgency. The ambience listening urgent call request message shall indicate the level of urgency ("urgent" or "most urgent"). The alerted party shall record the time at which the request was receive... |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 7.8.1.6 Scanning on and off | Scanning on and off status values may be used to indicate to the CCAS whether the MU wishes to be presented with calls from its list of scanned groups or no. |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 7.8.1.7 Transmit inhibit on and off | A user may select a transmit inhibit mode which restricts the transmissions made by an MU. The status indicates the current state of this function. NOTE: It is for further study whether a transmit inhibit mode can prevent UE/terminal transmissions, or can only suppress CCA level messages. |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 7.8.1.8 Imminent peril status | The imminent peril status is sent by a MU upon action of the user to signal an imminent peril condition. The imminent peril status (including the identity of the initiator) is then sent to a pre-programmed set or group of MUs which usually includes one or several wire-line connected units for dispatchers. The sending u... |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 7.8.2 Messaging | |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 7.8.2.0 Message service | Messaging is a service that supports transfer of messages that are usually, but not required to be, short. Messages shall use either the 7-bit GSM default alphabet (see ETSI TS 100 900 [20]) or the UTF-8 character set (IETF RFC 3629 [21]). The messaging service is also known as the Short Data Service (SDS). The maximum... |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 7.8.2.1 Message broadcast | Messages may be sent to specific broadcast addresses, both defined organizationally and system wide. Broadcast messages may be intended for user consumption (i.e. may be human readable text), but also may be used for functions usable by the mobile application. When the CCAS receives a request for a message to be sent t... |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 7.9 Presence | Presence is a service that provides information about user availability (presence) to authorized users. A Mobile Unit may publish the Presence status of its user(s) to the CCAS. Presence status includes an availability status and may include other metadata such as e.g. the group(s) the mobile unit is monitoring or a sy... |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 7.10 Localization and geographic information | |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 7.10.0 General | The MU shall be able to provide its geographic location when it is able to discover it, for example when in an outdoor location. The user and device profiles may permit the user or another authorized user to enforce or prevent transmission of location information. The location information should be sent using encryptio... |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 7.10.1 Mode of transmission | The system shall support different modes of transmission of the geographic location information as listed below: • Spontaneous transmission mode: in this mode, the MU spontaneously transmits its location information to the infrastructure. The transmission may be one-shot, periodic with a programmable period or may be d... |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 7.10.2 Assisted location | The system shall support assisted location for improved accuracy. Assistance may be broadcast in a suitable manner, see clause 6.1.4.1. |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 7.11 Supplementary services | |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 7.11.0 Introduction | The supplementary services described in the following clauses complement the services described in the previous clauses. |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 7.11.1 Ambience Listening | Ambience Listening (AL) is a service available to authorized units (such as dispatchers) allowing them to silently trigger transmission of a mobile unit. This may be required when the actual user of the mobile unit has been in some way incapacitated to allow the dispatcher to listen at the environment to assess the sit... |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 7.11.2 Talking party and calling party identity | Talking party identity (PTT calls) and calling party identity (full-duplex/telephone calls) are transmitted for display by the receiving parties in a call at the beginning of a media transmission sequence. The identity may be the CCA individual identity of the user of the MU or an identifier of the connected telephone ... |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 7.11.3 Dynamic group number allocation and group merging | The dynamic group number allocation allows the dynamic provision of additional group identities to the MU. These identities may immediately be used for group communications when the allocation uses simultaneous affiliation or they may be kept inside the MU memory for later use under user control. In this later case, se... |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 7.11.4 Disabling and enabling | The MU application may be disabled and re-enabled under control of the infrastructure to manage stolen MU or rogue user cases. The disabling process shall be appropriately secured to avoid misuse of this feature. The MU application may be temporarily disabled or permanently disabled. A temporarily-disabled MU applicati... |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 7.11.5 Call forwarding | |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 7.11.5.0 Call redirection | Call forwarding (or call diversion) reroutes a call for a given MU to another one when some conditions are fulfilled. This service only applies to individual streaming calls. As the MU which is the target of the call redirection may itself be subject to call forwarding, a redirection counter is maintained during the re... |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 7.11.5.1 Call forwarding unconditional | The unconditional call forwarding service (CFU) redirects to another MU every individual call to a given MU. This may apply for all type of calls or only for some specific types. The other MU may be statically designated at the time of the definition of the forwarding or may belong to a list address, allowing the redir... |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 7.11.5.2 Call forwarding on busy subscriber and on no reply | The main use of this type of call forwarding is the implementation of voice messaging services. When the service is activated and when an individual call cannot be completed for one of the above reasons (the subscriber is already involved in a call and not willing to respond or the subscriber does not reply, including ... |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 7.11.6 Call barring | |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 7.11.6.0 Introduction | The call barring supplementary service triggers the failure of calls when some conditions are met. |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 7.11.6.1 Barring of outgoing calls | An authorized user may prohibit a MU from setting up calls (individual and/or group) to defined set of recipients. This barring of outgoing calls triggers the failure of any call attempt by the barred MU to the barred individual or group recipients. The code for failure shall unambiguously indicate the cause of the fai... |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 7.11.6.2 Barring of incoming calls | An authorized user may prohibit a MU from receiving calls (individual and/or group) from a given source or a given set of sources. The calling party shall be notified the cause for failure of the call attempt. NOTE: In the same way as for outgoing calls, barring of incoming calls from an individual MU does not imply ba... |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 7.11.7 Call waiting and call hold | Call waiting and call hold enable simple management of the reception of several individual calls which are setup during the same period of time. The process follows normal SIP procedures; examples of such can be found in [i.7]. When a MU receives a call setup (i.e. receives a SIP INVITE) while being already involved in... |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 7.11.8 Discreet listening | The discreet listening service allows an authorized user to listen an individual or group call without any party of the call being notified of this intervention. The authorized user may release the call at any time. This function is a system level feature which does not impact MU protocol. |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 7.11.9 Call transfer | An MU receiving a call may perform a call transfer to another MU once the call has been setup. This step may be performed after a call diversion (or call forwarding unconditional) in order to implement a simple call authorized by dispatcher feature. The process follows normal SIP procedures; examples of such can be fou... |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 7.12 Principles for mobility management | |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 7.12.1 Roaming and Migration | As described in clause 7.2, two configurations have to be considered for roaming and registration, depending on whether a single CCAS or multiple CCASs are involved. If the transport network (e.g. LTE Core Network) allows direct access to the home CCAS of the user, then roaming is transparent to the user and to the app... |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 7.12.2 Media gateway re-allocation | A Critical Communication Application can comprise several media interfaces, in order to provide redundancy and/or load balancing and/or geographic zones. It can therefore be necessary or desirable to switch an MU from one media interface to another media interface, while staying attached to the same CCAS. The decision ... |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 8 Multiple User Instances | |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 8.1 User Instances | Clause 6.1.0 describes the CCA user identity and clause 6.1.1 defines CCA application identities. A user instance is a unique combination of a CCA individual identity, a user profile and a CCA client instance. As there is a one-to-one mapping of the CCA individual identity to a CCA user identity, multiple user instance... |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 8.2 List identifiers | List identifiers are used for the implementation of functions such as list addressing or list search call in existing narrowband systems. It allows a call to be directed to a set of individuals (for example dispatchers), without knowing which one will answer. The various individuals in the list are polled at call setup... |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 8.3 Use of multiple MUs | One user may be registered and authenticated via multiple MUs at any one time; i.e. the user can possess separate registered user instances on different MUs. For each user instance, the user shall authenticate to the CCAS independently through the relevant MU. The user may affiliate to different groups on the different... |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 8.4 Multiple users of one device | A single MU may support more than one user instance. The MU's CCA client creates a separate CCA client instance for each user instance. The MU's user instances may be for different users or for the same user. The MU obtains a unique GRUU for each of its CCA client instances during SIP registration (see clause 7.2.3.5).... |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 8.5 Participant types | The "participant type" is a functional category of a CCA user (e.g. first responder, second responder, dispatch, dispatch supervisor). The CCA user's permitted participant types are typically defined by a CCA administrator authorized to control CCA service parameters and user profiles, etc. (see clause 9). A CCA user p... |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 9 Profiles and Service Parameters | |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 9.1 General | The CCAS shall maintain user profiles, supplementary configurations, device profiles, group profiles and CCAS service parameters. Each MU shall store and maintain a copy of its device profile, copies of the user profiles of its current users, copies of the group profiles of its affiliated groups (see clause 7.2.3.8) an... |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 9.2 User Profiles | The CCAS shall maintain a user profile for each CCA user. In addition, the CCAS shall maintain a default user profile that defines the services available to unauthenticated users. A user profile can be an individual user profile or a functional user profile. Functional user profiles contain one of more CCA functional i... |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 9.3 Supplementary Configuration | Supplementary configuration may be provided to a visiting user to add group memberships relevant to the visited CCAS. A URI for the supplementary information is sent automatically by the visited CCAS in SIP NOTIFY message so that the supplementary information can be downloaded using HTTP. The supplementary information ... |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 9.4 Group Profiles | |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 9.4.1 General | The CCAS shall maintain a profile for each defined group. |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 9.4.2 Group profile items provided to group members | The following items in the group profile may be provided to group members: • CCA group identity; • the group's home CCA server identity; ETSI ETSI TS 103 269-2 V1.2.1 (2017-06) 90 • name of group's CCA organization; • group profile version number; • default displayable name of group (defined by either the 7-bit GSM def... |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 9.4.3 Group profile items not normally provided to group members | The following items in the group profile are not included in the group profile provided to group members: • maximum permitted group call duration; • maximum permitted imminent-peril group call duration; • maximum permitted emergency group call duration; NOTE 1: The remaining call duration may be provided to MUs in the ... |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 9.5 Device Profiles | |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 9.5.1 General | The CCAS shall maintain a profile for each device. ETSI ETSI TS 103 269-2 V1.2.1 (2017-06) 92 |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 9.5.2 Device profile items provided to the MU | The following items in the CCAS's copy of the device profile may be sent to the MU: • maximum number of simultaneous transmissions device is permitted to receive in the event of override in a single group call; • maximum permitted number of simultaneous individual calls per device; • set of services available prior to ... |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 9.5.3 Device profile items not normally provided to the MU | The following items in the CCAS's copy of the device profile are not normally included in the device profile sent to the MU: • CCA client identity; • CCA client status: - enabled; - temporarily disabled; - permanently disabled; • maximum supported number of simultaneous CCA client instances; • device class (supported o... |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 9.6 CCA Service parameters | |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 9.6.1 Service parameters provided to the MU | Services supported by the CCAS: • Voice: - individual half-duplex calls; - individual full-duplex calls; - group calls; • Messaging (SDS); • Video. The following CCA service parameters may affect the operation of MUs: • the maximum time for which an MU is permitted to transmit in a half-duplex call; • time remaining wh... |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 9.6.2 Service Parameters not provided to the MU | The following service parameters are stored by the CCAS but are not normally sent to the MU: • maximum permitted individual call duration; • maximum permitted emergency individual call duration; NOTE 1: Where a call transits between CCASs, the shortest of the relevant timers applies. ETSI ETSI TS 103 269-2 V1.2.1 (2017... |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 9.7 MU configuration data | Before it can be used for the first time, the MU needs to be configured with essential information. This includes: • CCA client identity; • the MU's home CCA server identity; • for each CCAS that this MU is configured to use, a set of: - CCA server identity; - APN; - IP address or FQDN or URI of the CCAS's application ... |
43ae532e6551f735fab5f793f0b2091c | 103 300-2 | 1 Scope | The present document analyses the impact of use cases described in ETSI TR 103 300-1 [i.1] and specifies the VRU related requirements, as well as the functional architecture of the VRU system that will prevent collisions with other road users. In addition, it provides the impact of the specified requirements and functi... |
43ae532e6551f735fab5f793f0b2091c | 103 300-2 | 2 References | |
43ae532e6551f735fab5f793f0b2091c | 103 300-2 | 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... |
43ae532e6551f735fab5f793f0b2091c | 103 300-2 | 2.2 Informative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. NOTE: While any hyperlinks i... |
43ae532e6551f735fab5f793f0b2091c | 103 300-2 | 3 Definition of terms, symbols and abbreviations | |
43ae532e6551f735fab5f793f0b2091c | 103 300-2 | 3.1 Terms | For the purposes of the present document, the terms given in ETSI TS 103 898 [i.12], ETSI TS 102 731 [i.23], ETSI TR 103 300-1 [i.1] and the following apply: actor: participant in a use case attestation: process by which a device proves to another party that it is in a known valid state authorization authority: securit... |
43ae532e6551f735fab5f793f0b2091c | 103 300-2 | 3.2 Symbols | Void. |
43ae532e6551f735fab5f793f0b2091c | 103 300-2 | 3.3 Abbreviations | For the purposes of the present document, the abbreviations given in ETSI TS 103 898 [i.12] and the following apply: AA Authorization Authority ADAS Advanced Driver-Assistance Systems AI Artificial Intelligence AT Authorization Ticket CA Cooperative Awareness CAM Cooperative Awareness Message C-ITS Cooperative ITS C-IT... |
43ae532e6551f735fab5f793f0b2091c | 103 300-2 | 4 General overview and use case analysis | |
43ae532e6551f735fab5f793f0b2091c | 103 300-2 | 4.1 Introduction | The present document specifies the requirements and the architecture of the VRU system and ITS Station (ITS-S), based on the results and analysis performed on exemplary use cases in ETSI TR 103 300-1 [i.1]. It describes the different functions involved in the identified architecture as well as their interfaces. Finally... |
43ae532e6551f735fab5f793f0b2091c | 103 300-2 | 4.2 Abstracted flow from use cases | The use cases in ETSI TR 103 300-1 [i.1] have shown the following steps (compiled as an abstraction of the use cases), with different alternatives. These steps were also highlighted by the VRUITS project [i.2]: 1) Detection of the VRU presence. The alternatives are: - VRU self-positioning. The VRU has sensors and poten... |
43ae532e6551f735fab5f793f0b2091c | 103 300-2 | 4.4 VRU system physical architecture | The physical architecture shall be as shown in Figure 1 (derived from VRUITS deliverable [i.2]). It consists of three main components: • VRUs, including VRU clusters and combined VRUs . The VRU ITS-S may be a personal ITS-S (P-ITS-S) or a vehicular ITS-S (V-ITS-S) depending on the type of road user. • Non-VRU Vehicles ... |
43ae532e6551f735fab5f793f0b2091c | 103 300-2 | 4.5 Security analysis of VRU use cases | |
43ae532e6551f735fab5f793f0b2091c | 103 300-2 | 4.5.0 Introduction | This clause presents the security analysis of the VRU use cases considered in ETSI TR 103 300-1 [i.1]. This security analysis considers each "entity activity" (i.e. each information flow with a particular goal) in the use cases. Each entity activity is rated as low, medium or high sensitivity with respect to the three ... |
43ae532e6551f735fab5f793f0b2091c | 103 300-2 | 4.5.1 UC-A1: Sharing sidewalk between pedestrian and cyclists | Table 3: Risk analysis: UC-A1: Sharing sidewalk between pedestrian and cyclists Use case: Sharing sidewalk between pedestrian and cyclists Actors: Pedestrian VRU, Cyclist VRU Information flow Entity activities Description Impact IA1-1 Exchange messages EA1-1.1 VRU → VRU Broadcast of dynamic and other information about ... |
43ae532e6551f735fab5f793f0b2091c | 103 300-2 | 4.5.2 UC-A2: Pedestrian crossing a road with an e-scooter approaching | Table 4: Risk analysis: UC-A2: Pedestrian crossing a road with an e-scooter approaching Use case: Pedestrian crossing a road with an e-scooter approaching Actors: Pedestrian VRU, Cyclist VRU Information flow Entity activities Description Impact IA2-1 Exchange messages EA2-1.1 E-Scooter → Pedestrian Broadcast of dynamic... |
43ae532e6551f735fab5f793f0b2091c | 103 300-2 | 4.5.3 UC-B1: Active roadwork | Table 5: Risk analysis: UC-B1: Active roadwork Use case: Active roadwork Actors: Active worker (pedestrian) VRU, Local Vehicle, Remote Vehicle Information flow Entity activities Description Impact IB1-1 Exchange messages EB1-1.1 Local Vehicle → Active Worker Broadcast of dynamic and other information about local vehicl... |
43ae532e6551f735fab5f793f0b2091c | 103 300-2 | 4.5.4 UC-B2: VRU crossing a road | Table 6: Risk analysis: UC-B2: VRU crossing a road Use case: VRU crossing a road Actors: VRU, Vehicle Information flow Entity activities Description Impact IB2-1 Exchange messages EB2-1.1 VRU → Vehicle Broadcast of dynamic and other information about VRU C: None - broadcast model. I: Low - Impact of false messages is f... |
43ae532e6551f735fab5f793f0b2091c | 103 300-2 | 4.5.5 UC-B3: Rider is separated from his motorcycle | Table 7: Risk analysis: UC-B3: Rider is separated from his motorcycle Use case: Rider separated from motorcycle Actors: Rider VRU-St, motorcycle VRU-St, Approaching Vehicle Information flow Entity activities Description Impact IB3-1 Exchange messages EB3-1.1 Rider VRU-St → Motorcycle VRU-St: communications to establish... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.