KR20240157504A - Network device for supporting satellite communication and operating method thereof - Google Patents

Abstract

An embodiment of the present invention relates to a device and a method for supporting satellite communication of an electronic device in a network device. According to one embodiment, the network device includes a communication circuit and at least one processor, wherein the at least one processor receives a message related to a registration request from the electronic device, and, when it is determined that the electronic device can be provided with limited functionality, the processor transmits a registration allowance message related to the limited functionality to the electronic device through the communication circuit. Furthermore, when a request message related to an IMS connection is received from the electronic device, based on the provision of the limited functionality, the processor transmits a rejection message related to the IMS connection to the electronic device through the communication circuit, and can support a message function based on the NAS of the electronic device. Other embodiments may also be possible.

Description

{NETWORK DEVICE FOR SUPPORTING SATELLITE COMMUNICATION AND OPERATING METHOD THEREOF}

An embodiment of the present invention relates to a network device supporting satellite communication and an operating method thereof.

A wireless communication system can provide wireless connections to electronic devices so that wireless communication between various electronic devices can be enabled. The wireless communication system can provide wireless communication between electronic devices by allocating radio frequency resources to the electronic devices through the control of a base station installed on the ground. Due to the physical limitation that the location where the base station is installed is on the ground, the wireless communication system may have difficulty providing wireless connections to electronic devices located at sea and/or above a certain altitude.

Wireless communication systems are being developed to include satellite networks and terrestrial networks in order to overcome the physical limitations of base stations located on the ground and to expand the range of wireless connection of electronic devices to the entire globe. By including terrestrial networks and satellite networks, wireless communication systems can provide wireless communication with electronic devices even in areas where it is difficult to construct terrestrial networks or in disaster situations.

The electronic device may perform an attach procedure to a satellite network and an IMS (IP multimedia subsystem) connection procedure to support wireless communication via the satellite network. For example, the IMS attachment procedure may include an IMS PDN (packet data network) connection procedure and an IMS registration procedure.

Since a network device supporting satellite communication must perform a registration procedure with the satellite network and an IMS connection procedure for each electronic device to access the satellite network, resource consumption of the satellite network may increase as the number of electronic devices attempting to access the satellite network increases. For example, a network device supporting satellite communication may include components of a satellite network and a terrestrial network wirelessly connected to the satellite network.

An electronic device can perform call setup by connecting to a satellite network to perform a voice call with another electronic device. A network device supporting satellite communication can transmit a rejection message corresponding to the call setup request of the electronic device to the electronic device if the satellite network does not support voice calls of the electronic device.

If an electronic device connected to a satellite network cannot distinguish between the satellite network and the terrestrial network, it may repeatedly request call setup to a satellite network that does not support voice calls, which may unnecessarily consume satellite network resources.

An embodiment of the present invention discloses a device and method for supporting satellite communication of an electronic device in a network device.

The technical problems to be achieved in this document are not limited to the technical problems mentioned above, and other technical problems not mentioned will be clearly understood by those skilled in the art to which the present invention belongs from the description below.

According to one embodiment, the network device may include a communication circuit supporting satellite communication, and at least one processor operatively connected to the communication circuit. According to one embodiment, the processor may receive a message related to a registration request from the electronic device. According to one embodiment, if the processor determines that the electronic device can provide a limited function (e.g., a messaging function), the processor may transmit a registration acceptance message related to the limited function to the electronic device through the communication circuit. According to one embodiment, if the processor receives a request message related to an IMS connection from the electronic device, the processor may transmit a rejection message related to the IMS connection to the electronic device through the communication circuit based on the provision of the limited function. According to one embodiment, the processor may support a messaging function based on a non-access stratum (NAS) of the electronic device as one of the limited functions that the electronic device can provide.

According to one embodiment, an operating method of a network device supporting satellite communication may include an operation of receiving a message related to a registration request from an electronic device. According to one embodiment, the operating method of the network device may include an operation of transmitting a registration acceptance message related to the limited function to the electronic device when it is determined that the electronic device can provide a limited function (e.g., a message function). According to one embodiment, the operating method of the network device may include an operation of transmitting a rejection message related to the IMS connection to the electronic device based on provision of the limited function to the electronic device when a request message related to an IMS connection is received from the electronic device. According to one embodiment, the operating method of the network device may include an operation of supporting a message function based on a non-access stratum (NAS) of the electronic device as one of the limited functions that can be provided by the electronic device.

According to one embodiment, a non-transitory computer-readable storage medium (or a computer program product) storing one or more programs may be described. According to one embodiment, the one or more programs may include instructions that, when executed by a processor of a network device, perform the following operations: receiving a message related to a registration request from an electronic device; if it is determined that the electronic device can provide a limited function, transmitting a registration acceptance message related to the limited function to the electronic device; if a request message related to an IMS connection is received from the electronic device, transmitting a rejection message related to an IMS connection to the electronic device based on the provision of the limited function; and supporting a message function based on a non-access stratum (NAS) of the electronic device. For example, if the limited function that the network device can provide to the electronic device is an SMS function, the registration acceptance message may be transmitted to the electronic device. The electronic device may perform the operation of supporting an SMS function based on the NAS based on the registration acceptance message.

According to an embodiment of the present invention, when a network device supporting satellite communication supports limited functions (e.g., a messaging function), by rejecting or limiting a request from an electronic device related to a function not supported by the satellite network (e.g., a voice call function), consumption of resources of the satellite network can be reduced.

According to one embodiment, a network device supporting satellite communication performs a NAS (non-access stratum)-based message function, and controls an electronic device not to perform a request for a voice call, which is a function not supported by the satellite network, thereby reducing consumption of satellite network resources for the message function.

In one embodiment, when the electronic device receives a rejection message related to an IMS connection from the network (or satellite network), it determines that the network (or satellite network) does not support voice calls and thus does not repeatedly request call setup, thereby reducing unnecessary consumption of network resources.

The effects that can be obtained from various embodiments of the present invention are not limited to the effects mentioned above, and other effects that are not mentioned can be clearly understood by those skilled in the art in which various embodiments of the present invention belong from the description below.

FIG. 1 is a block diagram of an electronic device within a network environment according to one embodiment.
FIG. 2 is a diagram illustrating an electronic device and a remote communication network environment according to one embodiment.
FIG. 3 is a block diagram of a network device supporting satellite communication according to one embodiment.
FIG. 4 is a flowchart for supporting satellite communication of an electronic device in a network device according to one embodiment.
FIG. 5 is a flowchart for transmitting a connection permission message from a network device to an electronic device according to one embodiment.
FIG. 6 is a flowchart for providing satellite communication in an electronic device according to one embodiment.
FIG. 7 is a flowchart for providing satellite communication in an electronic device according to one embodiment.
FIG. 8 is a flowchart for providing satellite communication in an electronic device satisfying specified conditions according to one embodiment.
FIG. 9 is an example for rejecting an IMS PDN connection of an electronic device in a network device according to one embodiment.
FIG. 10 is an example for rejecting IMS registration of an electronic device in a network device according to one embodiment.
FIG. 11 is an example for limiting IMS connectivity of an electronic device in a network device according to one embodiment.
FIG. 12 is an example of supporting satellite communication of an electronic device in a network device according to one embodiment.
FIG. 13 is an example of supporting satellite communication of an electronic device satisfying specified conditions in a network device according to one embodiment.
FIG. 14 is an example of supporting satellite communication of an electronic device satisfying specified conditions in a network device according to one embodiment.

The following various embodiments are described in detail with reference to the attached drawings.

FIG. 1 is a block diagram of an electronic device (101) in a network environment (100) according to one embodiment. Referring to FIG. 1, in the network environment (100), the electronic device (101) may communicate with the electronic device (102) via a first network (198) (e.g., a short-range wireless communication network) or may communicate 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 one embodiment, the electronic device (101) may communicate with the electronic device (104) via the server (108). According to one embodiment, the electronic device (101) may include a processor (120), a memory (130), an input module (150), an audio output module (155), a display module (160), an audio module (170), a sensor module (176), an interface (177), a connection terminal (178), a haptic module (179), a camera module (180), a power management module (188), a battery (189), a communication module (190), a subscriber identification module (196), or an antenna module (197). In some embodiments, the electronic device (101) may omit at least one of these components (e.g., the connection terminal (178)), or may have one or more other components added. In some embodiments, some of these components (e.g., the sensor module (176), the camera module (180), or the antenna module (197)) may be integrated into one component (e.g., the display module (160)).

The processor (120) may control at least one other component (e.g., a hardware or software component) of the electronic device (101) connected to the processor (120) by executing, for example, software (e.g., a program (140)), and may perform various data processing or calculations. According to one embodiment, as at least a part of the data processing or calculations, the processor (120) may store a command or data received from another component (e.g., a sensor module (176) or a communication module (190)) in the volatile memory (132), process the command or data stored in the volatile memory (132), and store result data in the nonvolatile memory (134). According to one embodiment, the processor (120) may include a main processor (121) (e.g., a central processing unit or an application processor) or an auxiliary processor (123) (e.g., a graphic processing unit, a neural processing unit (NPU), an image signal processor, a sensor hub processor, or a communication processor) that can operate independently or together therewith. For example, if the electronic device (101) includes a main processor (121) and a secondary processor (123), the secondary processor (123) may be configured to use lower power than the main processor (121) or to be specialized for a given function. The secondary processor (123) may be implemented separately from the main processor (121) or as a part thereof.

The auxiliary processor (123) may control at least a portion of functions or states associated with 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)), for example, on behalf of the main processor (121) while the main processor (121) is in an inactive (e.g., sleep) state, or together with the main processor (121) while the main processor (121) is in an active (e.g., application execution) state. In one embodiment, the auxiliary processor (123) (e.g., an image signal processor or a communication processor) may be implemented as a part of another functionally related component (e.g., a camera module (180) or a communication module (190)). In one embodiment, the auxiliary processor (123) (e.g., a neural network processing device) may include a hardware structure specialized for processing artificial intelligence models. The artificial intelligence models may be generated through machine learning. Such learning may be performed, for example, in the electronic device (101) itself on which the artificial intelligence model is executed, or may be performed through a separate server (e.g., server (108)). The learning algorithm may include, for example, supervised learning, unsupervised learning, semi-supervised learning, or reinforcement learning, but is not limited to the examples described above. The artificial intelligence model may include a plurality of artificial neural network layers. The artificial neural network may be one of a deep neural network (DNN), a convolutional neural network (CNN), a recurrent neural network (RNN), a restricted Boltzmann machine (RBM), a deep belief network (DBN), a bidirectional recurrent deep neural network (BRDNN), deep Q-networks, or a combination of two or more, but is not limited to the examples described above. In addition to the hardware structure, the artificial intelligence model may additionally or alternatively include a software structure.

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

The program (140) may be stored as software in memory (130) and may include, for example, an operating system (142), middleware (144), or an application (146).

The input module (150) can receive commands or data to be used in a component of the electronic device (101) (e.g., a processor (120)) from an external source (e.g., a user) of the electronic device (101). The input module (150) can include, for example, a microphone, a mouse, a keyboard, a key (e.g., a button), or a digital pen (e.g., a stylus pen).

The audio output module (155) can output an audio signal to the outside of the electronic device (101). The audio output module (155) can include, for example, a speaker or a receiver. The speaker can be used for general purposes such as multimedia playback or recording playback. The receiver can be used to receive an incoming call. According to one embodiment, the receiver can be implemented separately from the speaker or as a part thereof.

The display module (160) can visually provide information to an external party (e.g., a user) of the electronic device (101). The display module (160) can include, for example, a display, a holographic device, or a projector and a control circuit for controlling the device. According to one embodiment, the display module (160) can include a touch sensor configured to detect a touch, or a pressure sensor configured to measure the intensity of a force generated by a touch.

The audio module (170) can convert sound into an electrical signal, or vice versa, convert an electrical signal into sound. According to one embodiment, the audio module (170) can obtain sound through an input module (150), or output sound through an audio output module (155), or an external electronic device (e.g., an electronic device (102)) (e.g., a speaker or a headphone) directly or wirelessly connected to the electronic device (101).

The sensor module (176) can detect an operating state (e.g., power or temperature) of the electronic device (101) or an external environmental state (e.g., user state) and generate an electric signal or data value corresponding to the detected state. According to one embodiment, the sensor module (176) can include, for example, a gesture sensor, a gyro sensor, a barometric pressure sensor, a magnetic sensor, an acceleration sensor, a grip sensor, a proximity sensor, a color sensor, an IR (infrared) sensor, a biometric sensor, a temperature sensor, a humidity sensor, or an illuminance sensor.

