KR20240030855A - Electronic device for managing wake up time points for services and operating method thereof - Google Patents

Abstract

According to one embodiment, the electronic device 101 may include at least one communication circuit 190; 320, and at least one processor 120; 310 operatively connected to the at least one communication circuit. . According to one embodiment, the at least one processor is related to a first wake up time corresponding to a first service from the first external electronic device (108; 111a) through the at least one communication circuit. It may be configured to receive first information. According to one embodiment, the at least one processor may be further configured to set second information related to a second wake-up time point corresponding to the second service based on the first information. According to one embodiment, the at least one processor may be further configured to transmit the second information to the second external electronic device 108 (112a) through the at least one communication circuit. According to one embodiment, the at least one processor may be further configured to perform a second operation set at the second wake-up time. According to one embodiment, the difference between the first wake-up time and the second wake-up time may be less than or equal to a set value.
Other embodiments are possible.

Description

Electronic device for managing wake-up times for services and operating method thereof {ELECTRONIC DEVICE FOR MANAGING WAKE UP TIME POINTS FOR SERVICES AND OPERATING METHOD THEREOF}

This disclosure relates to an electronic device that manages wake up timings for services and a method of operating the same.

An electronic device (e.g., user equipment (UE)) may access a wireless communication system and use communication services (e.g., voice communication services and/or data communication services) at a given location or while moving. In order to provide a communication service to an electronic device, an authentication operation for the electronic device is required.

Typically, a universal integrated circuit card (UICC) is inserted into an electronic device, and the electronic device and a communication service provider (e.g., Authentication operations are performed between servers of a mobile network operator (MNO). UICC may be referred to as a “subscriber identity module (SIM) card” in the case of the global system for mobile communications (GSM) and wideband code division multiple access (WCDMA). ), long term evolution (LTE), and/or new radio (NR) may be referred to as a “USIM card”.

When a user of an electronic device subscribes to a wireless communication service provided by a telecommunication service provider, the telecommunication service provider provides the user with a UICC (e.g. SIM card or USIM card), and the user directly transfers the UICC (e.g. SIM card or USIM card) to the user's own electronic device. You can insert the received UICC. When the UICC is inserted into the electronic device, the USIM application installed inside the UICC is executed and uses the international mobile subscriber identity (IMSI) value stored inside the UICC and the encryption key value for authentication to the electronic device. Authentication operations may be performed between the server and the communication service provider. If the authentication operation for the electronic device is successful, the electronic device can be provided with a wireless communication service.

An electronic device may support two or more SIMs, and an electronic device that supports two SIMs may be referred to as a “dual SIM electronic device,” and an electronic device that supports multiple SIMs may be referred to as a “multi-SIM” electronic device. It may be referred to as a “(multi) SIM electronic device”. A dual SIM electronic device or a multi-SIM electronic device may support multiple SIMs, each of which may be associated with unique subscription information.

An electronic device in which one transceiver transmits and receives signals associated with two SIMs may be referred to as a “dual SIM dual standby (DSDS) electronic device.” In a DSDS electronic device, when one of two SIMs transmits and/or receives a signal, the other SIM may exist in a standby state. Alternatively, an electronic device in which two SIMs can operate in an active state simultaneously through multiple transceivers may be referred to as a “dual SIM dual active (DSDA) electronic device.”

When an electronic device supports multiple SIMs, a timer may be configured for each of the multiple SIMs. When the timer for each of the multiple SIMs expires, an operation set for timer expiration may be performed. For example, to periodically check network status, multiple timers may be managed by the electronic device. For example, multiple keep alive timers may operate in one electronic device. The keep alive timer may be a timer associated with a service (e.g., a rich communication suite (RCS) service). When the timer time set for each timer expires, each timer operating in the electronic device may perform a set operation according to the expiration of the timer time. For example, the set operation may include the operation of sending and receiving messages with a network (eg, RCS server).

When the electronic device supports multiple SIMs (for example, when the electronic device is a multi-SIM electronic device), a timer may be configured for each of the multiple SIMs. For example, each of multiple SIMs may each correspond to multiple RCS services. If the timers configured for multiple SIMs are not synchronized, the electronic device wakes up from the sleep state and returns to the normal state when the timer time of any one of the configured timers expires. enters, performs the operation set for the corresponding timer in the normal state, then enters the sleep state again, and then, when the time of another one of the configured timers expires, the operation set for the other timer expires. To perform an operation, you must wake up from sleep again.

If timers configured for multiple SIMs are not synchronized, the electronic device may wake up upon expiration of a timer time uniquely set for each of the configured timers, thereby wasting resources (e.g., current consumption).

If the electronic device does not support multiple SIMs and only supports a single SIM (e.g., if the electronic device is a single-SIM electronic device), for each of the multiple services (e.g., RCS services) A timer can be configured. If the timers configured for multiple services are not synchronized, the electronic device wakes up from the sleep state when the timer time of any one of the configured timers expires, enters the normal state, and sets the corresponding timer in the normal state. After performing the specified operation, it enters the sleep state again, and then wakes up from the sleep state again to perform the operation set for the other timer when the time of another one of the configured timers expires. Should be.

If timers configured for multiple services are not synchronized, the electronic device may wake up upon expiration of a timer time uniquely set for each of the configured timers, thereby wasting resources (e.g., current consumption).

According to an embodiment of the present disclosure, an electronic device may include at least one communication circuit, and at least one processor operatively connected to the at least one communication circuit.

According to an embodiment of the present disclosure, the at least one processor, through the at least one communication circuit, provides a first wake-up time point corresponding to a first service from a first external electronic device. 1 may be configured to receive information.

According to an embodiment of the present disclosure, the at least one processor may be further configured to set second information related to a second wake-up time point corresponding to the second service based on the first information.

According to an embodiment of the present disclosure, the at least one processor may be further configured to transmit the second information to a second external electronic device through the at least one communication circuit.

According to an embodiment of the present disclosure, the at least one processor may be further configured to perform a second operation set at the second wake-up time.

According to an embodiment of the present disclosure, the difference between the first wake-up time and the second wake-up time may be less than or equal to a set value.

According to an embodiment of the present disclosure, a method of operating an electronic device may include receiving first information related to a first wake-up time point corresponding to a first service from a first external electronic device.

According to an embodiment of the present disclosure, the operating method may further include setting second information related to a second wake-up time corresponding to the second service based on the first information.

According to an embodiment of the present disclosure, the operating method may further include transmitting the second information to a second external electronic device.

According to an embodiment of the present disclosure, the operation method may further include performing a second operation set at the second wake-up time.

According to an embodiment of the present disclosure, the difference between the first wake-up time and the second wake-up time may be less than or equal to a set value.

According to an embodiment of the present disclosure, a non-transitory computer-readable storage medium is executed by at least one processor of an electronic device, wherein the electronic device receives a first wake corresponding to a first service from a first external electronic device. It may include one or more programs including instructions configured to receive first information related to the up point.

According to an embodiment of the present disclosure, the instructions may be further configured to cause the electronic device to set second information related to a second wake-up time corresponding to the second service based on the first information. there is.

According to an embodiment of the present disclosure, the instructions may be further configured to cause the electronic device to transmit the second information to a second external electronic device.

According to an embodiment of the present disclosure, the instructions may be further configured to cause the electronic device to perform a second operation set at the second wake-up time.

According to an embodiment of the present disclosure, the difference between the first wake-up time and the second wake-up time may be less than or equal to a set value.

FIG. 1A is a block diagram schematically showing an electronic device in a network environment according to an embodiment.
FIG. 1B is a diagram schematically illustrating a network environment including an electronic device according to an embodiment.
FIG. 2 is a diagram schematically illustrating a wireless communication system that provides a profile-based communication connection to an electronic device according to an embodiment.
Figure 3 is a block diagram schematically showing the internal structure of an electronic device according to an embodiment.
Figure 4 is a flowchart illustrating an operation process of an electronic device, according to an embodiment.
FIG. 5 is a flowchart illustrating an operation process of an electronic device, according to an embodiment.
Figure 6 is a signal flow diagram illustrating a process for synchronizing wake-up times in a wireless communication network, according to one embodiment.
Figure 7 is a signal flow diagram illustrating a process for synchronizing wake-up times in a wireless communication network, according to one embodiment.
Figure 8 is a signal flow diagram illustrating a process for synchronizing wake-up times in a wireless communication network, according to one embodiment.
FIG. 9 is a flowchart illustrating an operation process of an electronic device, according to an embodiment.
FIG. 10 is a flowchart illustrating an operation process of an electronic device, according to an embodiment.
FIG. 11 is a flowchart illustrating an operation process of an electronic device, according to an embodiment.

Hereinafter, an embodiment of the present disclosure will be described in detail with reference to the attached drawings. Also, in describing an embodiment of the present disclosure, if it is determined that a detailed description of a related known function or configuration may unnecessarily obscure the gist of an embodiment of the present disclosure, the detailed description will be omitted. In addition, the terms described below are terms defined in consideration of functions in an embodiment of the present disclosure, and may vary depending on the intention or custom of the user or operator. Therefore, the definition should be made based on the contents throughout this specification.

It should be noted that the technical terms used in this specification are merely used to describe specific embodiments and are not intended to limit one embodiment of the present disclosure. Alternatively, technical terms used in this specification, unless specifically defined in a different way in this specification, should be interpreted as meanings commonly understood by those skilled in the art to which this disclosure pertains, and may not be overly inclusive. It should not be interpreted in a literal or excessively reduced sense. Alternatively, if the technical terms used in this specification are incorrect technical terms that do not accurately express the spirit of the present disclosure, they should be replaced with technical terms that can be correctly understood by those skilled in the art. Alternatively, general terms used in an embodiment of the present disclosure should be interpreted as defined in a dictionary or according to the context, and should not be interpreted in an excessively reduced sense.

Alternatively, as used herein, singular expressions include plural expressions unless the context clearly dictates otherwise. In this application, terms such as “consists of” or “includes” should not be construed as necessarily including all of the various components or operations described in the specification, and some of the components or operations may include It may not be included, or it may be interpreted as including additional components or operations.

Alternatively, terms including ordinal numbers, such as first, second, etc., used in this specification may be used to describe various components, but the components should not be limited by the terms. The above terms are used only for the purpose of distinguishing one component from another. For example, a first component may be referred to as a second component, and similarly, the second component may also be referred to as the first component without departing from the scope of the present disclosure.

When a component is referred to as being “connected” or “connected” to another component, it may be directly connected to or connected to the other component, but other components may also exist in between. On the other hand, when it is mentioned that a component is “directly connected” or “directly connected” to another component, it should be understood that there are no other components in between.

Hereinafter, an embodiment according to the present disclosure will be described in detail with reference to the attached drawings. However, identical or similar components will be assigned the same reference numerals regardless of reference numerals, and duplicate descriptions thereof will be omitted. Alternatively, when describing an embodiment of the present disclosure, if it is determined that a detailed description of a related known technology may obscure the gist of the present disclosure, the detailed description will be omitted. Alternatively, it should be noted that the attached drawings are only intended to facilitate easy understanding of the spirit of the present disclosure, and should not be construed as limiting the spirit of the present disclosure by the attached drawings. The spirit of the present disclosure should be construed as extending to all changes, equivalents, and substitutes other than the attached drawings.

Hereinafter, an embodiment of the present disclosure will be described using an electronic device as an example. The electronic device may include a terminal, a mobile station, mobile equipment (ME), or user equipment. It may be referred to as equipment: UE), user terminal (UT), subscriber station (SS), wireless device, handheld device, or access terminal (AT). . Alternatively, in one embodiment of the present disclosure, the electronic device has a communication function, such as a mobile phone, a personal digital assistant (PDA), a smart phone, a wireless modem, or a laptop. It can be a device.

Alternatively, in specifically describing an embodiment of the present disclosure, the rich communication suite (RCS) standard defined by the Global System for Mobile Communications (GSM) Association (GSMA) will be referred to, the main point of the present disclosure can be applied to communication systems applying other standards with similar technical background with slight modifications without significantly departing from the scope of the present disclosure, which is the scope of the present disclosure. This may be possible through the judgment of a person with skilled technical knowledge in the technical field.

FIG. 1A is a block diagram schematically showing an electronic device 101 in a network environment 100 according to an embodiment.

Referring to FIG. 1A, in the network environment 100, the electronic device 101 communicates with the electronic device 102 through a first network 198 (e.g., a short-range wireless communication network) or a second network 199. It is possible to communicate with the electronic device 104 or the server 108 through (e.g., a long-distance wireless communication network). According to one embodiment, the electronic device 101 may communicate with the electronic device 104 through the server 108. According to one embodiment, the electronic device 101 includes a processor 120, a memory 130, an input module 150, an audio output module 155, a display module 160, an audio module 170, and a 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 may include an antenna module 197. In some embodiments, at least one of these components (eg, the connection terminal 178) may be omitted or one or more other components may be added to the electronic device 101. In some embodiments, some of these components (e.g., sensor module 176, camera module 180, or antenna module 197) are integrated into one component (e.g., display module 160). It can be.

The processor 120, for example, executes software (e.g., program 140) to operate at least one other component (e.g., hardware or software component) of the electronic device 101 connected to the processor 120. It can be controlled and various data processing or calculations can be performed. According to one embodiment, as at least part of data processing or computation, processor 120 stores commands or data received from another component (e.g., sensor module 176 or communication module 190) in volatile memory 132. The commands or data stored in the volatile memory 132 can be processed, and the resulting data can be stored in the non-volatile memory 134. According to one embodiment, the processor 120 includes the main processor 121 (e.g., a central processing unit or an application processor) or an auxiliary processor 123 that can operate independently or together (e.g., a graphics processing unit, a neural network processing unit ( It may include 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 a secondary processor 123, the secondary processor 123 may be set to use lower power than the main processor 121 or be specialized for a designated function. You can. The auxiliary processor 123 may be implemented separately from the main processor 121 or as part of it.

The auxiliary processor 123 may, for example, act on behalf of the main processor 121 while the main processor 121 is in an inactive (e.g., sleep) state, or while the main processor 121 is in an active (e.g., application execution) state. ), together with the main processor 121, at least one of the components of the electronic device 101 (e.g., the display module 160, the sensor module 176, or the communication module 190) At least some of the functions or states related to can be controlled. According to one embodiment, co-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). there is. According to one embodiment, the auxiliary processor 123 (eg, neural network processing device) may include a hardware structure specialized for processing artificial intelligence models. Artificial intelligence models can be created through machine learning. For example, such learning may be performed in the electronic device 101 itself, where artificial intelligence is performed, or may be performed through a separate server (e.g., server 108). Learning algorithms may include, for example, supervised learning, unsupervised learning, semi-supervised learning, or reinforcement learning, but It is not limited. An artificial intelligence model may include multiple artificial neural network layers. Artificial neural networks include deep neural network (DNN), convolutional neural network (CNN), recurrent neural network (RNN), restricted boltzmann machine (RBM), belief deep network (DBN), bidirectional recurrent deep neural network (BRDNN), It may be one of deep Q-networks or a combination of two or more of the above, but is not limited to the examples described above. In addition to hardware structures, artificial intelligence models may additionally or alternatively include software structures.

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

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

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

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

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

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

The sensor module 176 detects the operating state (e.g., power or temperature) of the electronic device 101 or the external environmental state (e.g., user state) and generates an electrical signal or data value corresponding to the detected state. can do. According to one embodiment, the sensor module 176 includes, for example, a gesture sensor, a gyro sensor, an air pressure sensor, a magnetic sensor, an acceleration sensor, a grip sensor, a proximity sensor, a color sensor, an IR (infrared) sensor, a biometric sensor, It may include a temperature sensor, humidity sensor, or light sensor.

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

The connection terminal 178 may include a connector through which the electronic device 101 can be physically connected to an external electronic device (eg, the electronic device 102). According to one embodiment, the connection terminal 178 may include, for example, an HDMI connector, a USB connector, an SD card connector, or an audio connector (eg, a headphone connector).

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

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

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

