Electronic device and network connection method using same

Abstract

According to an embodiment of the present disclosure, an electronic device may comprise: a communication circuit; at least one processor including processing circuitry; and a memory for storing instructions. According to an embodiment, the instructions, when executed individually or collectively by the at least one processor, may cause the electronic device to connect to a network by using at least one of a first-type IP address or a second-type IP address by means of the communication circuit. According to an embodiment, the instructions, when executed individually or collectively by the at least one processor, may cause the electronic device to attempt to reconnect to the network by using the first-type IP address and the second-type IP address when a situation in which the network connection is released is detected. According to an embodiment, the instructions, when executed individually or collectively by the at least one processor, may cause the electronic device to identify at least one type of IP of the network by using a response to the network reconnection. According to an embodiment, the instructions, when executed individually or collectively by the at least one processor, may cause the electronic device to store the identified at least one type of IP in the memory. In addition to various embodiments disclosed in the present document, various other embodiments may be possible.

Description

Electronic device and network connection method using the same

[0001] The embodiments of the present disclosure relate to an electronic device and a network connection method using the same.

[0002] With the continuous popularization of various portable devices and the continuous advancement of communication technology, various data communication methods are being developed.

[0003] An electronic device can store the IP (Internet Protocol) types supported by the network and perform communication by receiving an IP address of that type through the network. If the network connection is disconnected due to situations such as a change in the carrier's IP address policy, communication errors may occur. In this case, the electronic device can perform communication through an update that changes the stored IP type.

[0004] The information described above may be provided as related art for the purpose of aiding understanding of the present disclosure. No claim or determination is made as to whether any of the foregoing may be applied as prior art related to the present disclosure.

[0005] However, it may take a long time to perform an update that changes the IP type, and consequently, communication errors may persist, making it difficult to perform communication.

[0006] An electronic device according to an embodiment of the present disclosure may attempt to reconnect to a network using a first type IP address and a second type IP address when a situation in which a network connection is disconnected is detected, and may reconnect to the network using at least one type of IP-based IP address included in a communication connection rejection message received from the network to perform communication.

[0007] According to one embodiment of the present disclosure, an electronic device may include at least one processor comprising a communication circuit and a processing circuitry, and a memory for storing instructions. According to one embodiment, when the instructions are executed individually or collectively by the at least one processor, the electronic device may be able to connect to a network using at least one of a first type IP address or a second type IP address through the communication circuit. According to one embodiment, when the instructions are executed individually or collectively by the at least one processor, the electronic device may be able to attempt to reconnect to the network using the first type IP address and the second type IP address when a situation in which the connection to the network is disconnected is detected. According to one embodiment, when the instructions are executed individually or collectively by the at least one processor, the electronic device may be able to identify at least one type IP of the network using a response to the network reconnection. According to one embodiment, when the instructions are executed individually or collectively by the at least one processor, the electronic device may store the identified at least one type of IP in the memory.

[0008] According to one embodiment of the present disclosure, a network connection method may include an operation of connecting to a network using at least one of a first type IP address or a second type IP address. According to one embodiment, the network connection method may include an operation of attempting to reconnect to the network using the first type IP address and the second type IP address when a situation in which the connection to the network is disconnected is detected. According to one embodiment, the network connection method may include an operation of identifying at least one type of IP of the network using a response to the network reconnection. According to one embodiment, the network connection method may include an operation of storing the identified at least one type of IP in memory.

[0009] According to one embodiment of the present disclosure, a non-transient computer-readable storage medium (or computer program product) storing one or more programs may be described. According to one embodiment, one or more programs may include a command to connect to a network using at least one of a first type IP address or a second type IP address via a communication circuit when executed by at least one processor of an electronic device. According to one embodiment, one or more programs may include a command to attempt to reconnect to the network using the first type IP address and the second type IP address when a situation in which the connection to the network is disconnected is detected when executed by at least one processor of an electronic device. According to one embodiment, one or more programs may include a command to identify at least one type of IP of the network using a response to the network reconnection when executed by at least one processor of an electronic device. According to one embodiment, one or more programs may include a command to store the identified at least one type of IP in memory when executed by at least one processor of an electronic device.

[0010] An electronic device according to an embodiment of the present disclosure can perform uninterrupted communication through a network by reconnecting to the network using at least one type of IP-based IP address included in a communication connection rejection message received from the network when a situation in which the network connection is disconnected is detected.

[0011] FIG. 1 is a block diagram of an electronic device in a network environment according to one embodiment of the present disclosure.

[0012] FIG. 2 is a block diagram illustrating an electronic device according to one embodiment of the present disclosure.

[0013] FIG. 3 is a flowchart illustrating a network connection method according to one embodiment of the present disclosure.

[0014] FIG. 4 is a flowchart illustrating a network connection method according to one embodiment of the present disclosure.

[0015] FIGS. 5a and 5b are flowcharts for illustrating a network connection method according to one embodiment of the present disclosure.

[0016] FIG. 6 is a diagram illustrating the signal flow between an electronic device and a network according to one embodiment of the present disclosure.

[0017] FIG. 7 is a diagram illustrating the signal flow between an electronic device and a network according to one embodiment of the present disclosure.

[0018] FIG. 8 is a diagram illustrating the signal flow between an electronic device and a network according to one embodiment of the present disclosure.

[0019] FIGS. 9a and 9b are drawings for illustrating signal flow between an electronic device and a network according to one embodiment of the present disclosure.

[0020] Hereinafter, embodiments of the present disclosure are described in detail with reference to the drawings so that those skilled in the art can easily practice them. However, the present disclosure may be embodied in various different forms and is not limited to the embodiments described herein. In relation to the description of the drawings, the same or similar reference numerals may be used for identical or similar components. Furthermore, in the drawings and related descriptions, descriptions of well-known functions and configurations may be omitted for clarity and brevity.

[0021] FIG. 1 is a block diagram of an electronic device (101) in a network environment (100) according to one embodiment of the present disclosure.

[0022] Referring to FIG. 1, in a network environment (100), an electronic device (101) may communicate with an electronic device (102) through a first network (198) (e.g., a short-range wireless communication network) or with at least one of an electronic device (104) or a server (108) through a second network (199) (e.g., a long-range wireless communication network). According to one embodiment, the electronic device (101) may communicate with the electronic device (104) through a server (108). According to one embodiment, the electronic device (101) may include a processor (120), memory (130), input module (150), sound output module (155), display module (160), audio module (170), sensor module (176), interface (177), connection terminal (178), haptic module (179), camera module (180), power management module (188), battery (189), communication module (190), subscriber identification module (196), or antenna module (197). In some embodiments, at least one of these components (e.g., connection terminal (178)) may be omitted from the electronic device (101), or one or more other components may be added. In some embodiments, some of these components (e.g., sensor module (176), camera module (180), or antenna module (197)) may be integrated into a single component (e.g., display module (160)).

[0023] The processor (120) can 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 software (e.g., a program (140)), and can perform various data processing or operations. According to one embodiment, as at least part of the data processing or operations, the processor (120) can store commands or data received from other components (e.g., a sensor module (176) or a communication module (190)) in volatile memory (132), process the commands or data stored in volatile memory (132), and store the resulting data in 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) that can operate independently or together with it (e.g., a graphics processing unit, a neural processing unit (NPU), an image signal processor, a sensor hub processor, or a communication processor). For example, if the electronic device (101) includes a main processor (121) and an auxiliary processor (123), the auxiliary processor (123) may be configured to use lower power than the main processor (121) or to be specialized for a designated function. The auxiliary processor (123) may be implemented separately from the main processor (121) or as part thereof.

[0024] The auxiliary processor (123) may control at least some of the functions or states associated with at least one component of the electronic device (101) (e.g., display module (160), sensor module (176), or communication module (190)) 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. According to one embodiment, the auxiliary processor (123) (e.g., image signal processor or communication processor) may be implemented as part of another functionally related component (e.g., camera module (180) or communication module (190)). According to one embodiment, the auxiliary processor (123) (e.g., neural network processing unit) may include a hardware structure specialized for processing an artificial intelligence model. The artificial intelligence model may be generated through machine learning. Such learning may be performed, for example, on the electronic device (101) itself where the artificial intelligence model is executed, or through a separate server (e.g., server (108)). The learning algorithm may include, for example, supervised learning, unsupervised learning, semi-supervised learning, or reinforcement learning, but is not limited to the examples described above. The artificial intelligence model may include a plurality of artificial neural network layers.An artificial neural network may be 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 the hardware structure, the artificial intelligence model may include a software structure, either additionally or substantially.

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

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

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

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

