Emergency context information for automated operation in disaster scenarios

Abstract

A user equipment of a wireless communication system according to an embodiment is provided. The user equipment is configured for generating an emergency context for the user equipment, such that the emergency context comprises first information and further information. Moreover, the user equipment is configured for transmitting the emergency context to another entity of the wireless communication system for making the emergency context in case of an emergency situation available at the other entity of the wireless communication system. The first information of the emergency context comprises at least one of: an information to distinguish an emergency SMS from a standard SMS, a location of the user equipment, a time when the location of the user equipment has been determined, an actual time of the user equipment, an actual date of the user equipment. The further information of the emergency context comprises at least one of: user-specific information comprising information on a user or a state of the user of the user equipment, device-specific information comprising information on the user equipment, environment-specific information comprising information on an environment in which the user equipment is located, privacy information comprising privacy settings that shall apply in case of an emergency, emergency transmission information comprising information for transmitting data in an emergency situation, an emergency message. The further information of the emergency context is different from the location of the user equipment, and is different from the time when the location of the user equipment has been determined, and is different from the actual time and the actual date of the user equipment.

Description

[0001] Emergency Context Information for Automated Operation in Disaster Scenarios

[0002] Description

[0003] The present invention relates to the field of wireless communication systems or networks, more specifically to user equipment, an entity and methods for a wireless communication system employing emergency context Information for automated operation in disaster scenarios.

[0004] BACKGROUND OF THE INVENTION

[0005] Fig. 1 is a schematic representation of an example of a terrestrial wireless network 100 including, as is shown in Fig. 1(a), the core network and one or more radio access networks RANi, RAN2, ... RANN (RAN = Radio Access Network). Fig. 1(b) is a schematic representation of an example of a radio access network RANnthat may include one or more base stations gNBi to gNBs (gNB = next generation Node B), each serving a specific area surrounding the base station schematically represented by respective cells IO61 to IO65. The base stations are provided to serve users within a cell. The one or more base stations may serve users in licensed and / or unlicensed bands. The term base station, BS, refers to a gNB in 5G networks, an eNB in UMTS / LTE / LTE-A / LTE-A Pro, or just a BS in other mobile communication standards. A user may be a stationary device or a mobile device. The wireless communication system may also be accessed by mobile or stationary loT (Internet of Things) devices which connect to a base station or to a user. The mobile devices or the loT devices may include physical devices, ground based vehicles, such as robots or cars, aerial vehicles, such as manned or unmanned aerial vehicles, UAVs, the latter also referred to as drones, buildings and other items or devices having embedded therein electronics, software, sensors, actuators, or the like as well as network connectivity that enables these devices to collect and exchange data across an existing network infrastructure. Fig. 1 (b) shows an exemplary view of five cells, however, the RANnmay include more or less such cells, and RANnmay also include only one base station. Fig. 1(b) shows two users UE1 and UE2, (UE = User Equipment) also referred to as user equipment, UE, that are in cell IO62 and that are served by base station gNB2. Another user UE3 is shown in cell IO64 which is served by base station gNB4. The arrows IO81, IO82 and IO83 schematically represent uplink / downlink connections for transmitting data from a user UE1, UE2 and UE3 to the base stations gNB2, gNB4 or for transmitting data from the base stations gNB2, gNB4 to the users

[0006] FH240807PEP-2025260532.DOCX UEi, UE2, UE3. This may be realized on licensed bands or on unlicensed bands. Further, Fig. 1(b) shows two loT devices 110i and HO2 in cell IO64, which may be stationary or mobile devices. The loT device 110i accesses the wireless communication system via the base station gNB4to receive and transmit data as schematically represented by arrow 112i . The loT device HO2 accesses the wireless communication system via the user UE3 as is schematically represented by arrow 1122. The respective base stations gNBi to gNBs may be connected to the core network 102, e.g. via the S1 interface, via respective backhaul links 114i to 114s, which are schematically represented in Fig. 1(b) by the arrows pointing to “core”. The core network 102 may be connected to one or more external networks. The external network may be the Internet or a private network, such as an intranet or any other type of campus networks, e.g. a private WiFi or 4G or 5G mobile communication system. Further, some or all of the respective base stations gNBi to gNBs may be connected, e.g. via the S1 or X2 interface or the XN interface in NR (New Radio), with each other via respective backhaul links 1161 to 1165, which are schematically represented in Fig. 1(b) by the arrows pointing to “gNBs”. A sidelink channel allows direct communication between UEs, also referred to as device-to-device, D2D (Device to Device), communication. The sidelink interface in 3GPP (3G Partnership Project) is named PC5 (Proximity-based Communication 5).

[0007] For data transmission a physical resource grid may be used. The physical resource grid may comprise a set of resource elements to which various physical channels and physical signals are mapped. For example, the physical channels may include the physical downlink, uplink and sidelink shared channels, PDSCH (Physical Downlink Shared CHannel), PLISCH (Physical Uplink Shared Channel), PSSCH (Physical Sidelink Shared Channel), carrying user specific data, also referred to as downlink, uplink and sidelink payload data, the physical broadcast channel, PBCH (Physical Broadcast Channel), carrying for example a master information block, MIB, and one or more of a system information block, SIB, one or more sidelink information blocks, SLIBs, if supported, the physical downlink, uplink and sidelink control channels, PDCCH (Physical Downlink Control Channel), PUCCH (Physical Uplink Control CHannel), PSCCH (Physical Sidelink Control Channel), the downlink control information, DCI, the uplink control information, UCI, and the sidelink control information, SCI, and physical sidelink feedback channels, PSFCH (Physical sidelink feedback channel), carrying PC5 feedback responses. Note, the sidelink interface may support a 2-stage SCI (Speech Call Items). This refers to a first control region comprising some parts of the SCI, and, optionally, a second control region, which comprises a second part of control information.

[0008] FH240807PEP-2025260532.DOCX For the uplink, the physical channels may further include the physical random-access channel, PRACH (Packet Random Access Channel) or RACH (Random Access Channel), used by UEs for accessing the network once a UE synchronized and obtained the MIB and SIB. The physical signals may comprise reference signals or symbols, RS, synchronization signals and the like. The resource grid may comprise a frame or radio frame having a certain duration in the time domain and having a given bandwidth in the frequency domain. The frame may have a certain number of subframes of a predefined length, e.g. 1ms. Each subframe may include one or more slots of 12 or 14 OFDM symbols (OFDM = Orthogonal Frequency-Division Multiplexing) depending on the cyclic prefix, CP, length. A frame may also include of a smaller number of OFDM symbols, e.g. when utilizing a shortened transmission time interval, sTTI (slot or subslot transmission time interval), or a mini- slot / non-slot-based frame structure comprising just a few OFDM symbols.

[0009] The wireless communication system may be any single-tone or multicarrier system using frequency-division multiplexing, like orthogonal frequency-division multiplexing, OFDM, or orthogonal frequency-division multiple access, OFDMA (Orthogonal frequency-division multiple access), or any other IFFT-based signal (IFFT = Inverse Fast Fourier Transformation) with or without CP, e.g. DFT-s-OFDM (DFT = discrete Fourier transform). Other waveforms, like non-orthogonal waveforms for multiple access, e.g. filter-bank multicarrier, FBMC, generalized frequency division multiplexing, GFDM, or universal filtered multi carrier, LIFMC, may be used. The wireless communication system may operate, e.g., in accordance with the LTE-Advanced pro standard, or the 5G or NR, New Radio, standard, or the NR-U, New Radio Unlicensed, standard.

[0010] The wireless network or communication system depicted in Fig. 1 may be a heterogeneous network having distinct overlaid networks, e.g., a network of macro cells with each macro cell including a macro base station, like base stations gNBi to gNBs, and a network of small cell base stations, not shown in Fig. 1 , like femto or pico base stations. In addition to the above described terrestrial wireless network also non-terrestrial wireless communication networks, NTN, exist including spaceborne transceivers, like satellites, and / or airborne transceivers, like unmanned aircraft systems. The non-terrestrial wireless communication network or system may operate in a similar way as the terrestrial system described above with reference to Fig. 1 , for example in accordance with the LTE-Advanced Pro standard or the 5G or NR, new radio, standard.

[0011] FH240807PEP-2025260532.DOCX In mobile communication networks, for example in a network like that described above with reference to Fig. 1 , like an LTE or 5G / NR network, there may be UEs that communicate directly with each other over one or more sidelink, SL, channels, e.g., using the PC5 / PC3 interface or WiFi direct. UEs that communicate directly with each other over the sidelink may include vehicles communicating directly with other vehicles, V2V communication, vehicles communicating with other entities of the wireless communication network, V2X communication, for example roadside units, RSUs, or roadside entities, like traffic lights, traffic signs, or pedestrians. An RSU may have a functionality of a BS or of a UE, depending on the specific network configuration. Other UEs may not be vehicular related UEs and may comprise any of the above-mentioned devices. Such devices may also communicate directly with each other, D2D communication, using the SL channels.

[0012] In a wireless communication network, like the one depicted in Fig. 1 , it may be desired to locate a UE with a certain accuracy, e.g., determine a position of the UE in a cell. Several positioning approaches are known, like satellite-based positioning approaches, e.g., autonomous and assisted global navigation satellite systems, A-GNSS, such as GPS, mobile radio cellular positioning approaches, e.g., observed time difference of arrival, OTDOA, and enhanced cell ID, E-CID, or combinations thereof.

[0013] Disasters such as earthquake, tsunami, flood, etc lead to widespread destruction of infrastructure, injuries, death and missing people. To mitigate the impact, there are standardized mechanisms to inform a user of impending disaster. For example, in LTE primary and secondary notification regarding ETWS are broadcasted on SIB11 and SIB10 respectively. The UEs are paged to ensure that the messages are received within short period of time, typically 4ms for primary notification. In NR, the warning systems are broadcasted using SIB6 (primary) and SIB7 (secondary). Likewise, CMAS (commercial mobile alert system) uses NR SIB8 RRC Message to send alert message to UE.

[0014] While warning system provide information alerting UE to take action, they fail to collect information to automatically assess the impact of disaster. Emergency calls, therefore, remain the technological solution to request help from emergency services - which primarily depends on the information provided by the caller. There has been enhancement to provide location of the user (either from UE or network) automatically when emergency services are triggered.

[0015] FH240807PEP-2025260532.DOCX It is noted that the information in the above section is only for enhancing the understanding of the background of the invention and, therefore, it may comprise information that does not form prior art that is already known to a person of ordinary skill in the art.

[0016] Starting from the above, there may be a need for improvements or enhancements for a wireless communication system or network and its components.

[0017] SUMMARY

[0018] A user equipment of a wireless communication system according to an embodiment is provided. The user equipment is configured for generating an emergency context for the user equipment, such that the emergency context comprises first information and further information. Moreover, the user equipment is configured for transmitting the emergency context to another entity of the wireless communication system for making the emergency context in case of an emergency situation available at the other entity of the wireless communication system. The first information of the emergency context comprises at least one of: an information to distinguish an emergency SMS from a standard SMS, a location of the user equipment, a time when the location of the user equipment has been determined, an actual time of the user equipment, an actual date of the user equipment. The further information of the emergency context comprises at least one of: user-specific information comprising information on a user or a state of the user of the user equipment, devicespecific information comprising information on the user equipment, environment-specific information comprising information on an environment in which the user equipment is located, privacy information comprising privacy settings that shall apply in case of an emergency, emergency transmission information comprising information for transmitting data in an emergency situation, an emergency message. The further information of the emergency context is different from the location of the user equipment, and is different from the time when the location of the user equipment has been determined, and is different from the actual time and the actual date of the user equipment.

[0019] Furthermore, a user equipment in a wireless communication system according to an embodiment is provided. The user equipment is configured to receive an emergency message from a PSAP or from a network entity, which may be sent in response to emergency detected by the network; and / or in response to information provided by a third party (e.g., trusted third party - like national organization monitoring emergency events -

[0020] FH240807PEP-2025260532.DOCX like meterological and / or seismological organisations); and / or in response to emergency call or sms initiated by the user equipment.

[0021] Moreover, an entity of a wireless communication system according to an embodiment is provided. The entity of the wireless communication system is configured for receiving an emergency context of a user equipment of the wireless communication system for having the emergency context in case of an emergency situation available at the entity of the wireless communication system, wherein said entity of the wireless communication system is different from said user equipment, wherein the emergency context of the user equipment comprises first information and further information. The first information of the emergency context comprises at least one of: an information to distinguish an emergency SMS from a standard SMS, a location of the user equipment, a time when the location of the user equipment has been determined, an actual time of the user equipment, an actual date of the user equipment. The further information of the emergency context comprises at least one of: user-specific information comprising information on a user or a state of the user of the user equipment, device-specific information comprising information on the user equipment, environment-specific information comprising information on an environment in which the user equipment is located, privacy information comprising privacy settings that shall apply in case of an emergency, emergency transmission information comprising information for transmitting data in an emergency situation, an emergency message. The further information of the emergency context is different from the location of the user equipment, and is different from the time when the location of the user equipment has been determined, and is different from the actual time and the actual date of the user equipment.

[0022] Furthermore, a method for a wireless communication system according to an embodiment is provided. Tthe method comprises:

[0023] Generating, by a user equipment of the wireless communication system, an emergency context for the user equipment, such that the emergency context comprises first information and further information. And:

[0024] T ransmitting, by the user equipment, the emergency context to another entity of the wireless communication system for making the emergency context in case of an emergency situation available at the other entity of the wireless communication system.

[0025] FH240807PEP-2025260532.DOCX The first information of the emergency context comprises at least one of: an information to distinguish an emergency SMS from a standard SMS, a location of the user equipment, a time when the location of the user equipment has been determined, an actual time of the user equipment, an actual date of the user equipment.

[0026] The further information of the emergency context comprises at least one of: user-specific information comprising information on a user or a state of the user of the user equipment, device-specific information comprising information on the user equipment, environment-specific information comprising information on an environment in which the user equipment is located, privacy information comprising privacy settings that shall apply in case of an emergency emergency transmission information comprising information for transmitting data in an emergency situation, an emergency message.

[0027] The further information of the emergency context is different from the location of the user equipment, and is different from the time when the location of the user equipment has been determined, and is different from the actual time and the actual date of the user equipment.

[0028] Moreover, a method for a wireless communication system according to an embodiment is provided. The method comprises receiving, by a user equipment, an emergency message from a PSAP or from a network entity, which may be sent in response to emergency detected by the network; and / or in response to information provided by a third party (e.g., trusted third party - like national organization monitoring emergency events - like meterological and / or seismological organisations); and / or in response to emergency call or sms initiated by the user equipment.

[0029] Moreover, another method for a wireless communication system accoprding to an embodiment is provided. The method comprises receiving, by an entity of the wireless communication system, an emergency context of a user equipment of the wireless

[0030] FH240807PEP-2025260532.DOCX communication system for having the emergency context in case of an emergency situation available at the entity of the wireless communication system, wherein said entity of the wireless communication system is different from said user equipment, wherein the emergency context of the user equipment comprises first information and further information.

[0031] The first information of the emergency context comprises at least one of: an information to distinguish an emergency SMS from a standard SMS, a location of the user equipment, a time when the location of the user equipment has been determined, an actual time of the user equipment, an actual date of the user equipment,

[0032] The further information of the emergency context comprises at least one of: user-specific information comprising information on a user or a state of the user of the user equipment, device-specific information comprising information on the user equipment, environment-specific information comprising information on an environment in which the user equipment is located, privacy information comprising privacy settings that shall apply in case of an emergency emergency transmission information comprising information for transmitting data in an emergency situation, an emergency message.

[0033] The further information of the emergency context is different from the location of the user equipment, and is different from the time when the location of the user equipment has been determined, and is different from the actual time and the actual date of the user equipment.

[0034] Furthermore, a computer program for implementing one of the above-described methods according to an embodiment is provided, when the method is being carried out by a computer program or signal processor.

[0035] FH240807PEP-2025260532.DOCX Some embodiments are based on the finding that emergency situations can arise when a user is in home network or in a roaming network or when connected via non-terrestrial network. Existing SMS mechanisms treat SMS to the home network, and even IMS initiated messaging (e.g. MMS may be sent over the home network). This is particularly problematic when the user’s home network (e.g. in Germany) is different from a roaming network, and the user has emergency in the roaming network (e.g. in Nepal). Then, if the SMS is sent to a PSAP in the home network instead of in the visted network, e.g., the roaming network, then the SMS is of no use. Furthermore, in case of emergency based messaging, it may be advantageous to indicate / request a local breakout (e.g., user data handled at the visited network instead of being routed back to the home network) of data pertaining to emergency messaging instead of home routed traffic (e.g. user data sent back to home network for purposes such as applying policies, charging and security).

[0036] Some embodiments aim at collecting the information needed to provide search and rescue services, forensic records at the UE side, proactively or in response to a message from the network entity, so that the information may be utilized for improving emergency response.

[0037] Moreover, some embodiments provide for mechanisms to collect and provide the information to the network, and also utilize information to reduce load on the system and / or provide search information for an extended period (for example, detecting emergency context, when the battery has died on a primary communication device - e.g. mobile phone).

[0038] Further particular embodiments are provided in the dependent claims.

[0039] BRIEF DESCRIPTION OF THE DRAWINGS

[0040] Fig. 1 illustrates a schematic representation of an example of a terrestrial wireless network.

[0041] Fig. 2 illustrates a handing emergency location in current 3GPP networks.

[0042] Fig. 3 illustrates an emergency context according to an embodiment, which is stored inside the internal memory of a user equipment.

[0043] Fig. 4 illustrates a creation of an emergency context according to an embodiment.

[0044] FH240807PEP-2025260532.DOCX Fig. 5 illustrates a creation and an update of an emergency context according to an embodiment.

[0045] Fig. 6 illustrates a flow chart depicting an embodiment, wherein the emergency contact of a user is informed that the user is safe.

[0046] Fig. 7 illustrates a transmissoun route via other UEs according to an embodiment, when base stations are no longer available in a disaster scenario.

[0047] Fig. 8 illustrates a transmission of a user-safe message according to an embodiment to other user equipments.

[0048] Fig. 9 illustrates an example of a computer system on which units or modules as well as the steps of the methods described in accordance with the inventive approach may execute.

[0049] DETAILED DESCRIPTION OF THE INVENTION

[0050] Embodiments of the present invention are now described in more detail with reference to the accompanying drawings, in which the same or similar elements have the same reference signs assigned.

[0051] A user equipment of a wireless communication system according to an embodiment is provided. The user equipment is configured for generating an emergency context for the user equipment, such that the emergency context comprises first information and further information. Moreover, the user equipment is configured for transmitting the emergency context to another entity of the wireless communication system for making the emergency context in case of an emergency situation available at the other entity of the wireless communication system. . The first information of the emergency context comprises at least one of: an information to distinguish an emergency SMS from a standard SMS, a location of the user equipment, a time when the location of the user equipment has been determined, an actual time of the user equipment, an actual date of the user equipment. The further information of the emergency context comprises at least one of: user-specific information comprising information on a user or a state of the user of the user equipment, devicespecific information comprising information on the user equipment, environment-specific information comprising information on an environment in which the user equipment is

[0052] FH240807PEP-2025260532.DOCX located, privacy information comprising privacy settings that shall apply in case of an emergency, emergency transmission information comprising information for transmitting data in an emergency situation, an emergency message. The further information of the emergency context is different from the location of the user equipment, and is different from the time when the location of the user equipment has been determined, and is different from the actual time and the actual date of the user equipment.