The battery 189 may 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.

Communication module 190 is configured to provide a direct (e.g., wired) communication channel or wireless communication channel between electronic device 101 and an external electronic device (e.g., electronic device 102, electronic device 104, or server 108). It can support establishment and communication through established communication channels. Communication module 190 operates independently of processor 120 (e.g., an application processor) and may include one or more communication processors that support direct (e.g., wired) communication or wireless communication. According to one embodiment, the communication module 190 is a wireless communication module 192 (e.g., a cellular communication module, a short-range wireless communication module, or a global navigation satellite system (GNSS) communication module) or a wired communication module 194 (e.g., : LAN (local area network) communication module, or power line communication module) may be included. Among these communication modules, the corresponding communication module is a first network 198 (e.g., a short-range communication network such as Bluetooth, Wi-Fi (wireless fidelity) direct, or IrDA (infrared data association)) or a second network 199. It may communicate with an external electronic device 104 through (e.g., a legacy cellular network, a 5G network, a next-generation communication network, the Internet, or a long-distance communication network such as a computer network (e.g., LAN or WAN)). These various types of communication modules may be integrated into one component (e.g., a single chip) or may be implemented as a plurality of separate components (e.g., multiple chips). The wireless communication module 192 uses subscriber information (e.g., International Mobile Subscriber Identifier (IMSI)) stored in the subscriber identification module 196 within a communication network such as the first network 198 or the second network 199. The electronic device 101 can be confirmed or authenticated.

The wireless communication module 192 may support 5G networks after 4G networks and next-generation communication technologies, for example, NR access technology (new radio access technology). NR access technology provides high-speed transmission of high-capacity data (eMBB (enhanced mobile broadband)), minimization of terminal power and access to multiple terminals (mMTC (massive machine type communications)), or high reliability and low latency (URLLC (ultra-reliable and low latency). -latency communications)) can be supported. The wireless communication module 192 may support high frequency bands (eg, mmWave bands), for example, to achieve high data rates. The wireless communication module 192 uses various technologies to secure performance in high frequency bands, for example, beamforming, massive array multiple-input and multiple-output (MIMO), and full-dimensional multiplexing. It can support technologies such as input/output (FD-MIMO: full dimensional MIMO), array antenna, analog beam-forming, or large scale antenna. The wireless communication module 192 may support various requirements specified in the electronic device 101, an external electronic device (e.g., electronic device 104), or a network system (e.g., second network 199). According to one embodiment, the wireless communication module 192 supports Peak data rate (e.g., 20 Gbps or more) for realizing eMBB, loss coverage (e.g., 164 dB or less) for realizing mmTC, or U-plane latency (e.g., 164 dB or less) for realizing URLLC. Example: Downlink (DL) and uplink (UL) each of 0.5 ms or less, or round trip 1 ms or less) can be supported.

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

According to one embodiment, the antenna module 197 may form a mmWave antenna module. According to one embodiment, a mmWave antenna module includes: a printed circuit board, an RFIC disposed on or adjacent to a first side (e.g., bottom side) of the printed circuit board and capable of supporting a designated high frequency band (e.g., mmWave band); and a plurality of antennas (e.g., array antennas) disposed on or adjacent to the second side (e.g., top or side) of the printed circuit board and capable of transmitting or receiving signals in the designated high frequency band. You can.

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

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

An electronic device according to an embodiment disclosed in this document may be of various types. Electronic devices may include, for example, portable communication devices (e.g., smartphones), computer devices, portable multimedia devices, portable medical devices, cameras, wearable devices, or home appliances. Electronic devices according to embodiments of this document are not limited to the above-mentioned devices.

An embodiment of this document and the terms used herein are not intended to limit the technical features described in this document to a specific embodiment, and should be understood to include various changes, equivalents, or substitutes for the embodiment. In connection with the description of the drawings, similar reference numbers may be used for similar or related components. The singular form of a noun corresponding to an item may include one or more of the above items, unless the relevant context clearly indicates otherwise. As used herein, “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 “A Each of phrases such as “at least one of , B, or C” may include any one of the items listed together in the corresponding phrase, or any possible combination thereof. Terms such as "first", "second", or "first" or "second" may be used simply to distinguish one component from another, and to refer to that component in other respects (e.g., importance or order) is not limited. One (e.g., first) component is said to be “coupled” or “connected” to another (e.g., second) component, with or without the terms “functionally” or “communicatively.” When mentioned, it means that any of the components can be connected to the other components directly (e.g. wired), wirelessly, or through a third component.

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

An embodiment of the present document is one or more instructions stored in a storage medium (e.g., built-in memory 136 or external memory 138) that can be read by a machine (e.g., electronic device 101). It may be implemented as software (e.g., program 140) including these. For example, a processor (e.g., processor 120) of a device (e.g., electronic device 101) may call at least one command among one or more commands stored from a storage medium and execute it. This allows the device to be operated to perform at least one function according to the at least one instruction called. The one or more instructions may include code generated by a compiler or code that can be executed by an interpreter. A storage medium that can be read by a device may be provided in the form of a non-transitory storage medium. Here, 'non-transitory' only means that the storage medium is a tangible device and does not contain signals (e.g. electromagnetic waves), and this term refers to cases where data is semi-permanently stored in the storage medium. There is no distinction between temporary storage cases.

According to one embodiment, a method according to an embodiment disclosed in this document may be provided and included in a computer program product. Computer program products are commodities and can be traded between sellers and buyers. The computer program product may be distributed in the form of a machine-readable storage medium (e.g. compact disc read only memory (CD-ROM)) or via an application store (e.g. Play Store ^TM ) or on two user devices (e.g. It can be distributed (e.g. downloaded or uploaded) directly between smart phones) or online. In the case of online distribution, at least a portion of the computer program product may be at least temporarily stored or temporarily created in a machine-readable storage medium, such as the memory of a manufacturer's server, an application store's server, or a relay server.

According to one embodiment, each component (e.g., module or program) of the above-described components may include a single or multiple entities, and some of the multiple entities may be separately placed in other components. . According to one embodiment, one or more of the above-described corresponding components or operations may be omitted, or one or more other components or operations may be added. Alternatively or additionally, multiple components (eg, modules or programs) may be integrated into a single component. In this case, the integrated component may perform one or more functions of each component of the plurality of components in the same or similar manner as those performed by the corresponding component of the plurality of components prior to the integration. . According to one embodiment, operations performed by a module, program, or other component may be executed sequentially, in parallel, iteratively, or heuristically, or one or more of the operations may be executed in a different order, omitted, or , or one or more other operations may be added.

FIG. 1B is a diagram schematically showing a network environment 100 including an electronic device 101 according to an embodiment.

Referring to FIG. 1B, a network according to an embodiment of the present disclosure may include an electronic device 101, a first rich communication suite (RCS) server 111a, or a second RCS server 112a. there is. The first RCS server 111a may be a server that provides the first RCS service. The second RCS server 111b may be a server that provides a second RCS service. Figure 1b shows a case where the first RCS server 111a providing the first RCS service and the second RCS server 111b providing the second RCS service are implemented separately, but the first RCS server 111a and The second RCS server 111b may be integrated into one RCS server, and one integrated RCS server may provide the first RCS service and the second RCS service.

According to one embodiment, the electronic device 101 may be a multi-SIM (multi-SIM) electronic device that supports multiple SIMs. If the electronic device 101 supports two SIMs, the electronic device 101 may be a dual SIM dual standby (DSDS) electronic device or a dual SIM dual active (DSDA) electronic device. there is. The electronic device 101 may include two SIMs (eg, a first SIM 111 and a second SIM 112). There are no restrictions on the types of each of the first SIM 111 and the second SIM 112. For example, each of the first SIM 111 and the second SIM 112 may be a removable SIM (rSIM) (eg, a SIM card). The electronic device 101 may include a first slot (not shown) and a second slot (not shown) to accommodate the first SIM 111 and the second SIM 112, respectively. In this case, the fact that the electronic device 101 includes the first SIM 111 and the second SIM 112 means that the first SIM 111 and the second SIM 112 are mounted on the electronic device 101. Those skilled in the art will understand that this may mean a state in which the first SIM 111 and the second SIM 112 are included in the electronic device 101. For another example, at least one of the first SIM 111 and the second SIM 112 may include an embedded subscriber identity module (eSIM). eSIM may also be referred to as an embedded universal integrated circuit card (UICC) (eUICC).

According to one embodiment, the first SIM 111 is a SIM subscribed to the communication service provider of the first RCS server 111a, and the electronic device 101 uses the first SIM 111 to connect the first RCS server 111a. You can receive RCS services by accessing ). The second SIM 112 is a SIM subscribed to the communication service provider of the second RCS server 112a, and the electronic device 101 provides RCS service by connecting to the second RCS server 112a using the second SIM 112. can be provided.

According to one embodiment, the electronic device 101 may be a single-SIM (single-SIM) electronic device that supports only a single SIM. Even if the electronic device 101 supports only a single SIM, it can provide multiple RCS services, and each of the multiple RCS services can be provided through a separate app.

FIG. 2 is a diagram schematically illustrating a wireless communication system that provides a profile-based communication connection to an electronic device according to an embodiment.

Referring to FIG. 2, a wireless communication system 200 according to an embodiment includes an electronic device 101 (e.g., the electronic device 101 of FIG. 1A or 1B) and a subscription manager discovery service (SM). -DS) server 210, subscription manager data preparation plus (SM-DP+) server 220, mobile network operator (MNO) server 230, and/or communication service server It may include (240).

In one embodiment, the MNO may be a telecommunication carrier. According to one embodiment, the electronic device 101 may include an eSIM 201. Although not shown for convenience of explanation, the electronic device 101 may include at least two slots that can accommodate at least two rSIMs. Alternatively, the electronic device 101 may be implemented to include one slot that can accommodate at least two eSIMs and one rSIM. According to one embodiment, the electronic device 101 may include or accommodate N SIMs (eSIM or rSIM) (N is an integer of 1 or more), and perform a switching operation so that some of the N SIMs can be used. can be performed. There is no limit to the combination of N SIMs, and there is no limit to the value of N.

According to one embodiment, the eSIM 201 may be inserted into the electronic device 101, provided integrally with the electronic device 101, or implemented to be accessible to the electronic device 101. According to one embodiment, the eSIM 201 is configured to allow the electronic device 101 to communicate with a telecommunication carrier ( Example: Authentication operations can be performed with the MNO) server. According to one embodiment, the eSIM 201 may be referred to as a subscriber identity module (SIM) card in the case of the global system for mobile communications (GSM), and may be used as a broadband code division multiple access ( For wideband code division multiple access (WCDMA), long term evolution (LTE), and/or new radio (NR) methods, it will be referred to as a universal subscriber identity module (USIM) card. You can. For example, when the user of the electronic device 101 subscribes to a wireless communication service provided by a telecommunication service provider, the electronic device 101 may use information in the eSIM 201 (e.g., international mobile subscriber identity: Authentication operations can be performed with the telecommunication service provider's server using the (IMSI) value) and the encryption key for authentication (e.g., K value).

If the authentication operation for the electronic device 101 is successful, the electronic device 101 can use a wireless communication service. For example, the authentication operation may be an authentication operation based on an authentication and key agreement (AKA) protocol. In one embodiment, the authentication operation may be based on the AKA protocol, as well as other authentication methods.

According to one embodiment, the eSIM 201 may be manufactured in the form of a dedicated card for a designated communication service provider at the request of the corresponding communication service provider. The eSIM 201 is preloaded with authentication information (e.g., USIM application and subscriber ID (e.g., IMSI)) and/or encryption key (e.g., a known K value or Ki value) for network access of the corresponding communication service provider. There may be. Applications (or information) in the eSIM 201 may be installed, modified, deleted, or updated based on methods such as OTA (over the air), when necessary.

According to one embodiment, the eSIM 201 may download and/or store information for providing communication services in the form of a profile. According to one embodiment, the profile may be installed or stored in the process of manufacturing the eSIM 201, or may be downloaded by the electronic device 101 based on an OTA method and then installed or stored in the eSIM 201. there is.

In one embodiment, the profile may include a provisioning profile and an operational profile. Even if the provisioning profile is not installed, the electronic device 101 may download the operational profile through a short-distance connection based on Wi-Fi or an Internet connection. According to one embodiment, the provisioning profile does not necessarily need to be installed on the electronic device 101. For example, the operational profile may be a profile that includes subscriber identification information (e.g., IMSI) of the user of the electronic device 101, and the provisioning profile may be a profile that includes subscriber identification information or subscriber identification information (e.g., IMSI) in the electronic device 101. Information for downloading a profile (hereinafter also referred to as "first operational profile") including a profile (hereinafter also referred to as "first subscriber identification information") (hereinafter also referred to as "first information") may be referred to) may be included.

The electronic device 101 may download the first operational profile based on the first information included in the provisioning profile in the eSIM 201.

According to one embodiment, the electronic device 101 is installed in the eSIM 201, or an operational profile (hereinafter, may be referred to as a “second operational profile”) stored in the eSIM 201. Communication services can be provided using the subscriber identification information (hereinafter also referred to as “second subscriber identification information”) included in the . For example, a profile containing subscriber identification information may be a SIM profile.

According to one embodiment, the operational profile includes not only subscriber identification information, but also various information related to the subscriber (e.g., network access authentication information, phone book, personal information (e.g., short message service (SMS)), subscribed communication information). Subscriber authentication and traffic security key generation when accessing a wireless communications network (e.g., GSM, WCDMA, LTE, and/or NR wireless networks), including carrier name, available services, available data volume, rates, service delivery speeds, or It may further include information that enables safe use of wireless communication services.

According to one embodiment, the first information for downloading data (e.g., a first operational profile) including the first subscriber identification information is a first communication connection designated for downloading the first operational profile. It may contain communication session information for. For example, the communication session information includes access information to the SM-DS server 210 for downloading the first operational profile, or information about a communication service provider network available for access to the SM-DS server 210. It can be included.

According to one embodiment, the SM-DS server 210 provides the electronic device 101 with an address of the SM-DP+ server 220 that can download the first operational profile based on the provisioning profile. can do.

According to one embodiment, the SM-DP+ server 220 is a profile providing server, an off-card entity of profile domain, a profile encryption server, a profile creation server, and a profile provisioner. , or it may be a profile provider. The SM-DP+ server 220 performs an operation to establish a first communication connection 22 with the electronic device 101 through a wireless communication network based on a provisioning profile-based first communication connection request from the electronic device 101. This can be done, and the first operational profile can be provided to the electronic device 101 through the first communication connection 22.

According to one embodiment, the wireless communication network may be a designated node of a wireless communication network. For example, the wireless communication network may be a base station, a subscriber information management node, or a mobility management node of the wireless communication network. According to one embodiment, the wireless communication network may include a home location register (HLR) and/or authentication center (AuC) server that the electronic device 101 accesses to perform subscriber authentication functions. According to one embodiment, after successful authentication, the electronic device 101 may be connected to a communication service server 240 that can provide various communication services such as voice communication or data communication.

According to one embodiment, the MNO server 230 may be a server associated with a mobile communication network operator. According to one embodiment, the MNO server 230 prepares at least one profile (or profile package) (e.g., first operational profile) associated with at least one subscriber identification information (e.g., first subscriber identification information). You can request the SM-DP+ server 220 to do something. In one embodiment, the MNO server 230 may transmit information associated with the first operational profile to the SM-DP+ server 220. According to one embodiment, the MNO server 230 may transmit a signal for updating and managing the first operational profile to the SM-DP+ server 220. The MNO server 230 may allow a second communication connection 24 between the electronic device 101 and the communication service server 240 through the second operational profile installed on the eSIM 201 of the electronic device 101. there is.

According to one embodiment, the communication service server 240 may be a server that provides a communication service. According to one embodiment, a communication service may be a service associated with transmitting or receiving data through a wireless communication network. According to one embodiment, the communication service may include downloading an operational profile (e.g., a first operational profile including first subscriber identifying information) and transmitting or receiving other profiles (or data) that do not include subscriber identifying information. May include services related to . For example, the communication service server 240 may include various service servers associated with data transmission and reception, such as servers associated with each of various applications, a push server, a search server, or a market server. In one embodiment, a communication service provided by the communication service server 240 may include various services such as data transmission and reception by an application, notification reception, push reception, link reception and connection, or service request.

According to one embodiment, when the electronic device 101 requests a service associated with transmission or reception of a profile (or data) that does not include subscriber identification information, the electronic device 101 sends the communication service server 240 based on the second operational profile. and a second communication connection 24 can be made.

According to one embodiment, the SM-DS server 210, SM-DP+ server 220, MNO server 230, or communication service server 240 are only examples of servers for performing the corresponding function, and SM- The DS server 210, SM-DP+ server 220, MNO server 230, or communication service server 240 may also be called other names. According to one embodiment, each of the SM-DS server 210, SM-DP+ server 220, MNO server 230, or communication service server 240 may be composed of one or more servers. Some or all of the SM-DS server 210, SM-DP+ server 220, MNO server 230, or communication service server 240 may be implemented as one integrated server.

According to one embodiment, an electronic device (e.g., the electronic device 101 in FIGS. 1A, 1B, or 2) includes a display (e.g., the display module 160 in FIG. 1A) and a communication module (e.g., the communication module in FIG. 1A). Module 190), an embedded subscriber identification module (e.g., FIG. Subscriber identification module 196 in 1A or eSIM 201 in FIG. 2), memory (e.g., memory 130 in FIG. 1A or memory 211 in FIG. 2), and a processor electrically connected to the display, communication module, and memory. (For example, the processor 120 of FIG. 1A).

