Emergency reporting via satellite store and forward operation

Abstract

A device which is capable of using services provided via a satellite-based non-terrestrial network of a mobile communication system acquires (S111), from the mobile communication system, an emergency service code which is to be used in an emergency mode. In case the device is in the emergency mode, an emergency report comprising at least identity and location of the device is generated (S113). At the time when the device is in a coverage area of a satellite of the non-terrestrial network, an emergency reporting request including the emergency report and the emergency service code is sent (S115) towards the satellite.

Description

[0001] EMERGENCY REPORTING VIA SATELLITE STORE AND FORWARD

[0002] OPERATION

[0003] TECHNICAL FIELD

[0004] At least some example embodiments relate to an emergency reporting service provided via a satellite-based non-terrestrial network of a mobile communication system, such as a 5G system (5GS), in a store-and-forward operation mode.

[0005] BACKGROUND

[0006] Fifth-generation (5G) telecommunication systems are expected to meet the world market demands of accessing and delivering services anywhere and anytime. The Non-Terrestrial Network (NTN) systems are able to satisfy the requests of anywhere and anytime connections by offering wide-area coverage and ensuring service availability, continuity, and scalability. NTN can be defined as "networks, or segments of networks, using an airborne or space-borne vehicle to embark a transmission equipment relay node or base station". "Satellite access" is direct connectivity between the UE and the satellite. The exponential growth of smart devices fuel the development of NTN systems as an effective solution to complement terrestrial networks in providing services over uncovered or under-served geographical areas. The uniqueness of NTNs is in their capability to offer wide-area coverage by providing connectivity over the regions that are expensive or difficult to cover with terrestrial networks (i.e., rural areas, vessels in oceans, airplanes). Therefore, the NTN represents a coverage extension for the terrestrial network in a market where the customer needs are increasing radically.

[0007] In the context of NTN, "a transparent payload" is radio frequency filtering, frequency conversion and amplification. Hence, the waveform signal repeated by the payload is un-changed. "A regenerative payload" is radio frequency filtering, frequency conversion and amplification as well as demodulation / decoding, switch and / or routing, coding / modulation. This is effectively equivalent to having all or part of base station functions (e.g. gNB functions) on board the satellite.

[0008] LIST OF ABBREVIATIONS

[0009] 3GPP Third Generation Partnership Project

[0010] 5G Fifth Generation

[0011] 5GS 5G System

[0012] AMF Access and Mobility Management Function

[0013] AS Application Server

[0014] AUSF Authentication Server Function

[0015] ESC Emergency Service Code gNB 5G NodeB

[0016] HN Home Network

[0017] HPLMN Home PLMN

[0018] ID Identifier loT Internet of Things

[0019] ISL Inter-Satellite Link

[0020] LEO Low Earth Orbit

[0021] MIoT Mobile loT

[0022] NGSO Non Geostationary Satellite Orbit

[0023] NTN Non-Terrestrial Network

[0024] PLMN Public Land Mobile Network

[0025] RID Routing ID

[0026] S&F Store and Forward

[0027] SAT Satellite

[0028] SMS Short Message Service

[0029] SMSC SMS Centre

[0030] SoR Steering and Roaming

[0031] UE User Equipment

[0032] UPU UE Parameter Update

[0033] LIST OF CITATIONS

[0034] 3GPP TR 22.865 version 1.0.0 SUMMARY

[0035] At least some example embodiments provide for an improved emergency reporting service provided via a satellite-based non-terrestrial network of a mobile communication system, such as a 5G system (5GS), in a store-and- forward operation mode.

[0036] According to at least some example embodiments, methods, apparatuses and non-transitory computer-readable storage media are provided as specified by the appended claims.

[0037] In the following, example embodiments will be described with reference to the accompanying drawings.

[0038] BRIEF DESCRIPTION OF THE DRAWINGS

[0039] Fig. 1 shows flowcharts illustrating processes of an emergency reporting service provided via a satellite-based non-terrestrial network of a mobile communication system according to at least some example embodiments.

[0040] Fig. 2 shows a signaling diagram illustrating an emergency reporting service according to at least some example embodiments.

[0041] Fig. 3 shows a schematic block diagram illustrating a configuration of control units in which at least some example embodiments are implementable.

[0042] DESCRIPTION OF THE EMBODIMENTS

[0043] At least some example embodiments relate to delay-tolerant store-and- forward communication services provided via a satellite-based nonterrestrial network of a mobile communication system, such as a 5G system (5GS) described for example in clause 4 of 3GPP TR 22.865: Store and Forward (S&F) operation is an operation mode of a 5G system with satellite-access, where the 5G system can provide some level of service (in storing and forwarding the data) when satellite connectivity is intermittently / temporarily unavailable, e.g. to provide communication service for UEs under satellite coverage without a simultaneous active feeder link connection to the ground segment. This is particularly relevant for delay-tolerant loT services via NGSO space segment.

[0044] In 3GPP context, a service that could be assimilated to an S&F service is SMS, for which there is no need to have an end-to-end connectivity between the end-points (e.g. an end-point can be a UE and the other an application server) but only between the end-points and the SMSC which acts as an intermediate node in charge of storing and relying.

