Method of communication device, method of user equipment (UE), communication device, and UE

Abstract

Aspects of the present disclosure include a method of a communications device. The method includes sending a message. The message includes a request to send information. The information includes at least one of an identifier of a user equipment (UE(3)), location information where the UE(3) is located, video information around the UE(3), photo information around the UE(3), audio information around the UE(3), temperature information around the UE(3), vital information of a user of the UE(3), and contact information of the UE(3). The method includes receiving the information after sending the message.

Description

[Technical field]

[0001] The present disclosure relates to a communication device method, a user equipment (UE) method, a communication device, and a UE. [Background technology]

[0002] Lifesaving in disasters is an important issue to protect people's lives. In general, it is difficult to predict when a disaster will occur and what kind of disaster will occur, so the task is difficult. Mobile communication systems can be useful to support lifesaving activities after a disaster. Paging of UEs and broadcasting of messages to UEs are equipped as basic functions in mobile communication systems. [Prior art documents] [Non-patent literature]

[0003] [Non-Patent Document 1] 3GPP TR 21.905:”Vocabulary for 3GPP Specifications”.V17.1.0(2021-12) [Non-Patent Document 2] 3GPP TS 23.041:”Technical realization of Cell Broadcast Service(CBS)”.V17.2.0(2021-09) [Non-Patent Document 3] 3GPP TS 24.526:”IP Multimedia Subsystem(IMS)emergency sessions”.V17.2.0(2021-09) [Non-Patent Document 4] IETF RFC 5580:”Carrying Location Objects in RADIUS and Diameter”.(2009-08) [Non-Patent Document 5] 3GPP TS 38.331: "NR;Radio Resource Control (RRC) protocol specification".V16.7.0(2021-12)

Non-licensed Document 6

Non-licensed Document 7

Non-licensed literature 9

Non-licensed literature 10

Non-licensed Document 11

Non-licensed Document 12

Non-licensed Document 13

[0004] When disasters such as earthquakes, tsunamis, or volcanic eruptions occur, it can be very difficult to rescue people in the disaster area because they may be in serious condition, may not be able to make emergency calls, or their mobile phones (or user equipment) may be down because base stations may be damaged by the disaster.

[0005] In addition, rescuers are needed not only in disaster situations, but also in other emergency situations. For example, rescuers may need to assist with an unconscious person after a fall while climbing, a lost child, or a restrained situation. Even if a rescuer knows they need to rescue a person and call the person, the rescuer may not be able to determine the person's exact location in the emergency, for example, because the person is unable to answer the phone or provide sufficient information. [Means for solving the problem]

[0006] In a first exemplary aspect, a communications device method includes sending a message, where the message includes a request to send information, the information including at least one of an identifier of a user equipment (UE), location information where the UE is located, video information about the surroundings of the UE, photo information about the surroundings of the UE, audio information about the surroundings of the UE, temperature information about the surroundings of the UE, vital information of a user of the UE, and contact information for the UE, and receiving the information after sending the message.

[0007] In a second exemplary aspect, a method for a user equipment (UE) includes receiving a message, where the message includes a request to transmit information, where the information includes at least one of an identifier of the UE, location information where the UE is located, video information about the surroundings of the UE, photo information about the surroundings of the UE, audio information about the surroundings of the UE, temperature information about the surroundings of the UE, vital information of a user of the UE, and contact information of the UE, and transmitting the information after receiving the message.

[0008] In a third exemplary aspect, a communications device includes means for sending a message, where the message includes a request to send information, and the information includes at least one of an identifier of a user equipment (UE), location information where the UE is located, video information about the surroundings of the UE, photo information about the surroundings of the UE, audio information about the surroundings of the UE, temperature information about the surroundings of the UE, vital information of a user of the UE, and contact information of the UE, and means for receiving the information after sending the message.

[0009] In a fourth exemplary aspect, a user equipment (UE) includes means for receiving a message, where the message includes a request to transmit information, and the information includes at least one of an identifier of the UE, location information where the UE is located, video information about the UE's surroundings, photo information about the UE's surroundings, audio information about the UE's surroundings, temperature information about the UE's surroundings, vital information of a user of the UE, and contact information of the UE, and means for transmitting the information after receiving the message. Effect of the Invention

[0010] According to the present disclosure, a communication device method, a user equipment (UE) method, a communication device, and a UE can be provided. [Brief description of the drawings]

[0011] [Figure 1] FIG. 1 is a diagram illustrating an example of a target period for lifesaving after a disaster. [Diagram 2] FIG. 13 is a diagram illustrating another example of a target period for lifesaving after a disaster. [Diagram 3] 1 is a flowchart showing an example of a processing procedure in a first aspect. [Figure 4] FIG. 11 is a signaling diagram of a second example of the first embodiment. [Diagram 5] FIG. 11 is a signaling diagram of a variant of the second example of the first embodiment. [Figure 6] FIG. 11 is a signaling diagram of a third example of the first embodiment. [Figure 7] FIG. 11 is a signaling diagram of a first example of the second embodiment. [Figure 8] FIG. 11 is a signaling diagram of a second example of the second embodiment. [Figure 9] FIG. 11 is a signaling diagram of a third example of the second embodiment. [Figure 10] FIG. 11 is a signaling diagram of a first example of the third embodiment. [Figure 11] FIG. 11 is a signaling diagram of a second example of the third embodiment. [Figure 12] FIG. 11 is a signaling diagram of a third example of the third embodiment. [Figure 13] 1 shows a schematic diagram of a system to which the present invention can be applied; [Figure 14] FIG. 2 is a block diagram showing a UE. [Figure 15] FIG. 1 is a block diagram illustrating an (R)AN node. [Figure 16] FIG. 1 illustrates a system overview of an (R)AN node based on the O-RAN architecture. [Figure 17] FIG. 2 is a block diagram showing an RU. [Figure 18]FIG. 2 is a block diagram showing a DU. [Figure 19] FIG. 2 is a block diagram showing a CU. [Figure 20] FIG. 2 is a block diagram showing AMF. [Figure 21] FIG. 2 is a block diagram showing an SMF. [Figure 22] FIG. 2 is a block diagram showing a UPF. [Figure 23] FIG. 2 is a block diagram showing a PCF. [Figure 24] FIG. 2 is a block diagram showing an AUSF. [Diagram 25] FIG. 2 is a block diagram showing a UDM. [Figure 26] 1 is a block diagram illustrating NWDAF. [Figure 27] FIG. 2 is a block diagram showing an NEF. [Figure 28] FIG. 2 is a block diagram showing the NSACF. [Figure 29] FIG. 2 is a block diagram illustrating an IMS. [Diagram 30] FIG. 2 is a block diagram showing a PSAP. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0012] (abbreviation) For the purposes of this document, 3GPP TR 21.905 (Non-Patent Document 1) and the abbreviations given below apply. An abbreviation defined in this document takes precedence over the definition of the same abbreviation in 3GPP TR 21.905 (Non-Patent Document 1), if any. 4G-GUTI 4G Global Unique Temporary UE Identity 5GC 5G Core Network 5GLAN 5G Local Area Network 5GS 5G System 5G-AN 5G Access Network 5G-AN PDB 5G Access Network Packet Delay Budget 5G-EIR 5G Equipment Identification Register 5G-GUTI 5G Global Unique Temporary Identifier 5G-BRG 5G Broadband Residential Gateway 5G-CRG 5G Cable Residential Gateway 5G GM 5G Grandmaster 5G-RG 5G Residential Gateway 5G-S-TMSI 5G S Primary Mobile Subscription Identifier 5G VN 5G Virtual Network 5QI 5G QoS Identifier AF Application Features AI artificial intelligence AMF Access and Mobility Management Functions AMF-G Geographically Selected Access and Mobility Management Functions AMF-NG Non-geographically Selected Access and Mobility Management Functions ANDSF Access Network Discovery and Selection Function AS Access Layer ATSSS Access traffic steering, switching and division ATSSS-LL ATSSS Low Layer AUSF authentication server function AUTN Authentication Token BCCH Broadcast Control Channel BMCA Best Master Clock Algorithm BSF binding support function CAG Closed Access Group CAPIF: A Common API Framework for 3GPP Northbound APIs CHF Charging function CN PDB Core Network Packet Delay Budget CP Control Plane DAPS Dual Active Protocol Stack DL Downlink DN Data Network DNAI DN Access Identifier DNN Data Network Name DRX Discontinuous Reception DS-TT Device-side TSN translator ePDG Evolved Packet Data Gateway EBI EPS Bearer Identity Information EPS Evolved Packet System EUI Extended Unique Identifier FAR Forwarding Action Rules FN-BRG Fixed Network Broadband RG FN-CRG Fixed network cable RG FN-RG Fixed Network RG FQDN Fully Qualified Domain Name GFBR Guaranteed Flow Bit Rate GMLC Gateway Mobile Location Center GPSI Universal Public Subscription Identifier GUAMI Globally Unique AMF Identifier GUTI Globally Unique Temporary UE Identity HPLMN Home Public Land Mobile Network HR Home Routed (Roaming) IAB Integrated Access and Backhaul IMEI / TAC IMEI type assigned code IPUPS Inter-PLMN UP Security I-SMF Intermediate SMF I-UPF Intermediate UPF LADN Local Area Data Network LBO Local Breakout (Roaming) LMF location management function LoA Level of Automation LPP LTE Positioning Protocol LRF location search function MCC Mobile Country Code MCX Mission Critical Services MDBV Maximum Data Burst Volume MFBR Maximum Flow Bit Rate MICO Mobile Initiated Connection Only MITM man in the middle ML Machine Learning MNC Mobile Network Code MPS Multimedia Priority Service MPTCP Multipath TCP Protocol Minimum set of MSD data N3IWF Non-3GPP Interoperability Features N3GPP Non-3GPP Access N5CW Non-5G on WLAN NAI Network Access Identifier NAS non-access layer NEF network publishing function NF Network Function NGAP Next Generation Application Protocol NID Network Identifier NPN Non-Public Network NR new radio NRF Network Repository Function NSACF Network Slice Admission Control Function NSI ID Network Slice Instance Identifier NSSAA Network Slice Specific Authentication and Authorization NSSAAF Network slice specific authentication and authorization functions NSSAI Network Slice Selection Support Information NSSF Network Slice Selection Function NSSP Network Slice Selection Policy NSSRG Network Slice Simultaneous Registration Group NW-TT Network side TSN translator NWDAF network data analysis function PCF Policy Control Function PDB Packet Delay Budget PDR Packet Detection Rule PDU Protocol Data Unit PEI Permanent Equipment Identifier PER Packet Error Rate PFD Packet Flow Description PLMN Public Land Mobile Network PNI-NPN Public Network Integrated Non-Public Network PPD Paging Policy Differentiation PPF paging progress flag PPI Paging Policy Indicator PSA PDU Session Anchor PSAP Public Safety Answering Point PTP Precision Time Protocol QFI QoS Flow Identifier QoE Quality of Experience RACS Radio Function Signaling Optimization (R)AN (Radio) Access Network RAT Radio Access Technology RG Residential Gateway RIM Remote Interference Management RQA Reflective QoS Attribute RQI reflective QoS indication RSN Redundant Sequence Number SA NR Standalone New Radio SBA Service-Based Architecture SBI Service-Based Interface SCP Service Communication Proxy SD Slice Differentiator SDP Session Description Protocol SEAF Security Anchor Function SEPP Security Edge Protection Proxy SIP Session Initiation Protocol SMF Session Management Facility SMSF Short Message Service Facility SN Sequence Number SN Name Service providing network name. SNPN Standalone Non-Public Network S-NSSAI Single Network Slice Selection Assistance Information SSC Session and Service Continuity SSCMSP Session and Service Continuity Mode Selection Policy SST Slice / Service Type SUCI Subscription Concealment Identifier SUPI Subscription Persistent Identifier SV Software Version TMSI Temporary Mobile Subscriber Identity TNAN Trusted Non-3GPP Access Network TNAP Trusted Non-3GPP Access Point TNGF Trusted Non-3GPP Gateway Function TNL Transport Network Layer TNLA Transport Network Layer Association TSC Time Sensitive Communications TSCAI TSC Support Information TSN Time Sensing Network TSN GM TSN Grandmaster TSP Traffic Steering Policy TT TSN Translator TWIF Trusted WLAN Interworking Function UCMF UE Radio Capability Management Function UDM Unified Data Management UDR Unified Data Repository UDSF Unstructured Data Storage Facility UE User Equipment UL Uplink UL CL Uplink Classifier UPF User Plane Function URLLC: Ultra-reliable, low-latency communications URRP-AMF UE reachability request parameters for AMF URSP UE Route Selection Policy VID VLAN identifier VLAN Virtual Local Area Network VPLMN Visiting Public Land Mobile Network W-5GAN Wired 5G Access Network W-5GBAN Wired BBF Access Network W-5GCAN Wired 5G Cable Access Network W-AGF Wireline Access Gateway Function

[0013] (definition) For the purposes of this document, 3GPP TR21.905 and the terms and definitions given below apply. Terms defined in this document take precedence over the definition of the same term in 3GPP TR21.905, if any.

[0014] (General) Those skilled in the art will appreciate that elements in the figures are illustrated for simplicity and may not necessarily be drawn to scale. Further, with respect to the configuration of a device, one or more components of the device may be represented in the figures by conventional symbols, and the figures may show only certain details relevant to an understanding of the aspects of the present disclosure, so as not to obscure the figures with details that will be readily apparent to one of ordinary skill in the art having the benefit of the description herein.

[0015] For the purposes of promoting an understanding of the principles of the present disclosure, reference will be made to the embodiments illustrated in the drawings and specific language will be used to describe them. It will nevertheless be understood that no limitation of the scope of the present disclosure is intended thereby. Such changes and further modifications in the illustrated system, and such further applications of the principles of the present disclosure as would normally occur to one skilled in the art, should be construed as being within the scope of the present disclosure.

[0016] The terms "comprises," "including," or any other variations thereof, are intended to cover non-exclusive inclusions, such that a process or method that includes a list of steps does not include only those steps, but may include other steps not expressly recited or inherent to such process or method. Similarly, one or more devices or entities or subsystems or elements or structures or components preceded by "comprising..." does not, without further constraints, preclude the presence of other devices, subsystems, elements, structures, components, additional devices, additional subsystems, additional elements, additional structures, or additional components. Throughout this specification, appearances of the phrases "in an embodiment," "in another embodiment," and similar language may, but do not necessarily, all refer to the same embodiment.

[0017] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs. The systems, methods, and examples provided herein are illustrative only and are not intended to be limiting.

[0018] In the following specification and claims, reference will be made to a number of terms that will be defined to have the following meanings: The singular forms "a," "an," and "said" include plural references unless the context clearly dictates otherwise.

[0019] As used herein, information is associated with data and knowledge, since data is meaningful information and represents values ​​attributed to parameters. Further knowledge refers to understanding of abstract or concrete concepts. It should be noted that this exemplary system is simplified to facilitate explanation of the disclosed subject matter and is not intended to limit the scope of the present disclosure. Other devices, systems, and configurations can be used in addition to or instead of the system to implement aspects disclosed herein, and all such aspects are considered to be within the scope of the present disclosure.

[0020] In addition, each aspect or element included in each of the following aspects may be implemented independently or in any combination. These aspects include novel features different from each other. Therefore, these aspects contribute to achieving different objectives or solving different problems, and to obtaining different advantages.

[0021] An exemplary object of the present disclosure is to provide a method and apparatus that can solve the above problems.

