CN116472745A

CN116472745A - Electronic device for performing emergency services and method of operating the same

Info

Publication number: CN116472745A
Application number: CN202180076244.6A
Authority: CN
Inventors: 宋元根
Original assignee: Samsung Electronics Co Ltd
Current assignee: Samsung Electronics Co Ltd
Priority date: 2020-11-12
Filing date: 2021-10-07
Publication date: 2023-07-21

Abstract

According to various embodiments, an electronic device includes at least one processor, wherein the at least one processor may be configured to confirm an event associated with an emergency service upon registration with a first communication system, send a service request corresponding to the event to a network based on the confirmation of the event, start a timer having an end time shorter than an end time of a T3517 timer based on the sending of the service request, search for and select a cell corresponding to a PLMN of a second communication system that does not include the first communication system based on failing to receive a response corresponding to the service request until the timer ends, perform at least one operation for registering with the second communication system based on the selected cell, and perform the emergency service corresponding to the event in the second communication system based on registering with the second communication system. Various other embodiments are possible.

Description

Electronic device for performing emergency services and method of operating the same

Technical Field

Various embodiments relate to an electronic device for performing emergency services and a method of operating the same.

Background

To support various application scenarios for acquiring emergency services, a User Equipment (UE) and a fifth generation core (5 GC) may support a mechanism for switching the UE to E-UTRA connected to the 5GC by using a mobility from nrcommand or for redirecting the UE to E-UTRA by using RRC release (RRC release). For example, radio Access Technology (RAT) fallback may be performed when a New Radio (NR) does not support emergency services, wherein the UE is handed over or redirected to E-UTRA connected to 5 GC. Alternatively, when the 5GC does not support emergency services, a system fallback to E-UTRA connected to an Evolved Packet Core (EPC) may be performed, wherein the UE is handed over or redirected to the Evolved Packet System (EPS). The emergency service fallback may be used when the fifth generation system (5 GS) does not indicate support for emergency services and when the 5GS indicates support for emergency service fallback.

For example, when the AMF indicates support for emergency service fallback in the registration accept message, in order to initiate emergency services, a normally registered UE supporting emergency service fallback may initiate a service request. For example, the UE may send a service request to the AMF. The UE may receive a response (e.g., an RRC release message or a handover command) that causes system backoff, thereby performing emergency services in a communication system in which backoff has been performed.

Disclosure of Invention

Technical problem

In response to the service request, the UE may perform a system backoff (e.g., EPS backoff) based on an RRC release message or a handover command received from the network. However, the UE may not receive a response from the network due to deterioration of the electric field condition or temporary problems in the network. Technical Specification (TS) 24.501 of the third generation partnership project (3 GPP) proposes a timer T3517. After sending the service request, the UE may wait for a response until the timer T3517 expires. Thus, the execution of the emergency service may be delayed due to the failure of the response until the timer T3517 expires. If the timer T3517 is 15 seconds, the emergency call may be delayed by 15 seconds.

The electronic device and the operation method thereof according to various embodiments may perform the emergency service by performing a system fallback based on expiration of a timer having an expiration time shorter than that of the timer T3517.

Technical solution

According to various embodiments, an electronic device may include at least one processor, wherein the at least one processor is configured to: identifying an event associated with an emergency service when registered in a first communication system; based on the identification of the event, sending a service request corresponding to the event to a network; starting a timer having an expiration time shorter than that of the timer T3517 based on the transmission of the service request; searching and selecting a cell corresponding to a PLMN of a second communication system different from the first communication system based on failing to receive a response corresponding to the service request until the timer expires; performing at least one operation for registering in the second communication system based on the selected cell; and performing an emergency service corresponding to the event based on the second communication system based on registration in the second communication system.

According to various embodiments, a method of operating an electronic device may include: identifying an event associated with an emergency service when registered in a first communication system; based on the identification of the event, sending a service request corresponding to the event to a network; starting a timer having an expiration time shorter than that of the timer T3517 based on the transmission of the service request; searching and selecting a cell corresponding to a PLMN of a second communication system different from the first communication system based on failing to receive a response corresponding to the service request until the timer expires; performing at least one operation for registering in the second communication system based on the selected cell; and performing an emergency service corresponding to the event based on the second communication system.

According to various embodiments, an electronic device may include at least one processor, wherein the at least one processor is configured to: identifying an event associated with an emergency service when registered in a first communication system; searching and selecting a cell corresponding to a PLMN of a second communication system different from the first communication system in response to identifying an event related to emergency services; performing at least one operation for registering in the second communication system based on the selected cell based on the identification that the emergency service back-off indicator identified during registration of the first communication system is configured as "unsupported"; and performing an emergency service corresponding to the event by using the second communication system based on registration in the second communication system.

Advantageous effects

Various embodiments may provide an electronic device and an operating method thereof, in which emergency services may be performed by performing a system fallback based on expiration of a timer having an expiration time shorter than that of timer T3517. Thus, it is possible to prevent emergency services from being delayed during the expiration time of the timer T3517, which is a relatively long time according to the standard document.

Drawings

Fig. 1 is a block diagram of an electronic device in a network environment, in accordance with various embodiments.

Fig. 2a and 2b are block diagrams of an electronic device for supporting legacy network communications and 5G network communications, in accordance with various embodiments.

Fig. 3a is a flow chart illustrating an emergency services fallback procedure of a user equipment according to various embodiments.

Fig. 3b shows a flow chart of a comparative example for comparison with various embodiments.

Fig. 4 is a flow chart illustrating a method of operation of an electronic device according to various embodiments.

Fig. 5 is a flow chart illustrating a method of operation of an electronic device according to various embodiments.

Fig. 6 is a flow chart illustrating a method of operation of an electronic device according to various embodiments.

Fig. 7 is a flow chart illustrating a method of operation of an electronic device in accordance with various embodiments.

Fig. 8 is a flow chart illustrating a method of operation of an electronic device in accordance with various embodiments.

Fig. 9 is a flow chart illustrating a method of operation of an electronic device in accordance with various embodiments.

Fig. 10 is a flow chart illustrating a method of operation of an electronic device in accordance with various embodiments.

Fig. 11 is a flow chart illustrating a method of operation of an electronic device in accordance with various embodiments.

Fig. 12 is a flow chart illustrating a method of operation of an electronic device in accordance with various embodiments.

Fig. 13 is a flow chart illustrating a method of operation of an electronic device according to various embodiments.

Detailed Description

Fig. 1 is a block diagram illustrating an electronic device 101 in a network environment 100 according to various embodiments. Referring to fig. 1, an electronic device 101 in a network environment 100 may communicate with the electronic device 102 via a first network 198 (e.g., a short-range wireless communication network) or with at least one of the electronic device 104 or the server 108 via a second network 199 (e.g., a long-range wireless communication network). According to an embodiment, the electronic device 101 may communicate with the electronic device 104 via the server 108. According to an embodiment, the electronic device 101 may include a processor 120, a memory 130, an input module 150, a sound output module 155, a display module 160, an audio module 170, a sensor module 176, an interface 177, a connection end 178, a haptic module 179, a camera module 180, a power management module 188, a battery 189, a communication module 190, a Subscriber Identity Module (SIM) 196, or an antenna module 197. In some embodiments, at least one of the above-described components (e.g., connection end 178) may be omitted from electronic device 101, or one or more other components may be added to electronic device 101. In some embodiments, some of the components described above (e.g., sensor module 176, camera module 180, or antenna module 197) may be implemented as a single integrated component (e.g., display module 160).

The processor 120 may run, for example, software (e.g., program 140) to control at least one other component (e.g., hardware component or software component) of the electronic device 101 that is connected to the processor 120, and may perform various data processing or calculations. According to one embodiment, as at least part of the data processing or calculation, the processor 120 may store commands or data received from another component (e.g., the sensor module 176 or the communication module 190) into the volatile memory 132, process the commands or data stored in the volatile memory 132, and store the resulting data in the non-volatile memory 134. According to an embodiment, the processor 120 may include a main processor 121 (e.g., a Central Processing Unit (CPU) or an Application Processor (AP)) or an auxiliary processor 123 (e.g., a Graphics Processing Unit (GPU), a Neural Processing Unit (NPU), an Image Signal Processor (ISP), a sensor hub processor, or a Communication Processor (CP)) that is operatively independent of or combined with the main processor 121. For example, when the electronic device 101 comprises a main processor 121 and a secondary processor 123, the secondary processor 123 may be adapted to consume less power than the main processor 121 or to be dedicated to a particular function. The auxiliary processor 123 may be implemented separately from the main processor 121 or as part of the main processor 121.