[0045] At least some example embodiments provide for a solution to realize the use case "Store and forward - emergency report" of TR. 22.865 clause 5.16, based on S&F between a UE (also referred to, in the following, as a device, e.g. an loT device, which is capable of using services provided via a satellite-based non-terrestrial network of a mobile communication system, e.g. 5GS) and an Application Server (AS) in the mobile communication system via intermittent satellite connectivity, as will be described below.

[0046] Fig. 1 shows flowcharts illustrating processes of an emergency reporting service provided via a satellite-based non-terrestrial network of a mobile communication system according to at least some example embodiments.

[0047] Process 1 shown in Fig. 1 is implemented in / adopted by a device which is capable of using services provided via a satellite-based non-terrestrial network of a mobile communication system, e.g. 5GS. For example, the device is a UE, an loT device, etc. In step Sill, from the mobile communication system, an emergency service code which is to be used in an emergency mode is acquired. Then, process 1 advances to step SI 13.

[0048] In step SI 13, in case the device is in the emergency mode, an emergency report comprising at least identity and location of the device is generated. Then, process 1 advances to step SI 15.

[0049] In step S115, at the time when the device is in a coverage area of a satellite of the non-terrestrial network, an emergency reporting request including the emergency report and the emergency service code is sent towards the satellite which may operate in a store-and-forward operation mode. Then, process 1 ends.

[0050] According to at least some example embodiments, step Sill corresponds to step S202 of Fig. 2 which will be described later on.

[0051] Further, according to at least some example embodiments, step SI 13 corresponds to steps S209 to S211 of Fig. 2 which will be described later on.

[0052] Still further, according to at least some example embodiments, step SI 15 corresponds to step S212 of Fig. 2 which will be described later on.

[0053] According to at least some example embodiments, in step Sill, the emergency service code (which is a new Emergency Service Code (ESC)) is sent securely (i.e., in a secured way) by 5GS to a first loT device, for example using existing procedures such as Steering of Roaming (SoR) or UE Parameter Update (UPU).

[0054] According to at least some example embodiments, in step S113, the emergency report is generated by storing the emergency report, wherein the emergency report comprises zero or more information elements, encrypting one or more information elements, including in the emergency report the one or more encrypted information elements, and including in the emergency report a key identifier for decryption of the one or more encrypted information elements.

[0055] According to at least some example embodiments, the encrypting one or more information elements comprises performing the encryption using an asymmetric encryption algorithm with an HPLMN public key, the key identifier comprising an identifier of the HPLMN public key.

[0056] According to at least some example embodiments, a routing identifier is included in the emergency report.

[0057] For example, when the emergency mode is triggered at the first loT device, the device may be caused to generate an emergency report comprising the position of the device, an HPLMN public key ID, and Routing ID, and the report is encrypted by the device using the HPLMN public key.

[0058] Process 2 shown in Fig. 1 is implemented in / adopted by an apparatus associated with a mobile communication system (e.g. 5GS) which comprises a satellite-based non-terrestrial network.

[0059] In step S121, an emergency service code which is to be used in an emergency mode is provided to a device (e.g. UE, loT device, etc.) which is capable of using services provided via the satellite-based non-terrestrial network. Then, process 2 advances to step S123.

[0060] In step S123, the emergency service code is provided to a satellite of the non-terrestrial network. Then, process 2 ends.

[0061] According to at least some example embodiments, step S123 further comprises determining an expected location of the device, or a geographical area expected to comprise the location of the device, providing the emergency service code to a satellite of the non-terrestrial network based on determining that a coverage area of the satellite will overlap the expected location of the device, or will overlap the geographical area expected to comprise the location of the device.

[0062] According to at least some example embodiments, the expected location of the device or the geographical area expected to comprise the location of the device are determined based on at least one of: location information in at least one of one or more latest NAS Registration Request messages received from the device; or a coverage area of a satellite of the nonterrestrial network during each of at least one of one or more latest points of time, when a message from the device has been received by the satellite via the satellite-based non-terrestrial network.

[0063] For example, in S123, when the coverage area of a first satellite is approaching a geographical area of a plurality of loT devices comprising the device (first loT device), 5GS may send a list of ESCs to the first satellite which then is stored by the satellite.

[0064] According to at least some example embodiments, step S121 corresponds to step S202 of Fig. 2 which will be described later on.

[0065] Further, according to at least some example embodiments, step S123 corresponds to steps S204 and S208 of Fig. 2 which will be described later on.

[0066] According to at least some example embodiments, process 2 further comprises a step of receiving, from a satellite of the non-terrestrial network which may operate in a store-and-forward operation mode, an emergency report which comprises one or more encrypted information elements, and comprises a key identifier, and a step of decrypting at least one of the one or more encrypted information elements of the emergency report based on the key identifier. According to at least some example embodiments, the step of receiving corresponds to step S214 of Fig. 2 and the step of decrypting corresponds to step S216 of Fig. 2, which will be described later on.

[0067] According to at least some example embodiments, the step of decrypting further comprises determining a decryption key based on the key identifier, and decrypting the at least one of the one or more encrypted information elements with the decryption key.

[0068] According to at least some example embodiments, the key identifier comprises an identifier of an HPLMN public key, the determining a decryption key comprises determining an HPLMN private key corresponding to the HPLMN public key in a public-private key pair, and the decrypting the at least one of the one or more encrypted information elements with the decryption key comprises performing the decryption by using an asymmetric encryption algorithm with the HPLMN private key.