In one embodiment, the processor performs a first communication connection to download data including first subscriber identification information based on the first information through a communication module, and identifies the first subscriber while performing the first communication connection. When a request is made to transmit or receive data that does not contain information, the first communication connection may be terminated and a second communication connection based on second subscriber identification information may be performed to transmit or receive data.

According to one embodiment, the first information may include a provisioning profile, and data including the first subscriber identification information may include a first operational profile.

According to one embodiment, when performing a first communication connection and requesting transmission or reception of data, if the second subscriber identification information does not exist in the subscriber identification module, the processor displays a second subscriber identification information corresponding to the second subscriber identification information. Can be configured to indicate that an operational profile does not exist.

According to one embodiment, the processor may be further configured to display a purchase screen associated with the second operational profile when the second operational profile does not exist.

According to one embodiment, the processor may be configured to perform a second communication session based on a previously used second operational profile.

According to one embodiment, the processor may be configured to perform a second communication session based on a second operational profile selected by the user.

According to one embodiment, the processor may be configured to display at least one indicator indicating a first communication connection based on a provisioning profile through a display.

According to one embodiment, the at least one indicator includes at least one of a service provider name (SPN), a radio access technology (RAT), and a received signal strength indicator (RSSI). can do.

According to one embodiment, the processor may be configured to select a provisioning profile associated with a network being connected through a communication module.

According to one embodiment, the processor selects a provisioning profile associated with the network being connected based on at least one of a public land mobile network (PLMN) identifier, a mobile country code (MCC), and area information of the network being connected through a communication module. It can be configured.

FIG. 3 is a block diagram schematically showing an example of the internal structure of an electronic device 101 according to an embodiment.

Referring to FIG. 3, the electronic device 101 may include at least one of a processor 120, a communication processor 310, an RF circuit 320, a first SIM 331, or a second SIM 341. . At least one of the first SIM 331 or the second SIM 341 may be a removable SIM (removable SIM: rSIM). In this case, the electronic device 101 may further include at least one slot for connection to the rSIM. In one embodiment, the rSIM is removable from the electronic device 101 and is not necessarily included in the electronic device 101. At least one of the first SIM 331 or the second SIM 341 may be an embedded subscriber identity module (eSIM). rSIM may be referred to as “physical SIM (pSIM).”

According to one embodiment, communication processor 310 may support a specified number (eg, two) of SIMs. Although not shown in FIG. 3, the electronic device 101 may include a number of SIMs (eg, two rSIMs and one eSIM) exceeding a specified number. In this case, the electronic device 101 may further include a switch (not shown in FIG. 3) for switching SIM connections between a plurality of SIMs and the communication processor 310.

According to one embodiment, the communication processor 310 may support establishment of a communication channel in a band to be used for wireless communication and network communication through the established communication channel. For example, the communication processor 310 may be used for ^2nd generation (2G) network communication, ^3rd generation (3G) network communication, ^4th generation (4G) network communication, or 5th generation network communication. (5 ^th generation: 5G) Can support at least one of network communications.

The RF circuit 320 is at least one of a radio frequency integrated circuit (RFIC), a radio frequency front end (RFFE) module, or an antenna module (e.g., the antenna module 197 in FIG. 1). It can contain one. The RF circuit 320 may convert data (eg, a baseband signal) output from the communication processor 310 into an RF signal and transmit the RF signal through an antenna module. The RF circuit 320 may convert the RF signal received through the antenna module into a baseband signal and transmit the baseband signal to the communication processor 310. The RF circuit 320 may process an RF signal or a baseband signal based on a communication method supported by the communication processor 310, and there is no limitation on the type of the RF circuit 320. According to one embodiment, the interface between components may be a general purpose input/output (GPIO), universal asynchronous receiver/transmitter (UART) (e.g., high speed-UART (HS-UART)), or peripheral component interconnect bus express (PCIe). ) It can be implemented as an interface, and there are no restrictions on the interface between components. Alternatively, at least some of the components may exchange control information or packet data information using shared memory.

Figure 3 shows a case where the processor 120 and the communication processor 310 are implemented as separate hardware, but this is merely an example. Not only may the processor 120 and the communication processor 310 be implemented as separate hardware, but the processor 120 and the communication processor 310 may also be implemented on a single chip.

The communication processor 310 may obtain stored information from the first SIM 331 and the second SIM 341. For example, the information stored may include integrated circuit card identifier (ICCID), IMSI, home public land mobile network (HPLMN) related information, or mobile subscriber international ISDN number (MSISIDN). ) may include at least one of The stored information may be referred to as an elementary file (EF). The communication processor 310 performs network communication corresponding to the first SIM 331 and/or the second SIM 341 based on the information stored in the acquired first SIM 331 and/or the second SIM 341. The authentication procedure for this can be performed through the RF circuit 320. If authentication is successful, the communication processor 310 may perform network communication corresponding to the first SIM 331 and/or the second SIM 341 through the RF circuit 320.

According to one embodiment, the communication processor 310 may perform dual SIM network communications according to the first SIM 331 or the second SIM 341. Depending on the implementation of the RF circuit 320, the dual SIM's network communications may be performed in either DSDS mode or DSDA mode.

According to one embodiment, the communication processor 310 may include two stacks (e.g., a stack according to ISO7816) for processing SIM, and includes a first SIM 331 and a second SIM 332. ) can be connected to two stacks. For example, a first slot 330 may be connected to one stack, and a second slot 340 may be connected to another stack.

According to an embodiment of the present disclosure, an electronic device that manages wake up timings for services and a method of operating the same may be provided.

According to an embodiment of the present disclosure, an electronic device (electronic device 101 of FIGS. 1A, 1B, 2, or 3) includes at least one communication circuit (communication module 190 of FIG. 1A, or RF circuit 320 in Figure 3), and at least one processor (Figure 1 or It may include the processor 120 of FIG. 3 or the communication processor 310 of FIG. 3.

According to an embodiment of the present disclosure, the at least one processor (processor 120 of FIG. 1A or FIG. 3, or communication processor 310 of FIG. 3) includes the at least one communication circuit (communication module of FIG. 1A) 190, or the RF circuit 320 in FIG. 3), corresponding to the first service from the first external electronic device (server 108 in FIG. 1A, or first RCS server 111a in FIG. 1B). It may be configured to receive first information related to a first wake up time.

According to an embodiment of the present disclosure, the at least one processor (processor 120 of FIG. 1A or FIG. 3, or communication processor 310 of FIG. 3) provides a second service based on the first information. It may be further configured to set second information related to a corresponding second wake-up time point.

According to an embodiment of the present disclosure, the at least one processor (processor 120 of FIG. 1A or FIG. 3, or communication processor 310 of FIG. 3) includes the at least one communication circuit (communication module of FIG. 1A) To transmit the second information to a second external electronic device (server 108 in FIG. 1A or second RCS server 112a in FIG. 1B) via (190) or RF circuit 320 in FIG. 3). It can be configured further.

According to an embodiment of the present disclosure, the at least one processor (processor 120 of FIG. 1A or FIG. 3, or communication processor 310 of FIG. 3) performs a second operation set at the second wake-up time. It may be further configured to perform.

According to an embodiment of the present disclosure, the difference between the first wake-up time and the second wake-up time may be less than or equal to a set value.

According to an embodiment of the present disclosure, the at least one processor (processor 120 of FIG. 1A or FIG. 3, or communication processor 310 of FIG. 3) is connected to the first external electronic device (server of FIG. 1A). 108), or may be configured to set the first information received from the first RCS server 111a of FIG. 1B as the second information.

According to an embodiment of the present disclosure, before transmitting the second information, the at least one processor (processor 120 of FIG. 1A or FIG. 3, or communication processor 310 of FIG. 3) Through a communication circuit (communication module 190 in FIG. 1A or RF circuit 320 in FIG. 3), the second external electronic device (server 108 in FIG. 1A or second RCS server 112a in FIG. 1B) )) may be configured to receive third information related to the second wake-up time corresponding to the second service.

According to an embodiment of the present disclosure, the at least one processor (processor 120 of FIG. 1A or FIG. 3, or communication processor 310 of FIG. 3) based on the first information and the third information. It may be configured to set the second information.

According to an embodiment of the present disclosure, the first information may be a timer value of a first timer used to set the first wake-up time.

According to an embodiment of the present disclosure, the second information may be a first timer value of a second timer used to set the second wake-up time.

According to an embodiment of the present disclosure, the third information may be a second timer value of a second timer used to set the second wake-up time.

According to an embodiment of the present disclosure, the first timer value of the second timer is set to the timer value of the first timer or the second timer value of the second timer, or the timer value of the first timer and the It may be set to an integer multiple of any one of the second timer values of the second timer.

According to an embodiment of the present disclosure, the at least one processor (processor 120 of FIG. 1A or FIG. 3, or communication processor 310 of FIG. 3) wakes up at the first wake-up time and sets the first processor. It may be further configured to perform operation 1.

According to an embodiment of the present disclosure, the first operation is a keep alive request to the first external electronic device (the server 108 in FIG. 1A or the first RCS server 111a in FIG. 1B). ) An operation of transmitting a message, and a keep alive response (keep) from the first external electronic device (the server 108 in FIG. 1A or the first RCS server 111a in FIG. 1B) in response to the keep alive message. It may include the operation of receiving an alive response) message.

According to an embodiment of the present disclosure, the second operation includes a keep alive request from the second external electronic device (the server 108 in FIG. 1A or the second RCS server 112a in FIG. 1B). An operation of receiving a message, and sending, to the second external electronic device (the server 108 of FIG. 1A or the second RCS server 112a of FIG. 1B), a keep alive response in response to the keep alive message. ) may include the operation of sending a message.

According to an embodiment of the present disclosure, the first external electronic device (server 108 in FIG. 1A, or first RCS server 111a in FIG. 1B) and the second external electronic device (server 108 in FIG. 1A) ) or the second RCS server 112a in FIG. 1B) may be integrated into one external electronic device.

According to an embodiment of the present disclosure, the second operation includes receiving a keep alive request message from the one external electronic device, and sending the keep alive message to the one external electronic device. It may include transmitting a keep alive response message in response.

According to an embodiment of the present disclosure, the keepalive request message may include information related to the first service and information related to the second service.

According to an embodiment of the present disclosure, the first external electronic device (server 108 in FIG. 1A or first RCS server 111a in FIG. 1B) is configured to use the at least one processor (processor in FIG. 1A or FIG. 3). A plurality of subscriber identity modules (SIMs) connected to 120 (or communication processor 310 of FIG. 3) (subscriber identity module 196 of FIG. 1, or first SIM 331 of FIG. 3) Alternatively, it may correspond to the first SIM (the subscriber identification module 196 of FIG. 1 or the first SIM 331 of FIG. 3) among the second SIMs 341.

According to an embodiment of the present disclosure, the second external electronic device (server 108 in FIG. 1A or second RCS server 112a in FIG. 1B) uses a second SIM (the subscriber in FIG. 1) among the plurality of SIMs. It may correspond to the identification module 196, or the second SIM 341 in FIG. 3).

Figure 4 is a flowchart illustrating an operation process of an electronic device, according to an embodiment.

Referring to FIG. 4 , an electronic device (e.g., electronic device 101 of FIG. 1A, 1B, FIG. 2, or FIG. 3) (e.g., processor 120 of FIG. 1A or FIG. 3, or communication processor of FIG. 3) (310)) is a first wake up time point corresponding to a first service (e.g., a first RCS service) from a first external electronic device (e.g., a first RCS server) in operation 411. Information (e.g., parameter value of parameter “keep”) may be received. In one embodiment, the electronic device may be a multi-SIM electronic device and may include a first SIM and a second SIM. In one embodiment, the first RCS server (eg, server 108 in FIG. 1A or first RCS server 111a in FIG. 1B) may be a first external electronic device corresponding to the first SIM of the electronic device. In one embodiment, the first SIM is a SIM subscribed to the communication service provider of the first RCS server and may correspond to the first service (eg, the first RCS service).

A detailed description of operation 411, in which the electronic device receives the parameter value of parameter keep from the first RCS server, may be as follows.

The electronic device may transmit a register message to the first RCS server as it initiates an Internet protocol (IP) multimedia subsystem (IMS) registration procedure with the first RCS server. The registration message may be a session initiation protocol (SIP) registration message and may include the parameter keep, which is a Via header field parameter. The parameter keep is used to send a keep alive message (e.g. keep alive request message) from a SIP entity (e.g. electronic device) to an adjacent downstream SIP entity (e.g. first RCS server). The intention to transmit an alive request message can be indicated. In one embodiment, the adjacent downstream SIP entity may be the adjacent SIP entity to which a SIP request message (e.g., keepalive request message) is sent.

The first RCS server may receive a registration message sent from the electronic device, and may transmit a 200 OK message to the electronic device based on the received registration message. The first RCS server may confirm that the electronic device intends to transmit a keepalive request message based on the parameter keep included in the received registration message. The first RCS server includes a parameter keep with a parameter value to indicate that it is willing to receive a keepalive message (e.g., a keepalive request message) from an adjacent upstream SIP entity (e.g., an electronic device). A 200 OK message can be sent. In one embodiment, the parameter value of the parameter keep may be information related to the first wake-up time of the electronic device, corresponding to the first RCS service. For example, the electronic device may configure a timer (e.g., a first timer) for the first RCS service, and set the timer value of the first timer to the parameter value of the parameter keep included in the 200 OK message. . In this case, the electronic device may wake up when the first timer expires and perform the set first operation. In one embodiment, the first operation includes transmitting a keep alive request message to the first RCS server and receiving a keep alive response message, which is a response message to the keep alive request message, from the first RCS server. Can include actions.

In one embodiment, the adjacent upstream SIP entity may be the adjacent SIP entity from which the SIP request message (e.g., keepalive request message) is received. The parameter value of the parameter keep may indicate the keep alive frequency. For example, the keepalive frequency may be given in seconds or minutes, and the electronic device may have to transmit a keepalive request message based on the parameter value of the parameter keep. The 200 OK message may include a Via header field containing a parameter keep with a parameter value. As an example, in Figure 4, it is assumed that the parameter value of the parameter keep is set to 7 minutes. As the electronic device receives a 200 OK message including a parameter keep with a parameter value from the first RCS server, the IMS registration procedure between the electronic device and the first RCS server may be completed.

