hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 4
595
| content
stringlengths 0
6.67M
|
|---|---|---|---|
3239937b55fdc406849fa93870986364 | 22.916 | 5.6 Real-time conversational robot | |
3239937b55fdc406849fa93870986364 | 22.916 | 5.6.1 General description | This scenario proposes a service robot who participates in a spoken conversation with a human.
Voicebots can enable an elderly person to access those digital services which use is difficult for them due to physical or cognitive challenges. Voicebots are well suited especially for primary contacts with customer service, because they make it easier and faster to access the services. In addition, voice bots can help in gathering information related to elderly’s wellbeing and functioning, for example. This can speed up health care personnel’s response to the customer's service needs, making the allocation of resources easier while improving patient safety as a consequence.
In addition, voicebots can support health care professionals to perform routine tasks which often requires lot of resources. Voice-based solutions can speed up, for example, making appointments, reporting laboratory results, or customer surveys for large groups. In this manner, professionals’ resources would be freed up for those tasks where there is need for human service.
Fundamentally, a voicebot can work in one of three ways:
1) The user’s device works on the text transcript of the customer’s speech, obtained using an Automatic Speech Recognition (ASR) engine, send this text transcript to a cloud or Edge based Natural language processing (NLP) and natural language understanding (NLU) entity capable of processing text transcripts, receive a response, and the user’s device converts the text response to voice using a Text-to-speech (TTS) engine,
2) The user’s device records voice input as audio samples, transmits these audio samples to a cloud or Edge based NLP and natural language understanding (NLU) entity capable of processing speech audio, receive a response, and the user’s device converts the text response to voice using a TTS engine,
3) The user’s device establishes a voice call (VoIP, VoLTE, VoNR, RCS, or other) towards a cloud or Edge function which directly interprets the speech, performs analysis and response formulation, before directly responding to the user by generating speech.
There are latency constraints with solution (1) (many ASR and TTS engines each consume a second of processing time, rendering the speech flow unnatural) which might limit suitability for conversational services. Typically, solution (3) is preferred in the voice assistant industry where conversational response times are less critical. It is proposed here that for voicebot services, solution (3) is the prime candidate. However, it should be noted that if the seconds of latency experienced in solutions (1) and (2) are covered by some language or some sound as the voicebot retrieves information, the perceived latency may be much less insignificant compared to the actual latency.
Solution (3) results in the requirement that the 3GPP system needs to be able to maintain a resilient voice connection with sufficient throughput and quality to enable the user’s speech to be adequately processed at the cloud or Edge ASR engine, to allow for voicebot processing and response generation, and for the voicebot’s response to be received by the user with sufficiently low latency as to enable a perception of “humanity” by the user. |
3239937b55fdc406849fa93870986364 | 22.916 | 5.6.2 Related existing service requirements | TS 22.261, clause 7.6.1: To support interactive task completion during voice conversation, the 5G system shall support low-delay speech coding for interactive conversational services (100 ms, one-way mouth-to-ear).
ITU-T Recommendation G.114 & 3GPP TS 26.114: See Figure 5.6.2-1 for the relationship between mouth-to-ear delay (one way transmission time for voice, also consider this as voicebot-to-ear delay) and perceived quality by the user
Figure 5.6.2-1: ITU-T Rec. G.114 – Determination of the effects of absolute delay by the E-model. |
3239937b55fdc406849fa93870986364 | 22.916 | 5.6.3 Challenges and potential gaps | None. |
3239937b55fdc406849fa93870986364 | 22.916 | 5.7 MEC for Efficient Management of Geo-surface Sensing Data Using a Group of Aerial Robots | |
3239937b55fdc406849fa93870986364 | 22.916 | 5.7.1 General description | Geo-surface Sensing:
Geo-surface sensing is a wide area of remote sensing applications encompassing, but not limited to:
• agricultural use cases such as detecting the change of farming field surface (e.g., growth and/or other conditions of plants) [20,21]
• wildlife preservation use cases such as detecting / tracking the movement or change of certain kind of animals of interest [23]
• 3D architectural design and urban planning use cases: urban planning covers both new development and renovation that are supported by geo-surface sensing technology combined with data collection, analysis and prediction via collaboration of multiple entities (e.g., autonomous robots capable of role-playing in various settings), which require communications.
• many more
which are expected to produce a huge amount of measurement data that would require certain level of pre-processing and sharing with participating role-players for efficient data fusion. The quality of outcome of data fusion is an important optimization objective and, at the same time, the efficiency of the process required to draw out quality outcome is also critically important. Considering the United Nations’ Sustainable Development Goals, study on recommendations and requirements is essential for developing resource-efficient (e.g., energy-efficient, time-efficient) and sustainable solutions.
Multi-access Edge Computing (MEC) for SOBOT:
Edge cloud service (or MEC) for service robots is an emerging technology aimed at enhancing the performance and efficiency of these robots. It involves granting robots access to computing resources located closer to them, resulting in reduced latency and improved service quality.
Using edge cloud service offers several advantages for service robots. Firstly, it enhances their performance by providing them with access to more robust computing resources. This enables robots to execute complex tasks, such as navigating intricate environments or engaging in natural interactions with humans.
Secondly, edge cloud service improves the efficiency of service robots by offloading some processing tasks to the edge cloud. This alleviates the robot's own resources, extending its battery life and making its operation more cost-effective.
While still in the developmental stage, edge cloud service has the potential to revolutionize the use of service robots. By equipping robots with powerful computing resources, this technology enhances their performance and efficiency, paving the way for innovative applications.
Below are examples illustrating how edge cloud service can benefit service robots:
• Intelligent navigation: Real-time information about the robot's surroundings, including obstacle locations, can be provided through edge cloud service. This assists in improving navigation performance and avoiding collisions.
• Object recognition: Edge cloud service enables robots to recognize objects in their environment, enhancing their ability to interact with objects and accomplish tasks.
• Human-robot interaction: By leveraging edge cloud service, robots can communicate and interact with humans in a more natural manner. This facilitates better comprehension and response to human commands.
Edge cloud service is a promising new technology that has the potential to revolutionize the way that service robots are used. By providing robots with access to more powerful computing resources, edge cloud service can improve the performance and efficiency of robots, which can lead to new and innovative applications for service robots.
Fig. 5.7.1-1 presents some examples of usage scenarios where MEC (Edge cloud service) is used for geo-surface sensing data management. The expected types of aerial robots are fully autonomous robots, semi-autonomous robots, remote-controlled / teleoperated robots. The robots are expected to be able to meet the orientation value requirement, required by the robot operator or by the operating applications that are coordinated by the robot operator in the edge cloud.
Fig. 5.7.1-1: Usage scenarios of MEC (Edge cloud service) for geo-surface sensing data management. Some features and KPI characteristics for communication are recommended. |
3239937b55fdc406849fa93870986364 | 22.916 | 5.7.2 Related existing service requirements | Clock synchronisation: 3GPP TS 22.104
• clause 5.6.1 Clock synchronisation service level requirements
• clause 5.6.2 Clock synchronisation service performance requirements
• clause 7.2.3.2 Clock synchronisation requirements
NOTE 1: The MEC scenario described in 5.X.1 assumes collaboration among the group of aerial robots. The data collection and sensor fusion aspects (in clause 5.3 and in Annex A – Levels of Fusion) are still important considerations for this MEC scenario.
NOTE 2: The types of sensor data and media that robots are collecting, pre-processing and sharing with each other and/or with edge cloud (or edge server, cloud server) are related to the need of fulfilling the above sets of requirements.
Multi-path relay: 3GPP TS 22.261
• clause 6.9.2.1 support of a traffic flow of a remote UE via different indirect network connection paths
Positioning: 3GPP TS 22.261
• clause 7.3.2 High accuracy positioning performance requirements (see also clause 5.7.1 of 3GPP TS 22.104 for Factory of the Future scenario)
Efficient user plane: 3GPP TS 22.261
• Clause 6.5 Efficient user plane
Service continuity: 3GPP TS 22.263
• clause 5.5 Service continuity |
3239937b55fdc406849fa93870986364 | 22.916 | 5.7.3 Challenges and potential gaps | The following applicable aspects are identified and recommended for further study and can be further considered with other ongoing or recently completed Studies if applicable.
[CPG-5.7.3-001] A robot that is participating in a group project and is designated (or nominated) by the robot operator is expected to be able to meet the orientation value requirement, required or adjusted by the robot operator or by one or more operating applications that are coordinated by the robot operator in the edge cloud.
NOTE 1: The orientation value defined and required by the robot operator is expected to be used by communications layer(s), e.g., for ranging, when certain communications layer KPI target needs to be adjusted for robot operation.
NOTE 2: In this scenario, a robot consists of robot communicating part and, optionally, a combination of robot actuating part, robot processing part, and robot sensing part.
NOTE 3: The expected types of robots listed in Clause 5.X.1 are intended to describe the robots’ capability to maneuver over the project site (job site) but are not intended to describe their capability to control / adjust orientation for sensing and measurements. Such capabilities are intended to be specified in combination of communication features in CPGs.
[CPG-5.7.3-002] 5G system is expected to provide a means to ensure continuity of session when a subset of robots participating in a group project need handover (i.e., switching between source gNB and target gNB) or trigger a relocation from the current MEC server to a new MEC server.
NOTE 4: The term “continuity of service” can be interpreted in a few different ways, depending on the type of robotic applications. For example, for real-time acoustic and/or audio sensing data, it can be interpreted as “service continuity” (i.e., within 20 ms of interruption), for 3D RF sensing measurement data, it is recommended to ensure up to 10ms of interruption not including the intrinsic propagation delay (e.g., a total of approximately 500 ms for one round trip to a ground station over a GEO satellite, 4 * 125 ms) [25]. For example, the minimum value occurs when a UE is located at a point on the equator closest to the satellite, 36 000 km / (3 * 10^5 km / s) ≈ 120 ms..
[CPG-5.7.3-003] 5G system is expected to provide a means to ensure the acceptable range of arrival time difference(s) of information, defined and required by the robot operator for particular robotic application(s), when the robotic application(s) uses multiple routes for information delivery (e.g., one terrestrial route and one non-terrestrial route).
[CPG-5.7.3-004] 5G system is expected to provide a means to expose the capability on propagation delay-related information when offering candidate routes to the robotic application(s).
[CPG-5.7.3-005] 5G system is expected to provide a means to provide expected disruption time for the robot when communication path switching (e.g., from satellite to terrestrial, or vice versa) is necessary so that the robot can select suitable alternative path according to its preference and traffic characteristics. |
3239937b55fdc406849fa93870986364 | 22.916 | 5.8 A group of autonomous robots and tele-operated robots working on mining actuation and delivery | |
3239937b55fdc406849fa93870986364 | 22.916 | 5.8.1 General description | |
3239937b55fdc406849fa93870986364 | 22.916 | 5.8.1.1 The use of a group of robots in mining: | It is expected that the mining industry pave new pathways toward global sustainability, including “greater inclusion and diversity effort” (e.g., worker safety, well-being of employees in general), green/clean energy transition, material consumption reduction, deep sea mining explortion, greenfield exploration [27]. More interestingly, the industry is with no exceptions as other industries, exploring a new path to “cloud-integrated mining processes”.
Fig. 5.8.1.1-1 Examples of extreme working conditions in mining site (underground).
Fig. 5.8.1.1-2 Examples of extreme working conditions with workers’ roles replaced by robots. Integrated sensing and communications (ISAC), distributed sensing and communication (data collections), and AI-enabled compute are expected.
Among these, (1) greater inclusion and diversity effort (with a narrower angle of worker safety using tele-operated robots in mining) and (2) cloud-integrated mining processes are interesting topics for consideration in the telco domain (refer to Fig. 5.8.1.1-1 and Fig. 5.8.1.1-2).
Robots have a range of applications in the mining industry, contributing to increased safety, efficiency, and productivity. Here are some tasks that robots can perform in mining:
1. Exploration and Mapping: Robots can be equipped with various sensors, such as LiDAR and cameras, to explore and map underground or hazardous areas that might be dangerous for humans.
2. Drilling and Blasting: Automated drilling and blasting robots can accurately and safely bore holes for explosives, increasing precision and minimizing the risk to human operators.
3. Hauling and Transport: Robotic vehicles can be used for hauling materials, removing the need for human drivers in dangerous environments. These robots can transport materials within mines and even across long distances.
4. Inspection and Maintenance: Robots can inspect equipment and infrastructure, identifying issues before they become serious. They can also perform maintenance tasks in hazardous areas, reducing the need for human workers in risky environments. Note: Maintenance includes corrective maintenance and preventive maintenance. Predictive maintenance is related to preventive maintenance.
5. Remote Operation: Teleoperated or semi-autonomous robots can be controlled by operators from a safe location, allowing them to work in environments that are unsafe for humans.
6. Hazardous Environment Exploration: Robots can be deployed in areas with extreme temperatures, toxic gases, or other hazardous conditions, where human presence would be dangerous.
7. Material Sorting and Processing: Robots can be programmed to sort and process mined materials, improving efficiency and accuracy in material separation.
8. Surveying and Mapping: Robots equipped with advanced sensors can create detailed 3D maps of mining sites, helping with planning and optimization.
9. Search and Rescue: In the event of a mine collapse or other emergency, robots equipped with cameras and sensors can be used to search for trapped miners and assess the situation.
10. Environmental Monitoring: Robots can be used to monitor air quality, water quality, and other environmental factors in and around mining sites.
11. Dust Suppression: Robots can be designed to control dust levels, which is crucial for the health and safety of miners.
12. Rehabilitation and Land Restoration: After mining operations cease, robots can be employed to rehabilitate and restore mined areas, aiding in reforestation or other environmental recovery efforts.
The use of robots in mining can improve safety for human workers, increase operational efficiency, and enable the extraction of resources from challenging and hazardous environments.
Motivation and Discussion:
In the on-surface environment of radio signal propagation (i.e., one being line-of-sight reception and the other a slightly longer reflected one, which are combined at the receiver’s side), the signal transmission and reception situation is not ideal due to the inherent 'phase difference' caused by reflection, as depicted in Fig. 5.8.1.1-3 below. The point that we bring in is to lead to the main motivating message that the signal propagation situation is so difficult in underground tunnels (as justified in the point #2 below).
Fig. 5.8.1.1-3: Phase difference caused between two antennas on a horizontal ground surface with different heights. The phase difference is depedent upon seveal parameters, the antenna heights, and some other parameters, such as a, b, l, and θ.
In the underground tunnel environment, there are two characteristics that are simply observed:
1) motivating argument #1: The signal reflections are multifold around the inner surface of the tunnel which is furthermore “uneven”:
2) motivating argument #2: The communication nodes (i.e., UEs/Robots or mining carts that have UE functionality) are distributed along the tunnel pathway.
3)
Justification on point #1 (as motivating argument #1):
In underground tunnels, radio propagation faces significant challenges due to the confined and reflective nature of the environment. Signals can be absorbed, diffracted, or reflected by the tunnel walls, leading to multipath propagation. This phenomenon creates multiple signal paths between the transmitter and receiver, causing delays and phase differences in the received signals. As a result, the radio propagation situation in underground tunnels is complex, making it difficult to achieve reliable and stable communication. Specialized techniques and equipment are often required to mitigate these challenges and ensure effective wireless communication in such environments.
Justification on point #2 (as motivating argument #2):
The distribution of mining carts (which we assume are equipped with UE functionality and called robots) in a mining tunnel typically involves strategic planning and organization to ensure efficient transportation of materials and resources within the mine. Mining carts, also known as mine cars or skips, are used to transport extracted ore, waste, or other materials from the mining face to the surface or processing area. The distribution process involves several key considerations:
1) Loading and Filling: Mining carts are loaded with ore or other materials at the mining face. Proper loading ensures maximum utilization of the cart's capacity while maintaining safety standards.
2) Transportation Routes: Mining tunnels are designed with specific transportation routes for the mining carts. These routes are planned to optimize the movement of carts, minimize congestion, and ensure a smooth flow of materials within the mine.
3) Track Systems: Mining carts often run on track systems embedded in the tunnel floor. These tracks guide the carts, preventing derailments and ensuring stable movement along the designated routes.
4) Automated Systems: In modern mining operations, automated systems, such as conveyor belts or autonomous vehicles, might be used to transport materials. These systems can enhance efficiency and reduce the need for manual distribution of mining carts.
5) Monitoring and Control: Mining companies use monitoring systems to track the movement of mining carts. Sensors and communication technologies are employed to monitor the location, load capacity, and maintenance needs of the carts. This data helps optimize the distribution process and prevent bottlenecks.
6) Safety Protocols: Safety is paramount in mining operations. Adequate safety protocols, including signaling systems, speed limits, and emergency procedures, are in place to ensure the safe distribution of mining carts and the protection of workers in the tunnels.
Overall, the distribution of mining carts in mining tunnels requires careful planning, efficient logistics, and the integration of technology to optimize the transportation of materials and maintain a safe working environment.
It is commonly agreed that carts cannot remain outside the designated pathway space of the tunnel unless unintended events occur.
Characteristics of the ”set of UE relays” consisting of robots in mining tunnel:
1) Serially distributed;
2) the random variable of inter-node distance depends the mining operation strategy
3) if the communication nodes (e.g., carts with UE functionality) are available to use non-conventional (or advanced) communication/networking schemes, such as cooperative diversity (or cooperative communication/networking) and network coding, the topology of the network is not completely serial but is a combined one.
Fig. 5.8.1.1-4: (a) conventional, serially connected multihop network (b) non-conventional, serially connected multihop network with a supplementary link supported (e.g., when cooperative diversity is applied). |
3239937b55fdc406849fa93870986364 | 22.916 | 5.8.1.2 Enhanced support of communnications and sensing features: | Mining as a whole takes place in extreme environments under the ground surfaces (e.g., search, monintor, preparation, processing, maintenance, repair shop, mining actuation (i.e., drilling operations), loading and underground delivery to off-surface station) and some tasks require their completion on the ground surface.
According to the US Energy Information Administration (www.eia.gov, as of 2021), the average number of employees at underground and surface mines differs from one State to another: 755 at underground and 272 at surface mines in Pennsylvania; 2103 at underground in West Virgina (Northern), 184 at underground and 36 at surface mines in West Virgina (Southern). Along a single or multiple tunnels, a set of tandem communication sub-networks can be formed as dipicted in Fig. 5.8.1.2-1. Each sub-network might include a 3GPP UE-type entity that only requires an intermittant communications (e.g., Ambient IoT device).
NOTE: It is assumed that a set of multihop UE relays consists of a group of service robots that are performing specific task(s) with (autonomous or tele-operated) physical mobility inside the mining job site. However, non-robot type of UE’s can also be part of a set of multihop UE relays.
Fig. 5.8.1.2-1 Some examples of set of multihop UE relays of robots at underground mines. |
3239937b55fdc406849fa93870986364 | 22.916 | 5.8.2 Related existing service requirements | Clock synchronisation: 3GPP TS 22.104
• clause 5.6.1 Clock synchronisation service level requirements
• clause 5.6.2 Clock synchronisation service performance requirements
• clause 7.2.3.2 Clock synchronisation requirements
NOTE 1: The MEC scenario described in 5.X.1 assumes collaboration among the group of aerial robots. The data collection and sensor fusion aspects (in clause 5.3 and in Annex A – Levels of Fusion) are still important considerations for this MEC scenario.
NOTE 2: The types of sensor data and media that robots are collecting, pre-processing and sharing with each other and/or with edge cloud (or edge server, cloud server) are related to the need of fulfilling the above sets of requirements.
Multi-path relay: 3GPP TS 22.261
• clause 6.9.2.1 support of a traffic flow of a remote UE via different indirect network connection paths
Positioning: 3GPP TS 22.261
• clause 7.3.2 High accuracy positioning performance requirements (see also clause 5.7.1 of 3GPP TS 22.104 for Factory of the Future scenario)
Efficient user plane: 3GPP TS 22.261
• Clause 6.5 Efficient user plane
Service continuity: 3GPP TS 22.263
• clause 5.5 Service continuity, when required by the application
Multi-hop connectivity: 3GPP TS 22.261
Energy efficiency: 3GPP TS 22.261
Integrated Sensing and Communication features: 3GPP TS 22.261, TS 22.137 (new). |
3239937b55fdc406849fa93870986364 | 22.916 | 5.8.3 Challenges and potential gaps | The following applicable aspects are identified and recommended for further study and can be further considered with other ongoing or recently completed Studies if applicable.
[CPG-5.8.3-001] 5G system is expected to provide a suitable means that can support an advanced energy-efficient mechanism for a group of robots that formed a set of multihop UE relays.
[CPG-5.8.3-002] 5G system is expected to provide a suitable means for robots that formed a set of multihop UE relaysto gain access to MEC service in order to determine whether or not to use certain advanced energy-efficient mechanism for a group of robots that formed a set of multihop UE relays.
[CPG-5.8.3-003] 5G system is expected to provide a suitable means for robots within a set of multihop UE relaysto timely reselect another energy-efficient mechanism for the set of multihop UE relayswhen communication is disrupted (e.g., connection loss, the existing energy-efficient mechanism becomes unavailable due to remarkable changes of inter-robot distance).
NOTE 1: The above CPGs are intended to ensure that a group of robots as a UE should have advanced energy-efficient mechanisms that are relevant to existing and new spectrum bands for 3GPP systems (e.g., cooperative diversity, full duplex, network coding) [26]. However, studies on such candidate mechanisms are up to the relevant Working Group within 3GPP, which is outside the scope of stage-1 study.
NOTE 2: The above CPGs are intended for a group of robots as a UE that are working under extreme conditions (e.g., at underground mines)
NOTE 3: In [CPG-5.8.3-002], examples of “gain access to MEC service” includes requesting distributed compute service (e.g., via edge or cloud) for certain task that is computationally intensive, such as scheduling, whether or not to use certain advanced mechanisms. |
3239937b55fdc406849fa93870986364 | 22.916 | 6 Other considerations | |
3239937b55fdc406849fa93870986364 | 22.916 | 6.1 TACMM aspects related to robot applications | |
3239937b55fdc406849fa93870986364 | 22.916 | 6.1.1 General description | 3GPP Release 18 stage-1 study on tactile and multimodality communication (TACMM) [28] involves identifying potential service and performance requirements for efficient data transmission, coordinations across devices (e.g., haptic glove, haptic wear, and so on as a 5G UE) and networks. These advancements have the potential to revolutionize how we interact remotely, making communication more immersive, expressive, and accessible.
NOTE 1: In the Release 18 TACMM study, the scope was focused on providing multimodality communication between a UE and a 5G network with no intermediate nodes acting as a relay. In a multi-hop connections scenario, certain devices (such as gloves, goggles) are connected to 5G network via a 5G UE. In this case, the devices are not considered as 5G UEs. Devices (gloves, goggles, etc.) are only considered as 5G UEs when they are directly connected to 5G network as shown in Fig. 6.1.1-1. It is observed that multi-hop aspects are not considered in the consolidated KPI table. However, some multi-hop aspects are captured in 3GPP TS 23.501, clause 5.37.2.
Fig. 6.1.1-1: Example of topology studied within 3GPP Release 18 TACMM (single hop connections only). Source: Fig. 5.1.2-1 of 3GPP TR 22.847.
The following user cases from TACMM study (TR 22.847) are related to robot applications.
• 5.2 Remote control robot
• 5.4 Support of skillset sharing for cooperative perception and manoeuvring of robots
• 5.5 Haptic feedback for a personal exclusion zone in dangerous remote environments
• 5.8 Virtual factory
UC - Remote control robot
Refer to the next UC.
UC - Support of skillset sharing for cooperative perception and manoeuvring of robots
Automated vehicles (robots) mostly rely on individual controllers, which can be limiting in unpredictable settings. Efforts by 3GPP have explored LTE-based V2V features, but challenges persist in unstructured contexts. Sharing sensor info and maneuvers is a solution, facilitated by Tactile Internet for fast data exchange between nearby vehicles. This enables cooperative perception and maneuvering, enhancing safety and prediction. Tactile Internet allows vehicles to collectively perceive their surroundings through shared local and remote maps, extending sensing range and prediction. New network architectures are needed for ultralow-latency connections based on Tactile Internet, supporting cooperative driving. This addresses scenarios like local delivery robots, enhancing communication for skill sharing.
Fig. 5.4.4-1 (in 3GPP TR 22.847) presents examples of benefit of using skillset sharing where the skillset is in the form of multimodality information and/or control. These scenarios are suitable for a robot group operation scenario using ProSe and Uu interface (e.g., a group of tele-operated robots, such as for hazardous control, mining (both underground and on-surface consolidated operations).
UC - Haptic feedback for a personal exclusion zone in dangerous remote environments
The advent of 5G networks has enabled tele-operations in industries like mining. To ensure safety, wearables like belts and shoe soles are used to improve alarm reliability, especially in situations where traditional alarms might be missed due to protective gear. Haptic feedback, detected faster by the brain than audio or visual cues, is integrated into wearables for quicker alerts in hazardous environments. A multi-modal approach combines haptic, audio, and visual signals for effective emergency response.
Surveillance cameras, drones, and wearables monitor environments, with data sent to a control unit for hazard prediction. Personal exclusion zones, restricting access, are defined and navigation is adjusted based on worker data. In mining, a hazard triggers a multi-modal alarm system, combining haptic, audio, and visual alerts, as well as surveillance and worker feedback, to guide workers away from danger.
This use case has identified the following PRs for single-hop cases:
[PR. 5.5.6-1] The 5G network shall support a mechanism to allow an authorized 3rd party to provide QoS policy for flows of multiple UEs associated with an application. The policy may contain e.g. the expected 5GS handling and the associated triggering event.
[PR. 5.5.6-2] The 5G system shall support a mechanism to apply QoS policy for flows of multiple UEs associated with an application received from an authorized 3rd party.
UC - Virtual Factory:
A factory utilizes a 5G network to synchronize its robot's motion data and monitor video. The robot's movements are collected through a dataflow (say, dataflow 1), while a monitor captures real-time motion via another dataflow (say, dataflow 2). The network categorizes these flows as instructed. Dataflow 1 generates VR video on a VR server based on motion data, while dataflow 2 is directly sent to a remote screen. At the remote site, VR glasses receive VR video, and a monitor displays the actual robot motion. To minimize delay, dataflow 2 is briefly held by the network as motion data is processed into VR video. This setup ensures seamless coordination between robot motion and video monitoring, facilitated by 5G technology.
This use case has identified the following PRs for single-hop cases:
[PR 5.8.6-1] 5G system shall be able to support the interaction with applications on UEs or data flows grouping information within one tactile and multi-modal communication service.
[PR 5.8.6-2] The 5G system shall support a means to apply 3rd party provided policy(ies) for flows associated with an application. The policy may contain e.g. the set of UEs and data flows, the expected QoS handling and associated triggering events, other coordination information.
NOTE 2: The policy can be used by a 3rd party application for coordination of the transmission of multiple UEs’ flows (e.g., haptic, audio and video) of a multi-modal communication session. |
3239937b55fdc406849fa93870986364 | 22.916 | 6.1.2 Challenges and potential gaps | The PRs referenced above are limited to a single-hop scenario. To extend to a multi-hop scenario, the following can be further considered with other ongoing or recently completed studies if applicable.
[CPG-6.1.2-001] 5G system is expected to be evolved so that it can support some or all of the referenced PRs in both direct network connections and indirect network connections.
NOTE: The suitable number of hops that are required to support depends on the types and characteristics of robot applications. |
3239937b55fdc406849fa93870986364 | 22.916 | 6.2 ISAC aspects related to robot applications | |
3239937b55fdc406849fa93870986364 | 22.916 | 6.2.1 General description | Autonomous Mobile Robots (AMRs) are revolutionizing logistics operations in industries such as manufacturing and warehousing. Unlike traditional Automated Guided Vehicle (AGV) systems, AMRs possess the intelligence to navigate and perform tasks autonomously, offering unparalleled flexibility. However, a significant challenge for AMRs lies in acquiring accurate and continuous sensing data as they move through complex environments [29,30]. Factors like unexpected obstacles or sudden appearances of people and machines can compromise their safety.
To address this challenge, 5G base stations are strategically deployed in factories. These stations serve a dual purpose: not only do they provide essential communication capabilities for factory equipment, but they also act as sensing nodes. By transmitting sensing signals and receiving reflected signals, these base stations capture real-time 3GPP sensing data. This data is then processed and analyzed by the core network, generating valuable insights into the AMRs' surroundings.
Crucially, these sensing results can be shared with trusted third-party platforms, empowering AMRs with a comprehensive understanding of their environment. This enhanced sensing capability allows AMRs to adapt their routes dynamically, ensuring both efficiency and safety. Moreover, in scenarios where obstacles obstruct radio signals or AMR paths traverse indoor and outdoor spaces, collaboration between multiple base stations further improves sensing accuracy and service continuity.
[30] presents a few use cases addressing sensing issues related to robot operation. Examples include the following with some KPIs as shown in, e.g., Table 5.23.6-1 and Table 5.32.6-1:
[PR 5.23.6-1] The 5G system shall be able to provide the continuity of sensing service for a specific target object, across indoor and outdoor.
[PR 5.23.6-2] The 5G system shall be able to provide a secure mechanism to ensure sensing result data privacy within the sensing service area.
[PR 5.32.6-1] Based on operator’s policy, the 5G system may provide a mechanism for a trusted third party to provide sensing assistance information about a sensing target. |
3239937b55fdc406849fa93870986364 | 22.916 | 6.2.2 Challenges and potential gaps | While the PRs referenced above have addressed potential new requirements, such as on the continuity of sensing services both in indoor and outdoor settings, data privacy and network exposure, it is still worthwhile to consider the support of scalable and efficient use of communication resources needed for stable operation of multiple service robots especially when a large number of service robots are present. |
3239937b55fdc406849fa93870986364 | 22.916 | 6.3 Metaverse aspects related to robot applications | |
3239937b55fdc406849fa93870986364 | 22.916 | 6.3.1 General description | The Technical Report on Localized Mobile Metaverse Services [31] addressed several use cases related to robot applications. The following includes some examples.
1) Metaverse use case on Spatial Mapping and Localization (Clause 5.5, [31])
In the context of robot operations, spatial mapping involves constructing or updating a map of an unknown location, while localization tracks an object to identify its location and orientation over time. For the localized mobile Metaverse use case (e.g., clause 5.5, [31]), communication technology support is vital. Spatial Mapping Service creates and maintains a 3D map of indoor or outdoor environments, enabling the identification of stationary and moving objects. This spatial map is utilized by Spatial Localization Service, allowing for accurate positioning and orientation of users.
Spatial mapping gathers sensing data to create a detailed 3D map, integrating information from various sources like sensors and architectural specifications. Localization, based on this spatial map, identifies users' positions and viewing angles in 3D space. Examples of spatial mapping applications include government projects mapping entire cities, navigation service providers mapping roads, and customers mapping indoor spaces. To achieve this, vehicles or robots equipped with multiple cameras and LiDAR devices capture images and depth information. This data is then processed, enhancing location accuracy and enabling various applications like visual positioning and Metaverse content management. The information is communicated through uplink sensor data, enabling precise localization and enriching the spatial internet experience.
The following includes some example of potential new requirements:
[PR 5.5.6.1-1] Subject to operator policy and relevant regional and national regulation, the 5G system shall support mechanisms for an authorized UE to provide sensing data that can be used to produce or modify a spatial map.
[PR 5.5.6.1-2] Subject to operator policy, user consent and relevant regional and national regulation, the 5G system shall support mechanisms to receive and process sensing data to produce or modify a spatial map.
[PR 5.5.6.1-3] Subject to operator policy and relevant regional and national regulation, the 5G system shall support mechanisms to expose a spatial map or derived localization information from that map to authorized third parties.
NOTE 1: Some KPI’s required to fulfil e.g., [PR 5.5.6.1-2] is not specified in this particular use case.
2) Metaverse use case on Immersive tele-operated driving (Clause 5.20, [31])
The use case involves operating vehicles, lifting devices, or machines/robots in hazardous industrial environments, where manual operation poses risks due to exposure to dangerous materials, extreme conditions, or radioactivity. While Automated Guided Vehicles (AGVs) exist, the proposal suggests leveraging 5G technology to create a system allowing remote users to control these devices. This control occurs through an immersive cockpit displayed on a virtual reality head-mounted display and haptic gloves. The cockpit integrates data from the digital twin of the operating environment, including information from factory sensors and the surroundings. This approach enhances user safety and operational accuracy by merging data from the digital twin, enabling remote control in hazardous settings.
This use case includes some requirements that are needed to support immersive teleoperations (or digital twins) within a service area up to 10km (radius).
[PR 5.20.6-1] The 5G system shall be able to provide a means to associate data flows related to one or multiple UEs with a single digital twin maintained by the mobile metaverse service.
[PR 5.20.6-2] The 5G system shall be able to provide a means to support data flows from one or multiple UEs to update a digital twin maintained by the mobile metaverse service. |
3239937b55fdc406849fa93870986364 | 22.916 | 6.3.2 Challenges and potential gaps | None. |
3239937b55fdc406849fa93870986364 | 22.916 | 6.4 High-level communication scenarios | Robotic Application Enablement Communication (in short Robotic Communication) is a technology that enables a group of robots (or a robot) to communicate with various entities, including other robots (or robotic applications), humans (e.g., residents, workers, pedestrians in indoor/ outdoor structured or unstructured environments), infrastructure, and networks. Here are several scenarios for Robotic Communication.
NOTE 1: A robot with communication functionality is a physical entity that can act as an ordinary UE, a UE acting as a relay for other UE (e.g., UE Relay) that is fixed or mobile depending on scenarios.
NOTE 2: In the following scenarios, the communication direction is assumed to be unidirectional or bidirectional.
NOTE 3: In the following scenarios, the communication path is assumed to be a single hop or multi-hop. In a multi-hop scenario, a combination of different scenarios are possible when applicable, e.g., R2R and R2C.
NOTE 4: In some of the following scenarios, the counterpart of a robot (or a group of robots) in communication path can be an IoT device, an ordinary UE, a UE acting as a relay, and so on.
1. Robot-to-Robot (R2R) Communication:
- Collision Avoidance: Robots can exchange information about their speed, direction, and position to avoid collisions, especially in intersections or blind spots.
- Traffic Congestion Management: R2R communication allows robots to share real-time traffic information, helping them choose less congested routes. Both road traffic (e.g., in public roads) and robot traffic are considered.
- Examples:
• A group of robots for public safety purposes.
• Indoor and outdoor delivery robots.
• Internet of aerial robots (or Internet of drones).
• A group of robots using machine-type media communications (e.g., media between robots).
• Robots maneuvering in unstructured environments or in structured environments such as public roads, sidewalks.
• In the United States, currently, robot operations lack national regulation and are governed by individual states. Virginia set a precedent in 2017 by regulating robot operation, allowing them to move on sidewalks and crosswalks at speeds not exceeding 10 mph (ca. 16km/h). If these paths are unavailable, robots are permitted to operate on the roadside with a speed limit of 25 mph (ca. 40km/h). In 2020, Pennsylvania enacted regulations allowing robots weighing up to 550 pounds (ca. 250kg) without payload [29].
2. Robot-to-Infrastructure (R2I) Communication:
- Traffic Signal Coordination: Robots can receive data from traffic signals to optimize their speed and reduce unnecessary stops, improving traffic flow.
- Roadside Assistance: Remote drivers can receive alerts and assistance information, such as nearby charging stations or emergency services, from roadside infrastructure.
NOTE 5: For example, in some States of the United States where robots are legally considered as road vehicles, such robots are assumed to be capable of supporting communication features relevant to Cellular V2X (e.g., LTE-V2X, NR-based V2X).
- Examples:
• Indoor and outdoor delivery robots.
• Internet of aerial robots (or Internet of drones).
• Car valet robot at parking lots
• A group of robots using machine-type media communications (e.g., media from a robot to infrastructure).
• A group of aerial roots (e.g., UAVs) performing geo-surface sensing and/or environmental monitoring.
3. Robot-to-Pedestrian (R2P) Communication:
- Pedestrian/Human Safety: Robots can detect pedestrians/human equipped with or without communication devices, issuing warnings to both robot operators and pedestrians/human to prevent accidents or collision.
- Crosswalk and human-zone Safety: Pedestrians/humans can receive alerts on their devices (UE’s, tethered/untethered devices) about approaching robots, ensuring timely safety-related alert.
- Examples:
• Surveillance robot (e.g., in CCRC)
• Disinfection robot (e.g., in hospitals, hotels)
• Outdoor delivery robots allowed to use public roads some of which are shared by humans.
• Personalized assistive robots: personalized digital experience (e.g., VR/XR/MR assisted shopping, gaming). Both physical robots and virtual bots are considered where virtual bots are assumed to be linked to authorized multi-sensory input (e.g., acoustic signals, voice, audio, or visual input such as facial expressions, gesture, and/or gait) and display mechanisms that are security and privacy ensured.
4. Robot-to-Network (R2N) Communication:
- Robot/road Traffic Management: Traffic authorities can collect real-time data from robots to monitor traffic patterns, analyze congestion, and adjust traffic signals for optimal flow. See NOTE 5 for outdoor delivery robots that are considered as a regular vehicle depending on local regulatory requirements.
- Emergency Response: Robots can transmit information about accidents or road hazards directly to emergency services, enabling faster response times.
- Timely Response: Robots that are in inter-continental real-time trading environments (e.g., trans-Atlantic financial market), realistic mixed-reality gaming and entertainment, and so on.
NOTE 6: the term `Network’ can include 3GPP NTN and TN. Different from R2I scenarios, R2N scenarios include communication with a server. Also, refer to V2I (clauses 4, 5.6, 5.7, and 5.8 in TR 22.185 and V2N (clauses 5.15, 5.26, and 5.27 of TR 22.185).
5. Robot-to-Cloud (R2C) Communication:
NOTE 7: This communication scenario describes the use of edge or cloud for, e.g., AI/ML-related computation that are commonly necessary to support intelligent operations of a robot or a group of robots. This scenario can be overlaid with other scenarios such as R2N or R2I.
- Fleet Management: Fleet operators can track robots, monitor their health, and optimize routes, leading to efficient operations and reduced maintenance expenses.
- Over-the-Air (OTA) Updates: Robot manufacturers can remotely deploy software updates and patches to improve robot performance and security.
- Examples:
• A group of robots in healthcare, delivery, and/or manufacturing environments.
• Tele-operated robots with haptic feedback/control.
6. Robot-to-Grid (R2G) Communication:
- Smart Charging: Electric robots can communicate with the grid to schedule charging during off-peak hours, optimizing energy usage and reducing costs for both consumers and utilities.
- Grid Stability: Electric robots can provide feedback to the grid about available battery capacity, enabling the grid to balance demand and supply effectively.
- Examples:
• A group of robots in smart city settings, in hazardous control environments.
7. Robot-to-Home (R2H) Communication:
- Home Automation: Robots can communicate with smart home devices, allowing users to control home appliances, lighting, and security systems remotely from their robots.
- Energy Management: Electric robots can supply power back to homes during peak demand periods, reducing the load on the grid and lowering household electricity expenses.
- Examples:
• A group of robots in smart home that can provide timely and accurate information for the smart home server for high-quality decision-making. |
3239937b55fdc406849fa93870986364 | 22.916 | 7 Conclusions and recommendations | The present document includes the outcome of Study on Network of Service Robots with Ambient Intelligence. This includes various use cases with challenges and potential gaps and other consideration points related to efficient communications service and cooperative operation for a group of service robots.It is recommended that future work can consider the present document for enhancements of communications support relevant for the network of service robots. Annex A: Levels of Fusion A.1 Levels of Fusion A.1.0 Description The use of “levels of fusion” [14,15,16]is expected to help the United Nations Sustainability Development Goals (SDGs) in several aspects. Providing that the 6G technology enablers are designed in resource-efficient ways for various types of resources (e.g., radio resources, network resources, material, such as battery related), such considerations can also help provide affordable 6G services in the society, especially when certain groups of residents, patients, public-safety officers, or underrepresented need the communication services the most at a critical point in time in their everyday living. A.1.1 A Six-Level Approach This approach is based on U.S. Department of Defense Joint Directors of Laboratories (JDL) Data Fusion Subgroup. Each of the following six levels of fusion progressively adds meaning at higher levels of abstraction and involves more analysis (Reference: NIST [14]): Level 0 - organize. This is the initial processing accomplished at or near the sensor that organizes the collected data into a usable form for the system or person who will receive it. Level 1 - identify/correlate. This level takes new input and normalizes its data; correlates it into an existing entity database, and updates that database. Level 1 Fusion tells you what is there and can result in actionable information. Level 2 - aggregate/resolve. This level aggregates the individual entities or elements, analyzes those aggregations, and resolves conflicts. This level captures or derives events or actions from the information and interprets them in context with other information. Level 2 Fusion tells you how they are working together and what they are doing. Level 3 - interpret/determine/predict. Interprets enemy events and actions, determines enemy objectives and how enemy elements operate, and predicts enemy future actions and their effects on friendly forces. This is a threat refinement process that projects current situations (friendly and enemy) into the future. Level 3 Fusion tells you what it means and how it affects your plans. Level 4 - assess. This level consists of assessing the entire process and related activities to improve the timeliness, relevance, and accuracy of information and/or intelligence. It reviews the performance of sensors and collectors, as well as analysts, information management systems, and staffs involved in the fusion process. This process tells you what you need to do to improve the products from Fusion Levels 0-3. Level 5 - visualize. This process connects the user to the rest of the fusion process so that the user can visualize the fusion products and generate feedback/control to enhance/improve these products. A.1.2 A Three-Level Approach A three-level approach was proposed in [15] as follows. In terms of data processing, multi-modal fusion is typically implemented at three different levels of abstractions: Sensor level: Fusion module processes raw data captured from different sources. If multiple sensors are measuring the same physical aspect, a single feature vector to represent the phenomena under analysis can be directly combined. However, if sensor data represents different phenomena, the data fusion should be completed in a later stage. Feature level: Sensor data is represented by feature vectors. Features are extracted from different sources independently. The fusion module then combines the feature vectors from each module into a single fused feature vector. Decision level: Features are extracted from each source independently and passed to a corresponding classification module to make their own decision. The Fusion module then consolidates these decisions into one final classification decision. Hybrid models: These models can include more than one level of Fusion. For example, features from two modalities can be combined together to construct one feature set for classification model, the decisions of this classification model are then combined with decisions from a second classification model that is trained using features from a third modality. Fig. A.1.2: A three-level approach for data fusion (source: [15] IEEE). Annex B: Example Scenario B.1 Example Scenario for robot applications to adjust the accuracy level of clock synchronization provided by 5G system Energy-efficient robots collaborate to jointly work on certain task in an area of interest such as cleaning, disinfection, and agriculture. They adapt actions based on environmental conditions, emphasizing accuracy while optimizing computing and communication resources. The application server is aware that a higher accuracy level of clock synchronization is reqired in a more complex enviroment of interest (e.g. Area 1 in Figure B.1-1). The application requests the moniroting of the accuracy level for clock synchninization to the 5G system, and the 5G system can perform the monitoring based on the application request and report the measured results. In addition, the 5G system can inform the application server of its accuracy checking capability. The application server can request the 5G system to adjust the accuracy level to in order to maintain the proper accuracy level needed for robot applications in the particular area. Figure B.1-1: Example scenario adjusting clock synchronization accuracy level Table 5.6.2-1 of 3GPP TS 22.104 [2] presents various scenarios that require different accuracy levels of clock synchronization. In practice, there are occasions in which robots need adaptation to changes on the need of accuracy level of clock synchronization (e.g., due to changes in robot task or in the environment) or 5G system needs to inform of its change on its capability on the accuracy level to robots. Annex C: Change history Change history Date Meeting TDoc CR Rev Cat Subject/Comment New version 2022-08 SA1#99-e S1-222282 TR skeleton, scope 0.1.0 2022-11 SA1#100 S1-223575 S1-223724 Online cooperative high-resolution 3D map building, Real-time cooperative safety protection 0.2.0 2023-02 SA1#101 S1-230352 S1-230354 S1-230355 S1-230356 S1-230382 S1-230383 S1-230398 Terminology n SOBOT Patrol robots in CCRC Real-time conversational robot Multimodal Sensors Fusion in Multi-Robot Scenarios Annex: Fusion Levels for Robotic Applications Machine-type media communication Update on cooperative safety protection 0.3.0 2023-05 SA1#102 S1-231535 S1-231548 S1-231549 S1-231802 S1-231720 S1-231547 Editorial Update on 5.1 Update on 5.2 Update on 5.3 MEC for Efficient Management of Geo-surface Sensing Data Using a Group of Aerial Robots Smart community with service robots 0.4.0 2023-08 SA1#103 S1-232518 Inclusion of: S1-232089; S1-232519; S1-232506; S1-232520; S1-232521; S1-232516 0.5.0 2023-11 SA1#104 S1-233260 Inclusion of: S1-233356; S1-233363; S1-233358; S1-233354; S1-233355; S1-233362; S1-233192; S1-233366 0.6.0 2023-12 SA#102 SP-231399 MCC Clean-up for presentation to one-step approval 1.0.0 2023-12 SA#102 - Approved by SA#102 19.0.0 |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 1 Scope | The present document analyses FRMCS Use cases, system principles of FRMCS and Interworking between GSM-R and FRMCS in order to derive potential requirements. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 2 References | The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
- References are either specific (identified by date of publication, edition number, version number, etc.) or non‑specific.
- For a specific reference, subsequent revisions do not apply.
- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
[1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
[2] 3GPP TS 36.213 V14.0.0, Technical Specification Group Radio Access Network; Evolved Universal Terrestrial radio Access (E-UTRA); Physical layer procedures, 2016.
[3] 3GPP TS 23.179 V13.3.0, Technical Specification Group Services and System Aspects; Functional architecture and information flows to support mission critical communication services; Stage 2. 2016.
[4] TTA TTAK.KO-06.0437, LTE Based Railway Communication System Requirements (Conventional and High Speed Railway), Dec. 2016.
[5] TTA TTAK.KO-06.0370, User Requirements for LTE-Based Railway Communication System, Oct. 2014.
[6] TTA TTAK KO-06.0-369, Functional Requirements for LTE-Based Communication System, Oct. 2014.
[7] Y.-S. Song, J. Kim, S. W. Choi, and Y.-K. Kim, “Long term evolution for wireless railway communications: Testbed deployment and performance evaluation,” IEEE Comm. Mag., Feb. 2016.
[8] J. Kim, S. W. Choi, Y.-S. Song, and Y.-K. Kim, “Automatic train control over LTE: Design and performance evaluation,” IEEE Comm. Mag., Oct. 2015.
[9] UNISIG Subset-041 ERTMS/ETCS Performance Requirements for Interoperability
[10] UIC FU-7100: “FRMCS User Requirements Specification”.
[11] UIC MG-7900: “FRMCS Use Cases”.
[12] UIC CODE 950: “EIRENE Functional Requirements Specification (FRS)”.
[13] UIC CODE 951: “EIRENE System Requirements Specification (SRS)”.
[14] 3GPP TR 22.990: “Study on off-network for rail”. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 3 Definitions, and abbreviations | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 3.1 Definitions | For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1].
Automatic Train Operation (ATO): Automatic Train Operation applications are responsible for acceleration to the permitted speed, speed reduction where necessary due to speed restrictions and stop at designated stations in the correct location.
Automatic Train Protection (ATP): Automatic Train Protection applications are responsible for giving Limit of Movement Authority to a train based on the train’s current speed, its braking capability and the distance it can go before it must stop.
Balise: An electronic beacon or transponder placed between the rails of a railway as part of an automatic train protection or operation (ATP/ATO) system.
Business communication applications: communication applications that support the railway business operation in general, such as wireless internet, etc.
Controller (Train Controller): A Ground FRMCS User provided with special capabilities by the FRMCS System.
Driver (Train Driver): A Mobile FRMCS User provided with special capabilities by the FRMCS System.
External System(s): A general category of stationary FRMCS Users. For example, External Systems could be systems monitoring for trains passing a red light to initiate a railway emergency call.
FRMCS Application: The application on a 3GPP UE offering railway specific communication services to the FRMCS User by making use of the communication capabilities offered by the 3GPP UE and the 3GPP network.
FRMCS Equipment Identity: The identity by which a FRMCS equipment can be addressed.
FRMCS Equipment Type: Indicates the purpose the FRMCS equipment is being used for, FRMCS equipment of different equipment types do have different capabilities.
FRMCS Equipment: The FRMCS Equipment consists of a 3GPP UE and a FRMCS Application residing on it. It may be combined with legacy railway communication equipment (e.g. GSM-R or TRS)
FRMCS Functional Identity: The identity related to a user or related to the equipment, as specified in 9.3 "Role management and presence" indicating its special Role (e.g. as Driver of a specific train, usually a train number) can be addressed.
FRMCS Network: this is a sub-part of the FRMCS System.
FRMCS Roaming: The ability for a FRMCS User to make use of FRMCS Applications in a Visited (FRMCS) Network.
FRMCS System: The system providing railway specific communication constituted of the FRMCS Equipment, the 3GPP transport and the application servers in the network. Legacy networks are not included in the FRMCS System.
FRMCS User Identity: The identity by which a FRMCS User can be addressed.
FRMCS User: A human user or a machine making use of the railway specific communication. FRMCS Users can be connected via 3GPP RAT, wired connectivity or other radio technology
Ground FRMCS User: A general category of FRMCS Users that are predominantly stationary. Mostly they are connected via wired connectivity but may be using also wireless in certain conditions.
Home FRMCS Network: The Home FRMCS Network is the network in which the FRMCS User is engaged in a subscription.
Mobile FRMCS User: A general category of FRMCS Users that are mobile. Thus, they are connected via wireless connectivity all the time.
Mobile Intelligent Assistant: 5G enabled robot with autonomous movements and artificial intelligence to support passengers in the Railway Smart Station.
Off-Network communication: direct communication between FRMCS Users in proximity.
On-Network communication: indirect communication between FRMCS Users connected to FRMCS Network(s).
Performance communication applications: applications that help to improve the performance of the railway operation, such as train departure, telemetry, etc.
Radio Block Centre (RBC): A train sends its position and speed information periodically to the RBC. The RBC uses the received information to decide movement authority of the train.
Rail Infrastructure Manager: A company that owns or manages rail infrastructure; within this document the Rail Infrastructure Manager owns, administrates and operates the FRMCS Network.
Railway Smart Station: a train station where the 5G-based services such as IoT and AI, are used for providing assisting railway services.
Railways Undertaking: A company that offers train freight or passenger transportation services, making use of FRMCS network for their operational communication needs that is operated by a Rail Infrastructure Manager.
Role (Functional Role): The function a FRMCS User or a FRMCS Equipment is currently performing. Examples of Roles are Driver, Controller or shunting staff, etc. This is indicated by the FRMCS Functional Identity.
Shunting: manoeuvring trains in order to change their location or composition.
Trackside staff: Staff working as trackside maintenance and/or shunting members
Trainborne equipment: FRMCS Equipment which is physically embedded in train
Visited (FRMCS) Network: A Visited (FRMCS) Network can be either another FRMCS Network than the Home FRMCS Network, or a Public Land Mobile Network (PLMN).
Zone: A 2-dimensional region of a pre-determined size.
Zone resolution: The pre-determined size of the given zone. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 3.2 Abbreviations | For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply.
An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1].
ATO Automatic Train Operation
ATP Automatic Train Protection
AVC Assured Voice Communication
DoS Denial of Service
GNSS Global Navigation Satellite System
LMR Land Mobile Radio
MACN Multi Access Core Network
NA Naming Authority
OATP On-board Automatic Train Protection
PSAP Public Safety Answering Point
RBC Radio Block Centre
REC Railway Emergency Communication
TRS Trunked Radio System
WATP Wayside Automatic Train Protection |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 4 Overview | The present document is an 800 series Technical Report (TR) written by 3GPP TSG SA WG1 (SA1). Such a TR is not normative, i.e. cannot be used for implementation directly and cannot be referred to by other 3GPP specifications. It was primarily written by SA1 to summarise the high-level communication needs of the railway community and to identify the corresponding requirements, which, in another step have been introduced into normative Technical Specifications (TS) of 3GPP.
An 800 series TR will not be updated when in the process of introduction of the requirements to TS changes are made to those requirements, i.e. the text of the requirements listed here in this TR will not be aligned with the requirements in the TS. Due to the fact that most of the requirements identified in this document were introduced in already existing Mission Critical Communication (MCX) TS, an alignment with the MCX terminology and functionality was made resulting in most of the requirements in here being reworded in the TS. Also, TS requirements changes due to future work affecting requirements stemming from this TR will not result in updates of this TR.
However, the columns “Comments” of the requirements tables listed below were updated to indicate the disposition of the requirement in the TS and most of the time summarising deviations and decisions taken when introducing those requirement into normative TS. By following these references into the normative TS the functionality provided by 3GPP for railway communication can be derived by the reader.
FRMCS will adapt 3GPP transport to provide communication to railway users. It eventually will resemble GSM-R and will additionally provide communication capabilities beyond what GSM-R has been able to. It will provide higher data rates, lower data latencies, multimedia communication, and improved communication reliability. FRMCS considers end-to-end use cases and also provides requirements that might or might not be in scope of 3GPP existing specifications. To facilitate smooth migration from legacy communication systems (e.g. GSM) to FRMCS, interworking requirements between legacy communication systems and FRMCS are provided.
FRMCS Equipment shall connect to application domain through 3GPP radio access or other access. It provides emergency group communication, low latency and high reliable data and video service in high speed train environment. Amongst others it has the following important features:
- Prioritized emergency group communication, train control data and video service
- Seamless connectivity in high speed railway moving environments
- Low latency and high reliable data and video service
- Real time train monitoring and management for safe train operation
- Reliable location tracking including in tunnel tracking
- Legacy railway communication interworking to GSM-R system
Figure 4-1: High-level relation of FRMCS and legacy systems
Basically, railway communication services [5] can be categorized into
- Train control services
- Maintenance services
- Railway specific services (such as Railway Emergency Call, functional addressing, and location-based addressing)
- Other services (providing train crews or train Drivers with information of train operation and interworking with the existing railway communication systems)
This study categorizes all the use cases by considering inherent characteristics of railway applications. Specifically, the following categories of use cases are considered.
- Basic functionality
- Critical communication applications
- Performance communication applications
- Business communication applications
- Critical support applications
- Performance support applications
- Business support applications
- FRMCS System principles
The categories can be depicted conceptually as follows:
Figure 4-2: Grouping of FRMCS Applications |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 5 Basic functionality use cases | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 5.1 Introduction | The basic functionality use cases describe the behaviour of the FRMCS Equipment when powered up and down. For power up it takes the already powered up 3GPP UE as starting point conversely the same applies for power down. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 5.2 Device power on and shut-down related use cases | In this chapter the use cases related to the function Initialisation and shut-down are defined.
- Power on the UE
- Access to the FRMCS System
- Controlled power down UE
- Uncontrolled power down UE
Note: Annex A provides examples of Role management (such as functional identities or FRMCS Equipment Identities) in the railway environment. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 5.3 Use case: Power on the UE | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 5.3.1 Description | This use case provides the user with a powered-on UE. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 5.3.2 Pre-conditions | The UE is switched off.
Note: In this use case and all the following it is assumed the UE contains a FRMCS Application, thus an UE with FRMCS Application is further referred to as FRMCS Equipment. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 5.3.3 Service flows | Successful self-test
The user switches on the UE.
The FRMCS Application performs a self-test. If the test is successful, the user is informed about this.
Unsuccessful self-test
The user switches on the UE.
The FRMCS Application performs a self-test. If the test is not successful, the user is informed about this. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 5.3.4 Post-conditions | The UE is switched on and attached to a 3GPP network following normal 3GPP defined network selection procedures but not logged into any FRMCS System. The user is informed about the results of the self-test. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 5.3.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-5.3-001]
The FRMCS Application shall be capable to perform a self-test and inform the user about the results.
A
N/A
Implementation requirement |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 5.4 Use case: Access to the FRMCS System to activate the FRMCS Equipment | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 5.4.1 Description | This use case describes how the FRMCS Equipment registers to the FRMCS System. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 5.4.2 Pre-conditions | The UE is powered on and attached to a 3GPP network but is not registered to the FRMCS System.
The UE has a subscriber identity. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 5.4.3 Service flows | The FRMCS Equipment selects an applicable FRMCS System and logs on to it.
The FRMCS Equipment is initialised by the FRMCS System according to its type. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 5.4.4 Post-conditions | The FRMCS Equipment capabilities are activated.
The FRMCS Application(s) are running on the device.
The FRMCS Equipment is logged in to the FRMCS System |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 5.4.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-5.4-001]
When a FRMCS Equipment registers to the FRMCS System, the FRMCS Equipment capabilities are activated and the FRMCS Equipment shall be reachable by its FRMCS Equipment Identity.
A
N/A
Implementation requirement |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 5.5 Use case: Controlled power down of UE | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 5.5.1 Description | The UE is powered down. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 5.5.2 Pre-conditions | The UE is switched on and the FRMCS Equipment is registered to the FRMCS System. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 5.5.3 Service flows | The user / FRMCS User initiates power-down of the UE.
If logged in, a FRMCS User is logged-out from the FRMCS System.
The FRMCS Equipment will deregister all identities which are active.
The FRMCS Equipment de-registers from the FRMCS System.
The UE is switched off. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 5.5.4 Post-conditions | The UE is de-registered from the FRMCS System and switched off. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 5.5.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-5.5-001]
When the UE is about to be powered down, a FRMCS User logged into the FRMCS System shall be logged off first.
A
N/A
Implementation requirement
[R-5.5-002]
By logging off the functional Role of a FRMCS User shall be deregistered from the FRMCS System.
A
N/A
Implementation requirement
[R-5.5-003]
After logging off the FRMCS User, the FRMCS Equipment capabilities shall be deactivated and the FRMCS Equipment shall be removed from the FRMCS System.
A
N/A
Implementation requirement |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 5.6 Use case: Uncontrolled power down UE | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 5.6.1 Description | This use case describes the case when the UE is powered down in an uncontrolled way e.g. due to battery failure. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 5.6.2 Pre-conditions | The UE is switched on, the FRMCS Equipment is registered to the FRMCS System. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 5.6.3 Service flows | The UE loses power probably without being able to notify the FRMCS System.
The UE is without power.
The FRMCS System will deregister all identities associated with the FRMCS Equipment. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 5.6.4 Post-conditions | The UE is de-registered from the FRMCS System and switched off. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 5.6.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-5.6-001]
When the UE is uncontrolled powered down, a FRMCS User logged into the FRMCS System shall be logged out from the FRMCS System.
A
N/A
Implementation requirement
[R-5.6-002]
By logging out the functional Role of the FRMCS User shall be deregistered from the FRMCS System.
A
N/A
Implementation requirement |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6 Critical communication applications related use cases | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.1 Introduction | Critical communications applications are essential for train movements, safety, shunting, presence, trackside maintenance, legal aspects such as emergency communications, etc. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.2 Multi-train voice communication for Drivers and Ground FRMCS User(s) | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.2.1 Introduction | In this chapter the use cases related to the function of Multi-train voice communication from the Drivers and/or a Ground FRMCS User towards the Driver and/or Ground FRMCS Users are defined. Ground FRMCS Users may include Controllers. The following use cases are defined:
• Initiation of Multi-train voice communication for Drivers and Ground FRMCS User(s) communication
• Join a Multi-train voice communication for Drivers and Ground FRMCS User(s) communication
• Termination of Multi-train voice communication for Drivers and Ground FRMCS User(s) communication
• Interworking GSM-R and FRMCS for Multi-train voice communication for Drivers and Ground FRMCS User(s) communication |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.2.2 Use case: Initiation of Multi-train voice communication for Drivers and Ground FRMCS User(s) communication | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.2.2.1 Description | A Driver and/or a Ground FRMCS User is able to initiate a voice communication to other Drivers and/or Ground FRMCS Users. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.2.2.2 Pre-conditions | The Driver and the Ground FRMCS User are authorised to initiate the communication. This is managed by the authorisation of communication application.
The authorisation application authorises the Driver and the Ground FRMCS User to use the Multi-train voice communication for Drivers and Ground FRMCS User(s) |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.2.2.3 Service flows | The Driver and/or Ground FRMCS User initiates the voice communication to the (other) Driver(s) and/or Ground FRMCS Users. The priority of the communication is managed by the prioritisation application. The voice communication has the priority which matches the application category of CRITICAL VOICE (see 12.10) within the FRMCS System.
The FRMCS System determines the Driver(s) and the Ground FRMCS User(s) to be included in the communication, based on:
• location information of all users provided by the locations services application, and/or
• functional identity of all users provided by the Role management and presence application.
• System configuration on which Ground FRMCS User is responsible for which part of the track/station/etc.
The FRMCS System establishes the voice communication within a setup time specified as NORMAL (see 12.10). The information from the Role management and presence application is used to present the identities for both Driver(s) and Ground FRMCS User(s). The initiating Driver is indicated to the Ground FRMCS User(s). Also the location of the Driver(s) in the voice communication is presented to the Ground FRMCS User(s) which is retrieved from the location services application.
If the Driver and/or Ground FRMCS User is connected to more than one Drivers and/or Ground FRMCS Users, the multiuser talker control application is used.
The precedence of the incoming voice communication at the Driver and the Ground FRMCS User is managed by the prioritisation application.
The voice communication is recorded by the FRMCS System voice recording and access application. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.2.2.4 Post-conditions | The Driver and/or the Ground FRMCS User is connected to requested Driver(s) and/or Ground FRMCS User (s). |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.2.2.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-6.2.2-001]
For a Multi-train voice communication for Drivers and Ground FRMCS User(s), the FRMCS Users shall be able to initiate the voice communication to FRMCS Users in trains or on ground.
A
22.280
22.179
TS 22.179 Floor Control clause 6.2.3.2 Req #1,
TS 22.280 clause 5.1 Req # 2
[R-6.2.2-002]
For a Multi-train voice communication for Drivers and Ground FRMCS User(s) the application layer priority of the communication shall be managed by the prioritisation application.
A
22.280
6.8.7 Application layer priority, 7.6 MCX Service priority requirements
[R-6.2.2-003]
For a Multi-train voice communication for Drivers and Ground FRMCS User(s), the FRMCS System shall be able to determine the FRMCS User(s) to be included in the voice communication, based, amongst others, on the following criteria:
location information, speed and direction of travel provided by the locations services application, and/or functional identity provided by the Role management and presence application.
System configuration on which Ground FRMCS Useris responsible for which part of the track/station/etc.
A
22.280
6.4.9 req #6, 5.17 req # 3, 6.1 req #5, R-6.1.005, R6.6.5.2-00X
6.6.4.1.1, 6.6.4.1.2, 6.6.4.2-002a,002b
5.9a-006, 5.9a-008a
[R-6.2.2-004]
For a Multi-train voice communication for Drivers and Ground FRMCS User(s) the FRMCS System shall be able to add or remove FRMCS User from the communication once criteria are met or no more met, e.g. by a FRMCS User entering or leaving an area
A
22.280
6.4.9 req #6, 5.17 req # 3, 6.1 req #5, R-6.1.005, R6.6.5.2-00X
6.6.4.1.1, 6.6.4.1.2, 6.6.4.2-002a,002b
5.9a-006, 5.9a-008a
[R-6.2.2-005]
For a Multi-train voice communication for Drivers and Ground FRMCS User(s), the FRMCS System shall establish the communication within a setup time specified as NORMAL (see 12.10).
A/T
N/A
See section 12.10 below
[R-6.2.2-006]
The FRMCS System shall be able to mutually present the identities of all communication partners involved in a Multi-train voice communication for Drivers and Ground FRMCS User(s).
A
22.280
5.3 req #2, 5.7 req # 3, 6.4.3 req # 1 & #2
Presentation of the id of the speaker is sufficient
See reqs in 6.4.5
[R-6.2.2-006a]
The FRMCS System shall be able to present the location of the Driver(s) to the Ground FRMCS Users involved in a Multi-train voice communication for Drivers and Ground FRMCS User(s).
A
22.280
5.11 001, 008, 015
6.12 001,006,007
6.4.5 001, 003, 004
[R-6.2.2-006b]
The FRMCS System shall be able to update the presentation of the location of the Drivers as they move.
A
22.280
5.11 007, 009, 013
6.12 006
[R-6.2.2-007]
A Multi-train voice communication for Drivers and Ground FRMCS User(s) always includes more than two participants.
If only two participants remain, the communication shall be treated as a user-to-user communication.
A
N/A
This is not a service requirement. It is up to 3GPP SA6 to decide whether a communication with only two has to change the mode of operation to 1-2-1 communication.
[R-6.2.2-008]
For a Multi-train voice communication for Drivers and Ground FRMCS User(s), multiuser talker control shall be used (See "9.7 Multiuser talker control related use cases").
A
22.179
6.2.3.7
[R-6.2.2-009]
For a Multi-train voice communication for Drivers and Ground FRMCS User(s), on the application layer the precedence of the incoming voice communication at the Driver and the Ground FRMCS User shall be managed by the prioritisation application.
A
N/A
See section 9.16 below
[R-6.2.2-010]
The FRMCS System shall be able to make available the speech and communication related data of a Multi-train voice communication for Drivers and Ground FRMCS User(s) for recording.
A
22.280
On-Net:6.15.4-001 – 010
Off-Net: Not implemented
6.2.2a Use case: Join an on-going Multi-train voice communication for Drivers and Ground FRMCS User(s) communication
6.2.2a.1 Description
An authorised FRMCS User is automatically connected to the ongoing Multi-train voice communication when meeting conditions based on location and/or functional identities.
An authorised FRMCS User can request to connect to an ongoing Multi-train voice communication, that has been previously left, when meeting conditions based on location and/or functional identities.
6.2.2a.2 Pre-conditions
The FRMCS User is authorised to connect to a Multi-train voice communication for Drivers and Ground FRMCS User(s) communication. This is managed by the application “authorisation of communication” (see 9.8).
The FRMCS User is authorised to use the Multi-train voice communication for Drivers and Ground FRMCS User(s) application. This is managed by the application “authorisation of application” (see 9.9).
There is an ongoing Multi-train voice communication for Drivers and Ground FRMCS User(s) communication.
6.2.2a.3 Service flows
When a Driver and/or Ground FRMCS User meets the criteria (location and/or functional identity) for being involved in the ongoing Multi-train voice communication for Drivers and Ground FRMCS User(s), the User application automatically sends the request to connect to the ongoing voice communication, or the FRMCS User sends this request by selecting or dialling the corresponding communication.
The FRMCS system connects the Driver and/or Ground FRMCS User to the ongoing call.
The information from the Role management and presence application is used to present the identities for both Driver(s) and Ground FRMCS User(s) to the parties in the call.
If the Driver and/or Ground FRMCS User is connected to more than one Drivers and/or Ground FRMCS Users, the multiuser talker control application is used.
The precedence of the incoming voice communication at the Driver and the Ground FRMCS User is managed by the prioritisation application.
The voice communication is recorded by the FRMCS System Voice recording and access application.
6.2.2a.4 Post-conditions
The Driver and/or the Ground FRMCS User is connected to the on-going Multi-train voice communication for Drivers and Ground FRMCS User(s) communication.
6.2.2a.5 Potential requirements and gap analysis
Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-6.2.2a-001]
The FRMCS System shall be able to notify the user application of an authorised FRMCS User about an ongoing Multi-train voice-communication for Drivers and Ground FRMCS User(s) when conditions based on location and/or functional identities are met.
A
22.280
22.179
TS 22.179 Floor Control clause 6.2.3.2 Req #1,
TS 22.280 clause 5.1 Req # 2, 6.4.9 req #6, 5.17 req # 3, 6.1 req #5
[R-6.2.2a-002]
When the user application of an authorised FRMCS User receives a notification of an ongoing Multi-train voice-communication for Drivers and Ground FRMCS User(s), it shall be able to request automatically to the FRMCS System a connection to the communication.
A
22.280
6.4.9 req #6, 5.17 req # 3, 6.1 req #5, R6.6.5.2-00X
6.6.4.2-002a,002b
5.9a-006, 5.9a-008a
[R-6.2.2a-003]
When the user application of an authorised FRMCS User receives a notification of an ongoing Multi-train voice-communication for Drivers and Ground FRMCS User(s) that has been previously left, it shall be able to request to the FRMCS System a connection to the communication again
A
22.280
6.4.9 req #6, 5.17 req # 3, 6.1 req #5, R6.6.5.2-00X
6.6.4.2-002a,002b
5.9a-006, 5.9a-008a
[R-6.2.2a-004]
When a FRMCS User joins a Multi-train voice communication for Drivers and Ground FRMCS User(s), the application layer priority of the communication shall be managed by the prioritisation application.
A
22.280
6.8.7 Application layer priority, 7.6 MCX Service priority requirements
[R-6.2.2a-005]
For a Multi-train voice communication for Drivers and Ground FRMCS User(s), the FRMCS System shall be able to determine the FRMCS User(s) to be joined in the ongoing voice communication, based, amongst others, on the following criteria:
location information, speed and direction of travel provided by the locations services application, and/or functional identity provided by the Role management and presence application.
A
22.280
6.4.9 req #6, 5.17 req # 3, 6.1 req #5, R-6.1.005, R6.6.5.2-00X
6.6.4.1.1, 6.6.4.1.2, 6.6.4.2-002a,002b
5.9a-006, 5.9a-008a
[R-6.2.2a-006]
When a FRMCS User joins a Multi-train voice communication for Drivers and Ground FRMCS User(s), the FRMCS System shall be able to mutually present the identities of all communication partners involved in the communication.
A
22.280
5.3 req #2, 5.7 req # 3, 6.4.3 req # 1 & #2
Presentation of the id of the speaker is sufficient
See reqs in 6.4.5
[R-6.2.2a-007]
The FRMCS System shall be able to present the location of the newly added Driver(s) to the Ground FRMCS Users involved in a Multi-train voice communication for Drivers and Ground FRMCS User(s).
A
22.280
5.11 001, 008, 015
6.12 001,006,007
6.4.5 001, 003, 004
[R-6.2.2a-008]
For a Multi-train voice communication for Drivers and Ground FRMCS User(s), multiuser talker control shall be used for the newly added FRMCS Users (See "9.7 Multiuser talker control related use cases").
A
22.179
6.2.3.7
[R-6.2.2a-009]
When a FRMCS User joins an on-going Multi-train voice communication for Drivers and Ground FRMCS User(s), the precedence of the incoming voice communication at the Driver and the Ground FRMCS User shall be managed by the prioritisation application.
A
N/A
See section 9.16 below
[R-6.2.2a-010]
When a FRMCS User joins an on-going Multi-train voice communication for Drivers and Ground FRMCS User(s), the FRMCS System shall be able to make available the speech and communication related data for recording.
A
22.280
On-Net:6.15.4-001 – 010
Off-Net: Not implemented |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.2.3 Use case: Termination of Multi-train voice communication for Drivers and Ground FRMCS User(s) communication | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.2.3.1 Description | The Driver is able to either put on hold, leave, or terminate (by configuration) the voice communication.
The Driver is automatically disconnected from the voice communication when the conditions to be included in it are not fulfilled
The Ground FRMCS User(s) is able to either put on hold, leave or terminate the voice communication. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.2.3.2 Pre-conditions | There is an ongoing Multi-train voice communication for Drivers and Ground FRMCS User(s) communication. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.2.3.3 Service flows | Driver on hold
The Driver is able to put the voice communication on hold.
After the Driver has put the voice communication on hold, the communication remains in the FRMCS System, and the Driver is able to return to the communication again. When put on hold the other participants in the communication are informed and can continue the communication.
Driver leaving
The Driver is able to leave the voice communication.. When a Driver has left the other participants in the communication are informed and can continue the communication if there are still Driver(s) involved in the communication.
The Driver automatically leaves the voice communication if the conditions to be included in it are not fulfilled
The FRMCS System terminates the voice communication if the last Driver has left (although (multiple) Ground FRMCS Users are still active in the communication). All involved FRMCS Users are informed.
Driver termination
By configuration, a Driver is able to terminate the voice communication. The FRMCS system terminates the voice communication. All involved users are informed.
Ground FRMCS User on hold
A Ground FRMCS User is able to put the voice communication on hold in the case that more than one Ground FRMCS User is part of the voice communication. The Ground FRMCS User is able to be part of the communication again.
When put on hold the other participants in the communication are informed and can continue the communication.
Ground FRMCS User leaving
A Ground FRMCS User is able to leave the voice communication.
After the Ground FRMCS User has left the voice communication, the remaining users are informed.
Ground FRMCS User termination
Any Ground FRMCS User is able to terminate the voice communication.
The FRMCS System terminates the voice communication. All involved users are informed. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.2.3.4 Post-conditions | A Ground FRMCS User or a Driver has put on hold or left the voice communication, or a Driver, Ground FRMCS User or FRMCS system has terminated the communication. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.2.3.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-6.2.3-001]
For a Multi-train voice communication for Drivers and Ground FRMCS User(s), a Driver or a Ground FRMCS User shall be able to put the voice communication on hold. The voice communication between the remaining users shall not be affected by a Driver or Ground FRMCS User putting the voice communication on hold.
A
22.280
5.4.1, 5.4.2, 5.1.5
R-6.4.4-003, R-6.4.4-004
The affiliation mechanism is considered sufficient to mimic the desired behaviour.
[R-6.2.3-002]
For a Multi-train voice communication for Drivers and Ground FRMCS User(s), a Driver shall be able to leave the voice communication at any time. After a Driver has left the communication, the remaining users are informed.
A
22.280
TS 22.280: R-6.4.4-003, R-6.4.4-004
The affiliation mechanism is considered sufficient to mimic the desired behaviour.
[R-6.2.3-003]
For a Multi-train voice communication for Drivers and Ground FRMCS User(s) the Driver is able to terminate the communication based on configuration (authorised FRMCS User).
A
22.179
22.280
TS 22.179: 6.2.3.4, 6.2.3.5, 6.2.4
TS 22.280: R-6.4.4-003, R-6.4.4-004
[R-6.2.3-005]
For a Multi-train voice communication for Drivers and Ground FRMCS User(s), the FRMCS System terminates the voice communication if the last Driver has left (although (multiple) Ground FRMCS Users are still active in the communication). All involved users are informed.
A
22.280
22.179
22.179 6.2.4 008
22.280 6.4.9 001
CR 22.280 0048 rev1: R-6.1-006, R-6.4.9-001
[R-6.2.3-006]
For a Multi-train voice communication for Drivers and Ground FRMCS User(s), a Ground FRMCS User shall be able to leave the communication. After a Ground FRMCS User has left the communication, the remaining users are informed.
A
22.280
6.4.4 002; 6.4.5 001; 5.1.5 003-008
R-6.4.4-003, R-6.4.4-004
The affiliation mechanism is considered sufficient to mimic the desired behaviour.
[R-6.2.3-007]
For a Multi-train voice communication for Drivers and Ground FRMCS User(s), any Controller shall be able to terminate the communication. All involved users are informed.
A
N/A
Due to the use of the affiliation mechanism and the burst-oriented nature of the MCPTT communication there is no such thing like a termination of a communication. It is simply not used anymore and the MCX Service deletes the identifiers and reservation for it after some time. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.2.4 Use case: Service Interworking and service continuation between GSM-R and FRMCS for Multi-train voice communication for Drivers and Ground FRMCS User(s) communication | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.2.4.1 Description | For migration purposes the service interworking and service continuation between the GSM-R system and FRMCS System for Multi-train voice communication for Drivers and Ground FRMCS User(s) communication needs to be defined.
Interworking between FRMCS and GSM-R shall not require any changes in the GSM-R system.
Depending on the migration scenario a Ground FRMCS User or a Driver can be attached to the FRMCS system, to the GSM-R system or both. The Driver can be attached either in the GSM-R system or in the FRMCS System. Functional identities are applicable in one system only.
This use case only applies to end user devices supporting both FRMCS and GSM-R systems, i.e. contains a FRMCS UE and a GSM-R UE |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.2.4.2 Pre-conditions | None. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.2.4.3 Service flows | Driver attached to GSM-R
When the Driver is attached to the GSM-R system and is initiating voice communication to other Drivers and Ground FRMCS User, the FRMCS system routes the group call to the appropriate Drivers and Ground FRMCS User(s) attached to the FRMCS.
The Multi-train voice communication for Drivers and Ground FRMCS User(s) communication is linked between GSM-R and FRMCS. It is controlled by the FRMCS system.
Service interworking between the talker control in the GSM-R system and the FRMCS system is not required but is expected to be done independently in the GSM-R and FRMCS systems.
If the Driver or the Ground FRMCS User is located in the FRMCS System, the GSM-R system can only route the call if it can be reached by an address or identity understood by the GSM-R system. The Role management in FRMCS provides the appropriate address or identity e.g. by providing a mapping of GSM-R identities and FRMCS identities.
The information from the Role management and presence application is used to route the communication and to present the identities of both Driver and Ground FRMCS User.
Driver attached to FRMCS
When the Driver is attached to the FRMCS System and is initiating voice communication to other Drivers and Ground FRMCS User(s), the FRMCS System will route the communication through the GSM-R to the appropriate GSM-R Drivers and Ground GSM-R User(s)..
The information from the Role management and presence application is used to route the communication and to present the identities of both Driver and Ground FRMCS User. The Role management in FRMCS provides the appropriate address or identity e.g. by providing a mapping of GSM-R identities and FRMCS identities.
Driver moving from GSM-R to FRMCS
When the GSM-R user equipment of the Driver is detached from the GSM-R system, the FRMCS end user device provides service continuation by setting up the communication via the FRMCS System. An interruption of voice communication is acceptable.
Note: It is assumed the FRMCS Application on the FRMCS Equipment will have some control on the GSM-R part of the UE.
Driver moving from FRMCS to GSM-R
When the FRMCS User equipment of the Driver is detached from the FRMCS System, the FRMCS end user device provides service continuation by setting up the communication via the GSM-R system. An interruption of voice communication is acceptable.
Note: It is assumed the FRMCS Application on the FRMCS Equipment will have some control on the GSM-R part of the UE. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.2.4.4 Post-conditions | None. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.2.4.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-6.2.4-001]
The FRMCS System shall provide the necessary means to allow FRMCS Users to be reachable from a legacy GSM-R system. Interworking between FRMCS and GSM-R shall not require any changes on GSM-R network side.
A
22.179
22.280
TS 22.179: Covered in 6.18.4.2
TS 22.280: R-6.17.3.1-001 to 005
[R-6.2.4-001a]
The FRMCS System shall provide the necessary means to Driver attached to the GSM-R system to set up a Multi-train voice communication for Drivers and Ground FRMCS User(s) for users attached to the FRMCS system. Interworking between FRMCS and GSM-R shall not require any changes on GSM-R network side
A
22.179
22.280
TS 22.179: Covered in 6.18.4.2
TS 22.280: R-6.17.3.1-001 to 005
[R-6.2.4-002]
The FRMCS System shall provide the necessary means to FRMCS Users to set up a Multi-train voice communication for Drivers and Ground FRMCS User(s) also to users in legacy GSM-R system. Interworking between FRMCS and GSM-R shall not require any changes on GSM-R network side.
A
22.179
Covered in 6.18.4.2
[R-6.2.4-003]
For Multi-train voice communication for Drivers and Ground FRMCS User(s), when the GSM-R UE becomes detached from the GSM-R system, e.g. due to coverage problems, the end user device, if capable of making use of the FRMCS System, shall be able to set up the communication on the FRMCS System. An interruption of voice communication is acceptable.
Note 1: This use case only applies to end user devices containing a FRMCS UE and a GSM-R UE. It is assumed the FRMCS Application on the FRMCS Equipment will have some control of the GSM-R part of the UE which is referred to here as end user device.
A
22.280
Covered by 6.6.4.1.2 and 6.6.5.2
[R-6.2.4-004]
For Multi-train voice communication for Drivers and Ground FRMCS User(s), when the FRMCS Equipment becomes detached from the FRMCS System, e.g. due to coverage problems, the end user device, if capable of making use of legacy GSM-R, shall be able to set up the communication on legacy GSM-R. An interruption of voice communication is acceptable.
Note 2: This use case only applies to end user devices containing a FRMCS Equipment and a GSM-R UE. It is assumed the FRMCS Application on the FRMCS Equipment will have some control of the GSM-R part of the UE which is referred to here as end user device.
A
N/A
Covered by GSM-R “Late Entry |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.3 On-train outgoing voice communication from the Driver towards the Controller(s) of the train | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.3.1 Introduction | In this chapter the use cases related to the function of On-train outgoing voice communication from the Driver towards the Controller(s) of the train are defined. This use case allows the Driver to only communicate with Controllers. The following use cases are defined:
• Initiation of Driver to Controller(s) voice communication
• Termination of Driver to Controller(s) voice communication
• Interworking GSM-R and FRMCS of Driver to Controller(s) communication |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.3.2 Use case: Initiation of Driver to Controller(s) voice communication | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.3.2.1 Description | The Driver shall be able to initiate a voice communication to the Controller(s) that was, is, or will be responsible for the movement of the train. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.3.2.2 Pre-conditions | The Driver is authorised to initiate the voice communication to the Controller. This is managed by the authorisation of voice communication application.
The Driver is authorised to use the On-train outgoing voice communication from the Driver towards the Controller(s) of the train application by the application authorisation of application. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.3.2.3 Service flows | Driver to responsible Controller(s)
The Driver initiates the voice communication to the Controller. The priority of the communication is managed by the prioritisation application.
The FRMCS System determines the responsible Controller(s), based on:
• location information of the train provided by the locations services application, and/or
• functional identity provided by the Role management and presence application.
• system configuration on which Controller is responsible for which part of the track/station/etc.
The FRMCS System establishes the voice communication to the Controller(s) within a setup time specified as NORMAL (see 12.10). The information from the Role management and presence application is used to present the identities for both Driver and Controller. Also, the location of the Driver is presented to the Controller which is retrieved from the location services application.
If the Driver is connected to more than one Controller, the multiuser talker control application is used.
The precedence of the incoming voice communication at the Controller is managed by the prioritisation application.
The voice communication is recorded by the voice recording and access application.
Driver to another Controller(s)
The Driver initiates the voice communication to the Controller who was or will be responsible for the movement of the train. The addressing is performed by selecting an entry from a list or entered manually. The priority of the communication is managed by the prioritisation application.
The FRMCS System presents the list of Controllers to the Driver, based on:
• location information provided by the locations services application, and/or
• functional identity provided by the Role management and presence application.
• system configuration on which Controller is responsible for which part of the track/station/etc.
The FRMCS System establishes the voice communication to the Controller(s) within a setup time specified as NORMAL (see 12.10). The information from the Role management and presence application is used to present the identities for both Driver and Controller. Also, the location of the Driver is presented to the Controller which is retrieved from the location services application.
If the Driver is connected to more than one Controller, the multiuser talker control application is used.
The precedence of the incoming voice communication at the Controller is managed by the prioritisation application.
The voice communication is recorded by the Voice recording and access application. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.3.2.4 Post-conditions | The Driver is connected to the requested Controller. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.3.2.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-6.3.2-001]
For Driver to Controller voice communication, the Driver shall be able to initiate a voice communication to the Controller who is currently responsible for the train. The application layer priority of the voice communication shall be managed by the prioritisation application.
A
22.280
22.280 6.8.7.1, 6.8.7.2; 5.1.1 002
22.179 6.2.3.7.3 001
[R-6.3.2-002]
For Driver to Controller voice communication the FRMCS System shall be able to determine the responsible Controller(s), based on e.g.:
location information, speed and direction provided by the locations services application, and/or
functional identity provided by the Role management and presence application.
System configuration on which Controller is responsible for which part of the track/station/etc.
A
22.280
CR 22.280 0049rev3, 6.6.4.1.1, 6.6.4.1.2, Req 6.6.4.2-002a,002b
[R-6.3.2-003]
For Driver to Controller voice communication the FRMCS System shall add or remove FRMCS User from the communication once criteria are met or no more met, e.g. by a FRMCS User entering or leaving an area.
A
22.280
CR 22.280 0049rev3, 6.6.4.1.1, 6.6.4.1.2, Req 6.6.4.2-002a,002b
[R-6.3.2-004]
For Driver to Controller communication the FRMCS System shall establish the communication to the Controller(s) within a setup time specified as NORMAL (see 12.10).
A/T
N/A
See section 12.10 below
[R-6.3.2-005]
The FRMCS System shall be able to mutually present the identities of all communication partners involved in a Driver to Controller(s) voice communication.
A
22.280
TS 22.280, 5.3 req #2, 5.7 req # 3, 6.4.3 req # 1 & #2
22.280 6.12-006
The id of the speaker is considered sufficient
See reqs in 6.4.5
[R-6.3.2-006]
The FRMCS System shall be able to present the location of the Driver to the Controller(s) involved in a Driver to Controller(s) voice communication.
A
22.280
22.280
5.11 001, 008, 015
6.12 001,006,007
6.4.5 001, 003, 004
22.280 R-6.4.4-003, R-6.4.4-004
[R-6.3.2-007]
The FRMCS System shall be able to update the presentation of the location of the Drivers as they move.
22.280
22.280
5.11 007, 009, 013
6.12 006
[R-6.3.2-007 a]
For Driver to Controller communication, if the Driver is connected to just one Controller, the communication shall be considered as a user-to-user communication.
A
22.280
This is not a service requirement it is up to 3GPP SA6 to decide whether a communication with only two has to change the mode of operation to 1-2-1 communication
[R-6.3.2-008]
For Driver to Controller voice communication, if the Driver is connected to more than one Controller, the multiuser talker control shall be used (See "9.7 Multiuser talker control related use cases").
A
22.179
CRs 22.179 adding and CRs subsequently changing Section 5.9a
[R-6.3.2-009]
For Driver to Controller communication on application layer the precedence of the incoming voice communication at the Controller shall be managed by the prioritisation application.
A
22.280
See section 9.16 below
[R-6.3.2-010]
The FRMCS System shall be able to make available the speech and communication related data of a Multi-train voice communication for Drivers including Ground FRMCS User(s) for recording.
A
22.280
On-Net:6.15.4-001 – 010
Off-Net: Not implemented
[R-6.3.2-011]
For Driver to Controller communication the Driver shall be able to initiate the communication to the Controller who was previously or will be responsible next for the movement of the train. The selection shall be performed by selecting an entry from a list or entered manually. The priority of the communication on application layer shall be managed by the prioritisation application.
A
22.280
CR 22.280 0049rev3: 5.9a-006, 5.9a-008a, 6.6.4.1.1, 6.6.4.1.2, Req 6.6.4.2-002a,002b
[R-6.3.2-012]
For Driver to Controller communication the FRMCS System shall be able to present the list of Controllers to the Driver in order to select from, based on, amongst others, the following criteria:
location information, speed and direction provided by the locations services application, and/or
functional identity provided by the Role management and presence application.
System configuration on which Controller is responsible for which part of the track/station/etc.
A
22.280
CR 22.280 0049rev3: 5.9a-006, 5.9a-008a, 6.6.4.1.1, 6.6.4.1.2, Req 6.6.4.2-002a,002b |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.3.3 Use case: Termination of Driver to Controller(s) voice communication | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.3.3.1 Description | The Driver shall be able to terminate the Driver to Controller voice communication. The Driver is not able to leave the communication or to put on hold.
The Controller(s) shall be able to either put on hold, leave or terminate the Driver to Controller communication. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.3.3.2 Pre-conditions | The Driver to Controller voice communication is ongoing. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.3.3.3 Service flows | Driver termination
The Driver shall be able to terminate the voice communication. The FRMCS System terminates the voice communication. All involved Controllers are informed.
Note: The Driver is not able to leave the communication or to put on hold.
Controller on hold
A Controller shall be able to put the Driver to Controller voice communication on hold in the case that more than one Controller is part of the voice communication.
After the Controller has put the voice communication on hold, the communication remains in the FRMCS System, and the Controller is able to be part of the communication again.
Controller leaving
A Controller shall be able to leave the Driver to Controller voice communication in the case that more than one Controller is part of the voice communication.
After the Controller has left the voice communication he is not able to return to the communication and the remaining users are informed.
Controller termination
Any Controller shall be able to terminate the Driver to Controller voice communication.
The FRMCS System terminates the voice communication. All involved users are informed. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.3.3.4 Post-conditions | A Controller has left the voice communication or the Driver to Controller voice communication is terminated. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.3.3.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-6.3.3-001]
For Driver to Controller communication the Driver shall be able to terminate the communication.
A
22.280
22.179
22.280 6.4.9 001
22.179 6.4.9 002, 6.2.4 008
[R-6.3.3-002]
For Driver to Controller communication the FRMCS System shall allow the operator to configure whether a Driver shall be able to leave the voice communication.
A
22.280
CR 22.280: 5.9a-012a, 5.9a-012b
[R-6.3.3-003]
For Driver to Controller communication the FRMCS System shall allow the operator to configure whether a Driver shall be able to put the voice communication on hold.
A
22.280
22.280, 5.4.1, 5.4.2, 5.1.5
The affiliation mechanism is considered sufficient to mimic the desired behavior.
[R-6.3.3-004]
For Driver to Controller communication a Controller shall be able to put the voice communication on hold in the case that more than one Controller is part of the communication. The voice communication between the remaining users shall not be affected by a Controller putting the voice communication on hold.
A
22.280
22.280 6.4.4 002; 6.4.5 001; 5.1.5 003-008
22.280 R-6.4.4-003, R-6.4.4-004
The affiliation mechanism is considered sufficient to mimic the desired behavior.
[R-6.3.3-005]
For Driver to Controller communication a Controller shall be able to leave the Driver to Controller communication in the case that more than one Controller is part of the communication. After a Controller has left the communication, the remaining users shall be informed.
A
22.280
22.280 6.4.4 002; 6.4.5 001; 5.1.5 003-008
22.280 R-6.4.4-003, R-6.4.4-004
The affiliation mechanism is considered sufficient to mimic the desired behavior.
[R-6.3.3-006]
For Driver to Controller communication any Controller shall be able to terminate the Driver to Controller communication. All involved users shall be informed.
A
22.280
22.179
22.280 6.4.9 001
22.179 6.2.4 008 |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.3.4 Use case: Service Interworking and service continuation between GSM-R and FRMCS of Driver to Controller(s) voice communication | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.3.4.1 Description | For migration purposes the service interworking and service continuation between the GSM-R system and FRMCS System for Driver to Controller(s) voice communication needs to be defined.
Interworking between FRMCS and GSM-R shall not require any changes in the GSM-R system.
Depending on the migration scenario a Controller can be attached to the FRMCS system, to the GSM-R system or both. The Driver can be attached either in the GSM-R system or in the FRMCS System. Functional identities are applicable in one system only.
This use case only applies to end user devices supporting both FRMCS and GSM-R systems. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.3.4.2 Pre-conditions | None. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.3.4.3 Service flows | Driver attached to GSM-R
When the Driver is attached to the GSM-R system and is initiating voice communication to Controller(s), the GSM-R system will route the voice communication to the Controller(s) accordingly.
If the Controller is located in the FRMCS System, the GSM-R system can only route the call to the Controller if the Controller can be reached by an address or identity understood by the GSM-R system. The Role management in FRMCS provides the appropriate address or identity e.g. by providing a mapping of GSM-R identities and FRMCS identities.
The information from the Role management and presence application is used to route the communication and to present the identities of both Driver and Controller.
Driver attached to FRMCS
When the Driver is attached to the FRMCS System and is initiating voice communication to Controller(s), the FRMCS System will route the communication to the Controller(s) accordingly. The information from the Role management and presence application is used to route the communication and to present the identities of both Driver and Controller. The Role management in FRMCS shall provide the appropriate address or identity e.g. by provide a mapping of GSM-R identities and FRMCS identities.
Driver moving from GSM-R to FRMCS
When the GSM-R user equipment of the Driver is detached from the GSM-R system the FRMCS end user device shall provide service continuation by setting up the communication via the FRMCS System. An interruption of voice communication is acceptable.
Note: This use case only applies to end user devices supporting both FRMCS and GSM-R systems, i.e. contains a FRMCS UE and a GSM-R UE. It is assumed the FRMCS Application on the FRMCS Equipment will have some control of the GSM-R part of the UE.
Driver moving from FRMCS to GSM-R
When the FRMCS User equipment of the Driver is detached from the FRMCS System the FRMCS end user device shall provide service continuation by setting up the communication via the GSM-R system. An interruption of voice communication is acceptable.
Note: This use case only applies to end user devices supporting both FRMCS and GSM-R systems, i.e. contains a FRMCS UE and a GSM-R UE. It is assumed the FRMCS Application on the FRMCS Equipment will have some control of the GSM-R part of the UE. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.3.4.4 Post-conditions | None. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.