[0053] According to an embodiment, the first information of the emergency context comprises the information to distinguish an emergency SMS from a standard SMS.

[0054] In an embodiment, the information to distinguish an emergency SMS from a standard SMS comprises at least one of the following: indication of an emergency cause while setting up RRC connection or while setting up SIP connection or while resuming RRC connection from an RRCJNACTIVE mode, an indication of an emergency number or string, e.g., in a TP-DA field, an indication of a local network node, an indication of an emergency SIP URL, an indication of a type of number (TON), wherein an unknown number could trigger emergency handling, an indication of a type of emergency and / or a type of emergency service requested, e.g., fire, ambulance, police.

[0055] According to an embodiment, the information to distinguish an emergency SMS from a standard SMS may, e.g., be used by a network entity for at least one of the following: prioritizing a transmission of the emergency SMS or emergency message, enabling the message to be transmitted even without authorization, e.g., without USIM, eSIM, initiating a location service and / or sensing service and / or tracking service for the user equipment, e.g., trigger another network entity to initiate location service procedures, initiate a callback service, selecting a local PSAP (e.g., a visited network) over a PSAP in a home network, (e.g., home routed) in case of a roaming scenario,

[0056] FH240807PEP-2025260532.DOCX selecting a local PSAP corresponding to the location of the user equipment and / or routing the SMS or IMS message towards the local PSP.

[0057] In an embodiment, the user equipment may, e.g., be configured to receive an indication that the network does not support emergency SMS, or may, e.g., be configured to detect during initiating an emergency SMS that emergency SMS is not supported locally for the intended service.

[0058] According to an embodiment, if the user equipment receives an indication that the network does not support emergency SMS, or detects during initiating an emergency SMS that emergency SMS is not supported locally for the intended service, the user equipment may, e.g., be configured to conduct one or more of the following: indicate to one or more higher layers that the emergency SMS is not supported or is not supported for particular service (e.g., police only) or group of user equipments (e.g., for roaming user equipments, for home routed traffic), attempt to connect to a second PLMN that allows to transmit emergency SMS, indicate alternate means (e.g., voice call), an indication and / or warning that emergency SMS is sent out as a normal SMS (which may I may not be delivered, e.g., indicate the user for alternate means if no response is received).

[0059] In an embodiment, if the user equipment is in a roaming scenario and / or is connected to an NTN, the user equipment may, e.g., be configured to perform and / or o request a differentiated handling (e.g., indication of local breakout) of an emergency message over a normal data transmission (e.g., which may be in home routed traffic).

[0060] According to an embodiment, the user equipment may, e.g., be configured to generate an emergency message, when the user equipment detects an emergency, which does not support emergency calling and / or when a calling quality is degraded (e.g., due to power restrictions in an NTN user equipment).

[0061] According to an embodiment, if the user equipment has a battery power limitation for an emergency call (for example, if a remaining battery life is less than a certain value, such as

[0062] FH240807PEP-2025260532.DOCX 5 minutes or the remaining battery power is below a certain threshold), the user equipment may, e.g., be configured to send an emergency message instead of or in addition to initiating a voice call.

[0063] In an embodiment, when the user equipment receives an emergency SMS or emergency IMS or emergency message from one or more higher layers (e.g., from an application layer) and / or an indication to transmit an emergency SMS / message, the user equipment may, e.g., be configured to indicate to the network to request prioritized access by indicating emergency cause while requesting RRC_CONNECTION.

[0064] According to an embodiment, when the user equipment is in a visited network and / or connected via NTN, the user equipment may, e.g., be configured to generate SMSC address of a local emergency service via SMSC in a visited network and / or may, e.g., be configured to send an SMS over NAS and / or may, e.g., be configured to indicate a local breakout of emergency data when using IMS to send emergency message.

[0065] In an embodiment, the user equipment may, e.g., be configured to receive from a network entity a temporary mapping (e.g., communicated via SI messages or RRC messages or OMA client provisioning or OMA device management or SMS provisioning / update etc) of an emergency service access number for a message and / or for a call for emergency arising from a specific disaster. The user equipment may, e.g., be configured to receive from the network an indication that indicates a new mapping of an emergency service for this category of disaster (e.g., XXX for earthquake / flood instead of or in addition to the usual emergency numbers (e.g., 110, 111 , 112, 911)). The new mapping may be time-limited and / or area-limited and / or is applicable only in visited network.

[0066] Moreover, a user equipment in a wireless communication system according to an embodiment is provided.

[0067] The user equipment is configured to receive an emergency message from a PSAP or from a network entity, which may be sent in response to emergency detected by the network; and / or in response to information provided by a third party (e.g., trusted third party - like national organization monitoring emergency events - like meterological

[0068] FH240807PEP-2025260532.DOCX and / or seismological organisations; for example, the information may, e.g., comprise information on a missile and / or drone attack); and / or in response to emergency call or sms initiated by the user equipment.

[0069] According to an embodiment, the user equipment may, e.g., be configured to initiate an RRC_CONNECTION indicating an emergency cause while requesting the RRC_CONNECTION in response to a paging and / or a network indication and / or a higher layer indication for receiving emergency message (e.g., SMS / IMS or otherwise).

[0070] In an embodiment, the user equipment may, e.g., be configured to generate and transmit an emergency context to another entity of the wireless communication system for making the emergency context in case of an emergency situation available at the other entity of the wireless communication system.

[0071] According to an embodiment, the user equipment may, e.g., be configured to generate the emergency context, such that the emergency context comprises a timestamp, which indicates when the emergency context was last created or modified. And / or, the user equipment may, e.g., be configured to generate the emergency context, such that the emergency context comprises a timestamp, which indicates when at least one element of the emergency context was last created or modified.

[0072] In an embodiment, if a RAT (radio access technology, e.g. LTE, NR, 6G-Radio) and / or a frequency where the user equipment is currently connected on does not allow determining a location of the user equipment or does not allow determining a location of the user equipment for an emergency use case, the UE may, e.g., be configured to send the emergency message it has generated, and to await a network response, for example, in which the network redirects the user equipment to a different RAT and / or a different frequency to perform measurements and / or to transmit reference signals or to retransmit the emergency message, and / or perform a cell-reselection and to transmit and emergency message using the new RAT / frequency.

[0073] FH240807PEP-2025260532.DOCX According to an embodiment, whether or not transmission and / or reception of an emergency message and / or an emergency location is supported by the network may, e.g., be indicated to the user equipment via system information or through unicast signalling.

[0074] In an embodiment, the user equipment may, e.g., be configured to generate the emergency context, such that the user-specific information of the further information of the emergency context comprises a status indication which indicates that the user of the user equipment is safe, or comprises a status indication which indicates that the user needs rescue, or comprises a status indication which indicates that the user is injured.

[0075] According to an embodiment, the user equipment may, e.g., be configured to generate the emergency context, such that the emergency context comprises a timestamp indicating a time when the status indication has been created.

[0076] In an embodiment, the user equipment may, e.g., be configured to generate the emergency context, such that the emergency context comprises information on a source of a time information comprised by the emergency context and / or on a reliability of the time information comprised by the emergency context, for example, by indicating that the time information has been obtained using an NTP time from an NTP server, or using a GNSS, or using an internal user equipment time and date.

[0077] According to an embodiment, the user equipment may, e.g., be configured to transmit the emergency context by transmitting a first portion of the emergency context in a first message and by transmitting one or more further portions of the emergency context in one or more further messages.

[0078] In an embodiment, the user equipment may, e.g., be configured to transmit the emergency context within a single message.

[0079] According to an embodiment, the emergency situation is an emergency situation at the user equipment.

[0080] In an embodiment, the user equipment may, e.g., be configured to generate the emergency context, such that the emergency context comprises information on two or more locations of the user equipment at two or more different points-in-time.

[0081] FH240807PEP-2025260532.DOCX According to an embodiment, the user equipment may, e.g., be configured to generate the emergency context, such that the emergency context comprises time information for each location of the two or more locations of the user equipment, which indicates for said location at which point-in-time the user equipment has been located at said location.

[0082] In an embodiment, the user equipment may, e.g., be configured to generate the emergency context, such that the first information of the emergency context comprises the location of the user equipment. The user equipment may, e.g., be configured to determine its own location, for example, using self-location, e.g., using GNSS, or assisted GNSS or DL-TDOA, DL-AoD, multi-RTT, or sidelink positioning or using radar-like sensing.

[0083] According to an embodiment, the user equipment may, e.g., be configured to generate the emergency context, such that the first information of the emergency context comprises the location of the user equipment. The user equipment may, e.g., be configured to request a network entity of the wireless communication system to provide the location of the user equipment to the user equipment, for example, by initiating a MO-LR.

[0084] In an embodiment, the user equipment may, e.g., be configured to generate the emergency context, such that the further information of the emergency context comprises privacy information for the emergency context or for at least one element of the emergency context.

[0085] According to an embodiment, the user equipment may, e.g., be configured to generate the emergency context, such that the privacy information comprises an indication which indicates if the network is allowed to retrieve a particular element of the emergency context. And / or the user equipment may, e.g., be configured to generate the emergency context, such that the privacy information comprises an indication which indicates if the network is allowed to retrieve a particular portion of the emergency context. And / or the user equipment may, e.g., be configured to generate the emergency context, such that the privacy information comprises an indication which indicates if the network is allowed to retrieve the emergency context in its entirety.

[0086] In an embodiment, the user equipment may, e.g., be configured to generate the emergency context, such that the privacy information comprises an indication indicating for each PLMN of different PLMNs, which of the elements of the emergency context the PLMN is allowed to retrieve (e.g., different PLMNs may, e.g., be a home PLMN, a visited PLMN, an equivalent PLMN).

[0087] FH240807PEP-2025260532.DOCX According to an embodiment, the user equipment may, e.g., be configured to generate the emergency context, such that the privacy information comprises an indication that indicates that the user of the user equipment has to indicate its approval to a transmission of the emergency context to a network entity, or the user equipment may, e.g., be configured to generate the emergency context, such that the privacy information comprises an indication that indicates that a transmission of the emergency context to a network entity is allowed without that the user has to indicate its approval to the transmission.

[0088] In an embodiment, the user equipment may, e.g., be configured to generate the emergency context, such that the privacy information comprises an indication that indicates that a network entity may request a transmission of the emergency context without an indication of an approval for the transmission by the user of the user equipment.

[0089] In an embodiment, the user equipment may, e.g., be configured to receive a message indicating an override (for example, a regulatory override) regarding privacy. The user equipment may, e.g., be configured to transmit, in response to receiving the message indicating the override regarding privacy, the emergency context or a portion thereof irrespective of the privacy information.

[0090] According to an embodiment, the user equipment may, e.g., be configured to autonomously initiate an emergency call on detecting an emergency situation. The user equipment may, e.g., be configured to automatically transfer its location when the user or the user equipment autonomously has initiated the emergency call.

[0091] In an embodiment, the user equipment may, e.g., be configured to transmit an emergency message to one or more authorities (e.g., to a local emergency response center).

[0092] According to an embodiment, the emergency message may, e.g., comprise a text message and / or multimedia content.

[0093] According to an embodiment, the emergency message may, e.g., comprise the emergency context.

[0094] In embodiments, an emergency message, e.g., an emergency message sent by the user to the authority handling an emergency scenario (e.g. local emergency response center,

[0095] FH240807PEP-2025260532.DOCX PSAP or any other entity receiving the emergency message), may, e.g., comprise a text message or any multimedia message. The message may be associated with the identifier of the UE or an identifier of the UE emergency context or both. The message may be a selection of a pre-set message available for the user to choose or it may be a free-text message that the user provides.

[0096] The emergency message may be provided by the user in addition to or instead of the emergency call.

[0097] According to an embodiment, the user equipment may, e.g., be configured to obtain an indication on an emergency from a higher layer of a protocol stack of the user equipment.

[0098] In an embodiment, the user equipment may, e.g., be configured to transmit the emergency context or a portion of the emergency context or an element of the emergency context to another entity of the wireless communication system together with an identifier being associated with the emergency context.

[0099] According to an embodiment, the user equipment may, e.g., be configured to transmit a first message comprising a first portion of the emergency context to said other entity of the wireless communication system. Moreover, the user equipment may, e.g., be configured to transmit a second message comprising a second portion of the emergency context to said other entity of the wireless communication system together with the identifier being associated with the emergency context. In an embodiment, the identifier may, e.g., be created by the user equipment and may, e.g., then be also transmitted together with the first message. In another embodiment, the identifier may, e.g., be created by the other (e.g., network) entity in response to receiving the first message, may, e.g., then be transmitted to the user equipment, and the user equipment then may, e.g., transmit the second message together with the identifier.

[0100] In an embodiment, the user equipment may, e.g., be configured to transmit a first message comprising a first version of the emergency context to said other entity of the wireless communication system. Moreover, the user equipment may, e.g., be configured to transmit a second message comprising a second, updated version of the emergency context to said other entity of the wireless communication system together with the identifier being associated with the emergency context. In an embodiment, the identifier may, e.g., be created by the user equipment and may, e.g., then be also transmitted together with the

[0101] FH240807PEP-2025260532.DOCX first message. In another embodiment, the identifier may, e.g., be created by the other (e.g., network) entity in response to receiving the first message, may, e.g., then be transmitted to the user equipment, and the user equipment then may, e.g., transmit the second message together with the identifier.

[0102] According to an embodiment, the user equipment may, e.g., be configured to receive the identifier from a network entity of the wireless communication system.

[0103] In an embodiment, the user equipment may, e.g., be configured to generate itself the identifier which is associated with the emergency context.

[0104] In an embodiment, the user equipment may, e.g., be configured to generate the emergency context, such that the user-specific information of the further information of the emergency context comprises information on a health of the user of the user equipment.

[0105] According to an embodiment, the user equipment may, e.g., be configured to generate the emergency context, such that the user-specific information of the further information of the emergency context comprises medical information, comprising medical related information derived from information entered and / or stored by the user in the user equipment (e.g. allergies, medical conditions, additional medical information, reactions, medications, blood type etc).

[0106] In an embodiment, the user equipment may, e.g., be configured to generate the emergency context, such that the user-specific information of the further information of the emergency context comprises medical information, comprising medical related information derived from sensors in the user equipment and / or peripheral devices (e.g., smartwatch, etc.) associated to the user equipment.

[0107] In an embodiment, the user equipment may, e.g., be configured to generate the emergency context, such that the user-specific information of the further information of the emergency context comprises the indication indicating whether the user is willing to support a rescue and support operation in case of disaster scenario.

[0108] According to an embodiment, the user equipment may, e.g., be configured to receive information from the user entered via an interface of the user equipment, comprising an indication indicating whether the user is willing to be a blood-donor (e.g., in case of disaster

[0109] FH240807PEP-2025260532.DOCX scenario), and / or wherein the user equipment may, e.g., be configured to receive the indication from medical records of the user that the user is willing to be a blood-donor. The user equipment may, e.g., be configured to generate the emergency context, such that the user-specific information of the further information of the emergency context comprises the indication indicating whether the user is willing to be a blood-donor in case of disaster scenario.

[0110] In an embodiment, the user equipment may, e.g., be configured to generate the emergency context, such that the user-specific information of the further information of the emergency context comprises a blood group type of the user.

[0111] According to an embodiment, the interface of the user equipment may, e.g., be configured to receive information from the user in a disaster scenario indicating the user is safe, and indicating that the user is willing to be a blood donor.

[0112] In an embodiment, the interface of the user equipment may, e.g., be configured to receive information from the user overriding or pausing or resuming his willingness to support a rescue and support operation and / or to be a blood donor (e.g., because he just has contributed blood).

[0113] According to an embodiment, the user equipment may, e.g., be configured to obtain the information on the health of the user from one or more devices, for example, smartwatches, blood sugar monitors, heartbeat monitors, connected to the user equipment, for example using interfaces such as bluetooth or using sidelink data transmission.

[0114] In an embodiment, the user equipment may, e.g., be configured to obtain the information on the health of the user using sensing (for example, radar like sensing), or by conducting signal processing on transmitted data and signals for communication (e.g., by conducting integrated sensing and communication).

[0115] According to an embodiment, the user equipment may, e.g., be configured to initiate an emergency call and / or to transmit the emergency context depending on the information of the health of the user.

[0116] In an embodiment, the user equipment may, e.g., be configured to transmit the information on the health of the user within the emergency context depending on privacy information.

[0117] FH240807PEP-2025260532.DOCX Or, the emergency context comprises privacy information which indicates if access for another entity of the wireless communication system on the information on the health of the user within the emergency context is allowed.

[0118] According to an embodiment, the user equipment may, e.g., be configured to generate the emergency context, such that the user-specific information of the further information of the emergency context comprises personal identification information, comprising identification information stored by the user in the UE (e.g., a passport number, an identifier associated with insurance, social security, healthcare, etc.).

[0119] In an embodiment, the user equipment may, e.g., be configured to generate the emergency context, such that the emergency context comprises information relating to one or more other users being different from the user of the user equipment.

[0120] According to an embodiment, the user equipment may, e.g., be configured to receive the information on the one or more other users from one or more other entities of the wireless communication system.

[0121] In an embodiment, the user equipment may, e.g., be configured to generate the emergency context, such that the emergency context comprises information on a motion status of the user equipment, for example, if a user equipment is moving or if a user equipment is not moving.

[0122] According to an embodiment, the user equipment may, e.g., be configured to generate the emergency context, such that emergency context comprises information on a motion status of the user equipment for two or more different points-in-time.

[0123] In an embodiment, the user equipment may, e.g., be configured to generate the emergency context, such that the emergency context comprises sensor data from one or more sensors, wherein the sensor data depends on the user equipment and / or depends on the environment where the user equipment is located and / or depends on a state of the user of the user equipment.

[0124] According to an embodiment, the user equipment may, e.g., be configured to generate the emergency context, such that the sensor data comprises data on an air pressure, and / or

[0125] FH240807PEP-2025260532.DOCX data on a sound intensity, and / or data on a movement profile, and / or data on accelerometer readings, and / or data on gyroscope readings, and / or data on barometer readings.

[0126] In an embodiment, the user equipment may, e.g., be configured to process at least one sensor reading to derive a current status of the user (e.g. falling, trapped, lying down, moving, etc.). The user equipment may, e.g., be configured to generate the emergency context, such that the emergency context comprises the current status of the user.

[0127] According to an embodiment, the user equipment may, e.g., be configured to generate the emergency context, such that the emergency context comprises an indication on a last time when the user has used the user equipment.

[0128] In an embodiment, the user equipment may, e.g., be configured to generate the emergency context, such that the emergency context comprises an indication which indicates that the user is safe, or comprises an indication which indicates that the user needs rescue, or comprises an indication which indicates that the user is injured.

[0129] According to an embodiment, the user equipment comprises an interface which may, e.g., be configured to receive a user input from the user to allow the user to indicate that the user is safe. The user equipment may, e.g., be configured to set the indication of the emergency context that the user is safe depending on the user input.

[0130] In an embodiment, the user equipment may, e.g., be configured to generate the emergency context, such that the emergency context comprises an indication indicating that the user has abandoned the user equipment.

[0131] According to an embodiment, the user equipment may, e.g., be configured to make a determination that the user has abandoned the user equipment by analyzing an RSRP and / or an RTT between a peripheral device (e.g., a smartwatch) and the user equipment. The user equipment may, e.g., be configured to set the indication of the emergency context that the user has abandoned the user equipment depending on the determination.