The auxiliary processor 123 (instead of the main processor 121) may control at least some of the functions or states related to at least one of the components of the electronic device 101 (e.g., the display module 160, the sensor module 176, or the communication module 190) when the main processor 121 is in an inactive (e.g., sleep) state, or the auxiliary processor 123 may control at least some of the functions or states related to at least one of the components of the electronic device 101 (e.g., the display module 160, the sensor module 176, or the communication module 190) with the main processor 121 when the main processor 121 is in an active state (e.g., running an application). According to an embodiment, the auxiliary processor 123 (e.g., an image signal processor or a communication processor) may be implemented as part of another component (e.g., the camera module 180 or the communication module 190) functionally related to the auxiliary processor 123. According to an embodiment, the auxiliary processor 123 (e.g., a neural processing unit) may include hardware structures dedicated to artificial intelligence model processing. The artificial intelligence model may be generated through machine learning. Such learning may be performed, for example, by the electronic device 101 where artificial intelligence is performed or via a separate server (e.g., server 108). The learning algorithm may include, but is not limited to, for example, supervised learning, unsupervised learning, semi-supervised learning, or reinforcement learning. The artificial intelligence model may include a plurality of artificial neural network layers. The artificial neural network may be a Deep Neural Network (DNN), a Convolutional Neural Network (CNN), a Recurrent Neural Network (RNN), a boltzmann machine limited (RBM), a Deep Belief Network (DBN), a bi-directional recurrent deep neural network (BRDNN), or a deep Q network, or a combination of two or more thereof, but is not limited thereto. Additionally or alternatively, the artificial intelligence model may include software structures in addition to hardware structures.

The memory 130 may store various data used by at least one component of the electronic device 101 (e.g., the processor 120 or the sensor module 176). The various data may include, for example, software (e.g., program 140) and input data or output data for commands associated therewith. Memory 130 may include volatile memory 132 or nonvolatile memory 134.

The program 140 may be stored as software in the memory 130, and the program 140 may include, for example, an Operating System (OS) 142, middleware 144, or applications 146.

The input module 150 may receive commands or data from outside the electronic device 101 (e.g., a user) to be used by other components of the electronic device 101 (e.g., the processor 120). The input module 150 may include, for example, a microphone, a mouse, a keyboard, keys (e.g., buttons) or a digital pen (e.g., a stylus).

The sound output module 155 may output a sound signal to the outside of the electronic device 101. The sound output module 155 may include, for example, a speaker or a receiver. Speakers may be used for general purposes such as playing multimedia or playing a record. The receiver may be used to receive an incoming call. Depending on the embodiment, the receiver may be implemented separate from the speaker or as part of the speaker.

Display module 160 may visually provide information to the outside (e.g., user) of electronic device 101. The display device 160 may include, for example, a display, a holographic device, or a projector, and a control circuit for controlling a corresponding one of the display, the holographic device, and the projector. According to an embodiment, the display module 160 may comprise a touch sensor adapted to detect a touch or a pressure sensor adapted to measure the strength of the force caused by a touch.

The audio module 170 may convert sound into electrical signals and vice versa. According to an embodiment, the audio module 170 may obtain sound via the input module 150, or output sound via the sound output module 155 or headphones of an external electronic device (e.g., the electronic device 102) that is directly (e.g., wired) or wirelessly connected to the electronic device 101.

The sensor module 176 may detect an operational state (e.g., power or temperature) of the electronic device 101 or an environmental state (e.g., a state of a user) external to the electronic device 101 and then generate an electrical signal or data value corresponding to the detected state. According to an embodiment, the sensor module 176 may include, for example, a gesture sensor, a gyroscope sensor, an atmospheric pressure sensor, a magnetic sensor, an acceleration sensor, a grip sensor, a proximity sensor, a color sensor, an Infrared (IR) sensor, a biometric sensor, a temperature sensor, a humidity sensor, or an illuminance sensor.

Interface 177 may support one or more specific protocols that will be used to connect electronic device 101 with an external electronic device (e.g., electronic device 102) directly (e.g., wired) or wirelessly. According to an embodiment, interface 177 may include, for example, a High Definition Multimedia Interface (HDMI), a Universal Serial Bus (USB) interface, a Secure Digital (SD) card interface, or an audio interface.

The connection end 178 may include a connector via which the electronic device 101 may be physically connected with an external electronic device (e.g., the electronic device 102). According to an embodiment, the connection end 178 may include, for example, an HDMI connector, a USB connector, an SD card connector, or an audio connector (e.g., a headphone connector).

The haptic module 179 may convert the electrical signal into a mechanical stimulus (e.g., vibration or motion) or an electrical stimulus that may be recognized by the user via his sense of touch or kinesthetic sense. According to an embodiment, the haptic module 179 may include, for example, a motor, a piezoelectric element, or an electrostimulator.

The camera module 180 may capture still images or moving images. According to an embodiment, the camera module 180 may include one or more lenses, an image sensor, an image signal processor, or a flash.

The power management module 188 may manage power supply to the electronic device 101. According to an embodiment, the power management module 188 may be implemented as at least part of, for example, a Power Management Integrated Circuit (PMIC).

Battery 189 may power at least one component of electronic device 101. According to an embodiment, battery 189 may include, for example, a primary non-rechargeable battery, a rechargeable battery, or a fuel cell.