[0022] A method of a communication device according to an example aspect of the present disclosure includes transmitting a message. The message includes a request to transmit information. The information includes at least one of an identifier of a user equipment (UE), location information where the UE is located, video information around the UE, photo information around the UE, audio information around the UE, temperature information around the UE, vital information of a user of the UE, and contact information of the UE. The method includes receiving the information after transmitting the message.

[0023] A method of a user equipment (UE) according to an example aspect of the present disclosure includes receiving a message. The message includes a request to transmit information. The information includes at least one of an identifier of the UE, location information where the UE is located, video information around the UE, photo information around the UE, audio information around the UE, temperature information around the UE, vital information of a user of the UE, and contact information of the UE. The method includes transmitting the information after receiving the message.

[0024] A communication device according to an exemplary aspect of the present disclosure includes a memory and at least one hardware processor coupled to the memory. The at least one hardware processor is configured to send a message. The message includes a request to send information. The information includes at least one of an identifier of a user equipment (UE), location information where the UE is located, video information around the UE, photo information around the UE, audio information around the UE, temperature information around the UE, vital information of a user of the UE, and contact information of the UE. The at least one hardware processor is configured to receive the information after sending the message.

[0025] A user equipment (UE) according to an exemplary aspect of the present disclosure includes a memory and at least one hardware processor coupled to the memory. The at least one hardware processor is configured to receive a message. The message includes a request to transmit information. The information includes at least one of an identifier of the UE, location information where the UE is located, video information around the UE, photo information around the UE, audio information around the UE, temperature information around the UE, vital information of a user of the UE, and contact information of the UE. The at least one hardware processor is configured to transmit the information after receiving the message.

[0026] This disclosure will refer to FIGS. 1 and 2 to identify which examples of this disclosure are applicable to the time periods shown in FIGS.

[0027] FIG. 1 is a timeline showing an example of a period after a disaster occurs and the respective states of the base station and the UE. In this case, the base station remains operational (no damage), i.e., powered and the backhaul connection is maintained. However, the UE continues to operate for a limited period, indicated as "Period 1" in FIG. 1, since the UE's battery may be exhausted after some time (e.g., in 24 hours). Of course, those who can make a call, i.e., who are conscious or unrestrained, are not eligible for rescue according to the present disclosure, since they can call rescuers.

[0028] Throughout this disclosure, the term "rescuers" may refer to, for example, police, fire department, local government, mountain rangers, coast guard, self-defense forces, or the military.

[0029] FIG. 2 is a timeline illustrating some example periods and the respective states of base stations and UEs after a disaster occurs. In this case, the base station has lost power and can only operate for a limited period (depicted as “Period 2” in FIG. 2) after the disaster occurs. The UE can also continue to operate for a limited period, depicted as Period 2 plus Period 3 in FIG. 2, as long as the UE battery has some power remaining. It will be appreciated that in other scenarios, the base station may remain operable for a longer period than the UE, in which case Periods 2 and 3 may be defined differently. It will also be appreciated that the respective periods of different UEs and different base stations may differ depending on (among other things) their battery levels and energy consumption. For simplicity, a common period (e.g., a single Period 2 and / or a single Period 3) may be applied to a group of UEs and / or a group of base stations (but not necessarily all UEs and base stations) as needed.

[0030] (First aspect) This aspect discloses some examples that may be applicable to disaster situations to locate people who need to be rescued in the disaster area. It will be understood that the term "disaster" is intended to cover any other crisis event or emergency (e.g., a captive situation or any other public safety event). The term "disaster area" as used in this disclosure may refer to a geographical area affected by or associated with a disaster or any other crisis / emergency. A geographical area may be defined as an area defined by associated latitude and longitude, an area including a set of cells (at least one cell), an administrative area (e.g., a city, a district, a building, and / or the like), and any combination thereof.

[0031] Since the people in the disaster area are unknown, the main target of the results of this aspect is for rescuers to find UE identities and their locations. Furthermore, more detailed information, such as a picture showing the environment around the UE, can be useful for rescuers to decide what approach to take when trying to rescue the affected people.

[0032] (First Example of the First Aspect) A first example of the first aspect discloses a method for locating and rescuing people in a disaster area using a RAN node 5.

[0033] Hereinafter, detailed processing of the first example of the first aspect will be described with reference to Fig. 3. Fig. 3 shows the entire rescue procedure.

[0034] Step 1. A rescue worker identifies the occurrence of a disaster. The rescue worker may collect information about the disaster. For example, the rescue worker may collect information about the area where the disaster occurred. The area where the disaster occurred may be referred to as a disaster area.

[0035] Step 2. Based on the collected information about the disaster, rescuers collect status information of RAN nodes installed in the disaster area. The status information of a particular RAN node may indicate whether the particular RAN node is damaged or otherwise affected by the disaster. The status information of a particular RAN node may indicate whether the particular RAN node is operational.

[0036] Step 3. Depending on the status of RAN node 5, the rescuer takes appropriate actions.

[0037] Step 4. If the RAN node 5 is damaged, it may take the following actions depending on the damage (if known):

[0038] It should be noted that in addition to the RAN node functions and the so-called Lifeguard APL 553, the RAN node 5 may include 5GC functions, CBC functions, and IMS functions appropriate for performing a search procedure. The Lifeguard APL 553 may be an application or program configured to run on the RAN node 5. For example, a memory in the RAN node 5 may store the Lifeguard APL 553, and at least one processor in the RAN node 5 coupled to the memory may execute the Lifeguard APL 553 for processing in the present disclosure. In the present disclosure, a sentence in which the subject is described as the Lifeguard APL 553 may be interpreted as a sentence in which the subject is described as the RAN node 5.

[0039] {Connection to core network / O&M is lost while radio part and power are operational} - If the Lifeguard APL 553 determines that a search procedure needs to be performed based on a combination of various inputs, e.g., a loss of backhaul connectivity and detection of a large earthquake (e.g., exceeding a relevant threshold), the Lifeguard APL 553 initiates the search procedure as disclosed in the second example of the first aspect according to a preconfigured program in the data storage 5531. In this case, the RAN node 5 is responsible for rescue operations in both period 2 and period 3 of FIG.

[0040] {Power is lost while the connection to the core network / O&M and radio is still active} -If the Lifeguard APL553 determines that a search procedure needs to be performed based on a combination of various inputs, e.g., loss of backhaul connection and detection of a large earthquake, the Lifeguard APL553 initiates a search procedure as disclosed in the second example of the first aspect according to a pre-configured program in the data storage 5531. The Lifeguard APL 553 may initiate communication with rescue personnel to indicate that rescue procedures have been initiated by the RAN node 5 and the estimated time that the RAN node 5 will lose battery power. In this case, the RAN node 5 is responsible for the search procedure for period 2 shown in Figure 2.

[0041] Step 5. Based on the collected disaster information, rescuers launch drone RAN node 5 to the disaster area.

[0042] Information from the Lifeguard APL 553 of the RAN node 5 can also be referenced for decision making about when and where the drone RAN node 5 is needed.

[0043] For example, the Lifeguard APL 553 of the RAN node 5 indicates that the battery of the RAN node 5 will last at least 5 hours, and the drone RAN node 5 is launched / deployed to the disaster area where the RAN node 5 is located in about 5 hours. In this case, the drone RAN node 5 is responsible for the search procedure for period 3 shown in FIG. 2.

[0044] The drone RAN node 5 has one or more of the following features: The drone RAN node 5 includes all the normal RAN node functionality as shown in RAN node 5 of Figure 15. Further, the Lifeguard APL553 in the drone RAN node 5 includes 5GC functionality, CBC functionality, and IMS functionality to perform search procedures. The IMS function in the Lifeguard APL 553 may also have a PSAP function that interoperates with the IMS function. The PSAP function may handle the MSD in the IMS message and communicate with the UE 3 using a communication path established by the IMS function. The drone RAN node 5 has the capability to broadcast the PLMN ID available in the disaster area. The PLMN ID may be the one to which the damaged RAN node 5 belongs so that all UEs belonging to that PLMN can tune to the drone RAN node 5. The drone RAN node 5 has the capability to broadcast multiple PLMN IDs that may be available in the disaster area. All PLMN IDs operational in the disaster area are pre-configured in the drone RAN node 5. For example, all PLMN IDs identifying the PLMN(s) operational in the disaster area may be pre-configured in the drone RAN node 5. This shared RAN functionality can help to search for UEs that have some PLMN IDs registered in the forbidden PLMN list in the UE's USIM. Once the drone RAN node 5 completes the search procedure, it returns to its designated location, either programmatically or based on an order from rescuers.

[0045] Step 6. Once the normal RAN node 5 or the drone RAN node 5 completes the search procedure, rescuers initiate rescue operations based on the information collected during the search procedure in the normal RAN node 5 and / or the drone RAN node 5.

[0046] Step 7. Based on the collected information about the disaster and information from the RAN node 5 via the O&M connection, the rescue personnel can instruct the RAN node 5 to start a search procedure. When the RAN node 5 processes traffic for mobile communication including emergency calls, the rescue personnel can instruct the RAN node 5 to adopt a search procedure that does not affect traffic processing for mobile communication. For example, the rescue personnel can use their own UE to execute the above instruction. If the RAN node 5 is not damaged, step 7 can be executed.

[0047] Step 8. Once the RAN node 5 completes the search procedure, rescue personnel will initiate appropriate rescue operations based on the information collected during the search procedure in the RAN node 5.

[0048] (Second Example of the First Aspect) A second example of the first aspect discloses a search procedure using PWS and eCALL functions defined in 3GPP TS23.041 (Non-Patent Document 2) and 3GPP TS23.167 (Non-Patent Document 7), respectively. The search procedure provides useful information for rescuers to find and rescue people at the disaster site.

[0049] The RAN node 5 in this example may be a normal RAN node or a drone RAN node.

[0050] The Lifeguard APL553 in the RAN node 5 includes the following functions: - CBC function: The CBC function generates a write request alert request message as defined in 3GPP TS 23.041 (Non-Patent Document 2). The write request alert request message may be replaced by a write replacement alert request message. -AMF and MME functions: The AMF and MME functions are responsible for cell broadcast message processing, mobility management, and session management. -SMF, UPF, SGW and PGW, PCRF and PCF functions: These functions are responsible for session processing of IMS eCALL. - IMS Function: The IMS Function handles eCALL over IMS as defined in 3GPP TS 23.167 (Non-Patent Document 7). An eCALL can be expressed as an emergency call.

[0051] Lifeguard APL363 in UE3 includes the following features: - Public Warning System (PWS) Application Function: When an alert message in the System Information Block, SIB, is received, the Lifeguard APL 363 digests the received message and takes appropriate action based on the request in the received message. -IMS Function: The IMS Function handles eCALL over IMS as defined in 3GPP TS 23.167 (Non-Patent Document 7).

[0052] The lifeguard APL 363 may be an application or program configured to execute in the UE 3. For example, a memory in the UE 3 may store the lifeguard APL 363, and at least one processor in the UE 3 coupled to the memory may execute the lifeguard APL 363 for processing as described in this disclosure. Note that in this disclosure, a sentence in which the subject is the lifeguard APL 363 may be interpreted as a sentence in which the subject is the UE 3.

[0053] Hereinafter, detailed processing of the second example of the first aspect will be described with reference to Fig. 4. Fig. 4 shows a search procedure by eCALL.

[0054] Step 1. The RAN node 5 decides to initiate a search procedure. This decision may be made solely by the RAN node 5 based on pre-configured decision-making criteria within the RAN node 5, or may be instructed by rescue personnel (e.g., via O&M communication, etc.). For example, if the RAN node 5 determines that there is a disaster situation, the RAN node 5 may decide to initiate a search procedure. For example, the RAN node 5 may determine that there is a disaster situation based on information acquired by the RAN node 5 or information received from other communication devices. The information acquired by the RAN node 5 or received from other communication devices may indicate the occurrence of a disaster. For example, the RAN node 5 may acquire information indicating the occurrence of an earthquake using at least one sensor capable of acquiring seismic intensity, if it is an earthquake.

[0055] Step 2. The Lifeguard APL 553 generates a write request alert request message including a message ID, an alert type, and requested information parameters based on the disaster situation (e.g., if the RAN node 5 determines that there is a disaster situation) or instructions from the rescue personnel. The write request alert request message may be replaced with a write replacement alert request message. The instructions from the rescue personnel may be instructions to initiate a search procedure or instructions to generate a write request alert request message. The following bullet points describe some example details of each parameter that may be included in the write request alert request message. Message ID: Information that identifies the broadcasted message. In this example, it can mean "This is a request for data collection for the purpose of saving lives due to disasters." This message ID is read by the UE3 and routed to the Lifeguard APL363 in the UE3. - Alert Type: The alert type indicates the type of alert. In this example, it may be for example "Data Required Due to Disaster". This parameter may be read by the UE 3 and routed to the Lifeguard APL 363. - Requested Information: A message to the Lifeguard APL 363 in the UE 3. This requested information may include: #Notification mode: The notification mode may indicate whether an alert to the UE3 is required. If an alert is required, the type of alert is also indicated. For example, the type of alert may indicate at least one of a beep, a volume level, a vibration, and a pop-up message. If an alert is not required, the Lifeguard APL 363 in the UE3 performs any requested processing in the background to avoid being perceived by the user of the UE3 and / or other people in the vicinity. #Textual warning message: Human readable warning message. #User Consent Request: This indicates that the user of the UE 3 requires user consent to send information to the Lifeguard APL 553 in the RAN node 5. #Information requested: *UE Identifier: may be the IMSI, SUPI, and / or MSISDN number of the UE (or any other suitable identifier associated with the user or UE 3). *UE Location: The UE location may be given in GPS format or may be the location expressed in civic and geospatial location format as defined in IETF RFC5580 (Non-Patent Document 4). *Video: You will be asked to take a video clip of the surrounding scenery. *Photos: You will be asked to take photos of your surroundings. *Audio: The UE is requested to record the audio where it is located. *Temperature: A measurement of the temperature where the UE is located is requested. *Vital information: If there is vital information, request measurement. This can be measured when the UE is connected to a smart watch, etc. *Contact: Requests a report of the user's contact information. The requested information may indicate the information that UE 3 obtains.

[0056] The requested information may be normalized information. For example, the information may be expressed as a number. In this case, the meaning of the normalized information is shared in advance between the lifeguard APL 363 and the lifeguard APL 553. This normalization may help reduce the amount of data transferred to the lifeguard APL 363 in the UE 3.

[0057] Step 3. The AMF function or MME function in the Lifeguard APL 553 sends a write request alert request message including a message ID, an alert type, requested information, and other parameters according to 3GPP TS 23.041 (Non-Patent Document 2) to the RAN node function in the communication control module 552. The write request alert request message may be replaced with a write replacement alert request message.

[0058] Step 4. The RAN node function in the communication control module 552 broadcasts the requested information on the BCCH. The RAN node function in the communication control module 552 may broadcast a write request alert request message.

[0059] The requested information or write request alert request message may be broadcast in SIB6 as an ETWS primary notification, and / or in SIB7 as an ETWS secondary notification, and / or in SIB8 as a CMAS notification, if the RAN node 5 supports the NG-RAN functionality.

[0060] The requested information or write request alert request message may be broadcast in SIB10 as an ETWS primary notification and / or in SIB11 as an ETWS secondary notification and / or in SIB12 as a CMAS notification if the RAN node 5 supports E-UTRAN functionality.

[0061] Step 5. Upon receiving the message broadcast on the BCCH by the communication control module 362 in the UE 3, the communication control module 362 forwards the received message to the lifeguard APL 363 in the UE 3.

[0062] The Lifeguard APL 363 may be selected as the destination of an application by the communications control module 362 by referencing the message identifier and / or serial number values ​​received on the SIB in accordance with 3GPP 38.331 (Non-Patent Document 5) and 3GPP 36.331 (Non-Patent Document 6) for NG-RAN and E-UTRAN, respectively.

