hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
162c3f0c36a54745dc509a8130708d2d | 22.104 | 9.2 Requirements | Subject to regulatory requirements and operator policy, the 5G system shall support a mechanism by which an MNO can identify the ability of the MNO's infrastructure to continue operation despite a lack of electrical supply service, specifying which physical regions would be affected in terms of physical topology and the remaining time in which operation is possible. NOTE1: This information can facilitate energy distribution system recovery operations. Subject to regulatory requirements, the 5G system shall support a mechanism by which a third party can, in the event of an energy distribution system service interruption, communicate the energy distribution system recovery status in terms of location and time table to the MNO. NOTE2: This information can facilitate MNO operations to facilitate energy system recovery. Annex A (informative): Summary of service performance requirements A.1 About the vertical domains addressed in this Annex A vertical domain is an industry or group of enterprises in which similar products or services are developed, produced, and provided. The vertical domains addressed in this Annex are - Factories of the Future (A.2); - electric-power distribution (A.4); and - central power generation (A.5); and • Connected hospitals or medical facilities (A.6). A.2 Factories of the Future A.2.1 Overview The manufacturing industry is currently subject to a fundamental change, which is often referred to as the "Fourth Industrial Revolution" or simply "Industry 4.0" [15]. The main goals of Industry 4.0 are―among others―the improvement of flexibility, versatility, resource efficiency, cost efficiency, worker support, and quality of industrial production and logistics. These improvements are important for addressing the needs of increasingly volatile and globalised markets. A major enabler for all this is cyber-physical production systems based on a ubiquitous and powerful connectivity, communication, and computing infrastructure. The infrastructure interconnects people, machines, products, and all kinds of other devices in a flexible, secure and consistent manner. Several different application areas can be distinguished: 1) Factory automation: Factory automation deals with the automated control, monitoring and optimisation of processes and workflows within a factory. This includes aspects like closed-loop control applications (e.g., based on programmable logic or motion controllers) and robotics, as well as aspects of computer-integrated manufacturing. Factory automation generally represents a key enabler for industrial mass production with high quality and cost-efficiency. Corresponding applications are often characterised by highest requirements on the underlying communication infrastructure, especially in terms of communication service availability, determinism, and latency. In the Factories of the Future, static sequential production systems will be more and more replaced by novel modular production systems offering a high flexibility and versatility. This involves many increasingly mobile production assets, for which powerful wireless communication and localisation services are required. 2) Process automation: Process automation refers to the control of production and handling of substances like chemicals, food & beverage, pulp, etc. Process automation improves the efficiency of production processes, energy consumption, and safety of the facilities. Sensors measuring process values, such as pressures or temperatures, are working in closed loops via centralised and decentralised controllers. In turn, the controllers interact with actuators, e.g., valves, pumps, heaters. Also, monitoring of attributes such as the filling levels of tanks, quality of material, or environmental data are important, as well as safety warnings or plant shut downs. Workers in the plant are supported by mobile devices. A process automation facility may range from a few 100 m² to several km², and the facility may be geographically distributed. Depending on the size, a production plant may have several 10,000 measurement points and actuators. Autarkic device power supply for years is needed in order to stay flexible and to keep the total costs of ownership low. 3) HMIs and production IT: Human-machine interfaces (HMIs) include all sorts of devices for the interaction between people and production facilities, such as panels attached to a machine or production line, but also standard IT devices, such as laptops, tablet PCs, smartphones, etc. In addition, augmented- and virtual-reality applications are expected to play an increasingly important role in future. 4) Logistics and warehousing: Organisation and control of the flow and storage of materials and goods in the context of industrial production. In this respect, intra-logistics is dealing with logistics within a certain property (e.g., within a factory), for example by ensuring the uninterrupted supply of raw materials on the shop floor level using automated guided vehicles (AGVs), fork-lifts, etc. This is to be seen in contrast to logistics between different sites. Warehousing particularly refers to the storage of materials and goods, which is also getting more and more automated, for example based on conveyors, cranes and automated storage and retrieval systems. 5) Monitoring and maintenance: Monitoring of certain processes and/or assets in the context of industrial production without an immediate impact on the processes themselves (in contrast to a typical closed-loop control system in factory automation, for example). This particularly includes applications such as condition monitoring and predictive maintenance based on sensor data, but also big data analytics for optimising future parameter sets of a certain process, for instance. For these use cases, the data acquisition process is typically not latency-critical. For each of these application areas, a multitude of potential use cases exists, some of which are outlined in the following subclauses. These use cases can be mapped to the given application areas (see Table A.2.1-1). Table A.2.1-1: Mapping of the considered use cases (columns) to application areas (rows) Motion control Control-to-control Mobile control panels with safety Mobile robots Remote access and maintenance Augmented reality Closed-loop process control Process monitoring Plant asset management Factory automation X X X Process automation X X X X HMIs and Production IT X X Logistics and warehousing X X X Monitoring and maintenance X A.2.2 Factory automation A.2.2.1 Motion control A motion control system is responsible for controlling moving and/or rotating parts of machines in a well-defined manner, for example in printing machines, machine tools or packaging machines. A schematic representation of a motion control system is depicted in Figure A.2.2.1-1. A motion controller periodically sends desired set points to one or several actuators (e.g., a linear actuator or a drive) which thereupon perform a corresponding action on one or several processes (in this case usually a movement or rotation of a certain component). At the same time, sensors determine the current state of the process(es), e.g. the current position and/or rotation of one or multiple components, and send the actual values back to the motion controller. This is done in a strictly cyclic and deterministic manner, such that during one application cycle the motion controller sends updated set points to all actuators, and all sensors send their actual values back to the motion controller. Nowadays, typically Industrial Ethernet technologies are used for motion control systems. Figure A.2.2.1-1: Schematic representation of a motion control system Table A.2.2.1-1: Service performance requirements for motion control Use case # Characteristic parameter Influence quantity Communication service availability: target value [%] Communication service reliability: mean time between failures End-to-end latency: maximum Service bitrate: user experienced data rate Message size [byte] Transfer interval: lower bound Transfer interval: upper bound Survival time UE speed # of UEs Service area (note) 1 99.999 to 99.999 99 ~ 10 years < transfer interval value – 50 500 μs – 500 ns 500 μs + 500 ns 500 μs ≤ 72 km/h ≤ 20 50 m x 10 m x 10 m 2 99.999 9 to 99.999 999 ~ 10 years < transfer interval value – 40 1 ms – 500 ns 1 ms + 500 ns 1 ms ≤ 72 km/h ≤ 50 50 m x 10 m x 10 m 3 99.999 9 to 99.999 999 ~ 10 years < transfer interval value – 20 2 ms – 500 ns 2 ms + 500 ns 2 ms ≤ 72 km/h ≤ 100 50 m x 10 m x 10 m NOTE: Length x width x height. Use cases one to three Characteristic parameters and influence quantities for a communication service supporting the cyclic interaction described above. A.2.2.2 Control-to-control communication Control-to-control communication, i.e., the communication between different industrial controllers is already used today for different use cases, such as: - large machines (e.g., newspaper printing machines), where several controls are used to cluster machine functions, which need to communicate with each other; these controls typically need to be synchronised and exchange real-time data; - individual machines that are used for fulfilling a common task (e.g., machines in an assembly line) often need to communicate, for example for controlling and coordinating the handover of work pieces from one machine to another. Typically, a control-to-control network has no fixed configuration of certain controls that need to be present. The control nodes present in the network often vary with the status of machines and the manufacturing plant. Therefore, hot-plugging support for different control nodes is important and often used. Table A.2.2.2-1: Service performance requirements for control-to control communication in motion control Use case # Characteristic parameter Influence quantity Communication service availability: target value [%] Communication service reliability: mean time between failures End-to-end latency: maximum Message size [byte] Transfer interval Survival time UE speed # of UEs Service area (note 1) 1 (note 2) 99.999 9 to 99.999 999 ~ 10 years < transfer interval value 1 k ≤ 10 ms 10 ms stationary 5 to 10 100 m x 30 m x 10 m 2 (note 2) 99.999 9 to 99.999 999 ~ 10 years < transfer interval value 1 k ≤ 50 ms 50 ms stationary 5 to 10 1,000 m x 30 m x 10 m NOTE 1: Length x width x height. NOTE 2: Communication may include two wireless links (UE to UE) Use case one Control-to-control communication between different motion (control) subsystems, as addressed in Subclause A.2.2.1. An exemplary application for this is large printing machines, where it is not possible or desired to control all actuators and sensors by one motion controller only. Use case two Control-to-control communication between different motion (control) subsystems. Exemplary application for this are extra-large machines or individual machines used for fulfilling a common task (e.g., machines in an assembly line). A.2.2.3 Mobile robots Mobile robots and mobile platforms, such as automated guided vehicles, have numerous applications in industrial and intra-logistics environments and will play an increasingly important role in the Factory of the Future. A mobile robot essentially is a programmable machine able to execute multiple operations, following programmed paths to fulfil a large variety of tasks. This means, a mobile robot can perform activities like assistance in work steps, collaboration with other robots, e.g. for car assembly, and transport of goods, materials and other objects. Mobile robot systems are characterised by a maximum flexibility in mobility relative to the environment, with a certain level of autonomy and perception ability, i.e., they can sense and react with their environment. Autonomous guided vehicles (AGVs) are a sub-group of mobile robots. AGVs are driverless and used for moving materials efficiently within a facility. A detailed overview of the state of the art of autonomous-guided-vehicle systems is provided elsewhere in the literature [16]. All mobile robots incorporate all functionalities needed for an AGV. Today, the AGV’s control intelligence is hosted inside the AGV. In the future, centralised fleet control will be hosted in the edge cloud, which will require reliable wireless communication between the control entity and all AGVs. Also, the current paradigm of pre-describing a route for the AGV will be replaced with target-based navigation. This paradigm change will make AGV routes more flexible. Mobile robots are monitored and controlled from a guidance control system. Radio-controlled guidance control is necessary to get up-to-date process information, to avoid collisions between mobile robots, to assign driving jobs to the mobile robots, and to manage the traffic of mobile robots. The mobile robots are track-guided by the infrastructure with markers or wires in the floor or guided by own surround sensors, like cameras and laser scanners. Mobile robot systems can be divided in operation in indoor, outdoor and both indoor and outdoor areas. These environmental conditions have an impact on the requirements of the communication system, e.g., the handover process, to guarantee the required cycle times. Where this document does not explicitly refer to AGVs, the term mobile robots applies to AGVs as well as to mobile robots. Table A.2.2.3-1: Service performance requirements for mobile robots Use case # Characteristic parameter Influence quantity Communication service availability: target value [%] Communication service reliability: mean time between failures End-to-end latency: maximum Service bitrate: user experienced data rate Message size [byte] Transfer interval: lower bound Transfer interval: target value (note) Transfer interval: upper bound Survival time UE speed # of UEs Service area 1 > 99.999 9 ~ 10 years < target transfer interval value – 40 to 250 – < 25 % of target transfer interval value 1 ms to 50 ms + < 25 % of target transfer interval value target transfer interval value ≤ 50 km/h ≤ 2,000 ≤ 1 km2 2 > 99.999 9 ~ 1 year < target transfer interval value – 15 k to 250 k – < 25 % of target transfer interval value 10 ms to 100 ms + < 25 % of target transfer interval value target transfer interval value ≤ 50 km/h ≤ 2,000 ≤ 1 km2 3 > 99.999 9 ~ 1 year < target transfer interval value – 40 to 250 – < 25 % of target transfer interval value 40 ms to 500 ms + < 25 % of target transfer interval value target transfer interval value ≤ 50 km/h ≤ 2,000 ≤ 1 km2 4 > 99.999 9 ~ 1 week 10 ms > 10 Mbit/s – – – – ≤ 50 km/h ≤ 2,000 ≤ 1 km2 NOTE: The transfer interval is not so strictly periodic in these use cases. The transfer interval deviates around its target value within bounds. The mean of the transfer interval is close to the target value. Use case one Periodic communication for the support of precise cooperative robotic motion control (transfer interval: 1 ms), machine control (transfer interval: 1 ms to 10 ms), co-operative driving (10 ms to 50 ms). Use case two Periodic communication for video-operated remote control. Use case three Periodic communication for standard mobile robot operation and traffic management. Use case four Real-time streaming data transmission (video data) from a mobile robot to the guidance control system. Additional information AGVs have the following needs. – The direct-device control is time-critical since the communication involves safety-relevant functions such as emergency stop and the avoidance of obstacles. – For the implementation of swarm intelligence, position and availability information are needed. A possible route change due to a blocked route affects the routes of all other AGVs that will follow. The communication is less time-critical than for safety-relevant functions. – Camera-based navigation requires high data rates. Examples for camera-based navigation are the positioning of boxes/containers, detection of persons and obstacles, as well as creation and administration of a map for flexible navigation. Note that sensor-based navigation requires lower data rates than camera-based navigation. – AGV route control and emergency safety related time critical latency and response can be achieved with an edge cloud where the edge infrastructure is located close to the AGVs Mobile robots have additional needs. – The mobile robot provides an additional service during transport (for instance quality inspection, scanning of surroundings, asset identification, carrying of work pieces). In order to reduce the uplink data rate, pre-compression of data is possible directly on the device. The communication is not or at least less time-critical than the motion control of the mobile robot. – The mobile robot needs to interact with the periphery (for instance intelligent storage racks, stationary robots, and moving machines). This communication is time-critical. Interaction with the periphery can be relevant at the start point, end point, and also at several intermediate stations (for instance the collection of parts from intelligent storage racks). The exact position and orientation can be determined by a centering station and the AGV sensors. Additional scanning by the robot with a video camera may be necessary. – For some mobile robots, their control intelligence might be centralized and hosted in an edge cloud. They require secure communication towards the edge cloud. If the path layout such a mobile robot follows (e.g., including indoor and outdoor) causes it to switch the communication between a private network and a public network, consideration should be given to provide the required level of security for communication. – Mobile robots whose control intelligence is centralized and hosted in the edge cloud needs privacy protection of data stored in the edge cloud. – In order to be able to process time-sensitive data from local sensors and devices (AGVs, robots etc.) in an edge cloud, the edge infrastructure needs to be on-premise or close to the factory A.2.2.4 Wired to wireless link replacement In a traditional factory, the production environment is fixed. Machines that are cooperating are connected via cable, typically using an industrial ethernet technology like PROFINET. In order to increase flexibility in the production setup, the wired links are replaced with wireless links. Figure A.2.2.4-1: Example of four cooperating machines with wireless connections (based on [26]) We assume two or more machines (typically 4 or 5) to be cooperating with each other during production. In order to replace the cables, each machine is equipped with one UE, connected to the controller (shown in Figure A.2.2.4-1). The cooperating machine’s communication can be divided into two types. Periodic traffic and a-periodic traffic. Both types are scheduled, therefore the a-periodic traffic is also adhering to the transfer interval. The traffic requirements are from the point of view of the UE and give the maximum aggregate traffic of all links. Meaning, the traffic per link may change according to the number of cooperating machines but the total traffic at the UE cannot exceed the given values. Table A.2.2.4-1: Service performance requirements for wired to wireless link replacement Use case # Characteristic parameter Influence quantity Communication service availability: target value [%] Communication service reliability: mean time between failures End-to-end latency: maximum Data rate [Mbit/s] Transfer interval Survival time UE speed # of UEs Service area (note 1) 1 (periodic traffic) 99.999 9 to 99.999 999 ~ 10 years < transfer interval value 50 ≤ 1 ms 3 x transfer interval stationary 2 to 5 100 m x 30 m x 10 m 1 (aperiodic traffic) 99.999 9 to 99.999 999 ~ 10 years < transfer interval value 25 ≤ 1 ms (note 2) stationary 2 to 5 100 m x 30 m x 10 m 2 (periodic traffic) 99.999 9 to 99.999 999 ~ 10 years < transfer interval value 250 ≤ 1 ms 3 x transfer interval stationary 2 to 5 100 m x 30 m x 10 m 2 (aperiodic traffic) 99.999 9 to 99.999 999 ~ 10 years < transfer interval value 500 ≤ 1 ms (note 2) stationary 2 to 5 100 m x 30 m x 10 m NOTE 1: Length x width x height. NOTE 2: Transfer interval also applies for scheduled aperiodic traffic Use case one In the case of the 100 Mbit/s link replacement, 50 % periodic traffic and 25 % a-periodic traffic are assumed. Use case two In the case of the 1 Gbit/s link replacement, 25 % periodic traffic and 50 % a-periodic traffic are assumed. A.2.2.5 Cooperative carrying In a smart factory, large or heavy work pieces will be carried from one place to another by multiple mobile robots or AGVs. These mobile robots / AGVs need to work together in order to carry the large or heavy work piece safely. This cooperation is achieved with a cyber-physical control application that controls the drives and movements of the mobile robots / AGVs in a coordinated way, so that large or heavy work pieces are carried smoothly and safely from one place to another (see Figure 5.11.1-1). Figure A.2.2.5-1: Mobile robots / AGVs carrying a large work piece cooperatively The communication between the collaborating mobile robots / AGVs requires high communication service availability and ultra-low latency. The exchange of control commands and control feedback is done with periodic deterministic communication and using time-sensitive networking. There are two distinct use case variants of cooperative carrying: (1) carrying of rigid or fragile work pieces that require very precise coordination between the collaborating mobile robots, and (2) carrying of more flexible or elastic work pieces that allow some tolerance in the coordinated movements of the collaborative mobile robots. The higher tolerance in the coordinated movements allows for either faster movement of the work piece or longer transfer intervals (trade-off between UE speed and transfer interval). Table A.2.2.5-1: Service performance requirements for cooperative carrying Use case # Characteristic parameter Influence quantity Communication service availability: target value [%] Communication service reliability: mean time between failures End-to-end latency: maximum Service bitrate: user experienced data rate Message size [byte] Transfer interval: target value (note 1) Survival time (note 1) UE speed # of UEs Service area (note 2) 1 99.999 9 to 99.999 999 ~ 10 years < 0.5 x transfer interval 2.5 Mbit/s 250; 500 with localisation information > 5 ms > 2.5 ms > 1.7 ms 0 transfer interval 2 x transfer interval ≤ 6 km/h 2 to 8 10 m x 10 m x 5 m; 50 m x 5 m x 5 m 2 99.999 9 to 99.999 999 ~ 10 years < 0.5 x transfer interval 2.5 Mbit/s 250; 500 with localisation information > 5 ms > 2.5 ms > 1.7 ms 0 transfer interval 2 x transfer interval ≤ 12 km/h 2 to 8 10 m x 10 m x 5 m; 50 m x 5 m x 5 m NOTE 1: The first value is the application requirement, the other values are the requirement with multiple transmission of the same information (two or three times respectively). NOTE 2: Service Area for direct communication between UEs (length x width x height). The group of UEs with direct communication might move throughout the whole factory site (up to several km²) Use case one Periodic deterministic communication for cooperative carrying of fragile work pieces (UE to UE / ProSe communication). Use case two Periodic deterministic communication for cooperative carrying of elastic work pieces (UE to UE / ProSe communication). A.2.3 Process automation A.2.3.1 Closed-loop control In the closed-loop control use case for process automation, several sensors are installed in a plant and each sensor performs continuous measurements. The measurement data are transported to a controller, which takes decision to set actuators. The latency and determinism in this use case are crucial. This use case has very stringent requirements in terms of latency and service availability. The required service area is usually bigger than for motion control use cases. Interaction with the public network (e.g., service continuity, roaming) is not required. Table A.2.3.1-1: Service performance requirements for closed-loop control in process automation Use case # Characteristic parameter Influence quantity Communication service availability: target value [%] Communication service reliability: mean time between failures End-to-end latency: maximum Message size [byte] Transfer interval: lower bound Transfer interval: target value Transfer interval: upper bound Survival time UE speed # of UEs Service area (note) 1 99.999 9 to 99.999 999 ≥ 1 year < target transfer interval value 20 -5 % of target transfer interval value ≥ 10 ms +5 % of target transfer interval value 0 typically stationary typically 10 to 20 typically ≤ 100 m x 100 m x 50 m NOTE: Length x width x height. Use case one Several sensors are installed in a plant and each sensor performs continuous measurements. The measurement data are transported to a controller, which takes decision to set actuators. A.2.3.2 Process and asset monitoring For process and asset monitoring in the area of process automation, a large number of industrial wireless sensors are installed in the plant to give insight into process and environmental conditions, asset health and inventory of material. The data are transported to displays for observation and/or to databases for registration and data analysis Examples of sensors are temperature, pressure or flow rate sensors for process monitoring, vibration sensors for health monitoring of e.g. motors, or thermal cameras to detect leakages. Industrial wireless sensors are typically constrained in terms of size, complexity and/or power consumption. The operation for this use case can be in a wide service area, and interaction with the public network (e.g., service continuity, roaming) may be required. Table A.2.3.2-1: Service performance requirements for process and asset monitoring Characteristic parameter Influence quantity Use case Communication service availability: target value [%] Communication service reliability: mean time between failure End-to-end latency Transfer interval (note 1) Bit rate [bits/s] Battery lifetime [year] (note 2) Message Size [byte] Survival time UE speed UE density [UE / m²] Range [m] (note 4) Service area (note 5) 1 99.99 ≥ 1 week < 100 ms 100 ms to 60 s ≤ 1 M ≥ 5 20 (note 3) 3 x transfer interval Stationary Up to 1 < 500 ≤ 10 km x 10 km x 50 m 2 99.99 ≥ 1 week < 100 ms ≤ 1 s ≤ 200 k ≥ 5 25 k 3 x transfer interval Stationary Up to 0.05 < 500 ≤ 10 km x 10 km x 50 m 3 99.99 ≥ 1 week < 100 ms ≤ 1 s ≤ 2 M ≥ 5 250 k 3 x transfer interval Stationary Up to 0.05 < 500 ≤ 10 km x 10 km x 50 m NOTE 1: The transfer interval deviates around its target value by < ± 25 %. NOTE 2: Industrial sensors can use a wide variety of batteries depending on the use case, but in general they are highly constrained in terms of battery size. NOTE 3: The application-level messages in this use case are typically transferred over Ethernet, in which case the minimum Ethernet frame size of 64 bytes applies and dictates the minimum size of the PDU sent over the air interface. NOTE 4: Distance between the gNB and the UE. NOTE 5: Length x width x height. Use case one Sensors generating periodic measurements of a continuous value (e.g. temperature, pressure, flow rate sensors). The traffic is predominantly mobile originated. Use case two Sensors generating waveform measurements (e.g. vibration sensors). Even though the waveform measurement is continuous, it is expected that this type of sensors will buffer and transmit the data periodically (e.g. every second) to save battery by enabling discontinuous transmission. The traffic is predominantly mobile originated. Use case three Cameras (regular or thermal) for asset monitoring (e.g. for leakage detection). Even though the video recording is continuous, it is expected that this type of sensors will buffer and transmit the data periodically (e.g. every second) to save battery by enabling discontinuous transmission. The traffic is predominantly mobile originated. A.2.3.3 Plant asset management To keep a plant running, it is essential that the assets, such as pumps, valves, heaters, instruments, etc., are maintained. Timely recognition of any degradation and continuous self-diagnosis of components are used to support and plan maintenance. Remote software updates enhance and adapt the components to changing conditions and advances in technology. The operation for this use case can be in a wide service area, and interaction with the public network (e.g., service continuity, roaming) may be required. In this use case, the assets themselves are assumed to be connected to the 5G system. The use case where sensors are used to monitor assets is covered in clause A.2.3.2. Table A.2.3.3-1: Service performance requirements for plant asset management Use case # Characteristic parameter Influence quantity Communication service availability: target value [%] Communication service reliability: mean time between failures End-to-end latency: maximum Message size [byte] Transfer interval Survival time UE speed # of UEs Service area (note) 1 99.99 TBD < transfer interval value 20 to 255 several seconds matter of convenience; typically ≥ 3 x transfer interval value typically stationary ≤ 100,000 typically ≤ 10 km x 10 km x 50 m NOTE: Length x width x height. Use case one To keep a plant running, it is essential that the assets, such as pumps, valves, heaters, and instruments are maintained. Timely recognition of any degradation and continuous self-diagnosis of components are used to support and plan maintenance. Remote software updates enhance and adapt the components to changing conditions and advances in technology. A.2.3.4 Inspection in production systems An Edge Computing use case example: Digital twin based production quality maintenance: A digital twin is a virtual representation of a product or production systems. Digital twins are used to simulate, predict and optimize products and production systems. In future, digital twin production control system based on augmented reality based will be used in the factories. In this usecase, a digital twin’s digital and virtual model of a function combined with other physical data to simulate real-time aspects of how a system operates. A digital twin production control system can be automated using machine data and the AI/ML trained data after applying the AI/ML algorithm and further processing. The processed output can be translated to a control command back to the device by a control function running on the edge cloud. In another case, using telemetry data as input, the digital twin model’s output may be fed to an AR server for sending low latency AR streams toward the manual operator in the factory production area. At the same time, it can further be utilized as input by an AI/ML model. A process control function can compare the machine data (example:position, rotation level, speed, sensor data, high-speed photography etc.) and perhaps a high-resolution video from the manufacturing line and if necessary, it can send commands for corrective measure. In this example, the process control functions reside at the edge infrastructure and the inspection related corrective input is sent back to the production system control function. Corrective actions/commands for misalignments from the processed output can be sent in two ways: 1. Manual process with AR server: In this case the service performance requirements should follow the table A.2.4.2-1. 2. Automatic process with AI/ML: This usecase and service performance requirements are described below in table A.2.3.4 The general high-level service requirements of the edge computing usecase for the digital twin based production inspection: • High bandwidth wireless data for both uplink and downlink ◦ exact number depends on video encoding, frame rate and video-resolution requirements • Timing accuracy and low latency ( <=20ms) • High availability of the communication network • Security requirements: Data encryption, connection authentication, user authorization • QoS methods to ensure quality of service performance over different UE to Application connection sessions (video streaming, sensor data, control data) • UE Mobility and session continuity (optional) Table A.2.3.4: Service performance requirements for automated inspection Use case # Characteristic parameter Influence quantity Communication service availability: target value [%] Communication service reliability: mean time between failures End-to-end latency: maximum Message size [byte] Transfer interval: lower bound Transfer interval: target value Transfer interval: upper bound Survival time UE speed # of UEs Service area (note) 1 99.999 ≥ 1 year < target transfer interval value 20 – large packets -20 % of target transfer interval value <=20 ms +20% of target transfer interval value Variable depending upon vertical industry typically stationary < 5 typically typically ≤100 m x 100 m x 50 m NOTE: Length x width x height. Use case one The periodic telemetry data and video images are used from the digital twin in the production system for analysis and then the processed outcome is sent back to the system for any adjustment of the machine components. The following diagram explains the above digital twin usecase steps to manage the production in a factory (both manual and automated operations) • Low-latency AR overlays and incorporation of AI/ML techniques to identify manufacturing issues and improve product quality as well as to enable offline adjustments for optimization, adaptations, and preventive operations on the machines A.2.4 Human machine interfaces A.2.4.1 Mobile control panels Control panels are crucial devices for the interaction between people and production machinery as well as for the interaction with moving devices. These panels are mainly used for configuring, monitoring, debugging, controlling and maintaining machines, robots, cranes or complete production lines. In addition to that, (safety) control panels are typically equipped with an emergency stop button and an enabling device, which an operator can use in case of a safety event in order to avoid damage to humans or machinery. When the emergency stop button is pushed, the controlled equipment immediately comes to a safe stationary position. Likewise, if a machine, robot, etc. is operated in the so-called special ‘enabling device mode’, the operator manually keeps the enabling device switch in a special stationary position. If the operator pushes this switch too much or releases it, the controlled equipment immediately comes to a safe stationary position as well. This way, it can be ensured that the hand(s) of the operator are on the panel (and not under a moulding press, for example), and that the operator does―for instance―not suffer from any electric shock or the like. A common use case for this ‘enabling device mode’ is the installation, testing or maintenance of a machine, during which other safety mechanisms (such as a safety fence) are deactivated. Due to the criticality of these safety functions, safety control panels currently have mostly a wire-bound connection to the equipment they control. In consequence, there tend to be many such panels for the many machines and production units that typically can be found in a factory. With an ultra-reliable low-latency wireless link, it would be possible to connect such mobile control panels with safety functions wirelessly. This would lead to a higher usability and would allow for the flexible and easy re-use of panels for controlling different machines. The cycle times of the control application depends on the process/machinery/equipment whose safety has to be ensured. For a fast-moving robot, for example, end-to-end latencies are lower than for slowly moving linear actuators. Table A.2.4.1-1: Service performance requirements for mobile control panels Use case # Characteristic parameter Influence quantity Communication service availability: target value [%] Communication service reliability: mean time between failures End-to-end latency: maximum Service bitrate: user experienced data rate Message size [byte] Transfer interval: lower bound Transfer interval: target value Transfer interval: upper bound Survival time UE speed # of UEs Service area (note 1) 1 (note 3) 99.999 9 to 99.999 999 ~ 1 month < target transfer interval value – 40 to 250 – < 25 % of target transfer interval value 4 ms to 8 ms + 25 % of target transfer interval value target transfer interval value < 7.2 km/h TBD 50 m x 10 m x 4 m 2 (note 3) 99.999 9 to 99.999 999 ~ 1 month < target transfer interval value > 5 Mbit/s – – < 25 % of target transfer interval value < 30 ms + 25 % of target transfer interval value TBD < 7.2 km/h TBD TBD 3 (note 3) 99.999 9 to 99.999 999 ~ 1 year < target transfer interval – 40 to 250 – < 25 % of target transfer interval value < 12 ms + 25 % of target transfer interval value 12 ms < 7.2 km/h TBD typically 40 m x 60 m; maximum 200 m x 300 m NOTE 1: Length x width (x height). NOTE 2: The transfer interval is not so strictly periodic in these use cases. The transfer interval deviates around its target value within bounds. The mean of the transfer interval is close to the target value. NOTE 3: Communication may include two wireless links (UE to UE) Use case one Periodic, bi-directional communication for remote control. Examples for controlled units: assembly robots; milling machines. Use case two Aperiodic data transmission in parallel to remote control (use case one). Use case three Periodic, bi-directional communication for remote control. Examples for controlled units: mobile cranes, mobile pumps, fixed portal cranes. A.2.4.1A Mobile operation panels Operation and monitoring of machines, mobile robots, or production units via a mobile operation panel provides higher flexibility and comfort for human operators. A single mobile operation panel can be used to manage more than one production system due to its mobility in the factory. The mobile operation panel provides relevant information for configuration, control of industrial machines as well as monitoring of relevant data generated during the construction of a product. The monitoring data is generally considered to be less time-critical subsequently requiring non-real-time communication. On the other hand, the mobile operation panel supports safety-critical functions such as emergency stops or enabling or changing the position of robots and other machines. These functions are generally considered to have strict ultra-low latencies and reliable transmission requirements that must follow strict safety standards making them time-critical (real-time communication). Table A.2.4.1A-1: Service performance requirements for mobile operation panels Use case # Characteristic parameter Influence quantity Communication service availability: target value [%] Communication service reliability: mean time between failures End-to-end latency: maximum Service bitrate: user experienced data rate Direction (note 2) Message size [byte] Transfer interval: target value Survival time UE speed # of UEs Service area (note 1) 1 99.999 999 1 day < 8 ms 250 kbit/s Uplink Downlink 40 to 250 8 ms 16 ms quasi-static; up to 10 km/h 2 or more 30 m x 30 m 2 99.999 99 1 day < 10 ms < 1 Mbit/s Uplink < 1,024 10 ms ~10 ms quasi-static; up to 10 km/h 2 or more 30 m x 30 m 3 99.999 999 1 day 10 ms to 100 ms 10 kbit/s Uplink Downlink 10-100 10-100 ms transfer interval stationary 2 or more 100 m² to 2,000 m² 4 99.999 999 1 day < 1 ms 12 Mbit/s to 16 Mbit/s Downlink 10-100 1 ms ~1 ms stationary 2 or more 100 m² 5 99.999 999 1 day < 2 ms 16 kbit/s (UL) 2 Mbit/s (DL) Uplink Downlink 50 2 ms ~2 ms stationary 2 or more 100 m² 6 99.999 9 to 99.999 99 1 day up to [x] 12 Mbit/s Uplink Downlink 250 to 1,500 quasi-static; up to 10 km/h 2 or more 30 m x 30 m NOTE 1: Length x width. NOTE 2: The mobile operation panel is connected wirelessly to the 5G system. If the mobile robot/production line is also connected wirelessly to the 5G system, the communication includes two wireless links. Use case one Emergency Stop with periodic-deterministic communication for connectivity availability and aperiodic-deterministic communication for emergency stop events. Use case two Safety data stream with periodic deterministic communication. Use case three Visualization of Control with periodic deterministic communication. Use case four Motion Control with periodic deterministic communication. Use case five Haptic feedback data stream with periodic deterministic communication. Use case six Manufacturing data stream with mixed traffic. A.2.4.2 Augmented reality It is envisioned that in future smart factories and production facilities, people will continue to play an important and substantial role. However, due to the envisaged high flexibility and versatility of the Factories of the Future, shop floor workers should be optimally supported in getting quickly prepared for new tasks and activities and in ensuring smooth operations in an efficient and ergonomic manner. To this end, augmented reality may play a crucial role, for example for the following applications: - monitoring of processes and production flows; - step-by-step instructions for specific tasks, for example in manual assembly workplaces; - ad hoc support from a remote expert, for example for maintenance or service tasks. In this respect, especially head-mounted augmented-reality devices with see-through display are very attractive since they allow for a maximum degree of ergonomics, flexibility and mobility and leave the hands of workers free for other tasks. However, if such augmented-reality devices are worn for a longer period (e.g., one work shift), these devices have to be lightweight and highly energy-efficient while at the same time they should not become very warm. A very promising approach is to offload complex (e.g., video) processing tasks to the network (e.g., an edge cloud) and to reduce the augmented-reality head-mounted device’s functionality. This has the additional benefit that the augmented-reality application may have easy access to different context information (e.g., information about the environment, production machinery, the current link state, etc.) if executed in the network. Table A.2.4.2-1: Service performance requirements for augmented reality in human-machine interfaces Use case # Characteristic parameter Influence quantity Communication service availability: target value [%] Communication service reliability: mean time between failures End-to-end latency: maximum UE speed Service area (note) 1 > 99.9 ~ 1 month < 10 ms < 8 km/h 20 m x 20 m x 4 m NOTE: Length x width x height. Use case one Bi-directional message transmission between an augmented-reality device and an image processing server. A.2.5 Monitoring and maintenance A.2.5.1 Remote access and maintenance In factories of the future, there are needs to perform remote access and maintenance to devices and entities, for instance, by remote control centres. The devices and entities might be installed at geographically distributed locations. These devices typically have firmware/software which needs to be updated occasionally. Maintenance information also needs to be collected and distributed from/to these devices periodically. The devices can be both stationary and mobile. Device maintenance may happen in parallel to the actual production process and other communication services performed at the device side without any negative impact on these production communication services. Table A.2.5.1-1: Service performance requirements for remote access and maintenance Use case # Characteristic parameter Influence quantity Communication service availability: target value [%] Communication service reliability: mean time between failures End-to-end latency: maximum Service bitrate: user experienced data rate Message size [byte] Transfer interval: lower bound Transfer interval: upper bound Survival time UE speed # of UEs Service area (note) 1 – ~ 1 month – ≥ 1 Mbit/s – – – – ≤ 72 km/h ≤ 100 50 m x 10 m x 10 m NOTE: Length x width x height. Use case one Transmission of non-deterministic messages in parallel to other interactions. Example applications: software/firmware updates and exchange of maintenance information. A.3 (void) A.4 Electric-power distribution and Smart Grid A.4.1 Overview The energy sector is currently subject to a fundamental change, which is caused by the evolution towards renewable energy, i.e. an increasing number of power plants based on solar and wind power. These changes lead to bi-directional electricity flows and increased dynamics of the power system. New sensors and actuators are being deployed in the power system to efficiently monitor and control the volatile conditions of the grid, requiring real-time information exchange [11][12]. The emerging electric-power distribution grid is also referred to as Smart Grid. The smartness enhances insight into both the grid as a power network and the grid as a system of systems. Enhanced insight improves controllability and predictability, both of which drive improved operation and economic performance and both of which are prerequisites for the sustainable and scalable integration of renewables into the grid and the potential transition to new grid architectures. Smart Grid benefits spread across a broad spectrum but generally include improvements in: power reliability and quality; grid resiliency; power usage optimisation; operational insights; renewable integration; insight into energy usage; and safety and security. Overviews of (future) electric-power distribution can be found elsewhere in the literature [13][14]. A.4.2 Primary frequency control Primary frequency control is among the most challenging and demanding control applications in the utility sector. A primary frequency control system is responsible for controlling the energy supply injected and withheld to ensure that the frequency is not deviating more than 0.02 % from the nominal value (e.g., 50 Hz in Europe). Frequency control is based on having sensors for measuring the features in all parts of the network at all points where energy generation or storage units are connected to the grid. At these points, electronic power converters, also known as inverters, are equipped with communication units to send measurement values to other points in the grid such as a frequency control unit, or receive control commands to inject more, or less, energy into the local network. With the widespread deployment of local generation units, i.e. solar power units, or wind turbines, hundreds of thousands of such units, and their inverters, may have to be connected in a larger power distribution network. Primary frequency control is carried out in one of three ways: 1) Centralised control, all data analysis and corrective actions are determined by a central frequency control unit. 2) Decentralised control, the automatic routine frequency control is performed by the individual local inverter based on local frequency values. Statistics and other information is communicated to the central frequency control unit. 3) Distributed control, the automatic routine frequency control is performed by the individual local inverter based on local and neighbouring frequency values. Statistics and other information are communicated to the central frequency control unit. Table A.4.2-1: Service performance requirements for primary frequency control Use case # Characteristic parameter Influence quantity Communication service availability: target value [%] Communication service reliability: mean time between failures End-to-end latency: maximum Message size [byte] Transfer interval: target value Survival time # of UEs Service area 1 99.999 TBD ~ 50 ms ~ 100 ~ 50 ms TBD ≤ 100,000 several km2 up to 100,000 km2 Use case one Periodic communication service supporting message exchange for primary frequency control. A.4.3 Distributed voltage control In the evolution towards 100 % renewable electric power production, the objective of voltage control is to balance the voltage in future low voltage distribution grids connecting local loads and prosumers, as well as energy storage facilities. The aim is to stabilise the voltage as locally as possible, so that decisions and control commands can be issued as quickly as possible. Distributed voltage control is a challenging and demanding control application. Consumer devices rely on having stable voltage levels to operate successfully. When future energy networks rely on thousands of local energy generation units relying mostly on solar and wind power, then it is crucial to stabilise the voltage levels in all segments of the distribution grid. Inverters, or electronic power converters, measure the voltage and power and change the amount of power injected into the grid, and they connect and disconnect end points from the distribution network. Distributed control means that the automated voltage control shall be performed by the local voltage control units based on local and neighbouring voltage and impedance values. Statistics and other information shall be communicated to the central distribution management system, though. Table A.4.3-1: Service performance requirements for distributed voltage control Use case # Characteristic parameter Influence quantity Communication service availability: target value [%] Communication service reliability: mean time between failures End-to-end latency: maximum Message size [byte] Transfer interval: target value Survival time # of UEs Service area 1 99.999 TBD ~ 100 ms ~ 100 ~ 200 ms TBD ≤ 100,000 several km2 up to 100,000 km2 Use case one Periodic communication service supporting message exchange for distributed voltage control. A.4.4 Distributed energy automation A.4.4.1 Distributed automated switching for isolation and service restoration A power distribution grid fault is a stressful situation. There are self-healing solutions for automated switching, fault isolation, and service restoration. Furthermore, these solutions are ideally suited to handle outages that affect critical power consumers, such as industrial plants or data centres. Supply interruptions must be fixed within less than a second for critical power consumers. Automated solutions are able to restore power supply within a few hundred milliseconds. Figure A.4.4.1-1: Depiction of a distribution ring and a failure (flash of lighting) The FLISR (Fault Location, Isolation & Service Restoration) solution consists of switch controller devices which are especially designed for feeder automation applications that support the self-healing of power distribution grids with overhead lines. They serve as control units for reclosers and disconnectors in overhead line distribution grids. The system is designed for using fully distributed, independent automated devices. The logic resides in each individual feeder automation controller located at the poles in the feeder level. Each feeder section has a controller device. Using peer-to-peer communication among the controller devices, the system operates autonomously without the need of a regional controller or control centre. However, all self-healing steps carried out will be reported immediately to the control centre to keep the grid status up to date. The controllers conduct self-healing of the distribution line in typically 500 ms by isolating the faults. Peer-to-peer communication via IEC 61850 GOOSE (Generic Object Oriented Substation Event) messages provides data as fast as possible (Layer 2 multicast message). They are sent periodically (in steady state, with changing interval time in fault case) by each controller to several or all other controllers of the same feeder and are not acknowledged. The service bit rate per controller is low in steady state, but GOOSE bursts with high service bit rate do occur, especially during fault situations. GOOSE messages are sent by several or all controller units of the feeder nearly at the same point in time during the fault location, isolation and service restoration procedure with a low end-to-end latency. The associated (a)periodic communication KPIs are provided in Table A4.4.1-1. Table A.4.4-1.1: Service performance requirements for distributed automated switching for isolation and service restoration Use case # Characteristic parameter Influence quantity Communication service availability: target value [%] Communication service reliability: mean time between failures End-to-end latency: maximum Service bitrate: user experienced data rate Message size [byte] Transfer interval: target value Survival time UE speed # of UEs Service area (note 1) 1 (note 2) 99.999 9 – < 5 ms 1 kbit/s (steady state) 1.5 Mbit/s (fault case) < 1,500 < 60 s (steady state) ≥ 1 ms (fault case) transfer interval (one frame loss) stationary 20 30 km x 20 km 2 > 99.999 % - 20 ms (note 2) - < 100 - - stationary ≤ 100/km2 several km2 NOTE 1: Length x width NOTE 2: UE to UE communication (two wireless links) Use case one GOOSE (a)periodic deterministic communication service supporting bursty message exchange for fault location, isolation, and service restoration. Use case two Typically event-driven, aperiodic deterministic communication service supporting fault detection and isolation. A.4.4.2 Distributed automation without GOOSE If the control of electrical power distribution components is performed from a central system entity, the controlled entities can be operated in a way that a controlled service restoration is possible without the use of GOOSE. Though this is not as effective as the communication has less strict requirements, this form of distribution automation is nevertheless effective, and it is also compliant with IEC standards and widely deployed in energy systems. The associated KPI is provided in Table A.4.4.2-1. Table A.4.4.2-1: KPI for distributed automation without use of GOOSE Use case # Characteristic parameter Influence quantity Communication service availability: target value [%] Communication service reliability: mean time between failures End-to-end latency: maximum Service bitrate: user experienced data rate Message size [byte] Transfer interval: target value Survival time UE speed # of UEs Service area 1 99.999 – 100 ms to 2 s 9.6 to100 – – – – Concentrated rural: 70.8; Dispersed rural and semi-urban: 7.6; rural support: 0.048; urban: 11.0 several km2 Use case one Distributed automation without use of GOOSE using a centralized architecture. A.4.4.3 Intelligent distributed feeder automation Intelligent distributed feeder automation system which supported by 5G connections is designed to realize intelligent judgment, analysis, fault location, fault isolation and non-fault area power supply restoration operations. As illustrated in the Figure A.4.4.3-1, the distributed feeder automation system is mainly composed of a distribution master station, a distribution terminal, switch stations, and the communication system (UEs in the substations, 5G network, plus the data network). The distribution master station is mainly used for information gathering and human-computer interaction, and the distributed terminals are used for the collection of feeder status information and judgment, fault location, isolation, as well as power supply restoration based on this information. Distributed terminal actions are reported to the distribution master station. The 5G communication system enables communication among the distribution terminals. The distribution master station is usually connected to the 5G system via a data network, which is out of 3GPP scope. Figure A.4.4.3-1: Example of intelligent distributed feeder automation The distribution master station manages multiple distributed terminals. Each distributed terminal is served by a 5G UE to exchange the collected data with other distributed terminals. From an application perspective, the communication between distributed terminals is peer-to-peer. The 5G communication service availability needs to be very high. Therefore, at least two communication links are usually deployed for hot standby or for transmitting data synchronously between two distributed terminals. The associated KPI is provided in Table A.4.4.3-1. Table A.4.4.3-1: KPI for intelligent distributed feeder automation Use case # Characteristic parameter Influence quantity Communication service availability: target value [%] Communication service reliability: mean time between failures End-to-end latency: maximum Service bitrate: user experienced data rate Message size [byte] Transfer interval: target value Survival time UE speed # of UEs Service area 1 99.999 – Normal: 1 s; Fault: 2 ms (note 2) 2 M to10 M (note 1) – Normal: 1 s; Fault: 2 ms (note 2) – – 54/km2 (note 3) 78/km2 (note 4) several km2 NOTE 1: The KPI values are sourced from [29]. NOTE 2: It is the one-way delay from a distributed terminal to 5G network. NOTE 3: When the distributed terminals are deployed along overhead line, about 54 terminals will be distributed along overhead lines in one square kilometre. NOTE 4: When the distributed terminals are deployed in power distribution cabinets, there are about 78 terminals in one square kilometre. Use cases #1: Intelligent distributed feeder automation A.4.4.4 High-speed current differential protection High-speed current differential protection, which is required for sub-millisecond fault detection, is another typical use case of power distribution automation. The approach utilises differential current measurements to significantly reduce fault detection time. The protection relays exchange the current samples via the 5G system. Each relay then compares the sent and received samples to determine if a fault has occurred in a protected area. This is done in order to identify and isolate a fault in the grid. The sampling rate varies and is dependent on the algorithms designed by the manufacturers. A protection relay collects the current samples (with the typical message size of up to 245 bytes) at a frequency of 600 Hz, 1200 Hz, 1600 Hz, or 3000 Hz. The exchange of measurement samples is done in a strictly cyclic and deterministic manner. With the sampling rate of 600 Hz, the transfer interval is 1.7 ms and the required bandwidth 1.2 Mbit/s; for 1200 Hz, the transfer interval is 0.83 ms and the required bandwidth 2.4 Mbit/s. The maximum allowed end-to-end delay between two protection relays is between 5 ms and 10 ms, depending on the voltage (see IEC 61850-90-1 for more details [28]). For some legacy systems, the latency usually is set to 15 ms. The associated KPIs are provided in Table A.4.4.4-1. Table A.4.4.4-1: KPIs for high speed current differential protection Use case # Communication service availability End-to-end latency: maximum (note) Service bitrate: user experienced data rate Message size [byte] Transfer interval: target value Survival time UE speed UE density [#/km2)] Service area 1 > 99.999 % 15 ms 2.5 Mbit/s < 245 ≤ 1 ms transfer interval (one frame loss) stationary ≤ 100/km2 several km2 2 > 99.999 % 15 ms 1.2 Mbit/s < 245 ≤ 2 ms transfer interval (one frame loss) stationary ≤ 100/km2 several km2 3 > 99.999 % 10 ms 2.5 Mbit/s < 245 ≤ 1 ms transfer interval (one frame loss) stationary ≤ 100/km2 several km2 4 > 99.999 % 10 ms 1.2 Mbit/s < 245 ≤ 2 ms transfer interval (one frame loss) stationary ≤ 100/km2 several km2 5 > 99.999 % 5 ms 2.5 Mbit/s < 245 ≤ 1 ms transfer interval (one frame loss) stationary ≤ 100/km2 several km2 6 > 99.999 % 5 ms 1.2 Mbit/s < 245 ≤ 2 ms transfer interval (one frame loss) stationary ≤ 100/km2 several km2 NOTE : UE-to-UE communication. Use case #1: High-speed current differential protection with a sampling rate of 1200 Hz for legacy systems. Use case #2: High-speed current differential protection with a sampling rate of 600 Hz for legacy systems. Use case #3: High-speed current differential protection with a sampling rate of 1200 Hz under voltage condition 1 (see IEC 61850-90-1[28] for more details). Use case #4: High-speed current differential protection with a sampling rate of 600 Hz under voltage condition 1 (see IEC 61850-90-1[28] for more details). Use case #5: High-speed current differential protection with a sampling rate of 1200 Hz under voltage condition 2 (see IEC 61850-90-1[28] for more details). Use case #6: High-speed current differential protection with a sampling rate of 600 Hz under voltage condition 2 (see IEC 61850-90-1[28] for more details). A.4.5 Smart grid millisecond-level precise load control Precise Load Control is the basic application for smart grid. When serious HVDC (high-voltage direct current) transmission fault happens, Millisecond-Level Precise Load Control is used to quickly remove interruptible less-important load, such as electric vehicle charging piles and non-continuous production power supplies in factories. Table A.4.5-1: Service performance requirements for smart grid millisecond-level precise load control Use case # Characteristic parameter Influence quantity Communication service availability: target value [%] Communication service reliability: mean time between failures End-to-end latency: maximum Service bitrate: user experienced data rate Message size [byte] Transfer interval: target value Survival time UE speed # of UEs Service area 1 99.999 9 – < 50 ms 0.59 kbit/s 28 kbit/s < 100 n/a (note) – stationary 10 km-² to 100 km-² TBD NOTE: event-triggered Use case one A non-periodic deterministic communication service between control primary station and load control terminals for removing interruptible less-important load quickly. A.4.6 Distributed energy storage Distributed power generation includes various power sources such as solar, wind, fuel cells, and gas. Distributed power generation typically comes with a low power density and entails thus typicall a decentralised deployment. Decentralisation causes technical problems and challenges Smart Grid operators. When distributed power generation is connected to the elctrical grid, the energy flow becomes more complicated as the user often is both an electricity consumer and producer (a so-called “prosumer”). Therefore, the current in the electricity grid can change direction at different locations of the grid and at different times of the day. The information exchange in a distributed energy grid does not only include power-generation-related data, but also control commands for the distributed energy storage equipment. An example for such a command is “change the load characteristics to realise a flexible electricity grid” etc. Figure A.4.6-1 Example of a distributed-energy storage grid Figure A.4.6-1 shows an example of distributed-energy storage grid. The distributed-energy storage grid needs to exchange information among the distributed-energy storage management platform (DESMP) and distributed-energy devices (DEDs). The DED is a plug-and-play device and periodically collects its energy information, such as battery energy, charge and discharge status, energy alarm information, etc. The DED then transfers this information via 5G UE to the DESMP. The DESMP regularly manages the DEDs, e.g., the DESMP monitors the DEDs working status, controls the DEDs working modes, or configures the DEDs energy parameters etc. The associated KPIs are provided in Table A.4.6-1. Table A.4.6-1: Communication service performance requirements ‒ data for distributed energy storage Use case# Characteristic parameter Influence quantity Communication service availability: target value Communication service reliability: mean time between failures End-to-end latency: maximum Service bit rate: user experienced data rate Message size [byte] Transfer interval: target value Survival time UE speed # of UEs Service area 1 > 99.9 % DL: < 10 ms UL: < 10 ms UL: > 16 Mbit/s (urban); 640 Mbit/s (rural) DL: > 100 kbit/s (note 1) UL: 800 kbyte UL: 10 ms – stationary > 10/km2 (urban); > 100/km2 (rural) (note 2) several km2 2 > 99.9 % DL: < 10 ms UL: < 1 s UL: > 128 kbit/s (urban); 10.4 Mbit/s (rural); DL: > 100 kbit/s (note 1) UL: 1.3 Mbyte DL: > 100 kbyte UL: 1000 ms – stationary > 10/km2 (urban); > 100/km2 (rural) (note 2) several km2 3 > 99.9 % DL: < 10 ms UL:< 1 s (rural) DL: > 100 kbit/s UL: > 5 Gbit/s (note 3) stationary > 100/km2 several km2 NOTE 1: Service bit rate for one energy storage station. NOTE 2: Activity storage nodes/km2. This value is used for deducing the data volume in an area that features multiple energy storage stations. The data volume can be calculated with the following formula (current service bit rate per storage station) x (activity storage nodes/km2) + (video service bit rate per storage station) x (activity storage nodes/km2). NOTE 3: The downlink user experienced data rate is calculated as follows: 12.5 Mbytes/s x 50(containers) x 8 = 5 Gbit/s Use case#1: Distributed energy storage ‒ periodic communication for monitoring Use case#2: Distributed energy storage ‒ periodic communication for data collection Use case#3: Distributed energy storage ‒ aperiodic video communication A.4.7 Advanced metering Instead of recording and sending metering data from a wired electricity meter unit, electricity metering collecting can be executed by a UE-integrated smart meter unit. Smart meter units can send real-time metering data to a server in the utility through mobile networks. In this way, the power enterprise―based on the analysis of the user’s power consumption behavior―gives the user power consumption suggestions, which fosters the user’s power consumption and energy saving habits. The electric smart meters monitor relevant user energy status and deliver the status data to a measurement data management system (MDMS). The MDMS sends control commands according to its policy and the status of the data collected from the smart meters. The MDMS commands include tripping, closing permission, alarm, alarm release, power protection, and power protection release. Accurate-fee control is one of the basic services of advanced metering. When the electric power user doesn’t pay her electric fee on time, the MDMS can cut off the power supply. And when there is a need for temporary power supply for this user, the MDMS can recover the power supply. This operation requires real-time interaction between the electric smart meter and the MDMS. Due to massive number of electricity meters, it is estimated that in the near future, the amount of this kind of interaction will increase 5 to 10 times. The associated KPIs are provided in Table A.4.7-1. Table A.4.7-1: Communication KPI for advanced metering Use case# Characteristic parameter Influence quantity Communication service availability: target value Communication service reliability: mean time between failures End-to-end latency: maximum Service bit rate: user experienced data rate Message size [byte] Transfer interval: target value Survival time UE speed # of UEs Service area 1 > 99.99 Accuracy fee control: < 100 (note 1); General information data collection: < 3000 UL: < 2 M DL: < 1 M – – – stationary < 10 000/km2 (note2) – NOTE 1: One-way delay from 5G IoT device to backend system. The distance between the two is below 40 km (city range). NOTE 2: It is the typical connection density in today city environment. With the evolution from centralised meters to socket meters in the home, the connection density is expected to increase 5 to 10 times. Use case#1: Advanced metering A.4.8 Smart distribution transformer terminal A smart distribution transformer terminal is usually deployed in a distribution transformer area. The terminal can support multiple energy applications simultaneously. Multiple kinds of energy data are collected by the terminal and then delivered to a energy application platform. Figure A.4.8.1-1 illustrates a workflow example for a smart distribution transformer terminal. Figure A.4.8-1: Example of a smart distribution transformer terminal workflow In general, the connections between the smart distribution transformer terminal and the energy application platform are provided by the 5G system. The connections between energy end equipment and smart distribution transformer terminal may be provided by 5G system. In this case, about 300 to 500 energy end devices are connected to one smart distribution transformer terminal. The average service bit rate between the smart distribution transformer terminal and an energy end device is more than 2 Mbit/s in uplink for each application. The related communication distance is between 100 m and 500 m. The associated KPI is provided in Table A.4.8-1. Table A.4.8-1: Key Performance for Smart Distribution Transformer Terminal Use case# Characteristic parameter Influence quantity Communication service availability: target value Communication service reliability: mean time between failures End-to-end latency: maximum Service bit rate: user experienced data rate Message size [byte] Transfer interval: target value Survival time UE speed # of UEs Service area 1 >99.99% – 10 ms, 100 ms, 3 s (note 2) > 2 Mbit/s (note 1) – – – – 500 in the service area (note 3) Communication distance is from 100 m to 500 m, (outdoor, indoor, and deep indoor) NOTE 1: It is the smart metering application data rate between the Smart Distribution Transformer Terminal and energy end equipment. Once there are multiple smart grid applications, it is required more data rate. NOTE 2: It depends on different applications supported by the Smart Distribution Transformer Terminal. The less the latency is, the more applications can be supported. NOTE 3: The distribution area can be calculated as 3.14 x range2 and in general is between 0.031 km2 and 0.79 km2. Use case#1: smart distribution transformer terminal A.4.9 Distributed energy resources and micro-grids Distributed energy resources (DER) become increasingly important. The potentially large number of DERs will have an impact on security, stability, and operation efficiency of the energy grid. The integration of DERs into the energy grid poses many challenges for the involved communication system. To incorporate more renewable and alternative energy sources, the communication infrastructure must have the ability to easily handle an increasing amount of data traffic or service requests and must provide a real-time monitoring and control operation for these distributed energy resources. A reliable communication between the DERs is crucial. When it comes to communications architecture, IEC 61850 is a widely used standard for automation and equipment of power utilities and DER, specifically for defining protocols for IEDs (Intelligent electronic devices) at electrical substations The IEC 61850 standard specifies the timing constraints for messages typically used in substations. GOOSE (Generic Object Oriented Substation Events) and SV (Sampled Values) messages are assumed as time critical messages. They have the tightest deadlines (maximum allowed transfer time) among all IEC 61850 messages, corresponding to 3 ms. While GOOSE is typically used for transfering information related to monitoring and control functions (circuit breaker status etc.), SV is used for transfering measurement samples of current and voltage signals. The SV protocol works on a periodic information transmission model, sending messages at a fixed rate. For protection purposes, the default rate is 4000 or 4800 messages per second for 50 and 60 Hz power systems, respectively. On the other hand, the GOOSE protocol operates in a sporadic information transmission model, where a continuous flow of data is maintained to increase communication reliability. The typical sizes of GOOSE and SV messages are160 and 140 bytes, respectively. GOOSE messages are transmitted in two different modes: (1) safe operation: 1 message per second (service bit rate = 1.28 kbit/s); (2) emergency operation: 32 messages per second (service bit rate = 41.0 kbit/s). SV messages are transmitted at much higher rate, namely 4800 messages per second (service bit rate = 5.4 Mbit/s). The associated KPIs are provided in Table A.4.9-1. Table A.4.9-1: Key Performance for Distributed energy resources (DER): using SV (Sampled Values) message Use case# Characteristic parameter Influence quantity Communication service availability: target value Communication service reliability: mean time between failures End-to-end latency: maximum Service bit rate: user experienced data rate Message size [byte] Transfer interval: target value Survival time UE speed 1 99,9999 % – < 3 ms 4.5 Mbit/s 140 ≤ 1 ms transfer interval stationary 2 99,9999 % – < 3 ms 5.4 Mbit/s 140 ≤ 1 ms transfer interval stationary 3 > 99.9999 % – < 3 ms – 160 – – stationary NOTE: UE to UE communication is assumed. Use case#1: Distributed energy resources and micro-grids: using SV(sample value) message with 50Hz Use case#2: Distributed energy resources and micro-grids: using SV(sample value) message with 60Hz Use case#3: Distributed energy resources and micro-grids: using GOOSE message A.4.10 Ensuring uninterrupted communication service availability during emergencies During emergencies, public mobile land networks (PLMNs) may restrict network access, which may lead to a prohibitevly low communication service availability for machine-type communication (MTC) for Smart Grid applications. An example is communication for microgrids. Microgrids are separate parts of a power grid that can be controlled and operated individually in a so-called island mode, or together with other parts of the power grid. The idea is to prioritise Smart Grid-related communication in order to ensure reliable and available communication for selected devices during emergency conditions. Existing features of a mobile network can be used to differentiate MTC of devices in a microgrid from other kind of MTC traffic or human-to-human communication. These features can help these microgrid devices to have communication service during emergencies. The communication among the microgrid devices enables co-ordination of DERs, which help the DERs can autarkically implement recovery of an islanded microgrid. The associated KPI is provided in Table A.4.10-1. Table A.4.10-1: Key Performance for uninterrupted MTC service availability Characteristic parameter (KPI) Influence quantity Communication service availability: target value Communication service reliability: mean time between failures Max Allowed End-to-end latency (note 1; (note 2) Service bit rate: user-experienced data rate (note 2) Message size [byte] Survival time UE speed # of UEs Service Area 99.999 9 % – 100 ms < 1 kbit/s per DER – – Stationary – – NOTE 1: Unless otherwise specified, all communication includes 1 wireless link (UE to network node or network node to UE) rather than two wireless links (UE to UE). NOTE 2: It applies to both UL and DL unless stated otherwise. A.5 Central power generation A.5.1 Overview This domain comprises all aspects of centralised power generation, i.e. the centralised conversion of chemical energy and other forms of energy into electrical energy. Typical electric-power outputs are 100 MW and more. Examples for pertinent systems are large gas turbines, steam turbines, combined-cycle power plants, and wind farms. The planning and installation of respective equipment and plants as well as the operation, monitoring and maintenance of these plants is encompassed by this vertical domain. A.5.2 Wind power plant network Table A.5.2-1: Service performance requirements for wind power plant network Use case # Characteristic parameter Influence quantity Communication service availability: target value [%] Communication service reliability: mean time between failures End-to-end latency: maximum Packet error ratio UE speed Service area 1 99.999 999 9 ~ 10 years 16 ms < 10-9 stationary several km2 Use case one Communication in support of closed-loop cyber-physical control in a wind farm. The wind farm can be deployed offshore. NOTE: This type of communication service can be provided via a wired connection. A.6 Connected hospitals or medical facilities A.6.1 Overview The traditional value chain for the medical device industry, which historically has been driven by innovation and research and development, is currently witnessing a shift in the landscape. As governments and health insurers worldwide implement measures to control costs, public hospitals are operating on tighter budgets, while private facilities are receiving lower reimbursements. In the developed world, decisions that used to be the sole preserve of doctors are now also made by regulators, hospital administrators, and other non-clinicians. This broader set of influencers comes with different objectives, e.g. the prioritization of cost effectiveness or even just costs. This shift in focus from volume-based healthcare to value-based healthcare has led medical devices companies to move to business models based on providing clinical value with cost efficiency. Technological progress and better infrastructures, in particular high-quality wireless networks, have fed this business model transformation, allowing coordinated therapies, services, and health analytics and enabling efficient outcome measurement solutions. On this matter, 5G enables shifting care location from hospitals to homes and others lower cost facilities which mechanically translates into more savings. Additionally, another example showing that 5G can enable cost savings required by the medical industry can be found inside hospitals where wireless transmission of low latency data streams improves operating room planning, enable streamlining equipment usage and simplifies operating theater implementation. A.6.2 Robotic Aided Surgery Robotic aided surgery is particularly suitable to invasive surgical procedures that require delicate tissue manipulation and access to areas with difficult exposure. It is achieved through complex systems that translate the surgeon’s hand movements into smaller, precise movements of tiny instruments that can generally bend and rotate far more than a human hand is capable of doing inside the patient’s body. In addition, those systems are usually able to filter out hand tremor and therefore allow more consistent outcomes for existing procedures, and more importantly the development of new procedures currently made impractical by the accuracy limits of unaided manipulation. A typical robotic setup for telesurgery can be depicted as follows. Figure A.6.2-1: Typical Robotic Surgery System Setup The robot and the surgeon’s console can be co-located in the same operating room in which case they communicate through a NPN, or, in another deployment option, when specialists and patients are far from each other (hundreds of kilometres) they can exchange data through communication services delivered by PLMNs. The depicted medical application can be instantiated at either side or in the Cloud. Its role consists in: - Generating appropriate haptic feedback based on instrument location, velocity, effort measurements data and images issued by surgical instruments and 3D pre-operative patient body model. This allows to provide tactile guidance by constraining where the instruments (scalpel, etc.) can go. - Filtering motion control commands for better closed loop stability Typical surgery robotic systems can have around 40 actuators and the same number of sensors which allows to compute the data rate requires in each direction in order to execute a given movement. Human sensitivity of touch is very high, tactile sensing has about 400 Hz bandwidth, where bandwidth refers to the frequency of which the stimuli can be sensed. This is why, in general, haptic feedback systems operate at frequencies around 1,000 Hz. This rate naturally applies to the update of all information used in the generation of the haptic feedback, e.g. instruments velocity, position … Therefore, the robot control process involves: - The surgeon console periodically sending a set of points to actuators - Actuators executing a given process - Sensors sampling velocity, forces, positions, … at the very same time and returning that information to the surgeon console at the rate of 1 kHz As opposed to machine to machine communication, robotic aided surgery implies there is a human being in the middle of the control loop, which means that the console generates new commands based on the system state collected in the previous 1 kHz cycle and also on surgeon’s hand movement. Each equipment involved in a robotic telesurgery setup (endoscopes, image processing system, displays, motion controller and haptic feedback systems) is synchronized thanks to a common clock either external or provided by the 5G system. The synchronization is often achieved through dedicated protocols such as e.g. PTP version 2 and allows to e.g. guarantee the consistency of the haptic feedback and displayed images at the master console, or enable the recording and offline replay of the whole procedure. Table A.6.2-1: Service performance requirements for motion control and haptic feedback Use case # Characteristic parameter Influence quantity Communication service availability: target value [%] Communication service reliability: Mean Time Between Failure End-to-end latency: maximum Bit rate Direction Message Size [byte] Transfer Interval Survival time UE speed # of active UEs (note1) Service Area 1 > 99.999 999 > 10 years < 2 ms 2 Mbit/s to 16 Mbit/s network to UE; UE to network 250 to 2,000 1 ms transfer interval stationary 1 room 2 > 99.999 9 > 1 year < 20 ms 2 Mbit/s to 16 Mbit/s network to UE; UE to network 250 to 2,000 1 ms transfer interval stationary < 2 per 1,000 km2 national Note 1: The upper limit of UEs’ density is provided for large service areas to address non-uniform distributions of UEs, while an absolute number of UEs is provided for small service areas. Use case one Periodic communication for the support of precise cooperative robotic motion control and haptic feedback in case of robotic aided surgery where the surgeon console and the robot are collocated in the same operating room Use case two Periodic communication for the support of cooperative robotic motion control and haptic feedback in case of telesurgery. In this case, the surgeon console and the robot are not collocated and communicate with each other through a connection established over a PLMN possibly spanning an entire country. Relaxed requirements imply that much less complex surgical procedures are achievable in use case 2 than in use case 1. It shall be noted that this use case also involves more experienced and trained surgeons, who can cope with longer latencies in the communication system. A.6.3 Robotic Aided Diagnosis Robotic aided diagnosis involves a remote expert in a large central hospital who controls a diagnosis robotic system deployed in a local medical facility. Such robotic systems can be e.g.: - Haptic feedback tool used for palpating and deployed in e.g. a Mobile Specialist Practise facility - Ultrasound probe deployed in an ambulance or a medical facility A typical robotic setup for tele diagnosis can be depicted as follows: Figure A.6.3-1: Typical Robotic Surgery System Setup Specialists and patients are far from each other (typically dozens of kilometres) and can exchange data through communication services delivered by PLMNs. The depicted medical application can be instantiated at either side or in the Cloud. Its role consists in: • Generating appropriate haptic feedback based on instrument location, velocity, effort measurements data and images issued by instruments. • Filtering motion control commands for better closed loop stability Table A.6.3-1: Service performance requirements for motion control and haptic feedback Use case # Characteristic parameter Influence quantity Communication service availability: target value [%] Communication service reliability: Mean Time Between Failure End-to-end latency: maximum Bit rate Direction Message Size [byte] Transfer Interval Survival time UE speed # of active UEs Service Area 1 > 99.999 >> 1 month (< 1 year) < 20 ms 2 Mbit/s to 16 Mbit/s network to UE; UE to network ~80 < 20 ms per 100 km2 transfer interval stationary < 20 per 100 km2 regional Use case one Periodic communication for the support of precise cooperative robotic motion control and haptic feedback in case of robotic aided diagnosis where the expert and the patient are not collocated and communicate with each other through a connection established over a PLMN. A.7 Positioning A.7.1 Overview of positioning in industrial use cases Positioning is particularly important for cyber-physical control applications in vertical domains like factories. The reason for this is that mobile devices and mobile assets are becoming increasingly common in the flexible production and subsequently the need for real-time locations data is increasing. In this context, positioning is especially important for warehousing and logistics processes, autonomous driving systems and fleet management and flexible adaptation in production. In the best case all relevant goods and products are continuously tracked from the moment they are received to the moment they are made available. The tracking process provides the relevant context information that is needed for real-time control and optimization of the material flow and subsequent production processes. In this scenario, autonomous driving systems fetch parts from the warehouse independently and transport them to flexible assembly cells on the shop floor. As part of the flexible fleet management system, these autonomous driving systems are continuously localized and move quickly and in constant interaction with their environment. In the process, production machinery and assembly cells and their given status are monitored seamlessly while relevant objects like tools and workpieces being localized. This makes it possible to adapt quickly to changes in circumstances. The result is flexible, autonomously controlled production that is capable of adapting to new situations at any time. Wireless positioning for human machine interfaces like AR/VR should also be possible. The requirements for positioning vary widley between different use cases. A.7.2 Low Power High Accuracy Positioning Low power high accuracy positioning is an integral part of a considerable number of industrial applications. The total energy needed for a specific operation time for such a low power high accuracy positioning optimized IoT-device is a combination of energy for positioning (varies depending on the used positioning method), energy for communication/synchronization and a difficult to predict factor to take additional losses through e.g. security, power management, microcontroller, and self-discharge of batteries into account. Examples of target applications for low power high accuracy positioning are asset tracking in process automation, tracking of vehicles, and tool tracking. Table A.7.2-1 gives an indication of the required operation time of the 5G enabled IoT device and duty cycle of the updated position information for different use cases. Table A.7.2-1: Low power high accuracy positioning use cases Use Case # Horizontal accuracy Corresponding service level (22.261) Positioning interval/ duty cycle battery life time/ minimum operation time 1 10 m Service Level 1 on request 24 months 2 2 m to 3 m Service Level 2 < 4 seconds > 6 months 3 < 1 m Service Level 3 no indication 1 work shift - 8 hours (up to 3 days, 1 month for inventory purposes) 4 < 1 m Service Level 3 1 second 6 - 8 years 5 < 1 m Service Level 3 5 seconds - 15 minutes 18 months 6 < 1 m Service Level 3 15 s to 30 s 6 - 12 months 7 30 cm Service Level 5 250 ms 18 months 8 30 cm Service Level 5 1 second 6 - 8 years (no strong limitation in battery size) 9 10 m Service Level 1 20 minutes 12 years (@20mJ/position fix) Use case one Process automation: Dolly tracking (outdoor). Use case two Process automation: Asset tracking. Use case three Flexible modulare assembly area: Tool tracking in flexible, modular assembly areas in smart factories. Use case four Process automation: Sequence container (Intralogistics). Use case five Process automation: Palette tracking (e.g. in turbine construction). Use case six Flexible modulare assembly area: Tracking of workpiece (in- and outdoor) in assembly area and warehouse. Use case seven Flexible modulare assembly area: Tool assignment (assign tool to vehicles in a production line, left/right) in flexible, modular assembly area in smart factories. Use case eight Flexible modulare assembly area: Positioning of autonomous vehicles for monitoring purposes (vehicles in line, distance 1.5 meter). Use case nine (Intra-)logistics: Asset tracking Annex B (informative): Communication service errors B.1 Introduction IEC 61784-3-3 describes fundamental communication errors that can be identified for applications with functional safety requirements [3]. The description of these communication errors is adjusted to field buses. These errors may however also occur in other communication systems. As explained in Annex C, some of these errors are also used for the assessment of communication services that do not support safety-critical applications. B.2 Corruption Messages may be corrupted due to errors within an application, due to errors on the transmission medium, or due to message interference. NOTE 1: Message error during transfer is a normal event for any standard communication system; such events are detected with high probability at receivers by use of, for instance, hash functions. NOTE 2: Most communication systems include protocols for recovery from transmission errors, so these messages will not be classed as 'loss' until recovery or repetition procedures have failed or are not used. NOTE 3: If the recovery or repetition procedures take longer than a specified deadline, a message is classed as "unacceptable delay". See also the discussion in Clause C.3. NOTE 4: In the very low probability event that multiple errors result in a new message with correct message structure (for example addressing, length, hash function such as CRC, etc.), the message will be accepted and processed further. Evaluations based on a message sequence number or a time stamp can result in fault classifications such as unintended repetition, incorrect sequence, unacceptable delay, insertion [3]. B.3 Unintended repetition Due to an error, fault, or interference, not updated messages are accidentally repeated. NOTE 1: Repetition by the sender is a common procedure when an expected acknowledgment/response is not received from a target station, or when a receiver detects a missing message and asks for it to be resent. In some cases, the lack of response can be detected, and the message repeated with minimal delay and no loss of sequence, in other cases the repetition occurs later and arrives out of sequence with other messages. NOTE 2: Some field buses use redundancy to send the same message multiple times or via multiple alternate routes to increase the probability of good reception [3]. B.4 Incorrect sequence Due to an error, fault, or interference, the predefined sequence (for example natural numbers, time references) associated with messages from a source is incorrect. NOTE 1: Field bus systems can contain elements that store messages (for example FIFOs in switches, bridges, routers) or use protocols that can alter the sequence (for example, by allowing messages with high priority to overtake those with lower priority). NOTE 2: When multiple sequences are active, such as transmission of messages from different source entities or reports relating to different object types, these sequences are monitored separately, and errors can be reported for each sequence [3]. B.5 Loss Due to an error, fault or interference, a message or acknowledgment is not received [3]. B.6 Unacceptable deviation from target end-to-end latency Messages may be delayed or advanced beyond their permitted arrival time window. Causes for this behaviour include errors in the transmission medium, congested transmission lines, interference, and applications sending messages in such a manner that communication services are delayed or denied. Message errors can be recovered in the following ways using scheduled or cyclic scans, for instance, in field buses: a) immediate repetition; b) repetition using spare time at the end of the cycle; c) treating the message as lost and waiting for the next cycle to receive the next value. In case of (a), all subsequent messages in that cycle are slightly delayed, while in case (b) only the resent message is delayed. Cases (a) and (b) are often not classed as an unacceptable deviation from the target end-to-end latency. Case (c) would be classed as an unacceptable delay for cyclic, distributed automation functions, unless the cycle repetition interval is short enough to ensure that delays between cycles are not significant and that the next cyclic value can be accepted as a replacement for the missed previous value before the survival time expiries (see Clause C.3) [3]. B.7 Masquerade Due to a fault or interference, a message is inserted that relates to an apparently valid source entity, so a non-safety related message may be received by a safety-related participant, which then treats it as safety related. NOTE: Communication systems used for safety-related applications can use additional checks to detect masquerade, such as authorised source identities and pass-phrases or cryptography [3]. B.8 Insertion Due to a fault or interference, a message is received that relates to an unexpected or unknown source entity. NOTE: These messages are additional to the expected message stream, and because they do not have expected sources, they cannot be classified as correct, unintended repetition, or incorrect sequence [3]. B.9 Addressing Due to a fault or interference, a safety-related message is delivered to the incorrect safety related participant, which then treats reception as correct [3]. Annex C (informative): Characterising communication services C.1 Modelling of communication in automation C.1.1 Area of consideration For our discussion of communication in automation we apply a definition of the area of consideration for industrial radio communication that is found elsewhere in the literature [4]. This definition is illustrated in Figure C.1.1-1. NOTE: Blue objects: communication system; other objects: automation application system. Figure C.1.1-1: Abstract diagram of the area of consideration for industrial radio communication Here, a distributed automation application system is depicted. This system includes a distributed automation application, which is the aggregation of several automation functions. These can be functions in sensors, measurement devices, drives, switches, I/O devices, encoders etc. All of these functions contribute toward the control of physical objects. Field bus systems, industrial Ethernet systems, or wireless communication systems can be used for connecting the distributed functions. The essential function of these communication systems is the distribution of messages among the distributed automation functions. For cyber-physical control applications, the dependability of the entire communication system and/or of its devices or its links is essential. Communication functions are realised by the respective hardware and software implementation. In order for the automation application system to operate, messages need to be exchanged between spatially distributed application functions. For that process, messages are exchanged at an interface between the automation application system and the communication system. This interface is termed the reference interface. Required and guaranteed values for characteristic parameters, which describe the behavioural properties of the radio communication system, as well as some influence quantities refer to that interface. The conditions that influence the behaviour of wireless communication are framed by the communication requirements of the application (e.g., end-to-end latency), the characteristics of the communication system (e.g., output power of a transmitter), and the transmission conditions of the media (e.g., signal fluctuations caused by multipath propagation). General requirements from the application point of view for the time and failure behaviour of a communication system are mostly related to an end-to-end link. It is assumed in the present document that the behaviour of the link is representative of the communication system as a whole and of the entire scope of the application. C.1.2 Logical link C.1.2.1 Nature and function Starting with the general approach mentioned in Subclause C.1.1, the logical link can be regarded as a possible asset within the area of consideration (see Figure C.1.1-1). The conditions under which its functions are to be performed are vital for the dependability of the automation application system. Figure C.1.2.1-1: The concept of a logical link This is the link between a logical end point in a source device and the logical end point in a target device. Logical end points are elements of the reference interface, which may group several logical end points together. The intended function of the logical link is the transmission of a sequence of messages from a logical source end point to the correct logical target end point. This is achieved by transforming each message into a form that fosters error-free transmission. The transmission process includes certain processes, for instance repetitions, in order to fulfil the intended function. After transmission, the transported package(s) is converted back into a message. The message is to be available and correct at the target within a defined time. The sequence of messages at the target is to be the same as the sequence at the source. The functional units, which are necessary to fulfil this function are shown, in Figure C.1.2.1-1. Figure C.1.2.1-2: The asset "logical link" The required function can be impaired by various influences, which can lead to communication errors. Such errors are described elsewhere in the literature [4][5]. A summary of these errors is provided in Annex A. The occurrence of one of these errors influences the values of the relevant dependability parameters of the logical link. C.1.2.2 Message transformation The present document addresses both OSI-layer-3 (IP) and OSI-layer-2 communication. The model in Figure C.1.2-1 can be used for describing both cases. The implementation of communication functions is split between a higher communication layer (HCL) and a lower communication layer (LCL). The partition of the layer for the two traffic options discussed in the present document is provided in Table C.1.2.2-1. This difference is of importance when discussing the implications of the service performance requirements in Clause 5 and Annex A for the network performance (see Clause C.5). Table C.1.2.2-1: Partition into higher communication layer and lower communication layer OSI level at which the traffic occurs Levels comprised by the higher communication layer Levels comprised by the lower communication layer 3 4 to 6 1 to 3 2 3 to 6 (note) 1 to 2 NOTE: In some vertical application, level 3 to 6 are not implemented. The messages to be transmitted for the intended function of a logical link are defined by strings of characters with a certain semantic. Such a character string is handed over as user data at the reference interface for transmission. If the number of characters in a message is too great for it to be transmitted as a unit, the message is divided for transmission into several packets (fragmentation). C.1.2.3 Communication device The communication devices—together with the physical link—determine the function and thus the dependability of the logical link. The function of the communication devices is the correct sending and correct receipt of sequences of messages. The asset "communication device" is depicted in Figure C.1.2.3-1. Figure C.1.2.3-1: Asset "communication device" C.1.2.4 Communication system The communication system as an asset represents a quantity of logical links whose message transmissions are implemented by wireless devices via one or more media. The communication system function to be provided consists in transmitting messages for all the logical links in the distributed application. This function is to be performed for a defined period, the operating time of the automation application. In an automation application system, it is paramount that requirements pertaining to logical links are fulfilled. These requirements and the conditions can be very different from one case and implementation to the other. The functions (services and protocols) for individual logical links can therefore also be different. Despite these differences, some of the logical links share communication devices and media. C.2 Communication service description C.2.1 Overview Tables C.2.2-1, C.2.3-1 summarise candidate interface parameters for the description of the communication service performance. The lists are grouped according to whether the parameter stands for automation characteristic parameters (Table C.2.2-1) or influence quantities (Table C.2.3-1). The meaning of the columns and rows is explained after each table. NOTE 1: Not all parameters in Table C.2.2-1 and Table C.2.3-1 would be used in a service call. NOTE 2: Ingress and egress in this clause are in reference to the communication service interface between the source application and the communication service interface (ingress) and the communication service and the target application (egress). C.2.2 Characteristic parameters Table C.2.2-1: Candidate characteristic parameters for the dependable communication service interface Parameter name Typical metric (unit) Traffic class (note) Deterministic periodic communication Deterministic aperiodic communication Non-deterministic communication Communication service availability Minimum availability (dimensionless) X X X End-to-end latency Target value and timeliness (ms) X X X Communication service reliability Mean time between failures (days) X X X Service bit rate Target value (bit/s); user experienced data rate (bit/s); time window (s) – X X Update time Target value and timeliness X – – NOTE: – application requirements (KPIs). X: applies; –: does not apply. Parameter description Communication service availability This parameter indicates if the communication system works as contracted ("available"/"unavailable" state). The communication system is in the "available" state as long as the availability criteria for transmitted packets are met. The service is unavailable if the packets received at the target are impaired and/or untimely (e.g. update time > stipulated maximum). If the survival time (see Table C.2.3-1) is larger than zero, consecutive impairments and/or delays are ignored until the respective time has expired. End-to-end latency This parameter indicates the time allotted to the communication system for transmitting a message and the permitted timeliness. Communication service reliability Mean time between failures is one of the typical indicators for communication service reliability. This parameter states the mean value of how long the communication service is available before it becomes unavailable. For instance, a mean time between failures of one month indicates that a communication service runs error-free for one month on average before an error/errors make the communication service unavailable. Usually, an exponential distribution is assumed. This means, there will be several failures where the time between two subsequent errors is below the mean value (1 month in the example). Communication service availability and communication service reliability (mean time between failures) give an indication on the time between failures and the length of the failures. Service bit rate a) deterministic communication The target value indicates committed data rate in bit/s sought from the communication service. This is the minimum data rate the communication system guarantees to provide at any time, i.e. in this case target value = user experienced data rate. b) non-deterministic communication The target value indicates the target data rate in bit/s. This is the information rate the communication system aims at providing on average during a given (moving) time window (unit: s). The user experienced data rate the lower data rate threshold for any of the time windows. Update time Applicable only to periodic communication, the update time indicates the time interval between any two consecutive messages delivered from the egress (of the communication system) to the application. Traffic classes In practice, vertical communication networks serve applications exhibiting a wide range of communication requirements. In order to facilitate efficient modelling of the communication network during engineering, and for reducing the complexity of network optimisation, disjoint QoS sets have been identified. These sets are referred to as traffic classes [6]. Typically, only three traffic classes are needed in industrial environments [6], i.e. - deterministic periodic communication; - deterministic aperiodic communication; and - non-deterministic communication. Deterministic periodic communication stands for periodic communication with stringent requirements on timeliness of the transmission. Deterministic aperiodic communication stands for communication without a pre-set sending time. Typical activity patterns for which this kind of communication is suitable are event-driven actions. Non-deterministic communication subsumes all other types of traffic. Periodic non-real time and aperiodic non-real time traffic are subsumed by the non-deterministic traffic class, since periodicity is irrelevant in case the communication is not time-critical. Usage of the parameters in Table C.2.2-1 Control service request and response; monitoring service response and indication. C.2.3 Influence quantities Table C.2.3-1: Candidate application influencing parameters for the dependable communication service interface Parameter name Typical metric (unit) Traffic class (note) Usage of this parameter Deterministic periodic communication Deterministic aperiodic communication Non-deterministic communication Burst Maximum user data length (byte) and line rate of the communication service interface (bit/s) – X X Service request and response; monitoring service response and indication Message size Maximum or current value (byte) X (X) (X) Service request and response; non-deterministic data transmission; deterministic aperiodic data transmission Service time interval Start (time) and end (time) X X X Service request and response Survival time Maximum (s) X X – Service request and response Transfer interval Target value and timeliness (s) X – – Service request and response NOTE: X: applies; (X): usually does not apply; –: does not apply. Parameter description Burst The transmission of, for instance, program code and configuration data may be handed to the 3GPP system as data burst. In this case, the ingress data rate exceeds the capacity of the network, which implies that some of the data has to be stored within the ingress node of the communication system before it can be transmitted to the egress interface(s). However, the application consuming the communication service requires that the data of such a burst needs to be transmitted completely. This is in contrast to periodic data transmission, where new messages overwrite old ones. Typical metrices for bursts: maximum user data length and line rate of the communication service interface. Message size The user data length indicates the (maximum) size of the user data packet delivered from the application to the ingress of the communication system and from the egress of the communication system to the application. For periodic communication this parameter can be used for calculating the requested user-experienced data rate. If this parameter is not provided, the default is the maximum value supported by the PDU type (e.g. Ethernet PDU: maximum frame length is 1,522 octets, IP PDU: maximum packet length is 65,535 octets). Service time interval Describes the start and end time of a communication service. Note that there are other ways to describe the service time interval numerically, for instance as the tuple [start time, service duration]. Survival time The maximum survival time indicates the time period the communication service may not meet the application's requirement before the communication service is deemed to be in an unavailable state. NOTE 1: The survival time indicates to the communication service the time available to recover from failure. This parameter is thus tightly related to maintainability [7]. Transfer interval Applicable only to periodic communication, the transfer interval indicates the time elapsed between any two consecutive messages delivered by the automation application to the ingress of the communication system. C.3 Up time and up state vs. down state and down time The assessment of periodic deterministic communication services is based on the assessment of successful message transmission over a logical communication link. Message transmission is either: - successful, if it is correctly and timely received, or - unsuccessful, if it is incorrectly received, lost or untimely. Up time and down time can be derived from received messages. As far as timely received messages are correct, the logical communication link status is up. If a message loss or an incorrectly or untimely received message is detected the logical communication link status is down. To denote up and down states the terms “up time interval” and “down time interval”, or alternatively “available” and “unavailable” may be used. An example of the relation between logical communication link status, communication service status and application status is presented in Figure C.3-1. Figure C.3-1: Relation between logical communication link, communication service and application statuses (example with lost messages) The flow of events in Figure C.3-1 is as follows: a) The logical communication link is up and running (blue line is UP). A source device starts sending periodic messages to a target device (orange arrows), on which an automation function (application) is running. The communication service is, from the point of view of the target application, in an up state (violet line is UP) and so is the application (green line is UP). b) The logical communication link status changes to down state if it no longer can support end-to-end transmission of the source device's messages to the target device in agreement with the negotiated communication requirements. Once the application on the target device senses the absence (or unsuccessful reception) of expected messages ("Deadline for expected message" in Figure C.3-1), it will wait a pre-set period before it considers the communication service to be unavailable ; this is the so-called survival time. The survival time can be expressed as - a period or, - especially with cyclic traffic, as maximum number of consecutive incorrectly received or lost messages. c) If the survival time has been exceeded, both the communication service and the application transition into a down state (violet and green lines change to DOWN in Figure C.3-1). The application will usually take corresponding actions for handling such situations of unavailable communication services. For instance, it will commence an emergency shutdown. Note that this does not imply that the target application is "shut off"; rather it transitions into a pre-defined state, e.g. a safe state. In the safe state, the target application might still listen to incoming packets or may try to send messages to the source application. d) Once the logical communication link status is in the up state again (blue line in Figure C.3-1 changes to UP), the communication service state as perceived by the target application will change to the up state. The communication service is thus again perceived as available (violet line changes to UP in Figure C.3-1). The state of the application, however, depends on the counter measures taken by the application. The application might stay in down state if it is in a safe state due to an emergency shutdown. Or, the application may do a recovery and change to up state again. The time needed for the application to return to the up state after the communication service is restored is shown as “Application recovery time” in Figure C.3-1. The availability of the communication service is calculated using the accumulated down time. For instance, in case the communication service is expected to run for a time T, the unavailability U of the communication service can be calculated as Where Δti is the length of the i-th downtime interval of the communication service within the time period T. The communication service availability A can then be calculated as A = 1–U. C.4 Timeliness as an attribute for timing accuracy C.4.1 Overview There are several time parameters in dependability assessment. A required value is specified for every time parameter. This value can be a maximum, mean, modal, minimum etc. Typically, there is a deviation from the desired value to the actual value. Jitter is often used to characterise this variation. Since jitter generally is used for characterising the behaviour of a measured parameter, for instance the scatter of measured end-to-end latencies ("the world as it is"), it can be quite confusing to use it for formulating service performance requirements ("the world as we want it to be"). What is needed is a concept and related parameters that allow for formulating and talking about the end-to-end latency requirements in Clause 5 and Annex A. The most important attribute is timeliness. Timeliness can be formulated a permitted interval for the actual value of the time parameter. Accuracy, earliness and lateness describe the allowed deviation from a target value. Accuracy is the magnitude of deviation. It can be negative (early) or positive (tardy). C.4.2 Network latency requirement formulated by use of timeliness In 5G networks, the end-to-end latency KPI is a critical KPI in order to ensure that the network can deliver the packet within a time limit specified by an application: not too early and not too late. In cyber-physical automation, the arrival time of a specific packet should be strictly inside a prescribed time window. In other words, a strict time boundary applies: [minimum end-to-end latency, maximum end-to-end latency]. Otherwise, the transmission is erroneous. Although most use cases that require timely delivery only specify the maximum end-to-end latency, the minimum latency is also sometimes prescribed. In the latter case, a communication error occurs if the packet is delivered earlier than the minimum end-to-end latency. An example for a related application is putting labels at a specific location on moving objects, and the arrival of a message is interpreted as a trigger for this action. In other words, the application does not keep its own time, but interprets the message arrival as clock signal. Maximum and minimum end-to-end latency alone do not disclose which value is preferred, i.e. target value. The next three subclauses introduce concepts help with relating maximum end-to-end latency, minimum end-to-end latency, and target vale to each other. C.4.3 Timeliness Timeliness is described by a time interval (see Figure C.4.3-1). The interval is restricted by a lower bound (tLB) and an upper bound (tUB). This interval contains all values tA that are within an accepted "distance" to the target value tR. Figure C.4.3-1: Timeliness function A message reception is considered in time, if it is received within the timeliness interval. If it is received outside the timeliness interval, the message reception is considered invalid. This is related to the communication error "unacceptable deviation from target end-to-end latency" (see Subclause B.6). In other words, maximum end-to-end latency = tUB and minimum end-to-end latency = tLB. Timeliness is related to deviation (see Subclause C.4.4), the lower bound tLB is related to earliness (see Subclause C.4.5), and the upper bound tUB is related to lateness (see Subclause C.4.6). C.4.4 Deviation The term deviation describes the discrepancy between an actual value (tA) and a target value (tR). Deviation(tA) = tA – tR. Figure C.4.4-1 shows two examples. The target value is 10 time units (tR = 10) in both cases. In the first case (blue) the actual value measures 12 time units (tA = 12). The difference of both amounts to +2 time units, which means that the deviation is 2 time units [Accurracy(tA) = 2]. The second case (purple) shows the actual value as 9 time units (tA = 9). The difference of both amounts to -1 time unit, which means that the deviation is –1 time units [Accuracy(tA) = –1]. Figure C.4.4-1: Examples for accuracy values Figure C.4.4-2 shows the deviation with respect to the target time (t). The following applies: Deviation(t) < 0 for t < tR; that is, the arrival is early. Deviation(t) = 0 for t = tR; that is, the arrival is as desired, i.e. on time. Deviation(t) > 0 for t > tR; that is, the arrival is late (see also C.4.6) Figure C.4.4-2: Accuracy function C.4.5 Earliness Earliness describes how early the actual value is: earliness is greater than 0 if the actual value is less than the target value (see Figure C.4.5-1). The following applies: Eearliness(tA) = tR – tA = –Deviation(tA) for tA < tR; Eearliness(tA) = 0 for tA tR. In an example, the target value is 10 time units (tR = 10), and the actual value is 7 time units (tA = 7). The difference of both is 3 time units with respect to being early. That means that the earliness is 3 time units [Eearliness(tA) = 3]. Figure C.4.5-1: Earliness function C.4.6 Lateness Lateness describes how much greater the actual value is than the target value: lateness is greater than 0 if the actual value is greater than the desired value (see Figure C.4.6-1). The following applies: L(tA) = 0 for tA tR; L(tA) = tA–tR = Deviation(tA) for tA > tR. In an example, the target value is 10 time units (tR = 10), and the actual value measures 14 time units (tA = 14). The difference of both is 4 time units with respect to being late. That means that the lateness is 4 time units [L(tA) = 4]. Figure C.4.6-1: Lateness function C.4.7 Conclusion Using the concepts of earliness and lateness (see Subclauses C.4.5 and C.4.6, respectively), the maximum and minimum end-to-end latency can be rewritten as follows. Maximum end-to-end latency = target end-to-end latency + maximum lateness; Minimum end-to-end latency = target end-to-end latency – maximum earliness. C.5 Communication service terminology w.r.t. 5G network and vertical applications This section clarifies the wording and terminology with respect to communication interfaces that are relevant for vertical applications. Because the 3GPP network does not cover the complete ISO-OSI communication stack, it is important to distinguish between - the vertical applications’ point of view, and - the 3GPP network’s point of view. In this section, the relation between those two is clarified. Figure C.5-1 shows a simplified version of the communication stack. The PHY layer, the MAC layer and some parts of the IP layer are part of the 3GPP network. The layers that are part of the 3GPP network are referred to as lower communication layers (LCL). The communication stack also includes an application. The OSI layers related to providing data to the application are referred to as the higher communication layers (HCL). The interface between LCL and HCL is referred to as communication service interface (CSIF). For the assessment of the overall system performance, it is important to differentiate between the 3GPP network’s performance (i.e., including only the LCL and measured at the CSIF) and the overall system performance including the application layer (i.e., including both, the LCL and the HCL). In Figure C.5-1, the orange arrow depicts the vertical application’s point of view. The blue arrows indicate two options to measure the 3GPP network’s performance, i.e., including and excluding the IP layer. Figure C.5-1: Network performance measurements at different communication system interfaces (CSIF) Figure C.5-2 illustrates how messages are transmitted from a source application device (e.g., a programmable logic controller) to a target application device (e.g. an industrial robot). The source application function (AF) is executed in the source operating system (OS) and hands over a message to the application layer interface of the source communication device. In the higher communication layers (HCL), which are not part of the 3GPP system, the data is processed. From the HCL the data is transferred to the lower communication layers (LCL), which are part of the 3GPP system. After transmission through the physical communication channel and the LCL of the target communication device, the data is passed to the HCL and lastly to the target application device. Characteristic parameters with respect to time are defined in Figure C.5-2. From 3GPP system point of view: - Transfer interval of 5G system: Time between the arrival of two pieces of data at the source CSIF. - End-to-end latency: Time measured from the point when a piece of data received at the CSIF in the source communication device until the same piece of data is passed to the CSIF in the target communication device. From vertical application point of view: - Transfer interval of vertical application: Time between the transmission of two successive pieces of data from the source application. - Transmission time: Time measured from the point when a piece of data is handed from the application layer interface of the source application device, until the same piece of data is received at the application layer interface of the target application device. - Update time: Time between the reception of two consecutive pieces of data at the application layer interface to the target application device. If not stated otherwise, the terms "end-to-end latency" and "transfer interval" refer to the 3GPP system / 5G network parameters in this document. Figure C.5-2: Relation between application device and communication device (downlink example). Annex D (informative): 5G in industrial automation: different and multiple time domains for synchronization D.1 Description The required synchronization precision is usually given as the maximum absolute value of the time difference between sync master and any device in the synchronisation domain (time domain or clock domain). A common example is a synchronisation precision of ≤ 1 µs. This is equivalent to ± the precision value, so ±1 µs between sync master and any device in the synchronisation domain, resulting in two times this value as maximum absolute time difference between any two devices in the synchronisation domain (2 µs in the example). An industrial automation network generally consists of two distinct time domains. First is the global time domain. This is the time used for overall synchronization in the system (e.g. the factory). It is used to align operations and events chronologically. Industrial automation uses the term universal time domain [20] for the global time domain described in this document. Global time is known as a synonym for universal time in industrial automation. Global time is called wall clock in certain areas and standards. The synchronization precision is typically ≤ 1µs [20]. In some areas, a precision of ≤ 100 µs might be sufficient for the global time domain if a working clock with precision of ≤ 1 µs is available. The assigned timescale is usually the International Atomic Time (TAI, temps atomique international), based on the precision time protocol (PTP) epoch (starting from 1 January 1970 00:00:00 TAI) [22]. While there is usually only one global time, multiple global time domains are possible. Clock synchronization in the global time domain usually applies to all UEs within the industrial facility in industrial automation. That is, a global time domain covers usually the industrial facility. Second is the working clock domain. Working clock domains are constrained in size. They often consist of a single machine or a set of neighbouring machines that physically collaborate. The restricted size allows very precise time synchronization (≤1µs) with efficient network components. Synchronisation to a working clock is used to align e.g. production lines, production cells, or machines/functional units. In these cases, the application synchronizes locally within the working clock domains (Figure D.1-1), allowing precise synchronization with more efficient components. A global time domain usually contains multiple working clock domains. The starting point (epoch) is the start of the working clock domain. Figure D.1-1: Global time domain and working clock domains The assigned timescale of a working clock domain is arbitrary (timescale ARB [22]). Therefore, different working clock domains may have different timescales and different synchronisation accuracy and precision. Robots, motion control applications, numeric control, and any kind of clocked / isochronous application rely on the timescale of the working clock domain to make sure that actions are precisely interwoven as needed. Clock synchronization in the working clock domain is constraint in size. A specific working clock domain will contain only a subset of the UEs within the industrial facility. Often, the UEs of the working clock domain are connected to the same gNB. However, it is also possible that a working clock domain contains multiple neighbouring gNBs. This depends on the actual use case and its vertical application. Devices may be part of multiple time domains leading to overlapping working clock domains. The required precision (usually ≤ 1 µs) is between the sync master and any sync devices of the clock domain, both, global time domain and working clock domain. Clock domains might be called sync domains in certain areas and standards. D.2 Merging of working clock domains One key issue of the integration of TSN and 5G wireless networks that has to be handled is mobility. The integration of 5G wireless communication into the industrial communication infrastructure allows for mobility in the manufacturing process. This mobility enhances flexibility in the manufacturing process, e.g. through adding certain manufacturing capabilities on-demand by having a machine move to the respective production line. This means that machines that are synchronized to different working clock domains may need to interact with each other. The following scenario illustrates this. After the mobile machine has arrived at the intended location and is stationary again, the two interacting working clock domains have to be synchronized with each other. Otherwise interaction might not be possible without interfering with ongoing operations. An example is an autonomous mobile handling robot adding parts to an assembly line. Without synchronization between both, correct placement of the parts would be impossible. However, it is not feasible to schedule these interactions beforehand. Therefore, the interaction between different working clock domains requires a concept for handling the communication. TSN provides already mechanisms for this. The 5G systems and the UEs need to provide an interface in order to exchange information of the clock domain. Figure D.2-1: Working clock domain interactions "Merge" and "Separate" When members of different working clock domains interact, there are two possible options (Figure D.2-1). Which option is used depends on the application and its requirements. - Merge: The working clock domains merge into one. This option can be used in applications where synchronization is critical, e.g. high precision robots interacting with each other. - Separate: The members of the different working clock domains interact while keeping their own separate time synchronizations. This option can be used in applications where synchronization is non-critical, e.g. an AGV collecting finished products from a production line. D.3 Time synchronization with 5G networks For the time synchronization with 5G networks, we consider two possible options. The 5G system uses the IEEE 802.1AS sync domains [22]: In this case, the 5G system provides a media dependent interface to the IEEE 802.1AS sync domain, which the application can use to synchronize to the sync domain. In the IEEE 802.1AS standard [22], a similar concept is detailed in the MDSyncSend and MDSyncReceive structures. The 5G system provides the working clock domains and global time domain: In this case, the 5G system has to provide an interface which the application can use to derive their working clock domain or global time domain. A device can belong to multiple working clock domains. An application can use each of these as the reference clock for synchronization (reference clock model). NOTE: The required precision (usually ≤ 1 µs) is between the sync master and any sync device of the clock domain. Annex E (informative): Audio and Video Production E.1 Description AV production includes television and radio studios, outside and remotely controlled broadcasts, live newsgathering, sports events, music festivals, among others. All of these applications require a high degree of reliability, since they are related to the capturing and transmission of data at the beginning of a production chain. This differs drastically when compared to other multimedia services because the communication errors will be propagated to the entire audience that is consuming that content both live and recorded for later distribution. Furthermore, the transmitted data is often post-processed with nonlinear filters which could actually amplify defects that would be otherwise not noticed by humans. Therefore, these applications call for uncompressed or only slightly compressed data, and very low probability of errors. These devices will also be used alongside existing technologies which have a high level of performance and so any new technologies will need to match or improve upon the existing workflows to drive adoption of the technology. The performance aspects that are covered by/in TS 22.263 [27] (Service requirements for Video, Imaging and Audio for professional applications) also target the latency that these services experience. In recent years, production facilities have moved from bespoke unidirectional highly specialised networks to IP based systems and software-based workflows. This migration is expected to continue, and wireless IP connectivity is key to a number of these workflows. Typical set ups require multiple devices such as cameras, microphones and control surfaces that require extremely close synchronisation to maintain consistency of pictures and audio. Such clock synchronization requirements are captured in clause 5.6. Often devices need to communicate directly to each other for instance a camera to a monitor or a microphone to a PA system. Video and audio applications also require extremely high quality of service metrics as the loss of a single packet can cause picture or sound breakup in the downstream processing or distribution. Often this is a legal, regulatory or contractual agreement to maintain a high quality, stable and clear video or audio signal. E.2 Multiple source wireless studio This use case will deploy a multiple camera studio of approximately 1,000 m2 (~5 cameras) where wired and wireless functionalities currently provided by traditional infrastructure technologies are likely to be deployed using a standalone non-public network. A combination of IP enabled wired and wireless cameras working at both HD and UHD resolutions will be deployed in a studio. Associated equipment such as video monitors, prompting systems, camera control will be provided over the 5G network. Camera timing and synchronisation will be provided over the 5G system. As well as video, audio will be sourced from both wired and wireless microphones incl. control/monitoring and combined with the video to produce high quality synchronised AV content. 5G will also be deployed to control lighting and camera robotics. Talkback intercom systems will be deployed using low latency multicast links. Today’s digital AV network transport is typically handled separately for wireless and wired transfers (see figure E.1.2-1). Wireless AV transmissions are implemented with application specific solutions that allow deterministic data transport of a single isolated audio or video link. Wired AV transmissions are Ethernet / IP based. Quality of service in AV IP networks is mainly achieved with IP DiffServ / DSCP based prioritization of packets in network switches. This method is sufficient for most AV use cases since jitter resulting from packet collisions is small, for example in the order of 10 µs per concurring data stream in Gbit Ethernet. Figure E.2-1: Typical AVPROD setup The microphones and cameras can be co-located in a broadcast centre in which case they would communicate through a LAN or NPN. For remote production operations the mixing and production console may be separated by some distance (existing examples are cross continental. In this instance they may communicate via a PLMN or combination of PLMN and WAN networks. Some approaches may also deploy main (leader) equipment at the broadcast centre with secondary (follower) equipment at the location site to reduce latency. Other aspects of this workflow may also include robotic control where both the physical position (height, direction and tilt) and the technical control (focus, zoom, iris, colour) of a device of a camera, microphone or light may be controlled remotely. In this instance round trip latency of < 20ms is required in order for an operator to see a move reflected at his control position as it is made. It is important to note that these are a combination of automated robotics (pre-programmed moves) and manually controlled robotics (following an unpredictable event such a sport). E.3 Timing use in AV production applications Timing of multiple devices such as microphones and camera is also critical. Timing signals are used in 2 separate ways. - To maintain synchronisation between devices so that electronic shutters on cameras operate at the same time and frequency and that when cutting between any two cameras pointed at the same source no discernible jumps can be seen. This requires accuracy within the frame boundary of a given video signal. A single frame of video at 120 Hz would require a clock accurate to within 8 ms. - To timestamp an IP packet carrying a video or audio sample. Existing standards and workflows for AVPROD rely on IEEE 1588 PTP timing with a SMPTE media profile applied. This requires a clock accurate to within 1 µs Figure E.3-1 Typical IP based timing set up for AVPROD Annex F (informative): Relation of reliability and communication service availability Availability and reliability are used both in 3GPP and vertical industries, but with different meanings. Communication service availability addresses the availability of a communication service. This definition follows the vertical standard IEC 61907 [7]. On the other hand, reliability is a 3GPP term and addresses the availability of a communication network. The relation of both terms is depicted in figure F-1 for a mobile network. Figure F-1: Illustration of the concepts reliability and communication service availability. As depicted, reliability covers the communication-related aspects between two nodes (here: end nodes), while communication service availability addresses the communication-related aspects between two communication service interfaces. This might seem to be a small difference, but this difference can lead to situations, where reliability and communication service availability have different values. Example: traffic gets "stuck" The related scenario is depicted in figure F-2. Figure F-2: Example in which reliability and communication service availability have different values. Packets are reliably transmitted from the communication service interface A to end node B, but they are not exposed at the communication service interface B. This scenario addresses unicast communication from application A to B. The packets are handed over at the communication service interface A from the application to the communication network, and the packets are then transmitted to the end node B. In this example, the packets received by end node B are not exposed at the communication service interface B. So, even if all packets that are handed over to end node A are successfully delivered to end node B within the time constraint required by the targeted service (reliability = 100 %), the communication service availability is 0% since no packets arrive at the "end", namely the communication service interface B. Example: packets dropped at the communication service interface The related scenario is depicted in figure F-3. Figure F-3: Example in which reliability and communication service availability have different values. Only half of the packets handed over to the end node A are actually transmitted to end node B and then handed over to application B at the communication service interface B. This scenario describes unicast communication of evenly interspersed packets from application A to B. The packets are handed over at the communication service interface A from the application to the communication network, and the packets are then transmitted to the end node B. However, only every second packet is actually successfully handed over to end node A and then transmitted to end node B. Thus, only half of the packets arrive at application B. Note though that the reliability of the mobile network is 100%, since all packets transmitted by end node A are delivered to end node B within the time constraint required by the targeted service. However, depending on the agreed QoS, the communication service availability can be of the same value as the reliability or much lower. For instance, if the agreed survival time is equal to or larger than the end-to-end latency, reliability and communication service availability are equal. However, if the survival time is smaller, the reliability is two times the communication service availability. Note that the shortest time interval over which the communication service availability should be calculated is the sum of maximum allowed end-to-end latency and survival time. Annex G (informative): Change history Change history Date Meeting TDoc CR Rev Cat Subject/Comment New version 2018-05 SA1#82 S1-181551 – – – Skeleton for TS 22.104 ("Service requirements for cyber-physical control applications in vertical domains") 0.0.0 2018-05 SA1#82 S1-181552 – – – Includes agreements at SA1#82, Dubrovnik, Croatia 0.1.0 2018-08 SA1#83 S1-182344 – – – Includes agreements at SA1#83, West Palm Beach, Florida 0.2.0 2018-11 SA1#84 S1-183276 – – – Includes agreements at SA1#83, Spokane, WA, USA, rapporteur’s clean-up 0.3.0 2018-12 SA#82 SP-181006 Presentation to SA for one-step approval 1.0.0 2018-12 SA#82 SP-181006 Raised to v.16.0.0 following SA approval 16.0.0 2019-03 SA#83 SP-190081 0003 2 F Clarifying UE-to-UE versus UE-to-network 16.1.0 2019-03 SA#83 SP-190081 0002 1 F Moving rail-bound mass transit requirements – shift from cyberCAV 16.1.0 2019-03 SA#83 SP-190081 0001 1 F Clean-up and corrections of TS 22.104 cyberCAV 16.1.0 2019-06 SA#84 SP-190299 0008 F Corrections to TS 22.104 v16.1.0 16.2.0 2019-06 SA#84 SP-190299 0006 2 F Add missing abbreviations to TS 22.104 16.2.0 2019-06 SA#84 SP-190299 0005 2 C Adding edge computing aspect 16.2.0 2019-06 SA#84 SP-190311 0009 1 C Adding vertical positioning requirements to TS 22.104 v16.1.0 17.0.0 2019-09 SA#85 SP-190807 0012 1 B Addition of a new synchronisation performance requirement 17.1.0 2019-09 SA#85 SP-190807 0011 2 B Addition of robotic aided surgery and diagnosis performance requirements 17.1.0 2019-09 SA#85 SP-190800 0023 1 A Correction of a figure number in Annex D.2 17.1.0 2019-09 SA#85 SP-190812 0010 B Add one more case for control-to-control communication 17.1.0 2019-09 SA#85 SP-190812 0013 1 B Network operation requirements 17.1.0 2019-09 SA#85 SP-190812 0015 3 B eCAV – Further 5G service requirements for Positioning 17.1.0 2019-09 SA#85 SP-190812 0018 2 B eCAV – Service performance requirements for Industrial Wireless Sensors 17.1.0 2019-09 SA#85 SP-190812 0016 2 B eCAV – further 5G service requirements for wired to wireless link replacement for smart manufacturing / Industry 4.0 17.1.0 2019-09 SA#85 SP-190812 0020 3 B eCAV – further 5G service requirements for network performance 17.1.0 2019-09 SA#85 SP-190857 0021 3 B ECAV - further 5G service requirements for ProSe communication for CAV 17.1.0 2019-09 SA#85 SP-190856 0019 3 B ECAV - further 5G service requirements for industrial Ethernet integration (clock synchronization, time-sensitive communication) 17.1.0 2019-12 SA#86 SP-191016 0027 5 B Addition of informative annex for AV Prod 17.2.0 2019-12 SA#86 SP-191020 0026 1 F Correction of CMED KPIs tables 17.2.0 2019-12 SA#86 SP-191028 0034 4 A Clarification of clock synchronicity requirements 17.2.0 2019-12 SA#86 SP-191028 0028 F Addition of transmission directions and movement characteristics 17.2.0 2019-12 SA#86 SP-191028 0030 1 A Clarification on communication service reliability 17.2.0 2019-12 SA#86 SP-191028 0035 1 F Derivation of communication service availability and reliability from network performance metrics 17.2.0 2019-12 SA#86 SP-191028 0037 1 D Editorial and minor corrections to TR 22.104 17.2.0 2019-12 SA#86 SP-191028 0032 2 C Network performance requirements for mobile operation panel 17.2.0 2019-12 SA#86 SP-191028 0038 2 F TS 22104 - Annex A for cooperative carrying 17.2.0 2020-07 SA#88e SP-200568 0050 F Correction of service performance requirements in tables of annex A.6 17.3.0 2020-07 SA#88e SP-200567 0049 D 22.104 Miscellaneous editorial corrections 17.3.0 2020-07 SA#88e SP-200562 0041 2 A Clarifications to communication service performance requirements 17.3.0 2020-07 SA#88e SP-200567 0048 2 A Miscellaneous values for further study 17.3.0 2020-07 SA#88e SP-200562 0045 2 A Correcting description of communication service status in Clause C.3 17.3.0 2020-07 SA#88e SP-200562 0047 1 A Clock synchronicity budget for the 5G system 17.3.0 2020-09 SA#89e SP-200790 0055 F Quality improvement – burst definition 17.4.0 2020-09 SA#89e SP-200790 0058 1 D CR 22.104 R17 - Editorial Improvements – Decimal Separator 17.4.0 2021-03 SA#91e SP-210200 0063 D Non-inclusive language replacement 22.104 17.5.0 2021-03 SA#91e SP-210217 0064 1 B Adding energy efficiency use cases for positioning to the ANNEX A 17.5.0 2021-06 SA#92e SP-210564 0075 1 A Quality improvement - update of definition of communication service availability 18.1.0 2021-06 SA#92e SP-210565 0066 1 D Quality improvement - addition of new annex (relationship between reliability and communication service availability) 18.1.0 2021-06 SA#92e SP-210565 0068 1 D 22.104 - V18.0.0 - quality improvement - update of mobile-robots use case description 18.1.0 2021-06 SA#92e SP-210565 0069 1 F Correction of mobile-robot use cases (UE number) 18.1.0 2021-06 SA#92e SP-210565 0070 1 D Quality improvement - service duration 18.1.0 2021-06 SA#92e SP-210517 0065 1 B 5G timing resiliency 18.1.0 2021-06 SA#92e SP-210524 0073 D Alignment of positioning power consumption aspects between 22.261 and 22.104 18.1.0 2021-06 SA#92e SP-210524 0072 1 B Adding LPHAP requirements for Industrial IoT 18.1.0 2021-09 SA#93e SP-211038 0077 2 A Quality improvement: update of reference to IEEE 802.1AS 18.2.0 2021-09 SA#93e SP-211070 0078 1 B Introduction of Smart Energy Infrastructure Requirements 18.2.0 2021-09 SA#93e SP-211070 0080 1 B Annex for smart grid 18.2.0 2021-09 SA#93e SP-211070 0082 1 B Introduction of SEI KPIs 18.2.0 2021-09 SA#93e SP-211070 0083 1 D Adjusting scope clause in TS 22.104 to the specification s content 18.2.0 2021-09 SA#93e SP-211039 0084 1 F Clarification of requirements for clock synchronization with direct device connection and indirect network connection communication 18.2.0 2021-09 SA#93e SP-211070 0087 1 B Inclusion of Smart Energy Infrastructure Requirements 18.2.0 2021-12 SP-94 SP-211497 0089 1 C Correction of references for clause 2 18.3.0 2021-12 SP-94 SP-211497 0090 D Remove editor note for Figure A.4.4.3-1 18.3.0 2021-12 SP-94 SP-211497 0091 1 F Update to Smart Grid normative requirements 18.3.0 2023-03 SA#99 SP-230230 0093 3 B Additional clarification on security, privacy for mobile robots using edge cloud 19.0.0 2023-03 SA#99 SP-230230 0094 4 B An additional usecase for Industrial edge cloud regarding digital twin usage 19.0.0 2023-09 SA#101 SP-231040 0097 1 C Smaller 5GS time sync budget 19.1.0 2024-06 SA#104 SP-240786 0100 1 A Correction of reference to IEEE Std 1588-2019 19.2.0 |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 1 Scope
| The present document provides the protocol details for enhancements to IMS multimedia telephony communication services enabled by supporting the IMS data channel and for AR communication which is one of the applications based on IMS data channel capability, based on stage 1 requirements in 3GPP TS 22.261 [2] and stage 2 requirements in 3GPP TS 23.228 [3].
The present document is applicable to User Equipment (UE), Application Servers (AS)and IP Multimedia (IM) Core Network (CN) subsystem which are intended to support IMS multimedia telephony communication services supporting the IMS data channel and AR communication which is one of the applications based on IMS data channel capability.
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 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 22.261: "Service requirements for the 5G system; Stage 1".
[3] 3GPP TS 23.228: "IP Multimedia Subsystem (IMS); Stage 2".
[4] 3GPP TS 26.114: "IP Multimedia Subsystem (IMS); Multimedia Telephony; Media handling and interaction".
[5] IETF RFC 5688: "A Session Initiation Protocol (SIP) Media Feature Tag for MIME Application Subtype".
[6] IETF RFC 6809: "Mechanism to Indicate Support of Features and Capabilities in the Session Initiation Protocol (SIP)".
[7] IETF RFC 3264: "An Offer/Answer Model with the Session Description Protocol (SDP)".
[8] 3GPP TS 22.173: "IP Multimedia Core Network Subsystem (IMS) Multimedia Telephony Service and supplementary services; Stage 1".
[9] 3GPP TS 24.229: "IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3".
[10] 3GPP TS 24.173: "IMS Multimedia telephony communication service and supplementary services; Stage 3".
[11] 3GPP TS 24.275: "Management Object (MO) for Basic Communication Part (BCP) of IMS Multimedia Telephony (MMTEL) communication service".
[12] 3GPP TS 24.629: "Explicit Communication Transfer (ECT) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification".
[13] 3GPP TR 22.873: "Study on evolution of the IP Multimedia Subsystem (IMS) multimedia telephony service".
[14] IETF RFC 8864: "Negotiation Data Channels Using the Session Description Protocol (SDP)".
[15] 3GPP TS 24.147: "Conferencing using the IP Multimedia (IM) Core Network (CN) subsystem".
[16] 3GPP TS 24.604: "Communication Diversion (CDIV) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification".
[17] 3GPP TS 24.615: "Communication Waiting (CW) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification".
[18] 3GPP TS 29.175: "IP Multimedia Subsystem; IP Multimedia Subsystem (IMS) Application Server (AS) Services; Stage 3".
[19] 3GPP TS 29.176: "IP Multimedia Subsystems (IMS); Media Function (MF) Services; Stage 3".
[20] 3GPP TS 32.260: "Telecommunication management; Charging management; IP Multimedia Subsystem (IMS) charging".
[21] 3GPP TS 32.255: "Telecommunication management; Charging management; 5G data connectivity domain charging; stage 2".
[22] 3GPP TS 24.647: "Advice Of Charge (AOC) using IP Multimedia (IM) Core Network (CN) subsystem".
[23] 3GPP TS 24.239: "Flexible Alerting (FA) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification".
[24] 3GPP TS 24.174: "Support of multi-device and multi-identity in the IP Multimedia Subsystem (IMS); Stage3.
[25] 3GPP TS 24.642: " Completion of Communications to Busy Subscriber (CCBS) and Completion of Communications by No Reply (CCNR) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification".
[26] 3GPP TS 24.183: "IP Multimedia Subsystem (IMS) Customized Ringing Signal (CRS); Protocol specification".
[27] 3GPP TS 24.182: "IP Multimedia Subsystem (IMS) Customized Alerting Tones (CAT); Protocol specification".
[28] 3GPP TS 24.628: "Common Basic Communication procedures using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification".
[29] 3GPP TS 26.264: "IMS-based AR Real-Time Communication".
[30] 3GPP TS 31.103: "Characteristics of the IP multimedia services identity module (ISIM) application".
[31] 3GPP TS 31.102: "Characteristics of the Universal Subscriber Identity Module (USIM) application".
[32] 3GPP TS 24.610:" Communication HOLD (HOLD) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification".
[33] 3GPP TS 22.011: "Service accessibility".
[34] 3GPP TS 22.156: "Mobile Metaverse Services; Stage 1".
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 3 Definitions of terms, symbols and abbreviations
| |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 3.1 Terms
| For the purposes of the present document, the terms 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].
IMS data channel application: An IMS data channel application is an application using IMS data channel capability to provide IMS services.
AR anchor: AR anchor is meant to identify a point in the user space to be used to anchoring a visual object. It is kind of metadata allowing accurate overlaying/rendering of text, graphics or video contents.
For the purposes of the present document, the following terms and definitions given in 3GPP TS 23.228 [3] apply:
Bootstrap data channel
Application data channel
IMS communication service
IMS Communication Service Identifier (ICSI)
Standalone IMS Data Channel Session
The following terms and definitions given in 3GPP TS 26.264 [29] apply:
AR media
Split rendering
The following terms and definitions given in 3GPP TS 24.229 [9] apply:
3GPP PS data off status
The following terms and definitions given in 3GPP TS 22.011 [33] apply:
3GPP PS data off
3GPP PS data off exempt services
The following terms and definitions given in 3GPP TS 22.156 [34] apply:
Avatar
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 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].
ADC Application Data Channel
AR Augmented Reality
AOC Advice Of Charge
AS Application Server
BDC Bootstrap Data Channel
CAT Customized Alerting Tones
CB Communication Barring
CCBS Completion of Communications to Busy Subscriber
CCNL Completion of Communications on Not Logged-in
CCNR Completion of Communications by No Reply
CD Communication Deflection
CDIV Communication DIVersion
CFB Communication Forwarding Busy
CFNL Communication Forwarding on Not Logged-in
CFNR Communication Forwarding No Reply
CFNRc Communication Forwarding on subscriber Not Reachable
CFU Communication Forwarding Unconditional
CN Core Network
CONF Conference
CRS Customized Ringing Signal
CW Communication Waiting
DC Data Channel
DCSF Data Channel Signalling Function
CUG Closed User Group
eCNAM Enhanced Calling Name
ECT Explicit Communication Transfer
FA Flexible Alerting
HOLD Communication Hold
ICSI IMS Communication Service Identifier
IM IP Multimedia
IMS IP Multimedia Core Network Subsystem
ISIM IM Subscriber Identity Module
MF Media Function
MiD Multi-iDentity
MMTel Multimedia Telephony
MuD Multi-Device
MWI Message Waiting Indication
OIP Originating Identification Presentation
OIR Originating Identification Restriction
OMA-DM Open Mobile Alliance Device Management
P2A Person to Application
P2A2P Person to Application and Application to Person
P2P Person to Person
SBI Service Based Interface
PSI Public Service Identifier
TIP Terminating Identification Presentation
TIR Terminating Identification Restriction
UE User Equipment
UICC Universal Integrated Circuit Card
URN Uniform Resource Name
USIM Universal Subscriber Identity Module
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 3.3 Symbols
| For the purposes of the present document the following symbols apply:
DC1 Reference Point between an SBI capable IMS AS and DCSF.
DC2 Reference Point between an SBI capable IMS AS and MF.
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 4 General
| According to 3GPP TS 23.228 [3], IMS multimedia telephony service supporting IMS data channel includes IMS data channel capability negotiation and IMS data channel setup. AR communication which is application based on IMS data channel capability, provisioned to the UE as an IMS data channel application, includes respective application domain specific media capability negotiation and media processing (e.g. AR communication).
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 5 Functional entities
| |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 5.1 General
| This clause specifies the functionalities of the functional entities for IMS data channel.
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 5.2 UE
| An UE supporting IMS data channel has the following functionalities:
- support IMS data channel capability negotiation;
- support bootstrap data channel and application data channel establishment and management;
- may support IMS data channel multiplexing and its capability negotiation.
Additionally, the UE supporting the IMS data channel capability and provisioned with AR communication, which is an application having IMS data channel capability, supports the following functionalities:
- support application's domain specific media capability exchange; and
- support application's domain specific media processing.
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 5.3 IMS AS
| The IMS AS interacts with the DCSF and the MF.
For functionalities of the IMS AS supporting IMS data channel refer to 3GPP TS 23.228 [3] clause AC.2.2.4.
For the IMS AS interaction with the Media Function (MF) refer to 3GPP TS 29.176 [19].
For the IMS AS interaction with the Data Channel Signalling Function (DCSF), NEF and Trusted AF refer to 3GPP TS 29.175 [18].
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 6 Operational requirements
| |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 6.1 Provision/withdrawal
| IMS Multimedia Telephony communication service enhanced to support IMS data channel is provided after prior arrangement with the service provider.
IMS Multimedia Telephony communication service enhanced to support IMS data channel is withdrawn at the user's request or for administrative reasons.
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 7 Basic communication
| |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 7.1 IMS Session Control
| The IMS multimedia telephony communication enhanced to support the IMS data channel applications shall support data channel media specified in clause 6.2.10 of 3GPP TS 26.114 [4] in addition to MMTel media types listed in 3GPP TS 22.173 [8]. The session control procedures for the different media types shall be in accordance with 3GPP TS 24.229 [9], 3GPP TS 24.173 [10] and clause 9.
The usage of IMS data channel media streams in MMTel session is negotiated using the SDP offer/answer procedures defined in IETF RFC 3264 [7]. If the received SDP offer contains IMS data channel media description(s) and if the receiving entity determines not to accept the requested IMS data channels, the receiving entity shall reject the offered data channel media description(s) by setting the port number of the rejected data channel media description(s) to zero in created SDP answer.
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 7.2 IMS communication service identifier (ICSI)
| The MMTel service enhanced to support IMS Data Channel shall use the ICSI value defined in 3GPP TS 24.173 [10] clause 5.1. The UE and IMS AS shall handle the ICSI value as specified in 3GPP TS 24.229 [9].
NOTE: Based on the operator policy, the subclass identifier ".imsdc" can be used within the MMTel ICSI URN.
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 8 IMS data channel applications
| |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 8.1 Procedures at the UE
| |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 8.1.1 General
| Once an MMTel session with the bootstrap data channels have been established, if the IMS data channel applications are available, based on the IMS data channel applications list received via the established bootstrap data channel, the UE shall download through the established bootstrap data channel the IMS data channel applications. The UE shall follow the procedures in clause 9.3.2.1.3.2 to set up an application data channel and include in the re-INVITE request the updated SDP offer with negotiated bootstrap data channel media description, the requested application data channel media description as well as the associated data channel application binding information (provided within the "a=3gpp-req-app" SDP attribute), according to 3GPP TS 23.228 [3] and 3GPP TS 26.114 [4]. The UE receiving the re-INVITE request shall identify the requested application data channel and the corresponding IMS data channel application, select an established bootstrap data channel to download through if it is not available on the UE, based on the associated data channel application binding information.
Upon receipt of a re-INVITE request initiated by the IMS AS to update an existing MMTel session with established bootstrap data channels for adding an application data channel requested by a DC AS, the UE accepting the requested application data channel shall identify the corresponding IMS data channel application and select an established bootstrap data channel to download through if it is not available on the UE, based on the associated data channel application binding information.
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 8.1.2 Support of Standalone IMS Data Channel Session
| If the originating UE has downloaded the data channel application, application data channel can be established together with bootstrap data channel during standalone IMS data channel session establishment.
If the originating UE did not download the data channel application, the UE shall establish an IMS session with only the bootstrap data channel towards a PSI, download the application through the established bootstrap data channel, and then establish a standalone IMS session with the associated application data channel and required bootstrap data channels towards peer UE; or initiate an IMS session with only the bootstrap data channel towards peer UE, and download the application through the established bootstrap data channel then add the associated application data channel during standalone IMS data channel session establishment.
If the terminating UE received the INVITE request to set up the bootstrap and application data channel simultaneously, the UE shall identify the data channel application in the application binding information (provided within the "a=3gpp-req-app" SDP attribute) is available or not, and:
1) if available, it shall follow the procedure in clause 9.3.3.1.6.3 to establish the requested bootstrap data channel and application data channel; or
2) if not available, it shall accept the bootstrap data channel and reject the application data channel to indicate that the data channel application is desired to be downloaded and download the application data channel through the established bootstrap data channel.
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 8.2 Procedures at the IMS AS
| |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 8.2.1 General
| After an MMTel session with the bootstrap data channels have been established, if the IMS AS received a re-INVITE request with an SDP offer containing application data channels media descriptions (identified by "dcmap" attribute lines containing "stream-id" parameter set to values starting at 1000 and associated "a=3gpp-req-app" attribute lines as specified in 3GPP TS 26.114 [4]), the IMS AS shall notify the DCSF, may trigger the reservation or update of corresponding application data channel media resources upon the instruction from the DCSF and shall send re-INVITE request with the SDP offer containing the requested application data channel and related bootstrap data channel media descriptions according to the specific data channel application use case (e.g. P2P/P2A/P2A2P), following the procedures in 3GPP TS 23.228 [3] and clauses 9.3.2.2.2.2 and 9.3.3.2.2.2.
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 8.2.2 Support of Standalone IMS Data Channel session
| The application data channel can be established along with the bootstrap data channel. If the IMS AS receives the INVITE request to establish the bootstrap data channel and the application data channel, it shall check whether the user is authorized to use standalone data channel. If the user is authorized to use standalone data channel, the IMS AS shall notify the DCSF and reserve the data channel media as specified in clause 9.3.2.2.4.4 and 9.3.3.2.4.3.
If the IMS AS receives the INVITE request to establish only the bootstrap data channel, it shall check whether the user is authorized to use standalone data channel. If the user is authorized to use standalone data channel, the IMS AS shall notify the DCSF and reserve the data channel media as specified in clause 9.3.2.2.4.3A and 9.3.3.2.4.1A.
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9 Signalling Procedures
| |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.1 General
| This clause provides the following signalling procedures for IMS data channel:
- IMS data channel capability negotiation during IMS initial registration and re-registration;
- IMS data channel capability indication during session establishment and modification;
- IMS data channel establishment which includes both bootstrap data channel and application data channel establishment during session establishment and modification;
- IMS data channel shutdown which includes both bootstrap data channel and application data channel; and
- abnormal cases.
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.2 IMS data channel capability negotiation
| |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.2.1 IMS data channel capability negotiation during IMS initial registration
| |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.2.1.1 Procedure at the UE
| The policy related to the UE supporting the IMS data channel can be provided by the network to the UE using e.g. OMA-DM with the management objects specified in 3GPP TS 24.275 [11], ISIM with EFIMSDCI file specified in 3GPP TS 31.103 [30] or USIM with EFIMSDCI file specified in 3GPP TS 31.102 [31]. When the UE is configured as specified in 3GPP TS 24.275 [11], 3GPP TS 31.103 [30] or 3GPP TS 31.102 [31] with configuration for IMS data channel allowed then the UE determines support for IMS data channel according to the configuration. If the UE is configured with both IMS_DC_configuration node and EFIMSDCI file, then the EFIMSDCI file shall take precedence.
If the UE is configured with IMS_DC_configuration node specified in 3GPP TS 24.275 [11] or EFIMSDCI file specified in 3GPP TS 31.103 [30] or 3GPP TS 31.102 [31], and the DC_allowed leaf of the IMS_DC_configuration node or IMS DC Establishment Indication of the EFIMSDCI file indicates that IMS data channel is allowed, then a UE supporting IMS data channel on sending an unprotected REGISTER request shall include the media feature tag defined in IETF RFC 5688 [5] for supported streaming media type. For the IMS data channel capability indication, the UE shall use +sip.app-subtype="webrtc-datachannel" as specified in 3GPP TS 26.114 [4].
NOTE: Precedence for EFIMSDCI file configured on both the USIM and ISIM is defined in 3GPP TS 31.102 [31].
On receiving the 200 (OK) response to the REGISTER request, if the 200 (OK) response includes a Feature-Caps header field containing feature-capability indicator "g.3gpp.datachannel", the UE shall determine that the home network supports the IMS data channel capability as specified in 3GPP TS 23.228 [3].
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.2.1.2 Procedure at the IMS AS
| Upon receipt of a third-party REGISTER request, if the Contact header field of the REGISTER request in the body including a media feature tag for supported streaming media type containing +sip.app-subtype="webrtc-datachannel" as specified in 3GPP TS 26.114 [4], the IMS AS shall store this IMS data channel capability indication and determine the UE supports the IMS data channel capability.
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.2.2 IMS data channel capability negotiation during IMS re-registration
| |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.2.2.1 Procedure at the UE
| If the UE is allowed to use IMS data channel, on sending of re-REGISTER request, for user-initiated reregistration, the UE supporting IMS data channel shall include the media feature tag defined in IETF RFC 5688 [5] for supported streaming media type. For the IMS data channel capability indication, the UE shall use +sip.app-subtype="webrtc-datachannel" as specified in 3GPP TS 26.114 [4].
NOTE: The policy related to the IMS data channel allowed at the UE, can be provided by the network to the UE using e.g., OMA-DM with the management objects specified in 3GPP TS 24.275 [11] or UICC configuration, as specified in clause 9.2.1.1.
On receiving the 200 (OK) response to the re-REGISTER request, if the 200 (OK) response includes a Feature-Caps header field containing feature-capability indicator "g.3gpp.datachannel", the UE shall determine that the home network supports the IMS data channel capability as specified in 3GPP TS 23.228 [3].
The UE shall continue to indicate its IMS data channel capability as specified in the above procedure when the UE has successfully done the IMS data channel capability negotiation during IMS initial registration or re-registration.
On receiving the 200 (OK) response to the REGISTER request, if the 200 (OK) response does not include a Feature-Caps header field containing feature-capability indicator "g.3gpp.datachannel", the UE shall keep established data channel media of the UE's existing IMS session.
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.2.2.2 Procedure at the IMS AS
| Upon receipt of a third-party REGISTER request, if the Contact header field of the REGISTER request in the body including a media feature tag for supported streaming media type containing +sip.app-subtype="webrtc-datachannel" as specified in 3GPP TS 26.114 [4], the IMS AS shall store this IMS data channel capability indication and determine the UE supports the IMS data channel capability.
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.2.3 IMS data channel capability indication during IMS session establishment and modification
| |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.2.3.1 Procedure at the UE
| Upon generating an initial INVITE request or a re-INVITE request, if the UE supporting IMS data channel is configured with IMS data channel is allowed option and if the UE determined its home network supports the IMS data channel capability, the UE shall include the +sip.app-subtype media feature tag defined in IETF RFC 5688 [5] for supported streaming media type in the Contact header field set to the value="webrtc-datachannel" as specified in 3GPP TS 26.114 [4], regardless of IMS data channel media description being part of the SDP offer or not. The UE may include in the initial INVITE request an Accept-Contact header field containing the "sip.app-subtype" media feature tag defined in IETF RFC 5688 [5] with a value of "webrtc-datachannel" as specified in 3GPP TS 24.173 [10].
Upon receiving an initial INVITE request or a re-INVITE request, if the UE supporting IMS data channel is configured with IMS data channel is allowed option, the UE shall include +sip.app-subtype media feature tag defined in IETF RFC 5688 [5] set to the value ="webrtc-datachannel" as specified in 3GPP TS 26.114 [4] in the Contact header field in the SIP response, regardless of IMS data channel media description being part of the SDP offer or not.
9.2A IMS data channel multiplexing capability negotiation
9.2A.1 IMS data channel multiplexing capability negotiation during IMS registration
9.2A.1.1 Procedure at the UE
If a UE supporting IMS data channel multiplexing capability is allowed to use IMS data channel, on sending of an unprotected REGISTER request or re-REGISTER request for user-initiated re-registration, the UE shall include the "g.3gpp.dc-mux" media feature tag defined in 3GPP TS 26.114 [4] in the Contact header field.
On receiving the 200 (OK) response to the REGISTER request or re-REGISTER request, if the 200 (OK) response includes a Feature-Caps header field containing feature-capability indicator "g.3gpp.dc-mux", the UE shall determine that the home network supports the IMS data channel multiplexing capability as specified in 3GPP TS 23.228 [3].
The UE shall continue to indicate its IMS data channel multiplexing capability as specified in any subsequent re-registration procedure when the UE has successfully done the IMS data channel capability negotiation during IMS initial registration or re-registration.
9.2A.1.2 Procedure at the IMS AS
Upon receipt of a third-party REGISTER request, if the Contact header field of the REGISTER request in the body including a "g.3gpp.dc-mux" media feature tag defined in 3GPP TS 26.114 [4], the IMS AS shall store this IMS data channel multiplexing capability indication and determine the UE supports the IMS data channel multiplexing capability.
9.2A.2 IMS data channel multiplexing capability indication during IMS session establishment and modification
9.2A.2.1 Procedure at the UE
If supporting IMS data channel multiplexing capability, being allowed to use IMS data channel and having determined the home network supports the IMS data channel multiplexing capability, upon generating an initial INVITE request or a re-INVITE request including a SDP offer that contains data channel media descriptions using IMS data channel multiplexing, the UE shall include the "g.3gpp.dc-mux" media feature tag defined in 3GPP TS 26.114 [4] in the Contact header field.
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.3 MMTel session procedures
| |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.3.1 General
| The support of the IMS data channel is optional.
The session control procedures for IMS multimedia telephony communication service with IMS data channel shall be in accordance with 3GPP TS 24.173 [10] with the additions defined in the present document.
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.3.2 Originating side
| |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.3.2.1 Procedures at the UE
| |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.3.2.1.1 General
| The UE shall only initiate an MMTel session with an IMS data channel if the UE has determined that the UE and the home network supports the IMS data channel capability.
The policy related to the UE supporting the IMS data channel can be provided by the home network to the UE using e.g. OMA-DM with the management objects specified in 3GPP TS 24.275 [11] or UICC configuration, as specified in clause 9.2.1.1. When the UE is configured by home network with configuration for IMS data channel, then the UE may setup the IMS data channel.
If the UE is configured with IMS_DC_configuration node specified in 3GPP TS 24.275 [11] and:
a) if DC_allowed leaf indicates that IMS data channel is not allowed, the UE shall not include data channel capability indication and data channel related media description in SDP offer; or
b) if DC_allowed leaf indicates that IMS data channel is allowed, and:
1) if DC_Setup_Option leaf is configured and indicates the IMS data channel is allowed to be setup simultaneously while establishing an MMTel session, the UE:
- shall include the bootstrap data channel related media description in SDP offer within the initial INVITE request as described in clause 9.3.2.1.2 to setup the bootstrap data channel;
NOTE 1: If the bootstrap data channel was not established during the MMTel session establishment, the UE can try to setup the bootstrap data channel as described in clause 9.3.2.1.3.1.
2) if DC_Setup_Option leaf is configured and indicates the IMS data channel is not allowed to be setup simultaneously while establishing an MMTel session, the UE shall generate a re-INVITE request for the bootstrap data channel setup and include the bootstrap data channel related media description in SDP offer as described in clause 9.3.2.1.3.1 to setup the bootstrap data channel; and
3) if the UE receives an initial INVITE or a re-INVITE request including the bootstrap data channel related media description in SDP offer, the UE shall generate an SDP answer as described in clauses 9.3.3.1.2 and 9.3.3.1.3.1.
If the UE is configured with EFIMSDCI file specified in 3GPP TS 31.103 [30] or 3GPP TS 31.102 [31] and:
a) if IMS DC Establishment Indication indicates that IMS data channel is not allowed, the UE shall not include data channel capability indication and data channel related media description in SDP offer;
b) if IMS DC Establishment Indication indicates that IMS data channel is allowed and allowed to be setup simultaneously while establishing an MMTel session, the UE shall include the bootstrap data channel related media description in SDP offer within the initial INVITE request as described in clause 9.3.2.1.2 to setup the bootstrap data channel;
NOTE 2: If the bootstrap data channel was not established during the MMTel session establishment, the UE can try to setup the bootstrap data channel as described in clause 9.3.2.1.3.1.
c) if IMS DC Establishment Indication indicates that IMS data channel is allowed but not allowed to be setup simultaneously while establishing an MMTel session, the UE shall generate a re-INVITE request for the bootstrap data channel setup and include the bootstrap data channel related media description in SDP offer as described in clause 9.3.2.1.3.1 to setup IMS data channel; and
d) if IMS DC Establishment Indication indicates that IMS data channel is allowed, if the UE receives an initial INVITE or a re-INVITE request including the bootstrap data channel related media description in SDP offer, the UE shall generate an SDP answer as described in clauses 9.3.3.1.2 and 9.3.3.1.3.1.
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.3.2.1.2 IMS bootstrap data channel setup in conjunction with MMTel session setup
| If the UE initiates an MMTel session with IMS data channels, the UE:
1) shall generate an initial INVITE request in accordance with 3GPP TS 24.229 [9] and 3GPP TS 24.173 [10];
2) shall include the media feature tag defined in IETF RFC 5688 [5] for supported streaming media type with +sip.app-subtype="webrtc-datachannel" as specified in 3GPP TS 26.114 [4] in the Contact header field;
3) may include an Accept-Contact header field containing the "sip.app-subtype" media feature tag defined in IETF RFC 5688 [5] with a value of "webrtc-datachannel" as specified in 3GPP TS 26.114 [4]; and
4) if the configuration described in clause 9.3.2.1.1, allows the establishment of bootstrap data channels simultaneously with the setup of the MMTel session, shall include an SDP offer containing the media descriptions for the MMTel media according 3GPP TS 24.173 [10] and data channel media descriptions for both the local and remote bootstrap data channels in accordance with 3GPP TS 26.114 [4].
Upon receiving of the UPDATE request with the SDP offer to establish a bootstrap data channel, the procedure defined in clause 9.3.3.1.3.1 applies and the originating UE shall return a SIP response to the UPDATE request with the generated SDP answer.
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.3.2.1.3 IMS data channel setup in conjunction with MMTel session modification
| |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.3.2.1.3.1 IMS bootstrap data channel establishment
| If the UE wants to establish a bootstrap data channel, the UE shall take into account the data channel configuration as specified in clause 9.3.2.1.1, and if the UE determines that the configuration allows the establishment of IMS data channels after the establishment of the MMTel session, the UE shall:
1) generate a re-INVITE request in accordance with 3GPP TS 24.229 [9] and 3GPP TS 24.173 [10];
2) include the media feature tag defined in IETF RFC 5688 [5] for supported streaming media type with +sip.app-subtype="webrtc-datachannel" as specified in 3GPP TS 26.114 [4] in the Contact header field; and
3) include an updated SDP offer that contains data channel media descriptions for both the local and remote bootstrap data channels according to 3GPP TS 26.114 [4].
Upon receiving a re-INVITE request to establish a bootstrap data channel, the procedure defined in clause 9.3.3.1.3.1 applies.
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.3.2.1.3.2 IMS application data channel establishment
| If a UE wants to establish an application data channel within an existing MMTel session and if the UE has an established bootstrap data channel associated with the MMTel session available, the UE:
1) shall generate a re-INVITE request in accordance with 3GPP TS 24.229 [9] and 3GPP TS 24.173 [10];
2) shall include the media feature tag defined in IETF RFC 5688 [5] for supported streaming media type with +sip.app-subtype="webrtc-datachannel" as specified in 3GPP TS 26.114 [4] in the Contact header field; and
3) shall include an updated SDP offer that contains the data channel media descriptions for the bootstrap data channels, as well as the requested application data channel and the associated DC application binding information (provided within the "a=3gpp-req-app" SDP attribute), according to 3GPP TS 26.114 [4].
If the UE has an established bootstrap data channel associated with the MMTel session available and if the UE receives the re-INVITE request with an SDP offer which includes data channel media descriptions for the bootstrap data channel, as well as the requested application data channel, the procedure defined in clause 9.3.3.1.3.2 applies.
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.3.2.1.4 Closing IMS application data channel in conjunction with MMTel session modification
| If the UE wants to close an established application data channel during the session modification by sending re-INVITE request with the subsequent SDP offer, the UE shall remove the "a=dcmap" attribute line associated with the closed application data channel and, if the associated "a=3gpp-req-app" attribute references only the closed application data channel, the "a=3gpp-req-app" attribute line from the data channel media description as defined in IETF RFC 8864 [14] clause 6.6.1 or set the UDP port number of the data channel media description to zero if no other "a=dcmap" attribute line associated with an application data channel existed in this data channel media description.
If the UE receives a re-INVITE request with an SDP offer in which the UDP port number of the data channel media description was set to zero or the "a=dcmap" line associated with an application data channel was removed from the data channel media description, and the UE accepts the application data channel termination, it shall return a 200 (OK) response to the re-INVITE request with the generated SDP answer based on the IETF RFC 8864 [14].
The UE shall not close the bootstrap data channel during MMTel session modification procedure.
NOTE: The application data channel termination during the session modification does not impact the ongoing audio, video or other data channels within the MMTel session.
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.3.2.1.5 Closing IMS data channel in conjunction with MMTel session release
| When the UE releases an MMTel session that has associated bootstrap and application data channels, the UE shall apply procedures defined in 3GPP TS 24.229 [9] clause 5.1.5 and shall close bootstrap and application data channels.
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.3.2.1.6 Support of standalone data channel
| |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.3.2.1.6.1 General
| The procedures of standalone data channel include:
1. establish an IMS session to a PSI or a target UE with only bootstrap data channel;
2. establish an IMS data session with combined bootstrap data channel and application data channel;
3. modify an IMS session to add audio/video media to the IMS session that only contains data channel media; and
4. modify an IMS session to remove audio/video media in the IMS session that includes IMS data channel and audio/video media.
If the UE is configured with IMS_DC_configuration node specified in 3GPP TS 24.275 [11] and DC_allowed leaf indicates that IMS data channel is not allowed, the UE shall not establish an standalone IMS data channel session.
NOTE 1: The DC_setup_option of the IMS_DC_configuration leaf that is specified in 3GPP TS 24.275 [11] is not applicable to the standalone IMS data channel session establishment.
If the UE is configured with EFIMSDCI file specified in 3GPP TS 31.103 [30] or 3GPP TS 31.102 [31] and IMS DC Establishment Indication indicates that IMS data channel is not allowed, the UE shall not establish an standalone IMS data channel session.
NOTE 2: The coding '01' and '02' for the IMS Data Channel Establishment Indication in the EFIMSDCI file specified in 3GPP TS 31.103 [30] or 3GPP TS 31.102 [31] are not applicable to the standalone IMS data channel session establishment.
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.3.2.1.6.2 Standalone bootstrap data channel establishment
| If the UE wants to initiate a call to a Public Service Identifier (PSI) with only bootstrap data channel, the UE shall:
1) populate the Request-URI header field with a specific "request-uri" indicating standalone data channel pre-configured in the UE;
2) include data channel media description only for the local bootstrap data channel in the SDP offer; and
3) follow the procedure of clause 9.3.2.1.2 to generate an initial INVITE request.
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.3.2.1.6.3 Void
| 9.3.2.1.6.3A Adding application data channel during standalone IMS data channel session establishment
This procedure applies when the user selected data channel application is not available on the originating UE.
If the UE determines to initiate a standalone data channel session towards the terminating UE with only bootstrap data channels, it shall generate an initial INVITE request as per clause 9.3.2.1.2, but without the audio and video media in the SDP offer.
NOTE: The UE initiates a standalone data channel session towards the terminating UE with only bootstrap data channel if the user selected data channel application is not available.
Upon receipt of the 183 (Session Progress) response to the initial INVITE request which indicates the bootstrap data channel has been established and the data channel application is downloaded through the established bootstrap data channel, the UE shall generate a SIP UPDATE request with the updated SDP offer containing the established bootstrap data channel, as well as the requested application data channel and the associated DC application binding information (provided within the "a=3gpp-req-app" SDP attribute) according to 3GPP TS 26.114 [4].
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.3.2.1.6.4 Combined standalone bootstrap data channel and application data channel establishment
| This procedure applies when the user selected data channel application is available on the originating UE.
If the UE determines to initiate a standalone data channel session towards the terminating UE with both bootstrap data channel and application data channel, it shall generate an initial INVITE request with the SDP offer which includes both the bootstrap data channel media description and application data channel media description.
NOTE: The UE initiates a standalone data channel session towards the terminating UE with both bootstrap data channel and application data channel if the user selected data channel application is available at UE.
Upon receipt of the 183 (Session Progress) response to the initial INVITE request in which the bootstrap data channel is accepted but the application data channel is rejected, i.e. the port number of the application data channel media description is set to zero, the UE shall determine that the terminating UE has not downloaded the data channel application according to 3GPP TS 23.228 [3] clause AC.10.2.3 and consequently shall generate a SIP UPDATE request with the updated SDP offer containing the established bootstrap data channel, as well as the requested application data channel and the associated DC application binding information (provided within the "a=3gpp-req-app" SDP attribute) according to 3GPP TS 26.114 [4].
NOTE: If the terminating UE accepted the bootstrap data channel and rejected the application data channel received in the SDP answer of 183 (Session Progress) response to the initial INVITE request with both bootstrap and application data channel media description, it means that the terminating UE desires to download the data channel application.
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.3.2.1.6.5 Adding video/audio media to IMS session with standalone data channel
| If the UE wants to add audio/video media to the IMS session with standalone data channel toward the peer UE, it shall generate a re-INVITE request with the SDP offer which includes the media descriptions for established application data channel, bootstrap data channel and audio/video.
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.3.2.1.6.6 Removing video/audio media from IMS data channel session
| If the UE is authorized to use standalone data channel, and it wants to remove the audio/video media from the IMS session including both audio/video and data channel media, the UE shall generate a re-INVITE with the SDP offer in which the port number of audio/video media is set to zero.
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.3.2.1.7 Enforcement of 3GPP SIP-Based 3GPP PS Data Off Exempt Services
| When 3GPP PS data off is supported and 3GPP PS data off status is changed to "active", if the list of 3GPP PS data off exempt services configured in 3GPP TS 24.275 [11] or in 3GPP TS 31.102 [31] indicates that the services over IMS Data Channel is not a 3GPP PS data off exempt service, in addition to following 3GPP TS 24.229 [9], the UE shall:
1) prevent IMS data channel setup procedures;
2) close all the IMS data channels in the ongoing MMTel session with IMS data channel by generating a re-INVITE request including an SDP offer that contains the IMS data channel media descriptions for both bootstrap data channels and application data channels and set the UDP port number of each IMS data channel media description to zero;
3) terminate the ongoing standalone IMS data channel session by applying procedures defined in 3GPP TS 24.229 [9] clause 5.1.5; and
4) if the UE sent an initial INVITE request with IMS data channel media description(s) in the SDP offer and did not receive a final response to the initial INVITE request:
a) if the initial SDP offer contained only IMS data channel media description(s), send a CANCEL request; or
b) if the initial SDP offer also contained other media description(s):
- if the UE received the SDP answer, at least one of the offered IMS data channel media descriptions is accepted, and there is no ongoing SDP offer/answer exchange, create a new SDP offer in which the UDP port number of each accepted IMS data channel media description is set to zero and send the SDP offer within UPDATE (or PRACK) request; or
- if the UE did not yet receive the SDP answer, wait for reception of a SIP message with the SDP answer. If the received SDP answer indicates at least one of the offered IMS data channel media descriptions is accepted, the UE shall create a new SDP offer in which the UDP port number of each accepted IMS data channel media description is set to zero and send the SDP offer within UPDATE (or PRACK) request.
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.3.2.1.8 Support of data channel multiplexing
| If a UE determines both the UE and its home IMS network support IMS data channel multiplexing capability, and wants to multiplex IMS data channels during IMS data channel establishment, the UE shall:
1) follow the procedures of clause 9.3.2.1.2, clause 9.3.2.1.3 and clause 9.3.2.1.6.4 to generate an initial INVITE, a re-INVITE or a UPDATE request;
2) include the "g.3gpp.dc-mux" media feature tag defined in 3GPP TS 26.114 [4] in the Contact header field; and
3) include in the SDP offer the multiplexed data channel media description(s) according to 3GPP TS 26.114 [4], using:
a) a single m line for both the local and remote bootstrap data channels; and
b) a single m line for different application data channels for applications with compatible QoS requirements.
Upon receipt of the 18x or 2xx response including SDP answer to the initial INVITE, re-INVITE or UPDATE request, if the port number(s) of the multiplexed data channel media description(s) is set to zero and the "g.3gpp.dc-mux" header field parameter as specified in 3GPP TS 26.114 [4] is not included in the Contact header field, the UE may modify the SDP offer with de-multiplexed data channel media description and resend the corresponding request.
Upon receiving a re-INVITE request with an SDP offer, which contains multiplexed data channel media description(s), the procedure defined in clause 9.3.3.1.8 applies.
If a UE wants to close an established multiplexed application data channel during the session modification by sending re-INVITE request with the subsequent SDP offer, the procedure defined in clause 9.3.2.1.4 applies.
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.3.2.2 Procedure at the IMS AS
| |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.3.2.2.1 IMS bootstrap data channel establishment in conjunction with MMTel session setup
| Based on served user service specific data which is enhanced with IMS data channel specific service details, if the IMS AS received an initial INVITE request with an SDP offer containing media description for IMS data channels, the IMS AS shall determine whether the served user is authorized to use IMS data channel.
If the served user is not authorized to use IMS data channel, then based on the operator policy the IMS AS shall determine whether to remove from the SDP offer media lines related to the IMS data channels:
- If the operator policy indicates removal of media lines related to the IMS data channels, the IMS AS shall remove media lines describing the bootstrap data channel(s) i.e. "dcmap" attribute lines containing a subprotocol parameter set to "http" and "stream-id" parameter set to values 0, 10, 100 and 110, and associated with the "m=" line containing the media set to "application", the UDP port number, the proto value set to "UDP/DTLS/SCTP" and the fmt value set to "webrtc-datachannel". If there are no other "dcmap" attribute lines that contain a subprotocol parameter set to value other than "http", the IMS AS shall remove any other SDP media attribute lines associated with that m line e.g., "sctp-port", "max-message-size", "tls-id", "a=setup", "a=3gpp-qos-hint" SDP attribute lines from the received SDP offer, and send the initial INVITE request with the modified SDP offer to the S-CSCF.
- If the operator policy does not indicate removal of media lines related to the IMS data channels, the IMS AS may forward media description describing the bootstrap data channel with "dcmap" attribute lines containing a subprotocol parameter set to "http" and "stream-id" parameter set to values 100 and 110, and send the initial INVITE request to the S-CSCF.
Otherwise, if the served user is authorized to use IMS data channel and the DCSF is not selected, the IMS AS shall select a DCSF and notify the DCSF about the session establishment request event, with a calling identity set to the value of the P-Asserted-Identity header field and a called identity set to the value of Request URI of the received initial INVITE request, and shall not send the initial INVITE request to the S-CSCF until receiving an acknowledgement to the corresponding notification from the DCSF.
Based on the received Media instruction set from the DCSF, the IMS AS shall select a MF and request the MF to allocate required data channel media resources. Based on the response of the reserved media resource from the MF, the IMS AS shall:
1) delete the bootstrap data channel media description terminated locally, i.e. local bootstrap data channel for the originating UE (the media line with the "dcmap" attribute containing a subprotocol parameter set to "http" and "stream-id" parameter set to values 0 and 10);
2) replace the IP address represented in the attribute lines "c=" line, the UDP port number in the "m=application" line, as well as the DC endpoint information represented as the attribute lines "a=tlsId", "a=sctp-port", "a=fingerprint" and "a=setup" within the remote bootstrap data channel media description for the originating UE (the media line with the "dcmap" attribute containing a subprotocol parameter set to "http" and "stream-id" parameter set to values 100 and 110), i.e. the remote bootstrap data channel between the originating UE and terminating network, received in the SDP offer with the media resource information for the termination towards the remote network allocated on the MF if the media is anchored on the originating MF, and add "a=3gpp-bdc-used-by:" attribute line containing "bdc-used-by" parameter set to value "sender" if not present; and
3) generate and add the remote bootstrap data channel media description for the terminating UE (the media line with the "dcmap" attribute containing a subprotocol parameter set to "http" and "stream-id" parameter set to values 100 and 110 and "a=3gpp-bdc-used-by:" attribute with "bdc-used-by" parameter set to value "receiver"), i.e. remote bootstrap data channel between the originating network and the terminating UE.
Upon the reception of the successful acknowledgement to the corresponding notification from the DCSF, the IMS AS shall send the initial INVITE request with audio, video and modified data channel SDP offer to the S-CSCF towards the terminating network.
Upon receipt the 18x or 2xx response on the initial INVITE request including the SDP answer which includes the data channel media description, the IMS AS shall notify the DCSF about corresponding session event (session establishment progress (i.e. receiving the 183 (Session Progress) response ), session establishment alerting (i.e. receiving the 180 (Ringing) response) or session establishment success (i.e. receiving 200 (OK) response) event) and shall request the MF to update the media resource. Based on the media resource update response from the MF, the IMS AS shall:
1) delete the remote bootstrap data channel media description for the terminating UE (the media line with the "dcmap" attribute containing a subprotocol parameter set to "http" and "stream-id" parameter set to values 100 and 110 and "a=3gpp-bdc-used-by" attribute with "bdc-used-by" parameter set to value "receiver"), i.e. the remote bootstrap data channel between terminating UE and originating network from the SDP answer;
2) replace the IP address represented in the "c=" line, the UDP port number in the "m=application" line, as well as the DC endpoint information represented as the attribute lines "a=tlsId", "a=sctp-port", "a=fingerprint" and "a=setup" within the remote bootstrap data channel media description for originating UE (the media line with the "dcmap" attribute containing a subprotocol parameter set to "http" and "stream-id" parameter set to values 100 and110 and "a=3gpp-bdc-used-by" attribute with "bdc-used-by" parameter set to value "sender") in the SDP answer if the media is anchored on the MF, i.e. the remote data channel for the originating UE between originating UE and terminating network, with the media resource information for the termination towards the originating UE to the terminating network allocated by the MF; and
3) generate and add the local bootstrap data channel media description for the originating UE (the media line with the "dcmap" attribute containing a subprotocol parameter set to "http" and "stream-id" parameter set to values 0 and10), i.e. the local bootstrap data channel between originating UE and originating network in the SDP answer.
Upon the reception of an acknowledgement from the DCSF to the corresponding notification, the IMS AS shall include the modified SDP answer for data channel in the 18x or 2xx response and send 18x or 2xx response to S-CSCF towards the originating UE.
If the IMS AS received from the terminating network the UPDATE request with the SDP offer containing data channel media description for the bootstrap data channel establishment, the procedure of the IMS AS defined in clause 9.3.3.2.2.1 applies.
Upon receipt of a CANCEL request to the initial INVITE request, the IMS AS shall notify the DCSF about the session establishment cancellation, request the MF to release the corresponding data channel media resources, and forward the CANCEL request to the S-CSCF towards the terminating network.
Upon receipt of a 4xx, 5xx or 6xx response on the initial INVITE request from the terminating network, the IMS AS shall notify the DCSF about session establishment failure, and request the MF to release the data channel media resources.
9.3.2.2.1A Network-initiated standalone IMS data channel session setup
Upon receipt a request to setup a standalone IMS data channel session as specified in 3GPP TS 23.228 [3] AG.2.2, the IMS AS shall determine whether the served user is authorized to use IMS data channel as specified in clause 9.3.2.2.1. If the served user is authorized to use data channel, the IMS AS shall select a DCSF and notify the DCSF about the external session create event. Based on the instruction from the DCSF, the IMS AS shall request the MF to allocate data channel media resources, generate the media description for the data channel as specified in clause 9.3.2.2.2.4, generate and send initial INVITE request with
- SDP offer for the originating and terminating UEs as specified in 3GPP TS 24.229 [9] clause 5.7.3;
- the DC-Info header field as specified in 3GPP TS 24.229 [9] 7.2.x to indicate the data channel is initiated by the DC AS.
Upon receipt of the 18x or 2xx response including SDP answer to the initial INVITE request, the IMS AS shall notify the DCSF about corresponding session event (session establishment progress (i.e. receiving the 183 (Session Progress) response ), session establishment alerting (i.e. receiving the 180 (Ringing) response) or session establishment success (i.e. receiving 200 (OK) response) event) and request the MF to update the media resource.
Upon receipt of a 4xx, 5xx or 6xx response to the initial INVITE request, the IMS AS shall notify the DCSF about session establishment failure, and request the MF to release the data channel media resources.
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.3.2.2.2 MMTel session modification
| |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.3.2.2.2.1 IMS bootstrap data channel establishment
| If the IMS AS received from the originating UE a re-INVITE request with the SDP offer containing data channel media description for the bootstrap data channel establishment, the IMS AS shall determine whether the served user is authorized to use IMS data channel or not as specified in clause 9.3.2.2.1.
- if the served user is not authorized to use IMS data channel, the procedure defined in clause 9.3.2.2.1 applies; and
- if the served user is authorized to use IMS data channel, the IMS AS shall select a DCSF and notify the DCSF about the media change request event, with a calling identity set to the value of the P-Asserted-Identity header field and a called identity set to the value of Request URI of the initial INVITE request received during MMTel session establishment, if the media instruction from DCSF is:
a) to reject all the data channel medias in this request, the IMS AS shall send a 488 (Not Acceptable Here) to the originating UE if other medias are not updated; and
b) in other cases, the IMS AS shall request the MF to reserve the media resources and modify the data channel media description in the SDP offer and send the re-INVITE request as per clause 9.3.2.2.1. Upon receipt of the 183 (Session Progress) or 200 (OK) response to the re-INVITE request, the IMS AS shall send notify the DCSF about the media change success if the data channel media is accepted or media change failure if the data channel media is rejected and modify the data channel media description in the SDP answer and send the 183 (Session Progress) or 200(OK) response to S-CSCF as per clause 9.3.2.2.1. Upon receipt of a CANCEL request to the re-INVITE request, the IMS AS shall notify the DCSF about the media change cancellation, request the MF to release the corresponding data channel media resources, and forward the CANCEL request as per clause 9.3.2.2.1. Upon receipt of a 4xx, 5xx or 6xx response on the re-INVITE request, the IMS AS shall notify the DCSF about the media change failure and forward the response to the originating UE.
If the IMS AS received from the terminating network a re-INVITE request with the SDP offer containing data channel media description for the bootstrap data channel establishment, the procedure of the IMS AS in the terminating network on receipt of a re-INVITE request from the originating network defined in clause 9.3.3.2.2.1 applies.
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.3.2.2.2.2 IMS application data channel establishment
| After the DCSF is selected, upon receipt of the re-INVITE request with an SDP offer which contains new application data channel media descriptions (the media lines with the "dcmap" attribute containing "stream-id" parameter set to values starting at 1000) along with the video, audio, and bootstrap data channel media descriptions, the IMS AS shall notify to DCSF about a media change request event. If the media instruction from the DCSF is
- to reject all the data channel medias in this request, the IMS AS shall send a 488 (Not Acceptable Here) to the originating UE if other medias are not updated; and
- in other cases, the IMS AS shall request the MF to allocate media resources for the application data channels based on the instruction from the DCSF if the media is anchored on the MF, and shall not send a re-INVITE request to the S-CSCF until receiving an acknowledgement to the corresponding notification from the DCSF;
- based on the response on the data channel media resource update from the MF as specified in 3GPP TS 29.176 [19] and media instruction from the DCSF as specified in 3GPP TS 29.175 [18], the IMS AS shall:
1) delete the data channel media description (media line with the "dcmap" attribute containing "stream-id" parameter set to values starting at 1000 and "a=3gpp-req-app " attribute with "endpoint" parameter set to value "server") if the media instruction from the DCSF is to terminate that media;
2) delete the data channel media description if the media instruction from the DCSF is to reject the media and there are other medias to be established;
3) replace the IP address represented in the "c=" line, the UDP port number in the "m=application"in the data channel media description in the SDP offer with the media resource information for the termination towards the terminating network which is allocated by the MF if the media instruction from the DCSF is to terminate and originate the media; and also replace the DC endpoint information represented as the attribute lines "a=tlsId", "a=sctp-port", "a=fingerprint" and "a=setup" when the media proxy configuration is HTTP proxy; and
4) generate and add a data channel media description (media line with the "dcmap" attribute containing "stream-id" parameter set to values starting at 1000 and "a=3gpp-req-app " attribute with "endpoint" parameter set to value "server") by using the DC stream information provided by the DCSF in the attribute lines "a=dcmap" and "a=3gpp-req-app", DC endpoint information of the DC AS in the attribute lines "a=tlsId", "a=sctp-port", "a=fingerprint" and "a=setup", IP address and UDP port number allocated on the termination towards to the terminating network on the MF in the "c=" line and "m=application" line when the media proxy configuration is UDP proxy, or using the DC stream information provided by the DCSF in the attribute lines "a=dcmap" and "a=3gpp-req-app", IP address, UDP port number and DC endpoint information (e.g. tlsId, sctp-port) allocated on the termination towards to the terminating network on the MF in other attribute lines above when the media proxy configuration is HTTP proxy, if the media instruction from the DCSF is to originate a new media; and
- an existing application data channel media description in which a new "a=dcmap" line containing the "stream-id" parameter set to values starting at 1000 is added, the IMS AS shall notify the DCSF about media change request event, and request MF to update the media resource when receiving the media instruction from DCSF is to update the media.
Upon the reception of an acknowledgement from the DCSF to the media change request event notification, the IMS AS shall send the re-INVITE request with the modified SDP offer with the modified application data channel media description or the original application data channel media description if no media instruction received from DCSF, as well as the media description of established video, audio and bootstrap data channels.
Upon receipt of the 183 (Session Progress) or 200 (OK) response on the re-INVITE request with the SDP answer which contains media description of the requested application data channel from the terminating network:
- if the application data channel is accepted, the IMS AS shall notify the DCSF about the media change success and request the MF to update the media resources. Based on the response of the MF, the IMS AS shall:
a) generate and add a data channel media description in the SDP answer by using the DC endpoint information of the DC AS provided by the DCSF in the attribute lines "a=tlsId", "a=sctp-port", "a=fingerprint" and "a=setup" and IP address and UDP port number allocated on the termination towards to the originating UE on the MF in the "c=" and "m=application" line when the media proxy configuration is UDP proxy, or using IP address, UDP port number and DC endpoint information (e.g. tlsId, sctp-port) allocated on the termination towards to the originating UE on the MF in the attribute lines when the media proxy configuration is HTTP proxy, if the instruction from the DCSF is to terminate the media;
b) add the rejected media description and set the port number to 0 in the "m=application" line if the instruction from the DCSF is to reject the media and there are other medias to be established;
c) replace the IP address represented in the "c=" line, the UDP port number in the "m=application" in the media description in the SDP answer with the media resource information on the termination towards to the originating UE allocated by the MF, if the instruction from the DCSF is to terminate and originate the media; and also replace the DC endpoint information as attribute lines "a=tlsId", "a=sctp-port", "a=fingerprint" and "a=setup" when the media proxy configuration is HTTP proxy; and
d) delete the media description in the SDP answer if the instruction from the DCSF is to originate a new media;
and send the 183 (Session Progress) or 200 (OK) response with the modified SDP answer on the re-INVITE request to the S-CSCF towards to the originating UE after the receipt of an acknowledgement from the DCSF to the corresponding notification; or
if the application data channel is rejected, the IMS AS shall notify the DCSF about the media change failure event and request the MF to release the media resources. Then, the IMS AS shall send 183 (Session Progress) or 200 (OK) response to S-CSCF after the receipt of an acknowledgement from the DCSF to the corresponding notification.
Upon receipt of a CANCEL request to the re-INVITE request, the IMS AS shall notify the DCSF about the media change cancellation, request the MF to release the corresponding data channel media resources, and forward the CANCEL request as per clause 9.3.2.2.1.
Upon receipt of a 4xx, 5xx or 6xx response on the re-INVITE request from the terminating network, the IMS AS shall notify the DCSF about media change failure, request the MF to release the corresponding data channel media resources and forward the response to the originating UE.
Upon receiving the re-INVITE request from the terminating network to setup data channels and the corresponding response from the originating UE, the procedure in clause 9.3.3.2.2 applies.
9.3.2.2.2.2A Support of data channel interworking between an DC capable originatiing UE and a non-DC capable terminating UE
When the IMS AS receives an initial INVITE or the re-INVITE request with an SDP offer that contains the media description for the bootstrap data channel, the procedure in clause 9.3.2.2.1 and clause 9.3.2.2.2.1 applies. If the IMS AS receives the SIP response to the initial INVITE or the re-INVITE request in which the SDP answer indicates the remote bootstrap data channel to the terminating UE is rejected, the IMS AS may check the Contact header field of the received response. If the media feature tag "sip.video" is contained in the received Contact header field, the IMS AS may report to the DCSF about that the terminating UE supports video media. On receipt of a re-INVITE request with an SDP offer that contains media description for application data channel in which the "endpoint" parameter is set to "UE" in attribute "a=3gpp-app-req" line, the IMS AS shall follow the procedure from clause 9.3.2.2.2.2 with the following additions.
If the IMS AS, after reporting the media change request event to the DCSF as per clause 9.3.2.2.2.2, received from the:
- an instruction to transform the application data channel media to video media, the IMS AS shall:
a) request the MF to allocate the video media resources as well as the data channel media resources (as specified in 3GPP TS 29.176 [19]) and generate and add the SDP offer the media description for video media based on the reserved video media resource information by the MF; and
b) delete media description for the corresponding application data channel in SDP offer, or
- an instruction to terminate the data channel and indicates the interworking, the IMS AS shall delete the media description for the application data channel; request the MF to allocate media resources for a P2A application data channel and notify the NEF the DC interworking required event as specified in 3GPP TS 29.175 [18].
The IMS AS shall send the re-INVITE request with the updated SDP offer to the S-CSCF towards the terminating network.
Upon receiving the 200 (OK) response with the SDP answer on the re-INVITE request, the IMS AS shall report the media change success event to the DCSF. If the instruction from the DCSF when reporting the media change request event to DCSF was:
- to transform the application data channel media to video media, the IMS AS shall:
a)- request the MF to associate the data channel application to the video streams as per 3GPP TS 29.176 [19];
b)- delete the media description of the video media from the SDP answer; and
c) generate and add the corresponding application data channel media description in the SDP answer by using the DC endpoint information allocated on the termination towards to the originating UE on the MF with the "endpoint" parameter set to "UE" in attribute "a=3gpp-app-req" line; or
- to terminate the application data channel and indicates the interworking, the IMS AS shall:
a) generate and add the corresponding application data channel media description in the SDP answer as per clause 9.3.2.2.2.2 with the "endpoint" parameter set to "server" in attribute "a=3gpp-app-req" line.
9.3.2.2.2.3 Closing application data channel
Upon receipt of the re-INVITE request with an SDP offer which contains an existing application data channel media description in which an existing "a=dcmap" is removed, the IMS AS shall notify the DCSF about media change request event, and request MF to update the media resource when receiving the media instruction from DCSF is to update the media.
Upon receipt of the re-INVITE request with an SDP offer which contains an existing application data channel media description in which the UDP port number is set to 0, the IMS AS shall notify the DCSF about media change request event, and request the MF to release the corresponding media resource when receiving the media instruction from the DCSF is to delete the media.
Upon receipt of the 200 (OK) response on the re-INVITE message with the SDP answer, the procedure in clause 9.3.2.2.2.2 applies.
Upon receiving the re-INVITE request from the terminating network to close data channels and the corresponding 200 (OK) response from the originating UE, the procedure in clause 9.3.3.2.2.3 applies.
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.3.2.2.2.4 Network-initiated data channel establishment and update
| If the IMS AS received a request from the NEF or trusted AF to update an existing IMS session to add a P2A application data channel and/or bootstrap data channel as specified in 3GPP TS 29.175 [18] towards a served UE, the IMS AS shall:
a) determine whether the served user is authorized to use IMS data channel as specified in clause 9.3.2.2.1.
b) determine whether the requested application data channel is already established based on the comparison of the application binding information included in the request from the NEF or trusted AF with the "a=3gpp-req-app" attribute line within the application data channel media descriptions included in the latest stored SDP offer/answer for this IMS session;
c) determine whether the requested bootstrap data channel is already established based on the "dcmap" attribute containing a subprotocol parameter set to "http" and "stream-id" parameter set to values 0 and 10 within the data channel media descriptions included in the latest stored SDP offer/answer for this IMS session; or
d) determine whether the requested bootstrap data channel and/or application data channel is already established based on the comparison of the stored media correlation IDs with the one included in the request from the NEF.
If the served user is authorized to use data channel and the requested application data channel and/or bootstrap data channel is not established, the IMS AS shall select a DCSF and notify the DCSF about the external session update event. Based on the instruction of the DCSF, the IMS AS shall request the MF to allocate data channel media resources and
- generate the media description for:
a) the bootstrap data channel containing "a=dcmap" attribute line with the subprotocol parameter set to "http" and "stream-id" parameter set to values 0 and 10; or
b) the P2A application data channel containing "dcmap" attribute in which "stream-id" parameter set to values starting at 1000, "a=3gpp-req-app" attribute line with "endpoint" parameter set to value "server", "c=" line and "m=application" line with the IP address and UDP port number information of termination on the MF towards to the UE, and "a=tlsId", "a=sctp-port", "a=fingerprint" and "a=setup" attribute lines with the information of the termination on the MF towards the UE if the media proxy configuration is HTTP, or the information of the DC AS if the media proxy configuration is UDP; and
- include the DC-Info header field as specified in 3GPP TS 24.229 [9] 7.2.x to indicate the data channel is initiated by the DC AS;
and generate and send a re-INVITE request to the served UE with an updated SDP offer in which the generated media description of data channel above is added.
Upon reception of the 200 (OK) response to the re-INVITE request in which:
- the data channel media is accepted, the IMS AS shall notify the DCSF about the media change success event; or
- the data channel media is rejected, the IMS AS shall notify the DCSF about the media change failure event.
If the IMS AS receives a request from the NEF or trusted AF to establish a P2A2P application data channel between two UEs in an existing IMS session in which the video/audio media is established, the IMS AS shall
- follow the procedure above to determine the served user is authorized to use data channel and the requested application data channel is not established; and
- include the DC-Info header field as specified in 3GPP TS 24.229 [9] 7.2.x to indicate the data channel is initiated by the DC AS;
and generate the application data channel media descriptions and generate and send re-INVITE requests for the served UE and the remote UE.
Upon reception of the 200(OK) responses to the re-INVITE request:
- if both the two UEs accept the data channel media, the IMS AS shall notify the DCSF about the media change success event;
- if both the two UEs reject the data channel media, the IMS AS shall notify the DCSF about the media change failure event;
- if one UE accepts the data channel media, and the other UE rejects the data channel media, the IMS AS shall send a re-INVITE request to the UE who accepts the data channel media to close the established data channel, and notify the DCSF about the media change failure.
If the IMS AS received a request from the NEF or trusted AF to update an existing IMS session to add a P2P application data channel as specified in 3GPP TS 29.175 [18], the IMS AS shall determine the served user is authorized to use data channel and the requested application data channel is not established, notify the DCSF about the external session update event. If the DCSF instructs to anchor the added application data channel on the MF of the originating network, the IMS AS shall request the MF to allocate the data channel media resource on the termination towards the served originating UE. Based on the data channel media information from the MF, the IMS AS generates an application data channel media description containing "dcmap" attribute in which "stream-id" parameter set to values starting at 1000, "a=3gpp-req-app" attribute line with "endpoint" parameter set to value "UE", "c=" line and "m=application" line with the IP address and UDP port number information and "a=tlsId", "a=sctp-port", "a=fingerprint" and "a=setup" attribute lines with the information of the termination on the MF towards the originating UE; and generate and send the re-INVITE request to originating UE.
Upon receiving the 200 (OK) response to the re-INVITE request including the SDP answer for the application data channel from the originating UE, the IMS AS shall request the MF to update the data channel media resources of the termination towards the originating UE and create the data channel media resources of the termination towards the terminating UE. Based on the media resources created by the MF, the IMS AS shall create an application data channel media description containing "dcmap" attribute in which "stream-id" parameter set to values starting at 1000, "a=3gpp-req-app" attribute line with "endpoint" parameter set to value "UE", "c=" line and "m=application" line with the IP address and UDP port number information and "a=tlsId", "a=sctp-port", "a=fingerprint" and "a=setup" attribute lines with the information of the termination on the MF towards the terminating network and generate and send the re-INVITE request to terminating network.
Upon receiving the 200 (OK) response to the re-INVITE request from the terminating network, the IMS AS shall update the media resources of the termination towards the terminating network. And then, the IMS AS shall send ACK to both terminating network and originating UE and notify about the media change success event.
If the served user is authorized to use data channel and the requested application data channel and/or bootstrap data channel is established, the IMS AS shall follow the requirement as specified in 3GPP TS 29.175 [18].
If the IMS AS received a request from the NEF or trusted AF to update an existing IMS session to update an application data channel and/or bootstrap data channel as specified in 3GPP TS 29.175 [18] towards a served UE, the IMS AS shall:
a) determine the requested application data channel based on the comparison of the application binding information included in the request from the NEF or trusted AF with the "a=3gpp-req-app" attribute line within the application data channel media descriptions included in the latest stored SDP offer/answer for this IMS session;
b) determine the requested bootstrap data channel based on the "dcmap" attribute containing a subprotocol parameter set to "http" and "stream-id" parameter set to values 0 and 10 within the data channel media descriptions included in the latest stored SDP offer/answer for this IMS session; or
c) determine the requested bootstrap data channel and/or application data channel based on the comparison of the stored media correlation IDs with the one included in the request from the NEF; and
d) select a DCSF and notify the DCSF about the external session update event.
Based on the instruction of the DCSF, the IMS AS shall request the MF to update data channel media resources and update the media descriptions for the requested application data channel and/or bootstrap data channel and generate and send re-INVITE request for the served UE and also the remote UE when P2P or P2A2P application data channel is to be updated. In the re-INVITE request, the IMS AS shall include the DC-Info header field as specified in 3GPP TS 24.229 [9] 7.2.23 to indicate the data channel is updated by the DC AS.
If the requested application data channel and/or bootstrap data channel to update does not exist, the IMS AS shall follow the requirement as specified in 3GPP TS 29.175 [18].
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.3.2.2.2.5 Network-determined closing of bootstrap and application data channel
| If the IMS AS determines to terminate the established bootstrap data channels and application data channels to the terminating UE (e.g., due to supplementary service procedures as specified in clause 10.19.2) during the session modification, the procedure defined in clause 9.3.3.2.2.4 applies.
NOTE: This clause defines the procedure for network-determined closing of data channel based on the network's decision, such as supplementary service procedures as specified in clause 10.19.2, and not based on the request from NEF or trusted AF.
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.3.2.2.2.6 Network-initiated data channel termination based on the request from the trusted AF
| If the IMS AS received a request from the NEF or trusted AF to update an existing IMS session to terminate an application data channel and/or bootstrap data channel towards the originating or the terminating UE as specified in 3GPP TS 23.228 [3] clause AG.2.1, the IMS AS shall:
a) determine the requested application data channel based on the comparison of the application binding information included in the request from the NEF or trusted AF with the "a=3gpp-req-app" attribute line within the application data channel media descriptions included in the latest stored SDP offer/answer for this IMS session;
b) determine the requested bootstrap data channel based on the "dcmap" attribute containing a subprotocol parameter set to "http" and "stream-id" parameter set to values 0 and 10 within the data channel media descriptions included in the latest stored SDP offer/answer for this IMS session; or
c) determine the requested bootstrap data channel and/or application data channel based on the comparison of the stored media correlation IDs with the one included in the request from the NEF; and
notify the DCSF about external session update event as specified in 3GPP TS 29.175 [18], request MF to release or update the corresponding data channel media resource and send a re-INVITE request towards the UE with the subsequent SDP offer based on the media information of the data channel required by the NEF or the trusted AF. In the SDP offer, the IMS AS shall:
- set the UDP port number of the corresponding data channel media description to zero, if the required application data channel and/or bootstrap data channel is not multiplexed; or
- remove the "a=dcmap" attribute line associated with the required bootstrap data channel or application data channel and also the "a=3gpp-req-app" attribute if all the related application data channels for that application are to be terminated from the corresponding multiplexed data channel media description.
In the re-INVITE request, the IMS AS shall include the DC-Info header field as specified in 3GPP TS 24.229 [9] 7.2.23 to indicate the data channel is terminated by the DC AS.
Upon reception of the 200 (OK) response to the re-INVITE request, the IMS AS shall notify the DCSF about the media change success event.
If the requested application data channel and/or bootstrap data channel to terminate does not exist, the IMS AS shall follow the requirement as specified in 3GPP TS 29.175 [18].
If a request is to terminate only the bootstrap data channel in an existing IMS session containing application data channels, the IMS AS shall reject the request and follow the requirement as specified in 3GPP TS 29.175 [18].
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.3.2.2.3 MMTel session release
| Upon initiation or receipt of a BYE request matching an existing MMTel session with IMS data channel, the IMS AS shall notify session termination event to the DCSF and follow the call release procedure as per 3GPP TS 24.229 [9].
IMS AS shall send media resource management request to MF to release the allocated data channel media resources for this MMTel session.
Upon receipt of a request from the NEF or trusted AF to terminate a standalone IMS data channel session as specified in 3GPP TS 23.228 [3] clause AG.2.3, the IMS AS shall:
1) request MF to release the allocated data channel media resources for this standalone IMS data channel session;
2) send a BYE request containing the DC-Info header field as specified in 3GPP TS 24.229 [9], clause 7.2.23 to indicate this standalone IMS data channel session is terminated by the DC AS to both the served UE and the remote network; and
3) notify session termination event to the DCSF.
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.3.2.2.4 Support of standalone IMS data channel session
| |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.3.2.2.4.1 General
| If the IMS AS received from:
- the originating UE an initial INVITE request with the SDP offer containing only data channel media description; or
- the originating UE a re-INVITE request with the SDP offer in which the audio and video media is removed (i.e. the port number of the audio/video media set to 0);
the IMS AS shall determine whether the served user is authorized to use a standalone IMS data channel or not by the local configuration or the subscription data. If the user is not authorized to use IMS standalone data channel, the IMS AS shall send 401 (Unauthorized) to the originating UE to reject the session or to reject the media change request.
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.3.2.2.4.2 Standalone bootstrap data channel establishment
| Upon receipt of an initial INVITE request in which:
1) the SDP offer only includes IMS data channel media description for the local bootstrap data channel; and
2) the specific "request-uri" indicating standalone data channel contained in the Request-URI,
and the IMS AS determines that the user is authorized to use standalone data channel, the IMS AS shall:
a) notify the DCSF about session establishment request event;
b) request the MF to allocate the data channel media resources as per clause 9.3.2.2.1;
c) return a 200 (OK) response to the initial INVITE request with the SDP answer generated as per 3GPP TS 26.114 [4] and IETF RFC 8864 [14] to the S-CSCF towards the originating UE; and
d) notify the DCSF about the session establishment success event.
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.3.2.2.4.3 Void
| 9.3.2.2.4.3A Subsequent standalone bootstrap data channel and application data channel establishment
Upon receipt of the initial INVITE request towards a terminating UE with the SDP offer which only includes media descriptions for bootstrap data channels and the 183 (Session Progress) response to the initial INVITE request from the terminating network, the IMS AS shall follow the procedure in clause 9.3.2.2.1 to handle the bootstrap data channel media.
Upon receipt of the UPDATE request with an updated SDP offer that contains a data channel media description for the established bootstrap data channel, as well as the requested application data channel and the associated DC application binding information (provided within the "a=3gpp-req-app" SDP attribute) and the 200 (OK) response to the UPDATE request, the IMS AS shall follow the procedures upon receipt of the re-INVITE request and the response to the re-INVITE request in clause 9.3.2.2.2.2 to handle the application data channel media.
Upon receipt of the 200 (OK) response to the initial INVITE request from the terminating network, the IMS AS shall notify the DCSF about the session establishment success event and forward the 200 (OK) response to the originating UE.
Upon receipt of a 4xx, 5xx or 6xx response on the initial INVITE request from the terminating network, the IMS AS shall notify the DCSF about session establishment failure, request the MF to release the data channel media resources and forward the response to the originating UE.
Upon receipt of a 4xx, 5xx or 6xx response to the UPDATE request from the terminating network, the IMS AS shall notify the DCSF about media change failure, request the MF to release the corresponding data channel media resources and forward the response to the originating UE.
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.3.2.2.4.4 Combined standalone bootstrap data channel and application data channel establishment
| Upon receipt of the initial INVITE request towards a terminating UE with the SDP offer which includes the media description for both bootstrap data channel and application data channel and the 183 (Session Progress) response to the initial INVITE request from the terminating network, the IMS AS shall follow the procedure in clause 9.3.2.2.1 to handle the bootstrap data channel media and clause 9.3.2.2.2.2 to handle the application data channel media.
Upon receipt of the UPDATE request with an updated SDP offer that contains a data channel media description for the established bootstrap data channel, as well as the requested application data channel and the associated DC application binding information (provided within the "a=3gpp-req-app" SDP attribute) and the 200 (OK) response to the UPDATE request, the IMS AS shall follow the procedure in clause 9.3.2.2.2.2 to handle the application data channel media.
Upon receipt of the 200 (OK) response to the initial INVITE request from the terminating network, the IMS AS shall notify the DCSF about the session establishment success event and forward the 200 (OK) response to the originating UE.
Upon receipt of a 4xx, 5xx or 6xx response on the initial INVITE request from the terminating network, the IMS AS shall notify the DCSF about session establishment failure, request the MF to release the data channel media resources and forward the response to the originating UE.
Upon receipt of a 4xx, 5xx or 6xx response to the UPDATE request from the terminating network, the IMS AS shall notify the DCSF about media change failure, request the MF to release the corresponding data channel media resources and forward the response to the originating UE.
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.3.2.2.5 Enforcement of 3GPP PS data off
| If "Services over IMS Data Channel" is not in the list of 3GPP PS data off exempt services, upon receipt of a third-party REGISTER request containing a "+g.3gpp.ps-data-off" Contact header field parameter indicating the 3GPP PS data off status of the UE, in addition to the procedure in 3GPP TS 24.229 [9] clause 5.7.1.26, the IMS AS serving the UE:
1) may notify the DCSF about the 3GPP PS data off status of the UE by session establishment request event and PS data off status change event as specified in 3GPP TS 29.175 [18] and 3GPP TS 23.228 [3] clause X.3.2;
2) if the 3GPP PS data off status of the UE is changed from "inactive" to "active" and no SIP message removing all the IMS data channels in the ongoing MMTel session is received within an operator defined time, shall:
- generate a re-INVITE request including an SDP offer that contains the IMS data channel media descriptions for both bootstrap data channels and application data channels and set the UDP port number of each IMS data channel media description to zero, send to the served UE and remote network, notify the DCSF about media change request event due to the activation of the 3GPP PS data off and "Services over IMS Data Channel" is not in the list of 3GPP PS data off exempt services, and request MF to release the media resource for IMS data channels; and
- terminate the ongoing standalone IMS data channel session by applying procedures defined in 9.3.2.2.3; and
3) if the 3GPP PS data off status of the UE is changed from "inactive" to "active", no SIP message removing all the IMS data channels in the ongoing establishment of the MMTel session is received within an operator defined time, the IMS AS serving the UE received an initial INVITE request with IMS data channel media description(s) in the SDP offer and a final response to that initial INVITE request is not yet sent towards the served UE:
a) if the initial SDP offer contained only IMS data channel media description(s):
- shall send a 403 (Forbidden) response towards the served UE;
- if the initial INVITE request has been sent towards the terminating network, shall send a CANCEL request towards the terminating network;
- shall notify the DCSF about a session termination event due to the activation of the 3GPP PS data off and "Services over IMS Data Channel" is not in the list of 3GPP PS data off exempt services; and
- if the MF already allocated IMS data channel media resources, shall request the MF to release the allocated data channel media resource; or
b) if the initial SDP offer also contained other media description(s):
- if the IMS AS serving the UE did not yet receive the SDP answer, shall wait for reception of a SIP message with the SDP answer. Upon reception of the SDP answer, if at least one of the offered IMS data channel media descriptions is accepted (e.g., local or remote bootstrap data channel), the IMS AS serving the UE shall:
A) modify the SDP answer by setting the UDP port number of each accepted IMS data channel media description to zero and forward the received SIP message with the modified SDP answer to the served UE; and
B) create a new SDP offer in which the UDP port number of each accepted IMS data channel media description is set to zero and send the SDP offer within the UPDATE (or PRACK) request towards the terminating network;
- if the IMS AS serving the UE forwarded the SDP answer with accepted IMS data channel media descriptions to the served UE and there is no ongoing SDP offer/answer exchange, shall create a new SDP offer in which the UDP port number of each IMS data channel media description is set to zero and send the SDP offer within the UPDATE request towards the served UE and terminating network;
- notify the DCSF about media change request event due to the activation of the 3GPP PS data off and "Services over IMS Data Channel" is not in the list of 3GPP PS data off exempt services; and
- if the MF already allocated IMS data channel media resources, request the MF to release the allocated data channel media resource.
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.3.2.2.6 Support of data channel interworking between a non-DC capable originating UE and a DC capable terminating UE
| Upon receipt of an initial INVITE request with an SDP offer containing the audio and video media description from the originating UE, if the interworking required event subscribed and the IMS AS determines that the originating UE is a non-DC capable UE as specified in clause 9.2.1.2 and clause 9.2.2.2, the IMS AS shall notify the NEF or the trusted AF about the interworking required event based on the subscription from them as specified in 3GPP TS 23.228 [3] clause AC.7.9.4 and 3GPP TS 29.175 [18].
After the final response of the initial INVITE request received, the IMS AS shall notify the NEF or the trusted AF about the IMS session establishment event based on the subscription as specified in 3GPP TS 23.228 [3] clause AC.7.9.4 and 3GPP TS 29.175 [18].
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.3.2.2.7 Handling of data channel multiplexing
| |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.3.2.2.7.1 General
| When the IMS AS receives from the originating UE an initial INVITE with the SDP offer containing only the multiplexed data channel media description(s), if the data channel multiplexing is not supported or not allowed, the IMS AS shall return 488 (Not Acceptable Here) response containing an SDP message body.
Upon receipt of a 488 response to the initial INVITE request with the SDP offer containing only the multiplexed data channel media description(s), the IMS AS shall notify the DCSF about session establishment failure and request the MF to modify the data channel media resources of multiplexed data channels towards the terminating network based on the media instruction from the DCSF. After the successful response from the MF, the IMS AS shall modify the SDP offer with de-multiplexed data channel media descriptions and resend the initial INVITE request towards the terminating network.
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.3.2.2.7.2 Bootstrap data channel multiplexing
| When the IMS AS receives from the originating UE an initial INVITE, a re-INVITE or an UPDATE request with an SDP offer that contains a multiplexed bootstrap media description, if the data channel multiplexing is supported and allowed, the IMS AS shall select and notify the DCSF as specified in clause 9.3.2.2.1, clause 9.3.2.2.2, and clause 9.3.2.2.4.
Based on the instruction of the DCSF, the IMS AS shall select an MF supporting data channel multiplexing and request the MF to allocate data channel media resources for the multiplexed data channels. Based on the response from the MF, the IMS AS shall modify the SDP offer:
- delete the local bootstrap data channel related attributes ( the "dcmap" attribute line containing a subprotocol parameter set to "http" and "stream-id" parameter set to values 0 and 10) from the received multiplexed bootstrap data channel media description and add the "a=3gpp-bdc-used-by:" attribute line containing "bdc-used-by" parameter set to value "sender" if the "dcmap" attribute line containing a subprotocol parameter set to "http" and "stream-id" parameter set to values 100 and 110 presents, if the DCSF indicates the media is to be de-multiplexed and the media instruction from the DCSF is to terminate and originate the media;
- generate and add the remote bootstrap data channel media description for the terminating UE (media line with the "dcmap" attribute containing a subprotocol parameter set to "http" and "stream-id" parameter set to values 100 and 110 and "a=3gpp-bdc-used-by:" attribute with "bdc-used-by" parameter set to value "receiver"), i.e. remote bootstrap data channel between the originating network and the terminating UE, if the media instruction from the DCSF is to originate the media;
Upon the reception of an acknowledgement from the DCSF to the event notification, the IMS AS shall send the received SIP request with the modified SDP offer towards the terminating network.
Upon receipt of the 18x or 2xx response including SDP answer to the initial INVITE, re-INVITE or UPDATE request, the IMS AS shall notify the DCSF about corresponding session event or media change event and request the MF to update the media resource as specified in clause 9.3.2.2.1, clause 9.3.2.2.2, and clause 9.3.2.2.4. Based on the response from the MF, the IMS AS shall modify the SDP answer:
- delete the remote bootstrap data channel media description for the terminating UE (media line with the "dcmap" attribute containing a subprotocol parameter set to "http" and "stream-id" parameter set to values 100 and 110 and "a=3gpp-bdc-used-by" attribute with "bdc-used-by" parameter set to value "receiver"), i.e. the remote bootstrap data channel between the originating network and terminating UE;
- add the local bootstrap data channel related attributes ( the "dcmap" attribute line containing a subprotocol parameter set to "http" and "stream-id" parameter set to values 0 and 10), and replace the IP address as well as the DC endpoint information with the media resource information allocated by the MF towards the originating UE, if the original media is multiplexed bootstrap data channel media description and the media instruction from the DCSF is to terminate and originate the media;
and send the response with the modified SDP answer towards to the originating UE.
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.3.2.2.7.3 Application data channel multiplexing
| When the IMS AS receives from the originating UE an initial INVITE, re-INVITE or UPDATE request with an SDP offer that contains a multiplexed application data channel media description, if the data channel multiplexing is supported and allowed, the IMS AS shall notify the DCSF as specified in clause 9.3.2.2.2.
Based on the instruction from the DCSF, the IMS AS shall request the MF to allocate data channel media resources as specified 3GPP TS 29.176 [19].
If DCSF determines not to demultiplex the multiplexed media as specified in 3GPP TS 29.175, the IMS AS shall follow the procedure of clause 9.3.2.2.2.2 to handle the application data channel media description and send the INVITE, re-INVITE or UPDATE request with the multiplexed application data channel media description in the SDP offer to the terminating network.
If the DCSF determines to demultiplex the multiplexed media, for the multiplexed media description, the IMS AS shall:
1) remove the parameters "adc-info" with the "adc-stream-id-endpoint" is set to "Server" in attribute "a=3gpp-req-app" line and the corresponding "a=dcmap" lines with the same "stream-id" in the multiplexed data channel media description;
2) if media instruction from DCSF is to originate a new media and include one existing media Id as the associated media Id in the instruction (i.e. the media identified by associated media Id is demultiplexed), generate and add a new media description for the new de-multiplexed data channel in the SDP offer; and
3) remove the "a=dcmap" lines and the related "a=3gpp-req-app" lines that are using separate media descriptions in bullet 2) in the original multiplexed media description.
Upon receipt of the 488 (Not Acceptable Here) response or 18x or 200 (OK) response to the INVITE, re-INVITE or UPDATE request and the multiplexed application data channel media is accepted, the IMS AS shall determine that the terminating network supports data channel multiplexing.
Upon receipt of the 488 (Not Acceptable Here) response or the 18x or 200 (OK) response in which the multiplexed application data channel media is rejected, the IMS AS shall:
1) notify the DCSF as specified in 3GPP TS 29.175 [x]; and
2) de-multiplex the application data channel media description as specified in the bullet 2) and 3) above and send the INVITE, re-INVITE or UPDATE request to the terminating network again.
Upon receipt of the 18x or 200 (OK) response from the terminating network to the INVITE, re-INVITE or UPDATE request with the demultiplexed data channel media in the SDP answer, the IMS AS shall multiplex the data channel media descriptions in the SDP answer using the original multiplexed media id in the SDP offer and send the 18x or 200 (OK) response to the originating UE.
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.3.3 Terminating side
| |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.3.3.1 Procedures at the UE
| |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.3.3.1.1 General
| The terminating UE can also setup or terminate data channels during the session modification.
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.3.3.1.2 IMS bootstrap data channel setup in conjunction with MMTel session setup
| If the terminating UE determines that the UE and the network supports the IMS data channel, on the reception of SIP initial INVITE request, the terminating UE shall include the media feature tags defined in IETF RFC 5688 [5] for supported streaming media type with +sip.app-subtype="webrtc-datachannel" as specified in 3GPP TS 26.114 [4] in the Contact header field of SIP 18x and 2xx responses to the SIP INVITE request.
If the terminating UE receives the initial INVITE request with an SDP offer which includes the data channel media descriptions, i.e. the "m=" line containing the media set to "application", the UDP port number, the proto value set to "UDP/DTLS/SCTP" and the fmt value set to "webrtc-datachannel" and with associated "dcmap" attribute lines containing a subprotocol parameter set to "http" and any "stream-id" parameter set to values 0, 10, 100 or 110, and the terminating UE:
1) is not configured with IMS_DC_configuration node as specified in 3GPP TS 24.275 [11] and EFIMSDCI file specified in 3GPP TS 31.103 [30] or 3GPP TS 31.102 [31], and the terminating UE:
a) accepts the offered bootstrap data channel(s), it shall generate the SDP answer based on the 3GPP TS 26.114 [4] and IETF RFC 8864 [14]; or
b) does not accept the offered bootstrap data channel(s), it shall set the port number(s) of the rejected data channel media stream(s) to zero in the generated SDP answer; or
2) is configured with IMS_DC_configuration node as specified in 3GPP TS 24.275 [11] and the DC_allowed leaf indicates that IMS data channel:
a) is allowed and if the terminating UE accepts the offered bootstrap data channel(s), it shall generate the SDP answer based on the 3GPP TS 26.114 [4] and IETF RFC 8864 [14]; or
b) is not allowed, it shall reject the offered bootstrap data channel media stream(s) by setting the port number of the rejected data channel media stream(s) to zero in the generated SDP answer,
3) is configured with EFIMSDCI file specified in 3GPP TS 31.103 [30] or 3GPP TS 31.102 [31] and the IMS DC Establishment Indication indicates that IMS data channel:
a) is allowed and if the terminating UE accepts the offered bootstrap data channel(s), it shall generate the SDP answer based on the 3GPP TS 26.114 [4] and IETF RFC 8864 [14]; or
b) is not allowed, it shall reject the offered bootstrap data channel media stream(s) by setting the port number of the rejected data channel media stream(s) to zero in the generated SDP answer,
and the terminating UE shall return a 18x or 2xx response to the INVITE request with the above generated the SDP answer.
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.3.3.1.3 IMS data channel setup in conjunction with MMTel session modification
| |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.3.3.1.3.1 IMS bootstrap data channel establishment
| If the terminating UE determines that the UE and the network supports the IMS data channel, when the UE receives the re-INVITE request with an SDP offer, which includes the bootstrap data channel media descriptions, i.e. the "m=" line containing the media set to "application", the UDP port number, the proto value set to "UDP/DTLS/SCTP" and the fmt value set to "webrtc-datachannel" and with associated "dcmap" attribute lines containing a subprotocol parameter set to "http" and any "stream-id" parameter set to values 0, 10, 100 or 110, the procedure defined in clause 9.3.3.1.2 applies.
If the terminating UE wants to setup a bootstrap data channel during the session modification by sending SIP re-INVITE request, the procedure defined in clause 9.3.2.1.3.1 applies.
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.3.3.1.3.2 IMS application data channel establishment
| If the terminating UE has an established bootstrap data channel associated with the MMTel session available and if the UE receives the re-INVITE request with an SDP offer which includes data channel media descriptions for the bootstrap data channel, as well as the requested application data channel and the associated data channel application binding information (provided within the "a=3gpp-req-app" SDP attribute), and the terminating UE accepts the offered application data channel, it shall return a 183 (Session Progress) or 200 (OK) response to the re-INVITE request with the generated the SDP answer based on the 3GPP TS 26.114 [4] and IETF RFC 8864 [14].
If the terminating UE wants to setup an application data channel, the procedure defined in clause 9.3.2.1.3.2 applies.
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.3.3.1.4 Closing IMS application data channel in conjunction with MMTel session modification
| If the terminating UE receives a re-INVITE request including an SDP offer in which the UDP port number of the data channel media description was set to zero or the "a=dcmap" line associated with an application data channel was removed from the data channel media description, and the terminating UE accepts the application data channel termination, it shall return a 200 (OK) response to the re-INVITE request with the generated SDP answer based on the IETF RFC 8864 [14].
If the terminating UE wants to close an established application data channel during the session modification by sending re-INVITE request, the procedure defined in clause 9.3.2.1.4 applies.
NOTE: The application data channel termination during the session modification does not impact the ongoing audio, video or other data channels within the MMTel session.
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.3.3.1.5 Closing IMS data channel in conjunction with MMTel session release
| When the UE releases an MMTel session that has associated bootstrap and application data channels, the UE shall apply procedures defined in 3GPP TS 24.229 [9] clause 5.1.5 and shall close bootstrap and application data channels.
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.3.3.1.6 Support of standalone IMS data channel session
| |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.3.3.1.6.1 Void
| |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.3.3.1.6.2 Void
| 9.3.3.1.6.2A Adding application data channel during standalone IMS data channel session establishment
Upon receipt of the initial INVITE request with the SDP offer with only the media description for the bootstrap data channel and the UE accepts the bootstrap data channel, the UE shall return a 183 (Session Progress) response to the initial INVITE request with the SDP answer generated as per 3GPP TS 26.114 [4] and IETF RFC 8864 [1].
NOTE 1: When receiving the incoming INVITE request, the UE can alert the user that there is a standalone data channel establishing based on the UE's implementation for user consent.
Upon receipt of the UPDATE request with the updated SDP offer containing the established bootstrap data channel and a requested application data channel with the associated DC application binding information (provided within the "a=3gpp-req-app" SDP attribute) according to 3GPP TS 26.114 [4] to establish an application data channel, the UE shall determine whether the data channel application has been downloaded or not. If the data channel application:
a) has not been downloaded, the UE shall:
1) download the data channel application using the value in "a=3gpp-req-app" attribute line via the established bootstrap data channel;
2) alert the user and return the 180 (Ringing) once the data channel application is downloaded;
3) generate the SDP answer that contains the media description for the bootstrap data channel and application data channel as per 3GPP TS 26.114 [4] and IETF RFC 8864 [1] and return the 200 (OK) response to the UPDATE request; and
4) return 200 (OK) response to the INVITE request; or
b) has been downloaded, the UE shall:
1) alert the user and return the 180 (Ringing);
2) generate the SDP answer that contains media descriptions for both the bootstrap data channel and application data channel as per 3GPP TS 26.114 [4] and IETF RFC 8864 [1] and return the 200 (OK) response to the UPDATE request; and
3) return 200 (OK) response to the INVITE request.
NOTE 2: Based on the UE's implementation for user consent, the UE can alert the user that the data channel application is downloaded.
If the UE did not successfully download the data channel application, the UE shall reject the INVITE or re-INVITE or UPDATE request with a suitable 4xx response code. In this case, the UE shall not alert the terminating user.
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.3.3.1.6.3 Combined standalone bootstrap data channel and application data channel establishment
| Upon receipt of the initial INVITE request with the SDP offer with the media description for both the bootstrap data channel and the application data channel associated with the application binding information in "a=3gpp-req-app" line, the UE shall determine whether the data channel application has been downloaded or not. If the data channel application:
a) has not been downloaded, the UE:
1) shall generate SDP answer for the data channel as per 3GPP TS 26.114 [4] and IETF RFC 8864 [1] accepting the bootstrap data channel and rejecting the application data channel by setting the port number of m=line of application data channel to zero, indicate the data channel application is desired to be downloaded according to 3GPP TS 23.228 [3] clause AC.10.2.3 and return a 183 (Session Progress) response with the generated SDP answer to the initial INVITE request;
NOTE 1: When receiving the incoming INVITE request, the UE can alert the user that there is a standalone data channel establishing based on the UE's implementation for user consent.
2) download the data channel application using the value in "a=3gpp-req-app" attribute line via the established bootstrap data channel;
3) upon receipt of the UPDATE request with the updated SDP offer to establish the corresponding application data channel,
- alert the user and return the 180 (Ringing) once the data channel application is downloaded;
- generate the SDP answer as per 3GPP TS 26.114 [4] and IETF RFC 8864 [1] and return the 200 (OK) response to the UPDATE request;
- return 200 (OK) to the INVITE request; or
b) has been downloaded, the UE shall:
1) generate the SDP answer that contains both the bootstrap data channel and application data channel as per 3GPP TS 26.114 [4] and IETF RFC 8864 [1] and return the 183 (Session Progress) response to the network;
2) alert the user and return the 180 (Ringing) response; and
3) return the 200 (OK) response to the INVITE request.
NOTE 2: Based on the UE's implementation for user consent, the UE can alert the user that data channel application is downloaded.
If the UE did not successfully download the data channel application, the UE shall reject the INVITE or re-INVITE or UPDATE request with a suitable 4xx response code. In this case, the UE shall not alert the terminating user.
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.3.3.1.6.4 Adding video/audio media to standalone IMS data channel session
| Upon receipt of the re-INVITE request with an updated SDP offer in which the audio/video media description is added within the standalone IMS data channel session, the UE shall return a 183 (Session Progress) or 200 (OK) response to the re-INVITE request with the generated the SDP answer based on the 3GPP TS 26.114 [4].
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.3.3.1.6.5 Removing video/audio media from IMS data channel session
| Upon receipt of the re-INVITE request with an updated SDP offer in which the port number of audio/video media description is set to zero, the UE shall return a 183 (Session Progress) or 200 (OK) response to the re-INVITE request with the generated the SDP answer based on the 3GPP TS 26.114 [4].
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.3.3.1.7 Enforcement of 3GPP SIP-Based 3GPP PS Data Off Exempt Services
| When 3GPP PS data off is supported and 3GPP PS data off status is changed to "active", if "Services over IMS Data Channel" is not in the list of 3GPP PS data off exempt services:
1) if the UE received an initial INVITE request with IMS data channel media description(s) in the SDP offer and did not yet send a final response to the initial INVITE request:
a) if the initial SDP offer contained only IMS data channel media description(s), the UE shall send a 403 (Forbidden) response; or
b) if the initial SDP offer also contained other media description(s):
- if the UE did not yet send the SDP answer, the UE shall reject the offered IMS data channel media description(s) by setting the UDP port number of the rejected data channel media description(s) to zero in created SDP answer and shall send a SIP response to the initial INVITE request with the generated SDP answer; or
- if the UE already sent the SDP answer with the accepted IMS data channel media descriptions and there is no ongoing SDP offer/answer exchange, the UE shall create a new SDP offer in which the UDP port number of each accepted IMS data channel media description is set to zero and send the SDP offer within UPDATE request; and
2) otherwise, the procedure defined in clause 9.3.2.1.7 applies.
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.3.3.1.8 Support of the data channel multiplexing
| Upon receiving an initial INVITE, a re-INVITE or a UPDATE request with an SDP offer, which contains the multiplexed data channel media description(s), the UE shall:
1) follow the procedures of clause 9.3.3.1.2, clause 9.3.3.1.3, clause 9.3.3.1.4, and clause 9.3.3.1.6.3 to generate a response to the initial INVITE, re-INVITE or UPDATE request;
2) include the "g.3gpp.dc-mux" media feature tag defined in 3GPP TS 26.114 [4] in the Contact header field;
3) if the UE determines both the UE and its home IMS network support IMS data channel multiplexing capability and accepts the requested IMS data channels in the single m line in the SDP offer, generate an SDP answer based on the 3GPP TS 26.114 [4] and IETF RFC 8864 [14];
4) if the UE determines both the UE and its home IMS network support IMS data channel multiplexing capability but accepts neither of the offered IMS data channels, or if the UE does not support IMS data channel multiplexing capability, set the port number(s) of the multiplexed data channel media description(s) to zero; and
5) if the UE determines both the UE and its home IMS network support IMS data channel multiplexing capability and accepts the requested IMS data channels termination in the single m line in the SDP offer, generate an SDP answer based on the 3GPP TS 26.114 [4] and IETF RFC 8864 [14].
If the terminating UE wants to close an established multiplexed application data channel during the session modification by sending re-INVITE request with the subsequent SDP offer, the procedure defined in clause 9.3.2.1.4 applies.
If the UE wants to multiplex IMS data channels during IMS data channel establishment by sending SIP re-INVITE request, the procedure defined in clause 9.3.2.1.8 applies.
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.3.3.2 Procedures at the serving IMS AS for the terminating UE
| |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.3.3.2.1 IMS bootstrap data channel establishment in conjunction with MMTel session setup
| Upon receipt of a SIP initial INVITE request with the SDP offer including IMS data channel media descriptions from the originating network, if the IMS AS determined that the terminating registered UE:
1) supports IMS data channel capabilities and is authorized to use IMS data channel, the IMS AS shall notify the DCSF about a session establishment request event, with a calling identity set to the value of the P-Asserted-Identity header field and a called identity set to the value of Request URI of the received initial INVITE request, and shall not send a INVITE request to the S-CSCF until receiving an acknowledgement from the DCSF. Based on the received Media instruction set from the DCSF, the IMS AS shall select the MF and request the MF to allocate required data channel media resources. Based on the response of the reserved media resource from the MF, the IMS AS shall:
- delete the remote bootstrap data channel media description for the originating UE (the media line with the "dcmap" attribute containing a subprotocol parameter set to "http" and "stream-id" parameter set to values 100 and 110 and "a=3gpp-bdc-used-by" attribute with "bdc-used-by" parameter set to value "sender"), i.e. the remote bootstrap data channel between originating UE and terminating network in the SDP offer;
- replace the IP address represented in the "c=" line, the UDP port number in the "m=application" line as well as the DC endpoint information represented as the attribute lines including the "a=tlsId", "a=sctp-port", "a=fingerprint" and "a=setup" line in the remote bootstrap data channel media description for the terminating UE (the media line with the "dcmap" attribute containing a subprotocol parameter set to "http" and "stream-id" parameter set to values 100 and 110 and "a=3gpp-bdc-used-by" attribute with "bdc-used-by" parameter set to value "receiver"), i.e. the remote bootstrap data channel between terminating UE and originating network, with the media resource information for the termination towards the terminating UE if the media in anchored on the MF; and
- generate and add the local bootstrap data channel media description for the terminating UE (the media line with the "dcmap" attribute containing a subprotocol parameter set to "http" and "stream-id" parameter set to values 0 and 10), i.e. the local bootstrap data channel between the terminating network and terminating UE to the SDP offer.
upon the reception of a successful acknowledgement from the DCSF to the session establishment request event notification, the IMS AS shall send the initial INVITE request with the modified SDP offer via the S-CSCF towards the terminating registered UE of the served user, which support the IMS data channel capabilities; or
2) does not support IMS data channel capabilities or is not authorized to use IMS data channel, then based on the operator policy the IMS AS shall determine whether to remove from the SDP offer media lines related to the IMS data channels:
a) if the operator policy indicates removal of media lines related to the IMS data channels, the IMS AS shall not trigger the DC media resource reservation and the IMS AS shall remove from the received SDP offer media lines describing the bootstrap data channel(s) i.e.:
- "dcmap" attribute lines containing a subprotocol parameter set to "http" and "stream-id" parameter set to values 0, 10, 100 and 110; and
- if present, "a=3gpp-bdc-used-by:" attribute lines,
associated with the "m=" line containing the media set to "application", the UDP port number, the proto value set to "UDP/DTLS/SCTP" and the fmt value set to "webrtc-datachannel". If there are no other "dcmap" attribute lines that contain a subprotocol parameter set to value other than "http", the IMS AS shall remove any other SDP media attribute lines associated with that m line e.g., "sctp-port", "max-message-size", "tls-id", "a=setup", "a=3gpp-qos-hint" SDP attribute lines. The IMS AS shall send the SIP initial INVITE request with the modified SDP offer to the S-CSCF towards the terminating registered UE of the served user.
Upon receipt of a SIP initial INVITE request with the SDP offer not including IMS data channel media descriptions from the originating network, if the IMS AS determined that the terminating registered UE supports IMS data channel capabilities and is authorized to use IMS data channel, the IMS AS shall notify the DCSF of a session establishment request event and shall not send a INVITE request to the S-CSCF until receiving an acknowledgement from the DCSF. Based on the received media instruction set from the DCSF, the IMS AS shall select an MF and request the MF to allocate required data channel media resources.
Based on the response of the reserved media resource from the MF, the IMS AS shall generate and add the local bootstrap data channel media description for the terminating UE (the media line with the "dcmap" attribute containing a subprotocol parameter set to "http" and "stream-id" parameter set to values 0 and 10), i.e. the local bootstrap data channel between the terminating network and terminating UE to the SDP offer. Upon the reception of a successful acknowledgement from the DCSF to the session establishment request event notification, the IMS AS shall send the initial INVITE request with the modified SDP offer via the S-CSCF towards the terminating registered UE of the served user, which support the IMS data channel capabilities. If no media instruction received from the DCSF or no acknowledgement from the DCSF received, the IMS AS shall forward the initial INVITE request from the originating network (i.e. without IMS data channel media descriptions in the SDP offer) to the S-CSCF.
Upon receipt of the 18x or 2xx response on the initial INVITE message including the SDP answer which includes the data channel media description, the IMS AS shall notify the DCSF about corresponding session event (session establishment progress (i.e. receiving the 183 (Session Progress) response ), session establishment alerting (i.e. receiving the 180 (Ringing) response) or session establishment success (i.e. receiving the 200 (OK) response on the INVITE request) event) and shall request the MF to update the media resources. Based on the response from the MF, the IMS AS shall:
- generate and add the remote bootstrap data channel media description for the originating UE (the media line with the "dcmap" attribute containing a subprotocol parameter set to "http" and "stream-id" parameter set to values 100 and 110 and "a=3gpp-bdc-used-by" attribute with "bdc-used-by" parameter set to value "sender") in the SDP answer, i.e. the remote bootstrap data channel between originating UE and terminating network;
- replace the IP address represented in the "c=" line, the UDP port number in the "m=application" line as well as the DC endpoint information represented as the attribute lines "a=tlsId", "a=sctp-port", "a=fingerprint" and "a=setup" line within the remote bootstrap data channel media description for the terminating UE (the media line with the "dcmap" attribute containing a subprotocol parameter set to "http" and "stream-id" parameter set to values 100 and 110 and "a=3gpp-bdc-used-by" attribute with "bdc-used-by" parameter set to value "receiver"), i.e. the remote data channel between terminating UE and originating network, with the DC endpoint information for the termination towards the originating network allocated by the MF; and
- delete the bootstrap data channel media description (the media line with the "dcmap" attribute containing a subprotocol parameter set to "http" and "stream-id" parameter set to values 0 and 10) in the SDP answer, i.e. the bootstrap data channel between terminating UE and terminating network.
Upon receipt of the 18x or 2xx response including the SDP answer which only contains the data channel media description for the bootstrap data channel between terminating UE and terminating network, the IMS AS shall notify the DCSF, request the MF to update the media resources as above and delete this bootstrap data channel media description (i.e. the media line with the "dcmap" attribute containing a subprotocol parameter set to "http" and "stream-id" parameter set to values 0 and 10) in the SDP answer.
Upon the reception of an acknowledgement from the DCSF to the corresponding notification, the IMS AS shall include the modified SDP answer for data channel to originating network and send the 18x or 2xx response on the initial INVITE request to the S-CSCF.
Upon receipt of a CANCEL request the initial INVITE request, the IMS AS shall notify the DCSF about the session establishment cancellation, request the MF to release the corresponding data channel media resources, and forward the CANCEL request to the S-CSCF towards the terminating UE.
Upon receipt of a 4xx, 5xx or 6xx response on the initial INVITE request from the terminating UE, the IMS AS shall notify the DCSF about session establishment failure, and request MF to release the data channel media resources.
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.3.3.2.2 MMTel session modification
| |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.3.3.2.2.1 IMS bootstrap data channel establishment
| If the IMS AS received from the originating network a re-INVITE request with the SDP offer containing data channel media description for the bootstrap data channel establishment, if the IMS AS determined that the terminating registered UE:
- supports IMS data channel capabilities and is authorized to use IMS data channel, the IMS AS shall notify the DCSF about the media change request, with a calling identity set to the value of the P-Asserted-Identity header field and a called identity set to the value of Request URI of the initial INVITE request received during MMTel session establishment. If the media instruction from the DCSF is:
a) to reject the bootstrap data channel, the IMS AS shall send a 488 (Not Acceptable Here) to the originating network;
b) in other cases, based on the instruction from DCSF, the IMS AS shall request the MF to reserve the media resources and modify the data channel media description in the SDP offer and send the re-INVITE request as per clause 9.3.3.2.1. Upon receipt of the 183 (Session Progress) or 200 (OK) response to the re-INVITE request, the IMS AS shall send notify the DCSF about the media change success if the data channel media is accepted or media change failure if the data channel media is rejected and modify the data channel media description in the SDP answer and send the 183 (Session Progress) or 200 (OK) response to S-CSCF as per clause 9.3.2.2.1. Upon receipt of a CANCEL request to the re-INVITE request, the IMS AS shall notify the DCSF about the media change cancellation, request the MF to release the corresponding data channel media resources, and forward the CANCEL request as per clause 9.3.2.2.1. Upon receipt of a 4xx, 5xx or 6xx response on the re-INVITE request, the IMS AS shall notify the DCSF about the media change failure and forward the response to the originating network; and
- does not support IMS data channel capabilities or is not authorized to use IMS data channel, the procedure defined in clause 9.3.3.2.1 applies.
If the IMS AS received from the served user a re-INVITE request with the SDP offer containing data channel media description for the bootstrap data channel establishment, the procedure of the IMS AS in the originating network on receipt of a re-INVITE request from the originating UE defined in clause 9.3.2.2.2.1 applies.
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.3.3.2.2.2 IMS application data channel establishment
| Upon receipt of a re-INVITE request with the SDP offer including new application data channel media descriptions (the media lines with the "dcmap" attribute containing "stream-id" parameter set to values starting at 1000) along with the video, audio, and bootstrap data channel media descriptions from the originating network, the IMS AS shall notify the DCSF about the media change request. If the media instruction from the DCSF is
- to reject all the data channel medias in this request, the IMS AS shall send a 488 (Not Acceptable Here) response to the originating network and other medias are not updated; and
- in other cases, the IMS AS shall request MF to update the media resources. Based on the response on the data channel media resource update from the MF as specified in 3GPP TS 29.176 [19] and media instruction from DCSF as specified in 3GPP TS 29.175 [18], the IMS AS shall:
1) delete the data channel media description (media line with the "dcmap" attribute containing "stream-id" parameter set to the values starting at 1000 and "a=3gpp-req-app " attribute with "endpoint" parameter set to value "server") if the media instruction from DCSF is to terminate the media;
2) delete the data channel media description if the media instruction from DCSF is to reject the media as specified in 3GPP TS 29.175 [18] and there are other medias to be established;
3) replace the IP address represented in the "c=" line, the UDP port number in the "m=application" line in the data channel media description in the SDP offer with the media resource information for the termination towards the terminating UE allocated by the MF if the media instruction from DCSF is to terminate and originate the media, and also replace the DC endpoint information represented as the attribute lines "a=tlsId", "a=sctp-port", "a=fingerprint" and "a=setup" when the media proxy configuration is HTTP proxy; and
4) generate and add a data channel media description (media line with the "dcmap" attribute containing "stream-id" parameter set to values starting at 1000 and "a=3gpp-req-app " attribute with "endpoint" parameter set to value "server") by using the DC stream information provided by the DCSF in the attribute lines "a=dcmap" and "a=3gpp-req-app", DC endpoint information of the DC AS provided by the DCSF in the attribute lines "a=tlsId", "a=sctp-port", "a=fingerprint" and "a=setup", IP address and UDP port number allocated on the termination towards to the terminating UE on the MF in the "c=" line and "m=application" when the media proxy configuration is UDP proxy, or using the DC stream information provided by the DCSF in the attribute lines "a=dcmap" and "a=3gpp-req-app" and the IP address, UDP port number and DC endpoint information (e.g. tlsId, sctp-port) allocated on the termination towards to the terminating UE on the MF in the other attribute lines above when the media proxy configuration is HTTP proxy, if the media instruction from DCSF is to originate a new media as specified in 3GPP TS 29.175 [18].
- an existing application data channel media description in which the new "a=dcmap" line containing the "stream-id" parameter value set to values starting at 1000 is added, the IMS AS shall notify the DCSF about media change request, and request MF to update the media resource if the media instruction from DCSF is to update the media.
The IMS AS shall send the re-INVITE request to the S-CSCF with the modified SDP offer including the modified application data channel media description or the original application data channel media description if no media instruction received from DCSF as well as the media descriptions of established video, audio and bootstrap data channels, to the terminating UE.
Upon receipt of the 183 (Session Progress) or 200 (OK) response on the re-INVITE request with the SDP answer which contains media description of the requested application data channel from the terminating UE,
- if the application data channel is accepted, the IMS AS shall notify DCSF about the media change success and request the MF to update the media resources. Based on the response of the MF, the IMS AS shall:
a) generate and add a data channel media description in the SDP answer by using DC endpoint information of the DC AS provided by the DCSF in the attribute lines "a=tlsId", "a=sctp-port", "a=fingerprint" and "a=setup" and the IP address and the UDP port number allocated on the termination towards to the originating network on MF in the lines "c=" and "m=application", or using the IP address, the UDP port number and the DC endpoint information (e.g. tlsId, sctp-port) allocated on the termination towards to the originating network on the MF in the attribute lines above when the media proxy configuration is HTTP proxy, if the instruction from the DCSF is to terminate the media;
b) add the rejected media description and set the port number to 0 in the "m=application" line if the instruction from the DCSF is to reject the media and there are other medias to be established;
c) replace the IP address represented in the "c=" line, the UDP port number in the "m=application" line in the media description in the SDP answer with the media resource information on the termination towards to the originating network allocated by the MF if the instruction from the DCSF is to terminate and originate the media and also replace the DC endpoint information as attribute lines "a=tlsId", "a=sctp-port", "a=fingerprint" and "a=setup" when the media proxy configuration is HTTP proxy; and
d) delete the media description in the SDP answer if the instruction from the DCSF is to originate a new media;
and send the 183 (Session Progress) or 200 (OK) response with the modified SDP answer on the re-INVITE request to the S-CSCF towards to the originating network after the receipt of an acknowledgement from the DCSF to the corresponding notification; or
- if the application data channel is rejected, the IMS AS shall notify the DCSF about media change failure and request the MF to release the media resources. The IMS AS shall send the 183 (Session Progress) or 200 (OK) response to S-CSCF with the modified SDP answer for the requested application data channel as well as the media descriptions of established video, audio, and bootstrap data channels after the receipt of an acknowledgement from the DCSF to the corresponding notification.
Upon receipt of a CANCEL request to the re-INVITE request, the IMS AS shall notify the DCSF about the media change cancellation, request the MF to release the corresponding data channel media resources and forward the CANCEL request to the S-CSCF towards the terminating UE.
Upon receipt of a 4xx, 5xx or 6xx response on the re-INVITE request from the terminating UE, the IMS AS shall notify the DCSF about media change failure, request the MF to release the corresponding data channel media resources and forward the response to the originating network.
Upon receiving the re-INVITE request from the terminating UE to setup an application data channels and the corresponding response form the originating network, the procedure in clause 9.3.2.2.2.2 applies.
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.3.3.2.2.3 Closing application data channel
| Upon receipt of the re-INVITE request with an SDP offer which contains an existing application data channel media description in which the UDP port number is set to 0, the IMS AS shall notify the DCSF about media change request, and request the MF to release the corresponding media resource if the media instruction from DCSF is to delete the media.
Upon receipt of the re-INVITE request with an SDP offer which contains an existing application data channel media description in which an existing "a=dcmap" line is removed, the IMS AS shall notify the DCSF about media change request, and request MF to update the media resource if the media instruction from DCSF is to update the media.
Upon receipt of the 200 (OK) response on the re-INVITE message with the SDP answer, the procedure in clause 9.3.3.2.2.2 applies.
Upon receiving the re-INVITE request from the terminating UE to close an application data channels and the corresponding 200 (OK) response form the originating network, the procedure in clause 9.3.2.2.2.3 applies.
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.3.3.2.2.4 Network-determined closing of bootstrap and application data channel
| If the IMS AS determines to terminate the established bootstrap data channels and application data channels to the originating UE during the session modification (e.g. due to supplementary service procedures as specified in clause 10.19.2), the IMS AS shall send a re-INVITE request to the originating network with the subsequent SDP offer and set the UDP port number of the data channel media descriptions to zero.
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.3.3.2.3 MMTel session release
| Upon initiation or receipt of a BYE request matching an existing MMTel session with IMS data channel, the procedure defined in clause 9.3.2.2.3 applies.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.