[0029] The display module (160) can visually provide information to an external (e.g., 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 said 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 the force generated by said touch.

[0030] The audio module (170) can convert sound into an electrical signal or, conversely, convert an electrical signal into sound. According to one embodiment, the audio module (170) can acquire sound through the input module (150) or output sound through the sound output module (155) or an external electronic device (e.g., electronic device (102)) (e.g., speaker or headphones) connected directly or wirelessly to the electronic device (101).

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

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

[0033] The connection terminal (178) may include a connector through which the electronic device (101) can 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).

[0034] The haptic module (179) can convert an electrical signal into a mechanical stimulus (e.g., vibration or movement) or an electrical stimulus that can be perceived by the user through tactile or kinesthetic senses. According to one embodiment, the haptic module (179) may include, for example, a motor, a piezoelectric element, or an electric stimulation device.

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

[0036] 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, for example, as at least part of a power management integrated circuit (PMIC).

[0037] The battery (189) can supply power to at least one component of the electronic device (101). According to one embodiment, the battery (189) may include, for example, a non-rechargeable primary battery, a rechargeable secondary battery, or a fuel cell.

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

[0039] The wireless communication module (192) can support 5G networks and next-generation communication technologies following 4G networks, for example, new radio access technology. NR access technology can support high-speed transmission of high-capacity data (enhanced mobile broadband (eMBB)), minimization of terminal power and connection of multiple terminals (massive machine type communications (mMTC)), or high reliability and low latency (ultra-reliable and low-latency communications (URLLC)). The wireless communication module (192) can support a high-frequency band (e.g., mmWave band) to achieve a high data transmission rate, for example. The wireless communication module (192) can support various technologies for securing performance in the high-frequency band, such as beamforming, massive MIMO (multiple-input and multiple-output), 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), external electronic device (e.g., electronic device (104)), or network system (e.g., second network (199)). According to one embodiment, the wireless communication module (192) may support a Peak data rate (e.g., 20 Gbps or more) for eMBB realization, loss coverage (e.g., 164 dB or less) for mMTC realization, or U-plane latency (e.g., downlink (DL) and uplink (UL) each 0.5 ms or less, or round trip 1 ms or less) for URLLC realization.

[0040] An antenna module (197) can transmit a signal or power to or from an external source (e.g., an external electronic device). According to one embodiment, the antenna module (197) may include an antenna comprising a radiator made of a conductor or a conductive pattern formed on a substrate (e.g., a printed circuit board (PCB)). According to 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 a first network (198) or a second network (199), may be selected from the plurality of antennas, for example, by a communication module (190). A signal or power may be transmitted or received between the communication module (190) and an external electronic device through the selected at least one antenna. According to some embodiments, in addition to the radiator, other components (e.g., a radio frequency integrated circuit (RFIC)) may be additionally formed as part of the antenna module (197).

[0041] According to various embodiments, the antenna module (197) may form a mmWave antenna module. According to one embodiment, the mmWave antenna module may include a printed circuit board, an RFIC disposed on or adjacent to a first surface (e.g., bottom surface) of the printed circuit board and capable of supporting a specified high frequency band (e.g., mmWave band), and a plurality of antennas (e.g., array antennas) disposed on or adjacent to a second surface (e.g., top surface or side surface) of the printed circuit board and capable of transmitting or receiving a signal of the specified high frequency band.

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

[0043] According to one embodiment, commands or data may be transmitted or received between an electronic device (101) and an external electronic device (104) through 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 performed on the electronic device (101) may be performed on one or more of the external electronic devices (102, 104, or 108). For example, if the electronic device (101) needs to perform a function or service automatically or in response to a request from a user or another device, the electronic device (101) may request one or more external electronic devices to perform at least part of the function or service instead of performing the function or service itself or additionally. One or more external electronic devices that receive the above request may execute at least part of the requested function or service, or 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 provide the result as is or additionally processed as at least part of the response to the request. For this purpose, for example, cloud computing, distributed computing, mobile edge computing (MEC), or client-server computing technology may be used. The electronic device (101) may provide ultra-low latency services using, for example, distributed computing or mobile edge computing. In another embodiment, the external electronic device (104) may include an Internet of Things (IoT) device. The server (108) may be an intelligent server using machine learning and / or neural networks. According to one embodiment, the external electronic device (104) or the server (108) may be included within a 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.

[0044] FIG. 2 is a block diagram illustrating an electronic device (101) according to one embodiment of the present disclosure.

[0045] Referring to FIG. 2, an electronic device (e.g., electronic device (101) of FIG. 1) may include a communication circuit (210) (e.g., communication module (190) of FIG. 1), a memory (220) (e.g., memory (130) of FIG. 1), and / or a processor (230) (e.g., processor (120) of FIG. 1).

[0046] An electronic device (101) according to one embodiment may include an electronic device running on an operating system (e.g., the operating system (142) of FIG. 1), for example, Android™, iOS™, Windows™, Symbian™, Tizen™, or Bada™.

[0047] According to one embodiment of the present disclosure, a communication circuit (210) (e.g., a communication module (190) of FIG. 1) can perform the function of transmitting and receiving data through a network (250) (e.g., a first network (198) and / or a second network (199) of FIG. 1) under the control of a processor (230).

[0048] According to one embodiment of the present disclosure, a memory (220) (e.g., memory (130) of FIG. 1) performs the function of storing a program (e.g., program (140) of FIG. 1), an operating system (OS) (142), various applications, and / or input / output data for processing and controlling the processor (230) of the electronic device (101), and can store a program that controls the overall operation of the electronic device (101). The memory (220) can store various configuration information required for processing functions related to various embodiments of the present disclosure in the electronic device (101). The memory (220) can store executable instructions. For example, the memory (220) can store instructions that cause the electronic device (101) to perform operations when executed by the processor (230). For example, the instructions may be stored in a computer-readable storage medium. The storage medium It may be tangible and non-transitory. The memory (220) and / or storage medium may store one or more programs containing instructions.

[0049] In one embodiment, the memory (220) may store instructions for attempting to reconnect to the network (250) using a first type IP address and a second type IP address when a situation in which the network (250) is disconnected is detected. It may store instructions for identifying at least one type of IP of the network (250) using a response to the network (250) reconnection. The memory (220) may store the identified at least one type of IP under the control of the processor (230). The memory (220) may store instructions for reconnecting to the network (250) and performing communication using the identified at least one type of IP.

[0050] In one embodiment, the memory (220) may include a database (225). For example, the database (225) may store IP type information used for connecting to a network (250) to perform communication. For example, the IP type information may include IPv4 (internet protocol version 4), IPv6 (internet protocol version 6), or IPv4v6. However, it is not limited thereto.

[0051] According to one embodiment of the present disclosure, the processor (230) may include, for example, a microcontroller unit (MCU) and may control a plurality of hardware components connected to the processor (230) by running an operating system (OS) or an embedded software program. The processor (230) may control a plurality of hardware components according to, for example, instructions stored in memory (220) (e.g., program (140) of FIG. 1).

[0052] In one embodiment, the processor (230) may connect to the network (250) using at least one of a first type IP address or a second type IP address. For example, the first type IP address may include an IPv4-based IP address, and the second type IP address may include an IPv6-based IP address. However, it is not limited thereto.

[0053] In one embodiment, when the processor (230) detects a situation in which the connection of the network (250) is disconnected, it may attempt to reconnect to the network (250) using a first type IP address and a second type IP address. For example, the situation in which the connection of the network (250) is disconnected may include at least one of the following: a situation in which the electronic device (101) is terminated; a situation in which the connection with the network (250) is disconnected by a user of the electronic device (101); a situation in which the connection with the network (250) is disconnected by a request of the network (250); and a situation in which the connection with the network (250) is disconnected as the location of the electronic device (101) changes. However, it is not limited thereto.