[0063] The Lifeguard APL 363 may be selected as the application destination by the communications control module 362 by referencing received values ​​of message ID and / or alert type in the alert request message that correspond to the message ID and alert type set by the Lifeguard APL 553 in step 2.

[0064] Note that the message broadcast in step 4 can be received by the UE 3 even if the UE 3 is in a limited service state according to section 4.6.4 of 3GPP 22.268 (Non-Patent Document 9). Therefore, any device in the disaster area can receive the message broadcast in step 4.

[0065] Step 6. The Lifeguard APL 363 in the UE 3 may analyze the received message and decide whether to ignore the message or execute a reporting procedure. For example, the Lifeguard APL 363 may decide to execute a reporting procedure based on information contained in the requested message. For example, the Lifeguard APL 363 may decide to execute a reporting procedure if the requested message contains the requested information. If the Lifeguard APL 363 decides to execute a reporting procedure, the Lifeguard APL 363 may execute a process of step 7 described below as a reporting procedure. For example, the Lifeguard APL 363 may decide to ignore a requested message if the requested message does not contain the requested information.

[0066] Also, regardless of the above judgment, the Lifeguard APL363 may perform the following operations. Based on the received notification mode, the Lifeguard APL 363 may play a warning beep, play a warning sound, or vibrate the UE 3 to notify / warn the user of the UE 3. - If an alert message is received, the received message may be displayed on the user display of the UE3 or read by a voice generating application within the UE3.

[0067] If a received message has a digital signature, the sender can be verified using a public key pre-configured in data storage 3631 within the Lifeguard APL 363.

[0068] Step 7. Once the Lifeguard APL 363 decides to initiate the reporting procedure in step 6, the Lifeguard APL 363 collects all necessary data as requested by the Lifeguard APL 553 in step 2.

[0069] For example, one or more of the following actions may be performed by UE 3: If the notification mode indicates that no alert to the UE 3 is required, then all processing that the Lifeguard APL 363 performs in step 7 may be performed covertly (as background processing) to avoid being perceived by the user of the UE 3 and / or other people nearby. Otherwise (e.g., if the notification mode indicates that an alert to the UE is required), the Lifeguard APL 363 may sound an alert beep, sound an alert, or vibrate the UE 3 to notify / alert the user of the UE 3 as indicated by the notification mode parameter. When an alert message is received, the received message is displayed on the user display of the UE3 or read out by a voice generating application within the UE3. If user consent is required, the Lifeguard APL 363 prompts the user of the UE 3 to indicate a preference as to whether data reporting should be permitted. For example, this user consent may be one of the following actions: #Pop up a message asking the user to press a button. # A voice generating application will ask you to say YES or NO over the attached speaker. #A negative question can obtain user consent. For example, an equipped speaker can ask the user, "If you don't want to report, please shout or say something." This can be useful when the user of the UE3 is unconscious and cannot do anything. For example, the lifeguard APL363 may determine whether to perform data collection and reporting of the collected data based on the result of the inquiry, as described below. For example, if the microphone included in the UE3 does not detect the user's speech / voice, the lifeguard APL363 may perform data collection and reporting of the collected data, as described below. For example, if the microphone detects the user's speech / voice, the lifeguard APL363 may not perform data collection and reporting of the collected data, as described below. -The following data collection may be performed: #If a UE identifier is requested (e.g., the requested information includes a UE identifier), the Lifeguard APL 363 obtains an identifier of the UE 3 (e.g., at least one of the IMSI, SUPI, and MSISDN number of the UE 3). The Lifeguard APL 363 may obtain the identifier of the UE 3 from a memory of the UE 3. #If UE location is requested (e.g., the requested information includes UE location), the Lifeguard APL 363 obtains the current location of the UE 3 by interacting with a positioning / GPS application in the UE 3. The current location may be expressed as location information where the UE 3 is located. # If video is requested (e.g., the requested information includes video), the Lifeguard APL 363 creates a video clip of the UE's surroundings by interacting with the video application and camera of the UE 3. The Lifeguard APL 363 can create a video clip of the environment or scene surrounding the UE 3. The video clip may be represented as video information. #If a photo is requested (e.g., the requested information includes a photo), the lifeguard APL 363 takes several photos of the surroundings of the UE by interacting with the camera application and camera unit of the UE 3. The lifeguard APL 363 may take photos of the environment or scene surrounding the UE 3. The photos may be expressed as photo information or picture information. #If audio is requested (e.g., the requested information includes audio), the Lifeguard APL 363 interacts with the UE 3's recording application and microphone to record any noise / sound at the UE's location into one or more audio files. The Lifeguard APL 363 may record the sounds of the environment or scene surrounding the UE 3. The audio files and / or sounds may be referred to as audio information. #If temperature is requested (e.g., the requested information includes temperature), the Lifeguard APL 363 measures the temperature by interacting with a thermometer application in the UE 3. The Lifeguard APL 363 may measure or obtain the temperature of the UE's environment. The Lifeguard APL 363 may measure or obtain information about the weather conditions around the UE 3. The measured temperature may be represented as temperature information. #If vital information is requested (e.g., the requested information includes vital information), the lifeguard APL 363 measures the vital information and / or accesses any pre-recorded vital information in the UE 3 to obtain the vital information by interacting with a health monitoring application in the UE 3. The lifeguard APL 363 may measure or obtain vital information of the user of the UE 3. The vital information may include vital signs such as body temperature, heart rate, respiratory rate, blood pressure, etc. #If contact information is requested (e.g., the requested information includes contact information), the Lifeguard APL 363 provides the phone number and / or pre-configured phone number (e.g., emergency contact number) of the user of the UE 3, the relationship to the user of the UE 3, etc. For example, the contact information returned may be the phone number of a family member (e.g., spouse or parent's phone number) and current address. In one example, the lifeguard APL 363 obtains at least some (or all) of the contact information stored in the UE 3 by interacting with an address book application in the UE 3 .

[0070] Step 8. The Lifeguard APL 363 in the UE 3 initiates a UE detectable emergency session procedure as specified in section 7.7.1 of 3GPP TS 23.167 (Non-Patent Document 7).

[0071] Note that the UE 3 can initiate a UE discoverable emergency session procedure even if the UE 3 is in a limited service state according to section 3.5 of 3GPP 23.122 (Non-Patent Document 8). Therefore, if the UE 3 is 3GPP compliant, any device in the disaster area can initiate a UE discoverable emergency session procedure.

[0072] Step 9. The Lifeguard APL 363 in the UE 3 sends an initial emergency SIP Invite message to the Lifeguard APL 553 in the RAN node 5, including the MSD, an emergency service indicator of eCall type, and other parameters. The MSD includes the data collected by the UE 3 in step 7. The eCall type of the emergency service indicator can be either automatic or manual, according to the configuration set by the rescuer. The collected data can include at least one of an identifier of the UE 3, a location of the UE 3, a photo, an audio file, temperature, vital information, and contact information, as mentioned in step 7.

[0073] Step 10. When the initial emergency SIP Invite message is received by the Lifeguard APL 553 in the RAN node 5, the Lifeguard APL 553 stores the received MSD in the data storage 5531 of the RAN node 5.

[0074] Step 11. The Lifeguard APL 553 in the RAN node 5 sends a 200 OK message containing the MSD acknowledgement to the Lifeguard APL 363 in the UE 3.

[0075] Step 12. After the MSD transfer from UE 3 to RAN node 5 is successful, the emergency session is released by either the Lifeguard APL 553 or the Lifeguard APL 363. For example, if the Lifeguard APL 363 in UE 3 receives a 200 OK message, the Lifeguard APL 363 may release the emergency session. For example, if the Lifeguard APL 553 in RAN node 5 sends a 200 OK message, the Lifeguard APL 553 may release the emergency session.

