Electronic device for providing message by using non-terrestrial network communication, method for providing message based on non-terrestrial network communication, and storage medium

Abstract

According to an embodiment, a method for providing a message is provided. The method may comprise an operation of receiving, from a transmission-side device through a non-terrestrial network, a first message including a first MSISDN for transmission and a second MSISDN for reception. The method may comprise an operation of identifying whether or not a reception-side device corresponding to the second MSISDN may use an RCS. The method may comprise an operation of providing, on the basis that the reception-side device may use the RCS, a second message including the second MSISDN for reception and information associated with an RCS-based chatbot for transmission corresponding to the first MSISDN, which replaces the first MSISDN. Other various embodiments are possible.

Description

Electronic device for providing messages using non-terrestrial network communication, method for providing messages based on non-terrestrial network communication, and storage medium

[0001] The present disclosure relates to an electronic device for providing a message using non-terrestrial network communication, a method for providing a message based on non-terrestrial network communication, and a storage medium.

[0002] Recently, electronic devices supporting non-terrestrial network communications (e.g., satellite communications) are being actively introduced. For example, electronic devices can communicate with satellites operated by existing satellite communication companies by utilizing their frequencies and communication methods. For example, electronic devices can communicate with satellites using cellular frequencies based on the LTE (long-term evolution) standard (or 5G standard). For another example, electronic devices can communicate with satellites based on the 5G NTN (non-terrestrial networks) standard. In a wireless communication system, electronic devices (e.g., user equipment (UE)) can access a wireless communication network and use voice or data communication services at a fixed location or while moving.

[0003] The above information may be provided as background information to aid in understanding this document. None of the above is claimed to be prior art related to this document or can be used to determine prior art.

[0004] According to one embodiment, a method for providing a message is provided. The method may include receiving, from a sending device, a first message including a first MSISDN for sending and a second MSISDN for receiving, via a non-terrestrial network. The method may include determining whether a receiving device corresponding to the second MSISDN is RCS-enabled. The method may include providing, based on the RCS-enabled device, a second message including information associated with an RCS-based chatbot for sending, corresponding to the first MSISDN replacing the first MSISDN, and the second MSISDN for receiving.

[0005] According to one embodiment, a storage medium storing at least one computer-readable instruction may be provided. The at least one instruction, when executed by a processor of an electronic device, may cause the electronic device to perform at least one operation. The at least one operation may include receiving, from a sending device, a first message including a first MSISDN for sending and a second MSISDN for receiving, over a non-terrestrial network. The at least one operation may include determining whether a receiving device corresponding to the second MSISDN is RCS-enabled. The at least one operation may include providing, based on the RCS-enabled device, a second message including information associated with an RCS-based chatbot for sending corresponding to the first MSISDN that replaces the first MSISDN and the second MSISDN for receiving.

[0006] According to one embodiment, an electronic device may be provided. The electronic device may include a memory storing at least one instruction. The electronic device may include a processor. The at least one instruction, when executed by the processor, may cause the electronic device to perform at least one operation. The at least one operation may include receiving, from a sending device, a first message including a first MSISDN for sending and a second MSISDN for receiving, via a non-terrestrial network. The at least one operation may include determining whether a receiving device corresponding to the second MSISDN is capable of RCS. The at least one operation may include providing, based on the RCS availability of the receiving device, a second message including information associated with an RCS-based chatbot for sending corresponding to the first MSISDN that replaces the first MSISDN and the second MSISDN for receiving.

[0007] According to one embodiment, a method for providing a message is provided. The method may include receiving a first message including a first MSISDN for sending and a second MSISDN for receiving corresponding to the electronic device. The method may include obtaining at least one piece of information registered in association with a chatbot corresponding to the first MSISDN based on a determination that the first MSISDN is an MSISDN associated with a chatbot. The method may include providing the content of the first message and the at least one piece of information.

[0008] According to one embodiment, a storage medium storing at least one computer-readable instruction may be provided. The at least one instruction, when executed by a processor of an electronic device, may cause the electronic device to perform at least one operation. The at least one operation may include receiving a first message including a first MSISDN for transmission and a second MSISDN for reception corresponding to the electronic device. The at least one operation may include obtaining at least one piece of information registered in association with a chatbot corresponding to the first MSISDN based on confirming that the first MSISDN is an MSISDN associated with a chatbot. The at least one operation may include providing content of the first message and the at least one piece of information.

[0009] According to one embodiment, an electronic device may be provided. The electronic device may include a memory storing at least one instruction. The electronic device may include a processor. The at least one instruction, when executed by the processor, may cause the electronic device to perform at least one operation. The at least one operation may include receiving a first message including a first MSISDN for transmission and a second MSISDN for reception corresponding to the electronic device. The at least one operation may include obtaining at least one piece of information registered in association with a chatbot corresponding to the first MSISDN based on confirming that the first MSISDN is an MSISDN associated with a chatbot. The at least one operation may include providing content of the first message and the at least one piece of information.

[0010] According to one embodiment, a method for providing a message is provided. The method may include receiving, from a sending device, a first message based on a first type scheme, over a non-terrestrial network, the first message including a first MSISDN for sending and a second MSISDN for receiving. The method may include determining whether a receiving device corresponding to the second MSISDN can use a second type scheme different from the first type scheme. The method may include providing, depending on whether the receiving device can use the second type scheme, a second message based on the second type scheme, the second message including information based on the second type scheme for sending and the second MSISDN for receiving, or providing a third message based on the first type scheme, the third message including a third MSISDN for sending and the second MSISDN for receiving, the third message being mapped to the first MSISDN.

[0011] According to one embodiment, a storage medium storing at least one computer-readable instruction may be provided. The at least one instruction, when executed by a processor of an electronic device, may cause the electronic device to perform at least one operation. The at least one operation may include receiving, from a sending device over a non-terrestrial network, a first message based on a first type scheme, the first message including a first MSISDN for sending and a second MSISDN for receiving. The at least one operation may include checking whether a receiving device corresponding to the second MSISDN is capable of using a second type scheme different from the first type scheme. The at least one operation may include providing a second message based on the second type scheme, including information based on the second type scheme for transmission and the second MSISDN for reception, or providing a third message based on the first type scheme, including a third MSISDN for transmission mapped to the first MSISDN and the second MSISDN for reception, depending on whether the receiving device can use the second type scheme.

[0012] According to one embodiment, an electronic device may be provided. The electronic device may include a memory storing at least one instruction. The electronic device may include a processor. The at least one instruction, when executed by the processor, may cause the electronic device to perform at least one operation. The at least one operation may include receiving, from a sending device through a non-terrestrial network, a first message based on a first type scheme, the first message including a first MSISDN for sending and a second MSISDN for receiving. The at least one operation may include checking whether a receiving device corresponding to the second MSISDN can use a second type scheme different from the first type scheme. The at least one operation may include providing a second message based on the second type scheme, including information based on the second type scheme for transmission and the second MSISDN for reception, or providing a third message based on the first type scheme, including a third MSISDN for transmission mapped to the first MSISDN and the second MSISDN for reception, depending on whether the receiving device can use the second type scheme.

[0013] FIG. 1 is a block diagram of an electronic device within a network environment, according to one embodiment.

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

[0015] FIG. 3 is a drawing for explaining the connection of an electronic device according to one embodiment.

[0016] FIG. 4 is a diagram for explaining a non-terrestrial network system according to one embodiment.

[0017] FIG. 5A is a flowchart for explaining an operating method of an electronic device according to one embodiment.

[0018] FIG. 5b is a flowchart illustrating an operating method of an electronic device according to one embodiment.

[0019] Figure 6a is a flowchart illustrating a method for providing a message according to one embodiment.

[0020] FIG. 6b is a drawing for explaining a message providing method according to one embodiment.

[0021] FIG. 6c is an example of a screen for a received message according to one embodiment.

[0022] Figure 7a is a flowchart illustrating a method for providing a message according to one embodiment.

[0023] FIG. 7b is a drawing for explaining a message providing method according to one embodiment.

[0024] Figure 8a is a flowchart illustrating a method for providing a message according to one embodiment.

[0025] FIG. 8b is a drawing for explaining a message providing method according to one embodiment.

[0026] FIG. 8c is an example of a screen for a received message according to one embodiment.

[0027] Figure 8d is a flowchart for explaining the operation method of the receiving device.

[0028] Figure 9a is a flowchart illustrating a method for providing a message according to one embodiment.

[0029] Figure 9b is a flowchart illustrating a method for providing a message according to one embodiment.

[0030] FIG. 10a is a flowchart illustrating a method for providing a message according to one embodiment.

[0031] FIG. 10b is a drawing for explaining a message providing method according to one embodiment.

[0032] Fig. 11 is a flowchart illustrating a method for providing a message according to one embodiment.

[0033] Figure 12a is a diagram for explaining chatbot creation according to one embodiment.

[0034] Figure 12b is a drawing for explaining a screen provided according to one embodiment.

[0035] FIG. 13a and FIG. 13b are flowcharts illustrating a method of providing a message according to one embodiment.

[0036] FIG. 14a and FIG. 14b are flowcharts illustrating a method of providing a message according to one embodiment.

[0037] FIG. 1 is a block diagram of an electronic device (101) within 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 the electronic device (104) or a server (108) via a second network (199) (e.g., a long-range wireless communication network). In 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)).

[0038] The processor (120) may, for example, execute software (e.g., a program (140)) to control at least one other component (e.g., a hardware or software component) of the electronic device (101) connected to the processor (120) and perform various data processing or operations. According to one embodiment, as at least a part of the data processing or operations, the processor (120) may store commands or data received from other components (e.g., a sensor module (176) or a communication module (190)) in a volatile memory (132), process the commands or data stored in the volatile memory (132), and store result data in a non-volatile 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 graphics 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 with the main processor (121). For example, when the electronic device (101) includes the main processor (121) and the auxiliary processor (123), the auxiliary processor (123) may be configured to use less power than the main processor (121) or to be specialized for a given function. The auxiliary processor (123) may be implemented separately from the main processor (121) or as a part thereof.