As the IMS registration procedure between the electronic device and the first RCS server is completed, the electronic device may set the timer value of the first timer configured for the first RCS server to the parameter value of parameter keep and start the first timer. You can. As the first timer starts, the electronic device may transition to a sleep state.

The timer value of the first timer may indicate the expiration time of the first timer, and the expiration time may mean the time from when the timer starts to when it expires. For example, if the expiration time of the first timer is 7 minutes, the first timer may expire 7 minutes after the start of the first timer. After starting the first timer, the electronic device may enter a sleep state. The sleep state may refer to at least one of a state in which at least some of at least one function of the electronic device is restricted compared to the normal state, or a state in which power consumption is less than the normal state. The sleep state may be referred to as an “inactive state” or a “restricted state” depending on the implementation. In a sleep state, only some of at least one function of the electronic device may be restricted, or at least one function may be suspended entirely. Wake up may mean that an electronic device transitions from a sleep state to a normal state. If the electronic device is required to perform another operation, the electronic device may not enter the sleep state and the first timer may be started.

In operation 413, based on the first information, the electronic device provides second information (e.g., a parameter value of parameter “rkeep”) related to a second wake-up time point corresponding to a second service (e.g., a second RCS service). can be set. In one embodiment, the parameter rkeep having a parameter value may be included in a registration message that the electronic device transmits to a second external electronic device (eg, a second RCS server) corresponding to the second RCS service. In one embodiment, the second RCS server (e.g., the server 108 in FIG. 1A or the second RCS server 111b in FIG. 1B) may be a second external electronic device corresponding to the second SIM of the electronic device. In one embodiment, the second SIM is a SIM subscribed to the communication service provider of the second RCS server and may correspond to the second RCS service.

A detailed description of operation 413 in which the electronic device sets the parameter value of the parameter rkeep may be as follows.

The electronic device may set the parameter value of the parameter keep (e.g., 7 minutes) included in the 200 OK message received from the first RCS server as the parameter value of the parameter rkeep. For example, the keepalive frequency may be given in seconds or minutes, and the second RCS server may have to transmit a keepalive request message based on the parameter value of the parameter rkeep. In FIG. 4, the case where the electronic device sets the parameter value of parameter keep received from the first RCS server as the parameter value of parameter rkeep is described as an example, but the electronic device sets the parameter value of parameter keep received from the first RCS server. The parameter value of parameter rkeep can also be set to a parameter value other than the value.

In operation 415, the electronic device may transmit second information (e.g., a parameter value of parameter rkeep) to a second external electronic device (e.g., a second RCS server). A detailed description of operation 415, in which the electronic device transmits the parameter value of the parameter rkeep, may be as follows.

The electronic device may transmit a registration message to the second RCS server as it initiates a negotiation-based IMS registration procedure with the second RCS server. In one embodiment, the negotiation-based IMS registration procedure may be based on the parameter rkeep rather than the parameter keep, unlike the IMS registration procedure. In one embodiment, the registration message may be a SIP registration message and may include the parameter rkeep, which is a Via header field parameter. The parameter rkeep may indicate the intention of a SIP entity (e.g., an electronic device) to receive a keepalive message (e.g., a keepalive request message) from a neighboring downstream SIP entity (e.g., a second RCS server) of the SIP entity. The parameter rkeep may have a parameter value, and the parameter value of the parameter rkeep may indicate the keepalive frequency.

In one embodiment, the parameter value of parameter rkeep may be information related to the second wake-up time of the electronic device, corresponding to the second RCS service. For example, the electronic device may configure a timer (e.g., a second timer) for the second RCS service, and set the timer value of the second timer to the parameter value of the parameter rkeep included in the registration message. In this case, the electronic device may perform the second operation set with the second RCS server. In one embodiment, the second operation may include receiving a keepalive request message from the second RCS server and transmitting a keepalive response message, which is a response message to the keepalive request message, to the second RCS server. .

In operation 417, the electronic device may perform a second operation with a second external electronic device. A detailed description of operation 417, in which an electronic device performs a second operation with a second external electronic device, may be as follows.

In operation 415, the electronic device may transmit a registration message including a parameter rkeep with a parameter value to the second RCS server and then receive a 200 OK message, which is a response message to the registration message, from the second RCS server. Upon receiving the 200 OK message from the second RCS server, the negotiation-based IMS registration procedure between the electronic device and the second RCS server may be completed. As the negotiation IMS registration procedure between the electronic device and the second RCS server is completed, the electronic device may set the timer value of the second timer configured for the second RCS server to the parameter value of parameter rkeep, and set the second timer to the parameter value of parameter rkeep. You can start. As the second timer starts, the electronic device may transition to a sleep state. In one embodiment, the start time of the second timer may be synchronized with the start time of the first timer.

Thereafter, the electronic device may perform a second operation set with the second RCS server that confirms that the second timer has expired. In one embodiment, the electronic device transitions from the sleep state to the normal state upon receiving a keepalive request message from the second RCS server that confirms that the second timer has expired, and the electronic device in the normal state keeps to the second RCS server. A keepalive response message, which is a response message to the alive request message, can be transmitted. Or, if the keep alive request message is not received from the second RCS server until the expiration of the second timer, the electronic device transitions from the sleep state to the normal state, and the electronic device in the normal state receives a keep alive request message from the second RCS server. can receive.

Meanwhile, although not separately shown in FIG. 4, the electronic device does not transition from the normal state back to the sleep state after performing the second operation according to the expiration of the second timer, but rather performs the first operation set according to the expiration of the first timer. Since it must be performed, the normal state can be maintained. In FIG. 4, because the time when the first timer expires and the time when the second timer expires are the same, the electronic device does not wake up separately according to the expiration of the first timer, but wakes up according to the performance of the second operation (for example, For example, the normal state can be maintained (by receiving a keepalive request message from the second RCS server and transmitting a keepalive response message to the second RCS server). When confirming that the first timer expires, the electronic device may perform the first operation according to the expiration of the first timer and then transition to the sleep state.

FIG. 4 illustrates a case where the electronic device performs the second operation first and then the first operation. However, since the expiration time of the first timer and the expiration time of the second timer are set to be the same, Operation 1 may be performed before the second operation.

In Figure 4, an example is given where the timer value of the second timer is set to be the same as the timer value of the first timer. However, even if the timer value of the second timer is not the same as the timer value of the first timer, the timer value of the first timer is set to be the same as the timer value of the first timer. If the difference between the timer values of the second timer is less than or equal to the set value, the first wake-up time of the electronic device according to the expiration time of the first timer (e.g., the time of sending a keep-alive request message to the first RCS server) and the second wake-up time The second wake-up time of the electronic device according to the expiration time of the timer (e.g., the time of receiving a keepalive request message from the second RCS server) may be synchronized within a time based on a set value.

In Figure 4, by setting the timer values of the first timer configured for the first RCS service corresponding to the first SIM and the second timer configured for the second RCS service corresponding to the second SIM to be the same, the first timer and the second timer The timer can be synchronized, and thus the first wake-up time corresponding to the first RCS service and the second wake-up time corresponding to the second RCS service can be synchronized. By synchronizing the first wake-up time corresponding to the first RCS service and the second wake-up time corresponding to the second RCS service, the number of times the electronic device wakes up from the sleep state can be reduced, and the number of wake-ups is reduced. can make it possible to achieve a reduction in current consumption.

FIG. 5 is a flowchart illustrating an operation process of an electronic device, according to an embodiment.

Referring to FIG. 5 , an electronic device (e.g., electronic device 101 of FIG. 1A, 1B, FIG. 2, or FIG. 3) (e.g., processor 120 of FIG. 1A or FIG. 3, or communication processor of FIG. 3) (310)) may perform a registration procedure (e.g., IMS registration procedure) with a first external electronic device (e.g., a first RCS server) in operation 511. In one embodiment, the first RCS server (eg, server 108 in FIG. 1A or first RCS server 111a in FIG. 1B) may be a first external electronic device corresponding to the first SIM of the electronic device. In one embodiment, the first SIM is a SIM subscribed to the communication service provider of the first RCS server and may correspond to the first service (eg, the first RCS service).

The IMS registration procedure performed between the electronic device and the first RCS server may be described as follows.

The electronic device may transmit a registration message to the first RCS server as it initiates an IMS registration procedure with the first RCS server. The registration message may be a SIP registration message and may include the parameter “keep”, which is a Via header field parameter. The first RCS server may receive a registration message sent from the electronic device, and may transmit a 200 OK message to the electronic device based on the received registration message. The first RCS server may confirm that the electronic device intends to transmit a keepalive request message based on the parameter keep included in the received registration message. In response to the registration request message, the first RCS server may transmit a 200 OK message including a parameter keep with a parameter value added to the electronic device. In one embodiment, the parameter value of the parameter keep may be information related to the wake-up time of the electronic device, corresponding to the first RCS service. For example, the electronic device may configure a timer (e.g., a first timer) for the first RCS service, and set the timer value of the first timer to the parameter value of the parameter keep included in the 200 OK message. . In this case, the electronic device may wake up when the first timer expires and perform the set first operation. Since the first operation may be implemented similarly or substantially the same as that described in FIG. 4, its detailed description will be omitted here. As an example, in Figure 5, it is assumed that the parameter value of the parameter keep is set to 7 minutes. As the electronic device receives the 200 OK message from the first RCS server, the IMS registration procedure between the electronic device and the first RCS server may be completed.

In operation 513, the electronic device may check whether the parameter keep parameter value received from the first RCS server is an acceptable value. The electronic device may check whether the parameter keep parameter value received from the first RCS server is an acceptable value based on various parameters. For example, the parameter value of the parameter keep may need to be prevented from being set to a value less than a set value (e.g., 30 seconds).

As a result of the confirmation in operation 513, if the parameter value of the parameter keep received from the first RCS server is an acceptable value, in operation 515, the electronic device determines the second external electronic device based on the parameter value of the parameter keep received from the first RCS server. A negotiation-based IMS registration procedure can be performed with (e.g., a second RCS server). In one embodiment, the second RCS server (e.g., server 108 in FIG. 1A or second RCS server 112a in FIG. 1B) may be a second external electronic device corresponding to the second SIM of the electronic device. In one embodiment, the second SIM is a SIM subscribed to the communication service provider of the second RCS server and may correspond to a second service (eg, a second RCS service). In one embodiment, the negotiation-based IMS registration procedure may be an IMS registration procedure based on the parameter rkeep, and the negotiation-based IMS registration procedure between the electronic device and the second RCS server may be described as follows.

The electronic device may transmit a registration message to the second RCS server as it initiates a negotiation-based IMS registration procedure with the second RCS server. The registration message may be a SIP registration message and may include the parameter “rkeep”, which is a Via header field parameter. The parameter rkeep may indicate the intention of a SIP entity (e.g., an electronic device) to receive a keepalive message (e.g., a keepalive request message) from a neighboring downstream SIP entity (e.g., a second RCS server) of the SIP entity. The parameter rkeep may have a parameter value, and the parameter value of the parameter rkeep may indicate the keepalive frequency.

In one embodiment, the parameter value of parameter rkeep may be information related to the wake-up time of the electronic device, corresponding to the second RCS service. For example, the electronic device may configure a timer (e.g., a second timer) for the second RCS service, and set the timer value of the second timer to the parameter value of the parameter rkeep included in the registration message. In this case, the electronic device may perform the second operation set with the second RCS server. Since the second operation may be implemented similarly or substantially the same as that described in FIG. 4, its detailed description will be omitted here.

In one embodiment, the electronic device may set the parameter value of the parameter keep included in the 200 OK message received from the first RCS server as the parameter value of the parameter rkeep. For example, the keepalive frequency may be given in seconds or minutes, and the second RCS server may have to transmit a keepalive request message based on the parameter value of the parameter rkeep.

The second RCS server may receive a registration message sent from the electronic device, and may transmit a 200 OK message to the electronic device based on the received registration message. The second RCS server may confirm that the electronic device intends to receive the keepalive request message based on the parameter rkeep included in the received registration message, and the second RCS server may confirm that the electronic device intends to receive the keepalive request message based on the parameter value of the parameter rkeep. It can be confirmed that an alive request message must be sent. The 200 OK message may include a Via header field including the parameter rkeep. Upon receiving the 200 OK message from the second RCS server, the negotiation-based IMS registration procedure between the electronic device and the second RCS server may be completed. As the negotiation-based IMS registration procedure between the electronic device and the second RCS server is completed, the electronic device may set the timer value of the second timer configured for the second RCS server to the parameter value of parameter rkeep, and the second timer You can start. In one embodiment, the start time of the second timer may be synchronized with the start time of the first timer. As the negotiation-based IMS registration procedure between the electronic device and the second RCS server is completed, the second RCS server may also set the timer value of the second timer configured for the electronic device to the parameter value of parameter rkeep, and the second timer You can start. The timer value of the second timer may indicate the expiration time of the second timer.

As a result of the check in operation 513, if the parameter value of the parameter keep received from the first RCS server is not an acceptable value, the electronic device may perform an IMS registration procedure with the second RCS server in operation 517.

The IMS registration procedure performed between the electronic device and the second RCS server may be described as follows.

The electronic device may transmit a registration message to the second RCS server as it initiates an IMS registration procedure with the second RCS server. The registration message may be a SIP registration message and may include the parameter “keep”, which is a Via header field parameter. The second RCS server may receive a registration message sent from the electronic device, and may transmit a 200 OK message to the electronic device based on the received registration message. The second RCS server may confirm that the electronic device intends to transmit a keepalive request message based on the parameter keep included in the received registration message. In response to the registration request message, the second RCS server may transmit a 200 OK message including the parameter keep to which a parameter value (eg, 10 minutes) is added to the electronic device. In one embodiment, the parameter value of the parameter keep may be information related to the wake-up time of the electronic device, corresponding to the second RCS service. For example, the electronic device may configure a timer (e.g., a second timer) for the second RCS service, and set the timer value of the second timer to the parameter value of the parameter keep included in the 200 OK message. . In this case, the electronic device may wake up when the second timer expires and perform the set third operation. In one embodiment, the third operation may include transmitting a keepalive request message to the second RCS server and receiving a keepalive response message, which is a response message to the keepalive request message, from the second RCS server. .

In operation 519, the electronic device sets the timer value of the first timer (e.g., the parameter value of parameter keep received from the first RCS server) and the timer value of the second timer (e.g., the parameter value of parameter keep received from the second RCS server). ) can be confirmed to be not the same, and an appropriate timer value (e.g., parameter value of parameter rkeep) can be set to synchronize the first timer and the second timer.

In one embodiment, the electronic device sets the larger value (e.g., 10 minutes) of the parameter value of parameter keep received from the first RCS server and the parameter value of parameter keep received from the second RCS server as the parameter value of parameter rkeep. You can. In one embodiment, the electronic device sets the smaller value (e.g., 7 minutes) of the parameter value of parameter keep received from the first RCS server and the parameter value of parameter keep received from the second RCS server as the parameter value of parameter rkeep. You can. In one embodiment, the electronic device uses a value (e.g., 5 minutes) x times the larger value of the parameter keep received from the first RCS server and the parameter keep received from the second RCS server as the parameter rkeep. It can be set to the parameter value of . In FIG. 5, the electronic device sets the larger value (e.g., 10 minutes) of the parameter value of parameter keep received from the first RCS server and the parameter value of parameter keep received from the second RCS server as the parameter value of parameter rkeep. Let's assume.

In operation 521, the electronic device that has set the parameter value of parameter rkeep performs a negotiation-based IMS registration procedure with the first RCS server that transmitted a 200 OK message including a parameter keep having a parameter value different from the parameter value of parameter rkeep. can do. The negotiation-based IMS registration procedure between the electronic device and the first RCS server may be described as follows.

