Reference number | Requirement text | Comment |
---|---|---|
5.1.5-1 | The 5G system shall be able to support an end-to end secured link between the UEs (containers) and the Container Tracking Management System. | |
5.1.5-2 | The 5G System shall be able to support the request from the Container Tracking Management System to the UE (container) to provide its status and tracking information periodically with an update rate ranging from one status every [60 minutes] to one status every [24 hours] (i.e. 24 messages to 1 message per day). | |
5.1.5-3 | The 5G system shall be able to support terrestrial and non terrestrial (satellite) access networks. | |
5.1.5-4 | The 5G system shall be able to support a continuity of the service through network slicing including roaming. |
Reference number | Potential Requirement text | Comment |
---|---|---|
5.1.6-1 | The 5G system shall be able to support cellular IoT/mMTC type of communications by satellite. | |
5.1.6-2 | The UE shall be able to support a payload size up to 2500 bytes per message. |
Battery Life Expectancy (note 1) | Typical Message size | Maximum Message size | Typical Frequency (number of messages per day) | Typical Battery Capacity | Device density |
---|---|---|---|---|---|
12 years | 200 bytes | 2500 bytes | 24 | 21,6 Wh | 1,4 devices / m3 |
NOTE 1:
Battery life expectancy is to be assumed in all coverage conditions and is based on typical message size value and typical frequency
NOTE 2:
A large containership with a mix of 20 ft and 40 ft containers is assumed.
NOTE 3:
All the values in this table are example values and not strict requirements.
|
Reference number | Requirement text | Comment |
---|---|---|
5.2.5-1 | The 5G system shall be able to support an end-to end secured link between the UEs (wagons) and the wagon Tracking Management System. | |
5.2.5-2 | The 5G System shall be able to support the request from the wagon Tracking Management System to the UE (wagon) to provide its status and tracking information periodically with an update rate ranging from one status every [15 minutes] to one status every [24 hours] (i.e. 96 messages to 1 message per day). | |
5.2.5-3 | The 5G system shall be able to support terrestrial and non terrestrial (satellite) access networks. | |
5.2.5-4 | The 5G system shall be able to support a continuity of the service in roaming case. |
Battery Life Expectancy (note 1) | Typical Message size | Maximum Message size | Typical Frequency (number of messages per day) | Typical Battery Capacity | Device density |
---|---|---|---|---|---|
20 years | 200 bytes | 2500 bytes | 24 | 36 Wh | 0,3 devices / m2 |
NOTE 1:
Battery life expectancy is to be assumed in all coverage conditions and is based on typical message size value and typical frequency
NOTE 2:
All the values in this table are example values and not strict requirements.
|
Battery Life Expectancy (note 1) | Typical Message size | Maximum Message size | Typical Frequency (number of messages per day) | Typical Battery Capacity | Device density |
---|---|---|---|---|---|
7 years | 300 bytes | 300 bytes | 24 | 12 Wh | 4 devices/ m2 |
NOTE 1:
Battery life expectancy is to be assumed in all coverage conditions and is based on typical message size value and typical frequency
NOTE 2:
All the values in this table are example values and not strict requirements.
|
Scenario | Battery Life Expectancy (note 1) | Typical Message size | Maximum Message size | Typical Frequency (number of messages per day) | Typical Battery Capacity | Device density | |
---|---|---|---|---|---|---|---|
1 | Containers (note 2) | 12 years | 200 bytes | 2500 bytes | 24 | 21,6 Wh | 1,4 devices / m3 |
2 | Wagons | 20 years | 200 bytes | 2500 bytes | 24 | 36 Wh | 0,3 devices / m2 |
3 | Pallets | 7 years | 300 bytes | 300 bytes | 24 | 12 Wh | 4 devices/ m2 |
NOTE 1:
Battery life expectancy is to be assumed in all coverage conditions and is based on typical message size value and typical frequency
NOTE 2:
A large containership with a mix of 20 ft and 40 ft containers is assumed.
NOTE 3:
All the values in this table are targeted values and not strict requirements.
|