[0132] In an embodiment, the user equipment may, e.g., be configured to transmit information one or more elements of the emergency context to a user contact in an emergency situation.

[0133] FH240807PEP-2025260532.DOCX According to an embodiment, the user equipment may, e.g., be configured to transmit information that the user is safe or that the user is injured or that the user needs rescue as the information one or more elements of the emergency context to the user contact.

[0134] In an embodiment, the user equipment may, e.g., be configured to inform the user of the user equipment that the information that the user is safe or that the user is injured or that the user needs rescue has been transmitted to the user contact (e.g., to avoid the need that the user himself contacts the user contact, so that the transmission load on the network, e.g., due to phone calls, is reduced in case of an emergency situation).

[0135] According to an embodiment, the information on the one or more elements of the emergency context that is transmitted to the user contact in the emergency situation depends on a privacy profile.

[0136] In an embodiment, the user equipment may, e.g., be configured to generate the emergency context, such that the emergency context comprises information on the user contact.

[0137] According to an embodiment, the user equipment may, e.g., be configured to transmit information on a battery power of the user equipment to another entity of the wireless communication system in an emergency situation.

[0138] In an embodiment, the user equipment may, e.g., be configured to generate the emergency context, such that the emergency context comprises information on the battery power of the user equipment.

[0139] According to an embodiment, the user equipment is configured to generate and / or send an emergency message, if a battery power gets below a certain limit. The certain limit may, e.g., be a certain percentage of a battery power reference, for example a maximum battery power. Or, the certain limit may, e.g., be a certain time (e.g., a number of minutes) of remaining battery power.

[0140] For example, this may happen when an emergency call is made but the battery is too low. Then, the emergency message may, e.g., be generated and sent as a fallback.

[0141] In an embodiment, the user equipment may, e.g., be configured to generate and / or send the emergency context, if the user equipment detects an emergency. Such an emergency

[0142] FH240807PEP-2025260532.DOCX may, e.g., be a car crash and / or an unconcious user, etc. Likewise, the emergency SMS could be triggered by user or the PSAP answering point. For example, the PSAP may send an emergency SMS or emergency SMS reply indicating the user to send the emergency context or emergency message, when the emergency call does not succeed (e.g. poor signal quality) or the operator is unable to understand the caller or cannot hear the caller (e.g. emergency call automatically initiated but the user is unable to speak) .

[0143] According to an embodiment, the user equipment may, e.g., be configured to transmit the emergency context to another device of the wireless communication system. The user equipment may, e.g., be configured to transmit information that the user equipment has transmitted the emergency context to said other device to a network entity of the wirelss communication system.

[0144] In an embodiment, said other device is a passive loT device or an ambient loT device or an active loT device.

[0145] According to an embodiment, the user equipment may, e.g., be configured to generate the emergency context, such that the emergency context comprises information on a status of one or more other users, which are different from the user of the user equipment.

[0146] In an embodiment, the user equipment may, e.g., be configured to generate the emergency context, such that the emergency context is associated with an emergency PIN and / or with an emergency password which allows to update the emergency context from a different device.

[0147] According to an embodiment, the user equipment may, e.g., be configured to generate the emergency context, such that the emergency context comprises information on a structural integrity of an environment, where the user equipment is located.

[0148] In an embodiment, the user equipment may, e.g., be configured to employ a camera and / or radar-like sensing to obtain the information on the structural integrity of the environment, where the user equipment is located.

[0149] According to an embodiment, the user equipment may, e.g., be configured to generate the emergency context, such that the emergency context comprises multimedia content.

[0150] FH240807PEP-2025260532.DOCX In an embodiment, the user equipment may, e.g., be configured to record and / or transmit the multimedia content to another entity of the wireless communication system in an emergency situation.

[0151] According to an embodiment, the user equipment may, e.g., be configured to record and / or transmit the multimedia content to said other entity of the wireless communication system in response to an emergency warning received by the user equipment and / or in response to that the user equipment detects the emergency situation.

[0152] In an embodiment, the user equipment may, e.g., be configured to detect the emergency situation when detecting a shaking characteristic of an earthquake.

[0153] According to an embodiment, the user equipment may, e.g., be configured to delete the multimedia content when receiving information that the user of the user equipment is safe.

[0154] In an embodiment, the user equipment may, e.g., be configured to determine routing information via one or more other user equipments to transmit the emergency context to the network via the one or more other user equipments in case of an emergency situation, when one or more base stations are no longer available.

[0155] According to an embodiment, the user equipment may, e.g., be configured to transmit the emergency context via a transmission route identified by the routing information in case of an emergency situation, when the one or more base stations are no longer available.

[0156] In an embodiment, the user equipment may, e.g., be configured to generate the emergency context, such that the emergency context comprises the routing information.

[0157] According to an embodiment, the user equipment may, e.g., be configured to generate the emergency context, such that the emergency context comprises personalization information which allows or simplifies a communication of an emergency service with the user.

[0158] In an embodiment, the user equipment may, e.g., be configured to generate the emergency context, such that the personalization information comprises a preferred language of the user.

[0159] FH240807PEP-2025260532.DOCX According to an embodiment, the user equipment may, e.g., be configured to generate an automatic translation (e.g., a machine-learning translation) to simplify communication with the user in an emergency situation. In an embodiment, this translation functionality may also (e.g., alternatively or additionally) reside in a network entity, so that the emergency message can be decoded, understood and routed to proper answering point.

[0160] In an embodiment, the user equipment may, e.g., be configured to employ an artificial intelligence / machine learning concept to determine, using sensor data and / or using internal data of the user equipment, a medical state of the user, and / or a motion of the user, and / or a structural integrity of an environment where the user equipment is located.

[0161] According to an embodiment, the user equipment may, e.g., be configured to transmit the emergency context automatically in case of an emergency without interaction with the user.

[0162] In an embodiment, the user equipment may, e.g., be configured to transmit the emergency context only after an interaction with the user in which the user approves the transmission of the emergency context.

[0163] According to an embodiment, the user equipment may, e.g., be configured to transmit the emergency context to another entity of the wireless communication system irrespective of whether or not an emergency situation is present at the user equipment to make the emergency context available at said other entity if an emergency situation should occur at the user equipment.

[0164] In an embodiment, the user equipment may, e.g., be configured to transmit the emergency context to another entity of the wireless communication system in response to a request from said other entity or from a further entity of the wireless communication network.

[0165] According to an embodiment, the user equipment may, e.g., be configured to encrypt the emergency context to obtain an encrypted version of the emergency context. The user equipment may, e.g., be configured to transmit the encrypted version of the emergency context to another entity of the wireless communication system.

[0166] In an embodiment, the user equipment may, e.g., be configured to transmit a message comprising the encrypted version of the emergency context and an unencryped indication indicating that the message relates comprises emergency information.

[0167] FH240807PEP-2025260532.DOCX According to an embodiment, the emergency message may, e.g., be encapsulated within several layers of protocols, enabling the different network entities (e.g. one or more RAN nodes) or core nodes (e.g. an AMF or an SMS gateway) to prioritise and / or to route emergency messages, whereas the sensitive content is only decodable by the PSAP.

[0168] In an embodiment, the content of the emergency message may, e.g., be processed at a network node to determine the information in emergency message and to initiate one or more subsequent actions (e.g. trigger appropriate emergency services and / or create a report and / or forward the report to one or more PSAPs). For example, in case of earthquake, only the messages from UEs that indicate that the user needs to be rescuded are forwarded to PSAP, others indicating safe status are terminated at the network.

[0169] In an embodiment, the user equipment may, e.g., be configured to use a public key of a PSAP (public safety answering point) or a local emergency response center (LERC) or key from national authorities to encrypt the emergency context.

[0170] According to an embodiment, the user equipment may, e.g., be configured to update the emergency context periodically or on demand from another entity of the wireless communication network.

[0171] In an embodiment, the user equipment may, e.g., be configured to transmit the emergency context to said other entity of the wireless communication system after the update.

[0172] According to an embodiment, the user equipment may, e.g., be configured to transmit only those elements of the emergency context to said other entity of the wireless communication system that have been updated.

[0173] In an embodiment, the user equipment may, e.g., be configured to receive an indication of an emergency. The user equipment may, e.g., be configured to generate the emergency context after receiving the indication of the emergency.

[0174] According to an embodiment, the user equipment may, e.g., be configured to receive an indication of an emergency via one or more system information messages (e.g. cell-wide or area-wide bropadcast or on-demand SIB request) or via unicast signaling to the user equipment (e.g., NAS, LPP, RRC, SIP signaling, SLPP).

[0175] FH240807PEP-2025260532.DOCX In an embodiment, the user equipment may, e.g., be configured its capabilities to the network, wherein the capabilities indicate which element of the emergency context, the user equipment is capable to generate and / or is allowed to provide to the network.

[0176] According to an embodiment, the user equipment may, e.g., be configured to receive an information from the network via one or more system information messages (e.g., at least one SIB) or via dedicated signalling, wherein the information indicates that the network supports receiving the emergency context from the user equipment and / or wherein the information indicates which information should the user equipment prepare within the emergency context and / or wherein the information indicates an update and / or transfer frequency of the emergency context.

[0177] In an embodiment, the information is different for two or more different PLMNs supported by the cell.

[0178] According to an embodiment, the user equipment may, e.g., be configured to generate and / or transmit different emergency contexts when attached to different PLMNs, e.g., in case of an NTN cell.

[0179] In an embodiment, the user equipment may, e.g., be configured to generate the emergency context and / or to transmit a certain portion of the emergency context depending on a type of an indication received.

[0180] According to an embodiment, the user equipment may, e.g., be configured to generate the emergency context and / or to transmit a certain portion of the emergency context depends on whether the type of the indication received is an earthquake warning, and / or depends on whether the type of the indication received is a natural disaster warning (e.g., a tsunami warning, or a flood warning) and / or depends on whether the type of the indication received is a warning on an attack on an infrastructure, and / or depends on whether the type of the indication received is a warning on a missile attack, and / or depends on whether the type of the indication received is a warning on a terrorism act, and / or depends on whether the type of the indication received is a warning on an abduction, and / or depends on whether the type of the indication received is a warning on another emergency.

[0181] FH240807PEP-2025260532.DOCX According to an embodiment, the user equipment may, e.g., be configured to transmit a first message comprising a first portion of the emergency context via a first network. The user equipment may, e.g., be configured to transmit a second message comprising a second portion of the emergency context via a second network being different from the first network, if a transmission of the second message via the first network is not possible and / or if the first network is congested.

[0182] In an embodiment, the user equipment may, e.g., be configured to receive information from a first network, which triggers a generation and / or a transmission of the emergency context by the user equipment. The user equipment may, e.g., be configured to transmit the emergency context via a second network being different from the first network.

[0183] According to an embodiment, the first network is a terrestrial network and wherein the second network is a wireless network. Or, the first network is a wireless network and wherein the second network is a terrestrial network. Or, the first network is a terrestrial wireless network and wherein the second network is a non-terrestrial network (e.g. satellite).

[0184] In an embodiment, the user equipment may, e.g., be configured to detect that the first network is unavailable or is congested (e.g., an earthquake and / or a flooding has destroyed the functionality of the first, e.g., terrestrial, network). The user equipment may, e.g., be configured to decide to transmit the emergency context via the second network if the user equipment has detected that the first network is unavailable or is congested.

[0185] According to an embodiment, the user equipment may, e.g., be configured to transmit the emergency context end-to-end between to a server (e.g. a PSAP server), for example, by a user plane data transmission.

[0186] In an embodiment, the user equipment may, e.g., be configured to transmit an identifier to map information transmitted via a user plane with an emergency call or with an identifier associated with the user equipment.

[0187] According to an embodiment, the user equipment may, e.g., be configured to determine a location using a configuration of downlink reference signals preconfigured to the user equipment, wherein the user equipment may, e.g., be configured to receive an indication indicating to use reference signals in an emergency notification or warning system (for example, a corresponding network entity begins transmitting such signals latest when the

[0188] FH240807PEP-2025260532.DOCX emergency notification takes place). In an embodiment, these reference signals may be used in addition to the usually transmitted reference signals. In another embodiment, these reference signals may be used alternatively to the usually transmitted reference signals.

[0189] In an embodiment, the user equipment may, e.g., be configured to transmit one or more uplink reference signals preconfigured to the user equipment, wherein the UE may, e.g., be configured to receive an indication to use such reference signals, in an emergency notification or warning system within a certain area (e.g. list of cells) (for example, the corresponding network entity begins processing such signals latest when the emergency notification takes place).

[0190] According to an embodiment, the user equipment may, e.g., be configured to save one or more measurements (e.g. CIR) and / or multimedia content, on receiving an alert (for example, when receiving an impending earthquake notification), and wherein the user equipment may, e.g., be configured to clear the one or more measurements and / or the multimedia content on receiving an all clear notification and / or when receiving an indication indicating the safe status on the user equipment.

[0191] In an embodiment, the user equipment may, e.g., be configured to receive a request from the network to provide the one or more measurements and / or the multimedia content, if a safe status has not been transmitted to the network.

[0192] Moreover, an entity of a wireless communication system according to an embodiment is provided. The entity of the wireless communication system is configured for receiving an emergency context of a user equipment of the wireless communication system for having the emergency context in case of an emergency situation available at the entity of the wireless communication system, wherein said entity of the wireless communication system is different from said user equipment, wherein the emergency context of the user equipment comprises first information and further information. . The first information of the emergency context comprises at least one of: an information to distinguish an emergency SMS from a standard SMS, a location of the user equipment, a time when the location of the user equipment has been determined, an actual time of the user equipment, an actual date of the user equipment. The further information of the emergency context comprises at least one of: user-specific information comprising information on a user or a state of the user of the user equipment, device-specific information comprising information on the user equipment, environment-specific information comprising information on an environment in

[0193] FH240807PEP-2025260532.DOCX which the user equipment is located, privacy information comprising privacy settings that shall apply in case of an emergency, emergency transmission information comprising information for transmitting data in an emergency situation, an emergency message. The further information of the emergency context is different from the location of the user equipment, and is different from the time when the location of the user equipment has been determined, and is different from the actual time and the actual date of the user equipment.

[0194] According to an embodiment, the entity is a network node of the wireless communication system.

[0195] In an embodiment, the entity is another user equipment of the wireless communication system.

[0196] According to an embodiment, the entity may, e.g., be configured to process the emergency context of the user equipment in case of an emergency situation.

[0197] In an embodiment, the entity may, e.g., be configured to transmit the emergency context to another entity of the wireless communication system for making the emergency context in case of an emergency situation available at the other entity of the wireless communication system.

[0198] According to an embodiment, the emergency context comprises a timestamp, which indicates when the emergency context was last created or modified. And / or, the emergency context comprises a timestamp, which indicates when at least one element of the emergency context was last created or modified.

[0199] In an embodiment, the user-specific information of the further information of the emergency context comprises a status indication which indicates that the user of the user equipment is safe, or comprises a status indication which indicates that the user needs rescue, or comprises a status indication which indicates that the user is injured.

[0200] According to an embodiment, the emergency context comprises a timestamp indicating a time when the status indication has been created.

[0201] In an embodiment, the emergency context comprises information on a source of a time information comprised by the emergency context and / or on a reliability of the time

[0202] FH240807PEP-2025260532.DOCX information comprised by the emergency context, for example, by indicating that the time information has been obtained using an NTP time from an NTP server, or using a GNSS, or using an internal user equipment time and date.

[0203] According to an embodiment, the entity may, e.g., be configured to receive the emergency context by receiving a first portion of the emergency context in a first message and by receiving one or more further portions of the emergency context in one or more further messages.

[0204] In an embodiment, the entity may, e.g., be configured to receive the emergency context within a single message.

[0205] According to an embodiment, the emergency situation is an emergency situation at the user equipment.

[0206] In an embodiment, the emergency context comprises information on two or more locations of the user equipment at two or more different points-in-time.

[0207] According to an embodiment, the emergency context comprises time information for each location of the two or more locations of the user equipment, which indicates for said location at which point-in-time the user equipment has been located at said location.

[0208] In an embodiment, the first information of the emergency context comprises the location of the user equipment.

[0209] According to an embodiment, the first information of the emergency context comprises the location of the user equipment.

[0210] In an embodiment, the further information of the emergency context comprises privacy information for the emergency context or for at least one element of the emergency context.

[0211] According to an embodiment, the privacy information comprises an indication which indicates if the network is allowed to retrieve a particular element of the emergency context. And / or, the privacy information comprises an indication which indicates if the network is allowed to retrieve a particular portion of the emergency context. And / or, the privacy

[0212] FH240807PEP-2025260532.DOCX information comprises an indication which indicates if the network is allowed to retrieve the emergency context in its entirety.

[0213] In an embodiment, the privacy information comprises an indication indicating for each PLMN of different PLMNs, which of the elements of the emergency context the PLMN is allowed to retrieve (e.g., different PLMNs may, e.g., be a home PLMN, a visited PLMN, an equivalent PLMN).

[0214] According to an embodiment, the privacy information comprises an indication that indicates that the user of the user equipment has to indicate its approval to a transmission of the emergency context to a network entity. Or, the privacy information comprises an indication that indicates that a transmission of the emergency context to a network entity is allowed without that the user has to indicate its approval to the transmission.

[0215] In an embodiment, the privacy information comprises an indication that indicates that a network entity may request a transmission of the emergency context without an indication of an approval for the transmission by the user of the user equipment.

[0216] According to an embodiment, the entity may, e.g., be configured to receive an emergency message from the user equipment. The entity may, e.g., be configured to transmit the emergency message to one or more authorities (e.g., to a local emergency response center).

[0217] In an embodiment, the emergency message may, e.g., comprise a text message and / or multimedia content.

[0218] In an embodiment, the emergency message may, e.g., comprise the emergency message comprises the emergency context.

[0219] According to an embodiment, the entity may, e.g., be configured to provide an indication on an emergency to the user equipment via a higher layer of a protocol stack of the entity.

[0220] In an embodiment, the entity may, e.g., be configured to receive the emergency context or a portion of the emergency context or an element of the emergency context from the user equipment together with an identifier being associated with the emergency context.

[0221] FH240807PEP-2025260532.DOCX According to an embodiment, the entity may, e.g., be configured to receive a first message comprising a first portion of the emergency context from the user equipment. Moreover, the entity may, e.g., be configured to receive a second message comprising a second portion of the emergency context from the user equipment together with the identifier being associated with the emergency context. In an embodiment, the identifier may, e.g., be created by the user equipment and may, e.g., then be also transmitted together with the first message. In another embodiment, the identifier may, e.g., be created by the other (e.g., network) entity in response to receiving the first message, may, e.g., then be transmitted to the user equipment, and the user equipment then may, e.g., transmit the second message together with the identifier.

[0222] In an embodiment, the entity may, e.g., be configured to receive a first message comprising a first version of the emergency context from the user equipment. Moreover, the entity may, e.g., be configured to receive a second message comprising a second, updated version of the emergency context from the user equipment together with the identifier being associated with the emergency context. In an embodiment, the identifier may, e.g., be created by the user equipment and may, e.g., then be also transmitted together with the first message. In another embodiment, the identifier may, e.g., be created by the other (e.g., network) entity in response to receiving the first message, may, e.g., then be transmitted to the user equipment, and the user equipment then may, e.g., transmit the second message together with the identifier.

[0223] According to an embodiment, the entity may, e.g., be configured to transmit the identifier to the user equipment.

[0224] According to an embodiment, the user-specific information of the further information of the emergency context comprises information on a health of the user of the user equipment.