[0039] The auxiliary processor (123) may control at least a portion of functions or states associated with at least one component (e.g., a display module (160), a sensor module (176), or a communication module (190)) of the electronic device (101), 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 unit) may include a hardware structure specialized for processing artificial intelligence models. The artificial intelligence models may be generated through machine learning. This learning can be performed, for example, in the electronic device (101) itself where artificial intelligence is performed, or can be performed through a separate server (e.g., server (108)). The learning algorithm can 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 can include multiple 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), a deep Q-network, or a combination of two or more of the above, but is not limited to the examples described above. In addition to, or alternatively to, a hardware structure, an artificial intelligence model may include a software structure.

[0040] 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 non-volatile memory (134).

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

[0042] 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).

[0043] The audio output module (155) can output audio signals 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 incoming calls. In one embodiment, the receiver can be implemented separately from the speaker or as part of the speaker.

[0044] 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) may 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) may include a touch sensor configured to detect a touch, or a pressure sensor configured to measure the intensity of a force generated by the touch.

[0045] 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 acquire sound through the input module (150), output sound through the sound output module (155), or an external electronic device (e.g., electronic device (102)) (e.g., speaker or headphone) directly or wirelessly connected to the electronic device (101).

[0046] The sensor module (176) can detect the operating status (e.g., power or temperature) of the electronic device (101) or the external environmental status (e.g., user status) and generate an electrical signal or data value corresponding to the detected status. 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.

[0047] 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)). In 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.

[0048] 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., 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).

[0049] The haptic module (179) can convert electrical signals into mechanical stimuli (e.g., vibration or movement) or electrical stimuli that a user can perceive through tactile or kinesthetic sensations. According to one embodiment, the haptic module (179) can include, for example, a motor, a piezoelectric element, or an electrical stimulation device.

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

[0051] 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).

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

[0053] The communication module (190) may support the 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., electronic device (102), electronic device (104), or server (108)), and the performance of communication through the established communication channel. The communication module (190) may operate independently from the processor (120) (e.g., 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 global navigation satellite system (GNSS) communication module) or a wired communication module (194) (e.g., a local area network (LAN) communication module, or a power line communication module). Among these communication modules, the corresponding communication module can communicate with an external electronic device (104) via a first network (198) (e.g., a short-range communication network such as Bluetooth, wireless fidelity (WiFi) direct, or infrared data association (IrDA)) 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 can be integrated into a single component (e.g., a single chip) or implemented as multiple separate components (e.g., multiple chips). The wireless communication module (192) can verify or authenticate the electronic device (101) within a communication network such as the first network (198) or the second network (199) by using subscriber information (e.g., an international mobile subscriber identity (IMSI)) stored in the subscriber identification module (196).

[0054] The wireless communication module (192) can support 5G networks and next-generation communication technologies following the 4G network, such as 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 transmission rate. The wireless communication module (192) can 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) can support various requirements specified in the electronic device (101), an external electronic device (e.g., the electronic device (104)), or a network system (e.g., the 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), or 1 ms or less for round trip) for URLLC realization.

[0055] The antenna module (197) can transmit or receive signals or power to or from an external device (e.g., an external electronic device). In one embodiment, the antenna module (197) may include an antenna including a radiator formed of a conductor or a conductive pattern formed on a substrate (e.g., a PCB). In one embodiment, the antenna module (197) may 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), may be selected from the plurality of antennas, for example, by the communication module (190). A signal or power may be transmitted or received between the communication module (190) and an external electronic device via the at least one selected antenna. In some embodiments, in addition to the radiator, another component (e.g., a radio frequency integrated circuit (RFIC)) may be additionally formed as a part of the antenna module (197).

[0056] In one embodiment, the antenna module (197) may form a mmWave antenna module. In one embodiment, the mmWave antenna module may include a printed circuit board, an RFIC disposed 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., an array antenna) disposed on or adjacent a second side (e.g., a top side or a side side) of the printed circuit board and capable of transmitting or receiving signals in the designated high-frequency band.

[0057] At least some of the above 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)).

[0058] According to 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). According to 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 the function or at least a part of the service. One or more external electronic devices that receive the request may execute at least a portion 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 portion of a response to the request. For this purpose, cloud computing, distributed computing, mobile edge computing (MEC), or client-server computing technology may be used, for example. The electronic device (101) may provide an ultra-low latency service by using distributed computing or mobile edge computing, for example. In another embodiment, the external electronic device (104) may include an Internet of Things (IoT) device. The server (108) may be an intelligent server utilizing 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.

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

[0060] The electronic device (101) can transmit and / or receive data via a terrestrial network and / or a non-terrestrial network. The electronic device (101) may have the same configuration as the electronic device (101) presented in FIG. 1 or may include the configuration of the electronic device (101) presented in FIG. 1.

[0061] A 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 that the electronic device (101) can support. For example, the terrestrial wireless communication device (210) may include an eNodeB (e.g., an LTE-based base station) or a gNodeB (e.g., a 5G (or NR)-based base station), but there is no limitation on the type thereof.

[0062] A non-terrestrial network may refer to a network capable of providing data communication via at least one non-terrestrial wireless communication device (220). For example, the non-terrestrial wireless communication device (220) may include at least one of various communication devices such as a base station or repeater that are not located on the ground. For example, the non-terrestrial wireless communication device (220) may include, but is not limited to, a satellite and / or an unmanned aerial vehicle. 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.

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

[0064] 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 interconnected (e.g., a network provided by the same operator).

[0065] The electronic device (101) may perform wireless communication via a non-terrestrial network when communication with the terrestrial network is unavailable or not smooth. Alternatively, the electronic device (101) may perform wireless communication via a non-terrestrial network regardless of the status of communication with the terrestrial network, depending on the case.

[0066] According to one embodiment, the electronic device (101) may include a processor (120), a display module (160) (e.g., a display), 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).

[0067] 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, instructions (e.g., a program (140) of FIG. 1) at least temporarily stored in a memory (e.g., a memory (130) of FIG. 1), and may perform various data processing or operations. According to one embodiment, the processor (120) may control overall operations related to terrestrial network communication and / or non-terrestrial network communication. For example, the processor (120) may include a communication processor (e.g., an auxiliary processor (123) of FIG. 1) related to terrestrial network communication and / or non-terrestrial network communication.

[0068] The display module (160) can visually provide information to an external party (e.g., a user) of the electronic device (101).

[0069] According to one embodiment, the display module (160) may display a user interface (UI) representing information related to a terrestrial network and / or a non-terrestrial network. For example, the UI representing information related to a terrestrial network and / or a non-terrestrial network may include at least one of a UI representing information related to a type of network (e.g., cellular communication (3G, 4G, or 5G), short-range communication (e.g., BT, or WIFI), or satellite communication), a type of network service provider (e.g., a satellite communication service provider (e.g., Iridium), an emergency service provider (ESP)), a network signal strength (e.g., signal strength bars, RSSI, or RSRP), an orientation of a communication device (satellite) included in the network (e.g., orientation, elevation angle, azimuth angle), presence information, and / or a network communication status (e.g., idle, transmit, or receive).

[0070] According to one embodiment, the display module (160) may display a UI representing services related to a terrestrial network and / or a non-terrestrial network.

[0071] According to one embodiment, the services related to the terrestrial network and / or the non-terrestrial network may include, for example, at least one of an emergency message transmission service, a messaging service, a voice call, a video call, a data communication service, a location-related service, and / or an indicator-related service.

[0072] According to one embodiment, the emergency message transmission service may include, but is not limited to, at least one of a service providing SOS service status information (e.g., indicating SOS service availability), a service providing government office information, a service providing emergency contact information, a service providing common phrases that minimize text input by the user, or a service using questionnaires to quickly convey emergency situations (e.g., a service providing options for the type of accident, the location of the injury, or medical information (e.g., age, gender, disease information, or medication information)).

[0073] In one embodiment, the messaging service may include, but is not limited to, at least one of a small message service (SMS), a multimedia messaging service (MMS), or a rich communication suite (RCS) message.

[0074] According to one embodiment, the data communication service may include services through various applications (e.g., web browsers) that provide data communication.

[0075] According to one embodiment, the location-related service may include, but is not limited to, at least one of longitude / latitude coordinates, location-related map information of the non-terrestrial communication device (220), navigation, or street view.

[0076] According to one embodiment, the UI examples are not limited to the examples mentioned, and may also be provided through other output devices (e.g., the audio output module (155) of FIG. 1).

[0077] 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 bands supported by the electronic device (101) may include, but are not limited to, a short-range wireless communication band (e.g., BT or WiFi), a terrestrial network (e.g., cellular network) communication band, and / or a non-terrestrial network band.

[0078] According to one embodiment, the electronic device (101) may support a frequency band (e.g., n255 or n256) associated with non-terrestrial network wireless communication. The electronic device (101) may perform non-terrestrial network wireless communication using the frequency band associated with non-terrestrial network wireless communication, but is not limited thereto. For example, the electronic device (101) may perform non-terrestrial network wireless communication using at least a portion of the frequency band associated with terrestrial network wireless communication.

[0079] According to one embodiment, the antenna module (197) can transmit or receive signals or power to or from an external source (e.g., an external electronic device).

[0080] According to one embodiment, the electronic device (101) 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). The at least one antenna supporting non-terrestrial wireless communication may include a dedicated antenna and / or a dual-purpose antenna. The dedicated antenna may include an antenna supporting a non-terrestrial network. The dual-purpose antenna may include an antenna supporting both a different type of network and a non-terrestrial network. For example, the electronic device (101) may communicate with at least one satellite (e.g., a GNSS satellite or a satellite for an emergency message service) using at least one non-terrestrial network dedicated antenna. For example, the dual-purpose antenna may include an antenna supporting a short-range communication network (e.g., a Bluetooth network, a WiFi network) and / or a terrestrial network (e.g., a long term evolution (LTE) network). The electronic device (101) may support a non-terrestrial network using a plurality of antennas among the antennas supporting a terrestrial network.

[0081] Hereinafter, in the present disclosure, a satellite is mainly mentioned as a non-terrestrial wireless communication device (220), and although it is mentioned that the satellite provides wireless communication using a specific radio access technology (RAT) (e.g., LTE) or a specific function (e.g., base station), this is only an example and the type is not limited.

[0082] FIG. 3 is a drawing for explaining the connection of an electronic device according to one embodiment.