The electronic device may transmit a registration message including the parameter rkeep with a parameter value of 10 minutes to the first RCS server. The first RCS server may receive a registration message including the parameter rkeep from the electronic device, and may transmit a 200 OK message to the electronic device based on the received registration message. The first RCS server may confirm that the electronic device intends to receive a keepalive request message based on the parameter rkeep included in the received registration message, and the first RCS server may confirm that the electronic device intends to receive the keepalive request message based on the parameter value of the parameter rkeep. It can be confirmed that an alive request message must be sent. The 200 OK message may include a Via header field including the parameter rkeep. The electronic device that has received the 200 OK message from the first RCS server can set the timer value of the first timer configured for the first RCS server to the parameter value of parameter rkeep and start the first timer. The first RCS server may also set the timer value of the first timer configured for the electronic device to the parameter value of parameter rkeep and start the first timer.

Thereafter, in operation 523, the electronic device may perform the fourth operation set with the first RCS server. The fourth operation may include receiving a keepalive request message from the first RCS server and transmitting a keepalive response message, which is a response message to the keepalive request message, to the first RCS server. The electronic device may transition from the sleep state to the normal state as it receives a keepalive request message from the first RCS server, and the electronic device in the normal state sends a keepalive response, which is a response message to the keepalive request message, to the first RCS server. You can send a message.

After transmitting a keepalive response message to the first RCS server according to the fourth operation, the electronic device does not transition from the normal state back to the sleep state, but corresponds to the expiration of the second timer to the third time set with the second RCS server. Since the movement must be performed, the normal state can be maintained. In operation 525, the electronic device in the normal state may perform the third operation set with the second RCS server and transition to the sleep state. The third operation may be similar to or substantially identical to the third operation of operation 517, and therefore detailed description thereof will be omitted.

In FIG. 5 , the case where operation 521 is performed before operation 523 is described. However, since the expiration time of the first timer and the expiration time of the second timer are set to be the same, operation 523 may be performed before operation 521. .

In FIG. 5, the case in which the second RCS server accepts the parameter value of the parameter rkeep included in the registration request message by the electronic device is taken as an example in operation 515. However, the second RCS server accepts the parameter value of the parameter rkeep included in the registration request message by the electronic device. You can also reject the parameter value of parameter rkeep. In this way, when the second RCS server rejects the parameter value of the parameter rkeep included by the electronic device in the registration request message, the electronic device resets the parameter value of parameter rkeep and sets the second RCS server based on the parameter rkeep having the reset parameter value. A negotiation-based IMS registration procedure can be performed with the RCS server.

Additionally, in Figure 5, the case where the first RCS server accepts the parameter value of the parameter rkeep included in the registration request message by the electronic device in operation 521 is described as an example, but the first RCS server accepts the parameter value of the parameter rkeep included in the registration request message by the electronic device. You can also reject the parameter value of the included parameter rkeep. In this way, when the first RCS server rejects the parameter value of the parameter rkeep included in the registration request message by the electronic device, the electronic device resets the parameter value of parameter rkeep, and based on the parameter rkeep having the reset parameter value, the first RCS server A negotiation-based IMS registration procedure can be performed with the RCS server.

In Figure 5, an example is given where the timer value of the second timer is set to be the same as the timer value of the first timer. However, even if the timer value of the second timer is not the same as the timer value of the first timer, the timer value of the first timer is set to be the same as the timer value of the first timer. If the difference between the timer values of the second timer is less than or equal to the set value, the wake-up time of the electronic device according to the expiration time of the first timer (e.g., the time of receiving a keepalive request message from the first RCS server) and the time of the second timer The wake-up time of the electronic device according to the expiration time (e.g., the time of transmitting a keepalive request message to the second RCS server) may be synchronized within a time based on a set value.

In Figure 5, by setting the timer values of the first timer configured for the first RCS service corresponding to the first SIM and the second timer configured for the second RCS service corresponding to the second SIM to be the same, the first timer and the second timer The timer can be synchronized, and thus the first wake-up time corresponding to the first RCS service and the second wake-up time corresponding to the second RCS service can be synchronized. By synchronizing the first wake-up time corresponding to the first RCS service and the second wake-up time corresponding to the second RCS service, the number of times the electronic device wakes up from the sleep state can be reduced, and the number of wake-ups is reduced. can make it possible to achieve a reduction in current consumption.

Figure 6 is a signal flow diagram illustrating a process for synchronizing wake-up times in a wireless communication network, according to one embodiment.

Referring to FIG. 6, the wireless communication network includes an electronic device 101 (e.g., the electronic device 101 of FIG. 1A, FIG. 1B, FIG. 2, or FIG. 3), and a first RCS server 111a (e.g., FIG. 1a). server 108 or the first RCS server 111a in FIG. 1B), and a second RCS server 111b (e.g., the server 108 in FIG. 1A or the second RCS server 111b in FIG. 1B). can do. The electronic device 101 may be a multi-SIM electronic device and may include a first SIM and a second SIM. The first RCS server 111a may be a first external electronic device corresponding to the first SIM of the electronic device 101, and may be a second external electronic device corresponding to the second SIM of the second RCS server 111b. there is. In one embodiment, the first SIM is a SIM subscribed to the communication service provider of the first RCS server 111a and may correspond to the first service (e.g., the first RCS service), and the second SIM is the second RCS server. As a SIM subscribed to the communication service provider of (112a), it may correspond to a second service (eg, a second RCS service). Figure 6 shows a case where the first RCS server 111a providing the first RCS service and the second RCS server 111b providing the second RCS service are implemented separately, but the first RCS server 111a and The second RCS server 111b may be integrated into one RCS server, and one integrated RCS server may provide the first RCS service and the second RCS service.

In operation 611, the electronic device 101 may transmit a registration message to the first RCS server 111a by initiating an IMS registration procedure with the first RCS server 111a. The registration message may be a SIP registration message and may include the parameter “keep”, which is a Via header field parameter.

The first RCS server 111a may receive a registration message sent from the electronic device 101, and in operation 613, may transmit a 200 OK message to the electronic device 101 based on the received registration message. The first RCS server 111a may confirm that the electronic device 101 intends to transmit a keepalive request message based on the parameter keep included in the received registration message. A parameter to which a parameter value is added to indicate that the first RCS server 111a is willing to receive a keepalive message (e.g., a keepalive request message) from an adjacent upstream SIP entity (e.g., the electronic device 101). A 200 OK message including keep can be sent. In one embodiment, the parameter value of the parameter keep may be information related to the wake-up time of the electronic device 101, corresponding to the first RCS service. For example, the electronic device 101 may configure a timer (e.g., a first timer) for the first RCS service, and set the timer value of the first timer as the parameter value of the parameter keep included in the 200 OK message. You can set it. In this case, the electronic device 101 may wake up when the first timer expires and perform the set first operation. In one embodiment, the first operation includes transmitting a keepalive request message to the first RCS server 111a (operation 625) and sending a keepalive response, which is a response message to the keepalive request message, from the first RCS server 111a. It may include an operation of receiving a message (operation 627).

In one embodiment, the 200 OK message may include a Via header field containing a parameter keep with a parameter value. As an example, in Figure 6, it is assumed that the parameter value of the parameter keep is set to 7 minutes. As operation 613 is completed, the IMS registration procedure between the electronic device 101 and the first RCS server 111a may be completed.

As the IMS registration procedure between the electronic device 101 and the first RCS server 111a is completed, the electronic device 101 sets the timer value of the first timer configured for the first RCS server 111a to the parameter keep. It can be set as a parameter value, and the first timer can be started.

As the IMS registration procedure between the electronic device 101 and the first RCS server 111a is completed, the first RCS server 111a also sets the timer value of the first timer configured for the electronic device 101 to the parameter keep. It can be set as a parameter value, and the first timer can be started. The timer value of the first timer may indicate the expiration time of the first timer, and the expiration time may mean the time from when the timer starts to when it expires. For example, if the expiration time of the first timer is 7 minutes, the first timer may expire 7 minutes after the start of the first timer. After starting the first timer, the electronic device 101 may transition to a sleep state.

The electronic device 101 may receive a 200 OK message from the first RCS server 111a, and initiates a negotiation-based IMS registration procedure with the second RCS server 112a in operation 615. You can send a registration message with . The registration message may be a SIP registration message and may include the parameter “rkeep”, which is a Via header field parameter. In one embodiment, the parameter value of the parameter rkeep may be information related to the wake-up time of the electronic device 101, corresponding to the second RCS service. For example, the electronic device 101 may configure a timer (e.g., a second timer) for the second RCS service, and set the timer value of the second timer to the parameter value of the parameter rkeep included in the registration message. You can. In this case, the electronic device 101 may wake up when the second timer expires and perform the set second operation. In one embodiment, the second operation includes receiving a keepalive request message from the second RCS server 112a (operation 621) and sending a keepalive response, which is a response message to the keepalive request message, to the second RCS server 112a. It may include an operation of transmitting a message (operation 623).

In one embodiment, the electronic device 101 may set the parameter value of the parameter keep included in the 200 OK message received from the first RCS server 111a as the parameter value of the parameter rkeep. For example, the keepalive frequency may be given in seconds or minutes, and the second RCS server 112a may only transmit a keepalive request message based on the parameter value of the parameter rkeep. In FIG. 6, the case where the electronic device 101 sets the parameter value of the parameter keep received from the first RCS server 111a to the parameter value of the parameter rkeep is described as an example, but the electronic device 101 sets the parameter value of the parameter rkeep received from the first RCS server 111a as an example. The parameter value of the parameter rkeep may be set to a parameter value other than the parameter value of the parameter keep received from the RCS server 111a. As an example, in Figure 6, it is assumed that the parameter value of the parameter rkeep is set to 7 minutes.

The second RCS server 112a may receive a registration message sent from the electronic device 101, and in operation 617, may transmit a 200 OK message to the electronic device 101 based on the received registration message. The second RCS server 112a may confirm that the electronic device 101 intends to receive a keepalive request message based on the parameter rkeep included in the received registration message, and based on the parameter value of the parameter rkeep It can be confirmed that the second RCS server 112a must transmit a keepalive request message. The 200 OK message may include a Via header field including the parameter rkeep. As operation 617 is completed, the negotiation-based IMS registration procedure between the electronic device 101 and the second RCS server 112a may be completed. In FIG. 6, the case where the second RCS server 112a accepts the parameter value of the parameter rkeep received from the electronic device 101 as is is explained as an example, but the second RCS server 112a does not accept the parameter value of the parameter rkeep received from the electronic device 101 as is. The parameter value of parameter rkeep received from may be rejected. As the negotiation-based IMS registration procedure between the electronic device 101 and the second RCS server 112a is completed, the electronic device 101 sets the timer value of the second timer configured for the second RCS server 112a as a parameter. It can be set as the parameter value of rkeep, and the second timer can be started. In one embodiment, the start time of the second timer may be synchronized with the start time of the first timer. In one embodiment, the electronic device 101 may wake up when receiving a keepalive request message from the second RCS server 112a, so there may be no need to separately check the expiration of the second timer. In this case, the operation of the electronic device 101 starting the second timer may be omitted.

As the negotiation-based IMS registration procedure between the electronic device 101 and the second RCS server 112a is completed, the second RCS server 112a also sets the timer value of the second timer configured for the electronic device 101 as a parameter. It can be set as the parameter value of rkeep, and the second timer can be started. The timer value of the second timer may indicate the expiration time of the second timer.

Thereafter, in operation 619, each of the electronic device 101 and the first RCS server 111a may confirm that the first timer expires, and each of the electronic device 101 and the second RCS server 112a may confirm that the second timer expires. You can check that it has expired. In one embodiment, the electronic device 101 may wake up when receiving a keepalive request message from the second RCS server 112a, so there may be no need to separately check the expiration of the second timer. In this case, the operation of the electronic device 101 confirming completion of the second timer in operation 619 may be omitted.

When confirming that the second timer expires, the second RCS server 112a may transmit a keep alive request message to the electronic device 101 in operation 621. When the electronic device 101 receives a keepalive message from the second RCS server 112a, it can wake up from the sleep state and transition to the normal state. Alternatively, if the electronic device 101 does not receive a keepalive request message from the second RCS server 112a until the second timer expires, it wakes up from the sleep state and returns to the normal state due to the expiration of the second timer. Transition may occur, and the electronic device 101 in the normal state may receive a keep alive request message transmitted from the second RCS server 112a. The electronic device 101 that has received the keep alive request message may transmit a keep alive response message, which is a response message to the keep alive request message, to the second RCS server 112a in operation 623.

Since the electronic device 101 must transmit a keepalive request message to the first RCS server 111a according to expiration of the first timer, the electronic device 101 transmits a keepalive response message to the second RCS server 112a and then keeps alive in the normal state. Instead of transitioning back to the sleep state, the normal state can be maintained. In FIG. 6, since the time when the first timer expires and the time when the second timer expires are the same, the electronic device 101 does not wake up separately according to the expiration of the first timer, but wakes up according to the expiration of the second timer. The normal state can be maintained.

When confirming that the first timer expires, the electronic device 101 may transmit a keep alive request message to the first RCS server 111a in operation 625. When the electronic device 101 confirms that the first timer has expired, it may need to wake up from the sleep state. However, since the electronic device 101 is already in the normal state upon receiving a keepalive request message from the second RCS server 112a or upon expiration of the second timer, the electronic device 101 in the normal state is in the first A keepalive request message may be transmitted to the RCS server 111a. The first RCS server 111a, which has received the keep alive request message, may transmit a keep alive response message, which is a response message to the keep alive request message, to the electronic device 101 in operation 627. The electronic device 101 that receives the keep alive response message from the first RCS server 111a may transition from the normal state back to the sleep state.

In FIG. 6 , the case where operations 621 and 623 are performed before operations 625 and 627 is described. However, since the expiration time of the first timer and the expiration time of the second timer are set to be the same, operations 625 and 627 are performed. It may be performed before operations 621 and 623.

In Figure 6, an example is given where the timer value of the second timer is set to be the same as the timer value of the first timer. However, even if the timer value of the second timer is not the same as the timer value of the first timer, the timer value of the first timer is set to be the same as the timer value of the first timer. If the difference between the timer values of the second timer is less than or equal to the set value, the wake-up time of the electronic device 101 according to the expiration time of the first timer (e.g., the time of transmitting a keep-alive request message to the first RCS server 111a) ) and the wake-up time of the electronic device 101 according to the expiration time of the second timer (e.g., the time of receiving the keep-alive request message from the second RCS server 112a) will be synchronized within the time based on the set value. You can.

In Figure 6, by setting the timer values of the first timer configured for the first RCS service corresponding to the first SIM and the second timer configured for the second RCS service corresponding to the second SIM to be the same, the first timer and the second timer The timer can be synchronized, and thus the first wake-up time corresponding to the first RCS service and the second wake-up time corresponding to the second RCS service can be synchronized. By synchronizing the first wake-up time corresponding to the first RCS service and the second wake-up time corresponding to the second RCS service, the number of times the electronic device 101 wakes up from the sleep state can be reduced, and the wake-up time Reducing the number of times may make it possible to achieve a reduction in current consumption.

Figure 7 is a signal flow diagram illustrating a process for synchronizing wake-up times in a wireless communication network, according to one embodiment.

Referring to FIG. 7, the wireless communication network includes an electronic device 101 (e.g., the electronic device 101 of FIG. 1A, FIG. 1B, FIG. 2, or FIG. 3), and a first RCS server 111a (e.g., FIG. 1a). server 108 or the first RCS server 111a in FIG. 1B), and a second RCS server 111b (e.g., the server 108 in FIG. 1A or the second RCS server 111b in FIG. 1B). can do. The electronic device 101 may be a multi-SIM electronic device and may include a first SIM and a second SIM. The first RCS server 111a may be a first external electronic device corresponding to the first SIM of the electronic device 101, and may be a second external electronic device corresponding to the second SIM of the second RCS server 111b. there is. In one embodiment, the first SIM is a SIM subscribed to the communication service provider of the first RCS server 111a and may correspond to the first service (e.g., the first RCS service), and the second SIM is the second RCS server. As a SIM subscribed to the communication service provider of (112a), it may correspond to a second service (eg, a second RCS service). Figure 7 shows a case where the first RCS server 111a providing the first RCS service and the second RCS server 111b providing the second RCS service are implemented separately, but the first RCS server 111a and The second RCS server 111b may be integrated into one RCS server, and one integrated RCS server may provide the first RCS service and the second RCS service.