[0054] In one embodiment, the processor (230) can identify at least one type of IP of the network (250) using a response to the network (250) reconnection. For example, the processor (230) can detect a communication connection rejection message received from the network (250) in response to the network (250) reconnection. For example, the communication connection rejection message may include at least one type of IP that is connectable (or connectable, connectable) and / or information that causes the communication connection rejection. The processor (230) can identify at least one type of IP that is connectable to the network (250) and / or information that causes the communication connection rejection included in the communication connection rejection message. The processor (230) can store the identified at least one type of IP in memory (220), for example, a database (225). The processor (230) can reconnect to the network (250) using the identified at least one type of IP and perform communication.

[0055] An electronic device (101) according to one embodiment of the present disclosure may include a communication circuit (210), at least one processor (230) including a processing circuitry, and a memory (220) for storing instructions. When the instructions according to one embodiment are executed individually or collectively by at least one processor (230), the electronic device (101) may be configured to connect to a network (250) using at least one of a first type IP address or a second type IP address through the communication circuit (210). When the instructions according to one embodiment are executed individually or collectively by at least one processor (230), the electronic device (101) may be configured to attempt to reconnect to the network (250) using the first type IP address and the second type IP address when a situation in which the connection to the network (250) is disconnected is detected. Instructions according to one embodiment, when executed individually or collectively by at least one processor (230), may cause the electronic device (101) to identify at least one type of IP of the network (250) using a response to a network (250) reconnection. Instructions according to one embodiment, when executed individually or collectively by at least one processor (230), may cause the electronic device (101) to store the identified at least one type of IP in memory (220).

[0056] Instructions according to one embodiment, when executed individually or collectively by at least one processor (230), can cause an electronic device (101) to reconnect to a network (250) using at least one type of IP-based IP address.

[0057] Instructions according to one embodiment, when executed individually or collectively by at least one processor (230), may cause the electronic device (101) to detect a communication connection rejection message received from the network (250) in response to a reconnection to the network (250). A communication connection rejection message according to one embodiment may include at least one type of IP that is connectable to the network (250).

[0058] When instructions according to one embodiment are executed individually or collectively by at least one processor (230), the electronic device (101) may be able to reconnect to the network (250) using a first type IP-based IP address when the communication connection rejection message includes a first type IP.

[0059] Instructions according to one embodiment, when executed individually or collectively by at least one processor (230), may cause the electronic device (101) to check whether the at least one processor (230) supports converting the second type of IP to the first type of IP using the first conversion method when the communication connection rejection message includes the second type of IP. Instructions according to one embodiment, when executed individually or collectively by at least one processor (230), may cause the electronic device (101) to convert the second type of IP to the first type of IP using the first conversion method if it is confirmed that the at least one processor (230) supports converting the second type of IP to the first type of IP using the first conversion method. Instructions according to one embodiment, when executed individually or collectively by at least one processor (230), may cause the electronic device (101) to reconnect to the network (250) using the first type of IP-based IP address converted using the first conversion method.

[0060] When instructions according to one embodiment are executed individually or collectively by at least one processor (230), the electronic device (101) may convert the second type of IP to the first type of IP using a second conversion method if it is determined that the at least one processor (230) does not support converting the second type of IP to the first type of IP using a first conversion method. When instructions according to one embodiment are executed individually or collectively by at least one processor (230), the electronic device (101) may reconnect to the network (250) using the first type of IP-based IP address converted using the second conversion method.

[0061] When instructions according to one embodiment are executed individually or collectively by at least one processor (230), the electronic device (101) may be able to reconnect to the network (250) using the first type IP-based IP address and the second type IP-based IP address when the communication connection rejection message includes the first type IP and the second type IP.

[0062] A communication connection rejection message according to one embodiment may include information that causes the communication connection rejection.

[0063] When instructions according to one embodiment are executed individually or collectively by at least one processor (230), the electronic device (101) may attempt to reconnect to the network (250) using a first type IP address and a second type IP address at specified time intervals when the communication connection rejection message contains information that causes the communication connection rejection.

[0064] A first type of IP according to one embodiment may include IPv4. A second type of IP according to one embodiment may include IPv6.

[0065] FIG. 3 is a flowchart illustrating a network connection method according to one embodiment of the present disclosure.

[0066] In the following embodiments, each operation of FIG. 3 may be performed sequentially, but is not necessarily performed sequentially. For example, the order of each operation of FIG. 3 may be changed, and at least two operations may be performed in parallel.

[0067] According to one embodiment, operations 305 through 320 of FIG. 3 can be understood as being performed in a processor (e.g., processor (230) of FIG. 2) of an electronic device (e.g., electronic device (101) of FIG. 1 and FIG. 2).

[0068] Referring to FIG. 3, the processor (230) can connect to a network (e.g., the network (250) of FIG. 2) using at least one of a first type of IP (internet protocol) address or a second type of IP address in operation 305.

[0069] According to one embodiment, the first type of IP address includes an IP address of IPv4 (internet protocol version 4), and the second type of IP address may include an IP address of IPv6 (internet protocol version 6). However, it is not limited thereto.

[0070] In one embodiment, the first type IP address and / or the second type IP address may be set manually or automatically. For example, the first type IP address and / or the second type IP address may be set manually by an administrator or user inputting the first type IP address and the second type IP address. As another example, the first type IP address and / or the second type IP address may be set automatically by the processor (230) automatically obtaining them from the network (250). As yet another example, the first type IP address and / or the second type IP address may be set automatically by the network (250) automatically assigning them. However, this is not limited thereto.

[0071] In one embodiment, the processor (230) can connect to the network (250) and perform communication using at least one of the first type IP address or the second type IP address that is manually or automatically set as described above.

[0072] In one embodiment, when the processor (230) detects that the network (250) is disconnected during operation 310, it may attempt to reconnect to the network (250) using a first type IP address and a second type IP address.

[0073] A situation in which the connection of the network (250) according to one embodiment is disconnected may include at least one of the following: a situation in which the electronic device (101) is terminated; a situation in which the connection with the network (250) is disconnected by a user of the electronic device (101); a situation in which the connection with the network (250) is disconnected by a request of the network (250); and a situation in which the connection with the network (250) is disconnected as the location of the electronic device (101) changes. However, it is not limited thereto.

[0074] In one embodiment, the processor (230) can identify at least one type of IP of the network (250) by using a response to the network (250) reconnection in operation 315.

[0075] In one embodiment, the processor (230) can detect a communication connection rejection message received from the network (250) by using a response to a network (250) reconnection. For example, the communication connection rejection message may include at least one type of IP that is connectable. For example, the communication connection rejection message may include information that causes the communication connection rejection (or code information that causes the communication connection rejection). The processor (230) can identify at least one type of IP that is connectable (or communicable, connectable) to the network (250) included in the communication connection rejection message received from the network (250).

[0076] In one embodiment, the processor (230) can store at least one type of IP identified in operation 320 in memory (e.g., memory (220) of FIG. 2) (e.g., database (225) of FIG. 2).

[0077] In one embodiment, at least one type of IP that can connect to a network (250) may be stored in memory (220) (e.g., database (225)). The at least one type of IP that can connect to a network (250) may include at least one of a first type of IP (e.g., IPv4) or a second type of IP (e.g., IPv6) (e.g., IPv4, IPv6, or IPv4v6). For example, the at least one type of IP that can connect to a network (250) stored in the database (225) may be the at least one type of IP assigned when first connecting to the network (250).

[0078] In one embodiment, at least one type of IP stored in the aforementioned 320 operation may be different from at least one type of IP already stored in the database (225). In this case, at least one type of IP already stored in the database (225) may be updated to at least one type of IP stored in the 320 operation.

[0079] In one embodiment, although not shown, the processor (230) can reconnect to the network (250) using at least one type of IP identified to perform communication.

[0080] In one embodiment, the processor (230) can reconnect to the network (250) using at least one type of IP and perform communication, and when a situation of reconnecting to the network (250) is detected, check at least one type of IP stored in memory (220) (e.g., database (225)), and connect to the network (250) based thereon.

[0081] FIG. 4 is a flowchart illustrating a network connection method according to one embodiment of the present disclosure.

[0082] In the following embodiments, each operation of FIG. 4 may be performed sequentially, but is not necessarily performed sequentially. For example, the order of each operation of FIG. 4 may be changed, and at least two operations may be performed in parallel.

[0083] According to one embodiment, operations 405 through 435 of FIG. 4 can be understood as being performed in a processor (e.g., processor (230) of FIG. 2) of an electronic device (e.g., electronic device (101) of FIG. 1 and FIG. 2).