The communication module 190 may support establishing a direct (e.g., wired) communication channel or a wireless communication channel between the electronic device 101 and an external electronic device (e.g., the electronic device 102, the electronic device 104, or the server 108) and performing communication via the established communication channel. The communication module 190 may include one or more communication processors capable of operating independently of the processor 120 (e.g., an Application Processor (AP)) and supporting direct (e.g., wired) or wireless communication. According to an embodiment, the communication module 190 may include a wireless communication module 192 (e.g., a cellular communication module, a short-range wireless communication module, or a Global Navigation Satellite System (GNSS) communication module) or a wired communication module 194 (e.g., a Local Area Network (LAN) communication module or a Power Line Communication (PLC) module). A respective one of these communication modules may communicate with external electronic devices via a first network 198 (e.g., a short-range communication network such as bluetooth, wireless fidelity (Wi-Fi) direct, or infrared data association (IrDA)) or a second network 199 (e.g., a long-range communication network such as a conventional cellular network, a 5G network, a next-generation communication network, the internet, or a computer network (e.g., a LAN or wide-area network (WAN)). These various types of communication modules may be implemented as a single component (e.g., a single chip), or may be implemented as multiple components (e.g., multiple chips) separate from each other. The wireless communication module 192 may identify and authenticate the electronic device 101 in a communication network, such as the first network 198 or the second network 199, using user information (e.g., an International Mobile Subscriber Identity (IMSI)) stored in the user identification module 196.

The wireless communication module 192 may support a 5G network following a 4G network as well as next generation communication technologies (e.g., new Radio (NR) access technologies). NR access technologies may support enhanced mobile broadband (eMBB), large-scale machine type communication (mctc), or Ultra Reliable Low Latency Communication (URLLC). The wireless communication module 192 may support a high frequency band (e.g., millimeter wave band) to achieve, for example, a high data transmission rate. The wireless communication module 192 may support various techniques for ensuring performance over high frequency bands, such as, for example, beamforming, massive multiple-input multiple-output (massive MIMO), full-dimensional MIMO (FD-MIMO), array antennas, analog beamforming, or massive antennas. The wireless communication module 192 may support various requirements specified in the electronic device 101, an external electronic device (e.g., electronic device 104), or a network system (e.g., second network 199). According to an embodiment, the wireless communication module 192 may support a peak data rate (e.g., 20Gbps or greater) for implementing an eMBB, a lost coverage (e.g., 164dB or less) for implementing an emtc, or a U-plane delay (e.g., a round trip of 0.5ms or less, or 1ms or less for each of the Downlink (DL) and Uplink (UL)) for implementing a URLLC.

The antenna module 197 may transmit signals or power to the outside of the electronic device 101 (e.g., an external electronic device) or receive signals or power from the outside of the electronic device 101 (e.g., an external electronic device). According to an embodiment, the antenna module 197 may include an antenna including a radiating element composed of a conductive material or conductive pattern formed in or on a substrate, such as a Printed Circuit Board (PCB). According to an embodiment, the antenna module 197 may include a plurality of antennas (e.g., array antennas). In this case, at least one antenna suitable for a communication scheme used in a communication network, such as the first network 198 or the second network 199, may be selected from the plurality of antennas, for example, by the communication module 190 (e.g., the wireless communication module 192). Signals or power may then be transmitted or received between the communication module 190 and the external electronic device via the selected at least one antenna. According to an embodiment, further components (e.g., a Radio Frequency Integrated Circuit (RFIC)) other than radiating elements may additionally be formed as part of the antenna module 197.

According to various embodiments, antenna module 197 may form a millimeter wave antenna module. According to embodiments, a millimeter-wave antenna module may include a printed circuit board, a Radio Frequency Integrated Circuit (RFIC) disposed on a first surface (e.g., a bottom surface) of the printed circuit board or adjacent to the first surface and capable of supporting a specified high frequency band (e.g., a millimeter-wave band), and a plurality of antennas (e.g., array antennas) disposed on a second surface (e.g., a top surface or a side surface) of the printed circuit board or adjacent to the second surface and capable of transmitting or receiving signals of the specified high frequency band.

At least some of the above components may be interconnected via an inter-peripheral communication scheme (e.g., bus, general Purpose Input Output (GPIO), serial Peripheral Interface (SPI), or Mobile Industrial Processor Interface (MIPI)) and communicatively communicate signals (e.g., commands or data) therebetween.

According to an embodiment, commands or data may be sent or received between the electronic device 101 and the external electronic device 104 via the server 108 connected to the second network 199. Each of the electronic device 102 or the electronic device 104 may be the same type of device as the electronic device 101 or a different type of device from the electronic device 101. According to an embodiment, all or some of the operations to be performed at the electronic device 101 may be performed at one or more of the external electronic device 102, the external electronic device 104, or the server 108. For example, if the electronic device 101 should automatically perform a function or service or should perform a function or service in response to a request from a user or another device, the electronic device 101 may request the one or more external electronic devices to perform at least part of the function or service instead of or in addition to the function or service, or the electronic device 101 may request the one or more external electronic devices to perform at least part of the function or service. The one or more external electronic devices that received the request may perform the requested at least part of the function or service or perform another function or another service related to the request and transmit the result of the performing to the electronic device 101. The electronic device 101 may provide the result as at least a partial reply to the request with or without further processing of the result. For this purpose, for example, cloud computing technology, distributed computing technology, mobile Edge Computing (MEC) technology, or client-server computing technology may be used. The electronic device 101 may provide ultra-low latency services using, for example, distributed computing or mobile edge computing. In another embodiment, the external electronic device 104 may comprise an internet of things (IoT) device. Server 108 may be an intelligent server using machine learning and/or neural networks. According to an embodiment, the external electronic device 104 or the server 108 may be included in the second network 199. The electronic device 101 may be applied to smart services (e.g., smart home, smart city, smart car, or healthcare) based on 5G communication technology or IoT-related technology.

Fig. 2a is a block diagram 200 of an electronic device 101 for supporting legacy network communications and 5G network communications, according to various embodiments. Referring to fig. 2a, the electronic device 101 may include a first communication processor 212, a second communication processor 214, a first Radio Frequency Integrated Circuit (RFIC) 222, a second RFIC 224, a third RFIC 226, a fourth RFIC 228, a first Radio Frequency Front End (RFFE) 232, a second RFFE 234, a first antenna module 242, a second antenna module 244, a third antenna module 246, and an antenna 248. The electronic device 101 may also include a processor 120 and a memory 130. The second network 199 may include a first cellular network 292 and a second cellular network 294. According to another embodiment, the electronic device 101 may also include at least one of the components shown in fig. 1, and the second network 199 may also include at least one other network. According to an embodiment, the first communication processor 212, the second communication processor 214, the first RFIC 222, the second RFIC 224, the fourth RFIC 228, the first RFFE 232, and the second RFFE 234 may form at least a portion of the communication module 192. According to another embodiment, the fourth RFIC 228 may be omitted or may be included as part of the third RFIC 226.

The first communication processor 212 may establish a communication channel for a frequency band for wireless communication with the first cellular network 292 and may support legacy network communication through the established communication channel. According to various embodiments, the first cellular network may be a legacy network, including a 2G, 3G, 4G, or Long Term Evolution (LTE) network. The second communication processor 214 may establish a communication channel corresponding to a designated frequency band (e.g., from about 6GHz to about 60 GHz) among frequency bands to be used for wireless communication with the second cellular network 294, and may support 5G network communication through the established communication channel. According to various embodiments, the second cellular network 294 may be a 5G network defined in 3 GPP. Further, according to an embodiment, the first communication processor 212 or the second communication processor 214 may establish a communication channel corresponding to another designated frequency band (for example, about 6GHz or less) among frequency bands to be used for wireless communication with the second cellular network 294, and may support 5G network communication through the established communication channel.

The first communication processor 212 may send data to the second communication processor 214 and receive data from the second communication processor 214. For example, data classified for transmission over the second cellular network 294 may be transmitted over the first cellular network 292 by changing. In this case, the first communication processor 212 may receive the transmission data from the second communication processor 214. For example, the first communication processor 212 may send data to the second communication processor 214 and receive data from the second communication processor 214 through the inter-processor interface 213. The processor interface 213 may be implemented as, for example, a universal asynchronous receiver/transmitter (UART) (e.g., a high-speed UART (HS-UART) or a peripheral component interconnect bus express (PCIe) interface), although the type thereof is not limited. Alternatively, the first communication processor 212 and the second communication processor 214 may exchange control information and packet data information by using, for example, a shared memory. The first communication processor 212 may transmit and receive various types of information, such as sensing information, information about output strength, and information about Resource Block (RB) allocation, to and from the second communication processor 214.

Depending on the implementation, the first communication processor 212 may not be directly connected to the second communication processor 214. In this case, the first communication processor 212 may send data to the second communication processor 214 and receive data from the second communication processor 214 through the processor 120 (e.g., an application processor). For example, the first communication processor 212 and the second communication processor 214 may send data to and receive data from the processor 120 (e.g., an application processor) through an HS-UART interface or a PCIe interface, but the type of interface is not limited. Alternatively, the first communication processor 212 and the second communication processor 214 may exchange control information and packet data information with the processor 120 (e.g., an application processor) by using a shared memory.

The first communication processor 212 and the second communication processor 214 may be implemented in a single chip or a single package, depending on the embodiment. According to various embodiments, the first communication processor 212 or the second communication processor 214 may be provided in a single chip or a single package together with the processor 120, the auxiliary processor 123, or the communication module 190. For example, as shown in fig. 2b, the integrated communication processor 260 may support all of the functionality for communicating with the first cellular network 292 and the second cellular network 294.

In signaling, the first RFIC 222 may convert baseband signals generated by the first communication processor 212 to Radio Frequency (RF) signals of about 700MHz to about 3GHz for the first cellular network 292 (e.g., a legacy network). Upon signal reception, an RF signal may be acquired from a first network 292 (e.g., a legacy network) through an antenna (e.g., first antenna module 242) and may be preprocessed through an RFFE (e.g., first RFFE 232). The first RFIC 222 may convert the preprocessed RF signals to baseband signals that may be processed by the first communication processor 212.

In signaling, the second RFIC 224 may convert baseband signals generated by the first communication processor 212 or the second communication processor 214 into RF signals (hereinafter, referred to as "5gsub6 RF signals") of Sub6 frequency bands (e.g., about 6GHz or less) for the second cellular network 294 (e.g., a 5G network). Upon signal reception, a 5G Sub6 RF signal may be acquired from a second cellular network 294 (e.g., a 5G network) through an antenna (e.g., second antenna module 244) and may be preprocessed through an RFFE (e.g., second RFFE 234). The second RFIC 224 may convert the pre-processed 5g Sub6 RF signal to a baseband signal that may be processed by the corresponding communication processor of the first communication processor 212 or the second communication processor 214.

The third RFIC 226 may convert baseband signals generated by the second communication processor 214 into RF signals (hereinafter referred to as "5G Above6 RF signals") of a 5G Above6 band (e.g., from about 6GHz to about 60 GHz) to be used in a second cellular network 294 (e.g., a 5G network). Upon signal reception, the 5G Above6 RF signal may be acquired from the second cellular network 294 (e.g., a 5G network) via an antenna (e.g., antenna 248) and may be preprocessed via the third RFFE 236. The third RFIC 226 may convert the preprocessed 5g Above6 RF signal to a baseband signal that may be processed by the second communication processor 214. According to an embodiment, the third RFFE 236 may be formed as part of the third RFIC 226.

According to an embodiment, the electronic device 101 may include a fourth RFIC 228 separate from the third RFIC 226 or as at least a portion of the third RFIC 226. The fourth RFIC 228 may convert the baseband signal generated by the second communication processor 214 into an RF signal (hereinafter, referred to as an "IF signal") in an intermediate frequency band (e.g., from about 9GHz to about 11 GHz), and may then transmit the IF signal to the third RFIC 226. The third RFIC 226 may convert the IF signal to a 5g Above6 RF signal. Upon signal reception, the 5G Above6 RF signal may be received from the second cellular network 294 (e.g., a 5G network) via an antenna (e.g., antenna 248) and may be converted to an IF signal by the third RFIC 226. The fourth RFIC 228 may convert the IF signal to a baseband signal that may be processed by the second communication processor 214.

According to embodiments, the first RFIC 222 and the second RFIC 224 may be implemented as at least a portion of a single package or a single chip. According to various embodiments, in fig. 2a or 2b, when the first RFIC 222 and the second RFIC 224 are implemented as a single chip or a single package, the first RFIC 222 and the second RFIC 224 may be implemented as integrated RFICs. In this case, the integrated RFIC may be connected to the first RFFE 232 and the second RFFE 234 to convert a baseband signal into a signal of a frequency band supported by the first RFFE 232 and/or the second RFFE 234, and may transmit the converted signal to one of the first RFFE 232 and the second RFFE 234. According to an embodiment, the first RFFE 232 and the second RFFE 234 may be implemented as at least a portion of a single package or a single chip. According to an embodiment, at least one of the first antenna module 242 or the second antenna module 244 may be omitted or may be combined with the other antenna module to process RF signals of a plurality of frequency bands corresponding thereto.

According to an embodiment, the third RFIC 226 and the antenna 248 may be arranged on the same substrate to form a third antenna module 246. For example, the communication module 192 or the processor 120 may be disposed on a first substrate (e.g., a main PCB). In this case, the third antenna module 246 may be formed by disposing the third RFIC 226 in a partial region (e.g., a lower surface) of a second substrate (e.g., a sub PCB) different from the first substrate, and disposing the antenna 248 in another partial region (e.g., an upper surface) of the second substrate. Providing the third RFIC 226 and the antenna 248 on the same substrate may reduce the length of the transmission line between them. This may reduce the loss (e.g., attenuation) suffered by signals in the high frequency band (e.g., from about 6GH to about 60 GHz) through the transmission line, such as used for 5G network communications. Accordingly, the electronic device 101 may enhance the quality or speed of communication with the second network 294 (e.g., a 5G network).

According to an embodiment, the antenna 248 may be formed as an antenna array comprising a plurality of antenna elements that may be used for beamforming. In this case, for example, the third RFIC 226 may include a plurality of phase shifters 238 corresponding to a plurality of antenna elements as part of the third RFFE 236. Each of the plurality of phase shifters 238 may shift the phase of a 5G Above6 RF signal to be transmitted outside the electronic device 101 (e.g., a base station of a 5G network) through a corresponding antenna element when the signal is transmitted. Upon signal reception, each of the plurality of phase shifters 238 may shift the phase of the 5gabove6 RF signal externally received through the corresponding antenna element to the same or substantially the same phase. This enables transmission or reception by beamforming between the electronic apparatus 101 and the outside.

The second cellular network 294 (e.g., a 5G network) may operate independently (e.g., independent (SA)) from the first cellular network 292 (e.g., a legacy network) or may operate while connected to the first cellular network 192 (e.g., non-independent (NSA)). For example, a 5G network may include only an access network (e.g., a 5G Radio Access Network (RAN) or a next generation RAN (NG RAN)), and may not include a core network (e.g., a Next Generation Core (NGC)). In this case, the electronic device 101 may access an access network of the 5G network and then may access an external network (e.g., the internet) under the control of a core network (e.g., an Evolved Packet Core (EPC)) of the legacy network. Protocol information for communicating with a legacy network (e.g., LTE protocol information) or protocol information for communicating with a 5G network (e.g., new Radio (NR) protocol information) may be stored in the memory 230 and may be accessed by another component (e.g., the processor 120, the first communication processor 212, or the second communication processor 214).

According to various embodiments, in operation 311, the UE 300 (e.g., the electronic device 101) camps on the fifth generation system (5 GS) using a next generation radio access network (NG-RAN) 301, an access and mobility management function (AMF) 302, and a User Plane Function (UPF) 303. For example, the UE 300 may reside on a Universal Mobile Telecommunications System (UMTS) terrestrial radio access (E-UTRA) cell or a New Radio (NR) cell in 5 GS. For example, when the 5GS supports emergency services, the support may be sent to the UE 300 through a registration accept message, and may be performed, for example, based on TA and RAT.

According to various embodiments, in operation 313, the UE 300 may identify that it is requested to conduct an emergency session. For example, a pending IMS emergency session request (e.g., voice) may be received from an upper layer. In operation 315, the UE 300 may send a service request to the AMF 302. When the AMF 302 indicates support for emergency service fallback in the registration accept message, a typical UE 300 supporting emergency service fallback may typically send a service request, with the service type configured as emergency service fallback in order to initiate emergency services. This may follow, for example, but not limited to, third generation project partnership project (3 GPP) Technical Specification (TS) 23.502.

According to various embodiments, in operation 317, the AMF 302 may provide an N2 request for emergency back-off to the NG-RAN 301. After receiving a service request for emergency services, AMF 302 may trigger an N2 procedure based on factors such as N26 availability, network configuration, and raid conditions, which N2 procedure results in an IDLE (IDLE) state move (redirect) or a connection (CONNECTED) state move (handover procedure) to E-UTRA/5GC or E-UTRAN/EPC. The 5GC may request an emergency service fallback by performing an NG-AP procedure informing the NR-RAN 301 that the emergency service fallback is a fallback for emergency services. Based on support of emergency services within the Evolved Packet Core (EPC) or 5GC, the AMF 302 may inform the target core network of the RAN node to identify that inter-RAT or inter-system fallback is performed. When the AMF 302 initiates a redirection to the UE 300 for which authentication has been successful, the AMF 302 may include a security context in the triggered fallback request to the NG-RNA 301.

According to various embodiments, in operation 319, inter-RAT handover or RRC redirection to E-UTRA connected to 5GC may be performed. The AMF 302 may redirect the UE 300 to the appropriate RAT/system by using the service type indication in the service request. For example, when the UE 300 is currently camped on an NR cell, one of the following two procedures may be performed.

-handover or redirection to Evolved Packet System (EPS) 304

-handover or redirection to Universal Mobile Telecommunications System (UMTS) terrestrial radio access (E-UTRA) connected to a fifth generation core (5 GC)

In operation 321, the NG-RAN 301 may initiate a redirection or handover to the E-UTRAN connected to the EPS 304. The NG-RAN 301 may use the security context provided by the AMF 302. If a redirection procedure is used in operation 319 or operation 321, the redirection procedure may be provided to the UE 300 so that the target core network may perform an appropriate NAS procedure.

After handover to the target cell, the UE 300 may establish a PDU session/PDN connection for IMS emergency services in operation 323. The UE 300 may perform an IMS procedure for establishing an IMS emergency session according to a method based on, for example, 3gpp TS 23.617.

Fig. 3b shows a flow chart of a comparative example for comparison with various embodiments. At least some operations of the electronic apparatus 101 according to the comparative example may also be performed by the electronic apparatus 101 according to various embodiments.

In operation 331, the UE 300 (e.g., the electronic device 101) may send a service request to the network 306, wherein the service type is configured as an emergency service fallback. As described with reference to fig. 3a, the UE 300 may expect to receive a handover command (e.g., a mobility from nrcommand) or an RRC release message causing redirection (e.g., an RRCConnectionrelease message in E-UTRA, or an RRC release message in NR) from the network 306. In operation 333, the UE 300 may start a timer T3517 based on the transmission of the service request. The timer T3517 may be defined in, for example, 3gpp TS 24.501 and may have an expiration time of, for example, 15 seconds, but is not limited thereto. The timer T3517 may be started based on the transmission of the service request message. For example, the timer T3517 may be stopped based on the receipt of a message in response to a service request.

In one example, in operation 335, the network 306 may send a message in response to the service request. However, depending on the electric field situation, the UE 300 may not be able to receive messages from the network 306. Alternatively, although not shown, in another example, the network 306 may not be able to receive a service request from the UE 300, and in this case, the network 306 may not send a message in response to the service request. In another example, the network 306 receives a service request from the UE 300, but may not send a message in response to the service request due to an internal error of the network 306. According to various examples described above, the UE 300 may fail to receive a message from the network 306 during the expiration time of the timer T3517. In operation 337, the UE 300 may identify expiration of the timer T3517. When the timer T3517 expires, the UE 300 may terminate the emergency service procedure. For example, when the service type in the service request message is configured as an "emergency service fallback" and when the service request procedure is initiated in the 5GMM-IDLE mode, the 5GMM sublayer may stop the service request procedure, release the resources allocated for the service request procedure, and notify the upper layer of the failure of the service request procedure. Alternatively, when the service type in the service request message is configured as an "emergency service fallback" and when the service request procedure is initiated in the 5GMM-CONNECTED mode, the 5GMM sublayer may stop the service request procedure, maintain in the 5GMM-CONNECTED mode, and notify the upper layer of the failure of the service request procedure.

As in 3gpp TS 24.501, when the expiration time of timer T3517 is 15 seconds, UE 300 may display a screen showing that emergency services (e.g., emergency call connection) are being attempted for 15 seconds. Therefore, there is a problem in that the waiting time for emergency services becomes long even in an emergency.

According to various embodiments, in operation 401, the electronic device 101 (e.g., at least one of the processor 120, the first communication processor 212, the second communication processor 214, or the integrated communication processor 260) may identify an event related to an emergency service when registered in the first communication system. For example, assume that the electronic apparatus 101 is registered in 5GS (or 5 GC). The electronic device 101 may receive an emergency service fallback request from an upper layer in a 5GMM-IDLE mode, a 5GMM-CONNECTED mode over 3GPP access, or a 5GMM-CONNECTED mode with an RRC inactivity indication. For example, an E-UTRA or NR-based RAT may register the electronic device 101 in 5GS, and the RAT is not limited. In the present embodiment, it is assumed that the electronic apparatus 101 is initially registered in 5GS (or 5 GC), but a communication system (or core network) of registering the electronic apparatus 101 is not limited. For example, the electronic device 101 may obtain an emergency call request and may identify the obtained emergency call request as an event related to emergency services. The type of emergency service is not limited.

According to various embodiments, in operation 403, the electronic device 101 may send a service request message corresponding to the event to the network. For example, the electronic device 101 may configure the service type in the service request message as "emergency service fallback". The purpose of the service type element is to specify the purpose of the service request procedure. The service type is a type 1 information element and may follow, for example, 3gpp TS 24.501, but is not limited thereto. For example, the electronic device 101 may configure the service type as "emergency service fallback" by configuring the service type value "0100".

According to various embodiments, in operation 405, the electronic device 101 may start a timer based on the transmission of the service request message. For example, the electronic device 101 may start a timer having an expiration time shorter than the expiration time of the timer T3517. For example, the expiration time of the timer may be configured based on the time it takes for the electronic device 101 to send a service request message to the network and receive a message from the network in response to the service request message. For example, the network operator may configure a maximum period for responding to the service request message, and a time equal to or longer than the maximum period may be configured as an expiration time of the timer, but the configuration method is not limited. For example, the expiration time of the timer may be configured to be 1 second shorter than 15 seconds of the timer T3517. Since there may be a time difference between a transmission time point of the service request message and a reception time point of the response message according to a network operator, the expiration time of the timer may be specific to the network operator and may vary depending on the network condition according to an embodiment.

According to various embodiments, in operation 407, the electronic device 101 may search for and select a cell corresponding to a PLMN of a second communication system (e.g., EPS) based on failing to receive a response until expiration of a timer. For example, the electronic device 101 may preferentially search for and/or select a Registered PLMN (RPLMN) and/or a Home PLMN (HPLMN) of the second communication system, but is not limited thereto. The electronic device 101 may search for at least one cell corresponding to the selected PLMN. For example, the electronic device 101 may search for cells or perform a full scan based on the stored information. The electronic device 101 may select one cell from among at least one cell identified based on the cell search result. For example, the electronic apparatus 101 may select a cell satisfying the cell selection criteria, but the cell selection method is not limited. As will be described later, the electronic apparatus 101 may identify a cell determined to support the second communication system.

According to various embodiments, when a cell is selected, the electronic apparatus 101 may perform at least one operation for registering in the second communication system in operation 409. For example, the electronic device 101 may perform a RACH procedure on the selected cell. The electronic device 101 performs a Tracking Area Update (TAU) procedure on the second communication system (EPS) or a core network (e.g., EPC) of the second communication system by using the RRC connection established based on the RACH procedure. Alternatively, the electronic device 101 may perform an attachment procedure to the core network of the second communication system.

In an example, the electronic device 101 may select a cell supporting (or connected to) the second communication system from among cells corresponding to PLMNs of the second communication system. For example, the electronic device 101 may identify the type of communication system (e.g., core network) supported by the cell based on system information (e.g., SIB 1) from the cell. Table 1 is an example of SIB 1 (e.g., systemiformationblocktype 1).

TABLE 1

SIB 1 in table 1 may include "PLMN-Identity info" including "PLMN-Identity" and/or "PLMN-Identity info-r15" including "PLMN-Identity-5GC-r 15". For example, the fact that "PLMN-identity info" is included in SIB 1 may suggest that the cell corresponding to SIB 1 supports EPC. For example, the fact that "PLMN-identity info-r15" is included in SIB 1 may suggest that the cell corresponding to SIB 1 supports 5GC. The electronic device 101 may select a cell supporting the second communication system based on the information included in SIB 1 described above. If the electronic device 101 needs to fall back to EPS, the electronic device 101 may select a cell supporting EPS by selecting a cell that has transmitted SIB 1 that includes "plmn-Identity".

According to various embodiments, in operation 411, the electronic device 101 may perform a service corresponding to an event based on registration in the second communication system. For example, the electronic device 101 may perform at least one process for establishing an IMS emergency session. At least one procedure for establishing an IMS emergency session may follow, for example, 3gpp TS 23.167, but is not limited thereto.

As described above, after the emergency service fallback operation is completed, establishment of the IMS emergency session may be started in the network of the second communication system (e.g., EPS) that has performed the new registration. Accordingly, even when the electronic device 101 does not receive the response message before the timer T3517 expires and the communication system falls back to the second communication system, the IMS emergency session is established later, and thus the emergency service is likely to operate normally. Thus, emergency services may be performed after a relatively short expiration time of the timer (e.g., 1 second) without waiting 15 seconds, which is the standard expiration time of T3517.

According to various embodiments, in operation 501, the electronic device 101 (e.g., at least one of the processor 120, the first communication processor 212, the second communication processor 214, or the integrated communication processor 260) may identify an event related to an emergency service when registered in the first communication system. In operation 503, the electronic device 101 may send a service request message corresponding to the event to the network and may start a timer. As described above, the electronic device 101 may send a service request message in which the service type is configured as "emergency service fallback". The timer started in operation 503 may have an expiration time shorter than that of the timer T3517.

According to various embodiments, in operation 505, the electronic device 101 may identify whether a response has been received from the network. When a response has been received from the network (505—yes), the electronic device 101 may perform a rollback operation to perform a system rollback and may perform a service corresponding to the event in the system in which the rollback has been performed in operation 507. For example, when the electronic device 101 has received an RRC release message from the network that causes redirection, the electronic device 101 may perform an operation for redirection. The electronic device 101 may perform a cell search based on the reception of the RRC release message and may select a cell based on the search result. The electronic device 101 may perform a RACH procedure on the selected cell. The electronic device 101 may perform registration (e.g., TAU procedure or attach procedure) in the second communication system based on the RRC connection established based on the result of performing the RACH procedure. For example, when the electronic apparatus 101 has received a handover command from the network, the electronic apparatus 101 may perform an operation of handover to a target cell specified in the handover command. The at least one operation for redirecting and/or the at least one operation for switching from the first communication system to the second communication system may follow, for example, 3gpp TS 23.502, but is not limited thereto.

According to various embodiments, when no response is received from the network (505-no), the electronic device 101 may identify whether the timer has expired in operation 509. Before the timer expires (509-no), the electronic device 101 may monitor whether a response is received from the network. When the timer has expired (509-yes), the electronic device 101 may perform at least one operation for selecting a cell corresponding to a PLMN of the second communication system and registering with the second communication system in operation 511. When the timer expires, the electronic device 101 may search for and/or select a cell corresponding to the PLMN of the second communication system even if no message is received from the network. The electronic device 101 may be registered in the second communication system by performing a RACH procedure on one of the selected cells corresponding to the PLMN and performing a TAU procedure or an attach procedure on the second communication system based on the established RRC connection. In operation 513, the electronic device 101 may perform a service corresponding to the event based on the registration in the second communication system. For example, the electronic device 101 may perform an emergency call based on the second communication system.

According to various embodiments, in operation 601, the electronic device 101 (e.g., at least one of the processor 120, the first communication processor 212, the second communication processor 214, or the integrated communication processor 260) may identify an event related to an emergency service when registered in the first communication system. In operation 603, the electronic device 101 may transmit a service request message corresponding to the event to the network, and may start a timer. As described above, the electronic device 101 may send a service request message in which the service type is configured as "emergency service fallback". For example, the timer started in operation 603 may have an expiration time shorter than that of the timer T3517. In operation 605, the electronic device 101 may receive a response from the network before the timer expires. For example, the electronic device 101 may receive an RRC release message requesting redirection to a cell of the second communication system or a handover command requesting handover to a cell of the second communication system. The electronic device 101 may stop the timer based on receiving a message from the network.

According to various embodiments, in operation 607, the electronic device 101 may identify whether a cell of the second communication system is found. If a cell of the second communication system is found (607-yes), in operation 609, the electronic device 101 may perform a TAU procedure based on one of the found cells. For example, when the electronic device 101 is connected to a second communication system (e.g., EPS), the electronic device 101 may perform at least one operation for switching from 5GS to EPS, or at least one operation for inter-system redirection of the N26 interface to EPS. In both cases, the electronic apparatus 101 may perform a TAU procedure and may perform a procedure such as 3gpp TS 23.502, but is not limited thereto. After performing the TAU procedure, the electronic device 101 may perform an IMS-based emergency service in operation 611. For example, the electronic device 101 may perform at least one procedure for establishing an IMS emergency session, and may perform emergency services (e.g., emergency calls) based on the IMS emergency session. If no cell is found for the second communication system (607-no), then in operation 613 the electronic device 101 may register in a third communication system (e.g., UTMS or GSM) to perform CS-based services.

In various embodiments, the electronic device 101 may identify information about the core network specified in the RRC release message. As described above, to fall back to the second communication system (e.g., the second core network), the network may send an RRC release message specifying the second core network. For example, table 2 is an example of an RRCRelease message defined in 3gpp TS 38.331.

TABLE 2

As in table 2, the RRCRelease message may include the frequency to be redirected (e.g., eutraFrequency ARFCN-ValueEUTRA) and the core network to be redirected (e.g., cnType ENUMERATED epc, fiveGC). If the network sends an RRCRelease message with a cnType of "EPC", the electronic device 101 may perform emergency services only when camping on a cell supporting EPC. Accordingly, the electronic device 101 may be configured to select a cell supporting the core network specified in the RRC release message.

For example, the electronic device 101 may identify system information, such as a System Information Block (SIB) 1, corresponding to each of the at least one cell identified during the search. Based on the system information, e.g., information included in SIB 1, the electronic device 101 may identify a core network supported by each of the at least one cell. As described above, based on whether "PLMN-identity info" and/or "PLMN-identity info-r15" are included in SIB 1, the electronic device 101 may identify whether the corresponding cell supports EPC (or EPS) and/or 5GC (or 5 GS). The electronic device 101 may select a cell corresponding to the core network specified in the RRC release based on SIB 1.

According to various embodiments, the electronic device 101 may camp on a cell supporting the core network specified in the RRC release message and perform subsequent procedures, thereby performing emergency services.

According to various embodiments, in operation 701, the electronic device 101 (e.g., at least one of the processor 120, the first communication processor 212, the second communication processor 214, or the integrated communication processor 260) may identify an event related to an emergency service when registered in the first communication system. In operation 703, the electronic device 101 may transmit a service request message corresponding to the event to the network and may start a timer. As described above, the electronic device 101 may send a service request message in which the service type is configured as "emergency service fallback". For example, the expiration time of the timer started in operation 703 may be shorter than the expiration time of the timer T3517. The electronic device 101 may not be able to identify a response from the network during the expiration time of the timer and, in operation 705, may identify the expiration of the timer.

According to various embodiments, in operation 707, the electronic apparatus 101 may select a PLMN corresponding to the second communication system. Based on the identification of the event related to the emergency service and/or the type of service configured as "emergency service fallback", the electronic device 101 may identify that the PLMN to be found corresponds to the second communication system. Thus, the electronic device 101 may avoid selecting PLMNs corresponding only to the first communication system. In operation 709, the electronic apparatus 101 may identify whether a cell corresponding to the selected PLMN is found. In an example, the electronic device 101 may select a cell supporting (or connected to) the second communication system. For example, the electronic device 101 may select and camp on an appropriate cell based on the cell search result, but there is no limitation on the camping cell. The electronic device 101 may perform a cell search based on the stored information or may perform a full scan. In an example, the electronic device 101 may identify whether a particular cell supports the second communication system based on SIB 1 identified as a result of the cell search. The electronic device 101 may select and camp on a cell determined to support the second communication system. For example, when the reception intensity of the synchronization signal from the first cell is greater than the reception intensity of the synchronization signal from the second cell according to the cell search result, the electronic apparatus 101 may select and camp on the second cell on the assumption and when it is recognized that the first cell does not support the second communication system and the second cell supports the second communication system.

According to various embodiments, in operation 711, the electronic device 101 may select a cell, perform a RACH procedure, and perform a TAU procedure (or an attach procedure). After registering in the second communication system, the electronic device 101 may perform an IMS-based emergency service in operation 713. For example, the electronic device 101 may perform at least one procedure for establishing an IMS emergency session, and may perform emergency services (e.g., emergency calls) based on the IMS emergency session. When no cell of the second communication system is found (709-no), the electronic device 101 may register in a third communication system (e.g., UTMS or GSM) to perform CS-based services in operation 715.

According to various embodiments, in operation 801, the electronic device 101 (e.g., at least one of the processor 120, the first communication processor 212, the second communication processor 214, or the integrated communication processor 260) may perform an IMS-based emergency service by using the second communication system. For example, when registering in the first communication system, the electronic device 101 may identify an event related to emergency services. The electronic device 101 may send a service request message to the network with the service type configured as "emergency service back-off". In an example, the electronic device 101 may receive a message from the network in response to the service request message and may perform a redirection or handoff to the second communication system. In another example, the electronic device 101 may select and register a PLMN of the second communication system based on expiration of a timer having an expiration time shorter than an expiration time of the timer T3517. The electronic device 101 may perform emergency services based on registration in the second communication system. In operation 803, the electronic device 101 may terminate the emergency service execution. The electronic apparatus 101 may remain registered in the second communication system even after the emergency service execution is terminated.

When registering in the second communication system to perform the emergency service, the electronic device 101 may receive a message, such as an RRC release message, from the network requesting redirection of the first communication system in operation 805 after the emergency service is terminated, according to various embodiments. For example, the electronic device 101 may perform emergency services based on a cell supporting E-UTRA registered in the EPC, and may then terminate the performance of the emergency services. The electronic device 101 may receive an RRCConnectionRelease message from the network indicating redirection to 5GC. The RRCConnectionRelease message may include the core network (e.g., cn-Type-r15 ENUMERATED { epc, fivegc }) to which redirection is to be performed. When cn-Type-r15 ENUMERATED is designated as fivegc, the electronic apparatus 101 may identify that the core network to perform redirection is 5GC. When it is identified that the electronic device 101 has terminated emergency services, the network according to various embodiments may redirect the electronic device 101 to the communication system prior to fallback.

According to various embodiments, in operation 807, the electronic device 101 may reside on a cell of a first communication system. For example, the electronic device 101 may reside on a cell supporting a first communication system. When the electronic device 101 receives an RRC release message that causes redirection to 5GC, the electronic device 101 may select and camp on one of the 5 GC-capable cells. For example, the electronic device 101 may identify the type of core network supported by the cell based on SIB 1 identified as a result of the search. In operation 809, the electronic apparatus 101 may perform a RACH procedure for a cell. In operation 811, the electronic device 101 may perform registration (e.g., a TAU procedure or an attach procedure) in the first communication system. As described above, after the emergency service is terminated, the electronic device 101 may return to the first communication system again before the fallback.

According to various embodiments, in operation 901, the electronic device 101 (e.g., at least one of the processor 120, the first communication processor 212, the second communication processor 214, or the integrated communication processor 260) may perform an IMS-based emergency service by using the second communication system. As described with reference to fig. 8, the electronic device 101 may transmit a service request message corresponding to an emergency service based on a response from the network or based on expiration of a timer, and may be registered in the second communication system. The electronic device 101 may perform emergency services based on registration in the second communication system. In operation 903, the electronic device 101 may terminate the emergency service execution. The electronic device 101 may remain registered in the second communication system even after the emergency service is terminated.

According to various embodiments, in operation 905, the electronic device 101 may receive an RRC reconfiguration message including an MO associated with the first communication system from a serving cell. The RRC reconfiguration message may be an rrcconnectionreconfigurability message of 3gpp TS 36.331 or an rrcrecnonfigurability message of 3gpp TS 38.331. The MO may include information related to a frequency (or cell) to be measured by a User Equipment (UE). The RRC reconfiguration message may include a reporting configuration and may include, for example, reporting criteria for performing Measurement Reporting (MR), the RRC reconfiguration message may include at least one of a measurement ID for identifying an MO, a configuration indicating the number of values to be measured by the UE, or a measurement gap related to a measurement period.

According to various embodiments, in operation 907, the electronic device 101 may identify that MO-based measurement results (e.g., layer 3 filtered values) meet reporting criteria. For example, at a measurement timing of a signal (e.g., synchronization signal and/or reference signal) from a cell of the first communication system, a Reference Signal Received Power (RSRP), a Reference Signal Received Quality (RSRQ), a signal to interference plus noise ratio (SINR), a Received Signal Strength Indicator (RSSI), and/or a signal to noise ratio (SNR) may be identified as meeting reporting criteria. In operation 909, the electronic device 101 may perform Measurement Reporting (MR) based on the reporting criteria being met. The network may send a handover command to the electronic device 101 indicating that the target cell of the first communication system is supported (or connected) based on the received MR. In operation 911, the electronic device 101 may receive the switch command. In operation 913, the electronic device 101 may perform handover based on the received handover command and thus may register in the first communication system based on the target cell supporting the first communication system.

According to various embodiments, in operation 1001, the electronic device 101 (e.g., at least one of the processor 120, the first communication processor 212, the second communication processor 214, or the integrated communication processor 260) may perform an IMS-based emergency service by using the second communication system. As described with reference to fig. 8, the electronic device 101 may transmit a service request message corresponding to an emergency service based on a response from the network or based on expiration of a timer, and may be registered in the second communication system. The electronic device 101 may perform emergency services based on registration in the second communication system. In operation 1003, the electronic apparatus 101 may terminate the emergency service execution. The electronic device 101 may remain registered in the second communication system even after the emergency service is terminated. In operation 1005, the electronic apparatus 101 may enter an IDLE (IDLE) state while remaining registered in the second communication system.

According to various embodiments, the electronic device 101 may receive the SIB24 from a serving cell (e.g., eNB). In 3GPP TS 36.331, SIB24 is described as an Information Element (IE) of system information block type 24 (systemization blcoktype 24). SIB24 may include information related to NR neighbor cells only and inter-RAT cell reselection for cell reselection, e.g., information about NR frequencies supporting the SA mode of 5G. SIB24 may include frequency-shared cell reselection parameters. The SIB24 may include frequency information (e.g., ARFCN) such as NR supporting SA mode. The frequency information of NR supporting the SA mode may suggest information supporting 5GC (or 5 GS). When camping on a cell associated with a second communication system (e.g., EPC), the electronic device 101 may identify cell information, e.g., information about cells supporting 5GC, surrounding the cell that support NR of SA mode of the first communication system (e.g., 5 GC). The electronic device 101 according to various embodiments may identify frequencies of SA modes nearby supporting the first communication system (e.g., 5 GS) based on information included in the SIB 24.

In operation 1007, the electronic device 101 according to various embodiments may measure a frequency associated with the first communication system and identified based on the SIB 24. In operation 1009, the electronic apparatus 101 may identify that the measurement result satisfies the cell reselection criterion. In operation 1011, the electronic apparatus 101 may perform cell reselection based on meeting the cell reselection criteria. The electronic device 101 may camp on the reselected cell and thus may return to the first communication system (e.g., 5 GS).

According to various embodiments, in operation 1101, the electronic device 101 (e.g., at least one of the processor 120, the first communication processor 212, the second communication processor 214, or the integrated communication processor 260) may perform an IMS-based emergency service by using the second communication system. As described with reference to fig. 8, the electronic device 101 may transmit a service request message corresponding to an emergency service based on a response from the network or based on expiration of a timer, and may be registered in the second communication system. The electronic device 101 may perform emergency services based on registration in the second communication system. In operation 1103, the electronic device 101 may terminate the emergency service execution. The electronic device 101 may remain registered in the second communication system even after the emergency service is terminated. In operation 1105, the electronic apparatus 101 may identify the passage of the specified time. The electronic apparatus 101 may recognize that registration in the second communication system to which fallback has been performed is held until, for example, a specified time elapses.

According to various embodiments, in operation 1107, the electronic device 101 may scan a pre-stored frequency associated with the first communication system based on the registration held in the second communication system to which fallback has been performed until a specified time elapses. For example, the electronic apparatus 101 may previously store and manage information on frequencies supporting the SA mode of the first communication system in advance. For example, when registering in (or connecting to) the first communication system in the SA mode, the electronic apparatus 101 may store the frequency. In operation 1109, the electronic device 101 may identify that the measurement result of the specific frequency meets the cell reselection criterion. In operation 1111, the electronic apparatus 101 may perform cell reselection based on the cell reselection criterion being met.

According to various embodiments, in operation 1201, the electronic device 101 (e.g., at least one of the processor 120, the first communication processor 212, the second communication processor 214, or the integrated communication processor 260) may identify an event related to an emergency service when registered in the first communication system. For example, when registered in 5GS (or 5 GC), the electronic device 101 may identify an event related to emergency services. For example, the electronic device 101 may obtain an emergency call request and may identify the obtained emergency call request as an event related to emergency services. The type of emergency service is not limited. In operation 1203, the electronic device 101 may send a service request message corresponding to the event to the network. For example, the electronic device 101 may configure the service type in the service request message as "emergency service fallback".

According to various embodiments, in operation 1205, the electronic device 101 may select and search for a PLMN of a second communication system (e.g., EPS) based on the transmission of the service request message. For example, the electronic device 101 may preferentially select and search for a Registered PLMN (RPLMN) and/or a Home PLMN (HPLMN) of the second communication system, but is not limited thereto. In operation 1207, the electronic device 101 may identify whether a cell corresponding to the selected PLMN is found. For example, the electronic apparatus 101 may search for a cell associated with the second communication system and corresponding to the selected PLMN, and may perform, for example, search and/or full scan based on stored information, but the search method is not limited thereto. In contrast to the embodiment in fig. 4, after sending the service request message, the electronic device 101 may select a PLMN of the second communication system and search for a cell without waiting for the timer to expire.

When a cell corresponding to the selected PLMN is identified (1207-yes), the electronic apparatus 101 may select a cell and may perform a RACH procedure and a TAU procedure (or an attach procedure) in operation 1209. Thus, the electronic apparatus 101 may register in the second communication system. In operation 1211, the electronic device 101 may perform an IMS-based emergency service when registering in the second communication system. After the execution of the emergency service is terminated, the electronic device 101 may return to the first communication system according to a method based on, for example, fig. 8, 9, 10 or 11. When a cell corresponding to the selected PLMN is not identified (1207-no), the electronic device 101 may register in the third communication system to perform CS-based services in operation 1213. As described above, it is possible to prevent an error in an electric field or a network from causing a delay in performing an emergency service.

According to various embodiments, in operation 1301, the electronic apparatus 101 (e.g., at least one of the processor 120, the first communication processor 212, the second communication processor 214, or the integrated communication processor 260) may identify an event related to the emergency service when registering in the first communication system. For example, when registered in 5GS (or 5 GC), the electronic device 101 may identify an event related to emergency services. For example, the electronic device 101 may obtain an emergency call request and may identify the obtained emergency call request as an event related to emergency services. The type of emergency service is not limited.

According to various embodiments, in operation 1303, the electronic device 101 may select a PLMN of a second communication system (e.g., EPS) based on the identification of the event related to the emergency service. For example, the electronic device 101 may preferentially search for and select a Registered PLMN (RPLMN) and/or a Home PLMN (HPLMN) of the second communication system, but is not limited thereto. In operation 1305, the electronic apparatus 101 may determine whether a cell corresponding to the selected PLMN is identified. For example, the electronic apparatus 101 may search for a cell associated with the second communication system and corresponding to the selected PLMN, and may perform, for example, search and/or full scan based on stored information, but the search method is not limited thereto. In contrast to the embodiment of fig. 4, without sending a service request message, the electronic device 101 may select a PLMN of the second communication system and may search for a cell in response to an event acknowledgement related to the emergency service. For example, when the electronic device 101 has identified during registration of the first communication system that the emergency service back-off indicator indicates "not supported," the electronic device 101 may search for a cell corresponding to the second communication system in response to the event identification without sending the service request message.

When a cell corresponding to the selected PLMN is identified (1305-yes), the electronic apparatus 101 may select a cell and perform a RACH procedure and a TAU procedure (or an attach procedure) in operation 1307. Thus, the electronic apparatus 101 may register in the second communication system. In operation 1309, the electronic apparatus 101 may perform an IMS-based emergency service in a state of being registered in the second communication system. After the execution of the emergency service is terminated, the electronic device 101 may return to the first communication system according to a method based on, for example, fig. 8, 9, 10 or 11. When a cell corresponding to the selected PLMN is not identified (1207-no), the electronic device 101 may register in the third communication system to perform CS-based services in operation 1311. As described above, it is possible to prevent an error in an electric field or a network from causing a delay in performing an emergency service.

According to various embodiments, the at least one processor may be configured to send a service request to the network for a service type including an emergency service fallback as at least part of sending the service request corresponding to the event to the network.

According to various embodiments, the at least one processor may be configured to perform a RACH procedure with the selected cell as at least part of performing at least one operation for registering in the second communication system based on the selected cell, and to perform a procedure for registering in the second communication system based on an RRC connection established based on the RACH procedure.

According to various embodiments, the at least one processor may be configured to select, as at least part of selecting a cell, the cell based on information included in SIB 1 from the cell and based on the cell supporting the second communication system.

According to various embodiments, the at least one processor may be configured to perform at least one procedure for establishing an IMS emergency session as at least part of performing an emergency service corresponding to the event.

According to various embodiments, the at least one processor may be further configured to receive an RRC release message requesting redirection from a network before the timer expires, and to perform a procedure for redirecting to the second communication system specified in the RRC release message based on the reception of the RRC release message.

According to various embodiments, the at least one processor may be further configured to receive a handover command from the network before the timer expires, and to perform a procedure for handover to a target cell supporting the second communication system and specified in the handover command based on the handover command.

According to various embodiments, the at least one processor may be further configured to identify frequency information supporting the SA mode of the first communication system and identified by SIB 24 received from a serving cell, identify another cell supporting the SA mode of the first communication system based on the identified frequency information after performing the emergency service, and reselect the other cell based on the other cell satisfying a cell reselection condition.

According to various embodiments, the at least one processor may be further configured to identify frequency information supporting the SA mode of the first communication system and stored in the electronic device, identify another cell supporting the SA mode of the first communication system based on the identified frequency information based on a specified time elapsed after the emergency service is performed, and reselect the other cell based on the other cell satisfying a cell reselection condition.

According to various embodiments, the at least one processor may be further configured to receive an RRC release message requesting redirection to the first communication system after performing the emergency service, and to perform a procedure for redirecting to the first communication system specified in the received RRC release message.

According to various embodiments, the at least one processor may be further configured to: after performing the emergency service, receiving an RRC reconfiguration message including a measurement object; performing measurement reporting based on a measurement result based on the measurement object satisfying a reporting condition; and performing a procedure for handover to the target cell specified in the handover command based on receiving the handover command in response to the measurement report.

According to various embodiments, a method of operating an electronic device may include: identifying an event associated with an emergency service when registered in a first communication system; based on the identification of the event, sending a service request corresponding to the event to a network; starting a timer having an expiration time shorter than that of the timer T3517 based on the transmission of the service request; searching and selecting a cell corresponding to a PLMN of a second communication system different from the first communication system based on failing to receive a response corresponding to the service request until the timer expires; performing at least one operation for registering in the second communication system based on the selected cell; and performing an emergency service corresponding to the event based on the second communication system based on registration in the second communication system.

According to various embodiments, sending a service request corresponding to the event to the network includes sending a service request including a service type of emergency service fallback to the network.

According to various embodiments, performing at least one operation for registering in the second communication system based on the selected cell may include performing a RACH procedure with the selected cell and performing a procedure for registering in the second communication system based on an RRC connection established based on the RACH procedure.

According to various embodiments, selecting a cell includes selecting the cell based on the cell supporting the second communication system based on information included in SIB 1 from the cell.

According to various embodiments, performing an emergency service corresponding to the event includes performing at least one procedure for establishing an IMS emergency session.

According to various embodiments, the method of operation of the electronic device may further include receiving an RRC release message requesting redirection from a network before the timer expires, and performing a procedure for redirecting to the second communication system specified in the RRC release message based on the reception of the RRC release message.

According to various embodiments, the method of operation of the electronic device may further include receiving a handover command from a network before the timer expires, and performing a procedure for handover to a target cell supporting the second communication system and specified in the handover command based on the handover command.

According to various embodiments, the method of operation of the electronic device may further include: identifying frequency information supporting an SA mode of the first communication system and identified by SIB 24 received from a serving cell; identifying another cell supporting an SA mode of the first communication system based on the identified frequency information after performing the emergency service; and reselecting the other cell based on the other cell satisfying a cell reselection condition.

The electronic device according to various embodiments may be one of various types of electronic devices. The electronic device may include, for example, a portable communication device (e.g., a smart phone), a computer device, a portable multimedia device, a portable medical device, a camera, a wearable device, or a household appliance. According to the embodiments of the present disclosure, the electronic device is not limited to those described above.

It should be understood that the various embodiments of the disclosure and the terminology used therein are not intended to limit the technical features set forth herein to the particular embodiments, but rather include various modifications, equivalents or alternatives to the respective embodiments. For the description of the drawings, like reference numerals may be used to refer to like or related elements. It will be understood that a noun in the singular corresponding to a term may include one or more things unless the context clearly indicates otherwise. As used herein, each of the phrases such as "a or B", "at least one of a and B", "at least one of a or B", "A, B or C", "at least one of A, B and C", and "at least one of A, B or C" may include any or all possible combinations of items listed with a corresponding one of the plurality of phrases. As used herein, terms such as "1 st" and "2 nd" or "first" and "second" may be used to simply distinguish one element from another element and not to limit the element in other respects (e.g., importance or order). It will be understood that if the terms "operatively" or "communicatively" are used or the terms "operatively" or "communicatively" are not used, then if an element (e.g., a first element) is referred to as being "coupled to," "connected to," or "connected to" another element (e.g., a second element), it is intended that the element can be directly (e.g., wired) connected to, wireless connected to, or connected to the other element via a third element.

As used in connection with various embodiments of the present disclosure, the term "module" may include an element implemented in hardware, software, or firmware, and may be used interchangeably with other terms (e.g., "logic," "logic block," "portion," or "circuitry"). A module may be a single integrated component adapted to perform one or more functions or a minimal unit or portion of the single integrated component. For example, according to an embodiment, a module may be implemented in the form of an Application Specific Integrated Circuit (ASIC).

The various embodiments set forth herein may be implemented as software (e.g., program 140) comprising one or more instructions stored in a storage medium (e.g., internal memory 136 or external memory 138) readable by a machine (e.g., electronic device 101). For example, under control of a processor, a processor (e.g., processor 120) of the machine (e.g., electronic device 101) may invoke and execute at least one of the one or more instructions stored in the storage medium with or without the use of one or more other components. This enables the machine to operate to perform at least one function in accordance with the at least one instruction invoked. The one or more instructions may include code generated by a compiler or code capable of being executed by an interpreter. The machine-readable storage medium may be provided in the form of a non-transitory storage medium. Wherein the term "non-transitory" merely means that the storage medium is a tangible device and does not include a signal (e.g., electromagnetic waves), but the term does not distinguish between data being semi-permanently stored in the storage medium and data being temporarily stored in the storage medium.

According to embodiments, methods according to various embodiments of the present disclosure may be included and provided in a computer program product. The computer program product may be used as a product for conducting transactions between sellers and buyers. The computer program product may be distributed in the form of a machine-readable storage medium, such as a compact disk read only memory (CD-ROM), or may be distributed via an application Store (e.g., a Play Store ^TM ) The computer program product may be published (e.g., downloaded or uploaded) online, or may be distributed (e.g., downloaded or uploaded) directly between two user devices (e.g., smartphones). At least some of the computer program product may be temporarily generated if published online, or at least some of the computer program product may be stored at least temporarily in a machine readable storage medium, such as the memory of a manufacturer's server, an application store's server, or a forwarding server.

According to various embodiments, each of the above-described components (e.g., a module or a program) may include a single entity or multiple entities, and some of the multiple entities may be separately provided in different components. According to various embodiments, one or more of the above components may be omitted, or one or more other components may be added. Alternatively or additionally, multiple components (e.g., modules or programs) may be integrated into a single component. In this case, according to various embodiments, the integrated component may still perform the one or more functions of each of the plurality of components in the same or similar manner as the corresponding one of the plurality of components performed the one or more functions prior to integration. According to various embodiments, operations performed by a module, a program, or another component may be performed sequentially, in parallel, repeatedly, or in a heuristic manner, or one or more of the operations may be performed in a different order or omitted, or one or more other operations may be added.

Claims

1. An electronic device comprising at least one processor,

wherein the at least one processor is configured to:

identifying an event associated with an emergency service when registered in a first communication system;

based on the identification of the event, sending a service request corresponding to the event to a network;

starting a timer having an expiration time shorter than that of the timer T3517 based on the transmission of the service request;

searching and selecting a cell corresponding to a PLMN of a second communication system different from the first communication system based on failing to receive a response corresponding to the service request until the timer expires;

performing at least one operation for registering in the second communication system based on the selected cell; and

based on registration in the second communication system, emergency services corresponding to the event are performed based on the second communication system.

2. The electronic device of claim 1, wherein the at least one processor is configured to send a service request to a network for a service type including an emergency service fallback as at least a portion of sending the service request corresponding to the event to the network.

3. The electronic device of claim 1, wherein the at least one processor is configured to perform at least a portion of at least one operation for registering in the second communication system based on the selected cell:

performing a RACH procedure with the selected cell; and

a procedure for registering in the second communication system is performed based on the RRC connection established based on the RACH procedure.

4. The electronic device of claim 3, wherein the at least one processor is configured to select the cell based on information included in SIB 1 from the cell and based on the cell supporting the second communication system as at least a portion of selecting the cell.

5. The electronic device of claim 1, wherein the at least one processor is configured to perform at least one procedure for establishing an IMS emergency session as part of performing at least a portion of an emergency service corresponding to the event.

6. The electronic device of claim 1, wherein the at least one processor is further configured to:

receiving an RRC release message requesting redirection from the network before the timer expires; and

Based on the reception of the RRC release message, a procedure for redirecting to the second communication system specified in the RRC release message is performed.

7. The electronic device of claim 1, wherein the at least one processor is further configured to:

receiving a handover command from the network before the timer expires; and

based on the handover command, a procedure for handover to a target cell that supports the second communication system and is specified in the handover command is performed.

8. The electronic device of claim 1, wherein the at least one processor is further configured to:

identifying frequency information supporting an SA mode of the first communication system and identified by SIB 24 received from a serving cell;

identifying another cell supporting an SA mode of the first communication system based on the identified frequency information after performing the emergency service; and

and reselecting the other cell based on the other cell meeting the cell reselection condition.

9. The electronic device of claim 1, wherein the at least one processor is further configured to:

identifying frequency information supporting an SA mode of the first communication system and stored in the electronic device;

Identifying another cell supporting an SA mode of the first communication system based on the identified frequency information based on a specified time elapsed after the emergency service is performed; and

10. The electronic device of claim 1, wherein the at least one processor is further configured to:

receiving an RRC release message requesting redirection to the first communication system after performing the emergency service; and

a procedure for redirecting to the first communication system specified in the received RRC release message is performed.

11. The electronic device of claim 1, wherein the at least one processor is further configured to:

after performing the emergency service, receiving an RRC reconfiguration message including a measurement object;

performing measurement reporting based on a measurement result based on the measurement object satisfying a reporting condition; and

a procedure for handover to a target cell specified in the handover command is performed based on receiving a handover command in response to the measurement report.

12. A method of operation of an electronic device, comprising:

13. The method of operation of claim 12, wherein sending a service request corresponding to the event to a network comprises:

a service request including a service type of an emergency service fallback is sent to the network.

14. The method of operation of claim 12, wherein performing at least one operation for registering in the second communication system based on the selected cell comprises:

Performing a RACH procedure with the selected cell; and

15. The method of operation of claim 14, wherein selecting a cell comprises:

based on information included in SIB 1 from the cell, the cell is selected based on the cell supporting the second communication system.