[0069] Process 3 shown in Fig. 1 is implemented in / adopted by an apparatus associated with a satellite of a satellite-based non-terrestrial network of a mobile communication system (e.g. 5GS). The satellite may operate in a store-and-forward operation mode.

[0070] In step S131, a list of emergency service codes which are to be used in an emergency mode, of a plurality of devices (e.g. UEs, loT devices, etc.) which are capable of using services provided via the satellite-based non-terrestrial network is acquired. Then, process 3 advances to step S133.

[0071] In step S133, an emergency reporting request including an emergency report and an emergency service code is received from a device (e.g. UE, loT device, etc.) capable of using the services provided via the satellite-based nonterrestrial network. Then, process 3 advances to step S135. In step S135, the device is authenticated as an authorized sender based on the emergency service code matching one of the emergency service codes of the list. Then, process 3 advances to step S137.

[0072] In step S137, at the time when a feeder link is available to the satellite providing connectivity to the mobile communication network, the emergency report of the authorized sender is forwarded to the mobile communication network. Then, process 3 ends.

[0073] Alternatively, in step S137, in case no feeder link is available to the satellite but the satellite is in a communication range with another satellite of the nonterrestrial network, the emergency report of the authorized sender is forwarded to the other satellite via an inter-satellite link. Then, process 3 ends.

[0074] For example, in steps S133 and S135, when the device is in the coverage area of the first satellite, the device may send the encrypted emergency report and the ESC to the first satellite. The device may be authenticated as an authorized sender based on the received ESC matching one of the ESCs stored by the first satellite, ignoring any retransmissions of the ESC.

[0075] Further, for example, in step S137, once a feeder link is available to the first satellite providing connectivity to 5GS, the first satellite may forward the authorized encrypted emergency report to 5GS for delivering to an Application Server in the HPLMN of the loT device. Alternatively, if no feeder link is available to the first satellite, but it is in communication range with a second satellite, the forwarding to 5GS may be via an inter-satellite link (ISL) to the second satellite.

[0076] According to at least some example embodiments, step S131 corresponds to steps S204 and S208 of Fig. 2 which will be described later on. Further, according to at least some example embodiments, step S133 corresponds to S212 of Fig. 2 which will be described later on.

[0077] Still further, according to at least some example embodiments, step S135 corresponds to S213 of Fig. 2 which will be described later on.

[0078] Still further, according to at least some example embodiments, step S137 corresponds to S214 of Fig. 2 which will be described later on.

[0079] According to at least some example embodiments, process 3 further comprises a step of storing the list of emergency service codes, and a step of deleting the list of emergency service codes based on determining that a coverage area of the satellite no longer overlaps a geographical area comprising the plurality of devices, as e.g. illustrated by step S206 of Fig. 2 which will be described later on. For example, when the coverage area of the first satellite no longer overlaps with the geographical area, the list of ESCs in the first satellite may be deleted.

[0080] According to at least some example embodiments, process 3 further comprises a step of storing the emergency report received from the device authenticated as authorized sender and starting a storage timer, as e.g. illustrated by step S213 of Fig. 2 to be described later on, and a step of resetting the storage timer at the time of forwarding the emergency report to the mobile communication network, as e.g. illustrated by step S215 of Fig. 2 to be described later on.

[0081] According to at least some example embodiments, the emergency report is forwarded to the mobile communication network to be delivered to an application server (AS) in an HPLMN of the device, as e.g. illustrated by step S217 of Fig. 2 to be described later on. According to at least some example embodiments, in case the device is not authenticated as authorized sender in step S135, the emergency reporting request is ignored.

[0082] According to at least some example embodiments, the emergency service code is for one-time usage, and in case the device is authenticated as authorized sender but retransmission of the emergency reporting request is detected in step S135, the emergency reporting request is ignored.

[0083] Now reference is made to Fig. 2 illustrating an emergency reporting service according to at least some example embodiments.

[0084] In step S201, a primary authentication is successfully performed between an loT device (a UE) and an AS. It is to be noted that this authentication procedure (e.g. authentication procedure with extended timer in all network elements or new procedure) is out of scope of this application.

[0085] In step S202, after a security context was established between AMF and the UE or between the UE and loTSAT, 5GS sends an Emergency Service Code (ESC) to the loT device in a secured way. If there is no end-to-end connection, the ESC may be also sent using existing procedures like SoR. or UPU procedures. Content is still sent in secured way and with integrity protected using KAUSF.

[0086] It is to be noted that the ESC may be of one time usage, and once it is used and authorized for an loT device by a satellite, then it has to be re-provisioned to the loT device.

[0087] In steps S203 and S204, at the time when satellite IoTSAT#l is moving towards the geographical area of the loT device, then 5GS may share a list of Emergency Service Codes (ESCs) of a plurality of loT devices (UEs) including the loT device shown in Fig. 2 with IoTSAT#l. It may happen that no emergency call or session is initiated by any of the loT devices during the time when IoTSAT#l is in coverage.

[0088] In steps S205 and S206, at the time when the satellite IoTSAT#l moves out of the geographical area of the plurality of loT devices, the list of ESCs may be deleted by IoTSAT#l.