[0083] According to one embodiment, the electronic device (101) may be located within the coverage (315) of the terrestrial wireless communication device (210) (hereinafter, referred to as terrestrial wireless communication coverage (315)) and / or within the coverage (325) of the non-terrestrial wireless communication device (220) (hereinafter, referred to as non-terrestrial wireless communication coverage (325)). The non-terrestrial wireless communication coverage (325) may be relatively larger (e.g., 50 times larger) than the terrestrial wireless communication coverage (315). For example, the non-terrestrial wireless communication coverage (325) may cover an area that the coverage (315) of the terrestrial wireless communication device (210) does not cover, and thus, the electronic device (101) may perform communication even in an area where terrestrial wireless communication is not supported.

[0084] According to one embodiment, the electronic device (101) can perform a cell scan within the terrestrial wireless communication coverage (315) and / or the non-terrestrial wireless communication coverage (325). As a result of performing the cell scan, the electronic device (101) can check the cell provided by the terrestrial wireless communication device (210) and / or the cell provided by the non-terrestrial wireless communication device (220). If there is a cell that satisfies the cell selection condition, the electronic device (101) can perform at least some of the operations for connecting to a network (e.g., a non-terrestrial network and / or a terrestrial network). Here, connecting to the network may include, but is not limited to, at least some of the preceding operations for registration to the network (e.g., camp on, or a connection procedure (e.g., a random access (RA) procedure)) and / or a registration operation to the network (e.g., attach, or registration). The electronic device (101) may perform at least some of the disconnection operations when disconnection from a network is required (e.g., moving to a different network). The disconnection operation from the network may include at least some of the following operations: detaching from the network, disconnecting the connection, and / or declaring a radio link failure (RLF), but is not limited to the listed operations. Meanwhile, those skilled in the art will understand that the electronic device (101) may also perform the connection based on a method specific to an operator (e.g., Iridium) other than the method defined in 3GPP.

[0085] According to one embodiment, the electronic device (101) may perform at least some of the following operations: cell scanning, disconnecting from a network, and / or connecting to a network, depending on movement (330, 335).

[0086] According to one embodiment, when the electronic device (101) is located within the terrestrial communication coverage (315) included in the non-terrestrial wireless communication coverage (325) or is located in the boundary area of ​​the terrestrial communication coverage (315), the electronic device (101) may perform access to the terrestrial network and / or the non-terrestrial network based on a policy (e.g., priority policy) of the electronic device (101).

[0087] FIG. 4 is a drawing for explaining a non-terrestrial network system (400) according to one embodiment.

[0088] Referring to FIG. 4, the non-terrestrial network system (400) may include a non-terrestrial wireless communication device (220), a radio unit (415), a packet core (430), and / or a PDN (440).

[0089] According to one embodiment, the non-terrestrial network system (400) may be implemented in a regenerative manner, for example. When implemented in a regenerative manner, at least one non-terrestrial wireless communication device (220) may include a base station (e.g., an eNode B). The non-terrestrial network system (400) may be implemented in a bent-pipe manner, for example. The bent-pipe manner may include a passive relay method that performs frequency conversion and power amplification on a received signal. When the non-terrestrial network system (400) is implemented in a bent-pipe manner, at least one non-terrestrial wireless communication device (220) may include a relay that converts (e.g., amplifies) and transmits a signal. The implementation manner of the non-terrestrial network system (400) and the role of the non-terrestrial wireless communication device (220) described in FIG. 4 are merely examples and are not limited thereto.

[0090] According to one embodiment, the non-terrestrial wireless communication device (220) may include at least one satellite. The non-terrestrial wireless communication device (220) may perform communication with the electronic device (101) using, for example, a terrestrial network (e.g., a cellular network) band and / or a non-terrestrial network band. The terrestrial network band may be, for example, an operating band supported by long term evolution (LTE) and / or new radio (NR), but is not limited thereto. The non-terrestrial network band may include, but is not limited to, a band defined by 3GPP (e.g., n255 and / or n256 bands).

[0091] According to one embodiment, at least one radio unit (415) may receive a signal from a non-terrestrial wireless communication device (220) and transmit it to a packet core (430). The radio unit (415) and the non-terrestrial wireless communication device (220) may communicate using, for example, a non-terrestrial network band. The non-terrestrial network band may be different from the terrestrial network band, but may be set to be the same in some cases.

[0092] According to one embodiment, at least one packet core (430) can transmit and receive data associated with the electronic device (101) using the radio unit (415). Accordingly, the packet core (430) can process the data associated with the electronic device (101) and transmit it to a packet data network (PDN) (440) (e.g., the Internet). The packet core (415) can include, for example, at least a portion of an evolved packet core (EPC) and / or a 5G core (5GC), but is not limited thereto. The packet core (430) can include a packet core associated with a non-terrestrial wireless communication device (220) operator and / or a packet core associated with a mobile network operator (MNO). The packet core (430) can be additionally connected to a public switched telephone network (PSTN) (not shown) to transmit and receive data associated with the electronic device (101).

[0093] FIG. 5A is a flowchart for explaining an operating method of an electronic device according to one embodiment.

[0094] A sending device (501) (e.g., but not limited to, the electronic device (101) of FIG. 1) can transmit a message to a non-terrestrial network (520). While the non-terrestrial network (520) is illustrated as including a non-terrestrial wireless communication device (220), a radio unit (415), and / or a packet core (430), those skilled in the art will appreciate that the components of the non-terrestrial network (520) are not limited. The message can be, for example, an SMS (short message service)-based message. The “From” field of the message can include a first mobile station international subscriber directory number (MSISDN) for transmission, for example, +82-10-5222-8228. The “To” field of the message can include a second MSISDN for reception, for example, +82-10-9530-6128. The “Body” field of the message may contain a message entered by the user based on the sending device (501), for example, “I am Alice.”

[0095] A non-terrestrial network (520) can provide a message to a short message service center (SMSC) (511). Here, the operator of the non-terrestrial network (520) and the operator of the SMSC (511) (e.g., MNO: mobile network operator) may be different. The message that the non-terrestrial network (520) provides to the SMSC (511) may be substantially the same as the received message, but there is no limitation. The SMSC (511) can provide the message to a receiving device (502). The “From” field of the message provided to the receiving device (502) may include a first MSISDN for transmission, for example, +82-10-5222-8228. The “To” field of the message may include a second MSISDN for reception, for example, +82-10-9530-6128. The “Body” field of the message may include a message entered by the user based on the sending device (501), for example, “I am Alice.” The SMSC (511) may be implemented by a single mobile network operator (MNO). For example, if the first MSISDN (e.g., +82-10-5222-8228) included in the “From” field and the second MSISDN (e.g., +82-10-9530-6128) included in the “To” field are both numbers subscribed to a single MNO, the message may be provided through an SMSC (511) implemented by a single MNO. Alternatively, the SMSC (511) may be implemented by multiple MNOs.For example, if the first MSISDN (e.g., +82-10-5222-8228) included in the “From” field and the second MSISDN (e.g., +82-10-9530-6128) included in the “To” field are numbers subscribed to different MNOs, the message may first be delivered to the SMSC of the MNO corresponding to the first MSISDN (e.g., +82-10-5222-8228) and then provided to the receiving device (502) through the SMSC of the MNO corresponding to the second MSISDN (e.g., +82-10-9530-6128), but there is no limitation on the order. As described above, in this example, the “From” field of the message may include the first MSISDN (e.g., +82-10-5222-8228), and even if conversion of the first MSISDN (e.g., +82-10-5222-8228) is not performed, the message may be provided from the sending device (501) to the receiving device (502). Meanwhile, the user of the receiving device (502) may, after receiving the message, operate the receiving device (502) to transmit a reply thereto. In some cases, the provision of the message for the reply from the receiving device (502) to the sending device (501) via the non-terrestrial network (430) may fail, which will be described with reference to FIG. 5B.

[0096] FIG. 5b is a flowchart illustrating an operating method of an electronic device according to one embodiment.

[0097] A receiving device (502) (e.g., but not limited to, the electronic device (101) of FIG. 1) may transmit a message to an SMSC (511). The “From” field of the message may include a second MSISDN for transmission, for example, +82-10-9530-6128. The “To” field of the message may include a first MSISDN for reception, for example, +82-10-5222-8228. The “Body” field of the message may include a message entered by a user based on the receiving device (502), for example, “I am Bob.” For example, a user may operate the receiving device (502) to send a reply based on a first MSISDN (e.g., +82-10-5222-8228) included in a “From” field of a message provided to the receiving device (502) as described with reference to FIG. 5A, such that the “To” field of the message may include the first MSISDN for reception, e.g., +82-10-5222-8228. The message may be provided to an SMSC of an MNO corresponding to the first MSISDN.

[0098] Meanwhile, the sending device (501) may be in a state where communication can be performed only through the satellite network (520) and the network of the MNO of the sending device (501) may be in a state where connection is impossible. In this case, the SMSC of the MNO corresponding to the first MSISDN may determine that the sending device (501) is in a state where service is impossible (no-service). Accordingly, the SMSC of the MNO corresponding to the first MSISDN may no longer transmit messages (or may postpone transmission of messages). Accordingly, provision of messages may be refrained from (or postponed) until the sending device (501) connects to the network of the MNO of the sending device (501). As described above, when the sending device (501) transmits / receives a message through a non-terrestrial network (520), there is a possibility that the transmission of the message to the sending device (501) may fail (or be delayed).

[0099] FIG. 6A is a flowchart illustrating a method for providing a message according to one embodiment. The embodiment of FIG. 6A will be described with reference to FIG. 6B. FIG. 6B is a diagram illustrating a method for providing a message according to one embodiment.

[0100] Referring to FIGS. 6A and 6B together, according to one embodiment, an electronic device (510) (which may be, for example, but is not limited to, the server (108) of FIG. 1 ) may, in operation 601, receive a first message including a first MSISDN (611) and a second MSISDN (612) from a sending device (501) via a non-terrestrial network (520). The electronic device (510) may, for example, receive a message from the non-terrestrial network (520) or provide a message to the non-terrestrial network (520), and may thus be named a non-terrestrial network gateway, a non-terrestrial network server, a satellite gateway, or a satellite server, but is not limited in its name or implementation form. Although the electronic device (510) is illustrated as a single entity in the example of FIG. 6B, this is merely exemplary, and the electronic device (510) may be implemented as a single entity (e.g., a server device) or as multiple entities (e.g., multiple server devices for distributed computing, which may be physically and / or logically distinct entities), and there is no limitation on the form of implementation. For example, the electronic device (510) may include at least one processor. The at least one processor may include a CPU, a GPU, an NPU, an FPGA, an ASIC, and / or an SoC, and there is no limitation on the form of implementation. For example, the electronic device (510) may include at least one memory that stores at least one instruction. The at least one memory may include a volatile memory and / or a non-volatile memory, and there is no limitation on the form of implementation. At least one instruction, when executed by at least one processor, may cause the electronic device (510) to perform at least one operation (e.g., at least some of the operations performed by the electronic device (510) described herein).The electronic device (510) can be operatively connected to a non-terrestrial network (520), a Maap gateway (GW) (513), a Maap registry (515), and / or a rich communication service (RCS) application server (AS) (514), and can thus transmit / receive data.