In operation 711, the electronic device 101 may transmit a registration message to the first RCS server 111a by initiating an IMS registration procedure with the first RCS server 111a. The registration message in operation 711 may be similar to or implemented substantially the same as the registration message in operation 611 of FIG. 6, and therefore detailed description thereof will be omitted.

The first RCS server 111a may receive a registration message sent from the electronic device 101, and in operation 713, may transmit a 200 OK message to the electronic device 101 based on the received registration message. The first RCS server 111a can confirm that the electronic device 101 intends to transmit a keepalive request message based on the parameter keep included in the received registration message, and sends the parameter keep with the parameter value added. A message containing 200 OK can be sent. As an example, the parameter value of the parameter keep may be set to 7 minutes. The 200 OK message in operation 713 may be similar to or substantially identical to the 200 OK message in operation 613 of FIG. 6, and therefore detailed description thereof will be omitted.

As operation 713 is completed, the IMS registration procedure between the electronic device 101 and the first RCS server 111a may be completed. As the IMS registration procedure between the electronic device 101 and the first RCS server 111a is completed, the electronic device 101 sets the timer value of the first timer configured for the first RCS server 111a to the parameter keep. It can be set as a parameter value, and the first timer can be started.

In operation 715, the electronic device 101 may transmit a registration message to the second RCS server 112a by initiating an IMS registration procedure with the second RCS server 112a. The registration message of operation 715 may be similar to or implemented substantially the same as the registration message of operation 611 of FIG. 6, and therefore detailed description thereof will be omitted.

The second RCS server 112a may receive a registration message transmitted from the electronic device 101, and in operation 717, may transmit a 200 OK message to the electronic device 101 based on the received registration message. The second RCS server 112a can confirm that the electronic device 101 intends to transmit a keepalive request message based on the parameter keep included in the received registration message, and sends the parameter keep with the parameter value added. A message containing 200 OK can be sent. As an example, the parameter value of the parameter keep may be set to 10 minutes. The 200 OK message in operation 717 may be similar to or substantially identical to the 200 OK message in operation 613 of FIG. 6, and therefore detailed description thereof will be omitted.

As operation 717 is completed, the IMS registration procedure between the electronic device 101 and the second RCS server 112a may be completed. As the IMS registration procedure between the electronic device 101 and the second RCS server 112a is completed, the electronic device 101 sets the timer value of the second timer configured for the second RCS server 112a to the parameter keep. It can be set as a parameter value.

The electronic device 101 configures the timer value of the first timer (e.g., the parameter keep parameter value received from the first RCS server 111a) and the timer value of the second timer (e.g., the parameter value of parameter keep received from the first RCS server 111a). It can be confirmed that the parameter value of one parameter keep) is not the same, and in operation 719, an appropriate timer value (e.g., the parameter value of parameter rkeep) can be set to synchronize the first timer and the second timer.

In one embodiment, the electronic device 101 maintains the larger value of the parameter keep value received from the first RCS server 111a and the parameter keep value received from the second RCS server 112a (e.g., 10 minutes). ) can be set as the parameter value of parameter rkeep. In one embodiment, the electronic device 101 stores the smaller of the parameter keep parameter value received from the first RCS server 111a and the parameter keep parameter value received from the second RCS server 112a (e.g., 7 minutes). ) can be set as the parameter value of parameter rkeep. In one embodiment, the electronic device 101 receives a value x times the larger of the parameter keep parameter value received from the first RCS server 111a and the parameter keep parameter value received from the second RCS server 112a. (e.g. 5 minutes) can be set as the parameter value of parameter rkeep. In FIG. 7, the larger value (e.g., 10 minutes) of the parameter value of parameter keep received from the first RCS server 111a and the parameter value of parameter keep received from the second RCS server 112a is used as the parameter value of parameter rkeep. Let's assume that you set it up.

In operation 721, the electronic device 101, which has set the parameter value of the parameter rkeep, sends 10 to the first RCS server 111a, which sent a 200 OK message including the parameter keep having a parameter value different from the parameter value of the parameter rkeep. A registration message containing a parameter rkeep with a parameter value of 100 may be transmitted.

The first RCS server 111a may receive a registration message including the parameter rkeep from the electronic device 101, and in operation 723, transmit a 200 OK message to the electronic device 101 based on the received registration message. You can. The first RCS server 111a may confirm that the electronic device 101 intends to receive a keepalive request message based on the parameter rkeep included in the received registration message, and based on the parameter value of the parameter rkeep It can be confirmed that the first RCS server 111a must transmit a keepalive request message. The 200 OK message may include a Via header field including the parameter rkeep. In FIG. 7 , the case where the first RCS server 111a accepts the parameter value of the parameter rkeep received from the electronic device 101 as is is explained as an example, but the first RCS server 111a does not accept the parameter value of the parameter rkeep received from the electronic device 101 as is. The parameter value of parameter rkeep received from may be rejected.

The electronic device 101, which has received the 200 OK message from the first RCS server 111a, may set the timer value of the first timer configured for the first RCS server 111a to the parameter value of parameter rkeep, and 1 You can start the timer. The first RCS server 111a may also set the timer value of the first timer configured for the electronic device 101 to the parameter value of parameter rkeep and start the first timer. In one embodiment, the electronic device 101 may wake up when receiving a keepalive request message from the first RCS server 111a, so there may be no need to separately check the expiration of the first timer. In this case, the operation of the electronic device 101 starting the first timer may be omitted.

Thereafter, in operation 725, each of the electronic device 101 and the first RCS server 111a may confirm that the first timer expires, and each of the electronic device 101 and the second RCS server 112a may confirm that the second timer expires. You can check that it has expired. In one embodiment, the electronic device 101 may wake up when receiving a keepalive request message from the first RCS server 111a, so there may be no need to separately check the expiration of the first timer. In this case, the operation of the electronic device 101 confirming completion of the first timer in operation 725 may be omitted.

When confirming that the first timer expires, the first RCS server 111a may transmit a keep alive request message to the electronic device 101 in operation 727. When the electronic device 101 receives a keepalive request message transmitted from the first RCS server 111a, the electronic device 101 may wake up from the sleep state and transition to the normal state. Alternatively, when the electronic device 101 does not receive a keepalive request message from the first RCS server 111a until the first timer expires, it wakes up from the sleep state and returns to the normal state due to the expiration of the first timer. Transition may occur, and the electronic device 101 in the normal state may receive a keep alive request message transmitted from the first RCS server 111a. The electronic device 101 that has received the keep alive request message may transmit a keep alive response message, which is a response message to the keep alive request message, to the first RCS server 111a in operation 729.

Since the electronic device 101 must transmit a keepalive request message to the second RCS server 112a according to expiration of the second timer, the electronic device 101 transmits a keepalive response message to the first RCS server 111a in the normal state. Instead of transitioning back to the sleep state, the normal state can be maintained. In FIG. 7, because the time when the first timer expires and the time when the second timer expires are the same, the electronic device 101 does not wake up separately according to the expiration of the first timer, but wakes up according to the expiration of the second timer. The normal state can be maintained.

When confirming that the second timer expires, the electronic device 101 may transmit a keepalive request message to the second RCS server 112a in operation 731. When the electronic device 101 confirms that the second timer has expired, it may need to wake up from the sleep state. However, since the electronic device 101 is already in the normal state upon receiving a keep request alive message from the first RCS server 111a or upon expiration of the first timer, the electronic device 101 in the normal state is in the second A keepalive request message may be transmitted to the RCS server 112a. The second RCS server 111a, which has received the keep alive request message, may transmit a keep alive response message, which is a response message to the keep alive request message, to the electronic device 101 in operation 733. The electronic device 101 that receives the keep alive response message from the second RCS server 112a may transition from the normal state back to the sleep state.

In FIG. 7 , the case in which operations 727 and 729 are performed before operations 731 and 733 is described. However, since the expiration time of the first timer and the expiration time of the second timer are set to be the same, operations 731 and 733 are performed before operations 731 and 733. It may be performed before operations 727 and 729.

In Figure 7, an example is given where the timer value of the second timer is set to be the same as the timer value of the first timer. However, even if the timer value of the second timer is not the same as the timer value of the first timer, the timer value of the first timer is set as the same as the timer value of the first timer. If the difference between the timer values of the second timer is less than or equal to the set value, the wake-up time of the electronic device 101 according to the expiration time of the first timer (e.g., the time of receiving a keep-alive request message from the first RCS server 111a) ) and the wake-up time of the electronic device 101 according to the expiration time of the second timer (e.g., the time of transmitting a keepalive request message to the second RCS server 112a) will be synchronized within the time based on the set value. You can.

In Figure 7, by setting the timer values of the first timer configured for the first RCS service corresponding to the first SIM and the second timer configured for the second RCS service corresponding to the second SIM to be the same, the first timer and the second timer The timer can be synchronized, and thus the first wake-up time corresponding to the first RCS service and the second wake-up time corresponding to the second RCS service can be synchronized. By synchronizing the first wake-up time corresponding to the first RCS service and the second wake-up time corresponding to the second RCS service, the number of times the electronic device 101 wakes up from the sleep state can be reduced, and the wake-up time Reducing the number of times may make it possible to achieve a reduction in current consumption.

Figure 8 is a signal flow diagram illustrating a process for synchronizing wake-up times in a wireless communication network, according to one embodiment.

Referring to FIG. 8, the wireless communication network includes an electronic device 101 (e.g., the electronic device 101 of FIG. 1A, 1B, 2, or 3) and an RCS server 800 (e.g., the server of FIG. 1A). (108), or the first RCS server 111a or the second RCS server 111b in FIG. 1B). The electronic device 101 may be a single SIM electronic device and may be an electronic device that provides multiple services (eg, a first service and a second service). For example, each of the first service (eg, 1st RCS service) and the second service (eg, 2nd RCS service) may be provided through a separate app. The RCS server 800 may be an external electronic device that corresponds to an app that provides the first RCS service of the electronic device 101 and an app that provides the second RCS service of the electronic device 101.

In operation 811, the electronic device 101 transmits a registration message to the RCS server 800 by initiating an IMS registration procedure for the first RCS service (e.g., for the first RCS app) with the RCS server 800. You can. The registration message of operation 811 may be similar to or substantially identical to the registration message of operation 611 of FIG. 6, and therefore detailed description thereof will be omitted. The registration message of operation 811 may further include information related to the first RCS app.

The RCS server 800 may receive a registration message sent from the electronic device 101, and in operation 813, may transmit a 200 OK message to the electronic device 101 based on the received registration message. The RCS server 800 indicates that the electronic device 101 intends to transmit a keepalive request message to the first RCS app based on the parameter keep included in the received registration message and information related to the first RCS app. You can check and send a 200 OK message including the parameter keep with the parameter value added. As an example, the parameter value of the parameter keep may be set to 7 minutes. The 200 OK message in operation 813 may be similar to or substantially identical to the 200 OK message in operation 613 of FIG. 6, and therefore detailed description thereof will be omitted. The 200 OK message in operation 813 may further include information related to the first RCS app.

As operation 813 is completed, the IMS registration procedure for the first RCS app between the electronic device 101 and the RCS server 800 may be completed. As the IMS registration procedure for the first RCS app between the electronic device 101 and the RCS server 800 is completed, the electronic device 101 receives the first RCS app configured for the RCS server 800. The timer value of the timer can be set to the parameter value of the parameter keep, and the first timer can be started.

In operation 815, the electronic device 101 transmits a registration message to the RCS server 800 by initiating an IMS registration procedure for the second RCS service (e.g., for the second RCS app) with the RCS server 800. You can. The registration message of operation 815 may be similar to or implemented substantially the same as the registration message of operation 611 of FIG. 6, and therefore detailed description thereof will be omitted. The registration message of operation 815 may further include information related to the second RCS app.

The RCS server 800 may receive a registration message sent from the electronic device 101, and in operation 817, may transmit a 200 OK message to the electronic device 101 based on the received registration message. The RCS server 800 indicates that the electronic device 101 intends to transmit a keepalive request message to the second RCS app based on the parameter keep included in the received registration message and information related to the second RCS app. You can check and send a 200 OK message including the parameter keep with the parameter value added. As an example, the parameter value of the parameter keep may be set to 10 minutes. The 200 OK message in operation 817 may be similar to or substantially identical to the 200 OK message in operation 613 of FIG. 6, and therefore detailed description thereof will be omitted. The 200 OK message in operation 817 may further include information related to the second RCS app.

As operation 817 is completed, the IMS registration procedure for the second RCS app between the electronic device 101 and the RCS server 800 may be completed. As the IMS registration procedure for the second RCS app between the electronic device 101 and the RCS server 800 is completed, the electronic device 101 receives the second registration for the second RCS app configured for the RCS server 800. The timer value of the timer can be set as the parameter value of the parameter keep.

The electronic device 101 controls the timer value of the first timer (e.g., the parameter keep value received from the RCS server 800) and the timer value of the second timer (e.g., the parameter keep value received from the RCS server 800). It may be confirmed that the parameter values) are not the same, and in operation 819, an appropriate timer value (e.g., the parameter value of the parameter rkeep) may be determined to synchronize the first timer and the second timer.

In one embodiment, the electronic device 101 displays the parameter keep parameter value received from the RCS server 800 for the first RCS app and the parameter keep parameter value received from the RCS server 800 for the second RCS app. The larger value (e.g., 10 minutes) can be determined as the parameter value of parameter rkeep. In one embodiment, the electronic device 101 displays the parameter keep parameter value received from the RCS server 800 for the first RCS app and the parameter keep parameter value received from the RCS server 800 for the second RCS app. The smaller value (e.g. 7 minutes) can be determined as the parameter value of parameter rkeep. In one embodiment, the electronic device 101 displays the parameter keep parameter value received from the RCS server 800 for the first RCS app and the parameter keep parameter value received from the RCS server 800 for the second RCS app. A value x times the larger value (e.g., 5 minutes) can be determined as the parameter value of the parameter rkeep. In Figure 8, the larger value (e.g., 10 minutes) of the parameter keep parameter value received from the RCS server 800 for the first RCS app and the parameter keep parameter value received from the RCS server 800 for the second RCS app. ) is determined as the parameter value of the parameter rkeep.

The electronic device 101, which has determined the parameter value of the parameter rkeep, may transmit a registration message including the parameter rkeep with a parameter value of 10 minutes to the RCS server 800 in operation 821. The registration message of operation 821 may further include information related to the first RCS app and information related to the second RCS app.

The RCS server 800 may receive a registration message including the parameter rkeep from the electronic device 101, and in operation 823, may transmit a 200 OK message to the electronic device 101 based on the received registration message. . The RCS server 800 allows the electronic device 101 to use the first RCS app and the second RCS app based on the parameter rkeep, information related to the first RCS app, and information related to the second RCS app included in the received registration message. It can be confirmed that there is an intention to receive a keepalive request message for each, and the RCS server 800 transmits a keepalive request message for each of the first RCS app and the second RCS app based on the parameter value of the parameter rkeep. You can confirm that you have to do it. The 200 OK message may include a Via header field including the parameter rkeep. In FIG. 8, the case where the RCS server 800 accepts the parameter value of the parameter rkeep received from the electronic device 101 as is is explained as an example, but the RCS server 800 accepts the parameter value received from the electronic device 101 You can also reject rkeep's parameter value. The 200 OK message in operation 823 may further include information related to the first RCS app and information related to the second RCS app.