[0089] In steps S207 and S208, at the time when a new satellite IoTSAT#2 is moving towards the geographical area of the loT device, then 5GS may share the list of the ESCs with IoTSAT#2.

[0090] In step S209, the loT device is in emergency mode e.g. due to the use case described in clause 5.16 of 3GPP TR 22.865.

[0091] In steps S210 and S211, the loT device / UE based positioning may be calculated and an emergency report may be generated. The loT device may use the Home network public key to encrypt the location and emergency report. Also the loT device may add the HN public key ID to the emergency report along with RID (Routing ID).

[0092] In steps S212 and S213, the loT device may send the emergency report along with the ESC received in S202 to the IoTSAT#2. The IoTSAT#2 may authorize the loT device using the list of ESCs which is configured by 5GS in the satellite IoTSAT#2. The IoTSAT#2 may also store the received emergency report and start a storage timer.

[0093] It is noted that, if there is no Feeder link and if IoTSAT#2 comes across another satellite, it may forward the emergency report to the other satellite via ISL stating that ESC (i.e., the loT device) is authorized and the emergency report needs to be forwarded to correct satellite gateway.

[0094] Once the Feeder link is available, the emergency report may be forwarded to 5GS via the correct satellite gateway (S214). Once the report is sent to the correct satellite gateway after the Feeder link was established, the storage timer may be reset (S215).

[0095] It is noted that even if the storage timer expires, the emergency report may not be deleted. Only the storage timer may be set once again. This is different from a normal report of store and forward case in which, during timer expiry, the date content can be deleted.

[0096] The 5GS may use the HN public key ID to identify an HN private key and decrypt the emergency report (S216). Finally, the 5GS may send the emergency report to the AS (S217).

[0097] According to at least some example embodiments, an emergency reporting service is triggered in a home PLMN of an loT device based on an emergency reporting request received from the loT device via 5GS, as described above.

[0098] According to at least some example embodiments, the emergency reporting request comprises identity and location of the loT device.

[0099] According to at least some example embodiments, the only connectivity available to the loT device is an intermittent connection to a low earth orbit (LEO) satellite, when the loT device is in the coverage of the satellite.

[0100] According to at least some example embodiments, the satellite is intermittently connected to 5GS via a link to a ground network, available when the loT device is outside the coverage of the satellite.

[0101] According to at least some example embodiments, the satellite may be intermittently connected to another LEO satellite via an inter-satellite link (ISL).

[0102] According to at least some example embodiments, encryption is provided to the identity and location of the loT device in the emergency reporting request, with a decryption key available only to the home PLMN of the loT device.

[0103] According to at least some example embodiments, the home PLMN of the loT device is able to determine the key needed for decryption.

[0104] According to at least some example embodiments, the satellite ignores any emergency reporting requests from unauthorized senders.

[0105] According to at least some example embodiments, the satellite ignores any retransmissions of an emergency reporting request from an authorized sender.

[0106] According to at least some example embodiments, expiry of an S&F storage timer in 5GS for the emergency request will not cause the request to be deleted.

[0107] Now reference is made to Fig. 3 illustrating a simplified block diagram of control units 310, 320, 330 that are suitable for use in practicing at least some example embodiments. According to an implementation example, process 1 is implemented by the control unit 310, process 2 is implemented by the control unit 320, and process 3 is implemented by the control unit 330.

[0108] The control units 310, 320, 330 comprise processing resources (e.g. processing circuitry) 311, 321, 331, memory resources (e.g. memory circuitry) 312, 322, 332 and interfaces (e.g. interface circuitry) 313, 323, 333, which are coupled via a wired or wireless connection 314, 324, 334.

[0109] According to an example implementation, the memory resources 312, 322, 332 are of any type suitable to the local technical environment and are implemented using any suitable data storage technology, such as semiconductor based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory and removable memory. The processing resources 311, 321, 331 are of any type suitable to the local technical environment, and include one or more of general purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs) and processors based on a multi core processor architecture, as non-limiting examples.

[0110] According to an implementation example, the memory resources 312, 322, 332 comprise one or more non-transitory computer-readable storage media which store one or more programs that when executed by the processing resources 311, 321, 331 cause the control units 310, 320, 330 to function as loT device, apparatus associated with 5GS and apparatus associated with a satellite as described above.

[0111] According to at least some example embodiments, one or more or each of the control units 310, 320, 330 is hardware that includes software, or simply software that is executable by at least one processor of one or more computers, e.g., a distributed computing system or a cloud computing system.

[0112] In an embodiment, an apparatus carrying out at least some of the embodiments described comprises at least one processor and at least one memory including instructions that, when executed with the at least one processor, cause the apparatus to carry out the functionalities according to any one of the embodiments described. According to an aspect, when the at least one processor executes the instructions, the instructions cause the apparatus to carry out the functionalities according to any one of the embodiments described. According to another embodiment, the apparatus carrying out at least some of the embodiments comprises the at least one processor and at least one memory including instructions, wherein the at least one processor and the instructions perform at least some of the functionalities according to any one of the embodiments described. Accordingly, the at least one processor, the memory, and the instructions form processing means for carrying out at least some of the embodiments described. According to yet another embodiment, the apparatus carrying out at least some of the embodiments comprises a circuitry including at least one processor and at least one memory instructions. When activated, the circuitry causes the apparatus to perform the at least some of the functionalities according to any one of the embodiments described.