[0101] For example, the first MSISDN (611) is an MSISDN for transmission and may be included in the “From” field of the first message provided from the sending device (501). The second MSISDN (612) is an MSISDN for reception and may be included in the “To” field of the first message provided from the sending device (501). The “Body” field may include message content (613). For example, the MSISDN may be implemented to include a CC (country code), a NDC (network destination code), and a SN (subscriber number), but there is no limitation on the form of implementation. The MSISDN may also be named, for example, a phone number, a contact number, or a number, but there is no limitation. For example, a message provided from a sending device (501) and a message provided to a receiving device (502) may be based on any one of the following schemes: SMS, MMS (multimedia messaging service), RCS, or a manufacturer-specific scheme (e.g., but not limited to, iMessage). For example, the electronic device (510) may convert the scheme of a message provided from the sending device (501) into another scheme and provide it, or may maintain the scheme of the message as is.

[0102] In operation 603, the electronic device (510) can check whether the receiving device (502) corresponding to the second MSISDN (612) is capable of using RCS. In one example, the electronic device (510) can inquire of the RCS AS (514) as to whether the receiving device (502) corresponding to the second MSISDN (612) is capable of using RCS. In response to receiving the inquiry, the RCS AS (514) can inquire whether the receiving device (502) corresponding to the second MSISDN (612) is capable of using RCS. For example, the RCS AS (514) can check whether the receiving device (502) corresponding to the second MSISDN (612) can use RCS based on whether the receiving device (502) corresponding to the second MSISDN (612) is registered with the RCS AS (514), but this is exemplary and there is no limitation on the verification method. The RCS AS (514) can transmit the verification result of whether the receiving device (502) corresponding to the second MSISDN (612) can use RCS to the electronic device (510). The electronic device (510) can check whether the receiving device (502) corresponding to the second MSISDN (612) can use RCS based on the verification result provided from the RCS AS (514). Meanwhile, depending on the implementation, the electronic device (510) may receive information on whether the receiving device (502) corresponding to the second MSISDN (612) is capable of using RCS from an entity other than the RCS AS (514). Alternatively, the electronic device (510) may verify whether the receiving device (502) corresponding to the second MSISDN (612) is capable of using RCS without any connection with another entity, and there is no limitation on the verification method.

[0103] In operation 605, the electronic device (510) may provide (or transmit) a second message including information (614) associated with an RCS-based chatbot (512) corresponding to the first MSISDN (611) for sending and a second MSISDN (612), based on the fact that the receiving device (502) is capable of using RCS. The “From” field of the second message may include information (614) associated with the chatbot (512) instead of the first MSISDN (611). Here, the chatbot (512) may be defined, for example, in an RCS-related standard of the global system for mobile communications association (GSMA) (for example, but not limited to, Rich Communication Suite 9.0 Advanced Communications Services and Client Specification Version 10.0). For example, a chatbot (512) may be an RCS-based service, the output of which may follow a conversational format, and may be software for interfacing with a user to simulate an intelligent human-based conversation, but this is exemplary and not limiting. The chatbot (512) may be generated, for example, for non-terrestrial network communication of the first MSISDN (611) (or its user). The process of generating the chatbot (512) will be described with reference to FIGS. 12A and 12B . For example, the electronic device (510) may store a chatbot (512) (or at least one piece of information corresponding to the chatbot (512)) corresponding to the first MSISDN (611) (or its user), and may also store a chatbot (or at least one piece of information corresponding to the chatbot) corresponding to another user. A chatbot (or at least one piece of information corresponding to the chatbot) can be registered in the Maap registry (515). The at least one piece of information corresponding to the chatbot can be, for example, a chatbot ID (identifier), but there is no limitation.Meanwhile, at least one piece of information corresponding to a chatbot, such as profile information, may include a first MSISDN (611), a website address associated with a service (e.g., a non-terrestrial network communication service), and / or an email address. At least one piece of information corresponding to a chatbot, such as a chatbot ID and / or profile information, may be registered in the Maap registry (515).

[0104] As described above, the electronic device (510) may provide a second message including information (614) associated with an RCS-based chatbot (512) and a second MSISDN (612) based on the fact that the receiving device (502) corresponding to the second MSISDN (612) for reception is capable of using RCS, to, for example, a Maap gateway (513). For example, the electronic device (101) may also convert the scheme of the message to RCS if the scheme of the message received via the non-terrestrial network (520) is SMS or SMS-based rather than RCS. For example, in the example of FIG. 6B, the “From” field of the second message may include a chatbot ID (e.g., bot_+82-10-5232-8228) as information (614) associated with the chatbot (512), the “To” field may include a second MSISDN (612), and the “Body” field may include message content (613). The Maap gateway (513) may provide the second message to the RCS AS (514). The RCS AS (513) may provide the second message to the receiving device (502).

[0105] The receiving device (502) can provide (or display, express, reproduce, or output) information related to the second message. The receiving device (502) can, for example, retrieve (or receive) profile information from the Maap registry (515) based on information (614) associated with the chatbot (512). For example, the receiving device (502) can confirm that the second message is associated with the chatbot (512), and can thus retrieve (or receive) profile information from the Maap registry (515). For example, during the session establishment process for sending and receiving messages with the chatbot (512), the receiving device (502) can confirm that the other party to the session establishment is the chatbot (512). For example, the receiving device (502) can confirm that the counterparty of the session establishment is a chatbot (512) based on information included in an invite message based on a session initiation protocol (SIP) for session establishment (for example, it can be a Boolean value of the chatbot role, but there is no limitation), but there is no limitation on the type and / or confirmation method of the message. For example, the receiving device (502) can also confirm that the entity that sent the message is a chatbot (512) based on information included in a message other than a message for session establishment. For example, the receiving device (502) can inquire about the RCS capability of the message sending entity to the RCS AS (510). The receiving device (502) can also confirm whether the message sending entity is a chatbot based on a response from the RCS AS (510). For example, the receiving device (502) may determine that the sending entity of the message is the chatbot (512) based on the fact that the format of the information included in the “From” field of the received message is not the MSISDN format, but the format of information associated with the chatbot (512) (e.g., chatbot ID).As described above, if the sending entity of the message is confirmed to be a chatbot, the receiving device (502) may receive profile information from the Maap registry (515) based on information (614) corresponding to the chatbot (512). The receiving device (502) may provide (or display, express, reproduce, or output) a screen for the received message based on information and / or profile information included in the second message.

[0106] FIG. 6c is an example of a screen for a received message according to one embodiment.

[0107] According to one embodiment, a receiving device (502) (e.g., but not limited to, the electronic device (101) of FIG. 1) can provide (or display, represent, reproduce, or output) a first screen (650). The first screen (650) can include, for example, an object (651) (e.g., but not limited to, a UI element, a UI object, an icon, text, a button, an image, a visual element, a visual component, an avatar, a thumbnail, a pop-up, an animation, a key, and / or a button). The object (651) can also be configured to cause the display of a second screen (660) when designated (or selected).

[0108] The first screen (650) may include, for example, a first MSISDN (652) corresponding to the sending device (501). For example, the receiving device (502) may provide the first MSISDN (652) received as profile information corresponding to the chatbot (512) from the Maap registry (515). The first screen (650) may include, for example, an object (653) corresponding to the message content included in the “Body” field of the second message. The object (653) may be implemented to include, for example, location information (654) of the sending device (501), but is not limited thereto. Meanwhile, as the object (651) is designated (or selected), the receiving device (502) may provide (or display, express, reproduce, or output) a second screen (660). The second screen (660) may include profile information. Profile information may include, but is not limited to, information related to a chatbot (512) (661), information about a name (662) corresponding to a first MSISDN, information about a first MSISDN (663), information about a website (664), and / or information about an email (665).

[0109] As described above, even if the receiving device (502) receives a message in which the “From” field is expressed as information (514) associated with a chatbot (512) (e.g., a chatbot ID), the receiving device (502) may receive and express profile information related to the chatbot (512) from the Maap registry (515), and accordingly, the first MSISDN (611) corresponding to the sending device (501) may be expressed. The user of the receiving device (502) may be able to confirm the first MSISDN (611) or the name corresponding to the first MSISDN (611), and may not misunderstand the message as a spam message. Meanwhile, the receiving device (502) providing profile information is merely exemplary. In another example, the receiving device (502) may be implemented so that information (514) associated with the chatbot (512) and message content (613), which are included in the second message, are expressed without profile information. Meanwhile, as described above, information (514) associated with the chatbot (512) (e.g., chatbot ID) may be included in the “From” field, and a reply with information (514) associated with the chatbot (512) (e.g., chatbot ID) may be possible, which will be described with reference to FIGS. 7A and 7B .

[0110] FIG. 7A is a flowchart illustrating a message provision method according to one embodiment. The embodiment of FIG. 7A will be described with reference to FIG. 7B. FIG. 7B is a diagram illustrating a message provision method according to one embodiment.