[0076] After step 12, the rescuer can collect and refer to the data in the data storage 5531 in the RAN node 5, and perform appropriate rescue operations based on the collected data in the data storage 5531. For example, if the lifeguard APL 553 stores the received MSD, the lifeguard APL 553 may notify the rescuer (e.g., the rescuer's UE) that the RAN node 5 has collected data. The rescuer can then collect and refer to the data in the data storage 5531 in the RAN node 5.

[0077] (Modification 1 of the second example of the first aspect) In step 10 of FIG. 4, after the Lifeguard APL 553 in the RAN node 5 stores the received MSD in the data storage 5531, the Lifeguard APL 553 may request additional data from the Lifeguard APL 363 in the UE 3.

[0078] In this case, the following steps in Figure 5 can be performed between step 11 and step 12 in Figure 4. Figure 5 shows the MSD request procedure.

[0079] Step 11-1. The lifeguard APL 553 of the RAN node 5 sends a SIP message including a request for MSD to the lifeguard APL 363 of the UE 3. The request for MSD may include all or part of the requested information as described in step 2 of Figure 4. In one example, the SIP message of step 11-1 is a SIP information (INFO) method message.

[0080] Step 11-2: Upon receiving the SIP message in step 11-1, the Lifeguard APL 363 collects all the necessary data requested by the Lifeguard APL 553 in step 11-1. For the data collection process by the Lifeguard APL 363, please refer to step 7 in FIG.

[0081] Step 11-3. The Lifeguard APL 363 sends a SIP response message to the Lifeguard APL 553 in the RAN node 5 that includes the MSD. In one example, the SIP response message of step 11-3 is a SIP Information Method message. The MSD can include the data collected by the Lifeguard APL 363 in step 11-2.

[0082] Step 11-4. When the Lifeguard APL 553 in the RAN node 5 receives the SIP response message, the Lifeguard APL 553 stores the received MSD in the data storage 5531 of the RAN node 5.

[0083] (Third Example of the First Aspect) A third example of the first aspect discloses a search procedure using a PWS and an emergency call function defined in 3GPP TS23.041 (Non-Patent Document 2) and 3GPP TS23.167 (Non-Patent Document 7), respectively. The search procedure provides useful information for rescuers to find and rescue people at the disaster site.

[0084] The RAN node 5 in this example may be a normal RAN node or a drone RAN node.

[0085] The Lifeguard APL 553 in the RAN node 5 includes one or more of the following functions: - CBC function: The CBC function generates a write request alert request message as defined in 3GPP TS 23.041 (Non-Patent Document 2). The write request alert request message may be replaced by a write replacement alert request message. -AMF and MME functions: The AMF and MME functions are responsible for cell broadcast message processing, mobility management, and session management. -SMF, UPF, SGW and PGW, PCRF and PCF functions: These functions are responsible for session processing of IMS eCALL. - IMS Function: The IMS Function handles emergency calls over the IMS as defined in 3GPP TS 23.167 (Non-Patent Document 7). -Communication Function: The communication function is responsible for communicating with the user of the UE3 (e.g., via a user interface). Based on the conversation with the user, the communication function understands the situation the user is facing and finds the best way to rescue the user if necessary. The communication function may be realized by software within the Lifeguard APL553, which is capable of performing speech recognition and speech generation to converse with the user, for example using AI and ML techniques. Alternatively, voice communication may be performed with a rescuer / lifeguard. In this case, a dedicated data connection is established between the rescuer (rescuer's UE) and the lifeguard APL 553, and the data connection is used for voice communication between the user using the UE 3 and the rescuer / lifeguard via the RAN node 5.

[0086] Lifeguard APL363 in UE3 includes the following features: - Public Warning System (PWS) Application Function: When an alert message in the System Information Block, SIB, is received, the Lifeguard APL 363 digests the received message and takes appropriate action based on the request in the received message. -IMS Function: The IMS Function handles eCALL over IMS as defined in 3GPP TS 23.167 (Non-Patent Document 7).

[0087] Hereinafter, detailed processing of the third example of the first embodiment will be described with reference to Fig. 6. Fig. 6 shows a search procedure in response to an emergency call.

[0088] Steps 1 to 7. Steps 1 to 7 are the same as steps 1 to 7 in FIG.

[0089] Step 8. The Lifeguard APL 363 in the UE 3 initiates MSD transfer / acknowledgement during session establishment with a PSAP supporting the NG-eCall procedure as specified in section 7.7.1 of 3GPP TS 23.167 (Non-Patent Document 7). In step 8, the data collected in step 7 may be transmitted to the RAN node 5. The Lifeguard APL 553 may store the MSD including the received collected data in the data storage 5531 in the RAN node 5.

[0090] The lifeguard APL 553 of the RAN node 5 collects or determines the situation facing the user of the UE 3 and finds the best way to rescue the user if necessary. For example, the lifeguard APL 553 may report the situation and / or the best way to rescue the user to a rescuer (e.g., the rescuer's UE). The situation and / or the best way to rescue the user may be included in the collected data and / or transmitted to the RAN node 5.

[0091] For example, based on the collected data, the lifeguard APL 553 in the RAN node 5 can gather the situation faced by the user of the UE 3 and find the best way to rescue the user if necessary.

[0092] For example, the lifeguard APL 553 may transmit the UE location in the collected data to another communication device having location information indicating an area where a disaster has occurred. Then, the communication device determines that the user of UE3 is affected or may be affected by the disaster if the location indicated by the UE location falls within the area indicated by the location information. Then, the communication device transmits information indicating that the user of UE3 is affected or may be affected by the disaster to the lifeguard APL 553. Then, the lifeguard APL 553 collects information indicating that the user of UE3 is affected or may be affected by the disaster as a situation related to the user (or UE3). For example, the lifeguard APL 553 may determine that a fire engine and an ambulance are needed as the best way to rescue the user.

[0093] For example, the Lifeguard APL 553 in the RAN node 5 may determine whether the user of the UE 3 is affected by the disaster or may be affected by the disaster based on the location of the UE in the collected data and location information indicating the area where the disaster occurred. In this case, the Lifeguard APL 553 may obtain location information indicating the area where the disaster occurred from another communication device.

[0094] For example, the lifeguard APL 553 in RAN node 5 may determine that if a video clip or photo in the collected data shows a fire occurring (or indicates the risk of a fire), then the user of UE 3 is at risk of fire and that a fire truck is the best way to rescue the user.

[0095] For example, if an audio file in the collected data contains (or identifies) a scream or similar sound, the Lifeguard APL 553 in RAN node 5 may determine that the user of UE 3 is facing a dangerous situation and that the best way to rescue the user is to call the police.

[0096] For example, if the temperature in the collected data indicates a low temperature and the vital signs information in the collected data indicates that the user's condition is serious, the lifeguard APL 553 in the RAN node 5 determines that the life of the user of the UE 3 is in danger and that an ambulance is needed as the best way to rescue the user.

[0097] Additionally, once a connection for voice communication is established between UE3 and the Lifeguard APL553, the user of UE3 can interact with (or through) the communication functionality of the Lifeguard APL553 to describe the situation the user is facing and, if necessary, find the best way to rescue the user.

[0098] In addition, the UE 3 can initiate MSD transfer / acknowledgement during session establishment with a PSAP that supports the NG-eCall procedure, even if the UE 3 is in a limited service state, according to section 3.5 of 3GPP23.122 (Non-Patent Document 8). Therefore, if the UE 3 complies with 3GPP, any device in the disaster area can initiate MSD transfer / acknowledgement during session establishment with a PSAP that supports the NG-eCall procedure.

[0099] Step 9. After successful MSD transfer / acknowledgement during session establishment with a PSAP supporting NG-eCall procedure, the emergency session is released either by Lifeguard APL553 or Lifeguard APL363.

[0100] After step 9, the rescuer can collect / receive data from the MSD and store the data in the data storage 5531 in the RAN node 5. Then, the rescuer can refer to the collected data in the data storage 5531 of the RAN node 5 and take appropriate rescue actions based on the collected data in the data storage 5531 and the conversation with the user. For example, if the lifeguard APL 553 stores the collected data, the lifeguard APL 553 may notify the rescuer (e.g., the rescuer's UE) that the RAN node 5 has collected the data. Then, the rescuer can collect and refer to the data in the data storage 5531 in the RAN node 5.

[0101] (Modification 1 of the third example of the first aspect) If the UE 3 is unable to provide location information to the Lifeguard APL 553, for example if the UE 3 does not have GPS capability and the RAN node 5 is a drone RAN node 5, the following steps can be taken to find the exact location of the UE 3. -After a connection for voice communications is established between UE3 and Lifeguard APL553 in step 8, the drone RAN node 5 may maintain the connection and begin measuring the signal strength of a wireless signal (e.g., a reference signal or any other suitable signal) from UE3. The drone RAN node 5 may measure signals from the UE 3 by rotating the antenna direction and / or by using beamforming and / or by using other radio techniques. Based on multiple measurements, the drone RAN node 5 finds the exact location of the UE 3. The drone RAN node 5 may move closer to the UE 3 based on the measurement results. In this case, the Lifeguard APL 553 may add a video media connection between the Lifeguard APL 553 and the UE 3 to visually locate and recognize the user, in addition to the voice communication connection using native IMS capabilities.

[0102] (Second aspect) This aspect discloses several examples useful for locating and determining the status of a known person who is in need of rescue due to an emergency. For example, in one use case, a person may be rendered unconscious after a fall (or similar accident) while climbing a mountain. In this case, rescuers may know in advance who to call for rescue because the climber may have submitted a climbing plan with personal data including the climber's phone number.

[0103] (First Example of the Second Aspect) A first example of the second aspect discloses a search procedure using IMS functionality defined in 3GPP TS 23.228 (Non-Patent Document 11). The search procedure is particularly useful for obtaining information about the location and status of a user when the user is known or considered to be in an emergency situation.

[0104] PSAP202 includes the following functions: - IMS Function: The IMS Function handles IMS calls as defined in 3GPP TS 23.228 (Non-Patent Document 11). - Alert message processing function: To support the search function, the PSAP 202 generates an alert message and sends it to the IMS (e.g., CSCF) 201. The PSAP 202 also receives collected data from the IMS (e.g., CSCF) 201. The IMS 201 may be or may include a CSCF.

[0105] Lifeguard APL363 in UE3 includes the following features: - IMS Function: The IMS Function handles IMS calls as defined in 3GPP TS 23.228 (Non-Patent Document 11). - Alert Message Processing Function: When an IMS message containing an alert indication is received, the Lifeguard APL 363 digests the received message and takes appropriate action based on the request in the received message.

[0106] Next, detailed processing of the first example of the second aspect will be described with reference to Fig. 7. Fig. 7 shows a person discovery procedure using an IMS.

[0107] Step 0. The PSAP 202 places a call (originates a call) to a person suspected of being involved in an accident. For example, a worker uses the PSAP 202 to place a call to a person suspected of being involved in an accident. For example, if a climber does not return from the mountain as scheduled, the worker uses the PSAP 202 to place a call to the climber. If a person (a user of UE3) does not answer the phone, the worker may consider that the person discovery procedure of the present disclosure may be useful in locating the person (if the person is unable to answer the phone due to an injury or accident in the mountains).

[0108] It should be noted that step 0 does not have to be performed if, for example, a PSAP worker attempts to contact a detained person.

[0109] Step 1. PSAP202 decides to make (initiate) a call to find a user of UE3 who may be unable to answer or respond to a call. In this example, an operator decides whether to use PSAP202 to make a call to locate a user of UE3 who may be unable to answer or respond to a call. For example, if an operator instructs PSAP202 to start a search procedure, PSAP202 may decide to start a search procedure in step 1. For example, an operator may decide to start a search procedure and instruct PSAP202 to start the search procedure. An operator may decide to start a search procedure when a call is made to a user of UE but there is no answer / response from the user.

[0110] Step 2. PSAP 202 generates a SIP Invite message containing the requested information. The content of the requested information can be the same as the requested information described in step 2 of Fig. 4. The requested information can be expressed by parameters in the existing Session Initiation Protocol (SIP) and the associated Session Description Protocol (SDP) defined in 3GPP TS 24.229 (Non-Patent Document 10).

[0111] Step 3. The PSAP 202 sends a SIP Invite message containing the user ID and the requested information. The user ID may be a public user identity, a Tel URI, or the SIP URI of the UE 3.

[0112] Step 4. The IMS (eg, CSCF) 201 forwards the SIP Invite message received in step 3 to the UE 3.

[0113] Step 5. The UE3 receives the SIP invite message. The Lifeguard APL363 in the UE3 may analyze the received message and decide whether to ignore the message or to execute a reporting procedure. For example, the Lifeguard APL363 may decide to execute the reporting procedure based on information included in the SIP invite message. For example, the Lifeguard APL363 may decide to execute the reporting procedure when the SIP invite message contains the requested information. If the Lifeguard APL363 decides to execute the reporting procedure, the Lifeguard APL363 may execute the process of step 6 described below as the reporting procedure. For example, the Lifeguard APL363 may decide to ignore the requested message when the requested message does not contain the requested information.

[0114] Further, regardless of the above determination, the lifeguard APL363 may take one or more of the following actions: - Based on the received notification mode, the Lifeguard APL363 may notify / alert the user of the UE3 by playing a warning beep, playing a warning sound, or vibrating the UE3. When an alert message is received, the received message is displayed on the user display of the UE3 or read out by a voice generating application within the UE3.

[0115] Step 6. Once the Lifeguard APL 363 decides to initiate a reporting procedure in step 5, the Lifeguard APL 363 collects all the necessary data requested by the PSAP 202 in step 2.

[0116] In UE3, the following operations may be illustrated: If the notification mode indicates that no alert to the UE is required, then all processing done by the Lifeguard APL 363 in this step 6 may be performed covertly in the background so as not to be perceived by the user of the UE 3 and by people in the vicinity. Otherwise (e.g., if the notification mode indicates that an alert to the UE is required), the Lifeguard APL 363 may notify / alert the user of the UE 3 by sounding an alert beep, sounding an alert tone, or vibrating the UE 3, as indicated by the notification mode parameter. When an alert message is received, the received message is displayed on the user display of the UE3 or read out by a voice generating application within the UE3. If user consent is required, the Lifeguard APL 363 prompts the user of the UE 3 to indicate a preference as to whether data reporting should be permitted. For example, user consent may be obtained using any one of the following processes (or any combination thereof): #Pop up a message asking the user to press a button. # A voice generating application will ask you to say YES or NO over the attached speaker. #Negative questions can be used to obtain user consent or preference. For example, an equipped speaker can ask the user, "If you don't want to report, shout or say something." This can be useful when the user of UE3 is unconscious and unable to speak or act. For example, the lifeguard APL363 may determine whether to perform data collection and reporting of collected data, as described below, based on the result of querying the user. For example, if UE3 does not detect (using its microphone) words or sounds by the user, the lifeguard APL363 may perform data collection and reporting of collected data, as described below. For example, if the microphone detects words or sounds by the user, the lifeguard APL363 may not perform data collection and reporting of collected data, as described below. -The following data collection may be performed: #If a UE identifier is requested (e.g., the requested information includes a UE identifier), the Lifeguard APL 363 obtains an identifier for the UE 3 (e.g., the IMSI, SUPI, or MSISDN number of the UE 3). The Lifeguard APL 363 may obtain the identifier for the UE 3 from a memory of the UE 3. #If UE location is requested (e.g., the requested information includes UE location), Lifeguard APL 363 obtains the current location of UE 3 (e.g., by interacting with a GPS application in UE 3). #If video is requested (eg, the requested information includes video), the Lifeguard APL 363 creates a video clip of the UE's surroundings by interacting with the UE's 3 video application and camera unit. #If photos are requested (eg, the requested information includes photos), the Lifeguard APL363 takes several photos of the UE's surroundings by interacting with the camera application and unit of the UE3. #If audio is requested (e.g., the requested information includes audio), Lifeguard APL363 records any noise / speech at the UE's location to one or more audio files by interacting with the UE's recording application and microphone. #If temperature is requested (e.g., the requested information includes temperature), the Lifeguard APL363 interacts with a thermometer application (and any associated thermal sensors, if applicable) in UE3 to measure the temperature. #If vital information is requested (e.g., the requested information includes vital information), the Lifeguard APL363 obtains the appropriate vital information and / or accesses any recorded vital information in the UE3 by interacting with the health monitoring application (and any associated sensors, if applicable) in the UE3. #If contact information is requested (e.g., the requested information includes contact information), the Lifeguard APL 363 provides the phone number or pre-configured phone number (e.g., emergency contact number) of the user of the UE 3, the relationship to the user of the UE 3, etc. For example, the contact information returned may be the phone number of a family member of the user of the UE 3 (e.g., spouse or parent phone number) and current address. In one example, the lifeguard APL 363 obtains at least some (or all) of the contact information stored in the UE 3 by interacting with an address book application in the UE 3 .

[0117] Step 7. The Lifeguard APL 363 sends a SIP message including the collected data to the IMS (e.g., CSCF) 201. The collected data includes the data collected in step 6. The collected data may be included in an SDP.

[0118] Step 8. The IMS (eg, CSCF) 201 forwards the SIP message received in step 7 to the PSAP 202. Upon receiving the SIP message, the PSAP 202 may store the received SDP in its data storage.

[0119] After step 8, the rescuer refers to the collected data and takes appropriate rescue action. For example, if PSAP202 stores the received SDP, PSAP202 may notify the rescuer (e.g., the rescuer's UE) that it has collected data. The rescuer can then collect and refer to the data in the data storage in PSAP202.

[0120] (Second Example of the Second Aspect) A second example of the second aspect discloses a search procedure using NEF as specified in 3GPP TS 23.501 (Non-Patent Document 12) and 3GPP TS 23.502 (Non-Patent Document 13). The search procedure is particularly useful for obtaining information about the location and status of a user when the user is known or considered to be in an emergency situation.

[0121] PSAP202 includes the following functions: - Alert message processing function: To support the search function, the PSAP 202 generates alert messages and sends them to the NEF 77. The PSAP 202 also receives collected data from the NEF 77.

[0122] Lifeguard APL363 in UE3 includes the following features: - Alert message response function: When a page containing an alert display (paging message, system broadcast, etc.) is received, the Lifeguard APL363 digests the received message and takes appropriate action based on the request in the received message.

[0123] Next, detailed processing of the second example of the second aspect will be described with reference to Fig. 8. Fig. 8 shows a person discovery procedure using NEF.

[0124] Step 1. PSAP202 decides to start a search procedure to find a user of UE3 who may be in an emergency. For example, an operator of PSAP202 decides to start a search procedure to find a user of UE3 who may be in an emergency. For example, PSAP202 may decide to start a search procedure when an operator instructs PSAP202 to start a search procedure. For example, an operator may decide to start a search procedure and instruct PSAP202 to start the search procedure. An operator may decide to start a search procedure when a call is made to a UE (made a call) but there is no answer or response to the call from the user.

[0125] Step 2. The PSAP 202 generates a NEF service message containing the requested information, which may be the same as the requested information described in step 2 of FIG.

[0126] Step 3. The PSAP 202 sends an NEF_EventExposure_Subscribe message containing the UE ID and the requested information to the NEF 77. The UE ID may be any suitable identifier associated with the user or UE 3, such as the IMSI, SUPI, PEI, or MSISDN number of the UE 3. If the UE ID is a PEI or MSISDN number, the NEF 77 converts this to the SUPI of the UE 3.

[0127] Step 4: The NEF 77 sends an Nnef_EventExposure_Subscribe response message to the PSAP 202.

[0128] Step 5. The NEF 77 sends a Nudm_EventExposure_Subscribe message containing the UE ID and the requested information to the UDM 75. The UE ID can be an IMSI or a SUPI.

[0129] Step 6. The UDM 75 sends a Namf_EventExposure_Subscribe message containing the UE ID and the requested information to the AMF 70. The UE ID can be an IMSI or a SUPI.

[0130] Step 7. The AMF 70 sends a paging message containing the UE ID and the requested information to all RAN nodes 5 in the TAI list of the UE 3.

[0131] Step 8. The RAN node 5 receives the paging message from the AMF 70. The RAN node 5 pages the UE 3 with the requested information. For example, the RAN node 5 may page the UE 3 with a UE ID and the requested information.

[0132] Step 9. Upon receiving the paging message, the communication control module 362 in the UE3 recognizes the requested information and sends a signal to the lifeguard APL 363 to notify the received message (e.g., the requested information). The lifeguard APL 363 in the UE3 may analyze the received message (e.g., the requested information) and decide whether to ignore the message or to perform a reporting procedure. For example, the lifeguard APL 363 may decide to perform a reporting procedure based on the information included in the received message. For example, the lifeguard APL 363 may decide to perform a reporting procedure if the paging message includes the requested information. If the lifeguard APL 363 decides to perform a reporting procedure, the lifeguard APL 363 may perform the processing of steps 10 and 11, described below, as the reporting procedure. For example, the lifeguard APL 363 may decide to ignore the paging message if the paging message does not include the requested information.

[0133] Further, regardless of the above determination, the lifeguard APL363 may take one or more of the following actions: - Based on the received notification mode, the Lifeguard APL363 may notify / alert the user of the UE3 by playing a warning beep, playing a warning sound, or vibrating the UE3. When an alert message is received, the received message is displayed on the user display of the UE3 or read out by a voice generating application within the UE3.

[0134] Step 10. Step 10 is the same as step 6 in FIG.

[0135] Step 11. The UE 3 sends a service request message including the collected data to the AMF 70. The collected data includes any data collected in step 10.

[0136] Step 12. The AMF 70 sends a Namf_EventExposure_Notify message containing the UE ID and the collected data to the NEF 77. The UE ID in the Namf_EventExposure_Notify message may be the same as the UE ID received in step 6.

[0137] Step 13. The NEF 77 sends an Nnef_EventExposure_Notify message to the PSAP 202, including the UE ID and the collected data.

[0138] After step 13, the rescuer refers to the collected data and takes appropriate rescue action. For example, if PSAP202 stores the received SDP, PSAP202 may notify the rescuer (e.g., the rescuer's UE) that PSAP202 has collected data. The rescuer can then collect and refer to the data in the data storage in PSAP202.

[0139] (Third Example of the Second Aspect) A third example of the second aspect discloses a search procedure using a NEF and a PCF as specified in 3GPP TS 23.501 (Non-Patent Document 12), 3GPP TS 23.502 (Non-Patent Document 13), and TS 23.503 (Non-Patent Document 14). The search procedure is particularly useful for obtaining information about a user's location and status when the user is known to be or is considered to be in an emergency situation.

[0140] PSAP202 includes the following functions: - Alert message processing function: To support the search function, the PSAP 202 generates alert messages and sends them to the NEF 77. The PSAP 202 also receives collected data from the NEF 77.

[0141] Lifeguard APL363 in UE3 includes the following features: - Alert message response function: When a page containing an alert display (paging message, system broadcast, etc.) is received, the Lifeguard APL363 digests the received message and takes appropriate action based on the request in the received message.

[0142] Next, detailed processing of the second example of the second aspect will be described with reference to Fig. 9. Fig. 9 is a diagram showing a person discovery procedure using the NEF and PCF.

[0143] Steps 1 to 4. Steps 1 to 4 are the same as steps 1 to 4 in FIG.

[0144] Step 5. The NEF 77 sends an Npcf_EventExposure_Subscribe message containing the UE ID and the requested information to the PCF 73. The UE ID can be an IMSI or a SUPI. If the UE 3 roams out to another PLMN other than the home PLMN, the PCF 73 may be split into two parts: H-PCF (home) and V-PCF (visited). In this case, the H-PCF forwards the message received in step 5 to the V-PCF using the Npcf_EventExposure_Subscribe message.

[0145] Step 6. The PCF 73 sends a Nsmf_PDUSession_TransferMTData message containing the UE ID and the requested information to the SMF 71. The UE ID can be an IMSI or a SUPI. For example, if the V-PCF receives the Npcf_EventExposure_Subscribe message in step 5, the V-PCF can send a Nsmf_PDUSession_TransferMTData message to the SMF 71.

[0146] Step 7. The SMF 71 sends a Namf_Communication_N1N2MessageTransfer message containing the UE ID and the requested information to the AMF 70. The UE ID can be an IMSI or a SUPI.

[0147] Steps 8 to 12: Steps 8 to 12 are the same as steps 7 to 11 in FIG.

[0148] Step 13: The AMF 70 sends a Nsmf_PDUSession_SendMOData message to the SMF 71, including the UE ID and the collected data.

[0149] Step 14: The SMF 71 sends a Nsmf_PDUSession_TransferMOData message including the UE ID and the collected data to the PCF 73. If the UE 3 roams out to another PLMN, the PCF 73 may be split into two parts: an H-PCF and a V-PCF. In this case, the V-PCF forwards the message received in step 14 to the H-PCF using an Npcf_EventExposure_Notify message.

[0150] Step 15: The PCF 73 sends an Npcf_EventExposure_Notify message including the UE ID and the collected data to the NEF 77. For example, if the H-PCF receives the Nsmf_PDUSession_TransferMOData message in step 14, the H-PCF may send an Npcf_EventExposure_Notify message to the NEF 77.

[0151] Step 16: Step 16 is the same as step 13 in FIG.

[0152] After step 16, the rescuer refers to the collected data and takes appropriate rescue action. For example, if PSAP202 stores the received SDP, PSAP202 may notify the rescuer (e.g., the rescuer's UE) that PSAP202 has collected data. The rescuer can then collect and refer to the data in the data storage in PSAP202.

[0153] (Third aspect) This aspect discloses some examples of UE behavior when UE 3 receives a message from the network requesting data collection due to an emergency. According to this aspect, UE 3 provides information indicating whether a user of UE 3 is safe. The information indicating whether a user of UE 3 is safe may be used by rescuers or workers using PSAP 202 to rescue the user or to determine how to rescue the user.

[0154] This aspect is generally applicable to both the first and second aspects when the UE 3 receives a message in one or more of the following situations: - When UE3 receives the message broadcasted in step 4 of Figure 4. When the UE receives the SIP message in step 11-1 of Figure 5. - When UE3 receives the message broadcasted in step 4 of Figure 6. In step 4 of FIG. 7, when UE3 receives a SIP Invite message. In step 8 of FIG. 8, when UE 3 receives a paging message with the requested information. In step 9 of FIG. 9, when UE 3 receives a paging message with the requested information.

[0155] (First Example of the Third Aspect) A first example of the third aspect discloses a behavior of the UE when the user of the UE 3 is safe. The network in Fig. 10 may be a RAN node 5, an AMF 70, and / or an IMS 201. Fig. 10 illustrates the behavior of the UE when the user of the UE 3 is safe.

[0156] Next, detailed processing of the first example of the third aspect will be described with reference to FIG.

[0157] Step 1. The UE 3 receives a message indicating an emergency with requested information. The message in step 1 may be the broadcast message described above with reference to step 4 of Figure 4, the SIP message of step 11-1 of Figure 5, the broadcast message of step 4 of Figure 6, the SIP Invite message of step 4 of Figure 7, the paging message with requested information of step 8 of Figure 8, or the paging message with requested information of step 9 of Figure 9.

[0158] Step 2. Upon receiving the message in step 1, the UE 3 will play a loud alarm sound and / or use the voice generating application in the UE 3 to make a voice announcement saying "This is an emergency message. If you are safe, please press any button on your UE."

[0159] Step 3. The user of UE3 presses a button on the UE3 (if the user thinks he is safe).

[0160] Step 4. UE3 sends a message to the network including an appropriate UE ID of UE3, a UE location indicating the location of UE3, and a status set to "safe confirmed". The status being set to "safe confirmed" may indicate that the user of UE3 is safe. The UE ID, UE location, and status may be included in an appropriate information element of the message sent in step 4 (e.g., a disaster report information element, etc.).

[0161] For example, the UE 3 may obtain a UE ID (eg, the IMSI, SUPI, or MSISDN number of the UE 3) from a memory of the UE 3.

[0162] For example, the UE 3 may obtain the UE position by interacting with a GPS application within the UE 3.

[0163] For example, the UE3 may send a message if it detects that a user of the UE3 has pressed a button on the UE3 indicating that the user believes he or she is safe.

[0164] For example, if the network is a RAN node 5, the UE 3 may send the message of step 4 of Figure 10 to the RAN node 5. The information included in the message of step 4 of Figure 10 may be sent in a message as shown in step 9 of Figure 4. The information included in the message of step 4 of Figure 10 may be sent in a message as shown in step 11-3 of Figure 5. The information included in the message of step 4 of Figure 10 may be sent together with the collected data as shown in step 8 of Figure 6.

[0165] For example, if the network is IMS 201, then IMS 201 may forward the message received in step 4 to PSAP 202. The information included in the message of step 4 in Figure 10 may be transmitted in a message as shown in step 7 in Figure 7.

[0166] For example, if the network is AMF 70, AMF 70 may forward the message received in step 4 to PSAP 202 via NEF 77 as shown in Figure 8. The information included in the message of step 4 in Figure 10 may be transmitted in a message as shown in step 11 in Figure 8.

[0167] For example, if the network is AMF 70, AMF 70 may forward the message received in step 4 to PSAP 202 via SMF 71, PCF 73, and NEF 77, as shown in Figure 9. The information included in the message of step 4 in Figure 10 may be transmitted in a message as shown in step 12 in Figure 9.

[0168] (Second Example of the Third Aspect) A second example of the third aspect discloses a behavior of the UE when the user of the UE 3 is unconscious or cannot interact with the UE 3 for other reasons. The network in Figure 11 may be the RAN node 5, the AMF 70, and / or the IMS 201. Figure 11 illustrates the behavior of the UE when the user of the UE 3 is unconscious.

[0169] Next, detailed processing of the second example of the third aspect will be described with reference to FIG.

[0170] Step 1. UE 3 receives a message indicating an emergency with requested information. Step 1 may be the same as step 1 in FIG.

[0171] Step 2. Upon receiving the message in step 1, the UE 3 will play a loud alarm sound and / or use the voice generating application in the UE 3 to make a voice announcement saying "This is an emergency message. If you are safe, please press any button on your UE."

[0172] Step 3. The user of the UE3 is unable to press a button on the UE3 (eg, because the user is unconscious).

[0173] Step 4. After the warning process of step 2 (eg, 10 seconds after the warning process of step 2), UE3 launches the photo APL (application) of UE3 to take some photos.

[0174] Step 5. UE3 sends a message to the network including the UE ID of UE3, a UE location indicating the location of UE3, a photo, and a status set to "unsafe". The status being set to "unsafe" may indicate that the user of UE3 may be unconscious or unsafe. The UE ID, UE location, photo, and status may be included in an appropriate information element of the message sent in step 5 (e.g., a disaster report information element, etc.).

[0175] For example, if the network is a RAN node 5, the UE 3 may send the message of step 5 of Figure 11 to the RAN node 5. The information included in the message of step 5 of Figure 11 may be sent in a message as shown in step 9 of Figure 4. The information included in the message of step 5 of Figure 11 may be sent in a message as shown in step 11-3 of Figure 5. The information included in the message of step 5 of Figure 11 may be sent together with the collected data as shown in step 8 of Figure 6.

[0176] For example, if the network is IMS 201, then IMS 201 may forward the message received in step 4 to PSAP 202. The information included in the message of step 5 of Figure 11 may be transmitted in a message as shown in step 7 of Figure 7.

[0177] For example, if the network is AMF 70, AMF 70 may forward the message received in step 4 to PSAP 202 via NEF 77 as shown in Figure 8. The information included in the message of step 5 in Figure 11 may be transmitted in a message as shown in step 11 in Figure 8.

[0178] For example, if the network is AMF 70, AMF 70 may forward the message received in step 4 to PSAP 202 via SMF 71, PCF 73, and NEF 77, as shown in Figure 9. The information included in the message of step 5 in Figure 11 may be transmitted in a message as shown in step 12 in Figure 9.

[0179] (Third Example of the Third Aspect) A third example of the third aspect discloses a behavior of the UE when a user of the UE 3 is unconscious or cannot interact with the UE 3 for other reasons. In this example, the UE 3 has a suitable health measurement function. For example, the UE 3 may be a smartwatch UE or may be connected to a smartwatch worn by the user.

[0180] The network in Figure 12 may be a RAN node 5, an AMF 70, and / or an IMS 201. Figure 12 illustrates the behavior of a UE 3 equipped with a health measurement function when the user of the UE is unconscious.

[0181] Next, detailed processing of the third example of the third aspect will be described with reference to FIG.

[0182] Step 1. UE 3 receives a message indicating an emergency with the requested information. Step 1 may be the same as step 1 in FIG.

[0183] Step 2. Upon receiving the message in step 1, the UE 3 will play a loud alarm sound and / or use the voice generating application in the UE 3 to make a voice announcement saying "This is an emergency message. If you are safe, please press any button on your UE."

[0184] Step 3. The user of the UE3 is unable to press a button on the UE3 (eg, because the user is unconscious).

[0185] Step 4. After the warning process of step 2 (for example, 10 seconds after the warning process of step 2), the UE 3 performs vital measurement to obtain vital data of the user of the UE. The vital data previously measured in the memory of the UE 3 may be obtained.

[0186] Step 5. UE3 sends a message to the network including the UE ID of UE3, a UE location indicating the location of UE3, the vital data obtained in step 4, and a status set to "vitals checked". The status set to "vitals checked" may indicate that the vital data has been checked by a user. The status set to "vitals checked" may indicate that the vital data has been confirmed. The UE ID, UE location, vital data, and status may be included in an appropriate information element (e.g., a disaster report information element, etc.) of the message sent in step 5.

[0187] For example, if the network is a RAN node 5, the UE 3 may send the message of step 5 of Figure 12 to the RAN node 5. The information included in the message of step 5 of Figure 12 may be sent in a message as shown in step 9 of Figure 4. The information included in the message of step 5 of Figure 12 may be sent in a message as shown in step 11-3 of Figure 5. The information included in the message of step 5 of Figure 12 may be sent together with the collected data as shown in step 8 of Figure 6.

[0188] For example, if the network is IMS 201, then IMS 201 may forward the message received in step 4 to PSAP 202. The information included in the message of step 5 of Figure 12 may be transmitted in a message as shown in step 7 of Figure 7.

[0189] For example, if the network is AMF 70, AMF 70 may forward the message received in step 4 to PSAP 202 via NEF 77 as shown in Figure 8. The information included in the message of step 5 in Figure 12 may be transmitted in a message as shown in step 11 in Figure 8.

[0190] For example, if the network is AMF 70, AMF 70 may forward the message received in step 4 to PSAP 202 via SMF 71, PCF 73, and NEF 77, as shown in Figure 9. The information included in the message of step 5 in Figure 12 may be transmitted in a message as shown in step 12 in Figure 9.

[0191] (System Overview) FIG. 13 illustrates a schematic diagram of a mobile (cellular or wireless) telecommunications system 1 to which the above-described aspects can be applied.

[0192] The telecommunication system 1 represents a system overview capable of end-to-end communication, for example, a UE 3 (or user equipment, “mobile device”, 3) communicating with other UEs 3 or service servers in a data network 20 via respective (R)AN nodes 5 and a core network 7.

[0193] The (R)AN node 5 supports any wireless access including 5G radio access technologies (RATs), E-UTRA radio access technologies, RATs beyond 5G, 6G RATs, and non-3GPP RATs, including wireless local area network (WLAN) technologies defined by the Institute of Electrical and Electronics Engineers (IEEE).

[0194] The (R)AN node 5 may be divided into one or more Radio Units (RU), one or more Distributed Units (DU), and one or more Centralized Units (CU). In some aspects, each of the units may be connected to each other to form the (R)AN node 5 by adopting an architecture defined by the Open RAN (O-RAN) Alliance, where the above units are referred to as O-RU, O-DU, and O-CU, respectively.

[0195] The (R)AN node 5 may be split into a control plane function and a user plane function. Additionally, multiple user plane functions may be allocated to support communications. In some aspects, user traffic may be distributed across multiple user plane functions, and user traffic on each user plane function may be aggregated at both the UE 3 and the (R)AN node 5. This split architecture may be referred to as "dual connectivity" or "multi-connectivity."

[0196] The (R)AN node 5 may also support communications using satellite access. In some aspects, the (R)AN node 5 may support at least one of satellite access and terrestrial access. Satellite access may also be referred to as non-terrestrial access.

[0197] The (R)AN node 5 may also be referred to as an access node for non-wireless access, which may include, for example, fixed-line access as defined by the Broadband Forum (BBF) and / or optical access as defined by Innovative Optical and Wireless Networks (IOWN).

[0198] The core network 7 may include logical nodes (or "functions") for supporting communications in the telecommunications system 1. For example, the core network 7 may be a 5G Core Network (5GC) including control plane functions and user plane functions, among other functions. Each function within a logical node may be considered a network function. A network function may be provided to another node by adapting a service-based architecture (SBA).

[0199] Network functions can be deployed as distributed, redundant, stateless, and scalable functions providing services from several locations and several running instances in each location by adapting network virtualization technologies defined by the European Telecommunications Standards Institute, Network Functions Virtualization (ETSI NFV).

[0200] The core network 7 may support so-called non-public network (NPN) functionality. An NPN may be a Standalone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).

[0201] As is known, the UE 3 may move in and out of areas (i.e., radio cells) served by the (R)AN nodes 5 as the UE 3 moves within a geographic area covered by the telecommunication system 1. To track the UE 3 and facilitate movement between different (R)AN nodes 5, the core network 7 includes at least one Access and Mobility Management Function (AMF) 70. The AMF 70 communicates with the (R)AN nodes 5 coupled to the core network 7. In some core networks, the AMF 70 may be replaced by a Mobility Management Entity (MME) or an Beyond 5G or 6G mobility management node.

[0202] In this example, for purposes of illustration, the core network 7 also includes, among others, a session management function (SMF) 71, a user plane function (UPF) 72, a policy control function (PCF) 73, an authentication server function (AUSF) 74, a unified data management (UDM) 75, a network data analysis function (NWDAF) 76, a network publishing function (NEF) 77, and a network slice admission control function (NSACF) 78. When the UE 3 is roaming in a visited public land mobile network (VPLMN), the home public land mobile network (HPLMN) of the UE 3 provides the roaming out UE 3 with the UDM 75, as well as at least some of the functionality of the SMF 71, UPF 72, and PCF 73.

[0203] The UE 3 and the respective serving (R)AN node 5 are connected via a suitable air interface (such as the so-called "Uu" interface). Adjacent (R)AN nodes 5 are connected to each other via suitable (R)AN node 5 to (R)AN node interfaces (such as the so-called "Xn" interfaces). Each (R)AN node 5 is also connected to a node in the core network 7 (such as a so-called core network node) via a suitable interface (such as the so-called "N2" / "N3" interface). From the core network 7, a connection is also provided to a data network 20. The data network 20 may be the Internet, a public network, an external network, a private network, or an internal network of the PLMN. If the data network 20 is provided by a PLMN operator or a Mobile Virtual Network Operator (MVNO), IP Multimedia Subsystem (IMS) services may be provided by that data network 20. The UE 3 may connect to the data network 20 using IPv4, IPv6, IPv4v6, Ethernet, or unstructured data types. The data network 20 may include the IMS 201 and PSAP 202 nodes described above.

[0204] The "Uu" interface may include the control plane of the Uu interface and the user plane of the Uu interface.

[0205] The user plane of the Uu interface is responsible for carrying user traffic between the UE 3 and the serving (R)AN node 5. The user plane of the Uu interface may have a hierarchical structure with SDAP, PDCP, RLC, and MAC sublayers over the physical connection.

[0206] The control plane of the Uu interface is responsible for establishing, modifying and releasing the connection between the UE 3 and the serving (R)AN node 5. The control plane of the Uu interface may have a hierarchical structure with RRC, PDCP, RLC and MAC sublayers over the physical connection.

[0207] For example, to support AS signaling, the following messages may be communicated over the RRC layer: - RRC SETUP REQUEST message: This message is sent from the UE 3 to the (R)AN node 5. In addition to the parameters disclosed by the aspects described in this disclosure, the following parameters may be included together in the RRC SETUP REQUEST message: #Establishment cause and ue-identity. The ue-identity can take the value of ng-5G-S-TMSI-Part1 or a random value. - RRC SETUP message: This message is sent from the (R)AN node 5 to the UE 3. In addition to the parameters disclosed by the aspects described in this disclosure, the following parameters may be included together in the RRC SETUP message: #Master cell group and radio bearer configuration - RRC Setup Complete message: This message is sent from the UE 3 to the (R)AN node 5. In addition to the parameters disclosed by the aspects described in this disclosure, the following parameters may be included together in the RRC Setup Complete message: #guami-type, iab-node-indication, idle-measurements-available, mobility-state, ng-5G-S-TMSI-part-2, registered-AMF, selected-PLMN-identity

[0208] The UE 3 and the AMF 70 are connected via an appropriate interface (e.g., a so-called N1 interface, etc.). The N1 interface is an interface for communicating between the UE 3 and the AMF 70 using NAS signaling. The N1 interface may be established via 3GPP access and / or non-3GPP access. For example, the following messages may be communicated via the N1 interface: - Registration Request Message: This message is sent from the UE 3 to the AMF 70. In addition to the parameters disclosed by the aspects described in the present disclosure, the following parameters may be included together in the Registration Request message: #5GS registration type, ngKSI, 5GS mobile identity, non-current native NAS key set identifier, 5GMM capabilities, UE security capabilities, requested NSSAI, last visited registered TAI, S1 UE network capabilities, uplink data status, PDU session status, MICO indication, UE status, additional GUTI, allowed PDU session status, UE usage configuration, requested DRX parameters, EPS NAS message container, LADN indication, payload container type, payload container, network slicing indication, 5GS update type, mobile station class mark 2, supported codecs, NAS message container, EPS bearer context status, requested extended DRX parameters, T3324 value, UE radio capability ID, requested mapped NSSAI, requested information, requested WUS assistance information, N5GC indication and requested NB-N1 DRX parameters. - Registration Accept Message: This message is sent from the AMF 70 to the UE 3. In addition to the parameters disclosed by the aspects described in the present disclosure, the following parameters may be included together in the Registration Accept message: #5GS Registration Result, 5G-GUTI, Equivalent PLMN, TAI List, Allowed NSSAI, Rejected NSSAI, Configured NSSAI, 5GS Network Capability Support, PDU Session Status, PDU Session Reactivation Result, PDU Session Reactivation Result Error Cause, LADN Information, MICO Indication, Network Slicing Indication, Service Area List, T3512 Value, Non-3GPP Registration Timer Value, T3502 Value, Emergency Number List, Extended Emergency Number List, SOR Transparent Container, EAP Message, NSSAI Inclusion Mode, Operator Defined Access Category Definition, Negotiated DRX Parameters, Non-3GPP NW policy, EPS bearer context status, negotiated extended DRX parameters, T3447 value, T3448 value, T3324 value, UE radio capability ID, UE radio capability ID removal indication, pending NSSAI, ciphering key data, CAG information list, truncated 5G-S-TMSI configuration, negotiated WUS assistance information, negotiated NB-N1 mode DRX parameters, and extended rejected NSSAI. - Registration Complete Message: This message is sent from the UE 3 to the AMF 70. In addition to the parameters disclosed by the aspects described in the present disclosure, the following parameters may be included together in the Registration Complete message: #SORTransparentContainer. -Authentication Request Message: This message is sent from the AMF 70 to the UE 3. In addition to the parameters disclosed by the aspects described in this disclosure, the Authentication Request message may include the following parameters together: #ngKSI, ABBA, authentication parameter RAND (5G authentication challenge), authentication parameter AUTN (5G authentication challenge), and EAP message. -Authentication Response Message: This message is sent from the UE 3 to the AMF 70. In addition to the parameters disclosed by the aspects described in this disclosure, the authentication response message may be populated with the following parameters: #Authentication response message identity, authentication response parameters, and EAP message. -Authentication Result Message: This message is sent from the AMF 70 to the UE 3. In addition to the parameters disclosed by the aspects described in this disclosure, the Authentication Result Message may be populated with the following parameters: #ngKSI, EAP Message and ABBA. -Authentication Failure Message: This message is sent from the UE 3 to the AMF 70. In addition to the parameters disclosed by the aspects described in this disclosure, the Authentication Failure Message may be populated with the following parameters: #Authentication failure message identifier, 5GMM cause and authentication failure parameters. -Authentication Rejection Message: This message is sent from the AMF 70 to the UE 3. In addition to the parameters disclosed by the aspects described in this disclosure, the authentication rejection message may be populated with the following parameters: #EAPMessage. - Service Request Message: This message is sent from the UE 3 to the AMF 70. In addition to the parameters disclosed by the aspects described in the present disclosure, the following parameters may be taken together in the Service Request message: #ngKSI, Service Type, 5G-S-TMSI, Uplink Data Status, PDU Session Status, Allowed PDU Session Status, NAS Message Container. - Service Acceptance Message: This message is sent from the AMF 70 to the UE 3. In addition to the parameters disclosed by the aspects described in this disclosure, the following parameters may be taken together in the Service Acceptance Message: #PDU session status, PDU session reactivation result, PDU session reactivation result error cause, EAP message and T3448 value. - Service Rejection Message: This message is sent from the AMF 70 to the UE 3. In addition to the parameters disclosed by the aspects described in this disclosure, the following parameters may be taken together in the Service Rejection Message: #5 GMM cause, PDU session status, T3346 value, EAP message, T3448 value, and CAG information list. -Configuration Update Command Message: This message is sent from the AMF 70 to the UE 3. In addition to the parameters disclosed by the aspects described in this disclosure, the following parameters may be taken together in the Configuration Update Command message: #Configuration update instruction, 5G-GUTI, TAI list, Allowed NSSAI, Service area list, Network full name, Network short name, Local time zone Universal Coordinated Time and local time zone, Network daylight saving time, LADN information, MICO instruction, Network slicing instruction, Configured NSSAI, Rejected NSSAI, Operator defined access category definition, SMS instruction, T3447 value, CAG information list, UE radio capability ID, UE radio capability ID deletion instruction, 5GS registration result, Truncated 5G-S-TMSI configuration, Additional configuration instruction and Extended rejected NSSAI. -Configuration Update Complete message: This message is sent from the UE 3 to the AMF 70. In addition to the parameters disclosed by the aspects described in the present disclosure, the following parameters may be taken together in the Configuration Update Complete message: #Configuration update complete message identification information.

[0209] (User Equipment (UE)) FIG. 14 is a block diagram showing the main components of a UE 3 (mobile device 3). As shown, the UE 3 includes a transceiver circuit 31 operable to transmit signals to and receive signals from a connected node via one or more antennas 32. The UE 3 may also include a user interface 34 for inputting information from the outside or outputting information to the outside. Although not necessarily shown in FIG. 14, the UE 3 may have all the usual functions of a conventional mobile device, which may be provided by any one or any combination of hardware, software, and firmware, as appropriate. The software may be pre-installed in the memory and / or may be downloaded, for example, via a telecommunications network or from a removable data storage device (RMD). The control unit 33 controls the operation of the UE 3 according to the software stored in the memory 36. The software includes, among other things, an operating system 361 and a communication control module 362 having at least a transceiver control module 3621. The communication control module 362 (using its transceiver control module 3621) is responsible for handling (generating / sending / receiving) signaling and uplink / downlink data packets between the UE 3 and other nodes such as the (R)AN node 5 and the AMF 70. Such signaling may include, for example, appropriately formatted signaling messages (e.g., registration request messages and associated response messages) relating to access and mobility management procedures (for the UE 3). The control unit 33 interoperates with one or more Universal Subscriber Identity Modules (USIMs) 35. If equipped with multiple USIMs 35, the control unit 33 may activate only one USIM 35 or may activate multiple USIMs 35 simultaneously.

[0210] The memory 36 may include a lifeguard APL 363. The control unit 33 may execute the lifeguard APL 363 to execute the processing of the UE 3 described in this disclosure. The UE 3 may include associated data storage 3631. The memory 36 may include data storage 3631 (e.g., as part of the Lifeguard APL 363).

[0211] The UE 3 may, for example, support a non-public network (NPN), which may be a standalone non-public network (SNPN) or a public network integrated NPN (PNI-NPN). UE3 may be, for example, an item of equipment for production or manufacturing and / or energy-related machinery (e.g., equipment or machinery such as boilers; engines; turbines; solar panels; wind turbines; hydroelectric generators; thermal power plants; nuclear generators; batteries; nuclear systems and / or related equipment; heavy electrical machinery; pumps including vacuum pumps; compressors; fans; blowers; hydraulic equipment; pneumatic equipment; metal processing machinery; manipulators; robots and / or application systems thereof; tools; dies or molds; rolls; conveying equipment; elevators; material handling equipment; textile machinery; sewing equipment; printing and / or related machinery; paper converting equipment; chemical machinery; mining machinery and / or construction machinery and / or related equipment; machinery and / or implements for the agricultural, forestry and / or fisheries industries; safety and / or environmental protection equipment; tractors; precision bearings; chains; gears; power transmission equipment; lubrication equipment; valves; pipe fittings; and / or application systems for any of the foregoing equipment or machines, etc.).

[0212] UE 3 may be, for example, an item of transportation equipment (e.g., transportation equipment such as rolling stock; automobiles; motorcycles; bicycles; trains; buses; carts; human-powered vehicles; ships and other watercraft; aircraft; rockets; satellites; drones; balloons, etc.).

[0213] The UE 3 may be, for example, an item of information and communications equipment (eg, information and communications equipment such as electronic computers and related equipment; communications and related equipment; electronic components, etc.).

[0214] UE3 may be, for example, a refrigerator, a refrigerator application product, an item of goods and / or service industry equipment, a vending machine, an automated service machine, an office machine or equipment, consumer electronics and electronic devices (e.g., consumer electronics such as audio equipment; video equipment; speakers; radios; televisions; microwave ovens; rice cookers; coffee machines; dishwashers; washing machines; dryers; electronic fans or related equipment; vacuum cleaners, etc.).

[0215] UE 3 may be, for example, an electrical application system or device (eg, an electrical application system or device such as an x-ray system; a particle accelerator; a radioisotope device; a sonic device; an electromagnetic application device; an electronic power application device, etc.).

[0216] UE3 may be, for example, an electronic lamp, a lighting fixture, a measuring instrument, an analyzer, a tester, or surveying or sensing equipment (e.g., surveying or sensing equipment such as a smoke alarm; a motion sensor; a radio frequency tag; etc.), a watch or clock, inspection equipment, optical equipment, medical equipment and / or systems, a weapon, an item of cutlery, a hand tool, etc.

[0217] UE 3 may be, for example, a wireless-equipped personal digital assistant or associated equipment (eg, a wireless card or module designed to be attached to or inserted into another electronic device (eg, a personal computer, electrical measuring instrument)). The UE3 may be part of a device or system that uses a variety of wired and / or wireless communication technologies to provide the applications, services, and solutions described below with respect to the Internet of Things (IoT).

[0218] Internet of Things devices (or "things") can be equipped with appropriate electronics, software, sensors, network connectivity, etc. that enable these devices to collect and exchange data with each other and with other communicating devices. IoT devices can include automated equipment that follows software instructions stored in internal memory. IoT devices can operate without the need for human supervision or interaction. IoT devices can also remain stationary and / or inactive for long periods of time. IoT devices may be implemented as part of (generally) stationary equipment. IoT devices may also be embedded in non-stationary equipment (e.g., vehicles) or attached to animals or people being monitored / tracked.

[0219] It will be understood that IoT technologies may be implemented on any communication device capable of connecting to a communication network to transmit / receive data, regardless of whether such communication device is controlled by human input or software instructions stored in memory.

[0220] It will be appreciated that an IoT device may also be referred to as a Machine Type Communication (MTC) device or a Machine to Machine (M2M) communication device or a Narrowband IoT UE (NB-IoT UE). It will be appreciated that the UE 3 may support one or more IoT or MTC applications.

[0221] The UE 3 may be a smartphone or a wearable device (e.g., smart glasses, a smart watch, a smart ring, or a hearable device).

[0222] The UE3 may be an automobile, a connected automobile, an autonomous automobile, a vehicle device, a motorcycle, or a V2X (Vehicle to Everything) communication module (e.g., a vehicle-to-vehicle communication module, a vehicle-to-infrastructure communication module, a vehicle-to-people communication module, and a vehicle-to-network communication module).

[0223] ((R)AN node) FIG. 15 is a block diagram illustrating the main components of an exemplary (R)AN node 5, e.g., a base station ("eNB" in LTE, "gNB" in 5G, 5G base station onwards, 6G base station). As shown, the (R)AN node 5 includes a transceiver circuit 51 operable to transmit signals to and receive signals from connected UEs 3 via one or more antennas 52, and to transmit signals to and receive signals from other network nodes (directly or indirectly) via a network interface 53. A controller 54 controls the operation of the (R)AN node 5 according to software stored in memory 55. The software may be pre-installed in the memory and / or may be downloaded, for example, via a telecommunications network or from a removable data storage device (RMD). The software includes, among other things, an operating system 551 and a communication control module 552 having at least a transceiver control module 5521.

[0224] The communication control module 552 (using its transceiver control submodule) is responsible for handling (generating / sending / receiving) signaling between the (R)AN node 5 and other nodes such as the UE 3, another (R)AN node 5, the AMF 70, and the UPF 72 (e.g., directly or indirectly). The signaling may include, for example, appropriately formatted signaling messages related to the radio connection and connectivity with the core network 7 (for a particular UE 3), in particular connection establishment and maintenance (e.g., RRC connection establishment and other RRC messages), NG Application Protocol (NGAP) messages (i.e., messages over the N2 reference point) and Xn Application Protocol (XnAP) messages (i.e., messages over the Xn reference point), etc. Such signaling may also include, for example, broadcast information in the transmission case (e.g., master information and system information).

[0225] When implemented, the control unit 54 is also configured (by software or hardware) to handle related tasks such as UE mobility estimation and / or motion trajectory estimation.

[0226] The (R)AN node 5 may support a non-public network (NPN), which may be a stand-alone non-public network (SNPN) or a public network integrated NPN (PNI-NPN).

[0227] The memory 55 may include a lifeguard APL 553. The controller 54 may execute the lifeguard APL 553 to perform the processing of the RAN node 5 described in this disclosure.

[0228] The RAN node 5 may include data storage 5531. The memory 55 may include the data storage 5531 (e.g., as part of the Lifeguard APL 553).

[0229] (System overview of (R)AN Node 5 based on O-RAN architecture) FIG. 16 illustrates diagrammatically an (R)AN node 5 based on an O-RAN architecture to which aspects of the (R)AN node 5 are applicable.

[0230] The (R)AN node 5 based on the O-RAN architecture represents a system overview in which the (R)AN node is divided into a radio unit (RU) 60, a distributed unit (DU) 61, and a centralized unit (CU) 62. In some aspects, each unit can be combined. For example, the RU 60 can be combined / combined with the DU 61 as a combined / combined unit, and the DU 61 can be combined / combined with the CU 62 as another combined / combined unit. Any function in the description of a unit (e.g., one of the RU 60, DU 61, and CU 62) can be implemented in the combined / combined unit above. Furthermore, the CU 62 can be separated into two functional units, such as a CU control plane (CP) and a CU user plane (UP). The CU CP has a control plane function in the (R)AN node 5. The CU UP has a user plane function in the (R)AN node 5. Each CU CP is connected to a CU UP via an appropriate interface (such as a so-called "E1" interface).

[0231] The UE 3 and the respective serving RU 60 are connected via a suitable air interface (such as, for example, the so-called "Uu" interface). Each RU 60 is connected to a DU 61 via a suitable interface (such as, for example, the so-called "fronthaul", "open fronthaul", "F1" interface). Each DU 61 is connected to a CU 62 via a suitable interface (such as, for example, the so-called "midhaul", "open midhaul", "E2" interface). Each CU 62 is also connected to a node in the core network 7 (such as a so-called core network node) via a suitable interface (such as, for example, the so-called "backhaul", "open backhaul", "N2" / "N3" interface). Furthermore, the user plane part of the DU 61 may also be connected to the core network node 7 via a suitable interface (such as, for example, the so-called "N3" interface).

[0232] Depending on the functionality divided among the RU 60, DU 61, and CU 62, each unit provides a part of the functionality provided by the (R)AN node 5. For example, the RU 60 may provide functionality for communicating with the UE 3 over the air interface, the DU 61 may provide functionality for supporting the MAC and RLC layers, and the CU 62 may provide functionality for supporting the PDCP, SDAP, and RRC layers.

[0233] (Radio Unit (RU)) FIG. 17 is a block diagram illustrating the main components of an exemplary RU 60, e.g., the RU portion of a base station (eNB in ​​LTE, gNB in ​​5G, 5G base station onwards, 6G base station). As shown, the RU 60 includes a transceiver circuit 601 operable to transmit signals to and receive signals from a connected UE 3 via one or more antennas 602, and to transmit signals to and receive signals from other network nodes or units (directly or indirectly) via a network interface 603. A controller 604 controls the operation of the RU 60 according to software stored in memory 605. The software may be pre-installed in the memory and / or may be downloaded, e.g., via a telecommunications network or from a removable data storage device (RMD). The software includes, among other things, an operating system 6051 and a communication control module 6052 having at least a transceiver control module 60521.

[0234] The communication control module 6052 is responsible for handling (generating / sending / receiving) signaling (e.g., directly or indirectly) between the RU 60 (using its transceiver control sub-module) and other nodes or units, such as a UE 3, another RU 60, and a DU 61. The signaling may include, for example, appropriately formatted signaling messages relating to the radio connection and connectivity with the RU 60 (for a particular UE 3), in particular the MAC and RLC layers.

[0235] When implemented, the controller 604 is also configured (by software or hardware) to handle related tasks such as UE mobility estimation and / or motion trajectory estimation.

[0236] The RU 60 may support a non-public network (NPN), which may be a stand-alone non-public network (SNPN) or a public network integrated NPN (PNI-NPN).

[0237] As mentioned above, the RU 60 can be integrated / combined with the DU 61 as an integrated / combined unit. Any function in the description of the RU 60 can be implemented in the integrated / combined unit.

[0238] (Distributed Unit (DU)) FIG. 18 is a block diagram illustrating the main components of an exemplary DU 61, e.g., a DU section of a base station (eNB in ​​LTE, gNB in ​​5G, 5G base station onward, 6G base station). As shown, the device includes a transceiver circuit 611 operable to transmit signals to and receive signals from other nodes or units (including RU 60) via a network interface 612. A control unit 613 controls the operation of the DU 61 according to software stored in memory 614. The software may be pre-installed in the memory 614 and / or may be downloaded, e.g., via a telecommunications network or from a removable data storage device (RMD). The software includes, among other things, an operating system 6141 and a communication control module 6142 having at least a transceiver control module 61421. The communication control module 6142 (using its transceiver control module 61421) is responsible for handling (generating / sending / receiving) signaling between the DU 61 and other nodes or units, such as the RU 60 and other nodes and units.

[0239] The DU 61 may support a non-public network (NPN), which may be a stand-alone non-public network (SNPN) or a public network integrated NPN (PNI-NPN).

[0240] As mentioned above, the RU 60 can be integrated / combined with the DU 61 or the CU 62 as an integrated / combined unit. Any function in the description of the DU 61 can be implemented in one of the above integrated / combined units.

[0241] (Centralized Unit (CU)) FIG. 19 is a block diagram illustrating the main components of an exemplary CU 62, e.g., the CU portion of a base station (eNB in ​​LTE, gNB in ​​5G, 5G base station onward, 6G base station). As shown, the device includes a transceiver circuit 621 operable to transmit signals to and receive signals from other nodes or units (including the DU 61) via a network interface 622. A controller 623 controls the operation of the CU 62 according to software stored in a memory 624. The software may be pre-installed in the memory 624 and / or may be downloaded, e.g., via a telecommunications network or from a removable data storage device (RMD). The software includes, among other things, an operating system 6241 and a communication control module 6242 having at least a transceiver control module 62421. The communication control module 6242 (using its transceiver control module 62421) is responsible for handling (generating / sending / receiving) signaling between the CU 62 and other nodes or units, such as the DU 61 and other nodes and units.

[0242] The CU 62 may support a non-public network (NPN), which may be a stand-alone non-public network (SNPN) or a public network integrated NPN (PNI-NPN).

[0243] As mentioned above, the CU 62 can be integrated / combined with the DU 61 as an integrated / combined unit. Any functionality in the description of the CU 62 can be implemented in the integrated / combined unit.

[0244] (AMF) FIG. 20 is a block diagram illustrating the main components of the AMF 70. As shown, the apparatus includes a transceiver circuit 701 operable to transmit signals to and receive signals from other nodes (including the UE 3) via a network interface 702. A controller 703 controls the operation of the AMF 70 according to software stored in a memory 704. The software may be pre-installed in the memory 704 and / or may be downloaded, for example, via a telecommunications network or from a removable data storage device (RMD). The software includes, among other things, an operating system 7041 and a communication control module 7042 having at least a transceiver control module 70421. The communication control module 7042 is responsible for handling (generating / sending / receiving) signaling between the AMF 70 (using its transceiver control module 70421) and other nodes such as the UE 3 (e.g., via the (R)AN node 5) and other core network nodes (including core network nodes in the HPLMN of the UE 3 when the UE 3 is roaming in). Such signaling may include, for example, appropriately formatted signaling messages related to access and mobility management procedures (for UE 3) (e.g., registration request messages and associated response messages).

[0245] The AMF 70 may support a non-public network (NPN), which may be a stand-alone non-public network (SNPN) or a public network integrated NPN (PNI-NPN).

[0246] (SMF) FIG. 21 is a block diagram illustrating the main components of the SMF 71. As shown, the apparatus includes a transceiver circuit 711 operable to transmit signals to and receive signals from other nodes (including the AMF 70) via a network interface 712. A controller 713 controls the operation of the SMF 71 according to software stored in a memory 714. The software may be pre-installed in the memory 714 and / or may be downloaded, for example, via a telecommunications network or from a removable data storage device (RMD). The software includes, among other things, an operating system 7141 and a communication control module 7142 having at least a transceiver control module 71421. The communication control module 7142 (using its transceiver control module 71421) is responsible for handling (generating / sending / receiving) signaling between the SMF 71 and other nodes such as the UPF 72 and other core network nodes (including core network nodes in the HPLMN of the UE 3 when the UE 3 is roaming in). Such signaling may include, for example, appropriately formatted signaling messages (for UE 3) related to session management procedures (e.g., HyperText Transfer Protocol (HTTP) restful methods based on a service-based interface).

[0247] The SMF 71 may support a non-public network (NPN), which may be a stand-alone non-public network (SNPN) or a public network integrated NPN (PNI-NPN).

[0248] (UPF) FIG. 22 is a block diagram illustrating the main components of the UPF 72. As shown, the apparatus includes a transceiver circuit 721 operable to transmit signals to and receive signals from other nodes (including the SMF 71) via a network interface 722. A controller 723 controls the operation of the UPF 72 according to software stored in a memory 724. The software may be pre-installed in the memory 724 and / or may be downloaded, for example, via a telecommunications network or from a removable data storage device (e.g., a removable memory device (RMD)). The software includes, among other things, an operating system 7241 and a communication control module 7242 having at least a transceiver control module 72421. The communication control module 7242 (using its transceiver control module 72421) is responsible for handling (generating / sending / receiving) signaling between the UPF 72 and other nodes such as the SMF 71 and other core network nodes (including core network nodes in the HPLMN of the UE 3 when the UE 3 is roaming in). Such signaling may include, for example, appropriately formatted signaling messages related to user data processing (for the UE 3) (e.g., GPRS Tunneling Protocol (GTP) for the user plane).

[0249] The UPF 72 may support a non-public network (NPN), which may be a stand-alone non-public network (SNPN) or a public network integrated NPN (PNI-NPN).

[0250] A communication device performing the functions of a co-located gNB-CU-UP and UPF, or a communication device performing the functions of a co-located gNB-CU-UP and UPF, or a communication device performing the functions of a gNB-CU-UP and a UPF, may have the same components as UPF72.

[0251] (PCF) FIG. 23 is a block diagram illustrating the main components of the PCF 73. As shown, the apparatus includes a transceiver circuit 731 operable to transmit signals to and receive signals from other nodes (including the AMF 70) via a network interface 732. A controller 733 controls the operation of the PCF 73 according to software stored in a memory 734. The software may be pre-installed in the memory 734 and / or may be downloaded, for example, via a telecommunications network or from a removable data storage device (e.g., a removable memory device (RMD)). The software includes, among other things, an operating system 7341 and a communication control module 7342 having at least a transceiver control module 73421. The communication control module 7342 (using its transceiver control module 73421) is responsible for handling (generating / sending / receiving) signaling between the PCF 73 and other nodes such as the AMF 70 and other core network nodes (including core network nodes in the HPLMN of the UE 3 when the UE 3 is roaming in). Such signaling may include, for example, appropriately formatted signaling messages (for UE 3) related to policy management procedures (e.g., HTTP restful methods based on service-based interfaces).

[0252] The PCF 73 may support a non-public network (NPN), which may be a Standalone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN). The H-PCF and V-PCF may include similar components as the PCF 73.

[0253] (AUSF) FIG. 24 is a block diagram illustrating the main components of the AUSF 74. As shown, the apparatus includes a transceiver circuit 741 operable to transmit signals to and receive signals from other nodes (including the UDM 75) via a network interface 742. A controller 743 controls the operation of the AUSF 74 according to software stored in a memory 744. The software may be pre-installed in the memory 744 and / or may be downloaded, for example, via a telecommunications network or from a removable data storage device (e.g., a removable memory device (RMD)). The software includes, among other things, an operating system 7441 and a communication control module 7442 having at least a transceiver control module 74421. The communication control module 7442 (using its transceiver control module 74421) is responsible for handling (generating / sending / receiving) signaling between the AUSF 74 and other nodes such as the AMF 70 and other core network nodes (including core network nodes in the HPLMN of the UE 3 when the UE 3 is roaming in). Such signaling may include, for example, appropriately formatted signaling messages (for UE 3) related to policy management procedures (e.g., HTTP restful methods based on service-based interfaces).

[0254] The AUSF 74 may support a non-public network (NPN), which may be a stand-alone non-public network (SNPN) or a public network integrated NPN (PNI-NPN).

[0255] (UDM) FIG. 25 is a block diagram illustrating the main components of the UDM 75. As shown, the device includes a transceiver circuit 751 operable to transmit signals to and receive signals from other nodes (including the AMF 70) via a network interface 752. A controller 753 controls the operation of the UDM 75 according to software stored in a memory 754. The software may be pre-installed in the memory 754 and / or may be downloaded, for example, via a telecommunications network or from a removable data storage device (RMD). The software includes, among other things, an operating system 7541 and a communication control module 7542 having at least a transceiver control module 75421. The communication control module 7542 (using its transceiver control module 75421) is responsible for handling (generating / sending / receiving) signaling between the UDM 75 and other nodes such as the AMF 70 and other core network nodes (including core network nodes in the VPLMN of the UE 3 when the UE 3 is roaming out). Such signaling may include, for example, appropriately formatted signaling messages (for the UE 3) related to mobility management procedures (eg, HTTP restful methods based on a service-based interface).

[0256] The UDM 75 may support a non-public network (NPN), which may be a stand-alone non-public network (SNPN) or a public network integrated NPN (PNI-NPN).

[0257] (NWDAF) FIG. 26 is a block diagram illustrating the main components of the NWDAF 76. As shown, the device includes a transceiver circuit 761 operable to transmit signals to and receive signals from other nodes (including the AMF 70) via a network interface 762. A controller 763 controls the operation of the NWDAF 76 according to software stored in a memory 764. The software may, for example, be pre-installed in the memory 764 and / or downloaded via a telecommunications network or from a removable data storage device (e.g., a removable memory device (RMD)). The software includes, among other things, an operating system 7641 and a communication control module 7642 having at least a transceiver control module 76421. The communication control module 7642 (using its transceiver control module 76421) is responsible for handling (generating / sending / receiving) signaling between the NWDAF 76 and other nodes such as the AMF 70 and other core network nodes (including core network nodes in the HPLMN of the UE 3 when the UE 3 is roaming in). Such signaling may include, for example, appropriately formatted signaling messages (for UE 3) related to network data analysis function procedures (e.g., HTTP restful methods based on service-based interfaces).

[0258] The NWDAF 76 may support a non-public network (NPN), which may be a stand-alone non-public network (SNPN) or a public network integrated NPN (PNI-NPN).

[0259] (NEF) FIG. 27 is a block diagram illustrating the main components of the NEF 77. As shown, the apparatus includes a transceiver circuit 771 operable to transmit signals to and receive signals from other nodes (including the UDM 75) via a network interface 772. A controller 773 controls the operation of the NEF 77 according to software stored in a memory 774. The software may be pre-installed in the memory 774 and / or may be downloaded, for example, via a telecommunications network or from a removable data storage device (e.g., a removable memory device (RMD)). The software includes, among other things, an operating system 7741 and a communication control module 7742 having at least a transceiver control module 77421. The communication control module 7742 (using its transceiver control module 77421) is responsible for handling (generating / sending / receiving) signaling between the NEF 77 and other nodes such as the UDM 75 and other core network nodes (including core network nodes in the HPLMN of the UE 3 when the UE 3 is roaming in). Such signaling may include, for example, appropriately formatted signaling messages (for the UE 3) related to network exposure function procedures (e.g., HTTP restful methods based on service-based interfaces).

[0260] The NEF 77 may support a non-public network (NPN), which may be a stand-alone non-public network (SNPN) or a public network integrated NPN (PNI-NPN).

[0261] (NSACF) FIG. 28 is a block diagram illustrating the main components of the NSACF 78. As shown, the apparatus includes a transceiver circuit 781 operable to transmit signals to and receive signals from other nodes (including the AMF 70) via a network interface 782. A controller 783 controls the operation of the NSACF 78 according to software stored in a memory 784. The software may, for example, be pre-installed in the memory 784 and / or downloaded over a telecommunications network or from a removable data storage device (RMD). The software includes, among other things, an operating system 7841 and a communication control module 7842 having at least a transceiver control module 78421. The communication control module 7842 (using its transceiver control module 78421) is responsible for handling (generating / sending / receiving) signaling between the NSACF 78 and other nodes such as the AMF 70 and other core network nodes (including core network nodes in the HPLMN of the UE 3 when the UE 3 is roaming in). Such signaling may include, for example, appropriately formatted signaling messages (for UE 3) related to network data analysis function procedures (e.g., HTTP restful methods based on service-based interfaces).

[0262] The NSACF 78 may support a non-public network (NPN), which may be a stand-alone non-public network (SNPN) or a public network integrated NPN (PNI-NPN).

[0263] (IMS) 29 is a block diagram illustrating the main components of the IMS 201. As shown, the apparatus includes a transceiver circuit 2011 operable to transmit signals to and receive signals from other nodes (including the UE 3, the NEF 77, the PSAP 202) via a network interface 2012. A controller 2013 controls the operation of the IMS 201 in accordance with software stored in a memory 2014. The software may be pre-installed in the memory 2014 and / or may be downloaded, for example, via a telecommunications network or from a removable data storage device (RMD). The software includes, among other things, an operating system 20141 and a communication control module 20142 having at least a transceiver control module 201421. The communication control module 20142 (using its transceiver control module 201421) is responsible for handling (generating / sending / receiving) signaling between the IMS 201 and other nodes such as the UE 3, the NEF 77 or the PSAP 202 and other core network nodes (including core network nodes in the VPLMN of the UE 3 when the UE 3 is roaming out). Such signaling may include, for example, appropriately formatted signaling messages (for the UE 3) related to mobility management procedures (e.g., HTTP restful methods based on service-based interfaces).

[0264] The IMS 201 may support a non-public network (NPN), which may be a stand-alone non-public network (SNPN) or a public network integrated NPN (PNI-NPN). The IMS (CSCF) may include the same components as the IMS 201 described in the above embodiment.

[0265] (PSAP) 30 is a block diagram illustrating the main components of the PSAP 202. As shown, the apparatus includes a transceiver circuit 2011 operable to transmit signals to and receive signals from other nodes (including the NEF 77, the IMS 201) via a network interface 2012. A control unit 2013 controls the operation of the PSAP 202 according to software stored in a memory 2014. The software may be pre-installed in the memory 2014 and / or may be downloaded, for example, via a telecommunications network or from a removable data storage device (RMD). The software includes, among other things, an operating system 20141 and a communication control module 20142 having at least a transceiver control module 201421. The communication control module 20142 (using its transceiver control module 201421) is responsible for handling (generating / sending / receiving) signaling between the PSAP 202 and other nodes such as the NEF 77 or the IMS 201 and other core network nodes (including core network nodes in the VPLMN of the UE 3 when the UE 3 is roaming out). Such signaling may include, for example, appropriately formatted signaling messages (for the UE 3) related to mobility management procedures (e.g., HTTP restful methods based on service-based interfaces).

[0266] PSAP 202 may support a non-public network (NPN), which may be a stand-alone non-public network (SNPN) or a public network integrated NPN (PNI-NPN).

[0267] (Variations and Alternatives) Detailed embodiments have been described above. As will be appreciated by those skilled in the art, several modifications and alternatives may be made to the above embodiments while still benefiting from the disclosure embodied therein. By way of example, only some of these alternatives and modifications are described herein.

[0268] In the above description, for ease of understanding, the UE 3 and network devices are described as having several separate modules (such as a communications control module). These modules may be provided in this manner for a particular application, such as where an existing system is modified to implement the present disclosure, and in other applications, such as systems designed from the beginning with the features of the present invention in mind, but these modules may not be identifiable as separate entities because they may be incorporated into an overall operating system or code. These modules may be implemented in software, hardware, firmware, or a combination thereof.

[0269] Each control unit may include any suitable form of processing circuitry including, for example (but not limited to), one or more hardware-implemented computer processors, microprocessors, central processing units (CPUs), arithmetic logic units (ALUs), input / output (IO) circuitry, internal memory / cache (program and / or data), processing registers, communication buses (e.g., control buses, data buses and / or address buses), direct memory access (DMA) facilities, hardware or software implemented counters, pointers and / or timers, etc. In the above embodiment, a number of software modules have been described. As will be understood by those skilled in the art, the software modules may be provided in compiled or uncompiled form and may be provided to the UE 3 and the network device as a signal via a computer network or on a recording medium. Furthermore, the functions implemented by some or all of this software may be implemented using one or more dedicated hardware circuits. However, the use of software modules is preferred as it facilitates the updating of the UE 3 and the network device to update their functions.

[0270] In the above embodiment, 3GPP wireless communication (radio access) technology is used. However, any other wireless communication technology (e.g., WLAN, Wi-Fi, WiMAX, Bluetooth, etc.) and other fixed line communication technology (e.g., BBF access, cable access, optical access, etc.) may also be used according to the above embodiment.

[0271] Items of user equipment may include communication devices such as, for example, mobile phones, smartphones, user equipment, personal digital assistants, laptop / tablet computers, web browsers, e-book readers, etc. Such mobile (or even generally fixed) devices are typically operated by a user, although so-called "Internet of Things" (IoT) devices and similar machine-type communication (MTC) devices may also be connected to the network. For simplicity, the present application refers to mobile devices (or UEs) in the description, but it will be understood that the described techniques may be implemented on any communication device (mobile and / or generally fixed) that can be connected to a communication network to transmit and receive data, regardless of whether such communication devices are controlled by human input or by software instructions stored in memory. Various other modifications will be apparent to those skilled in the art and will not be described in further detail here.

[0272] As will be appreciated by those skilled in the art, the present disclosure may be embodied as a method and / or a system. Accordingly, the present disclosure may take the form of an entirely hardware embodiment, a software embodiment, or an embodiment combining software and hardware aspects.

[0273] It will be understood that each block of the block diagrams can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, a special purpose computer, or other programmable data processing apparatus to produce a machine such that the instructions, executed via the processor of the computer or other programmable data processing apparatus, create means for performing the functions / operations specified in one or more blocks of the flowcharts and / or block diagrams. A general purpose processor may be a microprocessor, but alternatively, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, e.g., multiple microprocessors, one or more microprocessors, or any other such configuration.

[0274] The methods or algorithms described in connection with the examples disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. The software module may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. The storage medium may be coupled to the processor such that the processor can read information from, and write information to, the storage medium. Alternatively, the storage medium may be integral to the processor. The processor and the storage medium may reside in an ASIC.

[0275] The preceding description of the disclosed examples is provided to enable any person skilled in the art to make or use the present disclosure. Various modifications to these examples will be readily apparent to those skilled in the art, and the general principles defined herein may be applied to other examples without departing from the spirit or scope of the present disclosure. Thus, the present disclosure is not intended to be limited to the examples shown herein, but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

[0276] Although the present disclosure has been particularly shown and described with reference to its exemplary embodiments, the present disclosure is not limited to these embodiments. Those skilled in the art will understand that various changes in form and details can be made without departing from the spirit and scope of the present disclosure defined by this specification. For example, the present invention is not limited to 5GS, but is also applicable to communication systems other than 5GS (e.g., 6G system, beyond 5G system).

[0277] (Additional Note) All or a part of the exemplary aspects disclosed above may be described as follows, but are not limited to these. (Appendix 1) Sending a message, the message includes a request to transmit information, The information includes at least one of an identifier of a user equipment (UE), location information of where the UE is located, video information of the surroundings of the UE, photo information of the surroundings of the UE, audio information of the surroundings of the UE, temperature information of the surroundings of the UE, vital information of a user of the UE, and contact information of the UE; receiving the information after sending the message. Method of communication device. (Appendix 2) A message will be sent in the event of a disaster. The method described in Appendix 1. (Appendix 3) The information includes information indicating whether a user of the UE is safe or not; 3. The method according to claim 1 or 2. (Appendix 4) Receiving a message, the message includes a request to transmit information, The information includes at least one of an identifier of a user equipment (UE), location information of where the UE is located, video information of the surroundings of the UE, photo information of the surroundings of the UE, audio information of the surroundings of the UE, temperature information of the surroundings of the UE, vital information of a user of the UE, and contact information of the UE; and transmitting the information after receiving the message. UE methods. (Appendix 5) A message will be sent in the event of a disaster. The method described in Appendix 4. (Appendix 6) The information includes information indicating whether a user of the UE is safe or not; 6. The method according to claim 4 or 5. (Appendix 7) A means for sending a message, comprising: the message includes a request to transmit information, The information includes at least one of an identifier of a user equipment (UE), location information of a location where the UE is located, video information of the surroundings of the UE, photo information of the surroundings of the UE, audio information of the surroundings of the UE, temperature information of the surroundings of the UE, vital information of a user of the UE, and contact information of the UE; and means for receiving the information after sending the message. Communications equipment. (Appendix 8) A message will be sent in the event of a disaster. 8. The communication device of claim 7. (Appendix 9) The information includes information indicating whether a user of the UE is safe or not; 9. The communication device of claim 7 or 8. (Appendix 10) A means for receiving a message, comprising: the message includes a request to transmit information, The information includes at least one of an identifier of a user equipment (UE), location information of a location where the UE is located, video information of the surroundings of the UE, photo information of the surroundings of the UE, audio information of the surroundings of the UE, temperature information of the surroundings of the UE, vital information of a user of the UE, and contact information of the UE; means for transmitting the information after receiving the message. U.E. (Appendix 11) A message will be received in the event of a disaster. 1. The UE as described in Appendix 10. (Appendix 12) The information includes information indicating whether a user of the UE is safe or not; 12. The UE according to claim 10 or 11.

[0278] This application claims the benefit of priority to Indian Patent Application No. 202211014351 filed on March 16, 2022, the disclosure of which is incorporated herein by reference in its entirety. [Explanation of symbols]

[0279] 3. UE 31 Transceiver Circuit 32 Antenna 33 Control Unit 34 User Interface 35 USIM 36 Memory 361 Operating Systems 362 Communication Control Module 3621 Transceiver Control Module 363 Lifeguard APL 3631 Data Storage 5 RAN Node 51 Transceiver Circuit 52 Antenna 53 Network Interface 54 Control section 55 Memory 551 Operating Systems 552 Communication Control Module 5521 Transceiver Control Module 553 Lifeguard APL 5531 Data Storage 60RU 601 Transceiver Circuit 602 Antenna 603 Network Interface 604 Control section 605 Memory 6051 Operating System 6052 Communication Control Module 60521 Transceiver Control Module 61DU 611 Transceiver Circuit 612 Network Interface 613 Control Unit 614 Memory 6141 Operating Systems 6142 Communication Control Module 61421 Transceiver Control Module 62 CU 621 Transceiver Circuit 622 Network Interface 623 Control Unit 624 Memory 6241 Operating Systems 6242 Communication Control Module 62421 Transceiver Control Module 7 Core Network 70 AMF 701 Transceiver Circuit 702 Network Interface 703 Control Unit 704 Memory 7041 Operating Systems 7042 Communication Control Module 70421 Transceiver Control Module 71 SMF 711 Transceiver Circuit 712 Network Interface 713 Control Unit 714 Memory 7141 Operating Systems 7142 Communication Control Module 71421 Transceiver Control Module 72 UPF 721 Transceiver Circuit 722 Network Interface 723 Control Unit 724 Memory 7241 Operating Systems 7242 Communication Control Module 72421 Transceiver Control Module 73 PCF 731 Transceiver Circuits 732 Network Interface 733 Control Unit 734 Memory 7341 Operating Systems 7342 Communication Control Module 73421 Transceiver Control Module 74 AUSF 741 Transceiver Circuit 742 Network Interface 743 Control Unit 744 Memory 7441 Operating Systems 7442 Communication Control Module 74421 Transceiver Control Module 75 UDM 751 Transceiver Circuit 752 Network Interface 753 Control Unit 754 Memory 7541 Operating Systems 7542 Communication Control Module 75421 Transceiver Control Module 76 NWDAF 761 Transceiver Circuit 762 Network Interface 763 Control Unit 764 Memory 7641 Operating Systems 7642 Communication Control Module 76421 Transceiver Control Module 77 NEF 771 Transceiver Circuit 772 Network Interface 773 Control Unit 774 Memory 7741 Operating Systems 7742 Communication Control Module 77421 Transceiver Control Module 78 NSACF 781 Transceiver Circuit 782 Network Interface 783 Control Unit 784 Memory 7841 Operating Systems 7842 Communication Control Module 78421 Transceiver Control Module 20 Data Network 201 IMS 2011 Transceiver Circuit 2012 Network Interface 2013 Control Unit 2014 Memory 20141 Operating Systems 20142 Communication control module 201421 Transceiver Control Module 202 PSAP 2021 Transceiver Circuit 2022 Network Interface 2023 Control Unit 2024 Memory 20241 Operating System 20242 Communication Control Module 202421 Transceiver Control Module

Claims

1. Sending a message, the message includes a request to transmit information; The information includes at least one of an identifier of a user equipment (UE), location information where the UE is located, video information of the surroundings of the UE, photo information of the surroundings of the UE, audio information of the surroundings of the UE, temperature information of the surroundings of the UE, vital information of a user of the UE, and contact information of the UE; receiving the information after sending the message. Method of communication device.

2. The message is sent in the event of a disaster. The method of claim 1.

3. The information includes information indicating whether a user of the UE is safe or not. The method according to claim 1 or 2.

4. Receiving a message, the message includes a request to transmit information; The information includes at least one of an identifier of a user equipment (UE), location information where the UE is located, video information of the surroundings of the UE, photo information of the surroundings of the UE, audio information of the surroundings of the UE, temperature information of the surroundings of the UE, vital information of a user of the UE, and contact information of the UE; and transmitting the information after receiving the message. A method for a UE.

5. The message is received in the event of a disaster. The method according to claim 4.

6. The information includes information indicating whether a user of the UE is safe or not. The method according to claim 4 or 5.

7. A means for sending a message, comprising: the message includes a request to transmit information; the information includes at least one of an identifier of a user equipment (UE), location information where the UE is located, video information of the surroundings of the UE, photo information of the surroundings of the UE, audio information of the surroundings of the UE, temperature information of the surroundings of the UE, vital information of a user of the UE, and contact information of the UE; and means for receiving the information after sending the message. Communications equipment.

8. The message is sent in the event of a disaster. The communication device according to claim 7.

9. The information includes information indicating whether a user of the UE is safe or not. A communication device according to claim 7 or 8.

10. A means for receiving a message, comprising: the message includes a request to transmit information; the information includes at least one of an identifier of a user equipment (UE), location information where the UE is located, video information of the surroundings of the UE, photo information of the surroundings of the UE, audio information of the surroundings of the UE, temperature information of the surroundings of the UE, vital information of a user of the UE, and contact information of the UE; and means for transmitting the information after receiving the message. U.E.

11. The message is received in the event of a disaster. The UE of claim 10.

12. The information includes information indicating whether a user of the UE is safe or not.

12. The UE according to claim 10 or 11.

Images