[0113] The control units 310, 320, 330 may be communicatively coupled with each other via connections (not shown) (e.g., radio signaling according to one or more cellular communication protocols).

[0114] According to an example, control unit 310 is or is comprised in the device (e.g. loT device, UE) performing process 1 of Fig. 1. For example, the control unit 310 may be or may be comprised in a user equipment.

[0115] According to an example, control unit 320 is or is comprised in the apparatus performing process 2 of Fig. 1. For example, the control unit 320 may be or may be comprised in an apparatus associated with 5GS.

[0116] According to an example, control unit 330 is or is comprised in the apparatus performing process 3 of Fig. 1. For example, the control unit 330 may be or may be comprised in an apparatus associated with a satellite.

[0117] The definitions indicated in the present description are based on the current 3GPP standards. However, they are not limiting. Other definitions according to the same or a corresponding concept are applicable to some example embodiments, too.

[0118] One piece of information may be transmitted in one or plural messages from one entity to another entity. Each of these messages may comprise further (different) pieces of information. Names of network elements, protocols, and methods are based on current standards. In other versions or other technologies, the names of these network elements and / or protocols and / or methods may be different, as long as they provide a corresponding functionality.

[0119] If not otherwise stated or otherwise made clear from the context, the statement that two entities are different means that they perform different functions. It does not necessarily mean that they are based on different hardware. That is, each of the entities described in the present description may be based on a different hardware, or some or all of the entities may be based on the same hardware. It does not necessarily mean that they are based on different software. That is, each of the entities described in the present description may be based on different software, or some or all of the entities may be based on the same software. Each of the entities described in the present description may be embodied in the cloud.

[0120] Further, as used in this application, the term "circuitry" may refer to one or more or all of the following:

[0121] (a) hardware-only circuit implementations (such as implementations in only analog and / or digital circuitry) and

[0122] (b) combinations of hardware circuits and software, such as (as applicable):

[0123] (i) a combination of analog and / or digital hardware circuit(s) with software / firmware and

[0124] (ii) any portions of hardware processor(s) with software (including digital signal processor(s)), software, and memory(ies) that work together to cause an apparatus, such as a mobile phone or server, to perform various functions) and

[0125] (c) hardware circuit(s) and or processor(s), such as a microprocessor(s) or a portion of a microprocessor(s), that requires software (e.g., firmware) for operation, but the software may not be present when it is not needed for operation. This definition of circuitry applies to all uses of this term in this application, including in any claims. As a further example, as used in this application, the term circuitry also covers an implementation of merely a hardware circuit or processor (or multiple processors) or portion of a hardware circuit or processor and its (or their) accompanying software and / or firmware. The term circuitry also covers, for example and if applicable to the particular claim element, a baseband integrated circuit or processor integrated circuit for a mobile device or a similar integrated circuit in a server, a cellular network device, or other computing or network device.

[0126] The term "non-transitory", as used herein, is a limitation of the medium itself (i.e., tangible, not a signal) as opposed to a limitation on data storage persistency (e.g., RAM vs. ROM).

[0127] It is noted that, as used herein, "at least one of the following: " and "at least one of " and similar wording, where the list of two or more elements are joined by "and" or "or", mean at least any one of the elements, or at least any two or more of the elements, or at least all the elements.

[0128] According to an aspect, a device which is capable of using services provided via a satellite-based non-terrestrial network of a mobile communication system is provided. The device comprises means for acquiring, from the mobile communication system, an emergency service code which is to be used in an emergency mode, means for, in case the device is in the emergency mode, generating an emergency report comprising at least identity and location of the device, and means for, at the time when the device is in a coverage area of a satellite of the non-terrestrial network, sending an emergency reporting request including the emergency report and the emergency service code towards the satellite.

[0129] According to at least some example embodiments, the emergency service code is acquired via a secured way. According to at least some example embodiments, the means for generating the emergency report comprises means for storing the emergency report, wherein the emergency report comprises zero or more information elements, means for encrypting one or more information elements, means for including in the emergency report the one or more encrypted information elements, and means for including in the emergency report a key identifier for decryption of the one or more encrypted information elements.

[0130] According to at least some example embodiments, the means for encrypting one or more information elements comprises means for performing the encryption using an asymmetric encryption algorithm with a home public land mobile network, HPLMN, public key, and the key identifier comprises an identifier of the HPLMN public key.

[0131] According to at least some example embodiments, a routing identifier is included in the emergency report.

[0132] According to an aspect, an apparatus associated with a mobile communication system which comprises a satellite-based non-terrestrial network is provided. The apparatus comprises means for providing an emergency service code which is to be used in an emergency mode, to a device which is capable of using services provided via the satellite-based non-terrestrial network, and means for providing the emergency service code to a satellite of the nonterrestrial network.

[0133] According to at least some example embodiments, the means for providing the emergency service code to a satellite of the non-terrestrial network further comprises means for determining an expected location of the device, or a geographical area expected to comprise the location of the device, means for providing the emergency service code to a satellite of the non-terrestrial network based on determining that a coverage area of the satellite will overlap the expected location of the device, or will overlap the geographical area expected to comprise the location of the device.