[0111] Referring to FIGS. 7A and 7B together, according to one embodiment, an electronic device (510) (e.g., but not limited to, the server (108) of FIG. 1 ) may, in operation 701, receive a message from a receiving device (502) that includes information (614) associated with a chatbot (512) and a second MSISDN (612). As in FIG. 7B , the receiving device (502) may transmit a message, for example, as a reply to the received message. The “From” field of the message may include the second MSISDN (612) (e.g., +82-10-9530-6128). The “To” field of the message may include information (614) associated with the chatbot (512). The “Body” field of the message may include message content (615). A message from a receiving device (502) can be provided to an electronic device (510) via an RCS AS (514) and a Maap gateway (513), but there is no limitation on the path and / or method of provision. Since the “To” field of the message includes information (614) related to a chatbot (512), the RCS AS (514) can provide the message to the chatbot (512) (or the electronic device (510) executing the chatbot (512). Accordingly, the electronic device (510) executing the chatbot (512) can receive the message. The electronic device (510), as a non-terrestrial network gateway, can manage the connection status of electronic devices connected to a non-terrestrial network (520), for example, the connection status of the sending device (501) to the satellite network (520). For example, the electronic device (510) can check whether the sending device (501) is connected to the satellite network (520) and can provide a message to the sending device (501) connected to the satellite network (520).Accordingly, the electronic device (510) may, in operation 703, provide a message including the first MSISDN (611) and the second MSISDN (612) to the sending device (501) corresponding to the first MSISDN (611) corresponding to the information (614) associated with the chatbot (512) via the non-terrestrial network (520). The “From” field of the message may include the second MSISDN (612) (e.g., +82-10-9530-6128). The “To” field of the message may include the first MSISDN (611) in place of the information (614) associated with the chatbot (512). The “Body” field of the message may include message content (615). Since the electronic device (510) manages the correspondence between the information (614) associated with the chatbot (512) and the first MSISDN (611), the information (614) associated with the chatbot (512) in the “To” field of the message can be replaced with the first MSISDN (611) based on the correspondence. Accordingly, the sending device (501) can receive the message from the electronic device (510) via the non-terrestrial network (520). As described above, even if the receiving device (502) transmits the message by including the information (614) associated with the chatbot (512) in the “To” field, the message can be provided to the sending device (501) as the information in the “To” field is replaced with the first MSISDN (611) by the electronic device (510). Accordingly, a reply based on information (614) associated with the chatbot (512) may be possible.

[0112] FIG. 8A is a flowchart illustrating a method for providing a message according to one embodiment. The embodiment of FIG. 8A will be described with reference to FIG. 8B. FIG. 8B is a diagram illustrating a method for providing a message according to one embodiment.

[0113] Referring to FIGS. 8A and 8B together, according to one embodiment, an electronic device (510) (e.g., but not limited to, the server (108) of FIG. 1) may, in operation 801, receive a first message including a first MSISDN (611) and a second MSISDN (612) from a sending device (501) via a non-terrestrial network (520). For example, the first MSISDN (611) is an MSISDN for transmission and may be included in a “From” field of the first message provided from the sending device (501). The second MSISDN (612) is an MSISDN for reception and may be included in a “To” field of the first message provided from the sending device (501). The “Body” field may include message content (613). The electronic device (510) can, in operation 803, check whether the receiving device (502) corresponding to the second MSISDN (612) is capable of using RCS.

[0114] Based on the fact that the receiving device (502) corresponding to the second MSISDN (612) is RCS-capable (operation 803 - example), as described with reference to FIGS. 6A and 6B, in operation 805, the electronic device (510) can provide (or transmit) a second message including information (614) associated with an RCS-based chatbot (512) corresponding to the first MSISDN (611) for sending and the second MSISDN (612), based on the fact that the receiving device (502) is RCS-capable. Based on the fact that the receiving device (502) corresponding to the second MSISDN (612) is not confirmed to be RCS-capable (Action 803-No), the electronic device (510) may, in operation 807, provide a third message including the third MSISDN (618) corresponding to the first MSISDN (611) and the second MSISDN (612), as in FIG. 8B . The “From” field of the third message may include the third MSISDN (618) corresponding to the first MSISDN (611) (or information (614) corresponding to the chatbot (512)) instead of the first MSISDN (611). As described above, the electronic device (510) may create, execute, and / or manage the chatbot (512) corresponding to the first MSISDN (614). The electronic device (510) can manage information (614) of a chatbot (512) corresponding to the first MSISDN (614). The electronic device (510) can map a third MSISDN (618) to the first MSISDN (614) (or information (614) of the chatbot (512)) based on the fact that the receiving device (502) corresponding to the second MSISDN (612) is not confirmed to be capable of using RCS.The third MSISDN (618) can be used by being mapped to the first MSISDN (614) (or, information (614) of the chatbot (512)) for a certain period of time, and can be named a virtual MSISDN, a disposable MSISDN, or a temporary MSISDN, but there is no limitation, and it can be used by being mapped to the first MSISDN (614) (or, information (614) of the chatbot (512)) permanently rather than for a certain period of time. The electronic device (510) can provide the mapping relationship between the first MSISDN (614) (or, information (614) of the chatbot (512)) and the third MSISDN (623) to the Maap registry (515). For example, the electronic device (510) may register a third MSISDN (623) with the Maap registry (515) as part of the profile information corresponding to the chatbot (512), but this is exemplary and there is no limitation on how the third MSISDN (623) is processed, stored, and / or managed.

[0115] As described above, the electronic device (510) may provide a third message including the third MSISDN (618) and the second MSISDN (612) to, for example, an SMSC (511) based on the fact that the receiving device (502) corresponding to the second MSISDN (612) for reception does not use RCS. For example, the electronic device (101) may convert the scheme of the message to SMS or MMS rather than RCS when the scheme of the message received via the non-terrestrial network (520) is RCS. The SMSC (511) may provide the third message to the receiving device (502).

[0116] The receiving device (502) can provide (or display, represent, reproduce, or output) information related to the third message. The receiving device (502) can, for example, retrieve (or receive) profile information from the Maap registry (515) based on information (614) associated with the chatbot (512). For example, the receiving device (502) can check whether the third MSISDN (618) included in the third message is the MSISDN of the query target. For example, the receiving device (502) can obtain and store information including the MSISDN of the query target, for example, from the RCS AS (514) (or the electronic device (510)). For example, the receiving device (502) can receive the MSISDN of the query target as RCS configuration information, but there is no limitation on the manner in which the MSISDN of the query target is provided. For example, the CS AS (514) (or the electronic device (510)) can provide the client with at least one MSISDN to be queried, including the third MSISDN (618). The receiving device (502) can, for example, check whether the MSISDN included in the “From” field of the received message (e.g., the third MSISDN (618)) corresponds to any one of the MSISDNs to be queried. If the MSISDN included in the “From” field (e.g., the third MSISDN (618)) corresponds to any one of the MSISDNs to be queried, the receiving device (502) can search for information about the corresponding MSISDN (e.g., the third MSISDN (618)) in the Maap registry (515). For example, the receiving device (502) may provide a request for information corresponding to the MSISDN (e.g., the third MSISDN (618)) included in the “From” field to the Maap registry (515), but there is no limitation.Alternatively, the receiving device (502) may first request RCS-related information corresponding to the MSISDN (e.g., the third MSISDN (618)) included in the “From” field to the RCS AS (514). The receiving device (502) may receive, from the RCS AS (514), information (614) related to the chatbot (512) corresponding to the request. The receiving device (502) may then provide a request for information corresponding to the information (614) related to the chatbot (512) to the Maap registry (515). The Maap registry (515), in response to the request as described above, may provide profile information corresponding to the third MSISDN (618) (or information (514) corresponding to the chatbot (512)) to the receiving device (502). The receiving device (502) can provide (or display, express, reproduce, or output) a screen for the received message based on information and / or profile information included in the second message.

[0117] FIG. 8c is an example of a screen for a received message according to one embodiment.

[0118] According to one embodiment, a receiving device (502) (e.g., but not limited to, the electronic device (101) of FIG. 1) can provide (or display, represent, reproduce, or output) a first screen (850). The first screen (850) can include, for example, an object (651) (e.g., but not limited to, a UI element, a UI object, an icon, text, a button, an image, a visual element, a visual component, an avatar, a thumbnail, a pop-up, an animation, a key, and / or a button). The first screen (850) can include, for example, a third MSISDN (851). Meanwhile, as an example, the receiving device (502) may provide the received first MSISDN (652) as profile information corresponding to the chatbot (512) from the Maap registry (515) by replacing the third MSISDN (851) or together with the third MSISDN (851). The first screen (850) may include, for example, an object (653) corresponding to the message content included in the “Body” field of the second message. The object (653) may be implemented to include, for example, location information (654) of the sending device (501), but there is no limitation. Meanwhile, as the object (651) is designated (or selected), the receiving device (502) may provide (or display, express, reproduce, or output) the second screen (860). The second screen (860) may include profile information. Profile information may include, but is not limited to, information related to a chatbot (512) (661), information corresponding to a third MSISDN (852), information about a name corresponding to a first MSISDN (662), information about a first MSISDN (663), information about a website (664), and / or information about an email (665).

[0119] As described above, even if the receiving device (502) receives a message in which the “From” field is expressed as a virtual MSISDN, the receiving device (502) can receive and express profile information related to the corresponding MSISDN (or chatbot (512)) from the Maap registry (515), and accordingly, the first MSISDN (611) corresponding to the sending device (501) can be expressed. The user of the receiving device (502) can confirm the first MSISDN (611) or the name corresponding to the first MSISDN (611), and thus may not misunderstand the message as a spam message. Meanwhile, the receiving device (502) providing the profile information is merely exemplary. In another example, the receiving device (502) may be implemented so that the third MSISDN (618) and the message content (613), which are information included in the third message, are expressed without the profile information. Meanwhile, as described above, the “From” field may include a third MSISDN (618), and a reply to the third MSISDN (618) may be possible, which will be described with reference to FIGS. 10a and 10b.

[0120] Figure 8d is a flowchart for explaining the operation method of the receiving device.

[0121] According to one embodiment, a receiving device (502) (e.g., the electronic device (101) of FIG. 1) may receive a first message including a first MSISDN for transmission and a second MSISDN corresponding to the receiving device (502). In operation 893, the receiving device (502) may obtain at least one piece of information registered in association with the chatbot corresponding to the first MSISDN based on confirming that the first MSISDN is an MSISDN associated with the chatbot. For example, the receiving device (502) may pre-store at least one MSISDN designated as a query target. The receiving device (502) may obtain at least one piece of information registered in association with the chatbot corresponding to the first MSISDN based on confirming that the first MSISDN included in the message is one of the at least one MSISDN designated as a query target, but this is exemplary and not limiting. The receiving device (502) can provide the contents of the first message and at least one piece of information obtained in operation 895.

[0122] Figure 9a is a flowchart illustrating a method for providing a message according to one embodiment.

[0123] According to one embodiment, an electronic device (510) (e.g., but not limited to, the server (108) of FIG. 1) may, in operation 901, receive a message from a sending device over a non-terrestrial network, the message including a first MSISDN for sending and a second MSISDN for receiving. In operation 903, the electronic device (510) may determine that a receiving device corresponding to the second MSISDN is unable to use RCS. In operation 905, the electronic device (510) may map (or correspond to, or associate) the first MSISDN with a third MSISDN. The electronic device (510) may secure at least one MSISDN in advance for providing a message to a receiving device that is unable to use RCS. The electronic device (510) may map the first MSISDN to any one of the secured at least one MSISDN. The electronic device (510) may map the third MSISDN to the first MSISDN (or information associated with a chatbot corresponding to the first MSISDN) and register information about the mapping relationship (or correspondence relationship or association relationship) in the Maap registry (515). Information about at least one MSISDN may be provided to the receiving device, for example, via (or directly) the RCS AS (514), and the receiving device may manage it as the MSISDN of the query target. The electronic device (501), in operation 907, may provide a message including the third MSISDN and the second MSISDN to the receiving device (502). As described above, the receiving device (502) may check whether the third MSISDN included in the “From” field of the message corresponds to any one of at least one MSISDN of the query target obtained in advance.If the third MSISSDN corresponds to at least one of the MSISDNs of the previously acquired query target, the receiving device (502) may receive and provide profile information corresponding to the third MSISSDN (or information associated with the chatbot corresponding to the third MSISSDN) from the Maap registry (515).

[0124] Figure 9b is a flowchart illustrating a method for providing a message according to one embodiment.

[0125] According to one embodiment, the electronic device (510) (e.g., but not limited to, the server (108) of FIG. 1) may, in operation 911, receive a message from a sending device over a non-terrestrial network, the message including a first MSISDN for sending and a second MSISDN for receiving. In operation 913, the electronic device (510) may determine that a receiving device corresponding to the second MSISDN is not RCS-capable. In operation 915, the electronic device (510) may map (or correspond to, or associate) the first MSISDN with a third MSISDN. The electronic device (510) may, for example, start a timer based on the mapping (or correspondence to, or association) of the first MSISDN with the third MSISDN. In operation 917, the electronic device (510) may determine whether the timer has expired. If the timer expires (917-Yes), the electronic device (510) may, in operation 919, release the mapping (or correspondence, or association) between the first MSISDN and the third MSISDN. Accordingly, the third MSISDN may be transitioned to a state where it is available for another MSISDN. Meanwhile, the expiration of the timer is only an example of releasing the mapping (or correspondence, or association) between the first MSISDN and the third MSISDN, and there is no limitation on the trigger for release. For example, the electronic device (510) may release the mapping (or correspondence, or association) between the first MSISDN and the third MSISDN based on the release of the satellite network (520) connection of the transmitting device (501) corresponding to the first MSISDN, and there is no limitation on the trigger. If the timer has not expired (917-No), the electronic device (510) may, in operation 921, determine whether a timer update event is confirmed. The timer update event may be, for example, but is not limited to, receiving a message from the receiving device (502) that includes a third MSISDN in the “From” field.If a timer update event is confirmed (921-Yes), the electronic device (510) can update the timer in operation 923. After updating the timer, the electronic device (510) can check whether the timer has expired in operation 917. If the timer update event is not confirmed (921-No), the electronic device (510) can check whether the timer has expired in operation 917. As described above, the electronic device (510) can, for example, unmap an MSISDN to a specific MSISDN based on timer expiration, and thus, the unmapped MSISDN can be used for non-terrestrial network communication of the MSISDN for other outgoing calls.

[0126] FIG. 10A is a flowchart illustrating a method for providing a message according to one embodiment. The embodiment of FIG. 10A will be described with reference to FIG. 10B. FIG. 10B is a diagram illustrating a method for providing a message according to one embodiment.

[0127] Referring to FIGS. 10A and 10B together, according to one embodiment, an electronic device (510) (e.g., but not limited to, the server (108) of FIG. 1 ) may, in operation 1001, receive a message from a receiving device (502) that includes a second MSISDN (612) and a third MSISDN (618). As in FIG. 10B , the receiving device (502) may transmit a message, for example, as a reply to the received message. The “From” field of the message may include the second MSISDN (612) (e.g., +82-10-9530-6128). The “To” field of the message may include the third MSISDN (618). The “Body” field of the message may include message content (615). A message from a receiving device (502) can be provided to an electronic device (510) via an RCS AS (514) and a Maap gateway (513), but there is no limitation on the provision path and / or method. Since the third MSISDN (618) is included in the “To” field of the message, the RCS AS (514) can provide the message to the electronic device (510) corresponding to the third MSISDN (618). Accordingly, the electronic device (510) can receive the message. The electronic device (510), as a non-terrestrial network gateway, can manage the connection status of electronic devices connected to a non-terrestrial network (520), for example, the sending device (501). Accordingly, the electronic device (510) may, in operation 1003, provide a message including the first MSISDN (611) and the second MSISDN (612) to the originating device (501) corresponding to the first MSISDN (611) corresponding to the third MSISDN (618) via the non-terrestrial network (520). The “From” field of the message may include the second MSISDN (612) (e.g., +82-10-9530-6128).The “To” field of the message may include the first MSISDN (611) in place of the third MSISDN (618). The “Body” field of the message may include message content (615). Since the electronic device (510) manages the correspondence between the third MSISDN (618) and the first MSISDN (611), the third MSISDN (618) in the “To” field of the message may be replaced with the first MSISDN (611) based on the correspondence. Accordingly, the sending device (501) may receive a message from the electronic device (510) via the non-terrestrial network (520). As described above, even if the receiving device (502) transmits a message by including the third MSISDN (618) in the “To” field, the message can be provided to the sending device (501) as the information in the “To” field is replaced with the first MSISDN (611) by the electronic device (510). Accordingly, a reply based on the third MSISDN (618) can be possible.

[0128] Fig. 11 is a flowchart illustrating a method for providing a message according to one embodiment.

[0129] According to one embodiment, the electronic device (510) (which may be, for example, but is not limited to, the server (108) of FIG. 1 ) may, in operation 1101, receive a first message based on a first type scheme including a first MSISDN and a second MSISDN from a sending device over a non-terrestrial network. The first type scheme may be, for example, but is not limited to, an IMS-based legacy scheme such as SMS or MMS. The electronic device (510) may, in operation 1103, determine whether a receiving device corresponding to the second MSISDN is capable of using a second type scheme. For example, but is not limited to, the second type scheme may be RCS or a manufacturer-specific scheme (which may be, for example, but is not limited to, iMessage). If the receiving device corresponding to the second MSISDN is confirmed to be capable of using the second type scheme (operation 1103 - Yes), the electronic device (101) may, in operation 1105, provide a second message of the second type scheme, including information based on the second type scheme corresponding to the first MSISDN and the second MSISDN. For example, the information based on the second type scheme may be information associated with an RCS-based chatbot, but is not limited thereto. The electronic device (101) may also convert the scheme of the first message from the first type scheme to the second type scheme. If the receiving device corresponding to the second MSISDN is not confirmed to be capable of using the second type scheme (operation 1103 - No), the electronic device (101) may, in operation 1107, provide a third message of the first type scheme, which includes a third MSISDN corresponding to the first MSISDN and a second MSISDN. Meanwhile, the receiving device may receive the second message and, using information based on the second type scheme, obtain and provide information corresponding to the first MSISDN. The third MSISDN may be mapped to the first MSISDN for a certain period of time, for example.Meanwhile, the receiving device may receive the third message and obtain and provide information corresponding to the first MSISDN using the third MSISDN.

[0130] Figure 12a is a diagram illustrating the creation of a chatbot according to one embodiment. The embodiment of Figure 12a will be described with reference to Figure 12b. Figure 12b is a diagram illustrating a screen provided according to one embodiment.

[0131] According to one embodiment, a sending device (501) corresponding to the first MSISDN (for example, but not limited to, the electronic device (101) of FIG. 1) may execute a messaging application (1201). The messaging application (1201) may, for example, support a function for creating a chatbot, but this is exemplary, and the type of application that supports the function for creating a chatbot is not limited. The sending device (501) may, for example, provide a chatbot creation request to the electronic device (510) based on a chatbot creation request input through the messaging application (1201). Meanwhile, the request for chatbot creation by the sending device (501) is exemplary, and those skilled in the art will understand that, in addition to the sending device (501), a request for chatbot creation may be made by a device (for example, but not limited to, a personal computer) on which authentication for the first MSISDN has been performed. For example, referring to FIG. 12B, the sending device (501) may provide (or display, express, reproduce, or output) a first screen (1210). The first screen (1210) may include a guide text for creating a chatbot, and may include an object (1211) set to cause the creation of a chatbot and an object (1212) for termination. If it is confirmed that the object (1211) is designated (or selected), the sending device (501) may provide a second screen (1220) for entering profile information. The second screen (1220) may include an object (1221) for entering an MSISDN, an object (1222) for entering a website address, an object (1223) for entering an email address, an object (1224) for entering a profile picture, an object (1225) for registering a message, and / or an object (1226) for storing profile information, but there is no limitation on the type and / or number of profile information. A chatbot creation request may include, for example, entered profile information.

[0132] The electronic device (510) may create a chatbot (512) corresponding to the first MSISDN based on a chatbot creation request. The electronic device (510) may register information and / or profile information related to the chatbot (512) in the Maap registry (515) based on the creation of the chatbot (512). The Maap registry (515) may perform user authentication with an MNO device (e.g., a server) (1202). If the user authentication is successful, the Maap registry (515) may issue a token (e.g., ACCESS_TOKEN) corresponding to the chatbot and provide it to the electronic device (510). The electronic device (510) may issue an authentication key based on the token and provide it to the sending device (501) that requested the creation of the chatbot (512). The sending device (510) may transmit an authentication key when transmitting a message via the satellite network (520). For example, the sending device (510) may transmit the authentication key by including it in the message, or may transmit the authentication key separately from the message, and there is no limitation on the method of transmitting the authentication key. The electronic device (510) may perform an authentication procedure (e.g., an authentication procedure based on the OAuth 2.0 method, but there is no limitation) based on the received authentication key and the authentication key stored corresponding to the first MSISDN. If the authentication procedure is successful, the electronic device (510) may process the message provided from the sending device (501) based on the method described above. If the authentication procedure fails, the electronic device (510) may refrain from processing the message.

[0133] FIG. 13a and FIG. 13b are flowcharts illustrating a method of providing a message according to one embodiment.

[0134] According to one embodiment, an electronic device (510) (e.g., but not limited to, the server (108) of FIG. 1) may receive a message from a sending device (501) via a satellite network (520). For example, a “From” field of the message may include a first MSISDN for transmission, for example, +82-10-5222-8228. A “To” field of the message may include a second MSISDN for reception, for example, +82-10-9530-6128. A “Body” field of the message may include message content (e.g., “I am Alice”). The electronic device (510) may provide the message received via the satellite network (510) to a mobile virtual network operator (MVNO) (519) for satellite services. The sending device (501) can register as a roaming state with the satellite network (520) and / or SMSC (511) through the MVNO (519). Accordingly, the MVNO (519) can provide the received message to the SMSC (511). The SMSC (511) can provide the received message to the receiving device (502) corresponding to the second MSISDN. Meanwhile, the receiving device (502) can provide the message to the SMSC (511) as in Fig. 13b. The “From” field of the message can include the second MSISDN for transmission, for example, +82-10-9530-6128. The “To” field of the message can include the first MSISDN for reception, for example, +82-10-5222-8228. The “Body” field of the message may include the message content (e.g., “I am Bob”). The SMSC (511) may send a reply message to the MVNO (519). The MVNO (519) may send the message to the electronic device (510). The electronic device (510) may send the message to the sending device (501) via the satellite network (520).

[0135] FIG. 14a and FIG. 14b are flowcharts illustrating a method of providing a message according to one embodiment.

[0136] According to one embodiment, an electronic device (510) (e.g., but not limited to, server (108) of FIG. 1) may receive a message from a sending device (501) via a satellite network (520). For example, a “From” field of the message may include a first MSISDN for transmission, for example, +82-10-5222-8228. A “To” field of the message may include a second MSISDN for reception, for example, +82-10-9530-6128. A “Body” field of the message may include message content (e.g., “I am Alice”). The electronic device (510) may map a third MSISDN (e.g., +82-31-301-4139) to the first MSISDN included in the “From” field of the message received via the satellite network (510). The electronic device (510) can replace the first MSISDN (e.g., +82-10-5222-8228) in the “From” field with a third MSISDN (e.g., +82-31-301-4139). The electronic device (510) can provide a message with the information in the “From” field replaced to the SMSC (511). The SMSC (511) can provide the message with the information in the “From” field replaced to the receiving device (502). Meanwhile, the receiving device (502) can provide the message to the SMSC (511), as in FIG. 14b. The “From” field of the message can include a second MSISDN for transmission, for example, +82-10-9530-6128. The "To" field of the message may include a third-party MSISDN for receiving, for example, +82-31-301-4139. The "Body" field of the message may include the message content (for example, "I am Bob"). The SMSC (511) may send a reply message to the electronic device (510).The electronic device (510) can replace the third MSISDN (e.g., +82-31-301-4139) in the “To” field of the message with the mapped first MSISDN (e.g., +82-10-5222-8228). The electronic device (510) can provide the message with the information in the “To” field replaced to the sending device (501).

[0137] According to one embodiment, a method for providing a message is provided. The method may include receiving, from a sending device (501) over a non-terrestrial network, a first message comprising a first MSISDN for sending and a second MSISDN for receiving. The method may include determining whether a receiving device (502) corresponding to the second MSISDN is RCS-enabled. Based on the RCS-enabled capability of the receiving device (502), the method may include providing a second message comprising information associated with an RCS-based chatbot for sending corresponding to the first MSISDN that replaces the first MSISDN and the second MSISDN for receiving.

[0138] According to one embodiment, the method may include providing a third message including a third MSISDN for sending and the second MSISDN for receiving, based on the receiving device (502) being unable to utilize the RCS.

[0139] According to one embodiment, the method may include receiving, from the receiving device (502), a fourth message comprising the third MSISDN mapped to the first MSISDN for reception and the second MSISDN for transmission. The method may include providing, to the sending device (501) corresponding to the first MSISDN mapped to the third MSISDN, a fifth message comprising the first MSISDN for reception and the second MSISDN for transmission, via the non-terrestrial network.

[0140] According to one embodiment, the method may include mapping the third MSISDN to the first MSISDN based on the receiving device (502) being unable to utilize the RCS.

[0141] According to one embodiment, the method may include an operation of unmapping the third MSISDN to the first MSISDN after a specified period of time has elapsed since mapping the third MSISDN to the first MSISDN.

[0142] According to one embodiment, the method may include receiving, from the receiving device (502), a sixth message comprising information associated with an RCS-based chatbot corresponding to the first MSISDN for reception and a second MSISDN for transmission. The method may include providing, to the sending device (501) corresponding to the first MSISDN corresponding to the information associated with the RCS-based chatbot, a seventh message comprising the first MSISDN for reception and the second MSISDN for transmission, via the non-terrestrial network.

[0143] According to one embodiment, the method may include converting the first message based on SMS or MMS into the second message based on RCS.

[0144] In one embodiment, the method may include receiving a request to create an RCS-based chatbot corresponding to the first MSISDN. The method may include creating an RCS-based chatbot corresponding to the first MSISDN based on the creation request. The method may include providing a request to register information associated with the chatbot in the MAPI registry.

[0145] In one embodiment, the method may include receiving a token corresponding to the RCS-based chatbot from the Maap registry. Based on the receipt of the token, the method may include providing a first authentication key corresponding to the RCS-based chatbot to the sending device (501).

[0146] According to one embodiment, the method may include an operation of performing authentication based on the second authentication key provided from the sending device (501) and the first authentication key. The operation of providing the second message may include an operation of transmitting the second message based on the success of the authentication.

[0147] According to one embodiment, the operation of checking whether the receiving device (502) corresponding to the second MSISDN is capable of using RCS may include an operation of checking whether the receiving device (502) is capable of using RCS based on information provided from a server of an RCS to which the receiving device (502) is registered.

[0148] According to one embodiment, a storage medium storing at least one computer-readable instruction may be provided. The at least one instruction, when executed by a processor of an electronic device (108; 510), may cause the electronic device (108; 510) to perform at least one operation. The at least one operation may include receiving, from a sending device (501) via a non-terrestrial network, a first message including a first MSISDN for sending and a second MSISDN for receiving. The at least one operation may include checking whether a receiving device (502) corresponding to the second MSISDN is RCS-enabled. The at least one action may include providing a second message including information associated with an RCS-based chatbot for transmission corresponding to the first MSISDN replacing the first MSISDN and the second MSISDN for reception, based on the availability of the RCS by the receiving device (502).

[0149] According to one embodiment, the at least one method may include providing a third message including a third MSISDN for sending and the second MSISDN for receiving, based on the receiving device (502) being unable to utilize the RCS.

[0150] According to one embodiment, the at least one method may include receiving, from the receiving device (502), a fourth message comprising the third MSISDN mapped to the first MSISDN for reception and the second MSISDN for transmission. The at least one method may include providing, to the sending device (501) corresponding to the first MSISDN mapped to the third MSISDN, a fifth message comprising the first MSISDN for reception and the second MSISDN for transmission, via the non-terrestrial network.

[0151] According to one embodiment, the at least one method may include mapping the third MSISDN to the first MSISDN based on the receiving device (502) being unable to utilize the RCS.

[0152] According to one embodiment, the at least one method may include an operation of unmapping the third MSISDN to the first MSISDN after a specified period of time has elapsed since mapping the third MSISDN to the first MSISDN.

[0153] According to one embodiment, the at least one method may include receiving, from the receiving device (502), a sixth message comprising information associated with the RCS-based chatbot corresponding to the first MSISDN for reception and a second MSISDN for transmission. The at least one method may include providing, to the sending device (501) corresponding to the first MSISDN corresponding to the information associated with the RCS-based chatbot, a seventh message comprising the first MSISDN for reception and the second MSISDN for transmission, via the non-terrestrial network.

[0154] According to one embodiment, the at least one method may include converting the first message based on SMS or MMS into the second message based on RCS.

[0155] According to one embodiment, the at least one method may include an operation of receiving a request for creating an RCS-based chatbot corresponding to the first MSISDN. The at least one method may include an operation of creating an RCS-based chatbot corresponding to the first MSISDN based on the creation request. The at least one method may include an operation of providing a registration request for information associated with the chatbot to a Maap registry.

[0156] According to one embodiment, the at least one method may include receiving a token corresponding to the RCS-based chatbot from the Maap registry. The at least one method may include providing a first authentication key corresponding to the RCS-based chatbot to the calling device (501) based on the receipt of the token.

[0157] According to one embodiment, the at least one method may include performing authentication based on the second authentication key provided from the sending device (501) and the first authentication key. The operation of providing the second message may include transmitting the second message based on the success of the authentication.

[0158] According to one embodiment, the operation of checking whether the receiving device (502) corresponding to the second MSISDN is capable of using RCS may include an operation of checking whether the receiving device (502) is capable of using RCS based on information provided from a server of an RCS to which the receiving device (502) is registered.

[0159] According to one embodiment, an electronic device (108; 510) may be provided. The electronic device (108; 510) may include a memory storing at least one instruction. The electronic device (108; 510) may include a processor. The at least one instruction, when executed by the processor, may cause the electronic device (108; 510) to perform at least one operation. The at least one operation may include receiving, from a sending device (501) over a non-terrestrial network, a first message including a first MSISDN for sending and a second MSISDN for receiving. The at least one operation may include checking whether a receiving device (502) corresponding to the second MSISDN is RCS-enabled. The at least one action may include providing a second message including information associated with an RCS-based chatbot for transmission corresponding to the first MSISDN replacing the first MSISDN and the second MSISDN for reception, based on the availability of the RCS by the receiving device (502).

[0160] According to one embodiment, a method for providing a message is provided. The method may include receiving a first message including a first MSISDN for sending and a second MSISDN for receiving corresponding to an electronic device (101). The method may include obtaining at least one piece of information registered in association with a chatbot corresponding to the first MSISDN based on confirming that the first MSISDN is an MSISDN associated with a chatbot. The method may include providing content of the first message and the at least one piece of information.

[0161] According to one embodiment, a storage medium storing at least one computer-readable instruction may be provided. The at least one instruction, when executed by a processor (120) of an electronic device (101), may cause the electronic device (101) to perform at least one operation. The at least one operation may include receiving a first message including a first MSISDN for transmission and a second MSISDN for reception corresponding to the electronic device (101). The at least one operation may include obtaining at least one piece of information registered in association with a chatbot corresponding to the first MSISDN based on confirming that the first MSISDN is an MSISDN associated with a chatbot. The at least one operation may include providing content of the first message and the at least one piece of information.

[0162] According to one embodiment, an electronic device (101) may be provided. The electronic device (101) may include a memory (130) that stores at least one instruction. The electronic device may include a processor (120). The at least one instruction, when executed by the processor (120), may cause the electronic device (101) to perform at least one operation. The at least one operation may include receiving a first message including a first MSISDN for transmission and a second MSISDN for reception corresponding to the electronic device (101). The at least one operation may include obtaining at least one piece of information registered in association with a chatbot corresponding to the first MSISDN based on confirming that the first MSISDN is an MSISDN associated with a chatbot. The at least one operation may include providing content of the first message and the at least one piece of information.

[0163] According to one embodiment, a method for providing a message is provided. The method may include receiving, from a sending device (501) over a non-terrestrial network, a first message based on a first type scheme, the first message including a first MSISDN for sending and a second MSISDN for receiving. The method may include determining whether a receiving device (502) corresponding to the second MSISDN can use a second type scheme different from the first type scheme. The method may include providing, depending on whether the receiving device (502) can use the second type scheme, a second message based on the second type scheme, the second message including information based on the second type scheme for sending and the second MSISDN for receiving, or a third message based on the first type scheme, the third message including a third MSISDN for sending and the second MSISDN for receiving mapped to the first MSISDN.

[0164] According to one embodiment, a storage medium storing at least one computer-readable instruction may be provided. The at least one instruction, when executed by a processor of an electronic device (108; 510), may cause the electronic device (108; 510) to perform at least one operation. The at least one operation may include receiving, from a sending device (501) over a non-terrestrial network, a first message based on a first type scheme, the first message including a first MSISDN for sending and a second MSISDN for receiving. The at least one operation may include checking whether a receiving device (502) corresponding to the second MSISDN is capable of using a second type scheme different from the first type scheme. The at least one operation may include providing a second message based on the second type scheme, including information based on the second type scheme for transmission and the second MSISDN for reception, or providing a third message based on the first type scheme, including a third MSISDN for transmission mapped to the first MSISDN and the second MSISDN for reception, depending on whether the receiving device (502) can use the second type scheme.

[0165] According to one embodiment, an electronic device (108; 510) may be provided. The electronic device (108; 510) may include a memory storing at least one instruction. The electronic device (108; 510) may include a processor. The at least one instruction, when executed by the processor, may cause the electronic device (108; 510) to perform at least one operation. The at least one operation may include receiving, from a sending device (501) over a non-terrestrial network, a first message based on a first type scheme, the first message including a first MSISDN for sending and a second MSISDN for receiving. The at least one operation may include checking whether a receiving device (502) corresponding to the second MSISDN is capable of using a second type scheme different from the first type scheme. The at least one operation may include providing a second message based on the second type scheme, including information based on the second type scheme for transmission and the second MSISDN for reception, or providing a third message based on the first type scheme, including a third MSISDN for transmission mapped to the first MSISDN and the second MSISDN for reception, depending on whether the receiving device (502) can use the second type scheme.

[0166] Electronic devices according to the embodiments disclosed in this document may take various forms. Electronic devices may include, for example, portable communication devices (e.g., smartphones), computer devices, portable multimedia devices, portable medical devices, cameras, wearable devices, or home appliances. Electronic devices according to the embodiments disclosed in this document are not limited to the aforementioned devices.

[0167] The embodiments of this document and the terminology used herein are not intended to limit the technical features described in this document to specific embodiments, but should be understood to include various modifications, equivalents, or substitutes of the embodiments. 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 indicates 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 among those phrases, 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 component) 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.