The interface (177) may support one or more designated protocols that may be used to directly or wirelessly connect the electronic device (101) with an external electronic device (e.g., the electronic device (102)). According to one embodiment, the interface (177) may include, for example, a high definition multimedia interface (HDMI), a universal serial bus (USB) interface, an SD card interface, or an audio interface.

The connection terminal (178) may include a connector through which the electronic device (101) may be physically connected to an external electronic device (e.g., the electronic device (102)). According to one embodiment, the connection terminal (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) can convert an electrical signal into a mechanical stimulus (e.g., vibration or movement) or an electrical stimulus that a user can perceive through a tactile or kinesthetic sense. According to one embodiment, the haptic module (179) can include, for example, a motor, a piezoelectric element, or an electrical stimulation device.

The camera module (180) can capture still images and moving images. According to one embodiment, the camera module (180) can include one or more lenses, image sensors, image signal processors, or flashes.

The power management module (188) can manage power supplied to the electronic device (101). According to one embodiment, the power management module (188) can be implemented as, for example, at least a part of a power management integrated circuit (PMIC).

The battery (189) can power at least one component of the electronic device (101). In one embodiment, the battery (189) can include, for example, a non-rechargeable primary battery, a rechargeable secondary battery, or a fuel cell.

The communication module (190) may support establishment of 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 performance of communication through the established communication channel. The communication module (190) may operate independently from the processor (120) (e.g., the application processor) and may include one or more communication processors that support direct (e.g., wired) communication or wireless communication. According to one 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 GNSS (global navigation satellite system) communication module) or a wired communication module (194) (e.g., a local area network (LAN) communication module or a power line communication module). Among these communication modules, a corresponding communication module may communicate with an external electronic device (104) via a first network (198) (e.g., a short-range communication network such as Bluetooth, Wi-Fi (wireless fidelity) direct, or IrDA (infrared data association)) or a second network (199) (e.g., a long-range communication network such as a legacy cellular network, a 5G network, a next-generation communication network, the Internet, or a computer network (e.g., a LAN or WAN)). These various types of communication modules may be integrated into a single component (e.g., a single chip) or implemented as a plurality of separate components (e.g., multiple chips). The wireless communication module (192) may use subscriber information (e.g., an international mobile subscriber identity (IMSI)) stored in the subscriber identification module (196) to identify or authenticate the electronic device (101) within a communication network such as the first network (198) or the second network (199).

The wireless communication module (192) can support a 5G network and next-generation communication technology after a 4G network, for example, NR access technology (new radio access technology). The NR access technology can support high-speed transmission of high-capacity data (eMBB (enhanced mobile broadband)), minimization of terminal power and connection of multiple terminals (mMTC (massive machine type communications)), or high reliability and low latency (URLLC (ultra-reliable and low-latency communications)). The wireless communication module (192) can support, for example, a high-frequency band (e.g., mmWave band) to achieve a high data throughput. The wireless communication module (192) may support various technologies for securing performance in a high-frequency band, such as beamforming, massive multiple-input and multiple-output (MIMO), full dimensional MIMO (FD-MIMO), array antenna, analog beam-forming, or large scale antenna. The wireless communication module (192) may support various requirements specified in an electronic device (101), an external electronic device (e.g., an electronic device (104)), or a network system (e.g., a second network (199)). According to one embodiment, the wireless communication module (192) can support a peak data rate (e.g., 20 Gbps or more) for eMBB realization, a loss coverage (e.g., 164 dB or less) for mMTC realization, or a U-plane latency (e.g., 0.5 ms or less for downlink (DL) and uplink (UL) each, or 1 ms or less for round trip) for URLLC realization. According to one embodiment, the subscriber identification module (196) can include a plurality of subscriber identification modules. For example, the plurality of subscriber identification modules can store different subscriber information.

The antenna module (197) can transmit or receive signals or power to or from the outside (e.g., an external electronic device). According to one embodiment, the antenna module (197) can include an antenna including a radiator formed of a conductor or a conductive pattern formed on a substrate (e.g., a PCB). According to one embodiment, the antenna module (197) can include a plurality of antennas (e.g., an array antenna). In this case, at least one antenna suitable for a communication method used in a communication network, such as the first network (198) or the second network (199), can be selected from the plurality of antennas by, for example, the communication module (190). A signal or power can be transmitted or received between the communication module (190) and the external electronic device through the selected at least one antenna. According to some embodiments, in addition to the radiator, another component (e.g., a radio frequency integrated circuit (RFIC)) can be additionally formed as a part of the antenna module (197).

In one embodiment, the antenna module (197) can form a high-frequency (e.g., mmWave) antenna module. In one embodiment, the high-frequency (e.g., mmWave) antenna module can include a printed circuit board, an RFIC positioned on or adjacent a first side (e.g., a bottom side) of the printed circuit board and capable of supporting a designated high-frequency band (e.g., a mmWave band), and a plurality of antennas (e.g., array antennas) positioned on or adjacent a second side (e.g., a top side or a side) of the printed circuit board and capable of transmitting or receiving signals in the designated high-frequency band. For example, the plurality of antennas can include patch array antennas and/or dipole array antennas.

At least some of the components can be interconnected and exchange signals (e.g., commands or data) with each other via a communication method between peripheral devices (e.g., a bus, GPIO (general purpose input and output), SPI (serial peripheral interface), or MIPI (mobile industry processor interface)).

In one embodiment, commands or data may be transmitted or received between the electronic device (101) and an external electronic device (104) via a server (108) connected to a second network (199). Each of the external electronic devices (102, or 104) may be the same or a different type of device as the electronic device (101). In one embodiment, all or part of the operations executed in the electronic device (101) may be executed in one or more of the external electronic devices (102, 104, or 108). For example, when the electronic device (101) is to perform a certain function or service automatically or in response to a request from a user or another device, the electronic device (101) may, instead of or in addition to executing the function or service itself, request one or more external electronic devices to perform at least a part of the function or service. One or more external electronic devices that have received the request may execute at least a part of the requested function or service, or an additional function or service related to the request, and transmit the result of the execution to the electronic device (101). The electronic device (101) may process the result as is or additionally and provide it as at least a part of a response to the request. For this purpose, for example, cloud computing, distributed computing, mobile edge computing (MEC), or client-server computing technology may be used. The electronic device (101) may provide an ultra-low latency service by using, for example, distributed computing or mobile edge computing. In another embodiment, the external electronic device (104) may include an IoT (Internet of Things) device. The server (108) may be an intelligent server using machine learning and/or a neural network. According to one embodiment, the external electronic device (104) or the server (108) may be included in the second network (199). The electronic device (101) can be applied to intelligent services (e.g., smart home, smart city, smart car, or healthcare) based on 5G communication technology and IoT-related technology.

An electronic device according to an embodiment disclosed in this document may be a device of various forms. The electronic device may include, for example, a portable communication device (e.g., a smartphone), a computer device, a portable multimedia device, a portable medical device, a camera, a wearable device, or a home appliance device. The electronic device according to an embodiment of this document is not limited to the above-described devices.

It should be understood that the embodiments of this document and the terminology used herein are not intended to limit the technical features described in this document to a particular embodiment, but rather to encompass various modifications, equivalents, or substitutes of the embodiment. In connection with the description of the drawings, similar reference numerals may be used for similar or related components. The singular form of a noun corresponding to an item may include one or more of the items, unless the context clearly dictates otherwise. In this document, each of the phrases "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" can include any one of the items listed together in the corresponding phrase, or all possible combinations thereof. Terms such as "first", "second", or "first" or "second" may be used merely to distinguish one component from another, and do not limit the components in any other respect (e.g., importance or order). When a component (e.g., a first) is referred to as "coupled" or "connected" to another (e.g., a second) component, with or without the terms "functionally" or "communicatively," it means that the component can be connected to the other component directly (e.g., wired), wirelessly, or through a third component.

The term "module" used in one embodiment of this document may include a unit implemented in hardware, software or firmware, and may be used interchangeably with terms such as logic, logic block, component, or circuit, for example. A module may be an integrally configured component or a minimum unit of the component or a portion thereof that performs one or more functions. For example, according to one embodiment, a module may be implemented in the form of an application-specific integrated circuit (ASIC).

An embodiment of the present document may be implemented as software (e.g., a program (140)) including one or more instructions stored in a storage medium (e.g., an internal memory (136) or an external memory (138)) readable by a machine (e.g., an electronic device (101)). For example, a processor (e.g., a processor (120)) of the machine (e.g., the electronic device (101)) may call at least one instruction among the one or more instructions stored from the storage medium and execute it. This enables the machine to operate to perform at least one function according to the at least one called instruction. The one or more instructions may include code generated by a compiler or code executable by an interpreter. The machine-readable storage medium may be provided in the form of a non-transitory storage medium. Here, 'non-transitory' simply means that the storage medium is a tangible device and does not contain signals (e.g. electromagnetic waves), and the term does not distinguish between cases where data is stored semi-permanently or temporarily on the storage medium.

According to one embodiment, the method according to one embodiment disclosed in the present document may be provided as included in a computer program product. The computer program product may be traded between a seller and a buyer as a commodity. The computer program product may be distributed in the form of a machine-readable storage medium (e.g., a compact disc read only memory (CD-ROM)), or may be distributed online (e.g., downloaded or uploaded) via an application store (e.g., Play Store ^TM ) or directly between two user devices (e.g., smart phones). In the case of online distribution, at least a part of the computer program product may be at least temporarily stored or temporarily generated in a machine-readable storage medium, such as a memory of a manufacturer's server, a server of an application store, or an intermediary server.

According to one embodiment, each component (e.g., a module or a program) of the above-described components may include a single or multiple entities, and some of the multiple entities may be separated and arranged in other components. According to one embodiment, one or more of the components or operations of the above-described components may be omitted, or one or more other components or operations may be added. Alternatively or additionally, the multiple components (e.g., a module or a program) may be integrated into one component. In such a case, the integrated component may perform one or more functions of each of the multiple components identically or similarly to those performed by the corresponding component of the multiple components before the integration. According to one embodiment, the operations performed by the module, program, or other component may be executed sequentially, in parallel, repeatedly, or heuristically, or one or more of the operations may be executed in a different order, omitted, or one or more other operations may be added.

FIG. 2 is a diagram illustrating an electronic device and a remote communication network environment according to one embodiment.

According to one embodiment referring to FIG. 2, an electronic device (e.g., electronic device (101) of FIG. 1) may transmit and/or receive data via a terrestrial network and/or a non-terrestrial network.

The terrestrial network may refer to a network capable of providing data communication via a terrestrial wireless communication device (210). For example, the terrestrial wireless communication device (210) may include a base station located on the ground (e.g., fixed to the ground). The terrestrial wireless communication device (210) may support at least one communication method among various communication methods (e.g., 3G, 4G, 5G, etc.) that the electronic device (101) can support. For example, the terrestrial wireless communication device (210) may include an eNB (eNodeB) or a gNB (gNodeB), but there is no limitation on the type thereof.

A non-terrestrial network may refer to a network capable of providing data communication via at least one non-terrestrial wireless communication device (200). For example, the non-terrestrial wireless communication device (200) may include at least one of various communication devices such as a base station and a repeater that are not located on the ground. For example, the non-terrestrial wireless communication device (200) may include a satellite and/or an unmanned aerial vehicle, but is not limited to the type thereof. For example, the satellite may include a low-earth orbit (LEO) satellite, a medium-earth orbit (MEO) satellite, a geostationary earth orbit (GEO) satellite, and/or a high elliptical orbit (HEO) satellite. For example, the satellite may include a mobile satellite and/or a geostationary satellite.

The non-terrestrial wireless communication device (200) can support at least one of various wireless communication methods. For example, the non-terrestrial wireless communication device (200) can support NR NTN (non-terrestrial network) defined by 3GPP (3rd generation partnership project). Alternatively, the non-terrestrial wireless communication device (200) can support at least one of communication methods based on various communication standards such as LTE, GSM (global system for mobile communications), and CDMA (code-division multiple access), but there is no limitation on the type.

The terrestrial network and the non-terrestrial network may be independent networks. Alternatively, the terrestrial network and the non-terrestrial network may be included in at least one network that is associated with each other (e.g., a network provided by the same operator).

The electronic device (101) may perform wireless communication through a non-terrestrial network when communication with the terrestrial network is impossible or not smooth. Alternatively, the electronic device (101) may perform wireless communication through a non-terrestrial network regardless of the status of communication with the terrestrial network.

