Tech-invite3GPPspecsSIPRFCs
Overview21222324252627282931323334353637384‑5x

Top   in Index   Prev   Next

TS 22.119
Maritime Communication Services over 3GPP System

Use "3GPP‑Page" to get the Word version, and "ETSI‑search" to get the PDF version
V16.2.0 (PDF)2020/09  … p.
Rapporteur:
Ms. Koo, Hyounhee

Content for  TS 22.119  Word version:  16.1.0

Here   Top
1  ScopeWord‑p. 5
The present document describes service requirements to enable maritime communication services to be supported over 3GPP system. Requirements for MCX Services applicable to general maritime usage are specified in 3GPP Technical Specifications dedicated to MCX Services.
Requirements in this specification are specific for maritime usage.
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]  TR 21.905   "Vocabulary for 3GPP Specifications".
Up
3  Definitions, symbols and abbreviations
3.1  Definitions
For the purposes of the present document, the terms and definitions given in TR 21.905 and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905.
3.2  Symbols
For the purposes of the present document, the following symbols apply:
3.3  Abbreviations
For the purposes of the present document, the abbreviations given in TR 21.905 and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905.
4  Overview
The maritime domain, one of the 5G vertical domains in 3GPP, is moving forward with the digitalisation and mobilisation of commercial as well as safety fields. Legacy 3GPP-based technologies and solutions can be beneficial to the digitalisation and mobilisation of the maritime domain though some of the legacy 3GPP enabling technologies and solutions may not be able to fully support the performances required by the maritime domain. The maritime radio environment was not originally considered by 3GPP when the technical specifications and solutions were standardised for LTE and 5G.
However, most of the legacy mobile services and IoT services based on capabilities of EPS and 5GS specified in 3GPP specifications are applicable to maritime usage for the support of mobile broadband services, and for the support of IoT services or machine-type communication services in a vessel at sea.
In addition, there are service scenarios and requirements specified in 3GPP specifications based on requirements of other related vertical domains (e.g. public safety domain, automotive domain, factory automation domain, and satellite industrial domain). Some requirements derived by service scenarios from these related vertical domains are applicable to the maritime domain. Thus, it is beneficial to use 3GPP enabling technologies developed to satisfy those requirements for the maritime domain in terms of the economy of scale.
For example, satellite access is one of the 3GPP radio access networks supported over the 5G system, so it is possible to provide seamless maritime mobile services by integrating multiple access technologies including satellite access depending on the service scenarios. In addition, 5G LAN-type access that can replace Ethernet-based access are applicable to indoor maritime mobile services inside a vessel.
MC Services specified in 3GPP specifications are applicable to commercial and maritime safety fields. Some similarities exist between the public safety domain and the maritime domain in terms of service scenarios that are essentially the same. For example, in some situations, mobile communication services are supported in spite of disconnected networks, i.e. off-network mode, or under isolated conditions.
However, the maritime domain also has specific situations that do not happen in other vertical domains or in the legacy ICT industrial domain. New 3GPP enabling technologies dedicated to the maritime domain can be used to address such specific situations based on requirements derived from maritime use cases. Other vertical domains may benefit from such new 3GPP enabling technologies that consider maritime domain scenarios and may need more robust technologies or solutions than those that currently exist for those vertical domains.
This technical specification provides the stage 1 requirements specific to maritime usage over 3GPP system for commercial as well as safety purposes. The stage 1 requirements derived from specific maritime usage but also related to MCX Services are specified in 3GPP technical specifications dedicated to MCX Services.
Up
5  Requirements of basic capabilitiesWord‑p. 6
5.1  Network connection and service continuity
5.1.1  Description
General 3GPP procedures of network connection and service continuity are applicable to maritime usage within 3GPP communication range. For example, a UE mapped to a vessel needs to perform the network reselection when a vessel arrives at a port where different 3GPP networks are available from a 3GPP network that a vessel was initially connected to but disconnected from when a vessel started a voyage away from the initial 3GPP communication range. Additional capabilities for the establishment of a 3GPP network connection and for the service continuity could improve user experiences on maritime communication services over 3GPP system in spite of some constraints from the maritime communication environment including the communication environment inside a vessel that is usually made of steel.
Up
5.1.2  Requirements
3GPP system shall provide a mechanism to establish a 3GPP network connection and support service continuity between direct network connection and indirect network connection for maritime usage under some constraints (e.g. any UE constraint on the uplink transmission capability or signal attenuation due to steel material of a vessel).
5.2  IdentificationWord‑p. 7
5.2.1  Description
A UE identity specified in 3GPP specifications is applicable to maritime usage. There are vessel identities for the identification of a vessel as a unique identity in maritime communication services. Mapping a UE identity with a vessel identity is needed to support identification procedures based on vessel identities in maritime domain when a vessel itself plays the role of a UE in a 3GPP system.
5.2.2  Requirements
3GPP system shall provide a mechanism to associate a UE identity with a vessel identity.
6  Requirements of multi-access and seamless mobility
6.1  Seamless mobility
6.1.1  Description
Network deployment scenarios are one of the different aspects to be taken into account for maritime communication from terrestrial communication in order to provide seamless mobile services within a vessel or at sea or on inland waterways. The usage of moving networks, isolated networks or satellite access networks may be more commonly applicable for maritime safety services as compared to general commercial services over 3GPP networks because fixed mobile network deployments are used for most terrestrial mobile services.
The communication range may depend on a number of factors such as the power level transmitted, the height of the antenna, the type of vessels, the particular service scenarios and propagation conditions. Thus, it may not be easy to provide a single value for the communication range between two vessels and a vessel that is applicable for all maritime service scenarios at sea.
Up
6.1.2  Requirements
The minimum communication range between vessels shall be equal to the maximum line-of-sight range between antennas mounted on two vessels at sea or on inland waterways.
7  Requirements of warning notification and emergency request
7.1  Notification for maritime safety
7.1.1  Description
Notifications for maritime safety can be transmitted by authorities to maritime mobile users at sea. Notifications can be used to inform vessels of the location of a vessel in danger. Considering maritime environment, a vessel that received notifications for maritime safety need to be able to send such received notifications to neighbouring vessels that are not in the coverage of 3GPP system.
7.1.2  RequirementsWord‑p. 8
3GPP system shall provide a mechanism of including the position, heading and speed of other UEs in a maritime notification transmitted only to a dedicated UE requesting maritime safety information.
3GPP system shall provide a mechanism of enabling all UEs dedicated to vessels that are in the coverage of 3GPP system to receive the distributed maritime notifications and identify which of these maritime notifications are targeted for the UE.
7.2  Emergency request for maritime safety
7.2.1  Description
Maritime accidents used to happen when crews of a vessel do not recognise that one of people on board is falling into the sea on a vessel. 3GPP system provides several mechanisms of enabling emergency request in case of maritime accidents to be transmitted to inform the authorities in charge about the occurrence of the emergency. In addition to legacy emergency request mechanisms, additional capabilities can make 3GPP system more powerful tools for maritime safety.
7.2.2  Requirements
The 3GPP system shall provide a mechanism of distributing the maritime emergency request received from a UE to all UEs on that vessel.
A UE dedicated to a vessel shall support the capability of sending maritime emergency requests including the vessel-dedicated UE's actual position (e.g. current position, heading and speed of the vessel and scheduled navigational routes.
The 3GPP system shall be able to transmit the maritime emergency request via the indirect network connection.
A  Status of legacy communication methods used for the navigationWord‑p. 9
Void
B  Status of legacy communication methods used by equipment inside a vesselWord‑p. 10
Void
$  Change historyWord‑p. 11

Up   Top