7 Requirements of warning notification and emergency request
22.1193GPPMaritime communication services over 3GPP systemRelease 17TS
7.1 Notification for maritime safety
7.1.1 Description
Notifications for maritime safety are transmitted by authorities to maritime mobile users at sea. Notifications can be used to inform vessels of the location of a vessel in danger. A vessel that receives notifications relating to maritime safety needs to be able to relay such notifications to neighbouring vessels that are not in coverage of the 3GPP system.
7.1.2 Requirements
The 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.
7.2 Emergency request for maritime safety
7.2.1 Description
Maritime accidents such as "man overboard" need to be handled quickly and effectively by the 3GPP system. 3GPP specifications provides several mechanisms for reporting emergencies to and requesting assistance from the appropriate authorities. In addition to legacy emergency request mechanisms, additional capabilities could make a 3GPP system more powerful for maritime safety.
7.2.2 Requirements
The 3GPP system shall provide a mechanism of distributing a 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).
Annex A (informative): Status of legacy communication methods used for the navigation
Void
Annex B (informative): Status of legacy communication methods used by equipment inside a vessel
Void
Annex C (informative): Change history
|
Change history |
|||||||||||
|
Date |
Meeting |
TDoc |
CR |
Rev |
Cat |
Subject/Comment |
New version |
||||
|
2018-08 |
SA1#83 |
S1-182608 |
TS Skeleton |
0.0.0 |
|||||||
|
2018-08 |
SA1#83 |
S1-182609 |
Scope |
0.1.0 |
|||||||
|
2018-08 |
SA1#83 |
S1-182610 |
Overview |
0.1.0 |
|||||||
|
2018-08 |
SA1#83 |
S1-182611 |
Requirements of basic capabilities |
0.1.0 |
|||||||
|
2018-08 |
SA1#83 |
S1-182726 |
Requirements of maritime notification and emergency request |
0.1.0 |
|||||||
|
2018-09 |
SA#81 |
SP-180762 |
Raised by MCC to v.1.0.0 for presentation to SA for information |
1.0.0 |
|||||||
|
2018-11 |
SA1#84 |
S1-183615 |
Requirement on the communication range between vessels |
1.1.0 |
|||||||
|
2018-12 |
SA#82 |
SP-181004 |
Raised by MCC to v.2.0.0 for presentation to SA for approval |
2.0.0 |
|||||||
|
2018-12 |
SA#82 |
SP-181004 |
Raised by MCC to v.16.0.0 following SA#82 approval |
16.0.0 |
|||||||
|
2019-09 |
SA#85 |
SP-190802 |
0002 |
2 |
F |
Clarification and editorial updates |
16.1.0 |
||||
|
2020-09 |
SA#89e |
SP-200785 |
0003 |
1 |
F |
R16 CR to TS22.119 for Requirement alignment for Relay |
16.2.0 |
||||
|
2020-09 |
SA#89e |
SP-200786 |
0004 |
1 |
F |
Clarification and disambiguation of text, provision of missing abbreviations and references |
16.2.0 |
||||
|
2022-03 |
SA#95e |
– |
– |
– |
– |
Updated to Rel-17 by MCC |
17.0.0 |
||||