After receiving the 200 OK message from the RCS server 800, the electronic device 101 sets the timer value of the first timer for the first RCS app configured for the RCS server 800 to the parameter value of parameter rkeep. The first timer can be started, and the second timer can be started after setting the timer value of the second timer for the second RCS app to the parameter value of parameter rkeep. In one embodiment, the electronic device 101 may wake up when receiving a keepalive request message from the RCS server 800, so there may be no need to separately check the expiration of the first timer and the second timer. In this case, the operation of the electronic device 101 to check completion of the first timer and the second timer may be omitted. The RCS server 800 may also set the timer value of the first timer configured for the first RCS app of the electronic device 101 to the parameter value of the parameter rkeep and then start the first timer, and the electronic device 101 After setting the timer value of the second timer configured for the second RCS app to the parameter value of parameter rkeep, the second timer can be started.

Thereafter, in operation 825, each of the electronic device 101 and the RCS server 800 may confirm that the first timer and the second timer expire. In one embodiment, the electronic device 101 may wake up when receiving a keepalive request message from the RCS server 800, so there may be no need to separately check the expiration of the first timer and the second timer. In this case, the operation of the electronic device 101 to check the expiration of the first timer and the second timer may be omitted. When confirming that the first timer and the second timer are expired, the RCS server 800 performs operation 827. A keepalive request message may be transmitted to the electronic device 101. The keepalive request message in operation 827 may include information related to the first RCS app and information related to the second RCS app.

When the electronic device 101 receives a keep alive request message transmitted from the RCS server 800, the electronic device 101 may wake up from the sleep state and transition to the normal state. Alternatively, when the electronic device 101 does not receive the keepalive request message sent from the RCS server 800 until at least one of the first timer or the second timer expires, at least one of the first timer or the second timer Due to one expiration, it can wake up from the sleep state and transition to the normal state, and the electronic device 101 in the normal state can receive a keep alive request message sent from the server 800. The electronic device 101 that has received the keep alive request message may transmit a keep alive response message, which is a response message to the keep alive request message, to the RCS server 800 in operation 829. The keepalive response message of operation 829 may include information related to the first RCS app and information related to the second RCS app. In FIG. 8, since the time when the first timer expires and the time when the second timer expires are the same, the electronic device 101 receives the keepalive request message transmitted from the RCS server 800, or when the first timer Alternatively, since the device is in a normal state due to expiration of at least one of the second timers, a keepalive response message for the first RCS app and the second RCS app may be transmitted in the normal state.

In Figure 8, an example is given where the timer value of the second timer is set to be the same as the timer value of the first timer. However, even if the timer value of the second timer is not the same as the timer value of the first timer, the timer value of the first timer is set to be the same as the timer value of the first timer. The difference between the timer values of the second timer may be less than or equal to a set value.

In Figure 8, the first timer and the second timer can be synchronized by setting the timer values of the first timer configured for the first RCS service and the second timer configured for the second RCS service to be the same, and thus the first timer and the second timer can be synchronized The first wake-up time corresponding to and the second wake-up time corresponding to the second RCS service can be synchronized. By synchronizing the first wake-up time corresponding to the first RCS service and the second wake-up time corresponding to the second RCS service, the number of times the electronic device 101 wakes up from the sleep state can be reduced, and the wake-up time Reducing the number of times may make it possible to achieve a reduction in current consumption.

FIG. 9 is a flowchart illustrating an operation process of an electronic device, according to an embodiment.

Referring to FIG. 9 , in operation 911, an electronic device (e.g., the electronic device 101 of FIG. 1A, FIG. 1B, FIG. 2, or FIG. 3) (e.g., the processor 120 of FIG. 1A or FIG. 3, or the processor 120 of FIG. 3 The communication processor 310) sends a registration message to the first RCS server as it initiates an IMS registration procedure with the first RCS server (e.g., server 108 in FIG. 1A or first RCS server 111a in FIG. 1B). Can be sent. Operation 911 may be implemented similarly or substantially the same as that described in operation 611 of FIG. 6, and therefore detailed description thereof will be omitted.

In operation 913, the electronic device may receive a 200 OK message, which is a response message to the registration message, from the first RCS server. Operation 913 may be implemented similarly or substantially the same as that described in operation 613 of FIG. 6, and therefore detailed description thereof will be omitted. Upon receiving the 200 OK message from the first RCS server, the IMS registration procedure between the electronic device and the first RCS server may be completed. As the IMS registration procedure between the electronic device and the first RCS server is completed, the electronic device may set the timer value of the first timer configured for the first RCS server to the parameter value of parameter keep and start the first timer. You can.

In operation 915, the electronic device sends a registration message to the second RCS server as it initiates a negotiation-based IMS registration procedure with the second RCS server (e.g., server 108 in FIG. 1A or second RCS server 111b in FIG. 1B). Can be sent. Operation 915 may be implemented similarly or substantially the same as that described in operation 615 of FIG. 6, and therefore detailed description thereof will be omitted.

In operation 917, the electronic device may receive a 200 OK message, which is a response message to the registration message, from the second RCS server. Operation 917 may be implemented similarly or substantially the same as that described in operation 617 of FIG. 6, and therefore its detailed description will be omitted. Upon receiving the 200 OK message from the second RCS server, the negotiation-based IMS registration procedure between the electronic device and the second RCS server may be completed. As the negotiation-based IMS registration procedure between the electronic device and the second RCS server is completed, the electronic device may set the timer value of the second timer configured for the second RCS server to the parameter value of parameter rkeep, and the second timer You can start. In one embodiment, the electronic device can wake up when receiving a keepalive request message from the second RCS server, so there may be no need to separately check the expiration of the second timer. In this case, the operation of the electronic device starting the second timer may be omitted.

Thereafter, in operation 919, the electronic device may confirm that each of the first timer and the second timer expires. Operation 919 may be implemented similarly or substantially the same as that described in operation 619 of FIG. 6, and therefore detailed description thereof will be omitted. In one embodiment, the electronic device can wake up when receiving a keepalive request message from the second RCS server, so there may be no need to separately check the expiration of the second timer. In this case, the operation of the electronic device confirming completion of the second timer may be omitted.

In operation 921, the electronic device may receive a keepalive request message from the second RCS server. Operation 921 may be implemented similarly or substantially the same as that described in operation 621 of FIG. 6, and therefore its detailed description will be omitted.

In operation 923, the electronic device may transmit a keepalive response message, which is a response message to the keepalive request message, to the second RCS server. Operation 923 may be implemented similarly or substantially the same as that described in operation 623 of FIG. 6, and therefore detailed description thereof will be omitted. Because the electronic device does not transition from the normal state back to the sleep state after transmitting a keepalive response message to the second RCS server, but must transmit a keepalive request message to the first RCS server according to the expiration of the first timer, The normal state can be maintained. In FIG. 9, since the time when the first timer expires and the time when the second timer expires are the same, the electronic device does not wake up separately upon expiration of the first timer, but sends a keepalive request message to the second RCS server. The normal state may be maintained according to reception or expiration of the second timer.

When confirming that the first timer expires, the electronic device may transmit a keepalive request message to the first RCS server in operation 925. When the electronic device confirms that the first timer has expired, it may need to wake up from the sleep state. However, since the electronic device is in a normal state upon receiving a keepalive request message from the second RCS server or upon expiration of the second timer, the electronic device in the normal state may transmit a keepalive request message to the first RCS server. You can. Operation 925 may be implemented similarly or substantially the same as that described in operation 625 of FIG. 6, and therefore detailed description thereof will be omitted.

In operation 927, the electronic device may receive a keepalive response message, which is a response message to the keepalive request message, from the first RCS server. The electronic device that receives the keepalive response message from the first RCS server may transition from the normal state back to the sleep state. Operation 927 may be implemented similarly or substantially the same as that described in operation 627 of FIG. 6, and therefore its detailed description will be omitted.

In FIG. 9 , the case in which operations 921 and 923 are performed before operations 925 and 927 is described. However, since the expiration time of the first timer and the expiration time of the second timer are set to be the same, operations 925 and 927 are performed before operations 925 and 927. It may be performed before operations 921 and 923.

9 shows an example where the timer value of the second timer is set to be the same as the timer value of the first timer. However, even if the timer value of the second timer is not the same as the timer value of the first timer, the timer value of the first timer is set to be the same as the timer value of the first timer. If the difference between the timer values of the second timer is less than or equal to the set value, the wake-up time of the electronic device according to the expiration time of the first timer (e.g., the time of sending a keepalive request message to the first RCS server) and the time of the second timer The wake-up time of the electronic device according to the expiration time (e.g., the time of receiving a keepalive request message from the second RCS server) may be synchronized within a time based on a set value.

In Figure 9, by setting the timer values of the first timer configured for the first RCS service corresponding to the first SIM and the second timer configured for the second RCS service corresponding to the second SIM to be the same, the first timer and the second timer The timer can be synchronized, and thus the first wake-up time corresponding to the first RCS service and the second wake-up time corresponding to the second RCS service can be synchronized. By synchronizing the first wake-up time corresponding to the first RCS service and the second wake-up time corresponding to the second RCS service, the number of times the electronic device wakes up from the sleep state can be reduced, and the number of wake-ups is reduced. can make it possible to achieve a reduction in current consumption.

FIG. 10 is a flowchart illustrating an operation process of an electronic device, according to an embodiment.

Referring to FIG. 10 , in operation 1011, an electronic device (e.g., the electronic device 101 of FIG. 1A, 1B, FIG. 2, or FIG. 3) (e.g., the processor 120 of FIG. 1A or FIG. 3, or the processor 120 of FIG. 3 The communication processor 310) sends a registration message to the first RCS server as it initiates an IMS registration procedure with the first RCS server (e.g., server 108 in FIG. 1A or first RCS server 111a in FIG. 1B). Can be sent. Operation 1011 may be implemented similarly or substantially the same as that described in operation 711 of FIG. 7, and therefore detailed description thereof will be omitted.

In operation 1013, the electronic device may receive a 200 OK message, which is a response message to the registration message, from the first RCS server. Operation 1013 may be implemented similarly or substantially the same as that described in operation 713 of FIG. 7, and therefore its detailed description will be omitted. Upon receiving the 200 OK message from the first RCS server, the IMS registration procedure between the electronic device and the first RCS server may be completed. As the IMS registration procedure between the electronic device and the first RCS server is completed, the electronic device may set the timer value of the first timer configured for the first RCS server to the parameter value of parameter keep and start the first timer. You can.

In operation 1015, the electronic device transmits a registration message to the second RCS server by initiating an IMS registration procedure with the second RCS server (e.g., server 108 in FIG. 1A or second RCS server 111b in FIG. 1B). You can. Operation 1015 may be implemented similarly or substantially the same as that described in operation 715 of FIG. 7, and therefore detailed description thereof will be omitted.

In operation 1017, the electronic device may receive a 200 OK message, which is a response message to the registration message, from the second RCS server. Operation 1017 may be implemented similarly or substantially the same as that described in operation 717 of FIG. 7, and therefore its detailed description will be omitted. Upon receiving the 200 OK message from the second RCS server, the IMS registration procedure between the electronic device and the second RCS server may be completed. As the IMS registration procedure between the electronic device and the second RCS server is completed, the electronic device may set the timer value of the second timer configured for the second RCS server to the parameter value of parameter keep and start the second timer. You can.

In operation 1019, the electronic device sets the timer value of the first timer (e.g., the parameter value of parameter keep received from the first RCS server) and the timer value of the second timer (e.g., the parameter value of parameter keep received from the second RCS server). ) can be confirmed to be not the same, and an appropriate timer value (e.g., parameter value of parameter rkeep) can be set to synchronize the first timer and the second timer. As an example, assume that the parameter value of parameter rkeep is set to 10 minutes. Operation 1019 may be implemented similarly or substantially the same as that described in operation 719 of FIG. 7, and therefore its detailed description will be omitted.

In operation 1021, the electronic device that has set the parameter value of the parameter rkeep sends a parameter value of 10 minutes to the first RCS server that transmitted a 200 OK message including a parameter keep with a parameter value different from the parameter value of the parameter rkeep. A registration message containing the parameter rkeep can be sent. Operation 1021 may be implemented similarly or substantially the same as that described in operation 721 of FIG. 7, and therefore its detailed description will be omitted.

In operation 1023, the electronic device may receive a 200 OK message, which is a response message to the registration message, from the first RCS server. The electronic device that has received the 200 OK message from the first RCS server can set the timer value of the first timer configured for the first RCS server to the parameter value of parameter rkeep and start the first timer. Operation 1023 may be implemented similarly or substantially the same as that described in operation 723 of FIG. 7, and therefore its detailed description will be omitted. In one embodiment, the electronic device can wake up when receiving a keepalive request message from the first RCS server, so there may be no need to separately check the expiration of the first timer. In this case, the operation of the electronic device starting the first timer may be omitted.

Thereafter, in operation 1025, the electronic device may confirm that each of the first timer and the second timer expires. Operation 1025 may be implemented similarly or substantially the same as that described in operation 725 of FIG. 7, and therefore detailed description thereof will be omitted. In one embodiment, the electronic device can wake up when receiving a keepalive request message from the first RCS server, so there may be no need to separately check the expiration of the first timer. In this case, the operation of the electronic device confirming completion of the first timer may be omitted.

The electronic device may receive a keepalive request message from the first RCS server in operation 1027. When the electronic device receives a keepalive request message sent from the first RCS server, it can wake up from the sleep state and transition to the normal state. Alternatively, if the electronic device does not receive a keepalive request message from the first RCS server until the first timer expires, the electronic device may wake up from the sleep state and transition to the normal state due to the expiration of the first timer, and the electronic device may wake up from the sleep state and transition to the normal state. The electronic device in the state may receive a keepalive request message sent from the first RCS server. Operation 1027 may be implemented similarly or substantially the same as that described in operation 727 of FIG. 7, and therefore its detailed description will be omitted.

The electronic device that has received the keep alive request message may transmit a keep alive response message, which is a response message to the keep alive request message, to the first RCS server in operation 1029. Since the electronic device must transmit a keepalive request message to the second RCS server upon expiration of the second timer, it does not transition from the normal state back to the sleep state after transmitting the keepalive response message to the first RCS server. The normal state can be maintained. In FIG. 7, since the time when the first timer expires and the time when the second timer expires are the same, the electronic device does not wake up separately according to the expiration of the second timer, but receives a keep request alive message from the first RCS server. The normal state may be maintained upon reception or upon expiration of the first timer. Operation 1029 may be implemented similarly or substantially the same as that described in operation 729 of FIG. 7, and therefore its detailed description will be omitted.

When confirming that the second timer expires, the electronic device may transmit a keepalive request message to the second RCS server in operation 1031. When the electronic device confirms that the second timer has expired, it may need to wake up from the sleep state. However, since the electronic device is already in the normal state upon receiving a keep request alive message from the first RCS server or upon expiration of the first timer, the electronic device in the normal state transmits a keep alive request message to the second RCS server. can do. Operation 1031 may be implemented similarly or substantially the same as that described in operation 731 of FIG. 7, and therefore its detailed description will be omitted.

In operation 1033, the electronic device may receive a keepalive response message, which is a response message to the keepalive request message, from the second RCS server. The electronic device that receives the keepalive response message from the second RCS server may transition from the normal state back to the sleep state. Operation 1033 may be implemented similarly or substantially the same as that described in operation 733 of FIG. 7, and therefore detailed description thereof will be omitted.

In FIG. 10 , the case where operations 1027 and 1029 are performed before operations 1031 and 1033 is described. However, since the expiration time of the first timer and the expiration time of the second timer are set to be the same, operations 1031 and 1033 are performed before operations 1031 and 1033. It may be performed before operations 1027 and 1029.

In Figure 10, an example is given where the timer value of the second timer is set to be the same as the timer value of the first timer. However, even if the timer value of the second timer is not the same as the timer value of the first timer, the timer value of the first timer is set to be the same as the timer value of the first timer. If the difference between the timer values of the second timer is less than or equal to the set value, the wake-up time of the electronic device according to the expiration time of the first timer (e.g., the time of receiving a keepalive request message from the first RCS server) and the time of the second timer The wake-up time of the electronic device according to the expiration time (e.g., the time of transmitting a keepalive request message to the second RCS server) may be synchronized within a time based on a set value.