[0084] FIG. 4 according to various embodiments embodies the operation of FIG. 3 described above.

[0085] Referring to FIG. 4, the processor (230) can connect to a network (e.g., the network (250) of FIG. 2) using at least one of a first type IP address or a second type IP address in operation 405. For example, the first type IP address may include an IPv4 IP address, and the second type IP address may include an IPv6 IP address. However, it is not limited thereto.

[0086] In one embodiment, the processor (230) can determine whether a situation in which the connection to the network (250) is disconnected is detected during operation 410. For example, a situation in which the connection to the network (250) is disconnected may include at least one of a situation in which the electronic device (101) is terminated, a situation in which the connection to the network (250) is disconnected by a user of the electronic device (101), a situation in which the connection to the network (250) is disconnected by a request of the network (250), and a situation in which the connection to the network (250) is disconnected as the location of the electronic device (101) changes. However, it is not limited thereto.

[0087] In one embodiment, if a situation in which the connection of the network (250) is disconnected is not detected (e.g., NO of operation 410), the processor (230) may continue to perform an operation of connecting to the network (e.g., the network (250) of FIG. 2) and performing communication using at least one of the IP address of the first type or the IP address of the second type of operation 405.

[0088] In one embodiment, when a situation is detected where the connection of the network (250) is disconnected (e.g., YES of operation 410), the processor (230) may attempt to reconnect to the network (250) using a first type IP address and a second type IP address in operation 415.