[0134] According to at least some example embodiments, the expected location of the device or the geographical area expected to comprise the location of the device are determined based on at least one of: location information in at least one of one or more latest NAS Registration Request messages received from the device; or a coverage area of a satellite of the non-terrestrial network during each of at least one of one or more latest points of time, when a message from the device has been received by the satellite via the satellite-based nonterrestrial network.

[0135] According to at least some example embodiments, the apparatus further comprises means for receiving, from a satellite of the non-terrestrial network, an emergency report which comprises one or more encrypted information elements, and comprises a key identifier, and means for decrypting at least one of the one or more encrypted information elements of the emergency report based on the key identifier.

[0136] According to at least some example embodiments, the means for decrypting further comprises means for determining a decryption key based on the key identifier, and means for decrypting the at least one of the one or more encrypted information elements with the decryption key.

[0137] According to at least some example embodiments, the key identifier comprises an identifier of a home public land mobile network, HPLMN, public key; the means for determining a decryption key comprises means for determining a HPLMN private key corresponding to the HPLMN public key in a public-private key pair; and the means for decrypting the at least one of the one or more encrypted information elements with the decryption key comprises means for performing the decryption by using an asymmetric encryption algorithm with the HPLMN private key.

[0138] According to an aspect, an apparatus associated with a satellite of a satellitebased non-terrestrial network of a mobile communication system is provided. The apparatus comprises means for acquiring a list of emergency service codes which are to be used in an emergency mode, of a plurality of devices which are capable of using services provided via the satellite-based nonterrestrial network, means for receiving an emergency reporting request including an emergency report and an emergency service code from a device capable of using the services provided via the satellite-based non-terrestrial network, and means for authenticating the device as an authorized sender based on the emergency service code matching one of the emergency service codes of the list, and means for, at the time when a feeder link is available to the satellite providing connectivity to the mobile communication network, forwarding the emergency report of the authorized sender to the mobile communication network, or means for, in case no feeder link is available to the satellite but the satellite is in a communication range with another satellite of the non-terrestrial network, forwarding the emergency report of the authorized sender to the other satellite via an inter-satellite link.

[0139] According to at least some example embodiments, the apparatus further comprises means for storing the list of emergency service codes, and means for deleting the list of emergency service codes based on determining that a coverage area of the satellite no longer overlaps a geographical area comprising the plurality of devices.

[0140] According to at least some example embodiments, the apparatus further comprises means for storing the emergency report received from the device authenticated as authorized sender and starting a storage timer, and means for resetting the storage timer at the time of forwarding the emergency report to the mobile communication network. According to at least some example embodiments, in case the storage timer expires before the emergency report is forwarded to the mobile communication network, the storage timer is set once again and the emergency report is not deleted.

[0141] According to at least some example embodiments, the emergency report is forwarded to the mobile communication network to be delivered to an application server in a HPLMN of the device.

[0142] According to at least some example embodiments, in case the device is not authenticated as authorized sender, the emergency reporting request is ignored.

[0143] According to at least some example embodiments, in case the device is authenticated as authorized sender but retransmission of the emergency reporting request is detected, the emergency reporting request is ignored.

[0144] According to at least some example embodiments, the emergency service code is for one-time usage.

[0145] According to at least some example embodiments, the satellite operates in a store-and-forward operation mode.

[0146] According to some aspects, there is provided the subject matter of the independent claims. Some further aspects are defined in the dependent claims. The embodiments that do not fall under the scope of the claims are to be interpreted as examples useful for understanding the disclosure.

[0147] It is to be understood that the above description is illustrative and is not to be construed as limiting. Various modifications and applications may occur to those skilled in the art without departing from the true spirit and scope as defined by the appended claims.

Claims

CLAIMS1. A method used by a device which is capable of using services provided via a satellite-based non-terrestrial network of a mobile communication system, the method comprising: acquiring, from the mobile communication system, an emergency service code which is to be used in an emergency mode; in case the device is in the emergency mode, generating an emergency report comprising at least identity and location of the device; and at the time when the device is in a coverage area of a satellite of the non-terrestrial network, sending an emergency reporting request including the emergency report and the emergency service code towards the satellite.

2. The method of claim 1, wherein the emergency service code is acquired via a secured way.

3. The method of claim 1 or 2, wherein the generating the emergency report comprises: storing the emergency report, wherein the emergency report comprises zero or more information elements; encrypting one or more information elements; including in the emergency report the one or more encrypted information elements; and including in the emergency report a key identifier for decryption of the one or more encrypted information elements.

4. The method of claim 3, wherein: the encrypting one or more information elements comprises performing the encryption using an asymmetric encryption algorithm with a home public land mobile network, HPLMN, public key; and the key identifier comprises an identifier of the HPLMN public key.

5. The method of claim 3 or 4, wherein a routing identifier is included in the emergency report.

6. A method used by an apparatus associated with a mobile communication system which comprises a satellite-based non-terrestrial network, the method comprising: providing an emergency service code which is to be used in an emergency mode, to a device which is capable of using services provided via the satellite-based non-terrestrial network; and providing the emergency service code to a satellite of the nonterrestrial network.