In Figure 10, by setting the timer values of the first timer configured for the first RCS service corresponding to the first SIM and the second timer configured for the second RCS service corresponding to the second SIM to be the same, the first timer and the second timer The timer can be synchronized, and thus the first wake-up time corresponding to the first RCS service and the second wake-up time corresponding to the second RCS service can be synchronized. By synchronizing the first wake-up time corresponding to the first RCS service and the second wake-up time corresponding to the second RCS service, the number of times the electronic device wakes up from the sleep state can be reduced, and the number of wake-ups is reduced. can make it possible to achieve a reduction in current consumption.

FIG. 11 is a flowchart illustrating an operation process of an electronic device, according to an embodiment.

Referring to FIG. 11 , in operation 1111, an electronic device (e.g., the electronic device 101 of FIG. 1A, FIG. 1B, FIG. 2, or FIG. 3) (e.g., the processor 120 of FIG. 1A or FIG. 3, or the processor 120 of FIG. 3 The communication processor 310) is an RCS server (e.g., server 108 in FIG. 1A, or first RCS server 111a or second RCS server 111b in FIG. 1B) and a first RCS service (e.g. : As the IMS registration procedure (for the first RCS app) is initiated, a registration message can be sent to the RCS server. Operation 1111 may be implemented similarly or substantially the same as that described in operation 811 of FIG. 8, and therefore its detailed description will be omitted.

In operation 1113, the electronic device may receive a 200 OK message, which is a response message to the registration message, from the RCS server. Operation 1113 may be implemented similarly or substantially the same as that described in operation 813 of FIG. 8, and therefore its detailed description will be omitted. Upon receiving the 200 OK message from the RCS server, the IMS registration procedure for the first RCS app between the electronic device and the RCS server may be completed. As the IMS registration procedure for the first RCS app between the electronic device and the RCS server is completed, the electronic device may set the timer value of the first timer configured for the first RCS app as the parameter value of parameter keep, 1 You can start the timer.

In operation 1115, the electronic device may transmit a registration message to the RCS server as it initiates an IMS registration procedure for the RCS server and the second RCS service (e.g., for the second RCS app). Operation 1115 may be implemented similarly or substantially the same as that described in operation 815 of FIG. 8, and therefore detailed description thereof will be omitted.

In operation 1117, the electronic device may receive a 200 OK message, which is a response message to the registration message, from the RCS server. Operation 1117 may be implemented similarly or substantially the same as that described in operation 817 of FIG. 8, and therefore its detailed description will be omitted. Upon receiving the 200 OK message from the RCS server, the IMS registration procedure for the second RCS app between the electronic device and the RCS server may be completed. As the IMS registration procedure for the second RCS app between the electronic device and the RCS server is completed, the electronic device may set the timer value of the second timer configured for the second RCS app to the parameter value of parameter keep, 2 You can start the timer.

In operation 1119, the electronic device determines that the timer value of the first timer (e.g., the parameter value of parameter keep received from the RCS server) and the timer value of the second timer (e.g., the parameter value of parameter keep received from the RCS server) are not the same. It can be confirmed that this is not the case, and an appropriate timer value (e.g., parameter value of parameter rkeep) can be set to synchronize the first timer and the second timer. Operation 1119 may be implemented similarly or substantially the same as that described in operation 819 of FIG. 8, and therefore its detailed description will be omitted.

The electronic device that has set the parameter value of the parameter rkeep may transmit a registration message including the parameter rkeep with the set parameter value to the RCS server in operation 1121. The registration message of operation 1121 may further include information related to the first RCS app and information related to the second RCS app. Operation 1121 may be implemented similarly or substantially the same as that described in operation 821 of FIG. 8, and therefore detailed description thereof will be omitted.

In operation 1123, the electronic device may receive a 200 OK message, which is a response message to the registration message, from the RCS server. The 200 OK message in operation 1123 may further include information related to the first RCS app and information related to the second RCS app. The electronic device that received the 200 OK message from the RCS server may set the timer value of the first timer for the first RCS app configured for the RCS server to the parameter value of parameter rkeep and then start the first timer, 2 After setting the timer value of the second timer for the RCS app to the parameter value of parameter rkeep, the second timer can be started. In one embodiment, the electronic device can wake up when receiving a keepalive request message from the RCS server, so there may be no need to separately check the expiration of the first timer and the second timer. In this case, the operation of the electronic device confirming completion of the first timer and the second timer may be omitted. Operation 1123 may be implemented similarly or substantially the same as that described in operation 823 of FIG. 8, and therefore detailed description thereof will be omitted.

Thereafter, in operation 1125, the electronic device may confirm that each of the first timer and the second timer expires. Operation 1125 may be implemented similarly or substantially the same as that described in operation 825 of FIG. 8, and therefore detailed description thereof will be omitted. In one embodiment, the electronic device can wake up when receiving a keepalive request message from the RCS server, so there may be no need to separately check the expiration of the first timer and the second timer. In this case, the operation of the electronic device checking the expiration of the first timer and the second timer may be omitted.

The electronic device may receive a keepalive request message from the RCS server in operation 1127. The keepalive request message in operation 1127 may include information related to the first RCS app and information related to the second RCS app. Operation 1127 may be implemented similarly or substantially the same as that described in operation 227 of FIG. 8, and therefore its detailed description will be omitted.

The electronic device that has received the keep alive request message may transmit a keep alive response message, which is a response message to the keep alive request message, to the RCS server in operation 1129. The keepalive response message of operation 1129 may include information related to the first RCS app and information related to the second RCS app. Operation 1129 may be implemented similarly or substantially the same as that described in operation 829 of FIG. 8, and therefore its detailed description will be omitted. In FIG. 11, since the time when the first timer expires and the time when the second timer expires are the same, the electronic device receives a keepalive request message from the RCS server at that time, transitions to the normal state, and then returns to the normal state. A keepalive response message can be transmitted for the 1 RCS app and the second RCS app.

In Figure 11, an example is given where the timer value of the second timer is set to be the same as the timer value of the first timer. However, even if the timer value of the second timer is not the same as the timer value of the first timer, the timer value of the first timer is The difference between the timer values of the second timer may be less than or equal to a set value.

In Figure 11, the first timer and the second timer can be synchronized by setting the timer values of the first timer configured for the first RCS service and the second timer configured for the second RCS service to be the same, and thus the first timer and the second timer can be synchronized The first wake-up time corresponding to and the second wake-up time corresponding to the second RCS service can be synchronized. By synchronizing the first wake-up time corresponding to the first RCS service and the second wake-up time corresponding to the second RCS service, the number of times the electronic device wakes up from the sleep state can be reduced, and the number of wake-ups is reduced. can make it possible to achieve a reduction in current consumption.

According to an embodiment of the present disclosure, a method of operating an electronic device (electronic device 101 of FIGS. 1A, 1B, 2, or 3) includes a first external electronic device (server 108 of FIG. 1A, Alternatively, it may include receiving first information related to the first wake up time corresponding to the first service from the first RCS server 111a of FIG. 1B.

According to an embodiment of the present disclosure, the operating method may further include setting second information related to a second wake-up time point corresponding to the second service based on the first information.

According to an embodiment of the present disclosure, the operating method further includes transmitting the second information to a second external electronic device (the server 108 in FIG. 1A or the second RCS server 112a in FIG. 1B). It can be included.

According to an embodiment of the present disclosure, the operation method may further include performing a second operation set at the second wake-up time.

According to an embodiment of the present disclosure, the difference between the first wake-up time and the second wake-up time may be less than or equal to a set value.

According to an embodiment of the present disclosure, the operation of setting the second information includes the first information received from the first external electronic device (the server 108 in FIG. 1A or the first RCS server 111a in FIG. 1B). It may include an operation of setting 1 information as the second information.

According to an embodiment of the present disclosure, the operation of setting the second information includes, before transmitting the second information, the second external electronic device (the server 108 of FIG. 1A or the second RCS server of FIG. 1B) It may include receiving third information related to the second wake-up time corresponding to the second service from (112a)).

According to an embodiment of the present disclosure, setting the second information may further include setting the second information based on the first information and the third information.

According to an embodiment of the present disclosure, the first information may be a timer value of a first timer used to set the first wake-up time.

According to an embodiment of the present disclosure, the second information may be a first timer value of a second timer used to set the second wake-up time.

According to an embodiment of the present disclosure, the third information may be a second timer value of a second timer used to set the second wake-up time.

According to an embodiment of the present disclosure, the first timer value of the second timer is set to the timer value of the first timer or the second timer value of the second timer, or the timer value of the first timer and the It may be set to an integer multiple of any one of the second timer values of the second timer.

According to an embodiment of the present disclosure, the operating method may further include waking up at the first wake-up time and performing a set first operation.

According to an embodiment of the present disclosure, the first operation is a keep alive request to the first external electronic device (the server 108 in FIG. 1A or the first RCS server 111a in FIG. 1B). ) An operation of transmitting a message, and a keep alive response (keep) from the first external electronic device (the server 108 in FIG. 1A or the first RCS server 111a in FIG. 1B) in response to the keep alive message. It may include the operation of receiving an alive response) message.

According to an embodiment of the present disclosure, the second operation includes a keep alive request from the second external electronic device (the server 108 in FIG. 1A or the second RCS server 112a in FIG. 1B). An operation of receiving a message, and sending, to the second external electronic device (the server 108 of FIG. 1A or the second RCS server 112a of FIG. 1B), a keep alive response in response to the keep alive message. ) may include the operation of sending a message.

According to an embodiment of the present disclosure, the first external electronic device (server 108 in FIG. 1A, or first RCS server 111a in FIG. 1B) and the second external electronic device (server 108 in FIG. 1A) ) or the second RCS server 112a in FIG. 1B) may be integrated into one external electronic device.

According to an embodiment of the present disclosure, the second operation includes receiving a keep alive request message from the one external electronic device, and sending the keep alive message to the one external electronic device. It may include transmitting a keep alive response message in response.

According to an embodiment of the present disclosure, the keepalive request message may include information related to the first service and information related to the second service.

According to an embodiment of the present disclosure, the first external electronic device (server 108 in FIG. 1A or first RCS server 111a in FIG. 1B) is connected to the electronic device (FIGS. 1A, 1B, 2, or a plurality of subscriber identity modules (SIMs) corresponding to the electronic device 101 of FIG. 3 (the subscriber identity module 196 of FIG. 1, or the first SIM 331 of FIG. 3 or the second It may correspond to the first SIM (the subscriber identification module 196 of FIG. 1 or the first SIM 331 of FIG. 3) among the SIMs 341).

According to an embodiment of the present disclosure, the second external electronic device (server 108 in FIG. 1A or second RCS server 112a in FIG. 1B) uses a second SIM (the subscriber in FIG. 1) among the plurality of SIMs. It may correspond to the identification module 196, or the second SIM 341 in FIG. 3).

According to an embodiment of the present disclosure, it may be possible to efficiently manage wake-up timings for services.

According to an embodiment of the present disclosure, resource consumption can be reduced by efficiently managing wake-up times for services.

Claims (20)

In the electronic device 101,
at least one communication circuit (190; 320); and
At least one processor (120; 310) operatively connected to the at least one communication circuit, the at least one processor comprising:
Receiving first information related to a first wake up time corresponding to a first service from a first external electronic device (108; 111a) through the at least one communication circuit,
Based on the first information, set second information related to the second wake-up time corresponding to the second service,
transmitting the second information to a second external electronic device (108; 112a) through the at least one communication circuit, and
Configured to perform a second operation set at the second wake-up time,
The electronic device wherein the difference between the first wake-up time and the second wake-up time is less than or equal to a set value. According to paragraph 1,
The at least one processor:
The electronic device configured to set first information received from the first external electronic device as the second information. According to claim 1 or 2,
The at least one processor:
Before transmitting the second information, receive third information related to a second wake-up time point corresponding to the second service from the second external electronic device through the at least one communication circuit, and
The electronic device configured to set the second information based on the first information and the third information. According to paragraph 3,
The first information is a timer value of the first timer used to set the first wake-up time,
The second information is a first timer value of the second timer used to set the second wake-up time,
The third information is a second timer value of the second timer used to set the second wake-up time, and
The first timer value of the second timer is set to the timer value of the first timer or the second timer value of the second timer, or one of the timer value of the first timer and the second timer value of the second timer. The electronic device set to a multiple of any one integer. According to any one of claims 1 to 4,
The at least one processor:
The electronic device is further configured to wake up at the first wake-up time and perform a set first operation. According to clause 5,
The first operation is:
An operation of transmitting a keep alive request message to the first external electronic device, and
The electronic device comprising receiving a keep alive response message from the first external electronic device in response to the keep alive message. According to any one of claims 1 to 6,
The second operation is:
An operation of receiving a keep alive request message from the second external electronic device, and
The electronic device comprising transmitting a keep alive response message to the second external electronic device in response to the keep alive message. According to any one of claims 1 to 7,
The electronic device wherein the first external electronic device and the second external electronic device are integrated into one external electronic device. According to clause 8,
The second operation includes receiving a keep alive request message from the one external electronic device, and
Transmitting a keep alive response message to the one external electronic device in response to the keep alive message,
The electronic device wherein the keep alive request message includes information related to the first service and information related to the second service. According to any one of claims 1 to 9,
The first external electronic device corresponds to a first SIM (196; 331) among a plurality of subscriber identity modules (SIMs) (196; 331; 341) connected to the at least one processor, and
The second external electronic device corresponds to a second SIM (196; 341) among the plurality of SIMs. In the method of operating the electronic device 101,
An operation of receiving first information related to a first wake up time corresponding to a first service from a first external electronic device (108; 111a);
An operation of setting second information related to a second wake-up time corresponding to a second service based on the first information;
Transmitting the second information to a second external electronic device (108; 112a); and
It includes performing a second operation set at the second wake-up time,
The operating method wherein the difference between the first wake-up time and the second wake-up time is less than or equal to a set value. According to clause 11,
The operation of setting the second information is:
The operating method includes setting first information received from the first external electronic device as the second information. According to claim 11 or 12,
The operation of setting the second information is:
Before transmitting the second information, receiving third information related to a second wake-up time corresponding to the second service from the second external electronic device; and
The operating method comprising setting the second information based on the first information and the third information. According to clause 13,
The first information is a timer value of the first timer used to set the first wake-up time,
The second information is a first timer value of the second timer used to set the second wake-up time,
The third information is a second timer value of the second timer used to set the second wake-up time, and
The first timer value of the second timer is set to the timer value of the first timer or the second timer value of the second timer, or one of the timer value of the first timer and the second timer value of the second timer. The above operating method is set to a multiple of any one integer. According to any one of claims 11 to 14,
The operating method further includes waking up at the first wake-up time and performing a set first operation. According to clause 15,
The first operation is:
An operation of transmitting a keep alive request message to the first external electronic device, and
The operating method comprising receiving a keep alive response message from the first external electronic device in response to the keep alive message. According to any one of claims 11 to 16,
The second operation is:
An operation of receiving a keep alive request message from the second external electronic device, and
The operating method comprising transmitting a keep alive response message to the second external electronic device in response to the keep alive message. According to any one of claims 11 to 17,
The operating method wherein the first external electronic device and the second external electronic device are integrated into one external electronic device. According to clause 18,
The second operation includes receiving a keep alive request message from the one external electronic device, and
Transmitting a keep alive response message to the one external electronic device in response to the keep alive message,
The operating method wherein the keepalive request message includes information related to the first service and information related to the second service. According to any one of claims 11 to 19,
The first external electronic device corresponds to a first SIM (196; 331) among a plurality of subscriber identity modules (SIMs) (196; 331; 341) corresponding to the electronic device, and
The operating method wherein the second external electronic device corresponds to a second SIM (196; 341) among the plurality of SIMs.

Images