According to one embodiment, the electronic device (101) may include a processor (120), a display module (160) (e.g., a display or a display device), a wireless communication module (192) (e.g., a communication circuit), and/or an antenna module (197). For example, the processor (120) may be operatively, functionally, and/or electrically connected to the display module (160), the wireless communication module (192), and/or the antenna module (197).

According to one embodiment, the processor (120) may control overall operations related to terrestrial network communications and/or non-terrestrial network communications. For example, the processor (120) may include a communication processor (e.g., auxiliary processor (123) of FIG. 1) related to terrestrial network communications and/or non-terrestrial network communications.

According to one embodiment, the display module (160) can visually provide information processed in the electronic device (101) (e.g., the processor (120) and/or the wireless communication module (192)). For example, the display module (160) can display a user interface (UI) (or graphical user interface (GUI)) related to a terrestrial network and/or a non-terrestrial network. For example, the user interface may include at least one of the following: a type of network (e.g., cellular communication (3G, 4G, 5G), short-range communication (e.g., BT, WIFI), satellite communication), a type of network service provider (e.g., satellite communication service provider), an emergency service provider (ESP: emergency service provider)), a strength of a network signal (e.g., signal strength bars, RSSI (received signal strength indicator), RSRP (reference signal received power)), an orientation of a communication device (e.g., satellite) included in the network (e.g., orientation, elevation angle, azimuth angle), presence information, and a network communication status (e.g., idle, transmit, receive).

For example, a user interface representing information related to a terrestrial network and/or a non-terrestrial network may include information related to at least one of service information related to a terrestrial network and/or a non-terrestrial network (e.g., an emergency message transmission service), government office information, emergency contact information, common phrases that minimize text input by a user, a questionnaire method for quickly conveying an emergency situation (e.g., guidance information such as the type of accident, the injured area, and medical information), a messaging service (e.g., a small message service (SMS), a multimedia message service (MMS), a rich communication service (RCS) message), a voice call, a video call, a data communication service (e.g., information on various applications providing data communication including an Internet browser app), a location sharing service (e.g., longitude/latitude coordinates, MAP information related to the location of a non-terrestrial communication device (200), navigation, and street view), and a user interface related to a dialer or an indicator. For example, an emergency message transmission service may include a series of actions that display SOS service status information related to whether the SOS service can be provided. For example, medical information may include at least one of age, gender, disease information, or medication information.

For example, a user interface displaying information related to a terrestrial network and/or a non-terrestrial network is not limited to the examples described above and may be provided via other output devices (e.g., the audio output module (155) of FIG. 1).