[0225] In an embodiment, the user-specific information of the further information of the emergency context comprises medical information, comprising medical related information derived from information entered and / or stored by the user in the user equipment (e.g. allergies, medical conditions, additional medical information, reactions, medications, blood type etc).

[0226] According to an embodiment, the user-specific information of the further information of the emergency context comprises medical information, comprising medical related information

[0227] FH240807PEP-2025260532.DOCX derived from sensors in the user equipment and / or peripheral devices (e.g., smartwatch, etc.) associated to the user equipment.

[0228] In an embodiment, the user-specific information of the further information of the emergency context may, e.g., comprise an indication indicating whether the user is willing to support a rescue and support operation.

[0229] In an embodiment, the user-specific information of the further information of the emergency context comprises an indication indicating whether the user is willing to be a blood-donor in case of disaster scenario.

[0230] According to an embodiment, the user-specific information of the further information of the emergency context comprises a blood group type of the user.

[0231] In an embodiment, the user-specific information of the further information of the emergency context comprises information from the user in a disaster scenario indicating the user is safe, and indicating that the user is willing to be a blood donor.

[0232] According to an embodiment, the user-specific information of the further information of the emergency context comprises information from the user overriding or pausing or resuming his willingness to support a rescue and support operation and / or to be a blood donor (e.g., because he just has contributed blood).

[0233] In an embodiment, the information on the health of the user originates from one or more devices, for example, smartwatches, blood sugar monitors, heartbeat monitors, connected to the user equipment, for example using interfaces such as bluetooth or using sidelink data transmission.

[0234] According to an embodiment, the emergency context comprises privacy information which indicates if access for another entity of the wireless communication system on the information on the health of the user within the emergency context is allowed.

[0235] In an embodiment, the user-specific information of the further information of the emergency context comprises personal identification information, comprising identification information stored by the user in the UE (e.g., a passport number, an identifier associated with insurance, social security, healthcare, etc.).

[0236] FH240807PEP-2025260532.DOCX According to an embodiment, the emergency context comprises information relating to one or more other users being different from the user of the user equipment.

[0237] In an embodiment, the emergency context comprises information on a motion status of the user equipment, for example, if a user equipment is moving or if a user equipment is not moving.

[0238] According to an embodiment, emergency context comprises information on a motion status of the user equipment for two or more different points-in-time.

[0239] In an embodiment, the emergency context comprises sensor data from one or more sensors, wherein the sensor data depends on the user equipment and / or depends on the environment where the user equipment is located and / or depends on a state of the user of the user equipment.

[0240] According to an embodiment, the sensor data comprises data on an air pressure, and / or data on a sound intensity, and / or data on a movement profile, and / or data on accelerometer readings, and / or data on gyroscope readings, and / or data on barometer readings.

[0241] In an embodiment, the emergency context comprises a current status of the user (e.g. falling, trapped, lying down, moving, etc.).

[0242] According to an embodiment, the emergency context comprises an indication on a last time when the user has used the user equipment.

[0243] In an embodiment, the emergency context comprises an indication which indicates that the user is safe, or comprises an indication which indicates that the user needs rescue, or comprises an indication which indicates that the user is injured.

[0244] According to an embodiment, the emergency context comprises an indication indicating that the user has abandoned the user equipment.

[0245] In an embodiment, the emergency context comprises information on a user contact.

[0246] FH240807PEP-2025260532.DOCX According to an embodiment, the emergency context comprises information on a battery power of the user equipment.

[0247] In an embodiment, the entity is a passive loT device or an ambient loT device or an active loT device.

[0248] According to an embodiment, the emergency context comprises information on a status of one or more other users, which are different from the user of the user equipment.

[0249] In an embodiment, the emergency context is associated with an emergency PIN and / or with an emergency password which allows to update the emergency context from a different device.

[0250] According to an embodiment, the emergency context comprises information on a structural integrity of an environment, where the user equipment is located.

[0251] In an embodiment, the emergency context comprises multimedia content.

[0252] According to an embodiment, the emergency context comprises the routing information for a transmission from the user equipment to the entity via one or more other user equipments.

[0253] Routing information provided by the network may, e.g., comprise one or more parameters, for example, one or more of the following: at least one threshold for selecting I not-selecting relays, at least one routing identifier and a list of relay UE IDs in the path, a default path and / or an indication, whether a UE is allowed to discover and / or deviate from the default path, a hop limit, to avoid excessive chaining of multi-hop links, information enabling the UE to reconstruct the whole path (this information may, e.g., be sourced from other UEs too and may be provided by the network / or other UEs to other UEs in vicinity).

[0254] In an embodiment, the emergency context comprises personalization information which allows or simplifies a communication of an emergency service with the user.

[0255] FH240807PEP-2025260532.DOCX According to an embodiment, the personalization information comprises a preferred language of the user.

[0256] In an embodiment, the entity may, e.g., be configured to transmit a request for a transmission of the emergency context to the user equipment.

[0257] According to an embodiment, the entity may, e.g., be configured to receive an encrypted version of the emergency context from the user equipment.

[0258] In an embodiment, the emergency context may, e.g., be encrypted with a public key of a PSAP or of a local emergency response center (LERC) or key from state authorities to encrypt the emergency context.

[0259] According to an embodiment, the entity may, e.g., be not located at the PSAP and may, e.g., not be located at the LERC, and may, e.g., not be located at the other state authority, and the entity may, e.g., be configured to transmit the emergency context in its encrypted version to the PSAP or to the LERC or to another state authority.

[0260] In an embodiment, the entity may, e.g., be located at the PSAP or is located at the LERC or is located at another state authority, and the entity may, e.g., be configured to decrypt the emergency context using a private key of the PSAP or of the LERC or of the other state authority.

[0261] According to an embodiment, the user equipment updates the emergency context periodically or on demand from the entity. The entity may, e.g., be configured to receive the emergency context from the user equipment after the update.

[0262] In an embodiment, the entity may, e.g., be configured to receive only those elements of the emergency context from the user equipment that have been updated.

[0263] According to an embodiment, the entity may, e.g., be configured to transmit an indication of an emergency to the user equipment. The entity may, e.g., be configured to receive the emergency from the user equipmentcontext after transmitting the indication of the emergency.

[0264] FH240807PEP-2025260532.DOCX Furthermore, a wireless communication system according to an embodiment is provided. The wireless communication system comprises a user equipment according to one of the above-described embodiments, and an entity of the wireless communication system according to one of the above-described embodiments. The user equipment is configured for generate an emergency context for the user equipment, such that the emergency context comprises first information and further information. Moreover, he user equipment is configured for transmitting the emergency context to said entity of the wireless communication system for making the emergency context in case of an emergency situation available at said entity of the wireless communication system. Said entity of the wireless communication system is configured to receive the emergency context from the user equipment.

[0265] According to an embodiment, said entity may, e.g., be configured to process the emergency context of the user equipment in case of an emergency situation.

[0266] In an embodiment, said entity is a second entity of the wireless communication system. The wireless communication system comprises a third entity. The second entity may, e.g., be configured to transmit the emergency context to the third entity. The third entity may, e.g., be configured to process the emergency context of the user equipment in case of an emergency situation.

[0267] According to an embodiment, the entity may, e.g., implement one or more of the following: a CSCF (Call session control function) an emergency-CSCF (Emergency call-session control function) an emergency call server an IMS (IP Multimedia subsystem) an LRF (Location retrieval function) an location server (e.g. LMF, GMLC, MPC, SLP) a PSAP (Public service answering point) a routing determination function (RDF) an AMF (Access and mobility function) a SMSF (SMS function) a UDR (Unified data repository) a UDM (Unified data management) a SMF (Session management function)

[0268] FH240807PEP-2025260532.DOCX a NEF (network exposure function) a RAN node (e.g. gNB, ng-eNB, BS, TRP , etc ) a NWDAF: Network data analytics function a Media Gateway control function (MGCF).

[0269] In an embodiment, the entity may, e.g., be configured to transmit the emergency context to a third entity of the wireless communication system, wherein the third entity may, e.g., implement one or more of the following: a CSCF (Call session control function) an emergency-CSCF (Emergency call-session control function) an emergency call server an IMS (IP Multimedia subsystem) an LRF (Location retrieval function) an location server (e.g. LMF, GMLC, MPC, SLP) a PSAP (Public service answering point) a routing determination function (RDF) an AMF (Access and mobility function) a SMSF (SMS function) a UDR (Unified data repository) a UDM (Unified data management) a SMF (Session management function) a NEF (network exposure function) a RAN node (e.g. gNB, ng-eNB, BS, TRP , etc ) a NWDAF: Network data analytics function a Media Gateway control function (MGCF).

[0270] In the following, some considerations are provided.

[0271] In 3GPP networks, earthquake and tsunami warning system (ETWS) has been standardized, which allows the network to send a message warning a UE of an impending earthquake or tsunami. The information is broadcasted over the complete cell, and a UE is paged to indicate the transmission of ETWS. The ETWS consists of two parts - the primary notification, which are short message broadcasted over the cells belonging to the affected area and contain minimal information. The second message, the secondary notification, which may be delivered either via cell-wide broadcast or SMS or as multimedia content. In summary, the network receives message from warning message providers and provide it

[0272] FH240807PEP-2025260532.DOCX to cell-broadcast center. The cell-broadcast center (CBC) formats the message and broadcasts to the RAN to the UE.

[0273] Likewise, the Android™ system also has provisions for detecting signals through crowdsourcing and / or through dedicated seismic sensors (for example, the ShakeAlert® system). Similar to the EWTS, the android system also provides alerts, such as “Be Aware Alert” or “Take Action Alert” depending on the magnitude of the earthquake to be experienced by the user.

[0274] It is possible that emergency situations are triggered in an aftermath of, e.g., an earthquake or a tsunami, may potentially lead situation where emergency calls are initiated, such as due to accidents, missing people or people requiring rescue, such as those buried under the rubble.

[0275] The following mechanisms are defined for handling emergency scenario:

[0276] Emergency calling numbers, such as 911 or 112 are provided for a user to dial, which are received by the public service answering point (PSAP). The E911 uses a feature called automatic location identification (ALI), which provides the caller’s location, and automatic number identification, which identifies caller’s phone number. Likewise, the E112 call uses the cell-ID to provide callers location, and a feature called AML (advanced mobile location) is provided to offer enhanced precision. The UE location, for example, in E112 is initiated when an emergency call is initiated.

[0277] Fig. 2 illustrates a handing emergency location in current 3GPP networks.

[0278] The following is set as requirements of E112 in ETSI TS 103 625 V1.1.1

[0279] • Based on send us what you have now (based on configurable timeout) o Handset shall immediately attempt to determine the best possible current location within T 1 o If no location is available within T1 , then a message should be sent saying all positioning methods have failed. o Should allow all location capabilities for AML (all capabilities normally not available may still be used) + battery check.

[0280] • Should not impact voice. o AML is automatically triggered. o AML should be invisible to user (also to prevent fraud)

[0281] FH240807PEP-2025260532.DOCX o The user should see no AML message record.

[0282] • PSAP (Public service answering point) need to be able to match voice call with AML data (they use MSISDN - mobile subscriber ISDN) o SMS or HTTPS

[0283] • Data connectivity o A / D for GNSS position o Crowd sources databases for location information related to WiFi Aps. o If no data connection, AML messages are still possible with GNSS and SMS transport.

[0284] • Battery check to allow at least 5 minute voice call, (priority is voice call to PSAP).

[0285] The following information may be transmitted as a part of E112.

[0286] • WGS 84 (latitude and longitude measured as a center of circle and radius o 5 decimal degree precision (in data) transferred. o Time of positioning -> Handset should attempt to use NTP time from NTP server, else GNSS. Last resort: Handset time and date. o Level of confidence o Predominant positioning method used

[0287] ■ GNSS or AGNSS

[0288] ■ WiFi Signals

[0289] ■ Cell

[0290] ■ Hybridised result (should say the predominant method) o SIM card identifier (I MSI) and identifier of handset (I MEI) o MCC o MNC

[0291] (MC and MCC is within IMSI with differences while roaming)

[0292] The following information is optional:

[0293] • Altitude

[0294] • Altitude variance

[0295] • Floor Number

[0296] • Emergency number used to make the call (including whether voice or SMS activation - to assist PSAPs to match the call).

[0297] • Source to indicate the version of handsets AML functionality

[0298] In the following, particular embodiments of the present invention are described.

[0299] FH240807PEP-2025260532.DOCX Emergency alerts, such as earthquake and tsunami warning system (ETWS) notification are generated to warn users of impending danger, and / or advising users to take precautions. Such events may potentially cause a large-scale search and rescue operations, where people may be trapped inside structures or isolated. For example, in some scenarios, people may be trapped in rubble after an earthquake and may be rescued only after an extended period. One major problem is identifying the victims, their status and dispatching help, even when the victims cannot themselves initiate emergency calls.

[0300] A solution is to provide information about the user associated with the UE that may be useful for rescue and / or forensic operation to emergency services via the mobile communication network. However, collection and storage of location information and / or other personal information at the network may be costly and / or involve privacy concerns.

[0301] To address these concerns, the emergency context is collected at the UE. The emergency context may be encrypted at the UE before transmission to a second entity and / or stored encrypted in the UE. The encryption key may be provided to the UE by a network entity or by PSAP or by other third party (e.g. authorities).

[0302] Fig. 3 illustrates an emergency context according to an embodiment, which is stored inside the internal memory of a user equipment. E.g., part of the contents may be transferred to a network entity and / or a peer UE.

[0303] In some examples, the emergency context may be transmitted by the UE to the network and stored at the network side. The transmission of UE emergency context may be subject to user preferences and / or privacy profile. For example, the following combinations are possible:

[0304] 1) The UE transmits the UE emergency context autonomously.

[0305] 2) The UE transmits the UE emergency context in response to the request from the network.

[0306] 3) The UE transmits the UE emergency context in response to the request from the network under certain circumstances and / or conditions (e.g. after receiving a message from at least one other entity (e.g. the ETWS notification) or after initiation of emergency call or detection of certain app in the UE) or after being configured by the UE’s higher layers (e.g. change of privacy profile by the UE)

[0307] 4) Autonomous transmission of context under certain circumstances and / or conditions (e.g. after receiving a message from at least one other entity (e.g. the ETWS notification) or after initiation of emergency call or detection of certain app in the UE)

[0308] FH240807PEP-2025260532.DOCX or after being configured by the UE’s higher layers (e.g. change of privacy profile by the UE)

[0309] The UE may request the network to update of context on periodic basis or on demand. The context provided by the UE may be stored for a preconfigured amount of time. For example, if there is an earthquake, the UE context may be stored by at least one network entity for a preconfigured amount of time.

[0310] In some examples, the periodic update of emergency context may be stored by the network entity, to provide forensic record of the UE. Such emergency context may be retrieved for rescue and / or forensic operations. For example, the emergency context may contain at least two positions of the UE, where at least one was generated after receiving the EWTS notification. In this example, the information from two emergency context at time t1 and time t2 may provide the information on the route the user has moved. This information could be combined with available information about the environment, e.g. maps, to determine search location. For example, if the emergency context at time instant t1 (EC1) indicates location inside the building and the emergency context at time instant t2 (EC2) also indicates a location inside the building, this could possibly indicate that the user is trapped under the rubble.

[0311] In such context, one or more parameter describing the health-related information of an individual could be stored as part of emergency context. For example, the pulse-rate or breathing rate could be stored as emergency context.

[0312] Furthermore, radar sensing approaches could be employed by the UE to determine what kind of situation the user is trapped in. The emergency context could indicate one or more measurements, for example, monostatic and / or bistatic and / or inference indicating the information about the environment the user is trapped in.

[0313] In the following, procedures for generating emergency context according to embodiments are described.

[0314] A UE registering itself in the NW may receive a notification and / or a configuration indicating the support of ‘emergency context’ by the visited network. The indication may be indicated to the UE using RRC signalling, NAS signalling, over the top (e.g. using applications) from a server in the trusted domain of an operator or via system information or via sidelink.

[0315] FH240807PEP-2025260532.DOCX A UE may indicate its capability and / or privacy by indicating the information that the UE can I may transfer (i.e. which elements - for example, UE position, user health), and / or under which conditions (e.g. UE indicated emergency, NW indicated emergency alert over an area, etc).

[0316] A NW entity may signal the UE to create / provide an initial ‘emergency context’ or the UE creates an initial emergency context or updates the existing emergency context as a part of the registering the UE with the network or as a response to the network indication to create / provide emergency context.

[0317] If the UE receives a warning message (such as EWTS notification), the UE may:

[0318] 1) Save the emergency context on the UE and / or at least one peripheral device associated with the UE. The emergency context may contain information about the last known location of the UE and / or a peripheral device. a. In some examples, the peripheral device may be a watch, the UE may retrieve at least one physical parameter, such as heart rate, breathing, etc. b. In some examples, the UE may have been used by a person some minutes before the warning, the last contact with the UE may be noted. c. Motion status of the UE upon detecting the warning message may be recorded - for example, if there were steps detected. d. The UE may attempt to determine structural integrity of the location, where the user is found, for example using sensing. e. In some examples, the UE may record some audio in response to emergency warning and store it as context.

[0319] 2) The UE may provide clear after a preconfigured amount of time, after the warning.

[0320] 3) There may be new procedures after every aftershock.

[0321] The trigger may come from application, and / or sensors, wherein at least one function may be triggered and / or at least one function may be disabled.

[0322] The UE may be configured to detect situation like flooding, wherein the UE may not be able to transmit or receive signal from the normal wireless network. The UE may, based on preconfiguration of emergency setting, activate a second interface - for example, a sound based transmission, for example, when the device / user are flooded.

[0323] Activate a second interface - for example, enabling data transmission through Ambient loT. Ambient loT are typically low-power, energy-efficient, and can operate autonomously,