7. The method of claim 6, wherein the providing the emergency service code to a satellite of the non-terrestrial network further comprises: determining an expected location of the device, or a geographical area expected to comprise the location of the device; providing the emergency service code to a satellite of the nonterrestrial network based on determining that a coverage area of the satellite will overlap the expected location of the device, or will overlap the geographical area expected to comprise the location of the device.

8. The method of claim 7, wherein the expected location of the device or the geographical area expected to comprise the location of the device are determined based on at least one of: location information in at least one of one or more latest NAS Registration Request messages received from the device; or a coverage area of a satellite of the non-terrestrial network during each of at least one of one or more latest points of time, when a message from the device has been received by the satellite via the satellite-based nonterrestrial network.

9. The method of any one of claims 6 to 8, further comprising:receiving, from a satellite of the non-terrestrial network, an emergency report which comprises one or more encrypted information elements, and comprises a key identifier; and decrypting at least one of the one or more encrypted information elements of the emergency report based on the key identifier.

10. The method of claim 9, wherein the decrypting further comprises: determining a decryption key based on the key identifier; and decrypting the at least one of the one or more encrypted information elements with the decryption key.

11. The method of claim 10, wherein : the key identifier comprises an identifier of a home public land mobile network, HPLMN, public key; the determining a decryption key comprises determining a HPLMN private key corresponding to the HPLMN public key in a public-private key pair; and the decrypting the at least one of the one or more encrypted information elements with the decryption key comprises performing the decryption by using an asymmetric encryption algorithm with the HPLMN private key.

12. A method used by an apparatus associated with a satellite of a satellitebased non-terrestrial network of a mobile communication system, the method comprising: acquiring a list of emergency service codes which are to be used in an emergency mode, of a plurality of devices which are capable of using services provided via the satellite-based non-terrestrial network; receiving an emergency reporting request including an emergency report and an emergency service code from a device capable of using the services provided via the satellite-based non-terrestrial network;authenticating the device as an authorized sender based on the emergency service code matching one of the emergency service codes of the list; and at the time when a feeder link is available to the satellite providing connectivity to the mobile communication network, forwarding the emergency report of the authorized sender to the mobile communication network, or in case no feeder link is available to the satellite but the satellite is in a communication range with another satellite of the non-terrestrial network, forwarding the emergency report of the authorized sender to the other satellite via an inter-satellite link.

13. The method of claim 12, further comprising: storing the list of emergency service codes; and deleting the list of emergency service codes based on determining that a coverage area of the satellite no longer overlaps a geographical area comprising the plurality of devices.

14. The method of claim 12 or 13, further comprising: storing the emergency report received from the device authenticated as authorized sender and starting a storage timer; and resetting the storage timer at the time of forwarding the emergency report to the mobile communication network.

15. The method of claim 14, wherein in case the storage timer expires before the emergency report is forwarded to the mobile communication network, the storage timer is set once again and the emergency report is not deleted.

16. The method of any one of claims 12 to 15, wherein the emergency report is forwarded to the mobile communication network to be delivered to an application server in a HPLMN of the device.

17. The method of any one of claims 12 to 16, wherein in case the device is not authenticated as authorized sender, the emergency reporting request is ignored.

18. The method of any one of claims 12 to 17, wherein in case the device is authenticated as authorized sender but retransmission of the emergency reporting request is detected, the emergency reporting request is ignored.

19. The method of any one of claims 1 to 18, wherein the emergency service code is for one-time usage.

20. The method of any one of claims 1 to 19, wherein the satellite operates in a store-and-forward operation mode.

21. A non-transitory computer-readable storage medium storing program code that, when executed by a computer of a device which is capable of using services provided via a satellite-based non-terrestrial network of a mobile communication system, causes the computer at least to: acquire, from the mobile communication system, an emergency service code which is to be used in an emergency mode; in case the device is in the emergency mode, generate an emergency report comprising at least identity and location of the device; and at the time when the device is in a coverage area of a satellite of the non-terrestrial network, send an emergency reporting request including the emergency report and the emergency service code towards the satellite.

22. A non-transitory computer-readable storage medium storing program code that, when executed by a computer of an apparatus associated with a mobile communication system which comprises a satellite-based nonterrestrial network, causes the computer at least to: provide an emergency service code which is to be used in an emergency mode, to a device which is capable of using services provided via the satellite-based non-terrestrial network; andprovide the emergency service code to a satellite of the non-terrestrial network.

23. A non-transitory computer-readable storage medium storing program code that, when executed by a computer of an apparatus associated with a satellite of a satellite-based non-terrestrial network of a mobile communication system, causes the computer at least to: acquire a list of emergency service codes which are to be used in an emergency mode, of a plurality of devices which are capable of using services provided via the satellite-based non-terrestrial network; receive an emergency reporting request including an emergency report and an emergency service code from a device capable of using the services provided via the satellite-based non-terrestrial network; authenticate the device as an authorized sender based on the emergency service code matching one of the emergency service codes of the list; and at the time when a feeder link is available to the satellite providing connectivity to the mobile communication network, forward the emergency report of the authorized sender to the mobile communication network, or in case no feeder link is available to the satellite but the satellite is in a communication range with another satellite of the non-terrestrial network, forward the emergency report of the authorized sender to the other satellite via an inter-satellite link.