According to one embodiment, the wireless communication module (192) may support various types of wireless communication bands supported by the electronic device (101). For example, the wireless communication band may include a short-range wireless communication band (e.g., BT (Bluetooth), BLE (Bluetooth low energy, Wi-Fi), a terrestrial network (e.g., a cellular network) communication band, and/or a non-terrestrial network band (e.g., n255 band and/or n256 band). For example, the wireless communication bands supported by the electronic device (101) may not be limited to the examples described above.

For example, the wireless communication module (192) can perform non-terrestrial network wireless communication using at least a portion of a frequency band associated with terrestrial network wireless communication.

According to one embodiment, the antenna module (197) may perform wireless communication with a non-terrestrial network using at least one antenna among a plurality of antennas included in the antenna module (197). For example, at least one antenna supporting wireless communication with the non-terrestrial network may include a dedicated antenna and/or a dual-purpose antenna. For example, the dedicated antenna may include an antenna supporting a non-terrestrial network. For example, the dual-purpose antenna may include an antenna supporting different types of networks and the non-terrestrial network together. For example, the dual-purpose antenna may include an antenna supporting a short-range communication network (e.g., a Bluetooth network, a wireless LAN network) and/or a terrestrial network (e.g., a long term evolution (LTE) network, a new radio (NR) network).

For example, the electronic device (101) can communicate with at least one satellite (e.g., a GNSS satellite, a satellite for emergency message service) using at least one non-terrestrial network dedicated antenna. For example, the electronic device (101) can support wireless communication of the non-terrestrial network using a plurality of antennas among the antennas supporting the terrestrial network.

Hereinafter, in the present disclosure, a satellite is mainly mentioned as a non-terrestrial wireless communication device (200), and although the satellite is mentioned as providing wireless communication based on a specific radio access technology (RAT) (e.g., LTE and/or NR) or a specific function (e.g., base station), it will be readily understood by those skilled in the art that this is an example and the type is not limited.

FIG. 3 is a block diagram of a network device supporting satellite communication according to one embodiment. For example, the network device (300) of FIG. 3 may include a non-terrestrial wireless communication device (200) of FIG. 2 and/or a terrestrial wireless communication device (210) wirelessly connected to the non-terrestrial wireless communication device (200). For example, the network device (300) may support limited functions via the satellite network. As an example, the limited functions may include a state in which the satellite network does not support a voice call function, but supports a function for transmitting and/or receiving information (or data) using a control signal (e.g., a message function). As an example, the voice call function may include a voice call based on IMS (Internet Protocol (IP) multimedia subsystem) (e.g., VoLTE (voice of long term evolution) or VoNR (voice of new radio)) and/or a voice call based on CS (circuit switched). For example, the function of transmitting and/or receiving information (or data) using a control signal may include a message function of transmitting and/or receiving information (or data) using a control signal transmitted and/or received between the electronic device and the core network. For example, the message function may include a message function (or emergency message function) based on NAS (non-access stratum). For example, the NAS-based message function may include SMS (short message service) in which information (or data) related to a message is transmitted and/or received using NAS signals transmitted and/or received between the electronic device and the core network.

According to one embodiment referring to FIG. 3, the network device (300) may include a processor (310), a communication circuit (320), and/or a memory (330). For example, the processor (310) may include a communication processor supporting satellite communications. For example, the processor (310) may be operatively, functionally, and/or electrically connected with the communication circuit (320) and/or the memory (330).

According to one embodiment, when the processor (310) receives a registration request (or connection request) (e.g., attach request) message from the electronic device (101) through the communication circuit (320), the processor (310) may control the communication circuit (320) to transmit a registration acceptance (or connection acceptance) (e.g., attach accept) message related to a limited function to the electronic device (101). As an example, the registration request message may include registration type (e.g., attach type or EPS attach type) information related to “combined EPS/IMSI attach.”

For example, when the processor (310) receives a registration request (or connection request) (e.g., attach request) message from the electronic device (101) through the communication circuit (320), the processor (310) may determine whether the electronic device (101) provides a limited function. When the processor (310) determines that the electronic device (101) provides a limited function, the processor (310) may control the communication circuit (320) to transmit a registration permission message related to the limited function to the electronic device (101).

For example, a registration allow message related to a limited function may include registration result information corresponding to a communication method to allow the electronic device (101) to request registration (or request access) to a network (or a satellite network). For example, a registration allow message related to a limited function may include a first type of registration result (e.g., an attach result or an EPS attach result) information to allow registration (or access) to a satellite network. As an example, the first type of registration result may include information related to registration of the first communication method and the second communication method (e.g., “combined EPS/IMSI attach”). As an example, the first communication method may include a communication method that supports EPS, such as a 4G communication method (e.g., long term evolution (LTE)). As an example, the second communication method may include a communication method that does not support EPS (e.g., non-EPS), such as a 2G communication method and/or a 3G communication method.

For example, a registration permission message related to a limited function may include registration result information for allowing a registration request of an electronic device (101) that satisfies a specified condition to a network (or satellite network) among electronic devices (101). As an example, the registration result information may include a second type of registration result that is different from the first type of registration result. As an example, the second type of registration result may include information related to registration of the first communication method (e.g., “EPS only”). As an example, the electronic device (101) that satisfies the specified condition may include an electronic device (101) that can recognize registration (or connection) to a satellite network.

For example, a registration acceptance message related to a limited feature may include additional result (e.g., additional update result) information related to the limited feature. For example, the additional result may include information related to a message function that can be provided by the network device (300) (e.g., "SMS only"). For example, the message function that can be provided by the network device (300) may include a message function based on NAS.

For example, a registration acceptance message related to restricted functionality may include information related to restrictions on voice calls in a packet switched (PS) network (e.g., voice of PS (VoPS) = 0).

According to one embodiment, the processor (310) may limit an IMS (IP multimedia subsystem) connection of an electronic device (101) registered (or connected) to a satellite network. For example, when the processor (310) receives a request message related to an IMS PDN (packet data network) connection from the electronic device (101), the processor (310) may control the communication circuit (320) to transmit a rejection message related to the IMS PDN connection to the electronic device (101). As an example, the rejection message related to the IMS PDN connection may include a rejection reason (e.g., ESM (EPS session management) cause) for rejecting (or limiting) an additional request of the electronic device (101) related to the IMS PDN connection.

For example, the rejection reason may include an ESM cause code specified in the 3rd generation partnership project (3GPP). As an example, the rejection reason for rejecting (or limiting) an additional request of the electronic device (101) related to the IMS PDN connection may include a first code indicating that the PDN connection does not exist (e.g., #54 (PDN connection does not exist)), a second code indicating a barring state determined by the operator (e.g., #8 (operator determined barring)), a third code for rejecting an unspecified request (e.g., #31 (Request rejected, unspecified)), and/or a fourth code indicating an unsupported state of a service option (e.g., #32 (service option not supported)). For example, when the processor (310) receives a request message related to IMS registration from the electronic device (101), it may control the communication circuit (320) to transmit a rejection message related to the IMS registration to the electronic device (101). For example, a rejection message related to IMS registration may include a reason for rejecting (or limiting) further requests by the electronic device (101) for IMS registration.

According to one embodiment, the processor (310) may limit a function related to a voice call of the electronic device (101) if the satellite network supports limited functions. For example, if the processor (310) receives a request message related to a CSFB (circuit switch fallback) from the electronic device (101), the processor (310) may control the communication circuit (320) to transmit a rejection message related to the CSFB to the electronic device (101). For example, the rejection message related to the CSFB may include a reason for rejecting (or limiting) an additional request of the electronic device (101) related to the CSFB of the electronic device (101) (e.g., an EMM (EPS mobility management) cause) and/or setting information of a timer (e.g., T3442) related to the CSFB of the electronic device (101). For example, the reason for rejecting an additional request of the electronic device (101) related to the CSFB may include a fifth code (e.g., #39 (CS service temporarily not available)) indicating a state in which the service is temporarily unavailable. For example, the setting information of a timer related to CSFB may include a value (e.g., a maximum value) specified as information related to the operating time of a timer that is set so that the electronic device (101) does not attempt CSFB while the timer related to CSFB is kept running.

According to one embodiment, when the processor (310) receives a NAS-based message from an electronic device (101) registered (or connected) to a satellite network, the processor (310) may process the message of the electronic device (101). For example, the processor (310) may check information (e.g., a phone number or identification information) related to another electronic device for transmitting the message from the message received from the electronic device (101). The processor (310) may control the communication circuit (320) to transmit the message received from the electronic device (101) to the other electronic device.

According to one embodiment, the communication circuitry (320) may support the network device (300) to transmit and/or receive signals and/or data with the electronic device (101) via a satellite network.

According to one embodiment, the memory (330) may store various data used by at least one component of the network device (300) (e.g., the processor (310) and/or the communication circuit (320)). For example, the memory (330) may store various instructions that may be executed by the processor (310).

According to one embodiment, the network device (300) may set a value specified in the system information to limit an attempt by the electronic device (101) to register (or connect) to the network device (300). For example, the specified value may include a first value (e.g., "barred") set in a "cell barred IE" of the system information (e.g., a system information block (SIB) 1) and/or a second value (e.g., "not allowed") set in an "interFreqReselection IE."

According to one embodiment, if the electronic device (101) cannot recognize the satellite network of the communication service provider, it may determine that registration (or connection) to the network device (300) is restricted based on a designated value set in the system information acquired from the network device (300). The electronic device (101) may restrict the registration (or connection) procedure to the network device (300) based on the determination that registration (or connection) to the network device (300) is restricted. For example, the registration (or connection procedure) procedure may include a series of operations of transmitting a registration (or connection) request message to the network device (300). For example, if the electronic device (101) can recognize the satellite network of the communication service provider, it may perform the registration (or connection) procedure to the network device (300) regardless of the system information acquired from the network device (300).

According to one embodiment, a network device (e.g., a network device (300) of FIG. 3) may include a communication circuit (e.g., a communication circuit (320) of FIG. 3) supporting satellite communication, and at least one processor (e.g., a processor (310) of FIG. 3) operatively connected to the communication circuit. According to one embodiment, the processor may receive a message related to a registration request from an electronic device (e.g., an electronic device (101) of FIG. 1 or FIG. 2). According to one embodiment, if the processor determines that the network device can provide a limited function (e.g., a message function) to the electronic device, the processor may transmit a registration acceptance message related to the limited function to the electronic device through the communication circuit. According to one embodiment, if the processor receives a request message related to an IMS connection from the electronic device, the processor may transmit a rejection message related to the IMS connection to the electronic device through the communication circuit based on whether the network device provides the limited function to the electronic device. According to one embodiment, the processor may support a non-access stratum (NAS) based messaging function as one of the limited functions that may be provided by the electronic device of the electronic device.

In one embodiment, the processor may determine whether to allow registration of the electronic device supporting satellite communication when receiving a message related to a registration request from the electronic device. In one embodiment, if the processor determines to allow registration of the electronic device supporting satellite communication, the processor may transmit a registration acceptance message including a first type of registration result and/or an additional result related to a limited function to the electronic device.

According to one embodiment, the processor may transmit a registration acceptance message including a first type of registration result, and, if the processor receives a request message related to a circuit switched fall back (CSFB) from an electronic device that has received the registration acceptance message, transmit a rejection message related to a CSFB to the electronic device through the communication circuit.

According to one embodiment, when the processor determines that registration of an electronic device satisfying a specified condition among electronic devices supporting satellite communication (e.g., an electronic device capable of recognizing a satellite network) is permitted, the processor may transmit a registration acceptance message including a second type of registration result different from the first type and/or an additional result related to a limited function to the electronic device.

According to one embodiment, when a processor receives a request message related to an IMS (IP multimedia subsystem) PDN (packet data network) connection from an electronic device, if the processor does not support the IMS PDN connection based on the provision of limited functionality, the processor can transmit a rejection message related to the IMS PDN connection to the electronic device through the communication circuit.

According to one embodiment, when the processor receives a request message related to an IMS PDN connection from the electronic device, the processor may transmit an acceptance message related to the IMS PDN connection to the electronic device through the communication circuit. According to one embodiment, when the processor receives a request message related to an IMS registration from the electronic device, the processor may transmit a rejection message related to the IMS registration to the electronic device through the communication circuit if the processor does not support IMS based on the provision of limited functionality.

In one embodiment, the processor, if it is determined that the electronic device is capable of providing limited functionality, may transmit, via the communication circuitry, a registration acceptance message to the electronic device that includes information relating to limitations of voice calls over a packet switched (PS) network.

FIG. 4 is a flowchart (400) for supporting satellite communication of an electronic device in a network device according to one embodiment. In the following embodiments, each operation may be performed sequentially, but is not necessarily performed sequentially. For example, the order of each operation may be changed, and at least two operations may be performed in parallel. As an example, the network device of FIG. 4 may be the network device (300) of FIG. 3.

According to one embodiment referring to FIG. 4, a network device (e.g., processor (310) of FIG. 3) may receive a registration request (or connection request) message from an electronic device (101) at operation 401. As an example, the registration request message may include registration type (e.g., attach type or EPS attach type) information related to "combined EPS/IMSI attach".

According to one embodiment, the network device (e.g., the processor (310)) may transmit, at operation 403, a registration acceptance message related to a limited function supported by the satellite network to the electronic device. For example, the registration acceptance message related to the limited function may include a first type of registration result information for allowing registration (or connection) of the electronic device (101) supporting satellite communication to the satellite network. For example, the first type of registration result may include information related to “combined EPS/IMSI attach.” For example, “combined EPS/IMSI attach” may include information that the electronic device (101) can receive not only EPS service but also non-EPS service through the network device (300) (or satellite network). For example, the registration acceptance message related to the limited function may include a second type of registration result information for allowing registration (or connection) of at least some electronic devices (101) satisfying a specified condition among the electronic devices (101) supporting satellite communication to the satellite network. For example, the registration result of the second type may include information related to "EPS only". For example, "EPS only" may include information that the electronic device (101) can only receive EPS service through the network device (300) (or satellite network). For example, the electronic device (101) satisfying the specified condition may include an electronic device (101) that can recognize registration (or connection) to the satellite network. For example, the registration acceptance message related to the limited function may include additional result information related to the limited function. For example, the additional result may include information related to "SMS only". For example, "SMS only" may include information that the electronic device (101) can receive SMS function through the network device (300) (or satellite network). For example, the registration acceptance message related to the limited function may include information related to limitation of voice calls in a PS (packet switched) network.

According to one embodiment, a network device (e.g., processor (310)) may, at operation 405, determine whether a request message related to an IMS connection is received from an electronic device (101) registered (or connected) to a satellite network. For example, the request message related to an IMS connection may include a request message related to an IMS PDN connection or a request message related to an IMS registration.

According to one embodiment, if a request message related to an IMS connection is not received from an electronic device (101) registered (or connected) to a satellite network (e.g., 'No' in operation 405), in operation 409, the network device (e.g., the processor (310)) may provide a NAS-based message function for the electronic device (101) registered (or connected) to the satellite network. For example, if the electronic device (101) satisfying a specified condition recognizes registration (or connection) to a satellite network, the electronic device (101) may determine that the NAS-based message function can be provided via the satellite network without an IMS connection. For example, if the electronic device (101) satisfying a specified condition obtains a first type of registration result from the satellite network, or obtains a first type of registration result and an additional result related to a restricted function, or obtains a second type of registration result and an additional result related to a restricted function, the electronic device (101) may determine that the NAS-based message function can be provided via the satellite network without an IMS connection. For example, if the electronic device (101) obtains information related to a limitation of voice calls in the PS network (e.g., VoPS (voice of PS) = 0) in a registration acceptance message, the electronic device (101) may determine that it can provide a NAS-based message function through a satellite network without an IMS connection. For example, the processor (310) may control the communication circuit (320) to provide a NAS-based message function of the electronic device (101) that satisfies a specified condition or of the electronic device (101) that obtained information related to a limitation of voice calls in the PS network.

According to one embodiment, when a network device (e.g., processor (310)) receives a request message related to an IMS connection from an electronic device (101) registered (or connected) to a satellite network (e.g., 'Yes' in operation 405), in operation 407, the network device may transmit a rejection message related to the IMS connection to the electronic device (101). For example, when the processor (310) receives a request message related to an IMS PDN connection from the electronic device (101), the processor (310) may control the communication circuit (320) to transmit a rejection message related to the IMS PDN connection to the electronic device (101). As an example, the rejection message related to the IMS PDN connection may include a rejection reason (e.g., ESM cause) that rejects (or limits) an additional request of the electronic device (101) related to the IMS PDN connection. According to one embodiment, the rejection reason (e.g., ESM cause) may represent information that the network device (300) provides to the electronic device (101) so that the electronic device (101) can recognize the reason for rejecting the IMS PDN connection of the electronic device (101). As an example, the rejection reason for rejecting (or limiting) an additional request of the electronic device (101) related to the IMS PDN connection may include a first code indicating that the PDN connection does not exist (e.g., #54 (PDN connection does not exist)), a second code indicating a barring state determined by an operator (e.g., #8 (operator determined barring)), a third code rejecting an unspecified request (e.g., #31 (Request rejected, unspecified)), and/or a fourth code indicating an unsupported state of a service option (e.g., #32 (service option not supported)). For example, when the processor (310) receives a request message related to IMS registration from the electronic device (101), it may control the communication circuit (320) to transmit a rejection message related to IMS registration to the electronic device (101). As an example, the rejection message related to IMS registration may include a rejection reason for rejecting (or limiting) an additional request from the electronic device (101) for IMS registration.

According to one embodiment, a network device (e.g., processor (310)) may, at operation 409, provide NAS-based messaging functionality to an electronic device (101) registered with (or connected to) the satellite network.

FIG. 5 is a flowchart (500) for transmitting a connection acceptance message from a network device to an electronic device according to one embodiment. According to one embodiment, at least a part of FIG. 5 may include a detailed description of operation 403 of FIG. 4. In the following embodiments, each operation may be performed sequentially, but is not necessarily performed sequentially. For example, the order of each operation may be changed, and at least two operations may be performed in parallel. As an example, the network device of FIG. 4 may be the network device (300) of FIG. 3.

According to one embodiment referring to FIG. 5, when a network device (e.g., processor (310) of FIG. 3) receives a registration request (or connection request) message from an electronic device (101) (e.g., operation 401 of FIG. 4), in operation 501, it may determine whether to allow registration (or connection) of all electronic devices supporting satellite communication in the satellite network.

According to one embodiment, when the network device (e.g., the processor (310)) determines that registration (or access) of all electronic devices supporting satellite communication in the satellite network is permitted (e.g., 'Yes' in operation 501), in operation 503, the network device may transmit a registration acceptance message including a first type of registration result to the electronic device (101). For example, the first type of registration result may include information related to "combined EPS/IMSI attach." For example, "combined EPS/IMSI attach" may include information that the electronic device (101) can receive not only EPS service but also non-EPS service via the network device (300) (or the satellite network).

According to one embodiment, if the network device (e.g., the processor (310)) determines that the registration (or connection) of all electronic devices supporting satellite communication in the satellite network is not permitted (e.g., 'No' in operation 501), in operation 505, the network device may transmit a registration permission message including a second type of registration result to the electronic device (101). For example, if the processor (310) determines that the registration (or connection) of all electronic devices supporting satellite communication in the satellite network is not permitted, the processor (310) may determine that the satellite network permits registration (or connection) of an electronic device (101) satisfying a specified condition. As an example, the electronic device (101) satisfying the specified condition may include an electronic device (101) capable of recognizing registration (or connection) with the satellite network. As an example, the second type of registration result may include information related to "EPS only". For example, “EPS only” may include information that the electronic device (101) can only receive EPS services through the network device (300) (or satellite network).

According to one embodiment, the network device (300) may select a first type or a second type of registration result for each electronic device (101) requesting registration (or connection). For example, when the network device (300) allows registration (or connection) of at least some of the electronic devices requesting registration (or connection) in the satellite network, the network device (300) may determine the type of registration result to be transmitted to the electronic device (101) based on identification information of the electronic device (101) obtained in the registration (or connection) request message. For example, the network device (300) may check a service level to be provided to the electronic device (101) based on the identification information of the electronic device (101). The network device (300) may transmit a registration result of a type corresponding to the service level to be provided to the electronic device (101) to the electronic device (101). For example, a service level may include the amount of wireless resources (e.g., time and/or frequency) that can be allocated to the electronic device (101) and/or the data transmission rate that can be provided to the electronic device (101).

For example, the network device (300) can determine whether the electronic device (101) can identify a satellite network based on the identification information of the electronic device (101). The network device (300) can transmit a registration result of a type corresponding to whether the electronic device (101) can identify a satellite network to the electronic device (101). As an example, the identification information of the electronic device (101) can include at least one of an international mobile equipment identify (IMEI), an international mobile subscriber identify (IMSI), or a phone number.

FIG. 6 is a flowchart (600) for providing satellite communication in an electronic device according to one embodiment. In the following embodiments, each operation may be performed sequentially, but is not necessarily performed sequentially. For example, the order of each operation may be changed, and at least two operations may be performed in parallel. For example, the electronic device (101) of FIG. 6 may be the electronic device (101) of FIG. 1 or FIG. 2. For example, the electronic device (101) of FIG. 6 may include an electronic device that cannot recognize (or distinguish) a satellite network.

According to one embodiment referring to FIG. 6, the electronic device (e.g., the processor (120) of FIG. 1 or FIG. 2) may, in operation 601, if a network (e.g., a satellite network) to which the electronic device (101) can register (or connect) is detected, transmit a registration (or connection) request message to the network. For example, the processor (120) may control the wireless communication module (192) to transmit the registration request message to the network device (300). As an example, the registration request message may include information on a registration type of the electronic device (101) for the network. As an example, the registration request message may include registration type (e.g., attach type or EPS attach type) information related to "combined EPS/IMSI attach" when the electronic device (101) needs to register (or connect) to the network for EPS service and non-EPS service.

According to one embodiment, the electronic device (e.g., the processor (120)) may obtain information related to the first type of registration result at operation 603. For example, if the processor (120) receives a registration acceptance message corresponding to a registration request message through the wireless communication module (192), the processor (120) may determine that the electronic device is registered (or connected) to the network (or the network device (300)). The processor (120) may obtain information related to the first type of registration result from the registration acceptance message. As an example, the information related to the first type of registration result may include information related to “combined EPS/IMSI attach.”

According to one embodiment, the electronic device (e.g., processor (120)) may determine, at operation 605, whether the IMS connection has failed. For example, if the processor (120) determines that it is registered in the network, the processor (120) may control the wireless communication module (192) to transmit a request message related to an IMS packet data network (PDN) connection to the network device (300). If the processor (120) receives a rejection message related to the IMS PDN connection, the processor (120) may determine that the IMS connection has failed.

For example, if the processor (120) determines that the network is registered, it can control the wireless communication module (192) to transmit a request message related to an IMS PDN connection to the network device (300). If the processor (120) receives an acceptance message related to an IMS PDN connection, it can determine that the IMS PDN is connected. If the processor (120) determines that the IMS PDN is connected, it can control the wireless communication module (192) to transmit a request message related to an IMS registration to the network device (300). If the processor (120) receives a rejection message related to an IMS registration, it can determine that the IMS connection has failed.

In one embodiment, the electronic device (e.g., processor (120)) may terminate one embodiment for providing satellite communication if it determines that the IMS connection is successful (e.g., 'No' in operation 605). For example, if the IMS connection is successful, the processor (120) may control the wireless communication module (192) to provide an IMS service through a network (e.g., a satellite network). For example, the IMS service may include an IMS-based voice call function and/or a messaging function.

In one embodiment, if the electronic device (e.g., processor (120)) determines that the IMS connection has failed (e.g., 'Yes' in operation 605), in operation 607, the processor (120) may determine whether additional result information related to the restricted functionality is obtained. For example, the processor (120) may determine whether the registration acceptance message includes information related to an additional result related to the restricted functionality (e.g., an additional update result).

In one embodiment, when the electronic device (e.g., the processor (120)) obtains additional result information related to the limited functionality (e.g., 'Yes' in operation 607), in operation 609, the electronic device may perform a network search to determine whether a network accessible to the electronic device (101) for a voice call is detected. For example, the additional result may include information related to "SMS only." For example, when the IMS connection fails and the processor (120) obtains additional result information related to the first type of registration result and the limited functionality, the processor (120) may determine that the network (or the network device (300)) to which the electronic device (101) is registered does not support a voice call (e.g., VoLTE (voice of LTE)) based on a PS (packet switched) network and CSFB. The processor (120) may perform a network search related to a CS (circuit switched) network to determine whether a CS network capable of providing a voice call exists. For example, the CS network may include a 2G network and/or a 3G network. For example, a network search may include a series of operations to determine if there is a CS network to which the electronic device (101) can register (or connect).

According to one embodiment, the electronic device (e.g., the processor (120)) may terminate one embodiment for providing satellite communication if a network related to a voice call is found through the network search (e.g., 'No' in operation 609). For example, if a CS network related to a voice call is detected through the network search, the processor (120) may control the wireless communication module (192) to perform a registration (or connection) procedure with the CS network detected through the network search for the voice call. For example, the electronic device (101) may release registration with the network device (300) based on registration with the CS network detected through the network search. For example, if registration with the network device (300) is released, the electronic device (101) may provide a voice call function and/or a message function through the CS network.

According to one embodiment, the electronic device (e.g., processor (120)) may, if a network related to a voice call is not detected through a network search (e.g., 'Yes' in operation 609), in operation 611, limit the performance of a voice call based on a network (or a network device (300)) and provide a NAS-based message function. For example, if a CS network related to a voice call is not detected through the network search, the processor (120) may determine that the voice call function cannot be provided. If the occurrence of an event related to a voice call is detected, the processor (120) may output information related to the limitation of the voice call to the outside. For example, the event related to the voice call may be generated based on the execution of an application or function related to the voice call, the reception of an input or gesture related to the voice call, or the reception of control information related to the voice call. For example, the information related to the limitation of the voice call may be output based on at least one of a sound, a graphic, a text, or a light source. For example, if the processor (120) determines that the network (or network device (300)) to which the electronic device (101) is registered (or connected) does not support a PS network-based voice call (e.g., VoLTE) and CSFB (circuit switched fallback), the processor (120) may control the wireless communication module (192) to perform a network search related to a CS (circuit switched) network based on a specified period. According to one embodiment, CSFB (circuit switched fallback) is a technology that supports a voice call by using another RAN (radio access network) (e.g., CS network) in the service area (coverage) of a PS (packet switched)-based network (e.g., LTE network) to support a voice call through a CS (circuit switched) network. For example, CSFB may include a function of providing a voice call (or SMS) through a CS network, such as a 2G network or a 3G network, when the electronic device (101) cannot use the LTE network or cannot use VoLTE. For example, the processor (120) may determine that a NAS-based message method (e.g., SMS over NAS, SMS over SGs, or SMS over SGd) is supported if the IMS connection fails and additional result information related to the first type of registration result and limited functionality is obtained. The processor (120) may control the wireless communication module (192) to transmit and/or receive a message based on the NAS-based message method.

According to one embodiment, if the electronic device (e.g., processor (120)) fails to obtain additional result information related to the limited function (e.g., 'No' in operation 607), in operation 613, the electronic device may transmit a voice call request message related to CSFB. For example, if the IMS connection fails and the first type of registration result is obtained, the processor (120) may determine that the network (or network device (300)) to which the electronic device (101) is registered does not support a voice call based on a packet switched (PS) network (e.g., VoLTE (voice of LTE)) but supports CSFB. The electronic device (101) may determine that a voice call is possible with CSFB through the network (or network device (300)) to which the electronic device (101) is registered (or connected), and may maintain a camp on state with the network (or network device (300)). For example, a camp on state may include a state in which the electronic device (101) is synchronized in time and/or frequency with a network (or network device (300)) and can receive control information (e.g., a master information block (MIB) and/or a system information block (SIB)) of the network (or network device (300)).

For example, when an occurrence of an event related to a voice call is detected, the processor (120) may control the wireless communication module (192) to transmit a voice call request message related to CSFB. For example, the voice call request message related to CSFB may include an extended service request message. For example, the voice call request message related to CSFB may include service type information of "mobile originating CS fallback" or "1xCS fallback."

In one embodiment, the electronic device (e.g., processor (120)) may determine, at operation 615, whether a rejection message related to a voice call is received. For example, the processor (120) may determine whether a rejection message related to a voice call is received from the network (or network device (300)) during a specified reference time from the time of transmitting the voice call request message related to CSFB.

According to one embodiment, the electronic device (e.g., the processor (120)), if a rejection message related to a voice call is not received (e.g., 'No' in operation 615), in operation 609, may determine whether a network accessible to the electronic device (101) for a voice call is detected through a network search. For example, if a voice call rejection message is not received for a specified reference time elapsed from the time of transmitting the voice call request message related to the CSFB, the processor (120) may control the wireless communication module (192) to transmit (or retransmit) the voice call request message related to the CSFB. According to one embodiment, the processor (120) may determine whether the network (or the network device (300)) supports a PS network-based voice call (e.g., VoLTE) and CSFB based on the number of transmissions of the voice call request message related to the CSFB. For example, if the number of times the processor (120) transmits a voice call request message related to CSFB exceeds a specified first number of times, the processor (120) may determine that the network to which the electronic device (101) is registered (or the network device (300)) does not support PS network-based voice calls (e.g., VoLTE) and CSFB. For example, if the processor (120) determines that the network to which the electronic device (101) is registered (or the network device (300)) does not support PS network-based voice calls (e.g., VoLTE) and CSFB, the processor (120) may perform a network search related to a CS (circuit switched) network to determine whether a CS network capable of providing a voice call exists. As an example, the specified first number of times may include a specified reference number of times to determine whether the network (or the network device (300)) supports PS network-based voice calls (e.g., VoLTE) and CSFB.

According to one embodiment, when the electronic device (e.g., the processor (120)) receives a rejection message related to a voice call (e.g., 'Yes' of operation 615), in operation 611, the electronic device may restrict performance of a voice call based on a network (or a network device (300)) and perform a NAS-based message function. For example, when the processor (120) repeatedly receives a rejection message related to a voice call exceeding a specified second number of times, the electronic device may restrict performance of a voice call based on a network (or a network device (300)) and perform a NAS-based message function. As an example, the specified second number of times may include a value that is the same as or different from the specified first number of times as a specified reference number of times to determine whether performance of a voice call based on a network (or a network device (300)) is restricted.

For example, the processor (120) can obtain a rejection reason (e.g., EMM cause) and setting information of a timer (e.g., T3442) related to the CSFB of the electronic device (101) from a rejection message related to a voice call. If the processor (120) obtains a rejection reason that restricts an additional request related to the CSFB, the processor (120) can restrict transmission of a voice call request message related to the CSFB until the operating time of the timer related to the CSFB expires. For example, if the occurrence of an event related to a voice call is detected while transmission of a voice call request message related to the CSFB is restricted, the processor (120) can output information related to the restriction of the voice call to the outside.

For example, the processor (120) may determine that a NAS-based message method (e.g., SMS over NAS, SMS over SGs, or SMS over SGd) is supported when the IMS connection fails and the first type of registration result information is obtained. The processor (120) may control the wireless communication module (192) to transmit and/or receive a message based on the NAS-based message method.

According to one embodiment, the electronic device (101) may determine that the IMS connection via the network (or satellite network) is restricted if the registration acceptance message received from the network device (300) includes information related to the restriction of voice calls in a PS (packet switched) network (e.g., VoPS (voice of PS) = 0). For example, if the electronic device (101) obtains the registration result of the first type and the information related to the restriction of voice calls in the PS network through the registration acceptance message, the electronic device may omit a series of operations (e.g., operation 605 of FIG. 6) for attempting an IMS connection based on the determination that the IMS connection is restricted.

FIG. 7 is a flowchart (700) for providing satellite communication in an electronic device according to one embodiment. In the following embodiments, each operation may be performed sequentially, but is not necessarily performed sequentially. For example, the order of each operation may be changed, and at least two operations may be performed in parallel. For example, the electronic device (101) of FIG. 7 may be the electronic device (101) of FIG. 1 or FIG. 2. For example, the electronic device (101) of FIG. 7 may include an electronic device that cannot recognize (or distinguish) a satellite network.

According to one embodiment referring to FIG. 7, the electronic device (e.g., the processor (120) of FIG. 1 or FIG. 2) may, in operation 701, if a network (e.g., a satellite network) to which the electronic device (101) can register (or connect) is detected, transmit a registration (or connection) request message to the network. For example, the processor (120) may control the wireless communication module (192) to transmit the registration request message to the network device (300). As an example, the registration request message may include information on a registration type of the electronic device (101) for the network. As an example, the registration request message may include registration type (e.g., attach type or EPS attach type) information related to "combined EPS/IMSI attach" when the electronic device (101) needs to register (or connect) to the network for EPS service and non-EPS service.

According to one embodiment, the electronic device (e.g., the processor (120)) may obtain information related to the registration result of the second type at operation 703. For example, if the processor (120) receives a registration acceptance message corresponding to the registration request message through the wireless communication module (192), the processor (120) may determine that the electronic device is registered (or connected) to the network (or the network device (300)). The processor (120) may obtain information related to the registration result of the second type from the registration acceptance message. For example, the information related to the registration result of the second type may include information related to “EPS only.”

According to one embodiment, the electronic device (e.g., processor (120)) may determine, at operation 705, whether the IMS connection has failed. For example, if the processor (120) determines that it is registered in the network, the processor (120) may control the wireless communication module (192) to transmit a request message related to the IMS PDN connection to the network device (300). If the processor (120) receives a rejection message related to the IMS PDN connection, the processor (120) may determine that the IMS connection has failed.

For example, if the processor (120) determines that the network is registered, it can control the wireless communication module (192) to transmit a request message related to an IMS PDN connection to the network device (300). If the processor (120) receives an acceptance message related to an IMS PDN connection, it can determine that the IMS PDN is connected. If the processor (120) determines that the IMS PDN is connected, it can control the wireless communication module (192) to transmit a request message related to an IMS registration to the network device (300). If the processor (120) receives a rejection message related to an IMS registration, it can determine that the IMS connection has failed.

According to one embodiment, when the electronic device (e.g., processor (120)) determines that the IMS connection has failed (e.g., 'Yes' in operation 705), in operation 707, the electronic device (101) may determine that voice call and message functions are restricted through the network (or network device (300)) to which the electronic device (101) is registered (or connected). For example, the processor (120) may determine that only data services can be provided through the network (or network device (300)) (e.g., LTE network) based on information related to the second type of registration result (e.g., "EPS only") received from the network device (300). For example, the processor (120) may determine that the service can be provided only through the EPS network based on the registration result of "EPS only." For example, the processor (120) may determine that the voice call and message function based on IMS and the message function based on NAS are restricted through the network (or the network device (300)) to which the electronic device (101) is registered (or connected). When the occurrence of an event related to a voice call and/or a message is detected, the processor (120) may output information related to the restriction of the voice call and/or the message function to the outside. For example, the processor (120) may camp on the network (or the network device (300)) for a data service, or may maintain a camp on state with the network (or the network device (300)).

In one embodiment, the electronic device (e.g., processor (120)) may terminate one embodiment for providing satellite communication if it determines that the IMS connection is successful (e.g., 'NO' of operation 705). For example, if the IMS connection is successful, the processor (120) may control the wireless communication module (192) to provide an IMS service through a network (e.g., a satellite network). For example, the IMS service may include an IMS-based voice call function and/or a messaging function.

According to one embodiment, when the electronic device (101) determines that only data services can be provided through the network (or network device (300)) to which the electronic device (101) is registered (or connected), the electronic device (101) may perform a network search related to a CS (circuit switched) network to determine whether a CS network capable of providing voice calls exists. For example, when a CS network related to voice calls is not detected through the network search, the electronic device (101) may determine that the voice call function cannot be provided. When the electronic device (101) determines that the voice call function cannot be provided, the electronic device (101) may camp on the network (or network device (300)) for data services. As an example, a state in which a CS network related to voice calls is not detected may include a state in which a signal exceeding a specified signal quality is not received from the CS network. For example, the signal quality may include at least one of a received signal strength indicator (RSSI), a reference signal received quality (RSRQ), a reference signal received power (RSRP), a signal to interference and noise ratio (SINR), or a bit error rate (BER).

According to one embodiment, the electronic device (101) may determine that the IMS connection via the network (or satellite network) is restricted if the registration acceptance message received from the network device (300) includes information related to the restriction of voice calls in a PS (packet switched) network (e.g., VoPS (voice of PS) = 0). For example, if the electronic device (101) obtains the registration result of the second type and the information related to the restriction of voice calls in the PS network through the registration acceptance message, the electronic device may omit a series of operations (e.g., operation 705 of FIG. 7) for attempting an IMS connection based on the determination that the IMS connection is restricted.

FIG. 8 is a flowchart (800) for providing satellite communication in an electronic device satisfying a specified condition according to one embodiment. In the following embodiments, each operation may be performed sequentially, but is not necessarily performed sequentially. For example, the order of each operation may be changed, and at least two operations may be performed in parallel. For example, the electronic device (101) of FIG. 8 may be the electronic device (101) of FIG. 1 or FIG. 2. For example, the electronic device (101) of FIG. 8 may include an electronic device capable of recognizing (or distinguishing) a satellite network.

According to one embodiment referring to FIG. 8, the electronic device (e.g., the processor (120) of FIG. 1 or FIG. 2) may, in operation 801, if a network (e.g., a satellite network) to which the electronic device (101) can register (or connect) is detected, transmit a registration (or connection) request message to the network. For example, the processor (120) may control the wireless communication module (192) to transmit the registration request message to the network device (300). As an example, the registration request message may include information on a registration type of the electronic device (101) for the network. As an example, the registration request message may include registration type (e.g., attach type or EPS attach type) information related to "combined EPS/IMSI attach" when the electronic device (101) needs to register (or connect) to the network for EPS service and non-EPS service.

According to one embodiment, the electronic device (e.g., the processor (120)) may obtain information related to the registration result of the first type or the second type at operation 803. For example, if the processor (120) receives a registration acceptance message corresponding to the registration request message through the wireless communication module (192), the processor (120) may determine that the network (or the network device (300)) is registered (or connected). The processor (120) may obtain information related to the registration result of the first type or the second type from the registration acceptance message. For example, the registration result of the first type may include information related to "combined EPS/IMSI attach". For example, the registration result of the first type may include information that the electronic device (101) can receive not only an EPS service but also a non-EPS service through the network device (300) (or a satellite network). For example, the information related to the registration result of the second type may include information related to "EPS only". For example, the second type of registration result may include information that the electronic device (101) can only receive EPS services through the network device (300) (or satellite network).

According to one embodiment, the electronic device (e.g., processor (120)) may determine, at operation 805, whether the IMS connection has failed. For example, if the processor (120) determines that it is registered with the network (or satellite network), the processor (120) may control the wireless communication module (192) to transmit a request message related to the IMS PDN connection to the network device (300). If the processor (120) receives a rejection message related to the IMS PDN connection, the processor (120) may determine that the IMS connection has failed.

For example, if the processor (120) determines that the network is registered, it can control the wireless communication module (192) to transmit a request message related to an IMS PDN connection to the network device (300). If the processor (120) receives an acceptance message related to an IMS PDN connection, it can determine that the IMS PDN is connected. If the processor (120) determines that the IMS PDN is connected, it can control the wireless communication module (192) to transmit a request message related to an IMS registration to the network device (300). If the processor (120) receives a rejection message related to an IMS registration, it can determine that the IMS connection has failed.

According to one embodiment, if the electronic device (e.g., processor (120)) determines that the IMS connection has failed (e.g., 'Yes' in operation 805), in operation 807, the electronic device (101) may limit the performance of a voice call through the satellite network (or network device (300)) to which the electronic device is registered (or connected) and may perform a message function based on the NAS. For example, the processor (120) may determine that if the IMS connection through the satellite network to which the electronic device (101) is registered (or connected) has failed, the voice call function through the satellite network is limited and a message function can be provided based on the NAS. The processor (120) may control the wireless communication module (192) to transmit and/or receive a message based on the NAS-based message method.

According to one embodiment, if the electronic device (e.g., processor (120)) determines that the IMS connection is successful (e.g., 'No' in operation 805), in operation 809, the electronic device may provide an IMS service. For example, if the IMS connection is successful via a satellite network, the processor (120) may control the wireless communication module (192) to provide an IMS service via the satellite network (or the network device (300)). For example, the IMS service may include an IMS-based voice call function and/or a message function.

FIG. 9 is an example for rejecting an IMS PDN connection of an electronic device in a network device according to one embodiment. As an example, the network device (300) is a network component that supports wireless communication via a satellite network, and may include a non-terrestrial wireless communication device (200) of FIG. 2 and/or a terrestrial wireless communication device (210) wirelessly connected to the non-terrestrial wireless communication device (200).

According to one embodiment referring to FIG. 9, when a network (e.g., a satellite network) to which the electronic device (101) can register (or connect) is detected, the electronic device (101) may transmit a registration (or connection) request (e.g., attach request) message to the network (operation 911). As an example, the registration request message may include registration type (e.g., attach type or EPS attach type) information related to "combined EPS/IMSI attach".

According to one embodiment, the network device (300) may determine whether to allow registration (or connection) of the electronic device (101) based on a registration (or connection) request message received from the electronic device (101). For example, when the network device (300) allows registration (or connection) of the electronic device (101), the network device (300) may transmit a registration acceptance (e.g., attach accept) message related to a limited function supported by the satellite network to the electronic device (101) (operation 913). For example, the registration acceptance message may include information on a first type of registration result (e.g., EPS attach result) and information on an additional result (e.g., additional update result) related to the limited function. For example, the first type of registration result may include information related to "combined EPS/IMSI attach". For example, the additional result may include information related to "SMS only".

According to one embodiment, the electronic device (101) may determine that it is registered (or connected) to a network (or satellite network) related to the network device (300) based on a registration acceptance message obtained from the network device (300). The electronic device (101) may transmit a request (e.g., PDN connectivity request) message related to IMS PDN connectivity for IMS connection through the network (or satellite network) based on the registration result of the first type (operation 915). As an example, the request message related to IMS PDN connectivity may include information indicating that the type of APN (access point name) is IMS (e.g., APN=IMS).

According to one embodiment, when the network device (300) provides limited functionality in a satellite network, the network device (300) may transmit an IMS PDN connection-related rejection (e.g., PDN connectivity reject) message corresponding to the IMS PDN connection request message to the electronic device (101) (operation 917). For example, the IMS PDN connection-related rejection message may include a rejection reason (e.g., ESM cause) that rejects (or restricts) an additional request of the electronic device (101) related to the IMS PDN connection. For example, the rejection reason may include an ESM cause code specified in 3GPP (3rd generation partnership project). For example, a rejection reason for rejecting (or limiting) an additional request of an electronic device (101) related to an IMS PDN connection may include a first code indicating that a PDN connection does not exist (e.g., #54 (PDN connection does not exist)), a second code indicating a barring status determined by an operator (e.g., #8 (operator determined barring)), a third code indicating a request that is not specified (e.g., #31 (Request rejected, unspecified)), and/or a fourth code indicating a service option not supported status (e.g., #32 (service option not supported)).

According to one embodiment, if the electronic device (101) receives a rejection message related to an IMS PDN connection from the network device (300), the electronic device (101) may determine that the IMS connection via the network device (300) has failed. If the electronic device (101) determines that the IMS connection via the network device (300) has failed and obtains additional result information related to the first type of registration result and the limited function, the electronic device (101) may determine that the NAS-based message function can be performed via the network device (300). The electronic device (101) may transmit and/or receive the NAS-based message via the network device (300) (operation 919).

For example, if the electronic device (101) cannot recognize a satellite network, the electronic device (101) may determine that the network (or satellite network) to which the electronic device (101) is registered does not support voice calls (e.g., VoLTE (voice of LTE)) and CSFB based on packet switched (PS) networks based on the failure of the IMS connection through the network device (300), the acquisition of additional result information related to the first type of registration result and the limited functionality. The electronic device (101) may perform a network search related to the circuit switched (CS) networks to determine whether a CS network capable of providing a voice call exists. If the electronic device (101) does not search for a CS network capable of registering (or connecting) for a voice call, the electronic device (101) may determine that the voice call function cannot be provided at the present time. The electronic device (101) can perform a NAS-based message function recognized as supported by the network device (300) based on the acquisition of additional result information related to the failure of the IMS connection through the network device (300), the registration result of the first type, and the limited functionality.

For example, if the electronic device (101) can recognize the satellite network, it can determine that the voice call function through the satellite network is limited based on the acquisition of additional result information related to the failure of the IMS connection through the network device (300), the registration result of the first type, and the limited function, and that the message function can be provided based on the NAS. The electronic device (101) can transmit and/or receive messages based on the NAS-based message method through the network device (300).

FIG. 10 is an example for rejecting IMS registration of an electronic device in a network device according to one embodiment. As an example, the network device (300) is a network component that supports wireless communication through a satellite network, and may include a non-terrestrial wireless communication device (200) of FIG. 2 and/or a terrestrial wireless communication device (210) wirelessly connected to the non-terrestrial wireless communication device (200).

According to one embodiment referring to FIG. 10, when a network (e.g., a satellite network) to which the electronic device (101) can register (or connect) is detected, the electronic device (101) may transmit a registration (or connection) request (e.g., attach request) message to the network (operation 1011). As an example, the registration request message may include registration type (e.g., attach type or EPS attach type) information related to "combined EPS/IMSI attach".

According to one embodiment, the network device (300) may determine whether to allow registration (or connection) of the electronic device (101) based on a registration (or connection) request message received from the electronic device (101). For example, when the network device (300) allows registration (or connection) of the electronic device (101), the network device (300) may transmit a registration acceptance (e.g., attach accept) message related to a limited function supported by the satellite network to the electronic device (101) (operation 1013). For example, the registration acceptance message may include information on a first type of registration result (e.g., EPS attach result) and information on an additional result (e.g., additional update result) related to the limited function. For example, the first type of registration result may include information related to "combined EPS/IMSI attach". For example, the additional result may include information related to "SMS only".

According to one embodiment, the electronic device (101) may determine that it is registered (or connected) to a network (or satellite network) related to the network device (300) based on a registration acceptance message obtained from the network device (300). The electronic device (101) may transmit a request (e.g., PDN connectivity request) message related to IMS PDN connectivity for IMS connection through the network (or satellite network) based on the registration result of the first type (operation 1015). As an example, the request message related to IMS PDN connectivity may include information indicating that the type of APN (access point name) is IMS (e.g., APN=IMS).

According to one embodiment, the network device (300) may transmit an IMS PDN connection-related acceptance (e.g., PDN connectivity accept) message corresponding to the IMS PDN connection request message to the electronic device (101) (operation 1017).

According to one embodiment, the electronic device (101) may transmit a request message related to IMS registration (e.g., an IMS registration request) for IMS registration over a network (or satellite network) (operation 1019).

According to one embodiment, the network device (300) may transmit an IMS registration-related rejection (e.g., an IMS registration reject) message corresponding to the IMS registration request message to the electronic device (101) (operation 1021). For example, the IMS registration-related rejection message may include a rejection reason that limits further requests for IMS registration.

According to one embodiment, if the electronic device (101) receives a rejection message related to IMS registration from the network device (300), the electronic device (101) may determine that the IMS connection via the network device (300) has failed. If the electronic device (101) determines that the IMS connection via the network device (300) has failed and obtains additional result information related to the first type of registration result and the limited function, the electronic device (101) may determine that the NAS-based message function can be performed via the network device (300). The electronic device (101) may transmit and/or receive the NAS-based message via the network device (300) (operation 1023).

For example, if the electronic device (101) cannot recognize a satellite network, the electronic device (101) may determine that the network (or satellite network) to which the electronic device (101) is registered does not support PS network-based voice calls (e.g., VoLTE) and CSFB based on the failure of the IMS connection through the network device (300), the acquisition of additional result information related to the first type of registration result and the limited function. The electronic device (101) may perform a network search related to the CS network to check whether a CS network capable of providing a voice call exists. If the electronic device (101) does not search for a CS network capable of registering (or connecting) for a voice call, the electronic device (101) may determine that the voice call function cannot be provided at the present time. The electronic device (101) may perform a message function based on the NAS recognized as supported by the network device (300) based on the failure of the IMS connection through the network device (300), the acquisition of additional result information related to the first type of registration result and the limited function.

For example, if the electronic device (101) can recognize the satellite network, it can determine that the voice call function via the satellite network is limited based on the acquisition of additional result information related to the failure of the IMS connection via the network device (300), the registration result of the first type, and the limited function, and that the message function can be provided based on the NAS. The electronic device (101) can transmit and/or receive messages based on the NAS-based message method via the network device (300). For example, if the electronic device (101) can recognize the satellite network, it can determine that the voice call function is limited without performing a network search.

FIG. 11 is an example for limiting IMS connection of an electronic device in a network device according to one embodiment. As an example, the network device (300) is a network component that supports wireless communication via a satellite network and may include a non-terrestrial wireless communication device (200) of FIG. 2 and/or a terrestrial wireless communication device (210) wirelessly connected to the non-terrestrial wireless communication device (200).

According to one embodiment referring to FIG. 11, when a network (e.g., a satellite network) to which the electronic device (101) can register (or connect) is detected, the electronic device (101) may transmit a registration (or connection) request (e.g., attach request) message to the network (operation 1111). As an example, the registration request message may include registration type (e.g., attach type or EPS attach type) information related to "combined EPS/IMSI attach".

According to one embodiment, the network device (300) may determine whether to allow registration (or connection) of the electronic device (101) based on a registration (or connection) request message received from the electronic device (101). For example, if the network device (300) allows registration (or connection) of the electronic device (101), the network device (300) may transmit a registration acceptance (e.g., attach accept) message related to a limited function supported by the satellite network to the electronic device (101) (operation 1113). For example, the registration acceptance message may include information on a first type of registration result (e.g., EPS attach result), information on an additional result (e.g., additional update result) related to the limited function, and information related to a limitation of voice calls in a PS (packet switched) network (e.g., VoPS (voice of PS) = 0). For example, the first type of registration result may include information related to "combined EPS/IMSI attach". For example, the additional result may include information related to "SMS only".

According to one embodiment, the electronic device (101) may determine that it is registered (or connected) to a network (or satellite network) related to the network device (300) based on a registration acceptance message obtained from the network device (300). The electronic device (101) may determine that the IMS connection via the network (or satellite network) is restricted based on information related to the restriction of voice calls in the PS network. When the electronic device (101) obtains additional result information related to the first type of registration result and the restricted function through the network device (300), it may determine that it can perform a NAS-based message function through the network device (300). The electronic device (101) may transmit and/or receive a NAS-based message through the network device (300) (operation 1115).

FIG. 12 is an example of supporting satellite communication of an electronic device in a network device according to one embodiment. As an example, the network device (300) is a network component that supports wireless communication via a satellite network, and may include a non-terrestrial wireless communication device (200) of FIG. 2 and/or a terrestrial wireless communication device (210) wirelessly connected to the non-terrestrial wireless communication device (200).

According to one embodiment referring to FIG. 12, when a network (e.g., a satellite network) to which the electronic device (101) can register (or connect) is detected, the electronic device (101) may transmit a registration (or connection) request (e.g., attach request) message to the network (operation 1211). As an example, the registration request message may include registration type (e.g., attach type or EPS attach type) information related to "combined EPS/IMSI attach".

According to one embodiment, the network device (300) may determine whether to allow registration (or connection) of the electronic device (101) based on a registration (or connection) request message received from the electronic device (101). For example, if the network device (300) allows registration (or connection) of the electronic device (101), the network device (300) may transmit a registration acceptance (e.g., attach accept) message related to a limited function supported by the satellite network to the electronic device (101) (operation 1213). For example, the registration acceptance message may include information on a first type of registration result (e.g., EPS attach result). For example, the first type of registration result may include information related to a "combined EPS/IMSI attach."

According to one embodiment, the electronic device (101) may determine that it is registered (or connected) to a network (or satellite network) related to the network device (300) based on a registration acceptance message obtained from the network device (300). The electronic device (101) may transmit a request message related to IMS PDN connectivity (e.g., PDN connectivity request) for IMS connection through the network (or satellite network) based on the registration result of the first type (operation 1215). As an example, the request message related to IMS PDN connectivity may include information indicating that the type of APN is IMS (e.g., APN=IMS).

In one embodiment, the network device (300) may transmit an IMS PDN connectivity-related rejection (e.g., PDN connectivity reject) message corresponding to the IMS PDN connection request message to the electronic device (101) when the satellite network provides limited functionality (operation 1217). For example, the IMS PDN connectivity-related rejection message may include a rejection reason (e.g., ESM cause) that limits additional requests related to the IMS PDN connection. For example, a rejection reason for rejecting (or limiting) an additional request of an electronic device (101) related to an IMS PDN connection may include a first code indicating that a PDN connection does not exist (e.g., #54 (PDN connection does not exist)), a second code indicating a barring status determined by an operator (e.g., #8 (operator determined barring)), a third code indicating a request that is not specified (e.g., #31 (Request rejected, unspecified)), and/or a fourth code indicating a service option not supported status (e.g., #32 (service option not supported)).

According to one embodiment, if the electronic device (101) receives a rejection message related to an IMS PDN connection from the network device (300), the electronic device (101) may determine that the IMS connection via the network device (300) has failed. For example, if the electronic device (101) cannot recognize a satellite network, the electronic device (101) may determine that the network (or satellite network) to which the electronic device (101) is registered does not support PS network-based voice calls (e.g., VoLTE) but supports CSFB based on the failure of the IMS connection via the network device (300) and the acquisition of the first type of registration result information.

According to one embodiment, when an occurrence of an event related to a voice call is detected, the electronic device (101) may transmit a voice call request (e.g., extended service request) message related to CSFB to the network device (300) (operation 1219). For example, the voice call request message related to CSFB may include an extended service request message. For example, the extended service request message may include service type information of "mobile originating CS fallback" or "1xCS fallback."

According to one embodiment, when the network device (300) provides limited functionality in a satellite network, the network device (300) may transmit a CSFB-related voice call rejection (e.g., service reject) message corresponding to a CSFB-related voice call request message to the electronic device (101) (operation 1221). For example, the CSFB-related voice call rejection message may include a rejection reason (e.g., EMM (EPS mobility management) cause) for limiting an additional request of the electronic device (101) related to the CSFB and/or setting information of a timer (e.g., T3442) related to the CSFB of the electronic device (101). For example, the rejection reason for rejecting (or limiting) an additional request of the electronic device (101) related to the CSFB may include a fifth code (e.g., #39 (CS service temporarily not available)). For example, the setting information of a timer related to CSFB may include a value (e.g., a maximum value) specified as information related to the operating time of a timer that is set so that the electronic device (101) does not attempt CSFB while the operation of the timer related to CSFB is maintained.

According to one embodiment, the electronic device (101) may determine that the voice call function cannot be provided through the network device (101) based on a voice call rejection message related to CSFB. The electronic device (101) may restrict transmission of a request message related to a voice call until the operating time of a timer related to CSFB expires based on a rejection reason related to a limitation of an additional request included in the voice call rejection message related to CSFB and setting information of a timer related to CSFB.

According to one embodiment, the electronic device (101) may determine that, if the satellite network is recognizable, the voice call function via the satellite network is limited based on the failure of the IMS connection via the network device (300), the acquisition of the first type of registration result information, and the message function can be provided based on the NAS.

According to one embodiment, the electronic device (101) can transmit and/or receive a NAS-based message via the network device (300) (operation 1223).

FIG. 13 is an example of supporting satellite communication of an electronic device satisfying a specified condition in a network device according to one embodiment. As an example, the network device (300) is a network component that supports wireless communication through a satellite network, and may include a non-terrestrial wireless communication device (200) of FIG. 2 and/or a terrestrial wireless communication device (210) wirelessly connected to the non-terrestrial wireless communication device (200).

According to one embodiment referring to FIG. 13, when a network (e.g., a satellite network) to which the electronic device (101) can register (or connect) is detected, the electronic device (101) may transmit a registration (or connection) request (e.g., attach request) message to the network (operation 1311). As an example, the registration request message may include registration type (e.g., attach type or EPS attach type) information related to "combined EPS/IMSI attach".

According to one embodiment, the network device (300) may determine whether to allow registration (or connection) of the electronic device (101) based on a registration (or connection) request message received from the electronic device (101). For example, if the network device (300) allows registration (or connection) of the electronic device (101), the network device (300) may transmit a registration acceptance (e.g., attach accept) message related to a limited function supported by the satellite network to the electronic device (101) (operation 1313). For example, the registration acceptance message may include information on a second type of registration result (e.g., EPS attach result). For example, the first type of registration result may include information related to “EPS only.”

According to one embodiment, the electronic device (101) may determine that it is registered (or connected) to a network (or satellite network) related to the network device (300) based on a registration acceptance message obtained from the network device (300). The electronic device (101) may transmit a request message related to IMS PDN connectivity (e.g., PDN connectivity request) for IMS connection through the network (or satellite network) based on the registration result of the first type (operation 1315). As an example, the request message related to IMS PDN connectivity may include information indicating that the type of APN (access point name) is IMS (e.g., APN=IMS).

In one embodiment, the network device (300) may transmit an IMS PDN connectivity rejection (e.g., PDN connectivity reject) message corresponding to the IMS PDN connection request message to the electronic device (101) when the satellite network provides limited functionality (operation 1317). For example, the IMS PDN connectivity rejection message may include a rejection reason (e.g., ESM cause) that limits additional requests related to the IMS PDN connection.

According to one embodiment, if the electronic device (101) receives a rejection message related to an IMS PDN connection from the network device (300), the electronic device (101) may determine that the IMS connection via the network device (300) has failed. For example, if the electronic device (101) cannot recognize a satellite network, the electronic device (101) may determine that the electronic device (101) cannot provide an IMS service and a NAS-based message function via the network (or satellite network) to which the electronic device (101) is registered based on a failure of the IMS connection via the network device (300) and acquisition of the second type of registration result information. For example, the IMS service may include an IMS-based voice call function and/or message function.

According to one embodiment, the electronic device (101) may determine that a voice call function through the satellite network is limited and a message function can be provided based on NAS based on a failure of an IMS connection through the network device (300) and acquisition of the second type of registration result information when the electronic device (101) can recognize the satellite network. For example, the electronic device (101) may limit the provision of a satellite service through the network device (300).

According to one embodiment, the electronic device (101) can transmit and/or receive a NAS-based message via the network device (300) (operation 1319).

FIG. 14 is an example of supporting satellite communication of an electronic device satisfying a specified condition in a network device according to one embodiment. As an example, the network device (300) is a network component that supports wireless communication through a satellite network, and may include a non-terrestrial wireless communication device (200) of FIG. 2 and/or a terrestrial wireless communication device (210) wirelessly connected to the non-terrestrial wireless communication device (200).

According to one embodiment referring to FIG. 14, when a network (e.g., a satellite network) to which the electronic device (101) can register (or connect) is detected, the electronic device (101) may transmit a registration (or connection) request (e.g., attach request) message to the network (operation 1411). As an example, the registration request message may include registration type (e.g., attach type or EPS attach type) information related to "combined EPS/IMSI attach".

According to one embodiment, the network device (300) may determine whether to allow registration (or connection) of the electronic device (101) based on a registration (or connection) request message received from the electronic device (101). For example, when the network device (300) allows registration (or connection) of the electronic device (101), the network device (300) may transmit a registration acceptance (e.g., attach accept) message related to a limited function supported by the satellite network to the electronic device (101) (operation 1413). For example, the registration acceptance message may include information on a second type of registration result (e.g., EPS attach result) and information on an additional result (e.g., additional update result) related to the limited function. For example, the first type of registration result may include information related to "EPS only". For example, the additional result may include information related to "SMS only".

According to one embodiment, the electronic device (101) may determine that it is registered (or connected) to a network (or satellite network) related to the network device (300) based on a registration acceptance message obtained from the network device (300). The electronic device (101) may transmit a request (e.g., PDN connectivity request) message related to IMS PDN connectivity for IMS connection through the network (or satellite network) based on the registration result of the first type (operation 1415). As an example, the request message related to IMS PDN connectivity may include information indicating that the type of APN (access point name) is IMS (e.g., APN=IMS).

According to one embodiment, when the network device (300) provides limited functionality in the satellite network, the network device (300) may transmit an IMS PDN connection-related rejection (e.g., PDN connectivity reject) message corresponding to the IMS PDN connection request message to the electronic device (101) (operation 1417). For example, the IMS PDN connection-related rejection message may include a rejection reason (e.g., ESM cause) that rejects (or restricts) an additional request of the electronic device (101) related to the IMS PDN connection.

According to one embodiment, if the electronic device (101) receives a rejection message related to an IMS PDN connection from the network device (300), the electronic device (101) may determine that the IMS connection via the network device (300) has failed. For example, if the electronic device (101) cannot recognize a satellite network, the electronic device (101) may determine that the electronic device (101) cannot provide an IMS service and a NAS-based message function via the registered network (or satellite network) based on the failure of the IMS connection via the network device (300), the acquisition of the second type of registration result information, and the non-support of additional result information (e.g., “SMS only”).

In one embodiment, the electronic device (101) may determine that the voice call function via the satellite network is limited and the message function can be provided based on NAS based on the failure of the IMS connection via the network device (300), the acquisition of the second type of registration result information, and the support of additional result information (e.g., “SMS only”) when the electronic device (101) cannot recognize the satellite network. As an example, the electronic device (101) may be limited in providing the satellite service via the network device (300).

According to one embodiment, the electronic device (101) can transmit and/or receive a NAS-based message via the network device (300) (operation 1419).

According to one embodiment, an electronic device (101) supporting a second type of registration result and additional results related to limited functions may determine, if it can recognize a satellite network, that a voice call function via the satellite network is limited based on a failure of an IMS connection via the network device (300) and acquisition of the second type of registration result information and additional result information, and that a message function can be provided based on NAS. For example, the electronic device (101) may be limited in providing a satellite service via the network device (300).

According to one embodiment, when the electronic device (101) determines that it cannot provide an IMS service and a NAS-based message function, it may output information related to a limitation of the voice call and/or message function to the outside based on the occurrence of an event related to the voice call and/or message.

According to one embodiment, the network device (300) may limit the IMS connection of the electronic device (101) based on a rejection message related to the IMS registration of the electronic device (101), such as in FIG. 10, in the case of FIG. 12, FIG. 13 and/or FIG. 14.

According to one embodiment, the network device (300) may limit the IMS connection of the electronic device (101) based on information related to limitation of voice calls in a PS (packet switched) network included in a registration (or connection) acceptance message, such as in FIG. 11, in the case of FIG. 12, FIG. 13 and/or FIG. 14.

According to one embodiment, a method of operating a network device supporting satellite communication (e.g., a network device (300) of FIG. 3) may include an operation of receiving a message related to a registration request from an electronic device (e.g., an electronic device (101) of FIG. 1 or FIG. 2). According to one embodiment, the method of operating the network device may include an operation of transmitting a registration acceptance message related to the limited function to the electronic device when it is determined that the electronic device can provide a limited function. According to one embodiment, the method of operating the network device may include an operation of transmitting a rejection message related to the IMS connection to the electronic device based on the provision of the limited function when a request message related to the IMS connection is received from the electronic device. According to one embodiment, the method of operating the network device may include an operation of supporting a message function based on a non-access stratum (NAS) of the electronic device as one of the limited functions that the electronic device can provide.

According to one embodiment, a method of operating a network device may include an operation of determining whether to allow registration of an electronic device supporting satellite communications when a message related to a registration request is received from an electronic device. According to one embodiment, the operation of transmitting a rejection message related to an IMS connection to the electronic device may include an operation of transmitting a registration acceptance message including a first type of registration result and/or an additional result related to a restricted function to the electronic device when it is determined to allow registration of the electronic device supporting satellite communications.

According to one embodiment, a method of operating a network device may include, when a request message related to a circuit switched fall back (CSFB) is received from an electronic device based on transmission of a registration acceptance message including a first type of registration result, transmitting a rejection message related to a CSFB to the electronic device.

According to one embodiment, the operation of transmitting a rejection message related to an IMS connection to the electronic device may include an operation of transmitting a registration acceptance message to the electronic device, the registration result including a second type different from the first type and/or an additional result related to a restricted function, if it is determined that registration of an electronic device satisfying a specified condition among electronic devices supporting satellite communications is permitted.

In one embodiment, the act of transmitting a rejection message related to an IMS connection to the electronic device may include, when a request message related to an IMS (IP multimedia subsystem) PDN (packet data network) connection is received from the electronic device, transmitting a rejection message related to the IMS PDN connection to the electronic device based on the provision of limited functionality.

According to one embodiment, the act of transmitting a reject message related to an IMS connection to the electronic device may include, when a request message related to an IMS PDN connection is received from the electronic device, transmitting an accept message related to the IMS PDN connection to the electronic device, and, when a request message related to an IMS registration is received from the electronic device, transmitting a reject message related to an IMS registration to the electronic device based on the provision of limited functionality.

In one embodiment, the act of transmitting a registration acceptance message to an electronic device may include transmitting a registration acceptance message to the electronic device that includes information relating to restrictions on voice calls in a packet switched (PS) network, if it is determined that the electronic device is capable of providing limited functionality.

The embodiments of the present invention disclosed in this specification and drawings are merely specific examples presented to easily explain the technical contents according to the embodiments of the present invention and to help understand the embodiments of the present invention, and are not intended to limit the scope of the embodiments of the present invention. Therefore, the scope of one embodiment of the present invention should be interpreted as including all changes or modified forms derived based on the technical idea of one embodiment of the present invention in addition to the embodiments disclosed herein.

Claims (20)

For network devices,
Communication circuit supporting satellite communications;
At least one processor operatively connected to said communication circuit,
At least one processor of the above,
Receive a message related to a registration request from an electronic device;
If it is determined that the electronic device can provide a limited function, a registration acceptance message related to the limited function is transmitted to the electronic device through the communication circuit,
When a request message related to an IMS connection is received from the electronic device, a rejection message related to an IMS connection is transmitted to the electronic device through the communication circuit based on the provision of the limited function.
A network device supporting a message function based on the NAS (non-access stratum) of the above electronic device.
In paragraph 1,
At least one processor of the above,
When a message related to a registration request is received from the electronic device, it is determined whether to allow registration of the electronic device supporting satellite communication,
A network device that, when it is determined that registration of an electronic device supporting the above satellite communication is permitted, transmits to the electronic device a registration acceptance message including the first type of registration result and/or additional results related to limited functionality.
In the second paragraph,
The registration result of the first type above includes information related to registration of the first communication method and the second communication method,
The above additional result is a network device that includes information related to the provision of a message function.
In the second paragraph,
A network device that transmits, through the communication circuit, a rejection message related to the CSFB to the electronic device when the at least one processor receives a request message related to the circuit switched fall back (CSFB) from the electronic device based on transmission of the registration acceptance message including the registration result of the first type.
In paragraph 4,
A network device wherein the rejection message related to the CSFB includes a reason related to the rejection of the CSFB and/or specified time information related to the electronic device's restriction of transmission of a request message related to the CSFB.
In the second paragraph,
At least one processor of the above,
A network device that, when it is determined that registration of an electronic device satisfying a specified condition among the electronic devices supporting the above satellite communication is permitted, transmits the registration permission message including the registration result of a second type different from the first type and/or the additional result related to a limited function to the electronic device.
In paragraph 6,
A network device, wherein the registration result of the second type includes information related to registration of the first communication method.
In paragraph 1,
A network device wherein said at least one processor, when receiving a request message related to an IMS (IP multimedia subsystem) PDN (packet data network) connection from said electronic device, transmits a rejection message related to the IMS PDN connection to said electronic device through said communication circuit based on the provision of said limited functionality.
In paragraph 1,
At least one processor of the above,
When a request message related to an IMS PDN connection is received from the electronic device, an acceptance message related to the IMS PDN connection is transmitted to the electronic device through the communication circuit,
A network device that, upon receiving a request message related to IMS registration from the electronic device, transmits a rejection message related to the IMS registration to the electronic device through the communication circuit based on the provision of the limited function.
In paragraph 1,
At least one processor of the above,
A network device that transmits, to the electronic device via the communication circuit, a registration acceptance message including information related to restrictions on voice calls in a PS (packet switched) network, when it is determined that the electronic device can provide limited functions.
In a method of operating a network device supporting satellite communication,
An action to receive a message relating to a registration request from an electronic device;
If it is determined that the electronic device can provide limited functions, an action of transmitting a registration acceptance message related to the limited functions to the electronic device;
When a request message related to an IMS connection is received from the electronic device, an action of transmitting a rejection message related to an IMS connection to the electronic device based on the provision of the limited function; and
A method comprising operations supporting a messaging function based on a non-access stratum (NAS) of the electronic device.
In Article 11,
Further comprising an action of determining whether to allow registration of the electronic device supporting satellite communication when a message related to a registration request is received from the electronic device;
The action of transmitting a rejection message related to the above IMS connection to the above electronic device is:
A method comprising the action of transmitting to the electronic device a registration acceptance message including a first type of registration result and/or additional results related to limited functionality, when it is determined that registration of the electronic device supporting the satellite communication is permitted.
In Article 12,
The registration result of the first type above includes information related to registration of the first communication method and the second communication method,
The above additional result is a method in which the message function includes information related to the provision.
In Article 12,
A method further comprising the action of transmitting a rejection message related to CSFB to the electronic device when a request message related to CSFB is received from the electronic device based on transmission of the registration acceptance message including the registration result of the first type.
In Article 14,
A method wherein the rejection message related to the CSFB includes a reason related to the rejection of the CSFB and/or specified time information related to the electronic device's restriction of transmission of a request message related to the CSFB.
In Article 12,
The action of transmitting a rejection message related to the above IMS connection to the above electronic device is:
A method comprising: when it is determined that registration of an electronic device satisfying a specified condition among the electronic devices supporting the satellite communication is permitted, a method comprising transmitting a registration permit message including a registration result of a second type different from the first type and/or the additional result related to a limited function to the electronic device.
In Article 16,
A method wherein the registration result of the second type includes information related to registration of the first communication method.
In Article 11,
The action of transmitting a rejection message related to the above IMS connection to the above electronic device is:
A method comprising: receiving a request message related to an IMS (IP multimedia subsystem) PDN (packet data network) connection from the electronic device; transmitting a rejection message related to the IMS PDN connection to the electronic device based on the provision of the limited functionality.
In Article 11,
The action of transmitting a rejection message related to the above IMS connection to the above electronic device is:
When a request message related to an IMS PDN connection is received from the electronic device, an operation of transmitting an acceptance message related to the IMS PDN connection to the electronic device; and
A method comprising the action of transmitting a rejection message related to IMS registration to the electronic device based on the provision of the limited functionality when a request message related to IMS registration is received from the electronic device.
In Article 11,
The action of transmitting the above registration acceptance message to the electronic device is:
A method comprising the action of transmitting to the electronic device a registration acceptance message including information relating to restrictions on voice calls in a packet switched (PS) network, when it is determined that the electronic device is capable of providing limited functionality.

Images