[0168] The term "module" used in the embodiments 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. A module may be an integral component, or a minimum unit or part of such a component 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).

[0169] One embodiment of the present document may be implemented as software (e.g., program (140)) including one or more instructions stored in a storage medium (e.g., built-in memory (136) or external memory (138)) readable by a machine (e.g., electronic device (101), electronic device (501)). For example, a processor (e.g., processor (120)) of the machine (e.g., electronic device (101), electronic device (501)) 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.

[0170] According to one embodiment, the method according to one embodiment disclosed in this document may be provided as included in a computer program product. The computer program product may be traded as a product between a seller and a buyer. The computer program product may be distributed in the form of a machine-readable storage medium (e.g., 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™) or directly between two user devices (e.g., smart phones). In the case of online distribution, at least a portion of the computer program product may be temporarily stored or temporarily generated in a machine-readable storage medium, such as the memory of a manufacturer's server, an application store's server, or an intermediary server.

[0171] According to one embodiment, each component (e.g., a module or a program) of the above-described components may include one or more entities, and some of the entities may be separated and placed in other components. According to one embodiment, one or more components or operations of the aforementioned components may be omitted, or one or more other components or operations may be added. Alternatively or additionally, a plurality of components (e.g., a module or a program) may be integrated into a single component. In this case, the integrated component may perform one or more functions of each of the plurality of components identically or similarly to those performed by the corresponding component among the plurality of components prior to the integration. According to one embodiment, the operations performed by a module, program, or other component may be executed sequentially, in parallel, iteratively, 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.