24. A device which is capable of using services provided via a satellitebased non-terrestrial network of a mobile communication system, the device comprising at least one processor and at least one memory including computer program code, the at least one memory and the computer program code configured to, with the at least one processor, cause the device at least to: acquire, from the mobile communication system, an emergency service code which is to be used in an emergency mode;in case the device is in the emergency mode, generate an emergency report comprising at least identity and location of the device; and at the time when the device is in a coverage area of a satellite of the non-terrestrial network, send an emergency reporting request including the emergency report and the emergency service code towards the satellite.

25. The device of claim 24, wherein the emergency service code is acquired via a secured way.

26. The device of claim 24 or 25, wherein, to generate the emergency report, the at least one memory and the computer program code are configured to, with the at least one processor, cause the device further to: store the emergency report, wherein the emergency report comprises zero or more information elements; encrypt one or more information elements; include, in the emergency report, the one or more encrypted information elements; and include, in the emergency report, a key identifier for decryption of the one or more encrypted information elements.

27. The device of claim 26, wherein: to encrypt one or more information elements, the at least one memory and the computer program code are configured to, with the at least one processor, cause the device further to perform the encryption using an asymmetric encryption algorithm with a home public land mobile network, HPLMN, public key; and the key identifier comprises an identifier of the HPLMN public key.

28. The device of claim 26 or 27, wherein a routing identifier is included in the emergency report.

29. An apparatus associated with a mobile communication system which comprises a satellite-based non-terrestrial network, the apparatuscomprising at least one processor and at least one memory including computer program code, the at least one memory and the computer program code configured to, with the at least one processor, cause the apparatus at least to: provide an emergency service code which is to be used in an emergency mode, to a device which is capable of using services provided via the satellite-based non-terrestrial network; and provide the emergency service code to a satellite of the non-terrestrial network.

30. The apparatus of claim 29, wherein to provide the emergency service code to a satellite of the non-terrestrial network, the at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus further to: determine an expected location of the device, or a geographical area expected to comprise the location of the device; provide the emergency service code to a satellite of the non-terrestrial network based on determining that a coverage area of the satellite will overlap the expected location of the device, or will overlap the geographical area expected to comprise the location of the device.

31. The apparatus of claim 30, wherein the expected location of the device or the geographical area expected to comprise the location of the device are determined based on at least one of: location information in at least one of one or more latest NAS Registration Request messages received from the device; or a coverage area of a satellite of the non-terrestrial network during each of at least one of one or more latest points of time, when a message from the device has been received by the satellite via the satellite-based nonterrestrial network.

32. The apparatus of any one of claims 29 to 31, wherein the at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus further to: receive, from a satellite of the non-terrestrial network, an emergency report which comprises one or more encrypted information elements, and comprises a key identifier; and decrypt at least one of the one or more encrypted information elements of the emergency report based on the key identifier.

33. The apparatus of claim 32, wherein, to decrypt, the at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus further to: determine a decryption key based on the key identifier; and decrypt the at least one of the one or more encrypted information elements with the decryption key.

34. The apparatus of claim 33, wherein: the key identifier comprises an identifier of a home public land mobile network, HPLMN, public key; to determine a decryption key, the at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus further to determine an HPLMN private key corresponding to the HPLMN public key in a public-private key pair; and to decrypt the at least one of the one or more encrypted information elements with the decryption key, the at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus further to perform the decryption by using an asymmetric encryption algorithm with the HPLMN private key.

35. An apparatus associated with a satellite of a satellite-based nonterrestrial network of a mobile communication system, the apparatus comprising at least one processor and at least one memory including computer program code, the at least one memory and the computer programcode configured to, with the at least one processor, cause the apparatus at least to: acquire a list of emergency service codes which are to be used in an emergency mode, of a plurality of devices which are capable of using services provided via the satellite-based non-terrestrial network; receive an emergency reporting request including an emergency report and an emergency service code from a device capable of using the services provided via the satellite-based non-terrestrial network; authenticate the device as an authorized sender based on the emergency service code matching one of the emergency service codes of the list; and at the time when a feeder link is available to the satellite providing connectivity to the mobile communication network, forward the emergency report of the authorized sender to the mobile communication network, or in case no feeder link is available to the satellite but the satellite is in a communication range with another satellite of the non-terrestrial network, forward the emergency report of the authorized sender to the other satellite via an inter-satellite link.

36. The apparatus of claim 35, wherein the at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus further to: store the list of emergency service codes; and delete the list of emergency service codes based on determining that a coverage area of the satellite no longer overlaps a geographical area comprising the plurality of devices.

37. The apparatus of claim 35 or 36, wherein the at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus further to: store the emergency report received from the device authenticated as authorized sender and start a storage timer; andreset the storage timer at the time of forwarding the emergency report to the mobile communication network.

38. The apparatus of claim 37, wherein in case the storage timer expires before the emergency report is forwarded to the mobile communication network, the storage timer is set once again and the emergency report is not deleted.

39. The apparatus of any one of claims 35 to 38, wherein the emergency report is forwarded to the mobile communication network to be delivered to an application server in an HPLMN of the device.

40. The apparatus of any one of claims 35 to 39, wherein in case the device is not authenticated as authorized sender, the emergency reporting request is ignored.

41. The apparatus of any one of claims 35 to 40, wherein in case the device is authenticated as authorized sender but retransmission of the emergency reporting request is detected, the emergency reporting request is ignored.

Images