[0324] FH240807PEP-2025260532.DOCX harvesting energy from their surroundings. The UE (which may be battery limited) may write the data to an associated ambient loT device (which may be able to harvest energy from the environment or be powered by a second device (e.g. device from first responders like rescue personnel) before the battery runs out, may be able to obtain emergency information about user (for example trapped in rubble)

[0325] At least a second UE may be configured with at least one resource to monitor for messages. (Like sidelink). The emergency context may be transmitted via sidelink.

[0326] Fig. 4 illustrates a creation of an emergency context according to an embodiment.

[0327] In the following, a transfer of an emergency context according to some embodiments is described.

[0328] The UE may store the created emergency context, and indicate the network that the emergency context is available at the UE. Alternatively, the UE may transfer the emergency context to the network, autonomously or upon network request.

[0329] The network may request to provide the initial ‘emergency context’ or an ‘updated emergency context’.

[0330] The UE provided emergency context may be the same as the NW requested one, or it may differ subject to UE privacy profile and / or capabilities.

[0331] The NW may indicate a timer for updating the UE emergency context at the UE or for updating the UE-emergency context to the network, if it has changed.

[0332] The NW may configure a different refresh time for different elements of the emergency context.

[0333] The emergency context may also be requested and / or transferred using 3GPP agnostic methods to the network entities and / or to PSP. For example, an APP may be installed at the UE to receive emergency notification, and receive emergency context from the UE. The emergency contact may be requested and transferred to the PSAP or an over the top server.

[0334] Fig. 5 illustrates a creation and an update of an emergency context according to an embodiment.

[0335] FH240807PEP-2025260532.DOCX According to some embodiments, a UE creates or updates its emergency context on indication of emergency from higher layers of the protocol stack of the UE. The indication may come from the UE’s own internal logic or processing at the application layer (e.g. APPs) or from UE’s own higher layers or based on the receipt of public warning system messages. The UE may provide initial emergency context, either unsolicited (e.g. based on its own internal processing or based on a request from the network side).

[0336] The network entity receiving the emergency context may store the emergency context and / or forward the emergency context to a second network entity.

[0337] The network entity may provide an identifier to the UE to provide updated emergency context, associating the updated emergency context with this identifier. In some embodiments, the UE may itself provide the identifier to the network. This may be conveyed with the initial emergency context. In this case, the network simply acknowledges the identifier or it may provide a network generated identifier associated with the emergency context. In some examples, the identifier may be used to associate the emergency call (e.g. a SIP call) with the initial emergency context and / or subsequent update to the emergency context. Especially in a SIM-less operation or when a UE is in limited service area (e.g. roaming in this area is not allowed), the identifier is generated by the UE may be derived using its permanent equipment identifier (PEI such as IMEI) or using derived identifiers (such as SUCI) or even its SIP address, SIP-URI and TEL-URI. In some examples, the identifier may be emergency service query key (ESQK) or equivalent identifier for association to previous call or emergency context information.

[0338] The UE may additionally update the emergency context, and provide the updated information using the identifier mutually understood by the network and the UE, so that it can be associated with the initial emergency context and / or the subsequent emergency context updates. In some examples, the identifier may be generated by the network entity in the core network. In other examples, the identifier may be generated by a second entity which contains the database accessible both to the network and the PSAP.

[0339] The identifier may be further be used to associate the emergency context of a UE with subsequent emergency calls or emergency contexts. This may be exchanged across PLMNs (e.g. by the network entity storing information for the PSAP), so that the information transmitted between one or more PLMNs (for example, NTN and terrestrial mobile network, or two different PLMNs) may associated with the same user can be associated together.

[0340] FH240807PEP-2025260532.DOCX The emergency context or some elements of the emergency context of the UE may be stored in an entity in the network (e.g. in UDR / UDM / NEF of the CN). These could be static elements of the emergency context, so that during emergency the information is readily available at the network side. As such, the identifier and initial emergency context may be created by the UE and / or stored at a network before indication of emergency, to be used at time of emergency.

[0341] Fetching or transmission of emergency context before an indication of emergency may take place if the user has indicated consent to transmit such information or if the network has indicated a regulatory override.

[0342] The initial emergency context and / or updates may be confirmed by the network side. For example, there may be an acknowledgement of the message and / or a response message from the PSAP or local emergency response center (LERC). The response message may indicate additional information to the user providing support to the user.

[0343] The emergency context provided by the user may be processed by the network entity and / or the local emergency response center. The information may be provided to authorized users in the system (such as response team).

[0344] According to some embodiments, some elements of the UE context may be stored in an entity in the core network (such as UDM, UDR). They may be stored in the core network in an encrypted form, which may be read only by entities external to the 3GPP network.

[0345] In one example, the network entity that needs to decode the stored information may depend on the current location of the UE. For example, based on the current UE location, the PSAP to which the emergency calls are routed may be different. Therefore, the network may provide information about encryption keys that are area based (e.g. based on camped cell, group of cells, or based on RAN-notification area, tracking area or based on geographic location). The RAN network may broadcast the public keys for generating the emergency context. The UE may provide the emergency context when performing an area update (e.g. change of TA, change of RAN area, change of camped cell), which may be stored at the network side. The UE context may additionally be saved at the H-PLMN for resilience when operating in the visited network. If the visited network goes out of operation, then the UE context is available at home network for retrieval.

[0346] To provide and / or update emergency context, the UE may register with the network indicating emergency registration or emergency context registration or emergency context

[0347] FH240807PEP-2025260532.DOCX update. The emergency registration (e.g emergency call and / or emergency context transfer after emergency indication) may be prioritized registration and data transfer compared to the registration where emergency information is provided proactively.

[0348] In some examples, the UE may make use of small data transmission (SDT) or small data reception (SDR) feature to transmit emergency context data, if the data volume is below a threshold value indicated to the by a network entity.

[0349] The network entity receiving the emergency context and / or an emergency message from the UE or forwarding to a second network entity or processing the information to derive any further analytics or information or provide information to another network entity may be any of the following:

[0350] CSCF (Call session control function)

[0351] Emergency-CSCF (Emergency call-session control function)

[0352] Emergency call server

[0353] IMS (IP Multimedia subsystem)

[0354] LRF (Location retrieval function)

[0355] Location server (e.g. LMF, GMLC, MPC, SLP)

[0356] PSAP (Public service answering point)

[0357] Routing determination function (RDF)

[0358] AMF (Access and mobility function)

[0359] SMSF (SMS function)

[0360] UDR (Unified data repository)

[0361] UDM (Unified data management)

[0362] SMF (Session management function)

[0363] NEF (network exposure function)

[0364] RAN node (e.g. gNB, ng-eNB, BS, TRP , etc )

[0365] NWDAF: Network data analytics function.

[0366] Media Gateway control function (MGCF).

[0367] In the following, a storage of an emergency context according to some embodiments is described.

[0368] The emergency context may, for example, be stored as a UE-specific data in one or more of network entities. The information may be stored in RAN-network, in the AMF and / or in the UDM in home or visited network.

[0369] FH240807PEP-2025260532.DOCX Likewise, some emergency context may be stored in a UE acting as a sidelink relay. For example, the ‘Safe indication’ of the user may be provided to a destination UE, where the sidelink relay UE relays the message. The emergency context may be encrypted, and only the destination UE may have the keys to decode the information.

[0370] Some emergency context may be stored in a peripheral device, such as smartwatch associated to the UE (e.g. using Bluetooth connection or sidelink).

[0371] Some emergency context may be stored in an ambient loT device, wherein the UE may have written the data to the ambient loT device. The ambient loT device may provide the transmit the data to a reader, where the reader is a second device. In some examples, the second device may be associated with the rescue team searching for trapped victims (e.g. during earthquake). This feature is useful when the battery in the UE may have run out, but the emergency context is still stored in the UE. In some examples, the infrastructure damage may have forced the UE emergency context not being successfully transmitted. If the UE is associated to an ambient loT device (e.g. writes to it during emergency), then the emergency context may be retrieved by the second device (e.g. the UE or TRP used by rescue services).

[0372] The stored emergency context for a UE at the network, may be based on at least one information transferred by the UE to the network. However, the network store different level of details of emergency context than the UE. For example, the network obtain information from data analytics (e.g. from the NWDAF) about probable UE location, and create a UE emergency context based on network information about the UE. The network may analyse and store the information provided by the UE according to time.

[0373] If the UE privacy profile does not send certain information, the network may use regulatory override to override the UE settings. For example, the UE privacy profile may be adapted to regulations in a home region, but the local regulations in visited network may differ. The regulatory override may be used to retrieve the information from the UE. Alternatively, additional information may be acquired by the network and put it as part of UE emergency context.

[0374] In some examples, the UE may be one of the legacy UE and may not support the emergency context function. The network may make use of legacy mechanism and / or network side signal processing to determine and store the UE context. For example, NW- sided positioning to determine UE location at one or more instants in time. For example, in

[0375] FH240807PEP-2025260532.DOCX an earthquake prone country, the network may update the location of the UE regularly to ascertain the UE location.

[0376] In the following, a usage of an emergency context according to some embodiments is described.

[0377] For example, the emergency context may, e.g., be employed for search and rescue operations, and / or for forensics, and / or for informing emergency contacts.

[0378] In one example, the emergency context may contain a notification indicating that the user is safe from the disaster situation. The notification may be stored at the network, for example, at the AMF or at the UDM. If a UE is paged with an incoming call from a number or a group of numbers, and the UE may not be reachable, for example due to contention in network or to prioritize certain services (e.g. calling emergency numbers), then if the user has stored the number to a certain group (e.g. emergency contact number), then the network may send at least one information from the emergency context to the caller ID. For example, sending a message (e.g. an SMS) that the user is safe to the emergency contact. Thus, the network resources usage is reduced at time of contention.

[0379] Such notification are used to trigger the UE to create, modify, or update information about the user that may be useful for rescue and / or forensic operations.

[0380] According to some embodiments, an emergency context may, e.g., comprise UE-specific and / or user-specific and / or device specific information, and may, e.g., be created and stored in the UE.

[0381] Subject to the capabilities of the UE, the ‘emergency context’ stored by the UE may consist of one or more information pertaining to the UE and / or the user.

[0382] The emergency context may, e.g., comprise of at least one position of the UE.

[0383] In the following, possible contents of emergency context according to some embodiments are provided.

[0384] The emergency context, e.g., the information generated and / or stored and / or transmitted by the UE pertaining to emergency may consist of one or more of the following information. The following embodiments are particular examples of some embodiments. The UE and / or the network may request further information which may aid emergency calls.

[0385] FH240807PEP-2025260532.DOCX According to a particular embodiment, the emergency context may, e.g., comprise a timestamp.

[0386] The timestamp may be provided to indicate when the emergency context was last created or modified. Alternatively or in addition, there may be a timestamp associated with the creation or modification of at least one element of the emergency context. For example, the emergency context may consist of a status indicating the user is safe after the disaster struck (e.g main quake), but there may be a second wave of disaster (e.g. an aftershock), where the emergency context may not have been updated. A second example, the emergency context may consist of one or more instances of user location (e.g. user location before ETWS warning, during the shaking, and after the shaking ends). The source of time and / or reliability may additionally be stored, for example, NTP time from NTP server, or GNSS or Handset time and date.

[0387] According to a particular embodiment, the emergency context may, e.g., comprise a location.

[0388] The UE may attempt to obtain its own location (self-location, e.g. using GNSS or assisted GNSS or DL-TDOA, DL-AoD, Multi-RTT or sidelink positioning or using radar-like sensing) or request the NW to provide its location (e.g. by initiating the MO-LR). If location data is included in the emergency context, then there may be one or more instances of user location (e.g. user location before ETWS warning, during the shaking, and after the shaking ends).

[0389] According to a particular embodiment, the emergency context may, e.g., comprise a privacy profile of the UE. Or, a privacy profile may, e.g., exist, which defines access to the emergency context and / or to portions of the emergency context and / or to elements of the emergency context.

[0390] The UE may store as a part of its emergency context, the privacy profile of at least one element of the emergency context. This means that the associated element of the emergency context, part of the emergency context or the entire emergency context may be retrieved by the network or the UE may provide the associated element of emergency context part of the emergency context or the entire emergency context to the network.

[0391] For example, the user may have indicated that the user consents to having the location transmitted to the network, if NW has requested the emergency context after sending an

[0392] FH240807PEP-2025260532.DOCX emergency warning (e.g. earthquake warning, tsunami warning, fire warning ... etc). Alternatively, the user may have indicated that the user needs to approve the context transfer each time it is transmitted.

[0393] Some elements of the emergency context may be transferred, despite not explicitly consented, subject to indication of ‘regulatory override’ to the UE (e.g. issued by authorities or subject to local regulations) and / or subject to initiation of emergency calls. For example, the UE may automatically transfer its location when the user or the UE autonomously has initiated the emergency call on detecting certain events (such as a car crash).

[0394] Some of the information may be transmitted only to home network or equivalent network, whereas others may also be provided to visited network.

[0395] According to a particular embodiment, the emergency context may, e.g., comprise health- related information of the user.

[0396] Health-related information may be obtained by the UE from the peripheral devices, such as smartwatches, blood sugar monitors, heartbeat monitors, connected to the UE using interfaces such as Bluetooth or using sidelink data transmission. Alternatively, they may be detected using sensing (such as radar like sensing) or signal processing on transmitted data and signals for communication (integrated sensing and communication).

[0397] In some examples, the collected information may already be a basis for triggering emergency calls or providing emergency context.

[0398] The transfer of health related information may be subject to privacy protection of the user. The UE may consent to transfer of health related information to the network under certain conditions (e.g. user vital data degrades to a certain point, in response to emergency warning (e.g. ETWS), etc).

[0399] According to a particular embodiment, the emergency context may, e.g., comprise a motion status of the UE.

[0400] In an example, the motion status of the UE at different time instances may be stored in the emergency context. This together with the information about the location may be utilized by emergency services or for forensic purposes.

[0401] FH240807PEP-2025260532.DOCX According to a particular embodiment, the emergency context may, e.g., comprise a sensor reading and / or information based on sensor readings.

[0402] The UE and / or the network node and / or a peripheral device connected to a UE may be able to record one or more sensor reading corresponding to the UE and / or the area where the UE is located in.

[0403] The example may include air pressure, sound intensity, movement profile, accelerometer readings, gyroscope readings, barometer readings.

[0404] According to a particular embodiment, the emergency context may, e.g., comprise users last interaction with the UE. (E.g., the last interaction of the user with his UE, or the last interaction of one or more other users, e.g., with their respective UE).

[0405] This indicates when was the last time a user has used the UE. Such information may be used to identify that the UE location and the associated user location may not be the same. Alternatively, if the user indicated ‘I am safe’ status, (e.g. in response to the prompt at the UE in aftermath of the emergency scenario), the emergency context can be reliably associated with a user. By contrast, if the UE location is indicated under a rubble but the interaction shows that it has not been used by a user or has collected no information about a user within a threshold period, then this may be a case where the automatically retrieved emergency context may not provide information associated with a person.

[0406] Likewise, the user may have been interacting with the UE but may have left UE behind at disaster spot. Additional information may be updated at the UE, for example, RSRP or RTT between peripheral device (e.g a smartwatch) and the UE indicating that the UE was abandoned.

[0407] A peripheral device may be able to announce later to other UEs or devices to update the context to the network. For example, the user may have moved out of the rubble but the UE may be trapped in the rubble. A peripheral device may be able to indicate other UE (e.g. using sidelink or Bluetooth) to update the emergency context for the user or the UE to the network.

[0408] According to a particular embodiment, the emergency context may, e.g., comprise an emergency contact of the user.

[0409] FH240807PEP-2025260532.DOCX The user may have indicated emergency contact of the user. This information may be subject to privacy and / or regulatory override be transferred to the network or the network may have acquired it as a part of agreement with the user. The network may store the emergency contact of the user, for example in the UDM. There may be more than one or more emergency contact number. The emergency number and / or conditions associated with receiving the emergency context retrieved from the UE may be stored.

[0410] For example, an emergency contact may be a relative of the user in the disaster area. The emergency caller may be in disaster area or outside of it. Most of the time the vital information sought by a caller is whether the user is safe or not. Radio network often has to drop incoming I outgoing calls or data to prioritize emergency calls in event of disaster due to high traffic or congestion or due to priority. To mitigate the impact, the caller indicated in emergency contact may be provided with at least one information acquired from the UE (safe status of the user), subject to privacy profile of the emergency context, even if the UE cannot be paged. This may be provided with a timestamp when the element of the emergency context was acquired by the network.

[0411] Fig. 6 illustrates a flow chart depicting an embodiment, wherein the emergency contact of a user is informed that the user is safe. Alternatively, the emergency contact may, e.g., be in the same way or in a simiar way be informed that the user is injured or that the user needs help I needs to be rescued.

[0412] According to a particular embodiment, the emergency context may, e.g., comprise a battery power, e.g., a battery power of the UE.

[0413] The remaining battery power level or remaining time may be an emergency context indicated to the network. This may enable the network to enable or disable some functionalities or change the sleep cycle of the UE, so as to conserve battery. For example, if the UE has remaining battery power above a certain threshold, then it may utilize additional sensors and processing, or deploy radar like sensing to obtain more accurate picture of the situation in which the UE finds itself in. On the other hand, if the network receives a battery power report below a second threshold, the network may choose to configure longer DRX cycles or longer eDRX cycles to preserve the battery. Furthermore, the network may be able to enable some ultra power saving measures to extend the battery life, thereby enabling the user in emergency situations to be accessible for a longer period.

[0414] According to a particular embodiment, the emergency context may, e.g., comprise information on alternate devices.

[0415] FH240807PEP-2025260532.DOCX Alternate devices (e.g. passive loT devices) may be indicated as alternate devices that store the latest emergency context. These devices may be triggered before the UE runs out of battery, and may provide signs during the later rescue phase. In emergencies, such as flooding, the information may be transferred to A-loT devices to assist in later rescue or forensic analysis (It should unfortunately not be assumed that everybody survives after a disaster).

[0416] In such a scenario, the important emergency context may be written into the A-loT devices, and such information may be retrieved later.

[0417] According to a particular embodiment, the emergency context may, e.g., comprise alternate information entered by the user.

[0418] A user may indicate additional information, which may be used by emergency services. For example, the user may provide identities of other users that are ‘Safe’ or ‘Trapped’. This may further indicate evidence. The emergency context may be created at the network side for such secondary users, based on (for example) verification by humans or based on ID and Emergency PIN.

[0419] According to a particular embodiment, the emergency context may, e.g., comprise an emergency PIN and / or an emergency password.

[0420] The emergency context may include emergency PIN to update emergency context from a different device. For example, during disaster (e.g. during earthquake), the UE may be forgotten and left under the rubble. The user may use emergency PIN / Password or suitable verification mechanisms to update emergency context, such as I am safe message, from a second device, which may or may not be associated with the user. The PIN to update the network-sided emergency context from a different device may be provided by the user as a part of its emergency context.

[0421] According to a particular embodiment, the emergency context may, e.g., comprise information on a structural integrity of the structure.

[0422] The UE may attempt to determine structural integrity of the location, where the user is found / trapped, for example using radar-like sensing or UE sensors available, like camera.

[0423] FH240807PEP-2025260532.DOCX According to a particular embodiment, the emergency context may, e.g., comprise multimedia content.

[0424] In some examples, the UE may record some audio, pictures, videos in response to emergency warning or UE-initiated emergency call and store / transmit it as an emergency context. This may be sent to network, subject to privacy profile or on user consent. For example, shaking characteristic of an earthquake detected after EWTS may trigger an automated video recording, which may be useful for rescue I forensic operations.

[0425] In some examples, such automatically recorded videos are deleted immediately after receiving ‘safe indication’. In some situation, such emergency context is transferred subject to user action or regulatory override or user consent.

[0426] According to a particular embodiment, the emergency context may, e.g., comprise routing information to next functional node. The next functional node may include sidelink relay UEs or repeaters or via satellites.

[0427] A UE may store routing information to reach a network node, as part of emergency context. This routing information may be computed and preconfigured to the UE before the disaster occurs, so that at time of disaster, data packets can be routed via different UEs to the next functional network.

[0428] Fig. 7 illustrates a transmissoun route via other UEs according to an embodiment, when base stations are no longer available in a disaster scenario.

[0429] A UE (e.g UE1), which is connected via a network node (e.g. TRP1) may be preconfigured with a possible sidelink connection to reach a second network node (e.g. TRP2) if the link between UE1 and TRP1 is broken. In this example, the UE1 loses connectivity and attempts to connect via UE2, which has also lost connectivity. However, the UE2 has a preconfiguration saying it may reach TRP3 via UE3, but UE3 like UE1 and UE2 is also in disaster area and has failed connectivity. However, UE3 is preconfigured to maintain connectivity via UE4. The UE4 is in connectivity after the disaster, so is able to provide connectivity to UE3, which in turn can now route packets of U2 to UE4 via UE3, and the UE2 now inturn routes packets of UE1 , via UE2, UE3 and UE4.

[0430] The emergency context in UE1 , which may have changed after the initial context that was provided to the network, may be updated using the new routing information.

[0431] FH240807PEP-2025260532.DOCX The routing information to the functional node is an emergency context, that may be shared among the peer UEs to establish functional connection.

[0432] Emergency context for UE-routing:

[0433] UE1 : Next Hop UE2, Nhops = 3.

[0434] UE2: UE1 , Nhops = 2.

[0435] UE3: UE4, Nhops = 1.

[0436] UE4: TRP4, Nhops = 0.

[0437] In an example, a UE may store one or more emergency contexts with multiple number of hops. It may broadcast the context of routing based on certain criteria:

[0438] 1) Number of hops