Claims

1. In the method of providing a message, An operation of receiving, from a sending device (501), a first message including a first MSISDN for sending and a second MSISDN for receiving, via a non-terrestrial network; An operation for checking whether a receiving device (502) corresponding to the second MSISDN can use RCS; and An operation of providing a second message including information related to an RCS-based chatbot for transmission corresponding to the first MSISDN replacing the first MSISDN and the second MSISDN for reception based on the availability of the RCS by the receiving device (502). A method including:

2. In paragraph 1, An operation of providing a third message including a third MSISDN for sending and the second MSISDN for receiving based on the fact that the receiving device (502) cannot use the RCS. A method including:

3. In any one of paragraphs 1 and 2, An operation of receiving a fourth message including the third MSISDN mapped to the first MSISDN for reception and the second MSISDN for transmission from the receiving device (502); and An operation of providing a fifth message including the first MSISDN for reception and the second MSISDN for transmission through the non-terrestrial network to the transmitting device (501) corresponding to the first MSISDN mapped to the third MSISDN A method including:

4. In any one of paragraphs 1 to 3, An operation of mapping the third MSISDN to the first MSISDN based on the fact that the receiving device (502) cannot use the RCS. A method including:

5. In any one of paragraphs 1 to 4, An operation of unmapping the third MSISDN to the first MSISDN after a specified period of time has elapsed since mapping the third MSISDN to the first MSISDN. A method including:

