hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.20.3.4 Void | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.20.3.5 Void | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.21 Automatic Train Protection data communication | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.21.1 Introduction | In this chapter the use cases related Automatic Train Protection (ATP) data communication are described, the following use cases are identified:
• Initiation of an Automatic Train Protection data communication
• Termination of an Automatic Train Protection data communication
• Service interworking with GSM-R |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.21.2 Description | Automatic Train Protection (ATP) is the application which performs some or all the functions that ensures the safe movement of a train. ATP supervises the train ensuring that speed and movement limits are kept and the train proceeds only when it is allowed to do so.
Some ATP systems require radio communication to inter... |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.21.3 Use case: Initiation of an Automatic Train Protection data communication | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.21.3.1 Description | The FRMCS Application is able to initiate data communication for communication having continuous characteristics between the on-board applications and ground system and/or the on-board applications of other trains. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.21.3.2 Pre-conditions | The FRMCS User at the train and at the FRMCS User at ground are authorised to initiate the Automatic Train Protection data communication.
The receiving application is authorised to use the Automatic Train Protection data communication. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.21.3.3 Service flows | The FRMCS User (i.e. on-board of the train or the control center at the track side) initiates the Automatic Train Protection data communication (i.e. control center at the trackside or on-board the train).
For the operation of ATP, a non-delay tolerant bearer service is required that corresponds to application category... |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.21.3.4 Post-conditions | ATP related data can be exchanged between the Automatic Train Protection communication entities. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.21.3.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-6.21.3-001]
Upon request of an authorised FRMCS User, the FRMCS System shall be able to provide a non-delay tolerant data bearer for ATP data communication that matches to the application category of CRITICAL DATA/ VERY CRITICAL DAT... |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.21.4 Use case: Termination of an Automatic Train Protection data communication | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.21.4.1 Description | The FRMCS User is able to terminate data communication. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.21.4.2 Pre-conditions | The Automatic Train Protection related data communication is ongoing. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.21.4.3 Service flows | The FRMCS User (i.e. on-board of the train or the control centre at the track side) terminates the Automatic Train Protection data communication.
The FRMCS System terminates the bearer service required for ATP related data communication. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.21.4.4 Post-conditions | The Automatic Train Protection data communication has been released. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.21.4.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-6.21.4-001]
The FRMCS User shall be able to terminate the Automatic Train Protection data communication. The FRMCS System shall terminate the bearer service.
A
TS 22.280
TS 22.280 Requirements [R-6.4.9-001] on termination conditions... |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.22 Voice communication transfer related use cases | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.22.1 Introduction | In this chapter the use cases related to the transfer of incoming or ongoing voice communication are defined. The following use cases are defined:
- Transfer of an incoming voice communication
- Transfer of an ongoing voice communication
- Service interworking and service continuation with GSM-R
To provide some backgro... |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.22.2 Use case: Transfer of an incoming voice communication | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.22.2.1 Description | When FRMCS User receives a notification of an incoming voice communication, and the FRMCS Equipment does not automatically accept the communication, the FRMCS User, if authorised, shall be able to transfer the communication to another FRMCS User. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.22.2.2 Pre-conditions | FRMCS User is registered to a single or multiple FRMCS Equipment.
FRMCS User is or is not part of an ongoing communication. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.22.2.3 Service flows | The FRMCS System provides and activates a mechanism to transfer communications.
FRMCS User is authorised to use the mechanism to transfer communications.
When the notification of an incoming voice communication is received by the FRMCS equipment, a notification is presented to appropriate FRMCS User allowing the transf... |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.22.2.4 Post-conditions | The incoming voice communication is transferred to the new FRMCS User by the FRMCS System. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.22.2.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-6.22.2-001]
The FRMCS System shall enable FRMCS User to transfer incoming voice communications based on different criteria
A/T
22.179
Limited to private calls because group communication already provides other meachnisms
[R-5.6.3-01... |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.22.3 Use case: Transfer of an ongoing voice communication | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.22.3.1 Description | When FRMCS User is part of an ongoing voice communication, FRMCS User, if authorised, shall be able to transfer the communication to another FRMCS User. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.22.3.2 Pre-conditions | FRMCS User is registered to a single or multiple FRMCS Equipment.
FRMCS User is part of an ongoing voice communication.
The FRMCS System provides and activates a mechanism to transfer communications.
FRMCS User is authorised to use the mechanism to transfer communications. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.22.3.3 Service flows | Whilst in an ongoing voice communication, the FRMCS Equipment provides an option to the FRMCS User allowing the transfer of the current communication to another FRMCS User.
FRMCS User selects the new FRMCS User out of a list (e.g. telephone book) or entered manually based on either FRMCS User Identity, FRMCS Functional... |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.22.3.4 Post-conditions | The ongoing voice communication is transferred to the new FRMCS User by the FRMCS System. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.22.3.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-6.22.3-001]
The FRMCS System shall enable FRMCS User to transfer ongoing voice communications.
A/T
22.179
Limited to private calls because group communication already provides other mechanisms
[R-5.6.3-014], [R-6.7.4-015] |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.22.4 Use case: Service interworking with GSM-R | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.22.4.1 Description | For coexistence between FRMCS System and the legacy GSM-R communication system, service interworking among the systems is required.
Transfer of incoming voice communication to a GSM-R User shall be provided by the FRMCS System.
Transfer of ongoing communication to a GSM-R User shall be provided by the FRMCS System.
Ser... |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.22.4.2 Pre-conditions | FRMCS User is attached to the FRMCS System.
GSM-R User is attached to GSM-R System.
The transfer procedure (either transfer of incoming voice communication or transfer of ongoing communication) has been initiated by the FRMCS User. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.22.4.3 Service flows | FRMCS User selects the new GSM-R User out of a list (e.g. telephone book) or entered manually based on the functional address of the GSM-R User or E.164 numbering plan. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.22.4.4 Post-conditions | The incoming voice communication or the ongoing voice communication is transferred to the new GSM-R User by the FRMCS System. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.22.4.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-6.22.4-001]
The FRMCS System shall allow FRMCS User to forward of incoming voice communications and transfer of ongoing communication to GSM-R User using the applicable the addressing scheme.
A/T
22.280
[R-5.19.2-006] |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.23 Virtual Coupling data communication | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.23.1 Introduction | In this chapter the use cases related to Virtual Coupling data communication are described, the following use cases are identified:
• Initiation of a Virtual Coupling data communication
• Termination of a Virtual Coupling data communication
• Service interworking with GSM-R |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.23.2 Description | In virtual coupling use case, multiple trains can synchronously move together as a platoon, where the distance between each train can be shorter than the absolute braking distance.
Virtual Coupling is the application which performs some or all the functions of, synchronous acceleration and braking, protection of indivi... |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.23.3 Use case: Initiation of a Virtual Coupling data communication | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.23.3.1 Description | The FRMCS user is able to initiate data communication for virtual coupling. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.23.3.2 Pre-conditions | The initiating FRMCS user is authorised to initiate the virtual coupling data communication from the trackside control centre.
The trackside control centre has requested the initiating FRMCS user to initiate the Virtual Coupling data communication. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.23.3.3 Service flows | The initiating FRMCS user in a train initiates the Virtual Coupling data communication to the receiving FRMCS user in the other train.
The FRMCS System establishes a data bearer services for Virtual Coupling data communication which matches to the application category of VERY CRITICAL DATA, the latency attributes of UL... |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.23.3.4 Post-conditions | The Virtual Coupling data communication is established.
Data can be exchanged between the FRMCS users. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.23.3.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-6.23.3-001]
The FRMCS System shall support Virtual Coupling data communication in Off-network, On-network and a combination of On-network/Off-network mode.
A
TS 22.282
On-network is covered by TS 22.282 subclause 5.5.
Off-network is... |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.23.4 Use case: Termination of a Virtual Coupling data communication | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.23.4.1 Description | The FRMCS user is able to terminate data communication for virtual coupling. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.23.4.2 Pre-conditions | The Virtual Coupling data communication is ongoing.
The trackside control centre has requested the terminating FRMCS user to terminate te the Virtual Coupling data communication. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.23.4.3 Service flows | The terminating FRMCS user in a train terminates the Virtual Coupling data communication with the receiving FRMCS user in the other train. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.23.4.4 Post-conditions | The Virtual Coupling data communication has been released. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.23.4.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-6.23.4-001]
The FRMCS System shall be able to terminate the Virtual Coupling data communication upon a request received from the functional identity that initiated the Virtual Coupling data communication.
A
TS 22.282
This requiremen... |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.23.5 Use case: Service interworking with GSM-R | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.23.5.1 Description | Service interworking of Virtual Coupling data communication with GSM-R is not required. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.24 Public train emergency communication | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.24.1 Introduction | In this chapter the following use cases related to Public train emergency communication are considered:
- Initiation of the Public train emergency alert
- New entry to the Public train emergency alert
- Changing of the Public train emergency alert
- Merging of Public train emergency alerts
- Leaving of the Public train... |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.24.2 General overview | The Public train emergency communication behaves as a Railway emergency communication, but with a limited/local impact (e.g. a platform of a level crossing). The communication can be initiated by railway staff but also by a member of the public using a dedicated FRMCS Equipment.
The Public train emergency alert serves ... |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.24.3 Use case on Initiation of the Public train emergency alert | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.24.3.1 Description | A FRMCS User is able to initiate the Public train emergency alert to users that are informed about the emergency situation, e.g. that fulfil the conditions of the emergency situation. The FRMCS User can be e.g. a member of the public, mobile user, a driver, an external system, a controller, maintenance staff or a membe... |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.24.3.2 Service flows | External FRMCS System initiated
This use case is similar to Railway emergency alert, except that this is applicable to Public train emergency alert. Please refer to corresponding Railway emergency alert section in the current document for relevant service flows.
Mobile FRMCS User initiated
This use case is similar to t... |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.24.3.3 Potential requirements and gap analysis | Potential requirements are similar to Railway emergency communication except the followings. Please refer to corresponding section in the current document for relevant potential requirements and gap analysis.
Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-6.24.3-001]
( [R-6.4.3-... |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.24.4 Use case on Initiation of Public train emergency voice communication | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.24.4.1 Description | Based on operational rules, additional information about the Public train emergency situation can be exchanged using voice communication, e.g the initiator of the Public train emergency voice communication may inform other involved FRMCS Users about the emergency situation. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.24.4.2 Service flows | Service flows are similar to Railway emergency voice communication, except that this is applicable to Public train emergency alert. Please refer to corresponding section in the current document.
In addition,
• the Public train emergency voice communication is not able to pre-empt Railway emergency communication.
• the ... |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.24.4.3 Potential requirements and gap analysis | Potential requirements are similar to Railway emergency communication, except the followings. Please refer to corresponding section in the current document for relevant potential requirements and gap analysis.
Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-6.24.4-001]
The Railwa... |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.24.5 Use case on Service interworking and service continuation with GSM-R | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.24.5.1 Description | The description is similar to the termination of Railway emergency communication, except that this is applicable to Public train emergency communication and no interworking in the direction from GSM-R Railway emergency call to FRMCS Public train emergency communication is required.
Please refer to corresponding Railway... |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.24.5.2 Service flows | Service flows for interworking - Mobile FRMCS User attached to GSM-R
There is no GSM-R counterpart for the FRMCS Public train emergency communication. No interworking in the direction from GSM-R Railway emergency call to FRMCS Public train emergency communication is required since a GSM-R Railway emergency call already... |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.24.5.3 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-6.24.5-001]
The FRMCS System shall provide the necessary means to FRMCS Users to set up a Public train emergency alert and /or Public train emergency voice communication, also to users in the legacy GSM-R system. Interworking betwee... |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.25 Railway staff emergency communication | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.25.1 Introduction | In this chapter the use cases related to Railway staff emergency communication are defined. The following use cases are defined:
- Initiation of the Railway staff emergency alert
- New entry to the Railway staff emergency alert
- Changing of the Railway staff emergency alert
- Merging of Railway staff emergency alerts
... |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.25.2 General overview | The Railway staff emergency communication is very similar to the Railway emergency communication, but both serve two different purposes.
The Railway emergency communication is meant to address staff of all Railway Undertakings in a given area, whereas the Railway staff emergency communication addresses only the users o... |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.25.3 Use case on Initiation of the railway staff emergency alert | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.25.3.1 Description | An FRMCS User is able to initiate the Railway staff emergency alert. Based on a set of conditions the FRMCS System will determine which FRMCS Users that shall be informed about the emergency.(see 6.25.2 General overview). The targeted FRMCS User can be e.g., railway staff, train staff, a train driver, an external syste... |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.25.3.2 Service flows | In any service flow, a mobile FRMCS User, e.g., a train driver, railway staff, train staff or maintenance staff of a specific organisation is not able to leave or terminate the railway emergency alert.
Operator initiated
Service flows are similar to Railway emergency communication, except that the operator is not an FR... |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.25.3.3 Potential requirements and gap analysis | Potential requirements are similar to Railway emergency communication, except the followings. Please refer to corresponding section in the current document for relevant potential requirements and gap analysis.
Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-6.25.3-001]
([R-6.4.3-... |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.25.4 Use case on New entry to the railway staff emergency alert | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.25.4.1 Description | Description is similar to Railway emergency communication, except that additional FRMCS Users can be e.g., railway staff, train staff, a train driver, a Railway staff emergency operator or maintenance staff. Please refer to corresponding section in the current document. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.25.4.2 Service flows | Service flows are similar to Railway emergency communication, except that the priority is lower than the Railway Emergency Alert. Please refer to corresponding section in the current document. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.25.5 Use case on Changing of the railway staff emergency alert | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.25.5.1 Description | Description is similar to Railway emergency communication, except that the authorised FRMCS User is an operator which is not an FRMCS Operator (i.e., independent from an administrator of the FRMCS System). Please refer to corresponding section in the current document. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.25.5.2 Service flows | Service flows are similar to Railway emergency communication, except that the priority is lower than the Railway Emergency Alert. Please refer to corresponding section in the current document. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.25.6 Use case on Merging of Railway Staff Emergency Alerts | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.25.6.1 Description | Description is similar to Railway emergency communication, except that the authorised FRMCS User is an operator which is not an FRMCS Operator (i.e., independent from an administrator of the FRMCS System). Please refer to corresponding section in the current document. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.25.6.2 Service flows | Service flows are similar to Railway emergency communication, except that the priority is lower than the Railway Emergency Alert. Please refer to corresponding section in the current document. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.25.7 Use case on Initiation of railway staff emergency voice communication | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.25.7.1 Service flows | Service flows are similar to Railway emergency voice communication, except that this is applicable to Railway staff emergency alert. Please refer to corresponding section in the current document.
In addition,
• the Railway staff emergency voice communication is not able to pre-empt Railway emergency communication.
• th... |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.25.7.2 Potential requirements and gap analysis | Potential requirements are similar to Railway emergency communication, except the followings. Please refer to corresponding section in the current document for relevant potential requirements and gap analysis.
Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-6.25.7-001]
The Railwa... |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.25.8 Use case on Service interworking and service continuation with GSM-R | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.25.8.1 Description | Service interworking of Railway staff emergency communication with GSM-R is not required. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7 Performance communication applications related use cases | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.1 Use cases related to transmission of real time video | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.1.1 Introduction | In this clause, the use cases related to the function of transmitting video in real time are defined.
- An FRMCS User requesting another FRMCS User to transmit real time video
- An FRMCS User receiving a request to transmit real time video
- An FRMCS User accepting a request to transmit real time video
- An FRMCS User ... |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.1.2 Use Case: An FRMCS User requesting another FRMCS User to transmit real time video | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.1.2.1 Description | An FRMCS User can request another FRMCS User to transmit real time video. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.1.2.2 Pre-conditions | The FRMCS User has a functional Role entitled to request other FRMCS Users to transmit real time video.
The requested FRMCS User can be addressed by the assigned functional identity(ies), FRMCS User Identity, or FRMCS Equipment Identity.
The FRMCS Equipment of the requested user is capable of providing video |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.1.2.3 Service flows | Requesting FRMCS User
From a list of FRMCS Users provided by the FRMCS System, or by entering an unlisted identity, the requesting FRMCS User selects another FRMCS User to be invited. The list may contain functional identities, FRMCS User identities, FRMCS Equipment Identities, or phone numbers. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.1.2.4 Post-conditions | The FRMCS User has been requested transmission of real time video. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.1.2.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-7.1.2-001]
The FRMCS System shall enable an entitled FRMCS User to request another FRMCS User to transmit video in real time.
A
22.281
5.1.2.2.2-xxx
[R-7.1.2-002]
The FRMCS System shall provide a list of identities for the requestin... |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.1.3 Use Case: An FRMCS User receiving a real time video request to transmit real time video |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.