hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.8 Authorisation of communication | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.8.1 Introduction | In this chapter the use cases related to authorisation of communication are described, the following use cases are identified:
• Permit / deny communication |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.8.2 Use case: Permit / deny communication | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.8.2.1 Description | The purpose of the authorisation function it to allow the network operator to control and regulate communications in order to avoid disruption/distraction to the users (for example Drivers during voice communication) and preventing unauthorised communication and to minimise network load.
The FRMCS System may therefore ... |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.8.2.2 Pre-conditions | An FRMCS User attempts to establish a communication. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.8.2.3 Service flows | Upon an attempt to establish a communication, the FRMCS System checks if the source FRMCS User address is allowed to invite the destination FRMCS User address. The FRMCS System shall consider for the verification process the source and destination FRMCS User address.
If multiple identities are simultaneously active to ... |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.8.2.4 Post-conditions | Either the communication has been established or the FRMCS User has been informed about the denial of the call attempt. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.8.2.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-9.8.2-001]
The FRMCS System shall be able to control and restrict the establishment of communication in order to avoid disruption/distraction of the FRMCS Users (for example Drivers).
A
TS 22.280
TS 22.280 sub-clause 6.7.3 Requireme... |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.9 Authorisation of application | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.9.1 Introduction | In this chapter the use cases related to authorisation of application are described, the following use case is identified
• Enabling/Disabling applications
• Robust mission critical group communication services
• Enabling/Disabling communication privileges per FRMCS User based on identities/talker status |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.9.2 Use case: Enabling/Disabling applications | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.9.2.1 Description | The FRMCS System shall allow the network operators to control the use of FRMCS Applications in order to avoid disruption/distraction to the FRMCS Users (for example Drivers), preventing unauthorised usage according to his Role.
The FRMCS System shall therefore be able to enable / disable FRMCS Applications for a FRMCS ... |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.9.2.2 Pre-conditions | The FRMCS User equipment is powered on and the FRMCS Application on the FRMCS User equipment has started. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.9.2.3 Service flows | Power-on
After powering on the FRMCS Equipment and start of the FRMCS Application on the FRMCS Equipment, the FRMCS System enables the FRMCS Application(s) on the FRMCS Equipment according to the Role related to the FRMCS subscriber identity.
Change of registration status
Upon a change in registration status by registr... |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.9.2.4 Post-conditions | The FRMCS User has access to all authorised FRMCS Applications. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.9.2.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-9.9.2-001]
The FRMCS System shall allow the network operator to control the use of FRMCS Applications in order to avoid disruption/distraction to the FRMCS Users (for example Drivers), preventing unauthorised usage according to his ... |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.9.3 Use case: Robust mission critical group communication services | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.9.3.1 Description | For reliable railway services, conventional way is to use dualization methodology. Most of railway services are based on on-network communication, which is supported by base station and core networks under 3GPP standard. However, when disaster happens so that the communication infrastructure is not feasible, railway se... |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.9.3.2 Pre-conditions | FRMCS Equipment for train driver, customer service staff, and train operations staff support device to device communications in the perspective of transport layer.
FRMCS Equipment for train driver, customer service staff, and train operations staff support on-network, off-network group communication services in the per... |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.9.3.3 Service Flows | 1. After initial disaster happens, emergency message (including voice or data) delivery service based on on-network group communication among train driver, customer service staff, or train operations staff have been preceded without any problem.
2. Disaster becomes worse, and associated communication infrastructure is ... |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.9.1.4 Post-conditions | Off-network or legacy network-based group communication among train driver, customer service staff, or train operations staff is activated and group communication service is maintained normally. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.9.3.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-9.9.3-001]
FRMCS Equipment shall support on-network based group communications.
A/T
TS 22.179 V.14.2.0
Support
[R-9.9.3-002]
FRMCS Equipment shall support off-network based group communications.
A/T
TS 22.179 V.14.2.0
Support
[R-9.9... |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.10 Sharing FRMCS Equipment by FRMCS Users | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.10.1 Description | Commonly, FRMCS Users may share FRMCS Equipment, e.g. a trainborne UE. To use the shared equipment securely, it is needed to identify the user for the equipment. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.10.2 Pre-conditions | A train driver is in a train.
The train driver has an identification card. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.10.3 Service Flows | The train driver wants to use a trainborne UE to make communication to train control centre.
The train driver puts his/her identification card in the trainborne UE to identify himself/herself. In this case, the identification card is an example. It can be a type of ID number, finger-print, etc. instead.
The trainborne ... |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.10.4 Post-conditions | The train driver makes a call to the train control centre.
The train driver receives a call using the trainborne UE that is relayed by FRMCS. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.10.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-9.10-001]
The FRMCS System shall be able to provide a mean to identify a FRMCS User (for example, the train driver).
A
TS 22.280
TS 22.280 sub-clause 5.9a and covered by many requirements in MCX
[R-9.10-002]
The FRMCS System shall b... |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.11 FRMCS naming authority | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.11.1 Description | The FRMCS Naming Authority (NA) is a registry service provided by FRMCS System to facilitate the handling of various namespaces, number spaces or other information sets needed to support FRMCS services.
For example, FRMCS User identification requires a registry to manage the identification information which shall not b... |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.11.2 Pre-conditions | A new train driver is registered as a new user of FRMCS.
A new trainborne UE is installed in a train. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.11.3 Service Flows | The new train driver wants to use FRMCS System.
The train driver makes a request to register the user identification information in FRMCS with his/her finger-print as an identification method.
The FRMCS checks the duplication of the user identification under the guidance of FRMCS NA and registers the user identificatio... |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.11.4 Post-conditions | The train driver is registered as a new user in FRMCS System without duplication of user identification information.
The user identification information is stored in the secure storage safely.
The trainborne UE is installed in the train and is registered as a new FRMCS UE in FRMCS System without duplication of UE addre... |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.11.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-9.11-001]
The FRMCS System shall be able to avoid duplication of identities.
A
22.280
covered by 22.280
[R-6.9-002]
[R-9.11-002]
The FRMCS System shall be able to provide secure method to store the identification information.
A
Not ... |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.12 Wayside-Centric Automatic Train Control | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.12.1 Description | Signalling block system, which is a fundamental factor in the perspective of train control, enables the safe and efficient operation of railways to avoid collisions between trains. The signalling block system basically keeps a train away from entering the block occupied by the other train. It is commonly known that mov... |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.12.2 Pre-conditions | 1. The user equipment dedicated to train control gets power-on, and registers to the train control system.
2. WATPs are located in the Packet Data Network (PDN), and each train knows the nearby WATP which can offer a movement authority and make it move.
3. The user equipment establishes a connection through the 3GPP ne... |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.12.3 Service flows | 1. The OATP periodically report its position to the serving WATP.
2. The WATP periodically provide movement authority to the OATP
3. The train accelerates, or triggers brake based on the last received movement authority. It moves till the position that it is authorized to move, and stops if it reaches to the border of ... |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.12.4 Post-conditions | The train triggers emergency brake and stops immediately if the connection is lost and data is not received for a certain time from WATP. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.12.5 Potential requirements and gap analysis | Requirement Reference Number
Requirement text
Application/
Transport
SA1 spec covering
Comments
[9.12-001]
The FRMCS System shall provide a mechanism for a train to autonomously discover an assigned application server which can offer movement authority.
A/T
22.280
This requirement is covered by the combination of funct... |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.13 Autonomous Train Control and Operation | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.13.1 Description | In legacy train control systems, trains typically decide its movement by interacting with trackside devices (e.g. track circuits, balise, radio block system) or communicating with a trackside server. If a train can autonomously figure out the positions of the nearby trains and decide its movement authority, the transpo... |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.13.2 Pre-conditions | 1. Trains know the overall schedule, and the user equipment of each train is connected to the user equipment of the other trains operating at the same time.
2. A user equipment of each train is able to establish a connection with the object Controller for the nearby point machine. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.13.3 Service Flows | 1. A train gets started and try registration to the currently operating trains. The registration message includes the position of the train.
2. The train gets the responses of the registration from the other trains and estimates the positions of the trains.
3. The train decides its movement authority based on the posit... |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.13.4 Post-conditions | The autonomous train control is achieved by activating movement authority for each train or activating object Controller for nearby point machine. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.13.5 Potential requirements and gap analysis | Requirement Reference Number
Requirement text
Application/Transport
SA1 spec covering
Comments
[9.13-001]
The 3GPP network shall provide a mechanism using on-network communications to establish a bearer from a user equipment to the other user equipment
A
22.280
The requirement of [R-5.9a-002] “The MC User shall be reac... |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.14 Virtual Coupling | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.14.1 Description | One of the important missions that the future railway service should achieve is to increase its transport capacity. A straight-forward solution is to minimize the distance between successive trains so that train interval is reduced. It is difficult to do so in a legacy train control system, because the successive train... |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.14.3 Service Flows | 1. The following train begins to approach to the leading train by exchanging the information about their position. The two trains, which are far enough to allow a certain amount of end-to-end latency, are initially connected through the 3GPP network.
2. As the following train approaches to the leading train, they start... |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.14.4 Post-conditions | For safety train operation, integrity needs to be checked for train control information delivery in the perspective of application or transport layer. Any error on integrity check shall be immediately reported to the train control application. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.14.5 Potential requirements and gap analysis | Requirement Reference Number
Requirement text
Application/Transport
SA1 spec covering
Comments
[9.14-001]
An On-board FRMCS UE for automatic train control shall be able to communicate through off-network up to 3km in the line of sight channel environment.
T
22.289
This requirement is covered by section 5.2.2 of TS22.28... |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.15 Composite-based train operation | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.15.1 Description | This use case considers the composition and decomposition of trains or tractions. One is the case, where two autonomous trains / traction (train A and train B) are conducted as one composition (Train C). The other case describes the decomposition of a train set (Train C) into autonomous train A and train B. For these s... |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.15.2 Pre-conditions | Train A and Train B share information for train operation such as position and velocity profile. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.15.3 Service Flows | Train composition
1. Train/traction A and Train/traction B are autonomous trains and moving on different tracks.
2. Train/traction A and the train/traction B are put together into one train composition using the same railway.
3. Consequently, the different FRMCS UE identities of train/traction A and train/traction B ar... |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.15.4 Post-conditions | 1. Train/traction C arrives at the destination consisting of train/traction A&B
2. Train A and Train B arrive at the planned destination. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.15.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[9.15-001]
The FRMCS System shall be able to assign and withdraw an FRMCS Equipment Identity common to several FRMCS Equipment, e.g. for trains being coupled together in order to be reachable under the same FRMCS Equipment Identity.
A
... |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.16 Arbitration related use cases | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.16.1 Introduction | In this chapter the use cases related to arbitration are defined. The following use cases are defined:
• Arbitration
• Arbitration for communication auto-connection |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.16.2 Use case: Arbitration | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.16.2.1 Description | The FRMCS System shall be able to perform arbitration, based on the context of the communication. Arbitration in this context means that the FRMCS System is able to determine the behaviour of the end user device in case of multiple competing communications. Additionally, the FRMCS System may ask the FRMCS User which co... |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.16.2.2 Pre-conditions | The FRMCS System is authorised to perform arbitration on communication on the end user device. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.16.2.3 Service flows | Incoming communication
When the communication is received by the FRMCS User on any of its registered functional identities, the FRMCS System provides to the FRMCS User arbitration information.
FRMCS System is able to present arbitration options to the FRMCS User to select from.
Arbitration of communication determines a... |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.16.2.4 Post-conditions | The communication is established to the FRMCS Equipment the FRMCS User has selected. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.16.2.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-9.16.2-001]
The FRMCS System shall be able to provide communication to the FRMCS User based on the arbitration information associated with the communication.
A
TS 22.280 section 6.19.1
[R-9.16.2-002]
The FRMCS System shall be able t... |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.16.3 Use case: Arbitration for communication auto-connection | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.16.3.1 Description | The FRMCS System shall be able to automatically accept incoming communications without asking the FRMCS User, based on configuration (i.e., configured arbitration rules). |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.16.3.2 Pre-conditions | The FRMCS System is authorised to perform arbitration on communication on the FRMCS Equipment (i.e., end user device). |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.16.3.3 Service flows | FRMCS User is using a single FRMCS Equipment
When the communication is received by the FRMCS User on any of its identities (including registered functional identities), the FRMCS System automatically accepts the incoming private or group communication if arbitration rules are configured to do so.
FRMCS User is using mu... |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.16.3.4 Post-conditions | The incoming communication is automatically accepted to the relevant FRMCS Equipment the FRMCS User is logged in. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.16.3.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-9.16.3-001]
When an incoming private communication is received by the FRMCS User, the FRMCS System shall be able to automatically accept the communication if arbitration rules are configured to do so (based on FRMCS User identities,... |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.17 Data communication to exchange key information for train safety application use cases | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.17.1 Introduction | In this chapter the use cases related to Key management communication are defined. The following use cases are defined:
• Initiation of a Key Management data communication
• Termination of a Key Management data communication
• Service interworking and service continuation with GSM-R |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.17.2 Use case: Initiation of a Key Management data communication | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.17.2.1 Description | Key Management communication is the application which performs the functions that ensure the exchange of credentials/keys required by other applications (such as ATO, ATP) to ensure the correct authentication of the end users of each application and the integrity of the messages exchanged.
Some Key Management systems r... |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.17.2.2 Pre-conditions | The initiating application on the FRMCS equipment is authorised to initiate the Key Management data communication. This is managed by the authorisation of communication application.
The receiving application on the FRMCS equipment is authorised to use the Key Management data communication. This is managed by the author... |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.17.2.3 Service flows | The initiating application on the FRMCS equipment (e.g. on-board of the train or the key distribution centre at the track side) initiates the Key Management data communication to the receiving side on the FRMCS equipment (e.g. key distribution centre at the trackside or on-board of the train). The QoS profile of the co... |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.17.2.4 Post-conditions | The initiating application on the FRMCS equipment is connected to the receiving application.
Data can be exchanged between the Key Management applications. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.17.2.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-9.17.2.5-001]
For Key management communication, the communication shall be considered to be user-to-user data communication.
A
TS 22.282
TS 22.282
Sub-clause: 5.5
Note: Application Layer Key Management is transparent to the transpor... |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.17.3 Use case: Termination of a Key Management data communication | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.17.3.1 Description | The initiating or the receiving application can terminate de Key Management data communication. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.17.3.2 Pre-conditions | The Key Management applications on-board and trackside have a data communication initiated. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.17.3.3 Service flows | The terminating application on the FRMCS equipment (e.g. on-board of the train or the key distribution centre at the track side) terminates the Key Management data communication with the receiving side application on the FRMCS equipment (e.g. key distribution centre at the trackside or on-board of the train).
The FRMCS... |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.17.3.4 Post-conditions | The terminating Key Management data application is disconnected from the receiving application. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.17.3.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-9.17.3.5-001]
For Key management communication, the terminating application on the FRMCS equipment (e.g. on-board of the train or the key distribution centre at the track side) shall be able to terminate the Key Management data comm... |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.17.4 Use case: service interworking and service continuation with GSM-R | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.17.4.1 Description | For migration purposes the service interworking and service continuation between the GSM-R system and FRMCS system for Key Management data communication needs to be clear.
Depending on the migration scenario a key distribution centre can be attached to the FRMCS system, to the GSM-R system or both. The on-board Key Man... |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.17.4.2 Pre-conditions | The initiating application on the FRMCS equipment is authorised to initiate the Key Management data communication. This is managed by the authorisation of communication application.
The receiving application on the FRMCS equipment is authorised to use the Key Management data communication. This is managed by the author... |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.17.4.3 Service flows | Initiating Key Management application attached to GSM-R
When the initiating Key Management application on the FRMCS equipment is attached to the GSM-R system and is initiating data communication to another Key Management application, the GSM-R system will route the data communication accordingly.
If the other Key Manag... |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.17.4.4 Post-conditions | None. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 10 Performance support applications related use cases | Editor’s Note: Text to be provided. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 11 Business support applications related use cases | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 11.1 Charging and Billing information related use cases | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 11.1.1 Introduction | In this chapter the use cases related to charging and billing are defined. The following use cases are defined:
- Obtaining charging and billing information |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 11.1.2 Use case: Obtaining charging and billing information | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 11.1.2.1 Description | The Railway operators may have the obligation or the desire to charge FRMCS Users of their FRMCS Networks, or to use billing information for statistical reasons.
An entitled FRMCS User shall be able to obtain information for any type of FRMCS communications from the FRMCS system, to be able to generate bills. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 11.1.2.2 Pre-conditions | An entitled FRMCS User is logged on to the FRMCS system. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 11.1.2.3 Service flows | The entitled FRMCS User requests billing information for a single FRMCS User or a group of FRMCS Users.
The entitled FRMCS User selects defined criterias (e.g. timeframe, incoming communications, outgoing communications, numbers and/or any kind of FRMCS Identity) to get more detailed results.
The entitled FRMCS User co... |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 11.1.2.4 Post-conditions | The requested billing information is generated from the FRMCS System. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 11.1.2.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-11.1.2-001]
The FRMS System shall be able to generate charging records for one or multiple FRMCS Users based on defined criterias (e.g. timeframe, incoming communications, outgoing communications, numbers and/or any kind of FRMCS Id... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.