[0089] In one embodiment, the processor (230) may detect a communication connection rejection message received from the network (250) in response to a reconnection to the network (250) in operation 420. The communication connection rejection message may include at least one type of IP that is accessible. According to one embodiment, the communication connection rejection message may include a communication connection rejection message including a first type of IP (e.g., ESM cause #50: PDN type IPv4 only allowed), a communication connection rejection message including a second type of IP (e.g., ESM cause #51: PDN type IPv6 only allowed), a communication connection rejection message including a first type of IP and a second type of IP (e.g., ESM cause #57: PDN type IPv4v6 only allowed), and a communication connection rejection message including service non-subscription information (e.g., ESM cause #33: requested service option not subscribed). However, it is not limited thereto.

[0090] In one embodiment, the processor (230) can identify at least one type of IP of the network (250) included in the communication connection rejection message in operation 425. In operation 430, the processor (230) can store at least one identified type of IP in memory (e.g., memory (220) of FIG. 2) (e.g., database (225) of FIG. 2). In operation 435, the processor (230) can reconnect to the network (250) using at least one identified type of IP-based IP address.

[0091] As seen in FIGS. 3 and 4 according to various embodiments, when the processor (230) detects a situation where the connection of the network (250) is disconnected, it attempts to reconnect to the network (250) using a first type IP and a second type IP, and can reconnect to the network (250) by checking at least one IP of the network (250) and using it. Accordingly, the electronic device (101) can perform communication through the network (250) without interruption.

[0092] FIGS. 5a and 5b are flowcharts for illustrating a network connection method according to one embodiment of the present disclosure.

[0093] In the following embodiments, each operation of FIGS. 5a and FIGS. 5b may be performed sequentially, but is not necessarily performed sequentially. For example, the order of each operation of FIGS. 5a and FIGS. 5b may be changed, and at least two operations may be performed in parallel.

[0094] According to one embodiment, operations 505 through 565 of FIGS. 5a and 5b can be understood as being performed in a processor (e.g., processor (230) of FIGS. 2) of an electronic device (e.g., electronic device (101) of FIGS. 1 and 2).

[0095] FIGS. 5a and FIG. 5b according to various embodiments embody the operation of FIG. 3 or FIG. 4 described above.

[0096] Referring to FIGS. 5a and 5b, the processor (230) can connect to a network (e.g., network (250) of FIG. 2) using at least one of a first type IP address or a second type IP address in operation 505. For example, the first type IP address may include an IPv4 IP address, and the second type IP address may include an IPv6 IP address. However, it is not limited thereto.

[0097] In one embodiment, the processor (230) can determine whether a situation in which the connection to the network (250) is disconnected is detected during operation 510. For example, a situation in which the connection to the network (250) is disconnected may include at least one of a situation in which the electronic device (101) is terminated, a situation in which the connection to the network (250) is disconnected by a user of the electronic device (101), a situation in which the connection to the network (250) is disconnected by a request of the network (250), and a situation in which the connection to the network (250) is disconnected as the location of the electronic device (101) changes. However, it is not limited thereto.

[0098] In one embodiment, if a situation in which the connection of the network (250) is disconnected is not detected (e.g., NO of operation 510), the processor (230) may continue to perform an operation of connecting to the network (e.g., the network (250) of FIG. 2) and performing communication using at least one of the IP address of the first type or the IP address of the second type of operation 505.

[0099] In one embodiment, when a situation is detected where the connection of the network (250) is disconnected (e.g., YES of operation 510), the processor (230) may attempt to reconnect to the network (250) using a first type IP address and a second type IP address in operation 515. In operation 520, the processor (230) may detect a communication connection rejection message received from the network (250) in response to the reconnection of the network (250).

[0100] A communication connection rejection message according to one embodiment may include at least one type of IP that is accessible to the network (250) (or at least one type of IP supported by the network (250)). For example, the communication connection rejection message may include a communication connection rejection message including a first type of IP accessible to the network (250), a communication connection rejection message including a second type of IP accessible to the network (250), and a communication connection rejection message including both the first type of IP and the second type of IP accessible to the network (250). However, it is not limited thereto, and the communication connection rejection message may include information that causes the communication connection rejection, for example, a communication connection rejection message including service non-subscription information indicating that the requested network service is not subscribed to.

[0101] In one embodiment, the processor (230) can check in operation 525 whether the communication connection rejection message contains a first type of IP. If it is confirmed that the communication connection rejection message contains a first type of IP (e.g., YES in operation 525), the processor (230) can check in operation 527 whether the type of IP used for network (230) connection and the first type of IP included in the communication connection rejection message are the same. If the type of IP used for network (230) connection and the first type of IP included in the communication connection rejection message are the same (e.g., YES in operation 527), the processor (230) can branch to operation 505 and perform an operation to connect to the network (250) using at least one of the first type of IP address or the second type of IP address.

[0102] In the case where the IP of the type used for connecting to the network (230) according to one embodiment and the IP of the first type included in the communication connection rejection message are the same, for example, it may be a situation where the connection to the network (250) is disconnected due to a temporary error in the network (250). However, it is not limited thereto.

[0103] In one embodiment, if the type of IP used for network (230) connection and the first type of IP included in the communication connection rejection message are not the same (e.g., NO of operation 527), the processor (230) may, in operation 530, store the first type of IP in memory (e.g., memory (220) of FIG. 2) (e.g., database (e.g., database (225) of FIG. 2). In operation 535, the processor (230) may reconnect to the network (250) using the first type of IP-based IP address. For example, although not shown, the processor (230) may manually or automatically receive the first type of IP-based IP address and reconnect to the network (250) using the received first type of IP-based IP address.

[0104] In one embodiment, if it is confirmed that the communication connection rejection message does not contain a first type of IP (e.g., NO of operation 525), the processor (230) can check in operation 540 whether the communication connection rejection message contains a second type of IP. If it is confirmed that the communication connection rejection message contains a second type of IP (e.g., YES of operation 540), the processor (230) can check in operation 543 whether the type of IP used for network (230) connection and the second type of IP included in the communication connection rejection message are the same. If the type of IP used for network (230) connection and the second type of IP included in the communication connection rejection message are the same (e.g., YES of operation 543), the processor (230) can branch to operation 505 and perform an operation to connect to the network (250) using at least one of the first type of IP address or the second type of IP address.

[0105] In the case where the IP of the type used for connecting to the network (230) according to one embodiment and the IP of the second type included in the communication connection rejection message are the same, for example, it may be a situation where the connection to the network (250) is disconnected due to a temporary error in the network (250). However, it is not limited thereto.

[0106] In one embodiment, if the type of IP used for network (230) connection and the second type of IP included in the communication connection rejection message are not the same (e.g., NO of operation 543), the processor (230) may store the second type of IP in memory (220) (e.g., database (225)) in operation 545. In operation 550, the processor (230) may reconnect to the network (250) using the second type of IP-based IP address. For example, although not shown, the processor (230) may manually or automatically receive the second type of IP-based IP address and reconnect to the network (250) using the received second type of IP-based IP address.

[0107] In one embodiment, if it is confirmed that the communication connection rejection message does not include the second type of IP (e.g., NO of operation 540), the processor (230) can check in operation 555 whether the communication connection rejection message includes the first type of IP and the second type of IP. If it is confirmed that the communication connection rejection message includes the first type of IP and the second type of IP (e.g., YES of operation 555), the processor (230) can check in operation 557 whether the type of IP used for network (230) connection is the same as the first type of IP and the second type of IP included in the communication connection rejection message. If the type of IP used for network (230) connection and the first type of IP and second type of IP included in the communication connection rejection message are the same (e.g., YES of operation 557), the processor (230) may branch to operation 505 and continue to perform the operation of connecting to the network (250) using at least one of the first type of IP address or the second type of IP address.

[0108] In the case where the IP of the type used for connecting to the network (230) according to one embodiment and the IP of the first type and the IP of the second type included in the communication connection rejection message are the same, for example, it may be a situation where the connection to the network (250) is disconnected due to a temporary error in the network (250). However, it is not limited thereto.

[0109] In one embodiment, if the type of IP used for network (230) connection and the first type of IP and second type of IP included in the communication connection rejection message are not the same (e.g., NO of operation 557), the processor (230) may store the first type of IP and second type of IP in memory (220) (e.g., database (225)) in operation 560. In operation 565, the processor (230) may reconnect to the network (250) using the first type of IP and second type of IP-based IP addresses. For example, although not shown, the processor (230) may manually or automatically receive the first type of IP-based IP address and the second type of IP-based IP address, and may reconnect to the network (250) using the assigned first type of IP-based IP address and second type of IP-based IP address.

[0110] In one embodiment, if it is confirmed that the communication connection rejection message does not include the first type IP and the second type IP (e.g., NO of the 555 operation), the processor (230) may branch to the 505 operation and perform an operation to connect to the network (250) using at least one of the first type IP address or the second type IP address.

[0111] FIG. 6 is a diagram illustrating the signal flow between an electronic device (101) and a network (250) according to one embodiment of the present disclosure.

[0112] In the following embodiments, each operation of FIG. 6 may be performed sequentially, but is not necessarily performed sequentially. For example, the order of each operation of FIG. 6 may be changed, and at least two operations may be performed in parallel.

[0113] According to various embodiments, FIG. 6 may be an operation performed after a situation in which the connection of a network (e.g., the network (250) of FIG. 2) is disconnected is detected. For example, FIG. 6 may be a signal flow between the electronic device (101) and the network (250) in operations 515 to 535 of FIG. 5a described above.

[0114] Referring to FIG. 6, a communication circuit (e.g., communication circuit (210) of FIG. 2) of an electronic device (e.g., electronic device (101) of FIG. 1) may, in operation 605, transmit a message requesting a first type of IP-based PDP (packet data protocol) context attach (or connect, access) to a processor (230) of the electronic device (101). The PDP context may include information used for connecting (or connecting, accessing) to a network (250). In operation 610, the communication circuit (210) may transmit a message requesting a second type of IP-based PDP context attach to a processor (230) of the electronic device (101). For example, the first type of IP may include IPv4. The second type of IP may include IPv6, but is not limited thereto.

[0115] Operations 605 and 610 according to one embodiment may be operations for receiving at least one type of IP-based IP address of the electronic device (101) to reconnect to the network (250) and perform communication after a situation in which the connection of the network (250) is disconnected is detected.

[0116] In one embodiment, the processor (230) may transmit a first type of IP-based RRC (radio resource control) connection setup request message to the network (250) in operation 615. The processor (230) may transmit a second type of IP-based RRC connection setup request message to the network (250) in operation 620.

[0117] In one embodiment, in response to receiving a first type IP-based RRC connection setup request message and a second type IP-based RRC connection setup request message from a processor (230) of an electronic device (101), the network (250) may, in operation 625, transmit a communication connection rejection message containing a first type IP (e.g., ESM cause #50: PDN type IPv4 only allowed) to the processor (230). Transmitting a communication connection rejection message containing a first type IP to the processor (230) may mean that the electronic device (101) can connect to the network (250) using a first type IP.

[0118] In one embodiment, the processor (230) may, in operation 630, transmit a communication connection rejection message including a first type of IP received from the network (250) to the communication circuit (210). By transmitting the communication connection rejection message including a first type of IP received from the network (250) to the communication circuit (210), the communication circuit (210) may prepare to connect to the network (250) based on the first type of IP.

[0119] In one embodiment, the network (250) may transmit a first type of IP-based RRC connection setup completion message to the processor (230) in operation 640. For example, as it is possible to connect to the network (250) using the first type of IP, the network (250) may transmit a first type of IP-based RRC connection setup completion message to the processor (230) in response to a first type of IP-based RRC connection setup request message (e.g., operation 615) received from the processor (230). For example, by transmitting the first type of IP-based RRC connection setup completion message to the processor (230), the network (250) may establish a logical path provided for data transmission between the electronic device (101) and the network (250).

[0120] In one embodiment, the processor (230) may transmit an attach acknowledgment message using a first type IP to the communication circuit (210) in operation 645. In operation 650, the processor (230) may store the first type IP in memory (e.g., memory (220) of FIG. 2). In one embodiment, although not shown, the processor (230) may manually or automatically receive an IP address based on the first type IP and may reconnect to the network (250) using the received IP address based on the first type IP.

[0121] FIG. 7 is a diagram illustrating the signal flow between an electronic device (101) and a network (250) according to one embodiment of the present disclosure.

[0122] In the following embodiments, each operation of FIG. 7 may be performed sequentially, but is not necessarily performed sequentially. For example, the order of each operation of FIG. 7 may be changed, and at least two operations may be performed in parallel.

[0123] According to various embodiments, FIG. 7 may be an operation performed after a situation in which the connection of a network (e.g., the network (250) of FIG. 2) is disconnected is detected. For example, FIG. 7 may be a signal flow between an electronic device (101) and a network (250) in operations 515, 520, 540 through 550 of FIG. 5a and 5b described above.

[0124] Referring to FIG. 7, a communication circuit (e.g., communication circuit (210) of FIG. 2) of an electronic device (e.g., electronic device (101) of FIG. 1) may, in operation 705, transmit a message requesting a first type of IP-based PDP context attach (or connection, access) to a processor (230) of the electronic device (101). In operation 710, the communication circuit (210) may, in operation 710, transmit a message requesting a second type of IP-based PDP context attach to a processor (230) of the electronic device (101). For example, the first type of IP may include IPv4. The second type of IP may include IPv6. However, it is not limited thereto.

[0125] In one embodiment, the processor (230) may transmit a first type of IP-based RRC connection setup request message to the network (250) in operation 715. In response to receiving the first type of IP-based RRC connection setup request message from the processor (230) of the electronic device (101), the network (250) may transmit a communication connection rejection message containing a second type of IP (e.g., ESM cause #51: PDN type IPv6 only allowed) to the processor (230) in operation 720. Transmitting a communication connection rejection message containing a second type of IP to the processor (230) may mean that the electronic device (101) can connect to the network (250) using the second type of IP.

[0126] In one embodiment, the processor (230) may transmit a communication connection rejection message containing a second type of IP to the communication circuit (210) in operation 725. By transmitting a communication connection rejection message containing a second type of IP received from the network (250) to the communication circuit (210), the communication circuit (210) may prepare to connect to the network (250) based on the second type of IP.

[0127] In one embodiment, the processor (230) may transmit a second type of IP-based RRC connection setup request message to the network (250) in operation 735. For example, as it is possible to connect to the network (250) using the second type of IP, the processor (230) may transmit a second type of IP-based RRC connection setup request message to the network (250). In operation 740, the network (250) may transmit a second type of IP-based RRC connection setup completion message to the processor (230). For example, by transmitting a second type of IP-based RRC connection setup completion message to the processor (230), the network (250) may establish a logical path provided for data transmission between the electronic device (101) and the network (250).

[0128] In one embodiment, the processor (230) can transmit an attach acknowledgment message using a second type IP to the communication circuit (210) in operation 745. In operation 747, the processor (230) can store the second type IP in memory (e.g., memory (220) of FIG. 2).

[0129] In one embodiment, although not illustrated, the processor (230) may manually or automatically receive a second type of IP-based IP address. For example, when the communication circuit (210) connects to a network (250) that supports a first type of IP using a second type of IP (e.g., IPv6)-based IP address, it may convert the second type of IP (e.g., IPv6)-based IP address into a first type of IP (e.g., IPv4)-based IP address. For example, the conversion method may include a first conversion method and a second conversion method. For example, the first conversion method may include a CLAT (customer-side translator) method, and the second conversion method may include an XLAT method. For example, the first conversion method and the second conversion method may be methods for supporting communication between the second type of IP-based IP address and the first type of IP-based IP. For example, the first conversion method may be a method of converting a second type IP (e.g., IPv6) based IP address into a first type IP (e.g., IPv4) based IP address when the processor (230) supports IP address conversion. The second conversion method may be a method in which the communication circuit (210) software-wise converts a second type IP (e.g., IPv6) based IP address into a first type IP (e.g., IPv4) based IP address when the processor (230) does not support IP address conversion.

[0130] In one embodiment, the communication circuit (210) may, in operation 750, transmit a message to the processor (230) requesting confirmation of whether IP address translation is supported. In operation 755, the processor (230) may, in operation 755, transmit a message to the communication circuit (210) containing information on whether IP address translation is supported.

[0131] In one embodiment, the communication circuit (210) can convert a second type IP-based IP address into a first type IP-based IP address using a first conversion method or a second conversion method in operation 760. For example, when the communication circuit (210) receives a message containing information that IP address conversion is supported from the processor (230), the communication circuit (210) can convert the second type IP-based IP address into a first type IP-based IP address using the first conversion method and reconnect to the network (250). For example, when the communication circuit (210) receives a message containing information that IP address conversion is not supported from the processor (230), the communication circuit (210) can convert the second type IP-based IP address into a first type IP-based IP address using the second conversion method and reconnect to the network (250).

[0132] FIG. 8 is a diagram illustrating the signal flow between an electronic device (101) and a network (250) according to one embodiment of the present disclosure.

[0133] In the following embodiments, each operation of FIG. 8 may be performed sequentially, but is not necessarily performed sequentially. For example, the order of each operation of FIG. 8 may be changed, and at least two operations may be performed in parallel.

[0134] According to various embodiments, FIG. 8 may be an operation performed after a situation in which the connection of a network (e.g., the network (250) of FIG. 2) is disconnected is detected. For example, FIG. 8 may be a signal flow between an electronic device (101) and a network (250) in operations 515, 520, 555 through 565 of FIG. 5a and 5b described above.

[0135] Referring to FIG. 8, a communication circuit (e.g., communication circuit (210) of FIG. 2) of an electronic device (e.g., electronic device (101) of FIG. 1) may, in operation 805, transmit a message requesting a first type of IP-based PDP context attach to a processor (230) of the electronic device (101). In operation 810, the communication circuit (210) may, in operation 810, transmit a message requesting a second type of IP-based PDP context attach to a processor (230) of the electronic device (101). For example, the first type of IP may include IPv4. The second type of IP may include IPv6. However, it is not limited thereto.

[0136] In one embodiment, the processor (230) may transmit a first type of IP-based RRC connection setup request message to the network (250) in operation 815. The processor (230) may transmit a second type of IP-based RRC connection setup request message to the network (250) in operation 820.

[0137] In one embodiment, in response to receiving a first type IP-based RRC connection setup request message and a second type IP-based RRC connection setup request message from a processor (230) of an electronic device (101), the network (250) may, in operation 825, transmit a communication connection rejection message (e.g., ESM cause #57: PDN type IPv4v6 only allowed) containing the first type IP and the second type IP to the processor (230). Transmitting a communication connection rejection message containing the first type IP and the second type IP to the processor (230) may mean that the electronic device (101) can connect to the network (250) using the first type IP and the second type IP.

[0138] In one embodiment, the processor (230) may transmit a communication connection rejection message, including a first type IP and a second type IP, to the communication circuit (210) in operation 830. By transmitting the communication connection rejection message, including the first type IP and the second type IP received from the network (250), to the communication circuit (210), the communication circuit (210) may prepare to connect to the network (250) based on the first type IP and the second type IP.

[0139] In one embodiment, the network (250) may transmit a message indicating the completion of an RRC connection setup based on a first type of IP and a second type of IP to the processor (230) in operation 835. The processor (230) may transmit an attachment acknowledgment message using the first type of IP and the second type of IP to the communication circuit (210) in operation 840. For example, by transmitting a message indicating the completion of an RRC connection setup based on a first type of IP and a second type of IP to the processor (230), the network (250) may establish a logical path provided for data transmission between the electronic device (101) and the network (250).

[0140] In one embodiment, the processor (230) may store a first type IP and a second type IP in memory (e.g., memory (220) of FIG. 2) in operation 845. In one embodiment, although not shown, the processor (230) may manually or automatically receive a first type IP-based IP address and a second type IP-based IP address, and may reconnect to the network (250) using the received first type IP-based IP address and second type IP-based IP address.

[0141] FIGS. 9a and 9b are drawings for illustrating signal flow between an electronic device (101) and a network (250) according to one embodiment of the present disclosure.

[0142] In the following embodiments, each operation of FIGS. 9a and FIGS. 9b may be performed sequentially, but is not necessarily performed sequentially. For example, the order of each operation of FIGS. 9a and FIGS. 9b may be changed, and at least two operations may be performed in parallel.

[0143] FIGS. 9a and 9b according to various embodiments may be operations performed after a situation in which the connection of a network (e.g., the network (250) of FIG. 2) is disconnected is detected. For example, FIGS. 9a and 9b may be signal flow between an electronic device (101) and a network (250) when, after a situation in which the connection of a network (250) is disconnected is detected, a communication connection rejection message containing service non-subscription information (e.g., ESM cause #33: requested service option not subscribed) is received from the network (250).

[0144] Referring to FIGS. 9a and 9b, a communication circuit (e.g., communication circuit (210) of FIG. 2) of an electronic device (e.g., electronic device (101) of FIG. 1) may, in operation 901, transmit a message requesting a first type of IP-based PDP context attach (or connection, access) to a processor (230) of the electronic device (101). In operation 903, the communication circuit (210) may, in operation 903, transmit a message requesting a second type of IP-based PDP context attach to a processor (230) of the electronic device (101). For example, the first type of IP may include IPv4. The second type of IP may include IPv6, but is not limited thereto.

[0145] In one embodiment, the processor (230) may transmit a first type of IP-based RRC connection setup request message to the network (250) in operation 905. In response to receiving the first type of IP-based RRC connection setup request message from the processor (230) of the electronic device (101), the network (250) may transmit a communication connection rejection message to the processor (230) in operation 907. For example, the communication connection rejection message transmitted in operation 907 may include service non-subscription information (e.g., ESM cause #33: requested service option not subscribed). For example, service non-subscription may include cases where the requested network service is not subscribed to.

[0146] In one embodiment, the processor (230) may, in operation 909, transmit a communication connection rejection message containing service non-subscription information to the communication circuit (210). By transmitting the communication connection rejection message containing service non-subscription information received from the network (250) to the communication circuit (210), the communication circuit (210) may prepare to transmit a second type of IP-based RRC connection setup request message to the network (250). For example, in operation 911, the processor (230) may transmit a second type of IP-based RRC connection setup request message to the network (250) after a specified time has elapsed. After transmitting a first type of IP-based RRC connection setup request message, upon receiving a communication connection rejection message containing service non-subscription information from the network (250), the processor (230) can transmit a second type of IP-based RRC connection setup request message, which is not of the first type of IP, to the network (250) to request the setup of a logical path for data transmission between the electronic device (101) and the network (250).

[0147] In one embodiment, the network (250) can check in operation 913 whether the second type of IP-based RRC connection setup is complete. If the second type of IP-based RRC connection setup is complete (e.g., YES in operation 913), the network (250) can send a message indicating the completion of the second type of IP-based RRC connection setup to the processor (230) in operation 915. For example, if the network is subscribed to a network service that supports the second type of IP, the network (250) can establish a logical path provided for data transmission between the electronic device (101) and the network (250) by sending a message indicating the completion of the second type of IP-based RRC connection setup to the processor (230).

[0148] In one embodiment, the processor (230) may transmit an attach acknowledgment message using a second type IP to the communication circuit (210) in operation 917. The processor (230) may store the second type IP in memory (e.g., memory (220) of FIG. 2) in operation 919.

[0149] In one embodiment, although not illustrated, the processor (230) may manually or automatically receive a second type of IP-based IP address. For example, when the communication circuit (210) connects to a network (250) that supports a first type of IP using a second type of IP (e.g., IPv6)-based IP address, it may convert the second type of IP (e.g., IPv6)-based IP address into a first type of IP (e.g., IPv4)-based IP address. For example, the conversion method may include a first conversion method and a second conversion method. For example, the first conversion method may include a CLAT method, and the second conversion method may include an XLAT method. For example, the first conversion method and the second conversion method may be methods for supporting communication of the second type of IP-based IP address to the first type of IP-based IP. For example, the first conversion method may be a method of converting a second type IP (e.g., IPv6) based IP address into a first type IP (e.g., IPv4) based IP address when the processor (230) supports IP address conversion. The second conversion method may be a method in which the communication circuit (210) software-wise converts a second type IP (e.g., IPv6) based IP address into a first type IP (e.g., IPv4) based IP address when the processor (230) does not support IP address conversion.

[0150] In one embodiment, the communication circuit (210) may, in operation 921, transmit a message to the processor (230) requesting confirmation of whether IP address conversion is supported. In operation 923, the processor (230) may transmit a message to the communication circuit (210) containing information on whether IP address conversion is supported. In operation 923, the communication circuit (210) may convert a second type IP-based IP address into a first type IP-based IP address using a first conversion method or a second conversion method. For example, if the communication circuit (210) receives a message containing information that IP address conversion is supported from the processor (230), the communication circuit (210) may convert the second type IP-based IP address into a first type IP-based IP address using the first conversion method and reconnect to the network (250). For example, if a message containing information that IP address conversion is not supported is received from the processor (230), the communication circuit (210) can use a second conversion method to convert a second type of IP-based IP address into a first type of IP-based IP address and reconnect to the network (250).

[0151] In one embodiment, if the second type of IP-based RRC connection setup is not completed (e.g., NO of operation 913), the network (250) may send a second type of IP-based RRC connection setup rejection message to the processor (230) in operation 929. For example, if the network service supporting the second type of IP is not subscribed to, the network (250) may send a second type of IP-based RRC connection setup rejection message to the processor (230).

[0152] In one embodiment, when a second type of IP-based RRC connection setup rejection message is received, the communication circuit (210) may prepare to send a second type of IP-based RRC connection setup request message to the network (250). For example, in operation 931, the processor (230) may send a first type of IP-based RRC connection setup request message to the network (250) after a specified time has elapsed.

[0153] In one embodiment, the network (250) can check whether the first type of IP-based RRC connection setup is completed in operation 933. If the first type of IP-based RRC connection setup is not completed (e.g., NO in operation 933), the network (250) can branch to operation 913.

[0154] In one embodiment, when the first type of IP-based RRC connection setup is completed (e.g., YES of operation 933), the network (250) may transmit a message indicating the completion of the first type of IP-based RRC connection setup to the processor (230) in operation 935. For example, by transmitting the message indicating the completion of the first type of IP-based RRC connection setup to the processor (230), the network (250) may establish a logical path provided for data transmission between the electronic device (101) and the network (250).

[0155] In one embodiment, the processor (230) can transmit an attach acknowledgment message using a first type IP to the communication circuit (210) in operation 937. The processor (230) can store the first type IP in memory (220) in operation 939.

[0156] As seen in FIGS. 5a to 9b according to various embodiments, when the processor (230) detects a situation in which the connection to the network (250) is disconnected, it attempts to reconnect to the network (250) using a first type IP and a second type IP, and can identify at least one type IP and / or information causing the communication connection rejection included in a communication connection rejection message received from the network (250). Based on at least one type IP and / or information causing the communication connection rejection included in the communication connection rejection message, the processor (230) can reconnect to the network (250) using at least one type IP, thereby enabling uninterrupted communication through the network (250).

[0157] A network connection method according to one embodiment of the present disclosure may include an operation of connecting to a network (250) using at least one of a first type IP address or a second type IP address through a communication circuit (210). A network connection method according to one embodiment may include an operation of attempting to reconnect to the network (250) using the first type IP address and the second type IP address when a situation in which the connection to the network (250) is disconnected is detected. A network connection method according to one embodiment may include an operation of identifying at least one type of IP of the network (250) using a response to the reconnection to the network (250). A network connection method according to one embodiment may include an operation of storing the identified at least one type of IP in a memory (220).

[0158] A network connection method according to one embodiment may include an operation of reconnecting to a network (250) using at least one type of IP-based IP address identified.

[0159] A network connection method according to one embodiment may include an operation of detecting a communication connection rejection message received from the network (250) in response to a reconnection to the network (250). A communication connection rejection message according to one embodiment may include at least one type of IP that can connect to the network (250).

[0160] A network connection method according to one embodiment may include an operation of reconnecting to a network (250) using an IP address based on the first type of IP when the communication connection rejection message includes an IP of the first type.

[0161] A network connection method according to one embodiment may include an operation of checking whether at least one processor (230) supports converting the second type of IP to the first type of IP using a first conversion method when the communication connection rejection message includes a second type of IP. A network connection method according to one embodiment may include an operation of converting the second type of IP to the first type of IP using a first conversion method when it is confirmed that at least one processor (230) supports converting the second type of IP to the first type of IP using the first conversion method. A network connection method according to one embodiment may include an operation of reconnecting to a network (250) using an IP address based on the first type of IP converted using the first conversion method.

[0162] A network connection method according to one embodiment may include an operation of converting a second type IP into a first type IP using a second conversion method if it is determined that at least one processor (230) does not support converting a second type IP into a first type IP using a first conversion method. A network connection method according to one embodiment may include an operation of reconnecting to a network (250) using an IP address based on a first type IP converted using the second conversion method.

[0163] A network connection method according to one embodiment may include an operation of reconnecting to a network (250) using a first type IP-based IP address and a second type IP-based IP address when a communication connection rejection message includes a first type IP and a second type IP.

[0164] A network connection method according to one embodiment may include a communication connection rejection message, which may include information that causes the communication connection rejection.

[0165] A network connection method according to one embodiment may include an operation of attempting to reconnect to a network (250) using a first type IP address and a second type IP address at specified time intervals when the communication connection rejection message contains information that causes the communication connection rejection.

[0166] A non-transitory computer-readable storage medium storing instructions that cause at least one processor (230) to perform operations when executed individually or collectively by at least one processor (230) of an electronic device (101) according to one embodiment of the present disclosure may enable the operation of connecting to a network (250) using at least one of a first type IP address or a second type IP address through a communication circuit (210). A non-transitory computer-readable storage medium storing instructions that cause at least one processor (230) to perform operations when executed individually or collectively by at least one processor (230) of an electronic device (101) according to one embodiment may enable the operation of attempting to reconnect to the network (250) using a first type IP address and a second type IP address when a situation in which the connection to the network (250) is disconnected is detected. A non-transient computer-readable storage medium storing instructions that cause at least one processor (230) to perform operations when executed individually or collectively by at least one processor (230) of an electronic device (101) according to one embodiment may enable the operation of identifying at least one type of IP of said network (250) using a response to a network (250) reconnection. A non-transient computer-readable storage medium storing instructions that cause at least one processor (230) to perform operations when executed individually or collectively by at least one processor (230) of an electronic device (101) according to one embodiment may enable the operation of storing the identified at least one type of IP in memory (220).

[0167] The electronic device according to the various embodiments disclosed in this document may be of various forms. The electronic device may include, for example, a portable communication device (e.g., a smartphone), a computer device, a portable multimedia device, a portable medical device, a camera, a wearable device, or a consumer electronics device. The electronic device according to the embodiments of this document is not limited to the devices described above.

[0168] The various embodiments of this document and the terms used therein are not intended to limit the technical features described in this document to specific embodiments, and should be understood to include various modifications, equivalents, or substitutions of said 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 said items unless the relevant context clearly indicates otherwise. In this document, phrases such as “A or B,” “at least one of A and B,” “at least one of A or B,” “A, B, or C,” “at least one of A, B, and C,” and “at least one of A, B, or C” each may include any one of the items listed together in the corresponding phrase, or all possible combinations thereof. Terms such as “first,” “second,” or “first” or “second” may be used simply to distinguish a component from another corresponding component and do not limit the components in any other aspect (e.g., importance or order). Where any (e.g., 1st) component is referred to as “coupled” or “connected” to another (e.g., 2nd) component, with or without the terms “functionally” or “communicationly,” it means that said any component may be connected to said other component directly (e.g., via a wire), wirelessly, or through a third component.

[0169] The term “module” as used in the various 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, for example. A module may be a component formed integrally, or a minimum unit of said component or a part thereof that performs one or more functions. According to one embodiment, a module may be implemented in the form of an application-specific integrated circuit (ASIC).

[0170] Various embodiments of the present document may be implemented as software (e.g., program (140)) comprising one or more instructions stored in a storage medium (e.g., internal memory (136) or external memory (138)) readable by a machine (e.g., electronic device (101)). For example, a processor (e.g., processor (120)) of the machine (e.g., electronic device (101)) may call at least one of the one or more instructions stored in the storage medium and execute it. This enables the machine to be operated 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 that can be executed by an interpreter. The storage medium readable by the machine may be provided in the form of a non-transitory storage medium. Here, 'non-temporary' simply means that the storage medium is a tangible device and does not contain a signal (e.g., electromagnetic waves), and the term does not distinguish between cases where data is stored semi-permanently and cases where it is stored temporarily.

[0171] According to one embodiment, the method according to the various embodiments disclosed herein may be provided by being included in a computer program product. The computer program product may be traded between a seller and a buyer as a product. The computer program product may be distributed in the form of a device-readable storage medium (e.g., compact disc read-only memory (CD-ROM)) or an application store (e.g., Play Store). TM It can be distributed online (e.g., downloaded or uploaded) through ) or directly between two user devices (e.g., smartphones). In the case of online distribution, at least a portion of the computer program product may be temporarily stored or temporarily created on a device-readable storage medium, such as the memory of a manufacturer's server, an application store's server, or a relay server.

[0172] According to various embodiments, each component (e.g., module or program) of the components described above may include a singular or multiple entities, and some of the multiple entities may be separated and placed in other components. According to various embodiments, one or more of the components or operations of the aforementioned components may be omitted, or one or more other components or operations may be added. Generally or additionally, multiple components (e.g., module or program) may be integrated into a single component. In this case, the integrated component may perform one or more functions of each of the multiple components in the same or similar manner as those performed by the corresponding component among the multiple components prior to integration. According to various embodiments, operations performed by the module, program, or other components 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 an electronic device (101), Communication circuit (210); At least one processor (230) including processing circuitry; and It includes a memory (220) that stores instructions, When the above instructions are executed individually or collectively by the at least one processor (230), the electronic device (101), Through the above communication circuit (210), a network (250) is connected using at least one of a first type IP address or a second type IP address, and When a situation is detected where the connection of the above network (250) is disconnected, an attempt is made to reconnect the above network (250) using the above type 1 IP address and the above type 2 IP address, and Using the response to the reconnection of the above network (250), at least one type of IP of the above network (250) is identified, and An electronic device that stores at least one type of IP identified above in the memory (220).

2. In Paragraph 1, When the above instructions are executed individually or collectively by the at least one processor (230), the electronic device (101), An electronic device that reconnects to the network (250) using at least one type of IP-based IP address identified above.

3. In Paragraph 1, When the above instructions are executed individually or collectively by the at least one processor (230), the electronic device (101), In response to the reconnection of the above network (250), a communication connection rejection message received from the above network (250) is detected, and The above communication connection rejection message is an electronic device including at least one type of IP that can connect to the network (250).

4. In Paragraph 3, When the above instructions are executed individually or collectively by the at least one processor (230), the electronic device (101), An electronic device that reconnects to the network (250) using the IP address based on the first type of IP when the communication connection rejection message includes the first type of IP.

5. In Paragraph 3, When the above instructions are executed individually or collectively by the at least one processor (230), the electronic device (101), If the communication connection rejection message contains the second type IP, the at least one processor (230) checks whether it supports converting the second type IP into the first type IP using a first conversion method, and If it is confirmed that the above at least one processor (230) supports converting the second type IP into the first type IP using the first conversion method, the second type IP is converted into the first type IP using the first conversion method, and An electronic device that reconnects to the network (250) using a first type of IP-based IP address converted by the first conversion method.

6. In Paragraph 5, When the above instructions are executed individually or collectively by the at least one processor (230), the electronic device (101), If it is determined that the above at least one processor (230) does not support converting the second type IP into the first type IP using the first conversion method, the second type IP is converted into the first type IP using the second conversion method, and An electronic device that reconnects to the network (250) using the first type of IP-based IP address converted by the second conversion method.

7. In Paragraph 3, When the above instructions are executed individually or collectively by the at least one processor (230), the electronic device (101), An electronic device that reconnects to the network (250) using the IP address based on the first type of IP and the IP address based on the second type of IP when the communication connection rejection message includes the IP of the first type and the IP of the second type.

8. In Paragraph 3, The above communication connection rejection message further includes information causing the above communication connection rejection, and When the above instructions are executed individually or collectively by the at least one processor (230), the electronic device (101), An electronic device that attempts to reconnect to the network (250) using the first type IP address and the second type IP address at specified time intervals when the communication connection rejection message contains information that causes the communication connection rejection.

9. In Paragraph 1, The above-mentioned first type of IP includes IPv4, and The above second type of IP is an electronic device including IPv6.

10. Regarding network connection methods, The operation of connecting to a network (250) using at least one of a first type IP address or a second type IP address through a communication circuit (210); When a situation is detected where the connection of the above network (250) is disconnected, an operation to attempt to reconnect the above network (250) using the above first type IP address and the above second type IP address; An operation to identify at least one type of IP of the network (250) using a response to the reconnection of the network (250); and A method including the operation of storing at least one type of IP identified above in memory (220).

11. In Paragraph 10, A method further comprising the operation of reconnecting to the network (250) using at least one type of IP-based IP address identified above.

12. In Paragraph 10, The operation further includes detecting a communication connection rejection message received from the network (250) in response to the reconnection of the network (250), and The above communication connection rejection message is a method including at least one type of IP that can be connected to the network (250).

13. In Paragraph 12, If the communication connection rejection message includes the first type of IP, the operation of reconnecting to the network (250) using the first type of IP-based IP address; If the communication connection rejection message contains the second type of IP, an operation to check whether at least one processor (230) supports converting the second type of IP into the first type of IP using a first conversion method; If it is confirmed that the above at least one processor (230) supports converting the second type IP into the first type IP using the first conversion method, the operation of converting the second type IP into the first type IP using the first conversion method; The operation of reconnecting to the network (250) using the first type of IP-based IP address converted by the first conversion method; If it is determined that the above at least one processor (230) does not support converting the second type IP into the first type IP using the first conversion method, the operation of converting the second type IP into the first type IP using the second conversion method; The operation of reconnecting to the network (250) using the IP-based address of the first type converted by the second conversion method; and A method further comprising the operation of reconnecting to the network (250) using the IP address based on the first type of IP and the IP address based on the second type of IP when the communication connection rejection message includes the IP address based on the first type of IP and the IP address based on the second type of IP.

14. In Paragraph 13, The above communication connection rejection message further includes information that causes the above communication connection rejection, and A method further comprising, when the communication connection rejection message contains information that causes the communication connection rejection, an operation of attempting to reconnect to the network (250) using the first type IP address and the second type IP address at specified time intervals.

15. A non-transitory computer-readable storage medium that stores instructions for causing at least one processor (230) to perform operations when executed individually or collectively by at least one processor (230) of an electronic device (101), The operation of connecting to a network (250) using at least one of a first type IP address or a second type IP address through a communication circuit (210); When a situation is detected where the connection of the above network (250) is disconnected, an operation to attempt to reconnect the above network (250) using the above first type IP address and the above second type IP address; An operation to identify at least one type of IP of the network (250) using a response to the reconnection of the network (250); and A computer-readable storage medium that enables the operation of storing at least one type of IP identified above in memory (220).

Images