[0439] 2) Throughput expected

[0440] If a new connectivity link appears, and the Nhops decreases, then the new node may also announce the new connectivity path.

[0441] In some examples, the UE may attempt to reach another UE (e.g. another UE on emergency contact). The UEs may exchange the safe status of the affected UE via the routing information after end-to-end contact is established.

[0442] In other example, a UE may flood the network with emergency context (e.g. safe status and intended destination), via broadcast, and the receiving UE forward the safe status, until the intended receipent is found.

[0443] When the intended UE receives the message, the receiver broadcasts the confirmation of safe receipt. The UEs that receive the safe receipt discard previously stored emergency context of the UE, if any.

[0444] Fig. 8 illustrates a transmission of a user-safe message according to an embodiment to other user equipments.

[0445] The emergency context received via multihop at a functional node may enable the incoming calls for the UE to be automatically answered using information from emergency context. For example, the call from the emergency contact number receives the safe status of the UE, even if the UE cannot be paged by the network.

[0446] FH240807PEP-2025260532.DOCX According to a particular embodiment, the emergency context may, e.g., comprise personalization information (e.g. a language).

[0447] This may for example, include, the language of the user for emergency context. Disaster can happen anywhere. For example, a user who does not speak Japanese does not benefit from emergency messages provided via broadcast in Japanese characters. The emergency context may be retrieved to provide alerts and information in correct language.

[0448] Although some aspects of the described concept have been described in the context of an apparatus, it is clear that these aspects also represent a description of the corresponding method, where a block or a device corresponds to a method step or a feature of a method step. Analogously, aspects described in the context of a method step also represent a description of a corresponding block or item or feature of a corresponding apparatus.

[0449] Various elements and features of the present invention may be implemented in hardware using analog and / or digital circuits, in software, through the execution of instructions by one or more general purpose or special-purpose processors, or as a combination of hardware and software. For example, embodiments of the present invention may be implemented in the environment of a computer system or another processing system. Fig. 9 illustrates an example of a computer system 600. The units or modules as well as the steps of the methods performed by these units may execute on one or more computer systems 600. The computer system 600 includes one or more processors 602, like a special purpose or a general-purpose digital signal processor. The processor 602 is connected to a communication infrastructure 604, like a bus or a network. The computer system 600 includes a main memory 606, e.g., a random-access memory, RAM, and a secondary memory 608, e.g., a hard disk drive and / or a removable storage drive. The secondary memory 608 may allow computer programs or other instructions to be loaded into the computer system 600. The computer system 600 may further include a communications interface 610 to allow software and data to be transferred between computer system 600 and external devices. The communication may be in the from electronic, electromagnetic, optical, or other signals capable of being handled by a communications interface. The communication may use a wire or a cable, fiber optics, a phone line, a cellular phone link, an RF link and other communications channels 612.

[0450] The terms “computer program medium” and “computer readable medium” are used to generally refer to tangible storage media such as removable storage units or a hard disk

[0451] FH240807PEP-2025260532.DOCX installed in a hard disk drive. These computer program products are means for providing software to the computer system 600. The computer programs, also referred to as computer control logic, are stored in main memory 606 and / or secondary memory 608. Computer programs may also be received via the communications interface 610. The computer program, when executed, enables the computer system 600 to implement the present invention. In particular, the computer program, when executed, enables processor 602 to implement the processes of the present invention, such as any of the methods described herein. Accordingly, such a computer program may represent a controller of the computer system 600. Where the disclosure is implemented using software, the software may be stored in a computer program product and loaded into computer system 600 using a removable storage drive, an interface, like communications interface 610.

[0452] The implementation in hardware or in software may be performed using a digital storage medium, for example cloud storage, a floppy disk, a DVD, a Blue-Ray, a CD, a ROM, a PROM, an EPROM, an EEPROM or a FLASH memory, having electronically readable control signals stored thereon, which cooperate or are capable of cooperating with a programmable computer system such that the respective method is performed. Therefore, the digital storage medium may be computer readable.

[0453] Some embodiments according to the invention comprise a data carrier having electronically readable control signals, which are capable of cooperating with a programmable computer system, such that one of the methods described herein is performed.

[0454] Generally, embodiments of the present invention may be implemented as a computer program product with a program code, the program code being operative for performing one of the methods when the computer program product runs on a computer. The program code may for example be stored on a machine readable carrier.

[0455] Other embodiments comprise the computer program for performing one of the methods described herein, stored on a machine readable carrier. In other words, an embodiment of the inventive method is, therefore, a computer program having a program code for performing one of the methods described herein, when the computer program runs on a computer.

[0456] A further embodiment of the inventive methods is, therefore, a data carrier or a digital storage medium, or a computer-readable medium comprising, recorded thereon, the

[0457] FH240807PEP-2025260532.DOCX computer program for performing one of the methods described herein. A further embodiment of the inventive method is, therefore, a data stream or a sequence of signals representing the computer program for performing one of the methods described herein. The data stream or the sequence of signals may for example be configured to be transferred via a data communication connection, for example via the Internet. A further embodiment comprises a processing means, for example a computer, or a programmable logic device, configured to or adapted to perform one of the methods described herein. A further embodiment comprises a computer having installed thereon the computer program for performing one of the methods described herein.

[0458] In some embodiments, a programmable logic device, for example a field programmable gate array, may be used to perform some or all of the functionalities of the methods described herein. In some embodiments, a field programmable gate array may cooperate with a microprocessor in order to perform one of the methods described herein. Generally, the methods are preferably performed by any hardware apparatus.

[0459] The above described embodiments are merely illustrative for the principles of the present invention. It is understood that modifications and variations of the arrangements and the details described herein are apparent to others skilled in the art. It is the intent, therefore, to be limited only by the scope of the impending patent claims and not by the specific details presented by way of description and explanation of the embodiments herein.

[0460] FH240807PEP-2025260532.DOCX REFERENCES

[0461] RRC TS38.331 V16.1.0 LPP TS37.355 V16.1.0

[0462] NRPPa TS38.455 V16.0.0

[0463] ETSI TS 103 625 V1.1.1

[0464] FH240807PEP-2025260532.DOCX ABBREVIATIONS

[0465] FH240807PEP-2025260532.DOCX

[0466]

[0467] FH240807PEP-2025260532.DOCX

Claims

CLAIMS1. A user equipment of a wireless communication system, wherein the user equipment is configured for: generating an emergency context for the user equipment, such that the emergency context comprises first information and further information, and transmitting the emergency context to another entity of the wireless communication system for making the emergency context in case of an emergency situation available at the other entity of the wireless communication system, wherein the first information of the emergency context comprises at least one of: an information to distinguish an emergency SMS from a standard SMS, a location of the user equipment, a time when the location of the user equipment has been determined, an actual time of the user equipment, an actual date of the user equipment, wherein the further information of the emergency context comprises at least one of: user-specific information comprising information on a user or a state of the user of the user equipment, device-specific information comprising information on the user equipment, environment-specific information comprising information on an environment in which the user equipment is located, privacy information comprising privacy settings that shall apply in case of an emergency emergency transmission information comprising information for transmitting data in an emergency situation, an emergency message wherein the further information of the emergency context is different from the location of the user equipment, and is different from the time when the location ofFH240807PEP-2025260532.DOCXthe user equipment has been determined, and is different from the actual time and the actual date of the user equipment.

2. A user equipment according to claim 1 , wherein the first information of the emergency context comprises the information to distinguish an emergency SMS from a standard SMS.

3. A user equipment according to claim 2, wherein the information to distinguish an emergency SMS from a standard SMS comprises at least one of the following: indication of an emergency cause while setting up RRC connection or while setting up SIP connection or while resuming RRC connection from an RRCJNACTIVE mode, an indication of an emergency number or string, e.g., in a TP-DA field, an indication of a local network node, an indication of an emergency SIP URL, an indication of a type of number (TON), wherein an unknown number could trigger emergency handling, an indication of a type of emergency and / or a type of emergency service requested, e.g., fire, ambulance, police.

4. A user equipment according to claim 2 or 3, wherein the information to distinguish an emergency SMS from a standard SMS is used by a network entity for at least one of the following: prioritizing a transmission of the emergency SMS or emergency message, enabling the message to be transmitted even without authorization, e.g., without USIM, eSIM, initiating a location service and / or sensing service and / or tracking service for the user equipment, e.g., trigger another network entity to initiate location service procedures, initiate a callback service,FH240807PEP-2025260532.DOCXselecting a local PSAP (e.g., a visited network) over a PSAP in a home network, (e.g., home routed) in case of a roaming scenario, selecting a local PSAP corresponding to the location of the user equipment and / or routing the SMS or IMS message towards the local PSP.

5. A user equipment according to one of claims 2 to 4, wherein, the user equipment is configured to receive an indication that the network does not support emergency SMS, or is configured to detect during initiating an emergency SMS that emergency SMS is not supported locally for the intended service.

6. A user equipment according to claim 5, wherein, if the user equipment receives an indication that the network does not support emergency SMS, or detects during initiating an emergency SMS that emergency SMS is not supported locally for the intended service, the user equipment is configured to conduct one or more of the following: indicate to one or more higher layers that the emergency SMS is not supported or is not supported for particular service (e.g. , police only) or group of user equipments (e.g., for roaming user equipments, for home routed traffic), attempt to connect to a second PLMN that allows to transmit emergency SMS, indicate alternate means (e.g., voice call), an indication and / or warning that emergency SMS is sent out as a normal SMS (which may I may not be delivered, e.g., indicate the user for alternate means if no response is received).

7. A user equipment according to one of claims 2 to 6, wherein, if the user equipment is in a roaming scenario and / or is connected to an NTN, the user equipment is configured to perform and / or o request a differentiated handling (e.g., indication of local breakout) of an emergency message over a normal data transmission (e.g., which may be in home routed traffic).FH240807PEP-2025260532.DOCX8. A user equipment according to one of claims 2 to 7, wherein the user equipment is configured to generate an emergency message, when the user equipment detects an emergency, which does not support emergency calling and / or when a calling quality is degraded (e.g., due to power restrictions in an NTN user equipment).

9. A user equipment according to one of the preceding claims, wherein, if the user equipment has a battery power limitation for an emergency call (for example, if a remaining battery life is less than a certain value, such as 5 minutes), the user equipment is configured to send an emergency message instead of initiating a voice call.

10. A user equipment according to one of the preceding claims, wherein, when the user equipment receives an emergency SMS or emergency IMS or emergency message from one or more higher layers (e.g., from an application layer) and / or an indication to transmit an emergency SMS / message, the user equipment is configured to indicate to the network to request prioritized access by indicating emergency cause while requesting RRC_CONNECTION.

11. A user equipment according to one of the preceding claims, wherein when the user equipment is in a visited network and / or connected via NTN, the user equipment is configured to generate SMSC address of a local emergency service via SMSC in a visited network and / or is configured to send an SMS over NAS and / or is configured to indicate a local breakout of emergency data when using IMS to send emergency message.

12. A user equipment according to one of the preceding claims, wherein the user equipment is configured to receive from a network entity a temporary mapping (e.g., communicated via SI messages or RRC messages or OMA client provisioning or OMA device management or SMS provisioning / updateFH240807PEP-2025260532.DOCXetc) of an emergency service access number for a message and / or for a call for emergency arising from a specific disaster, wherein the user equipment is configured to receive from the network an indication that indicates a new mapping of an emergency service for this category of disaster (e.g., XXX for earthquake / flood instead of or in addition to the usual emergency numbers (e.g., 110, 111 , 112, 911)), wherein the new mapping may be time-limited and / or area-limited and / or is applicable only in visited network.

13. A user equipment in a wireless communication system, wherein the user equipment is configured to receive an emergency message from a PSAP or from a network entity, which may be sent in response to emergency detected by the network; and / or in response to information provided by a third party (e.g., trusted third party - like national organization monitoring emergency events - like meterological and / or seismological organisations); and / or in response to emergency call or sms initiated by the user equipment.

14. A user equipment according to claim 13, wherein the user equipment is configured to initiate an RRC_CONNECTION indicating an emergency cause while requesting the RRC_CONNECTION in response to a paging and / or a network indication and / or a higher layer indication for receiving emergency message (e.g., SMS / IMS or otherwise).

15. An user equipment according to claim 13 or 14, wherein the user equipment is configured to generate and transmit an emergency context to another entity of the wireless communication system for making the emergency context in case of an emergency situation available at the other entity of the wireless communication system.FH240807PEP-2025260532.DOCX16. The user equipment according to one of claims 1 to 12 or according to claim 15, wherein the user equipment is configured to generate the emergency context, such that the emergency context comprises a timestamp, which indicates when the emergency context was last created or modified, and / or wherein the user equipment is configured to generate the emergency context, such that the emergency context comprises a timestamp, which indicates when at least one element of the emergency context was last created or modified.

17. The user equipment according to one of claims 1 to 12 or according to claim 15 or 16, wherein, if a RAT and / or a frequency where the user equipment is currently connected on does not allow determining a location of the user equipment or does not allow determining a location of the user equipment for an emergency use case, the UE is configured to send the emergency message it has generated, and to await a network response, for example, in which the network redirects the user equipment to a different RAT and / or a different frequency to perform measurements and / or to transmit reference signals or to retransmit the emergency message, and / or to perform a cell-reselection and to transmit and emergency message using the new RAR / frequency.

18. The user equipment according to claim 17, wherein whether or not transmission and / or reception of an emergency message and / or an emergency location is supported by the network is indicated to the user equipment via system information or through unicast signalling.

19. The user equipment according to one of claims 1 to 12 or according to one of claims 15 to 18, wherein the user equipment is configured to generate the emergency context, such that the user-specific information of the further information of the emergency contextFH240807PEP-2025260532.DOCXcomprises a status indication which indicates that the user of the user equipment is safe, or comprises a status indication which indicates that the user needs rescue, or comprises a status indication which indicates that the user is injured.

20. The user equipment according to claim 19, wherein the user equipment is configured to generate the emergency context, such that the emergency context comprises a timestamp indicating a time when the status indication has been created.

21. The user equipment according to claim 15 to 20, wherein the user equipment is configured to generate the emergency context, such that the emergency context comprises information on a source of a time information comprised by the emergency context and / or on a reliability of the time information comprised by the emergency context, for example, by indicating that the time information has been obtained using an NTP time from an NTP server, or using a GNSS, or using an internal user equipment time and date.

22. The user equipment according to one of claims 1 to 12 or according to one of claims 15 to 21, wherein the user equipment is configured to transmit the emergency context by transmitting a first portion of the emergency context in a first message and by transmitting one or more further portions of the emergency context in one or more further messages.

23. The user equipment according to one of claims 1 to 12 or according to one of claims 15 to 21, wherein the user equipment is configured to transmit the emergency context within a single message.

24. The user equipment according to one of claims 1 to 12 or according to one of claims 15 to 23,FH240807PEP-2025260532.DOCXwherein the emergency situation is an emergency situation at the user equipment.

25. The user equipment according to one of claims 1 to 12 or according to one of claims 15 to 24, wherein the user equipment is configured to generate the emergency context, such that the emergency context comprises information on two or more locations of the user equipment at two or more different points4n-time.

26. The user equipment according to claim 25, wherein the user equipment is configured to generate the emergency context, such that the emergency context comprises time information for each location of the two or more locations of the user equipment, which indicates for said location at which point-in-time the user equipment has been located at said location.

27. The user equipment according to one of claims 1 to 12 or according to one of claims 15 to 26, wherein the user equipment is configured to generate the emergency context, such that the first information of the emergency context comprises the location of the user equipment, and wherein the user equipment is configured to determine its own location, for example, using self-location, e.g., using GNSS, or assisted GNSS or DL-TDOA, DL-AoD, multi-RTT, or sidelink positioning or using radar-like sensing.

28. The user equipment according to one of claims 1 to 12 or according to one of claims 15 to 27, wherein the user equipment is configured to generate the emergency context, such that the first information of the emergency context comprises the location of the user equipment, andFH240807PEP-2025260532.DOCXwherein the user equipment is configured to request a network entity of the wireless communication system to provide the location of the user equipment to the user equipment, for example, by initiating a MO-LR.

29. The user equipment according to one of claims 1 to 12 or according to one of claims 15 to 28, wherein the user equipment is configured to generate the emergency context, such that the further information of the emergency context comprises privacy information for the emergency context or for at least one element of the emergency context.

30. The user equipment according to claim 29, wherein the user equipment is configured to generate the emergency context, such that the privacy information comprises an indication which indicates if the network is allowed to retrieve a particular element of the emergency context, and / or wherein the user equipment is configured to generate the emergency context, such that the privacy information comprises an indication which indicates if the network is allowed to retrieve a particular portion of the emergency context, and / or wherein the user equipment is configured to generate the emergency context, such that the privacy information comprises an indication which indicates if the network is allowed to retrieve the emergency context in its entirety.

31. The user equipment according to claim 29 or 30, wherein the user equipment is configured to generate the emergency context, such that the privacy information comprises an indication indicating for each PLMN of different PLMNs, which of the elements of the emergency context the PLMN is allowed to retrieve (e.g., different PLMNs may, e.g., be a home PLMN, a visited PLMN, an equivalent PLMN).

32. The user equipment according to one of claims 29 to 31 ,FH240807PEP-2025260532.DOCXwherein the user equipment is configured to generate the emergency context, such that the privacy information comprises an indication that indicates that the user of the user equipment has to indicate its approval to a transmission of the emergency context to a network entity, or wherein the user equipment is configured to generate the emergency context, such that the privacy information comprises an indication that indicates that a transmission of the emergency context to a network entity is allowed without that the user has to indicate its approval to the transmission.

33. The user equipment according to one of claims 29 to 32, wherein the user equipment is configured to generate the emergency context, such that the privacy information comprises an indication that indicates that a network entity may request a transmission of the emergency context without an indication of an approval for the transmission by the user of the user equipment.

34. The user equipment according to one of claims 29 to 33, wherein the user equipment is configured to receive a message indicating an override regarding privacy, for example, a regulatory override regarding privacy, wherein the user equipment is configured to transmit, in response to receiving the message indicating the override, the emergency context or a portion thereof irrespective of the privacy information.

35. The user equipment according to one of claims 1 to 12 or according to one of claims 15 to 34, wherein the user equipment is configured to transmit an emergency message to one or more authorities (e.g., to a local emergency response center).

36. The user equipment according to claim 35, wherein the emergency message comprises a text message and / or multimedia content.FH240807PEP-2025260532.DOCX37. The user equipment according to claim 35 or 36, wherein the emergency message comprises the emergency context.

38. The user equipment according to one of claims 1 to 12 or according to one of claims 15 to 37, wherein the user equipment is configured to obtain an indication on an emergency from a higher layer of a protocol stack of the user equipment.

39. The user equipment according to one of claims 1 to 12 or according to one of claims 15 to 38, wherein the user equipment is configured to transmit the emergency context or a portion of the emergency context or an element of the emergency context to another entity of the wireless communication system together with an identifier being associated with the emergency context.