6. In any one of paragraphs 1 to 5, An operation of receiving a sixth message including information related to an RCS-based chatbot corresponding to the first MSISDN for reception and a second MSISDN for transmission from the receiving device (502); and An operation of providing a seventh message including the first MSISDN for reception and the second MSISDN for transmission through the non-terrestrial network to the sending device (501) corresponding to the first MSISDN corresponding to information associated with the RCS-based chatbot. A method including:

7. In any one of paragraphs 1 to 6, An action of converting said first message based on SMS or MMS into said second message based on RCS A method including:

8. In any one of paragraphs 1 to 7, An action of receiving a request for creation of an RCS-based chatbot corresponding to the first MSISDN; An operation of generating an RCS-based chatbot corresponding to the first MSISDN based on the above generation request; and Action to provide a registration request for information related to the chatbot to the Maap registry A method including:

9. In any one of paragraphs 1 to 8, An action of receiving a token corresponding to the RCS-based chatbot from the Maap registry; and Based on the reception of the above token, an operation of providing a first authentication key corresponding to the RCS-based chatbot to the sending device (501) A method including:

10. In any one of paragraphs 1 to 9, The above method: An operation for performing authentication based on the second authentication key and the first authentication key provided from the above-mentioned sending device (501). Including, The action of providing the second message is an action of transmitting the second message based on the success of the authentication. A method including:

11. In any one of paragraphs 1 to 10, The operation of checking whether the receiving device (502) corresponding to the second MSISDN can use RCS is as follows: A method including an operation of checking whether the receiving device (502) can use RCS based on information provided from a server of a registered RCS.

12. A storage medium storing at least one computer-readable instruction, wherein the at least one instruction, when executed by a processor of an electronic device (108; 510), causes the electronic device (108; 510) to perform at least one operation, At least one of the above actions: An operation of receiving, from a sending device (501), a first message including a first MSISDN for sending and a second MSISDN for receiving, via a non-terrestrial network; An operation for checking whether a receiving device (502) corresponding to the second MSISDN can use RCS; and An operation of providing a second message including information related to an RCS-based chatbot for transmission corresponding to the first MSISDN replacing the first MSISDN and the second MSISDN for reception based on the availability of the RCS by the receiving device (502). A storage medium containing.

13. In paragraph 12, At least one of the above methods: An operation of providing a third message including a third MSISDN for sending and the second MSISDN for receiving based on the fact that the receiving device (502) cannot use the RCS. A storage medium containing.

14. In any one of paragraphs 12 to 13, At least one of the above methods: An operation of receiving a fourth message including the third MSISDN mapped to the first MSISDN for reception and the second MSISDN for transmission from the receiving device (502); and An operation of providing a fifth message including the first MSISDN for reception and the second MSISDN for transmission through the non-terrestrial network to the transmitting device (501) corresponding to the first MSISDN mapped to the third MSISDN A storage medium containing.

15. In the method of providing a message, An operation of receiving, from a transmitter device (501), a first message based on a first type scheme, including a first MSISDN for transmission and a second MSISDN for reception, through a non-terrestrial network; An operation for checking whether a receiving device (502) corresponding to the second MSISDN can use a second type scheme different from the first type scheme; and An operation of providing a second message based on the second type scheme including information based on the second type scheme for transmission and the second MSISDN for reception, or providing a third message based on the first type scheme including a third MSISDN for transmission mapped to the first MSISDN and the second MSISDN for reception, depending on whether the receiving device (502) can use the second type scheme. A method including:

Images