40. The user equipment according to claim 39, wherein the user equipment is configured to transmit a first message comprising a first portion of the emergency context to said other entity of the wireless communication system, and wherein the user equipment is configured to transmit a second message comprising a second portion of the emergency context to said other entity of the wireless communication system together with the identifier being associated with the emergency context.41 . The user equipment according to claim 39 or 40, wherein the user equipment is configured to transmit a first message comprising a first version of the emergency context to said other entity of the wireless communication system, andFH240807PEP-2025260532.DOCXwherein the user equipment is configured to transmit a second message comprising a second, updated version of the emergency context to said other entity of the wireless communication system together with the identifier being associated with the emergency context.

42. The user equipment according to one of claims 39 to 41 , wherein the user equipment is configured to receive the identifier from a network entity of the wireless communication system.

43. The user equipment according to one of claims 39 to 42, wherein the user equipment is configured to generate itself the identifier which is associated with the emergency context.

44. The user equipment according to one of claims 1 to 12 or according to one of claims 15 to 43, wherein the user equipment is configured to autonomously initiate an emergency call on detecting an emergency situation, and wherein the user equipment is configured to automatically transfer its location when the user or the user equipment autonomously has initiated the emergency call.

45. The user equipment according to one of claims 1 to 12 or according to one of claims 15 to 44, wherein the user equipment is configured to generate the emergency context, such that the user-specific information of the further information of the emergency context comprises information on a health of the user of the user equipment.

46. The user equipment according to one of claims 1 to 12 or according to one of claims 15 to 45, wherein the user equipment is configured to generate the emergency context, such that the user-specific information of the further information of the emergency contextFH240807PEP-2025260532.DOCXcomprises medical information, comprising medical related information derived from information entered and / or stored by the user in the user equipment (e.g. allergies, medical conditions, additional medical information, reactions, medications, blood type etc).

47. The user equipment according to one of claims 1 to 12 or according to one of claims 15 to 46, wherein the user equipment is configured to generate the emergency context, such that the user-specific information of the further information of the emergency context comprises medical information, comprising medical related information derived from sensors in the user equipment and / or peripheral devices (e.g., smartwatch, etc.) associated to the user equipment.

48. The user equipment according to one of claims 1 to 12 or according to one of claims 15 to 47, wherein the user equipment is configured to generate the emergency context, such that the user-specific information of the further information of the emergency context comprises the indication indicating whether the user is willing to support a rescue and support operation in case of disaster scenario.

49. The user equipment according to one of claims 1 to 12 or according to one of claims 15 to 48, wherein the user equipment is configured to receive information from the user entered via an interface of the user equipment, comprising an indication indicating whether the user is willing to be a blood-donor (e.g., in case of disaster scenario), and / or wherein the user equipment is configured to receive the indication from medical records of the user that the user is willing to be a blood-donor, wherein the user equipment is configured to generate the emergency context, such that the user-specific information of the further information of the emergency context comprises the indication indicating whether the user is willing to be a blood-donor in case of disaster scenario.FH240807PEP-2025260532.DOCX50. The user equipment according to claim 49, wherein the user equipment is configured to generate the emergency context, such that the user-specific information of the further information of the emergency context comprises a blood group type of the user.

51. The user equipment according to claim 49 or 50, wherein the interface of the user equipment is configured to receive information from the user in a disaster scenario indicating the user is safe, and indicating that the user is willing to be a blood donor.

52. The user equipment according to one of claims 49 to 51 , wherein the interface of the user equipment is configured to receive information from the user overriding or pausing or resuming his willingness to support a rescue and support operation and / or to be a blood donor (e.g., because he just has contributed blood).

53. The user equipment according to one of claims 45 to 52, wherein the user equipment is configured to obtain the information on the health of the user from one or more devices, for example, smartwatches, blood sugar monitors, heartbeat monitors, connected to the user equipment, for example using interfaces such as bluetooth or using sidelink data transmission.

54. The user equipment according to one of claims 45 to 53, wherein the user equipment is configured to obtain the information on the health of the user using sensing (for example, radar like sensing), or by conducting signal processing on transmitted data and signals for communication (e.g., by conducting integrated sensing and communication).

55. The user equipment according to one of claims 45 to 54,FH240807PEP-2025260532.DOCXwherein the user equipment is configured to initiate an emergency call and / or to transmit the emergency context depending on the information of the health of the user.

56. The user equipment according to one of claims 45 to 55, wherein the user equipment is configured to transmit the information on the health of the user within the emergency context depending on privacy information, or wherein the emergency context comprises privacy information which indicates if access for another entity of the wireless communication system on the information on the health of the user within the emergency context is allowed.

57. The user equipment according to one of claims 1 to 12 or according to one of claims 15 to 56, wherein the user equipment is configured to generate the emergency context, such that the user-specific information of the further information of the emergency context comprises personal identification information, comprising identification information stored by the user in the user equipment (e.g., a passport number, an identifier associated with insurance, social security, healthcare, etc.).

58. The user equipment according to one of claims 1 to 12 or according to one of claims 15 to 57, wherein the user equipment is configured to generate the emergency context, such that the emergency context comprises information relating to one or more other users being different from the user of the user equipment.

59. The user equipment according to claim 58, wherein the user equipment is configured to receive the information on the one or more other users from one or more other entities of the wireless communication system.FH240807PEP-2025260532.DOCX60. The user equipment according to one of claims 1 to 12 or according to one of claims 15 to 59, wherein the user equipment is configured to generate the emergency context, such that the emergency context comprises information on a motion status of the user equipment, for example, if a user equipment is moving or if a user equipment is not moving.

61. The user equipment according to claim 60, wherein the user equipment is configured to generate the emergency context, such that emergency context comprises information on a motion status of the user equipment for two or more different points-in-time.

62. The user equipment according to one of claims 1 to 12 or according to one of claims 15 to 61 , wherein the user equipment is configured to generate the emergency context, such that the emergency context comprises sensor data from one or more sensors, wherein the sensor data depends on the user equipment and / or depends on the environment where the user equipment is located and / or depends on a state of the user of the user equipment.

63. The user equipment according to claim 62, wherein the user equipment is configured to generate the emergency context, such that the sensor data comprises data on an air pressure, and / or data on a sound intensity, and / or data on a movement profile, and / or data on accelerometer readings, and / or data on gyroscope readings, and / or data on barometer readings.

64. The user equipment according to one of claims 1 to 12 or according to one of claims 15 to 63, wherein the user equipment is configured to process at least one sensor reading to derive a current status of the user (e.g. falling, trapped, lying down, moving, etc.),FH240807PEP-2025260532.DOCXwherein the user equipment is configured to generate the emergency context, such that the emergency context comprises the current status of the user.

65. The user equipment according to one of claims 1 to 12 or according to one of claims15 to 64, wherein the user equipment is configured to generate the emergency context, such that the emergency context comprises an indication on a last time when the user has used the user equipment.

66. The user equipment according to one of claims 1 to 12 or according to one of claims 15 to 65, wherein the user equipment is configured to generate the emergency context, such that the emergency context comprises an indication which indicates that the user is safe, or comprises an indication which indicates that the user needs rescue, or comprises an indication which indicates that the user is injured.

67. The user equipment according to claim 66, wherein the user equipment comprises an interface which is configured to receive a user input from the user to allow the user to indicate that the user is safe, and wherein the user equipment is configured to set the indication of the emergency context that the user is safe depending on the user input.

68. The user equipment according to one of claims 1 to 12 or according to one of claims 15 to 67, wherein the user equipment is configured to generate the emergency context, such that the emergency context comprises an indication indicating that the user has abandoned the user equipment.

69. The user equipment according to claim 68,FH240807PEP-2025260532.DOCXwherein the user equipment is configured to make a determination that the user has abandoned the user equipment by analyzing an RSRP and / or an RTT between a peripheral device (e.g., a smartwatch) and the user equipment, and wherein the user equipment is configured to set the indication of the emergency context that the user has abandoned the user equipment depending on the determination.

70. The user equipment according to one of claims 1 to 12 or according to one of claims 15 to 69, wherein the user equipment is configured to transmit information one or more elements of the emergency context to a user contact in an emergency situation.

71. The user equipment according to claim 70, wherein the user equipment is configured to transmit information that the user is safe or that the user is injured or that the user needs rescue as the information one or more elements of the emergency context to the user contact.

72. The user equipment according to claim 71 , wherein the user equipment is configured to inform the user of the user equipment that the information that the user is safe or that the user is injured or that the user needs rescue has been transmitted to the user contact (e.g., to avoid the need that the user himself contacts the user contact, so that the transmission load on the network, e.g., due to phone calls, is reduced in case of an emergency situation).

73. The user equipment according to one of claims 70 to 72, wherein the information on the one or more elements of the emergency context that is transmitted to the user contact in the emergency situation depends on a privacy profile.

74. The user equipment according to one of claims 70 to 73,FH240807PEP-2025260532.DOCXwherein the user equipment is configured to generate the emergency context, such that the emergency context comprises information on the user contact.

75. The user equipment according to one of claims 1 to 12 or according to one of claims 15 to 74, wherein the user equipment is configured to transmit information on a battery power of the user equipment to another entity of the wireless communication system in an emergency situation.

76. The user equipment according to claim 75, wherein the user equipment is configured to generate the emergency context, such that the emergency context comprises information on the battery power of the user equipment.

77. The user equipment according to one of claims 1 to 12 or according to one of claims 15 to 76, wherein the user equipment is configured to generate and / or send an emergency message, if a battery power getw below a certain limit.

78. The user equipment according to one of claims 1 to 12 or according to one of claims 15 to 77, wherein the user equipment is configured to generate and / or send the emergency context, if the user equipment detects an emergency.

79. The user equipment according to one of claims 1 to 12 or according to one of claims 15 to 78, wherein the user equipment is configured to transmit the emergency context to another device of the wireless communication system, and wherein the user equipment is configured to transmit information that the user equipment has transmitted the emergency context to said other device to a network entity of the wirelss communication system.FH240807PEP-2025260532.DOCX80. The user equipment according to claim 79, wherein said other device is a passive loT device or an ambient loT device or an active loT device.

81. The user equipment according to one of claims 1 to 12 or according to one of claims 15 to 80, wherein the user equipment is configured to generate the emergency context, such that the emergency context comprises information on a status of one or more other users, which are different from the user of the user equipment.

82. The user equipment according to one of claims 1 to 12 or according to one of claims 15 to 81 , wherein the user equipment is configured to generate the emergency context, such that the emergency context is associated with an emergency PIN and / or with an emergency password which allows to update the emergency context from a different device.

83. The user equipment according to one of claims 1 to 12 or according to one of claims 15 to 82, wherein the user equipment is configured to generate the emergency context, such that the emergency context comprises information on a structural integrity of an environment, where the user equipment is located.

84. The user equipment according to claim 83, wherein the user equipment is configured to employ a camera and / or radar-like sensing to obtain the information on the structural integrity of the environment, where the user equipment is located.

85. The user equipment according to one of claims 1 to 12 or according to one of claims 15 to 84,FH240807PEP-2025260532.DOCXwherein the user equipment is configured to generate the emergency context, such that the emergency context comprises multimedia content.

86. The user equipment according to claim 85, wherein the user equipment is configured to record and / or transmit the multimedia content to another entity of the wireless communication system in an emergency situation.

87. The user equipment according to claim 86, wherein the user equipment is configured to record and / or transmit the multimedia content to said other entity of the wireless communication system in response to an emergency warning received by the user equipment and / or in response to that the user equipment detects the emergency situation.

88. The user equipment according to claim 87, wherein the user equipment is configured to detect the emergency situation when detecting a shaking characteristic of an earthquake.

89. The user equipment according to one of claims 86 to 88, wherein the user equipment is configured to delete the multimedia content when receiving information that the user of the user equipment is safe.

90. The user equipment according to one of claims 1 to 12 or according to one of claims 15 to 89, wherein the user equipment is configured to determine routing information via one or more other user equipments to transmit the emergency context to the network via the one or more other user equipments in case of an emergency situation, when one or more base stations are no longer available.

91. The user equipment according to claim 90,FH240807PEP-2025260532.DOCXwherein the user equipment is configured to transmit the emergency context via a transmission route identified by the routing information in case of an emergency situation, when the one or more base stations are no longer available.

92. The user equipment according to claim 90 or 91 , wherein the user equipment is configured to generate the emergency context, such that the emergency context comprises the routing information.

93. The user equipment according to one of claims 1 to 12 or according to one of claims 15 to 92, wherein the user equipment is configured to generate the emergency context, such that the emergency context comprises personalization information which allows or simplifies a communication of an emergency service with the user.

94. The user equipment according to claim 93, wherein the user equipment is configured to generate the emergency context, such that the personalization information comprises a preferred language of the user.

95. The user equipment according to one of claims 1 to 12 or according to one of claims 15 to 94, wherein the user equipment is configured to generate an automatic translation (e.g., a machine4earning translation) to simplify communication with the user in an emergency situation.

96. The user equipment according to one of claims 1 to 12 or according to one of claims 15 to 95, wherein the user equipment is configured to employ an artificial intelligence / machine learning concept to determine, using sensor data and / or using internal data of the user equipment, a medical state of the user, and / or a motion of the user, and / or a structural integrity of an environment where the user equipment is located.FH240807PEP-2025260532.DOCX97. The user equipment according to one of claims 1 to 12 or according to one of claims 15 to 96, wherein the user equipment is configured to transmit the emergency context automatically in case of an emergency without interaction with the user.

98. The user equipment according to one of claims 1 to 12 or according to one of claims 15 to 96, wherein the user equipment is configured to transmit the emergency context only after an interaction with the user in which the user approves the transmission of the emergency context.

99. The user equipment according to one of claims 1 to 12 or according to one of claims 15 to 96, wherein the user equipment is configured to transmit the emergency context to another entity of the wireless communication system irrespective of whether or not an emergency situation is present at the user equipment to make the emergency context available at said other entity if an emergency situation should occur at the user equipment.

100. The user equipment according to one of claims 1 to 12 or according to one of claims 15 to 96, wherein the user equipment is configured to transmit the emergency context to another entity of the wireless communication system in response to a request from said other entity or from a further entity of the wireless communication network.101 . The user equipment according to one of claims 1 to 12 or according to one of claims 15 to 100, wherein the user equipment is configured to encrypt the emergency context to obtain an encrypted version of the emergency context, andFH240807PEP-2025260532.DOCXwherein the user equipment is configured to transmit the encrypted version of the emergency context to another entity of the wireless communication system.

102. The user equipment according to claim 101 , wherein the user equipment is configured to use a public key of a PSAP (public safety answering point) or a local emergency response center (LERC) or key from national authorities to encrypt the emergency context.

103. The user equipment according to claim 101 or 102, wherein the user equipment is configured to transmit a message comprising the encrypted version of the emergency context and an unencryped indication indicating that the message relates comprises emergency information.

104. The user equipment according to one of claims 1 to 12 or according to one of claims 15 to 103, wherein the emergency message is encapsulated within several layers of protocols, enabling the different network entities (e.g. one or more RAN nodes) or core nodes (e.g. an AMF or an SMS gateway) to prioritise and / or to route emergency messages, whereas the sensitive content is only decodable by the PSAP.

105. The user equipment according to one of claims 1 to 12 or according to one of claims 15 to 103, wherein the content of the emergency message is processed at a network node to determine the information in emergency message and to initiate one or more subsequent actions, for example, trigger appropriate emergency services and / or create a report and / or forward the report to one or more PSAPs.

106. The user equipment according to one of claims 1 to 12 or according to one of claims 15 to 105,FH240807PEP-2025260532.DOCXwherein the user equipment is configured to update the emergency context periodically or on demand from another entity of the wireless communication network.

107. The user equipment according to claim 106, wherein the user equipment is configured to transmit the emergency context to said other entity of the wireless communication system after the update.

108. The user equipment according to claim 106 or 107, wherein the user equipment is configured to transmit only those elements of the emergency context to said other entity of the wireless communication system that have been updated.

109. The user equipment according to one of claims 1 to 12 or according to one of claims 15 to 108, wherein the user equipment is configured to receive an indication of an emergency, and wherein the user equipment is configured to generate the emergency context after receiving the indication of the emergency.

110. The user equipment according to one of claims 1 to 12 or according to one of claims 15 to 108, wherein the user equipment is configured to receive an indication of an emergency via one or more system information messages (e.g. cell-wide or area-wide bropadcast or on-demand SIB request) or via unicast signaling to the user equipment (e.g., NAS, LPP, RRC, SIP signaling, SLPP).

111. The user equipment according to claim 109 or 110,FH240807PEP-2025260532.DOCXwherein the user equipment is configured its capabilities to the network, wherein the capabilities indicate which element of the emergency context, the user equipment is capable to generate and / or is allowed to provide to the network.

112. The user equipment according to one of claims 109 to 111 , wherein the user equipment is configured to receive an information from the network via one or more system information messages (e.g., at least one SIB) or via dedicated signalling, wherein the information indicates that the network supports receiving the emergency context from the user equipment and / or wherein the information indicates which information should the user equipment prepare within the emergency context and / or wherein the information indicates an update and / or transfer frequency of the emergency context.

113. The user equipment according to claim 112, wherein the information is different for two or more different PLMNs supported by the cell.

114. The user equipment according to one of claims 109 to 113, wherein the user equipment is configured to generate and / or transmit different emergency contexts when attached to different PLMNs, e.g., in case of an NTN cell.

115. The user equipment according to one of claims 1 to 12 or according to one of claims 15 to 114, wherein the user equipment is configured to generate the emergency context and / or to transmit a certain portion of the emergency context depending on a type of an indication received.

116. The user equipment according to claim 115, wherein the user equipment is configured to generate the emergency context and / or to transmit a certain portion of the emergency context depends on whether the type of the indication received is an earthquake warning, and / or depends on whether theFH240807PEP-2025260532.DOCXtype of the indication received is a natural disaster warning (e.g., a tsunami warning, or a flood warning), and / or depends on whether the type of the indication received is a warning on an attack on an infrastructure, and / or depends on whether the type of the indication received is a warning on a missile attack, and / or depends on whether the type of the indication received is a warning on a terrorism act, and / or depends on whether the type of the indication received is a warning on an abduction, and / or depends on whether the type of the indication received is a warning on another emergency.

117. The user equipment according to one of claims 1 to 12 or according to one of claims 15 to 116, wherein the user equipment is configured to transmit a first message comprising a first portion of the emergency context via a first network, and wherein the user equipment is configured to transmit a second message comprising a second portion of the emergency context via a second network being different from the first network, if a transmission of the second message via the first network is not possible and / or if the first network is congested.

118. The user equipment according to one of claims 1 to 12 or according to one of claims 15 to 117, wherein the user equipment is configured to receive information from a first network, which triggers a generation and / or a transmission of the emergency context by the user equipment, and wherein the user equipment is configured to transmit the emergency context via a second network being different from the first network.

119. The user equipment according to claim 118, wherein the first network is a terrestrial network and wherein the second network is a wireless network, orFH240807PEP-2025260532.DOCXwherein the first network is a wireless network and wherein the second network is a terrestrial network, or wherein the first network is a terrestrial wireless network and wherein the second network is a non-terrestrial network (e.g. satellite).

120. The user equipment according to claim 118 or 119, wherein the user equipment is configured to detect that the first network is unavailable or is congested (e.g., an earthquake and / or a flooding has destroyed the functionality of the first, e.g., terrestrial, network), and wherein the user equipment is configured to decide to transmit the emergency context via the second network if the user equipment has detected that the first network is unavailable or is congested.121 . The user equipment according to one of claims 1 to 12 or according to one of claims 15 to 120, wherein the user equipment is configured to transmit the emergency context end-to- end between to a server (e.g. a PSAP server), for example, by a user plane data transmission.

122. The user equipment according to claim 121 , wherein the user equipment is configured to transmit an identifier to map information transmitted via a user plane with an emergency call or with an identifier associated with the user equipment.

123. The user equipment according to one of claims 1 to 12 or according to one of claims 15 to 122, wherein the user equipment is configured to determine a location using a configuration of downlink reference signals preconfigured to the user equipment, wherein the user equipment is configured to receive an indication indicating to use reference signals in an emergency notification or warning system (for example, aFH240807PEP-2025260532.DOCXcorresponding network entity begins transmitting such signals latest when the emergency notification takes place).

124. The user equipment according to one of claims 1 to 12 or according to one of claims 15 to 123, wherein the user equipment is configured to transmit one or more uplink reference signals preconfigured to the user equipment, wherein the user equipment is configured to receive an indication to use such reference signals, in an emergency notification or warning system within a certain area (e.g. list of cells) (for example, the corresponding network entity begins processing such signals latest when the emergency notification takes place).

125. The user equipment according to one of claims 1 to 12 or according to one of claims 15 to 124, wherein the user equipment is configured to save one or more measurements (e.g. CIR) and / or multimedia content, on receiving an alert (for example, when receiving an impending earthquake notification), and wherein the user equipment is configured to clear the one or more measurements and / or the multimedia content on receiving an all clear notification and / or when receiving an indication indicating the safe status on the user equipment.

126. The user equipment according to claim 125, wherein the user equipment is configured to receive a request from the network to provide the one or more measurements and / or the multimedia content, if a safe status has not been transmitted to the network.

127. An entity of a wireless communication system, wherein the entity of the wireless communication system is configured for: receiving an emergency context of a user equipment of the wireless communication system for having the emergency context in case of an emergency situation available at the entity of the wireless communication system, wherein said entity of the wireless communication system is different from said user equipment, whereinFH240807PEP-2025260532.DOCXthe emergency context of the user equipment comprises first information and further information, wherein the first information of the emergency context comprises at least one of: an information to distinguish an emergency SMS from a standard SMS, a location of the user equipment, a time when the location of the user equipment has been determined, an actual time of the user equipment, an actual date of the user equipment, wherein the further information of the emergency context comprises at least one of: user-specific information comprising information on a user or a state of the user of the user equipment, device-specific information comprising information on the user equipment, environment-specific information comprising information on an environment in which the user equipment is located, privacy information comprising privacy settings that shall apply in case of an emergency emergency transmission information comprising information for transmitting data in an emergency situation, an emergency message, wherein the further information of the emergency context is different from the location of the user equipment, and is different from the time when the location of the user equipment has been determined, and is different from the actual time and the actual date of the user equipment.

128. The entity according to claim 127, wherein the entity is a network node of the wireless communication system.

129. The entity according to claim 127, wherein the entity is another user equipment of the wireless communication system.FH240807PEP-2025260532.DOCX130. The entity according to one of claims 127 to 129, wherein the entity is configured to process the emergency context of the user equipment in case of an emergency situation.

131. The entity according to one of claims 127 to 130, wherein the entity is configured to transmit the emergency context to another entity of the wireless communication system for making the emergency context in case of an emergency situation available at the other entity of the wireless communication system.

132. The entity according to one of claims 127 to 131 , wherein the emergency context comprises a timestamp, which indicates when the emergency context was last created or modified, and / or wherein the emergency context comprises a timestamp, which indicates when at least one element of the emergency context was last created or modified.

133. The entity according to one of claims 127 to 132, wherein the user-specific information of the further information of the emergency context comprises a status indication which indicates that the user of the user equipment is safe, or comprises a status indication which indicates that the user needs rescue, or comprises a status indication which indicates that the user is injured.

134. The entity according to claim 133, wherein the emergency context comprises a timestamp indicating a time when the status indication has been created.

135. The entity according to claim 132 or 134,FH240807PEP-2025260532.DOCXwherein the emergency context comprises information on a source of a time information comprised by the emergency context and / or on a reliability of the time information comprised by the emergency context, for example, by indicating that the time information has been obtained using an NTP time from an NTP server, or using a GNSS, or using an internal user equipment time and date.

136. The entity according to one of claims 127 to 135, wherein the entity is configured to receive the emergency context by receiving a first portion of the emergency context in a first message and by receiving one or more further portions of the emergency context in one or more further messages.

137. The entity according to one of claims 127 to 136, wherein the entity is configured to receive the emergency context within a single message.

138. The entity according to one of claims 127 to 137, wherein the emergency situation is an emergency situation at the user equipment.

139. The entity according to one of claims 127 to 138, wherein the emergency context comprises information on two or more locations of the user equipment at two or more different points-in-time.

140. The entity according to claim 139, wherein the emergency context comprises time information for each location of the two or more locations of the user equipment, which indicates for said location at which point-in-time the user equipment has been located at said location.

141. The entity according to one of claims 127 to 140, wherein the first information of the emergency context comprises the location of the user equipment.FH240807PEP-2025260532.DOCX142. The entity according to one of claims 127 to 141 , wherein the first information of the emergency context comprises the location of the user equipment.

143. The entity according to one of claims 127 to 142, wherein the further information of the emergency context comprises privacy information for the emergency context or for at least one element of the emergency context.

144. The entity according to claim 143, wherein the privacy information comprises an indication which indicates if the network is allowed to retrieve a particular element of the emergency context, and / or wherein the privacy information comprises an indication which indicates if the network is allowed to retrieve a particular portion of the emergency context, and / or wherein the privacy information comprises an indication which indicates if the network is allowed to retrieve the emergency context in its entirety.

145. The entity according claim 143 or 144, wherein the privacy information comprises an indication indicating for each PLMN of different PLMNs, which of the elements of the emergency context the PLMN is allowed to retrieve (e.g., different PLMNs may, e.g., be a home PLMN, a visited PLMN, an equivalent PLMN).

146. The entity according to one of claims 133 to 145, wherein the privacy information comprises an indication that indicates that the user of the user equipment has to indicate its approval to a transmission of the emergency context to a network entity, orFH240807PEP-2025260532.DOCXwherein the privacy information comprises an indication that indicates that a transmission of the emergency context to a network entity is allowed without that the user has to indicate its approval to the transmission.

147. The entity according to one of claims 143 to 146, wherein the privacy information comprises an indication that indicates that a network entity may request a transmission of the emergency context without an indication of an approval for the transmission by the user of the user equipment.

148. The entity according to one of claims 127 to 147, wherein the entity is configured to receive an emergency message from the user equipment, wherein the entity is configured to transmit the emergency message to one or more authorities (e.g., to a local emergency response center).

149. The entity according to claim 148, wherein the emergency message comprises a text message and / or multimedia content.

150. The entity according to claim 148 or 149, wherein the emergency message comprises the emergency context.

151. The entity according to one of claims 127 to 150, wherein the entity is configured to provide an indication on an emergency to the user equipment via a higher layer of a protocol stack of the entity.

152. The entity according to one of claims 127 to 151 ,FH240807PEP-2025260532.DOCXwherein the entity is configured to receive the emergency context or a portion of the emergency context or an element of the emergency context from the user equipment together with an identifier being associated with the emergency context.

153. The entity equipment according to claim 152, wherein the entity is configured to receive a first message comprising a first portion of the emergency context from the user equipment, and wherein the entity is configured to receive a second message comprising a second portion of the emergency context from the user equipment together with the identifier being associated with the emergency context.

154. The entity equipment according to claim 152 or 153, wherein the entity is configured to receive a first message comprising a first version of the emergency context from the user equipment, and wherein the entity is configured to receive a second message comprising a second, updated version of the emergency context from the user equipment together with the identifier being associated with the emergency context.

155. The entity according to one of claims 152 to 154, wherein the entity is configured to transmit the identifier to the user equipment.

156. The entity according to one of claims 127 to 155, wherein the user-specific information of the further information of the emergency context comprises information on a health of the user of the user equipment.

157. The entity according to one of claims 127 to 156, wherein the user-specific information of the further information of the emergency context comprises medical information, comprising medical related information derived from information entered and / or stored by the user in the user equipmentFH240807PEP-2025260532.DOCX(e.g. allergies, medical conditions, additional medical information, reactions, medications, blood type etc).

158. The entity according to one of claims 127 to 157, wherein the user-specific information of the further information of the emergency context comprises medical information, comprising medical related information derived from sensors in the user equipment and / or peripheral devices (e.g., smartwatch, etc.) associated to the user equipment.

159. The entity according to one of claims 127 to 158, wherein the user-specific information of the further information of the emergency context comprises an indication indicating whether the user is willing to support a rescue and support operation.

160. The entity according to one of claims 127 to 159, wherein the user-specific information of the further information of the emergency context comprises an indication indicating whether the user is willing to be a blooddonor in case of disaster scenario.

161. The entity according to claim 160, wherein the user-specific information of the further information of the emergency context comprises a blood group type of the user.

162. The entity according to claim 160 or 161 , wherein the user-specific information of the further information of the emergency context comprises information from the user in a disaster scenario indicating the user is safe, and indicating that the user is willing to be a blood donor.

163. The entity according to one of claims 160 to 162,FH240807PEP-2025260532.DOCXwherein the user-specific information of the further information of the emergency context comprises information from the user the user overriding or pausing or resuming his willingness to support a rescue and support operation and / or to be a blood donor (e.g., because he just has contributed blood).

164. The entity according to one of claims 156 to 163, wherein the information on the health of the user originates from one or more devices, for example, smartwatches, blood sugar monitors, heartbeat monitors, connected to the user equipment, for example using interfaces such as bluetooth or using sidelink data transmission.

165. The entity according to one of claims 156 to 164, wherein the emergency context comprises privacy information which indicates if access for another entity of the wireless communication system on the information on the health of the user within the emergency context is allowed.

166. The entity according to one of claims 156 to 165, wherein the user-specific information of the further information of the emergency context comprises personal identification information, comprising identification information stored by the user in the user equipment (e.g., a passport number, an identifier associated with insurance, social security, healthcare, etc.).

167. The entity according to one of claims 156 to 166, wherein the emergency context comprises information relating to one or more other users being different from the user of the user equipment.

168. The entity according to one of claims 127 to 167, wherein the emergency context comprises information on a motion status of the user equipment, for example, if a user equipment is moving or if a user equipment is not moving.FH240807PEP-2025260532.DOCX169. The entity according to claim 168, wherein emergency context comprises information on a motion status of the user equipment for two or more different points-in-time.

170. The entity according to one of claims 127 to 169, wherein the emergency context comprises sensor data from one or more sensors, wherein the sensor data depends on the user equipment and / or depends on the environment where the user equipment is located and / or depends on a state of the user of the user equipment.

171. The entity according to claim 170, wherein the sensor data comprises data on an air pressure, and / or data on a sound intensity, and / or data on a movement profile, and / or data on accelerometer readings, and / or data on gyroscope readings, and / or data on barometer readings.

172. The entity according to one of claims 127 to 171 , wherein the emergency context comprises a current status of the user (e.g. falling, trapped, lying down, moving, etc.).

173. The entity according to one of claims 127 to 172, wherein the emergency context comprises an indication on a last time when the user has used the user equipment.

174. The entity according to one of claims 127 to 173, wherein the emergency context comprises an indication which indicates that the user is safe, or comprises an indication which indicates that the user needs rescue, or comprises an indication which indicates that the user is injured.

175. The entity according to one of claims 127 to 174,FH240807PEP-2025260532.DOCXwherein the emergency context comprises an indication indicating that the user has abandoned the user equipment.

176. The entity according to one of claims 127 to 175, wherein the emergency context comprises information on a user contact.

177. The entity according to claim 176, wherein the emergency context comprises information on a battery power of the user equipment.

178. The entity according to one of claims 127 to 177, wherein the entity is a passive loT device or an ambient loT device or an active loT device.

179. The entity according to one of claims 127 to 178, wherein the emergency context comprises information on a status of one or more other users, which are different from the user of the user equipment.

180. The entity according to one of claims 127 to 179, wherein the emergency context is associated with an emergency PIN and / or with an emergency password which allows to update the emergency context from a different device.

181. The entity according to one of claims 127 to 180, wherein the emergency context comprises information on a structural integrity of an environment, where the user equipment is located.

182. The entity according to one of claims 127 to 181 , wherein the emergency context comprises multimedia content.FH240807PEP-2025260532.DOCX183. The entity according to one of claims 127 to 182, wherein the emergency context comprises the routing information for a transmission from the user equipment to the entity via one or more other user equipments.

184. The entity according to one of claims 127 to 183, wherein the emergency context comprises personalization information which allows or simplifies a communication of an emergency service with the user.

185. The entity according to claim 184, wherein the personalization information comprises a preferred language of the user.

186. The entity according to one of claims 127 to 185, wherein the entity is configured to transmit a request for a transmission of the emergency context to the user equipment.

187. The entity according to one of claims 127 to 186, wherein the entity is configured to receive an encrypted version of the emergency context from the user equipment.

188. The entity according to claim 187, wherein the emergency context is encrypted with a public key of a PSAP or of a local emergency response center (LERC) or key from state authorities to encrypt the emergency context.

189. The entity according to claim 188, wherein the entity is not located at the PSAP and is not located at the LERC and is not located at the other state authority, andFH240807PEP-2025260532.DOCXwherein the entity is configured to transmit the emergency context in its encrypted version to the PSAP or to the LERC or to another state authority.

190. The entity according to claim 188, wherein the entity is located at the PSAP or is located at the LERC or is located at another state authority, and wherein the entity is configured to decrypt the emergency context using a private key of the PSAP or of the LERC or of the other state authority.

191. The entity according to one of claims 127 to 190, wherein the user equipment updates the emergency context periodically or on demand from the entity, wherein the entity is configured to receive the emergency context from the user equipment after the update.

192. The entity according to claim 191 , wherein the entity is configured to receive only those elements of the emergency context from the user equipment that have been updated.

193. The entity according to one of claims 127 to 192, wherein the entity is configured to transmit an indication of an emergency to the user equipment, and wherein the entity is configured to receive the emergency from the user equipmentcontext after transmitting the indication of the emergency.

194. The entity according to one of claims 127 to 193, wherein the entity implements one or more of the following:FH240807PEP-2025260532.DOCXa CSCF (Call session control function) an emergency-CSCF (Emergency call-session control function) an emergency call server an IMS (IP Multimedia subsystem) an LRF (Location retrieval function) an location server (e.g. LMF, GMLC, MPC, SLP) a PSAP (Public service answering point) a routing determination function (RDF) an AMF (Access and mobility function) a SMSF (SMS function) a UDR (Unified data repository) a UDM (Unified data management) a SMF (Session management function) a NEF (network exposure function) a RAN node (e.g. gNB, ng-eNB, BS, TRP , etc ) a NWDAF: Network data analytics function a Media Gateway control function (MGCF).

195. The entity according to one of claims 127 to 193, wherein the entity is configured to transmit the emergency context to a third entity of the wireless communication system, wherein the third entity implements one or more of the following: a CSCF (Call session control function) an emergency-CSCF (Emergency call-session control function) an emergency call server an IMS (IP Multimedia subsystem) an LRF (Location retrieval function) an location server (e.g. LMF, GMLC, MPC, SLP) a PSAP (Public service answering point) a routing determination function (RDF) an AMF (Access and mobility function) a SMSF (SMS function) a UDR (Unified data repository) a UDM (Unified data management) a SMF (Session management function)FH240807PEP-2025260532.DOCXa NEF (network exposure function) a RAN node (e.g. gNB, ng-eNB, BS, TRP , etc ) a NWDAF: Network data analytics function a Media Gateway control function (MGCF).

196. A wireless communication system, wherein the wireless communication system comprises: a user equipment according to one of claims 1 to 126, and an entity of the wireless communication system according to one of claims 127 to 195, wherein the user equipment is configured for generate an emergency context for the user equipment, such that the emergency context comprises first information and further information, wherein the user equipment is configured for transmitting the emergency context to said entity of the wireless communication system for making the emergency context in case of an emergency situation available at said entity of the wireless communication system, wherein said entity of the wireless communication system is configured to receive the emergency context from the user equipment.

197. A wireless communication system according to claim 196, wherein said entity is configured to process the emergency context of the user equipment in case of an emergency situation.

198. A wireless communication system according to claim 196 or 197, wherein said entity is a second entity of the wireless communication system, wherein the wireless communication system comprises a third entity,FH240807PEP-2025260532.DOCXwherein the second entity is configured to transmit the emergency context to the third entity, wherein the third entity is configured to process the emergency context of the user equipment in case of an emergency situation.

199. A method for a wireless communication system, wherein the method comprises: generating, by a user equipment of the wireless communication system, an emergency context for the user equipment, such that the emergency context comprises first information and further information, and transmitting, by the user equipment, the emergency context to another entity of the wireless communication system for making the emergency context in case of an emergency situation available at the other entity of the wireless communication system, wherein the first information of the emergency context comprises at least one of: an information to distinguish an emergency SMS from a standard SMS, a location of the user equipment, a time when the location of the user equipment has been determined, an actual time of the user equipment, an actual date of the user equipment, wherein the further information of the emergency context comprises at least one of: user-specific information comprising information on a user or a state of the user of the user equipment, device-specific information comprising information on the user equipment, environment-specific information comprising information on an environment in which the user equipment is located, privacy information comprising privacy settings that shall apply in case of an emergency emergency transmission information comprising information for transmitting data in an emergency situation,FH240807PEP-2025260532.DOCXan emergency message, wherein the further information of the emergency context is different from the location of the user equipment, and is different from the time when the location of the user equipment has been determined, and is different from the actual time and the actual date of the user equipment.

200. A method for a wireless communication system, wherein the method comprises receiving, by a user equipment, an emergency message from a PSAP or from a network entity, which may be sent in response to emergency detected by the network; and / or in response to information provided by a third party (e.g., trusted third party - like national organization monitoring emergency events - like meterological and / or seismological organisations); and / or in response to emergency call or sms initiated by the user equipment.201 . A method for a wireless communication system, wherein the method comprises: receiving, by an entity of the wireless communication system, an emergency context of a user equipment of the wireless communication system for having the emergency context in case of an emergency situation available at the entity of the wireless communication system, wherein said entity of the wireless communication system is different from said user equipment, wherein the emergency context of the user equipment comprises first information and further information, wherein the first information of the emergency context comprises at least one of: an information to distinguish an emergency SMS from a standard SMS, a location of the user equipment, a time when the location of the user equipment has been determined, an actual time of the user equipment, an actual date of the user equipment,FH240807PEP-2025260532.DOCXwherein the further information of the emergency context comprises at least one of: user-specific information comprising information on a user or a state of the user of the user equipment, device-specific information comprising information on the user equipment, environment-specific information comprising information on an environment in which the user equipment is located, privacy information comprising privacy settings that shall apply in case of an emergency emergency transmission information comprising information for transmitting data in an emergency situation, an emergency message, wherein the further information of the emergency context is different from the location of the user equipment, and is different from the time when the location of the user equipment has been determined, and is different from the actual time and the actual date of the user equipment.

202. A computer program for implementing the method according to one of claims 199 to 201 , when the method is being carried out by a computer program or signal processor.FH240807PEP-2025260532.DOCX

Images