JP7425555B2 - Notification methods, computer systems, and computer programs in a multi-device environment - Google Patents

Description

The following description relates to techniques for providing notifications in a multi-device environment.

The use of messengers for sending and receiving instant messages continues to grow and has become a major means of communication alongside telephones and mobile phones.

Instant Messenger, a common communication tool, is software that can send and receive messages and data in real time. When a user registers a conversation partner on Messenger, it will be possible to communicate with the person registered in the conversation partner list. You can exchange messages in real time.

Messenger is a communication method that has the advantage of being able to easily exchange not only general text messages but also document files, image files, etc. in real time.

Such messenger functions are widespread not only in PCs but also in the mobile environment of mobile communication terminals.

For example, Patent Document 1 (published on September 30, 2002) discloses a mobile messenger for mobile terminals that uses a wireless communication network and that enables messenger services to be provided between mobile messengers installed on the mobile terminals. A service system and method is disclosed.

Generally, when a messenger receives a message, a message reception notification is displayed. At this time, message reception notifications are made with sound, vibration, etc., and based on the notification settings, a pop-up screen may be displayed on the terminal screen immediately after the message is received, or a notification batch may be displayed on the messenger icon. is possible.

Korean Published Patent No. 10-2002-0074304

The problem in one embodiment is to be able to provide Messenger notifications in a multi-device environment, including devices that do not have Messenger installed.

A method performed by a computer system, the computer system comprising at least one processor configured to execute computer-readable instructions contained in memory, the method comprising: by the at least one processor: registering at least one other device on which the application is not installed for use by a user of the device on which the application is installed; The method includes the step of transmitting a simple notification in the form of a simple notification to the other device.

According to one aspect, the simple notification may omit a function that requires data synchronization work related to the application.

According to another aspect, the step of registering may register the other device through authentication with the application installed on the device.

According to another aspect, the step of registering includes the step of providing a notification application to the other device after authenticating the other device, and the step of registering the other device on which the notification application is installed, after passing the authentication to the other device. The method may include registering as a device for communicating notifications.

According to another aspect, the method may further include the step of generating a notification message by the at least one processor using information condensed from notification content when an event requiring notification occurs. .

According to another aspect, the generating step may separately generate a notification message to be transmitted to the device and a notification message to be transmitted to the other device.

According to another aspect, the generating step may generate the notification message to be transmitted to the other device as information that is more condensed than the notification message to be transmitted to the device.

According to another aspect, the preferences for the simple notification may be set solely in the notification application, or may be set in the same way as the notification preferences set on the application.

According to another aspect, the notification application may display a batch count indicating the number of unconfirmed simple notifications on the other device, independent of the application.

According to yet another aspect, the notification application may maintain a list of simple notifications received within a recent period of time, and display the list arranged or grouped according to certain criteria.

A non-transitory computer-readable recording medium is provided, on which a program for causing a computer to execute the method is recorded.

a memory, and at least one processor communicatively coupled to the memory and configured to execute computer-readable instructions contained in the memory, the at least one processor having an application installed on the device. a device registration unit that registers at least one other device on which the application is not installed, which is used by a user of the application, and transmits a notification associated with the application to the other device as a simple notification in the form of a one-way notification. Provided is a computer system comprising a notification transmission unit.

1 is a diagram illustrating an example network environment in one embodiment. FIG. FIG. 2 is a block diagram for explaining the internal configurations of an electronic device and a server in one embodiment. FIG. 2 is a diagram showing an overall example of a system environment for messenger notification. 1 is a diagram illustrating an overall example system environment for providing messenger notifications to multiple devices in one embodiment. FIG. FIG. 2 is a block diagram illustrating example components that a processor of a server may include, in one embodiment. 3 is a flowchart illustrating an example method that a server may perform, in one embodiment. FIG. 3 is an exemplary diagram showing a messenger notification pop-up. FIG. 3 is an exemplary diagram illustrating a notification pop-up of a notification application in one embodiment. FIG. 3 is an exemplary diagram illustrating a notification pop-up of a notification application in one embodiment. FIG. 2 is an exemplary diagram illustrating a notification list of a notification application in one embodiment.

Hereinafter, one embodiment will be described in detail with reference to the accompanying drawings.

One embodiment relates to techniques for providing notifications in a multi-device environment.

The problem in one embodiment is to be able to provide Messenger notifications in a multi-device environment, including devices that do not have Messenger installed.

Another challenge in one embodiment is to provide a service that allows users to keep track of Messenger notifications on the devices they have, regardless of the device on which they are using Messenger.

Another challenge in one embodiment is to significantly reduce implementation complexity by providing Messenger notifications unidirectionally across multiple devices and requiring no data synchronization efforts.

Embodiments, including those specifically disclosed herein, can provide Messenger notifications in a multi-device environment, including devices that do not have Messenger installed, thereby providing convenience, efficiency, and Considerable advantages can be achieved in terms of complexity improvement, cost savings, etc.

FIG. 1 is a diagram illustrating an example network environment in one embodiment. The network environment of FIG. 1 shows an example including multiple electronic devices 110, 120, 130, 140, multiple servers 150, 160, and a network 170. Such FIG. 1 is only an example for explaining the invention, and the number of electronic devices and the number of servers are not limited as shown in FIG. 1.

The plurality of electronic devices 110, 120, 130, and 140 may be fixed terminals or mobile terminals realized by a computer system. Examples of the plurality of electronic devices 110, 120, 130, and 140 include smartphones, mobile phones, navigation systems, PCs (personal computers), notebook PCs, digital broadcast terminals, PDAs (personal digital assistants), and PMPs (portable multimedia players). er ), tablets, game consoles, wearable devices, IoT (internet of things) devices, VR (virtual reality) devices, AR (augmented reality) devices, etc. As an example, although FIG. 1 shows a smartphone as an example of electronic device 110, in one embodiment, electronic device 110 may utilize substantially wireless or wired communication methods to communicate with other electronic devices via network 170. It may refer to one of a variety of physical computer systems that can communicate with devices 120, 130, 140 and/or servers 150, 160.

The communication method is not limited, and can include not only the communication method using the communication network that the network 170 can include (for example, a mobile communication network, wired Internet, wireless Internet, broadcasting network, satellite network, etc.), but also the equipment. may include short-range wireless communication between For example, the network 170 includes a PAN (personal area network), a LAN (local area network), a CAN (campus area network), a MAN (metropolitan area network), and a WAN (wide area network). area network), BBN (broadband network), the Internet, etc. may include any one or more of the networks. Additionally, network 170 may include any one or more of network topologies including, but not limited to, a bus network, a star network, a ring network, a mesh network, a star bus network, a tree or hierarchical network, and the like. It will not be done.

Each server 150, 160 is implemented by one or more computing devices that communicate with a plurality of electronic devices 110, 120, 130, 140 via a network 170 to provide instructions, code, files, content, services, etc. good. For example, the server 150 may be a system that provides a first service to a plurality of electronic devices 110, 120, 130, and 140 connected via the network 170, and the server 160 may also be a system that provides a first service to a plurality of electronic devices 110, 120, 130, and 140 connected via the network 170. The system may provide a second service to electronic devices 110, 120, 130, and 140. As a more specific example, the server 150 provides a service (for example, a messenger service) through an application that is a computer program that is installed and executed on the plurality of electronic devices 110, 120, 130, and 140. etc.) may be provided to the plurality of electronic devices 110, 120, 130, 140 as a first service. As another example, the server 160 may provide, as a second service, a service that distributes files for installing and executing the above-described applications to the plurality of electronic devices 110, 120, 130, and 140.

FIG. 2 is a block diagram for explaining the internal configuration of an electronic device and a server in one embodiment. In FIG. 2, the internal configuration of the electronic device 110 and the internal configuration of the server 150 will be described as examples of electronic devices. Further, other electronic devices 120, 130, 140 and server 160 may also have the same or similar internal configurations as electronic device 110 or server 150 described above.

Electronic device 110 and server 150 may include memory 211, 221, processor 212, 222, communication module 213, 223, and input/output interface 214, 224. The memories 211 and 221 are non-temporary computer-readable recording media, such as RAM (random access memory), ROM (read only memory), disk drive, SSD (solid state drive), and flash memory. may include permanent mass storage devices such as. Here, a permanent large capacity storage device such as a ROM, SSD, flash memory, or disk drive may be included in the electronic device 110 or the server 150 as a separate permanent storage device separated from the memories 211 and 221. good. The memories 211 and 221 also include an operating system and at least one program code (for example, a browser installed and executed on the electronic device 110 or an application installed on the electronic device 110 to provide a specific service). etc.) may be recorded. Such software components may be loaded from a computer readable storage medium separate from the memory 211, 221. Such other computer-readable recording media may include computer-readable recording media such as floppy drives, disks, tapes, DVD/CD-ROM drives, memory cards, and the like. In other embodiments, the software components may be loaded into the memory 211, 221 through a communication module 213, 223 that is not a computer readable storage medium. For example, at least one program may be a computer program (as an example, as described above) that is installed by a file provided over network 170 by a developer or a file distribution system that distributes application installation files (such as server 160, as described above). may be loaded into the memory 211, 221 based on the application (used by the user).

Processors 212, 222 may be configured to process instructions of a computer program by performing basic arithmetic, logic, and input/output operations. Instructions may be provided to the processor 212, 222 by a memory 211, 221 or a communication module 213, 223. For example, processors 212, 222 may be configured to execute instructions received according to program code recorded on a storage device, such as memory 211, 221.

The communication modules 213 and 223 may provide a function for the electronic device 110 and the server 150 to communicate with each other via the network 170, or may provide a function for the electronic device 110 and/or the server 150 to communicate with other electronic devices (for example, , electronic device 120) or other servers (eg, server 160). As an example, a request generated by the processor 212 of the electronic device 110 according to a program code recorded in a storage device such as the memory 211 may be transmitted to the server 150 via the network 170 under the control of the communication module 213. Conversely, control signals, instructions, content, files, etc. provided under the control of the processor 222 of the server 150 are received by the electronic device 110 via the communication module 213 of the electronic device 110 via the communication module 223 and the network 170. It's okay to be. For example, control signals, instructions, content, files, etc. of the server 150 received through the communication module 213 may be communicated to the processor 212 and the memory 211, and the content, files, etc. may be stored in the electronic device 110. It may be recorded on a medium (permanent storage device as described above).

Input/output interface 214 may be a means for interfacing with input/output device 215. For example, input devices may include devices such as a keyboard, mouse, microphone, camera, etc., and output devices may include devices such as a display, speakers, tactile feedback devices, and the like. As another example, input/output interface 214 may be a means for interfacing with a device that has integrated input and output functionality, such as a touch screen. Input/output device 215 may be comprised of one device with electronic device 110. The input/output interface 224 of the server 150 may also be a means for interfacing with devices for input or output (not shown) that may be connected to or included in the server 150. As a more specific example, when the processor 212 of the electronic device 110 processes instructions of a computer program loaded into the memory 211, a service screen or content is configured using data provided by the server 150 and the electronic device 120. may be displayed on the display through input/output interface 214.

Also, in other embodiments, electronic device 110 and server 150 may include more components than those in FIG. 2. However, most prior art components need not be clearly illustrated. For example, the electronic device 110 may be implemented to include at least some of the input/output devices 215 described above, or may include a transceiver, a GPS (Global Positioning System) module, a camera, various sensors, a database, etc. It may further include other components. As a more specific example, when the electronic device 110 is a smartphone, the smartphone generally includes an acceleration sensor, a gyro sensor, a camera module, various physical buttons, buttons using a touch panel, input/output ports, Various components, such as a vibrator for vibration, may also be implemented to be included in the electronic device 110.

Specific embodiments of methods and systems for providing application notifications in a multi-device environment are described below.

An application according to an embodiment includes a function of providing a notice regarding data exchanged between clients or data exchanged between a server and a client using the application. As an example, applications may include social media applications that provide social networking services such as messengers, timelines, and the like. As another example, the application may include a content providing application that provides content such as blogs, WebToons, news, etc. through a web feed or news feed.

In the following, a specific embodiment will be described using Messenger as a typical example of an application, but the application is not limited to this. Features related to one embodiment include not only Messenger but also all applications including notification functions. Applicable to the application.

FIG. 3 is a diagram showing an overall example of a system environment for messenger notification.

In FIG. 3, User A has device 1 (311) where Messenger PC version is installed, device 2 (312) where Messenger mobile version is installed, and device 3 (313) where Messenger is not installed. and Device 4 (314), and assume that UserB sends a message to UserA.

Referring to FIG. 3, when UserB sends a message to UserA using a device (320) on which the Messenger mobile version is installed, the server 350 sends the message sent by UserB to the Messenger among UserA's devices. The data will be sent to Device 1 (311) and Device 2 (312) where .

At this time, the server 350 may transmit a message reception notification to a device whose user authentication through login or the like has been confirmed. In other words, if UserA is logged in and using Messenger installed on Device 2 (312) among Device 1 (311) and Device 2 (312) where Messenger is installed, the message received from UserB The notification is transmitted to device 2 (312). If multi-device usage is supported, the message receipt notification can also be communicated to all devices on which the messenger is installed, ie, both device 1 (311) and device 2 (312).

However, if UserA is currently using a device on which Messenger is not installed, e.g., Device 3 (313), UserA may be unable to access notifications received by Device 1 (311) and/or Device 2 (312). It may happen that you cannot grasp the moment.

Therefore, if User A is using a device (313 or 314) on which Messenger is not installed, a situation may occur where User A is unable to recognize the message receipt notification from Messenger and misses an important message.

In order to use multiple devices, after installing Messenger on all devices used by User A, it is necessary to implement not only data transmission and reception but also all services related to Messenger. It is complicated to realize a service for a multi-device environment, as it is necessary to synchronize message read processing for each message across all devices used by UserA, as well as data synchronization between devices. be.

In one embodiment, a notification application is provided that is separate from Messenger and can receive only Messenger notifications. By using this notification application, Messenger notifications can be provided to multiple devices in a unidirectional simple notification format that does not require data synchronization (hereinafter referred to as "simple notification"). It becomes possible to do so.

In order to support the use of multiple devices, it is possible to provide a notification application (hereinafter referred to as "noti version") that allows you to receive simple notifications by simply performing a simple authentication process using Messenger.

The noti version includes only the function of transmitting Messenger notifications as a simple notification, as an example, and includes a series of other functions included in Messenger notifications, such as message read processing function, reply function, and data sending function. etc. are all omitted, and at the same time, no data synchronization work is required, making it possible to significantly reduce the implementation complexity for multi-device use. However, it is not essential for one embodiment to omit all functions other than the function of transmitting messenger notifications. More generally, functions that do not require data synchronization tasks may be omitted.

FIG. 4 is a diagram illustrating an overall example system environment for providing messenger notifications to multiple devices in one embodiment.

In FIG. 4, User A has Device 1 (311) on which Messenger PC version is installed, Device 2 (312) on which Messenger Mobile version is installed, Device 3 (313) and Device 4 (on which Messenger is not installed). 314), and assume a situation where UserB sends a message to UserA.

Devices 1, 2, 3, and 4 (311 to 314) owned by User A may be devices that have internal components that are the same as or similar to the electronic device 110 described with reference to FIGS. 1 and 2. , server 350 may also be a device having the same or similar internal components as server 150 described with reference to FIGS. 1 and 2.

For devices 3 (313) and 4 (314) where Messenger is not installed, the PC version of Messenger installed on device 1 (311) or the mobile version of Messenger installed on device 2 (312) has passed device authentication. Afterwards, the noti version may be installed. In other words, after the server 350 authenticates the devices 313, 314 owned by the messenger user with the messenger, the server 350 may provide the noti version to the successfully authenticated devices.

Referring to FIG. 4, when UserB sends a message to UserA using device 320 on which Messenger mobile version is installed, server 350 sends a notification for the message sent by UserB to device 1 on which Messenger is installed. (311) and device 2 (312), and may also be transmitted to device 3 (313) and device 4 (314), which do not have Messenger installed but have the noti version installed.

Messenger installed on device 1 (311) and device 2 (312) requires data synchronization with the server 350 or other devices, so it provides functions such as message read processing function, reply function, data transmission function, etc. It is possible to do so.

On the other hand, the noti version installed on device 3 (313) and device 4 (314) only includes the function of receiving notifications from the server 350 in one direction, so other functions except the notification reception function are not available. Get everything omitted.

Even if UserA is currently using a device on which Messenger is not installed, for example device 3 (313), the message will not be received by device 3 (313) nor by device 1 (311) and/or device 2 (312). Since all notifications are received in the same way, it is possible to immediately grasp the moment when a Messenger notification is received.

Therefore, even when User A is using another device (313 or 314) on which Messenger is not installed, he can receive Messenger notifications using the noti version, which allows him to receive only notifications, so he can receive important messages. This makes it possible to quickly check the information at the required time.

FIG. 5 is a block diagram illustrating example components that a processor of a server may include, in one embodiment, and FIG. 6 is a block diagram illustrating an example method that a server may perform, in one embodiment. This is a flowchart.

The server 350 according to the present embodiment may work with a notification application, that is, a noti version, installed on a plurality of devices that are clients, and may transmit messenger notifications as simple notifications.

The server 350 may be implemented as one system with a messenger server that provides a messenger service, but as another example, it may be implemented as a separate notification server that provides messenger notifications in conjunction with the messenger server.

Server 350 may be a device having the same or similar internal components as server 150 described with reference to FIGS. 1 and 2.

The server 350 may perform the notification providing method according to FIG. 6 . To this end, the processor 222 of the server 350 may include a device registration unit 510, a notification generation unit 520, and a notification transmission unit 530 as components, as shown in FIG. In some embodiments, components of processor 222 may be selectively included or excluded from processor 222. Also, in some embodiments, components of processor 222 may be separated or combined to express the functionality of processor 222.

Such processor 222 and components of processor 222 may control server 350 to perform steps 610-630 included in the notification providing method of FIG. For example, processor 222 and components of processor 222 may be implemented to execute instructions according to operating system code and at least one program code that memory 221 contains.

Here, the components of processor 222 may be representations of different functions of processor 222 that are executed by processor 222 according to instructions provided by program code stored on server 350. For example, device registration unit 510 may be utilized as a functional representation of processor 222 that controls server 350 according to the instructions described above to cause server 350 to register devices for receiving simple notifications.

Processor 222 may read the necessary instructions from memory 221 loaded with instructions related to control of server 350. In this case, the read instructions may include instructions for controlling the processor 222 to perform steps 610 to 630, which will be described below.

In step 610, the device registration unit 510 authenticates each Messenger user with the Messenger installed on the user's device, and registers at least one device owned by the user on which Messenger is not installed. Other devices may be registered. In other words, to support a multi-device environment where a user uses multiple devices at once, the device registration unit 510 may register a device on which Messenger is not installed as a device for receiving simple notifications. . At this time, the device registration unit 510 uses the messenger installed on one of the devices used by the user to authenticate other devices on which the messenger is not installed, and then applies the authentication to the corresponding device. A noti version may be provided to the device, and once the noti version is installed, the device may be registered as a device to receive simple notifications. For example, the device registration unit 510 may construct a multi-device authentication system based on a device ID (unique device identifier: UUID), and use a nearby device such as Bluetooth (registered trademark) or NFC on a device on which Messenger is installed. After searching for nearby devices by distance communication, at least one device selected by the user from the searched device list may be registered as a device for receiving simple notifications. A user may install the noti version, which only receives messenger notifications, on a device used in a multi-device environment on which messenger is not installed.

In step 620, when an event related to a messenger user occurs, the notification generation unit 520 may generate a notification message related to the corresponding event. For example, the notification generation unit 520 may predefine a list of events for which notification is required, and when a predefined event occurs, generate a notification message to notify the occurrence of the corresponding event. For example, if the event is a message reception event, a notification message may be generated to notify of message reception. The notification message may be generated with condensed information that includes only a part of the message content (for example, a character string from the first character to 15 characters) rather than the entire message content. The notification message also includes at least one of the following: the type of notification (for example, message reception notification, update notification, service official notification, etc.), part of the message content, the name of the sender of the message, and the name of the chat room where the message was received. may be included. For example, the notification generation unit 520 may generate the notification message by including the abridged information and the sender's name as part of the message content, or by including only the sender's name. As another example, the notification generation unit 520 may separately generate a notification message to be transmitted to the messenger and a notification message to be transmitted to the noti version for the same event. At this time, the notification generation unit 520 may generate the noti version notification message as information that is one step more condensed than the messenger notification message. For example, a messenger notification message may include part of the message content and the sender's name, and a noti version of the notification message may include only the sender's name.

In step 630, the notification delivery unit 530 may deliver the notification message generated in step 620 to the other device registered in step 610 as a unidirectional notification, ie, a simple notification. Simple notification is realized as a one-way notification transmitted only from the server 350 to the client, and unlike the notification realized on messenger, all functions such as message read processing function, response function, data transmission function, etc. are omitted, Data synchronization work required for read processing is not required. Targeting devices on which Messenger is not installed, the notification transmission unit 530 omits all complex functions required for processing such as message confirmation, and only provides the minimum amount of information needed to notify that a notification has been delivered to Messenger. may be transmitted in one direction. Users can use the noti version to recognize Messenger notifications even while using other devices that do not have Messenger installed, so they can immediately check which devices have Messenger installed. becomes possible.

Preferences for simple notifications may be set independently by the noti version, but may also be synchronized in the same way as notification preferences preset on a logged in messenger. The environment settings for simple notifications can not only be set all at once for Messenger, but also individually for each Messenger chat room or conversation partner. Preferences for simple notifications include whether to receive notifications, pause notifications, display method of notifications (sound, vibration, LED, etc.), notification pop-up time (pop-up appears when the screen is off, pop-up when the screen is on) (e.g., pop-up display), and whether the message content can be displayed in a notification pop-up.

FIG. 7 is a diagram showing an example of a messenger notification popup.

Referring to FIG. 7, when a message receipt notification is received from the server 350, the messenger may display a notification popup 700 on the screen of the device. At this time, the notification popup 700 may include a message reception time 711, a message sender's name 712, at least a part of the message content 713, etc., especially for a reply function that requires data synchronization. The menu 721 and the like may be included.

FIG. 8 is a diagram showing an example of a notification popup of the noti version.

Referring to FIG. 8, when a message reception notification is received from the server 350, the noti version may display a notification popup 800 that includes only the message reception time 811 and message sender name 812 on the device screen. At this time, the message reception notification is a simple notification and no response or feedback is possible, and the notification popup 800 requires data synchronization such as a message read processing function, a response function, a data transmission function, etc. All functions provided may be omitted.

Furthermore, the noti version may display the number of unconfirmed simple notifications (the cumulative number of simple notifications that have not been confirmed by the user). For example, as shown in FIG. 9, a notification batch 920 indicating the number of unconfirmed notifications accumulated up to now is internally displayed on a device on which the noti version is installed, regardless of the messenger, at a predetermined position on the device screen (e.g. , status display line, etc.) or on the notification popup 800. In the noti version, if the user inputs a confirmation request for a simple notification, the batch count may be initialized internally in the noti version, rather than the message read processing method that requests data synchronization.

Additionally, the noti version may provide a receiving list of simple notifications. For example, as shown in FIG. 10, if the user selects notification pop-up 800, a list 1030 of notifications received within a recent period of time (eg, one week) may be provided. The notification list 1030 may be configured as a list arranged in the order of recent reception of simple notifications, and may display simple notifications grouped based on unit time (eg, one day) or sender. It is also possible to maintain only the most recently received simple notifications without supporting the notification list 1030 to simplify and simplify the noti version.

In this way, according to one embodiment, when realizing a service that provides notifications to multiple devices, by applying simple notifications that do not require data synchronization work to some devices, the server It can significantly reduce the burden and implementation complexity.

The apparatus described above may be realized by hardware components, software components, and/or a combination of hardware and software components. For example, the devices and components described in the embodiments include a processor, a controller, an arithmetic logic unit (ALU), a digital signal processor, a microcomputer, a field programmable gate array (FPGA), a programmable logic unit (PLU), a microprocessor, or may be implemented using one or more general purpose or special purpose computers, such as various devices capable of executing and responding to instructions. A processing device may execute an operating system (OS) and one or more software applications that execute on the OS. The processing device may also be responsive to execution of the software to access, record, manipulate, process, and generate data. Although for convenience of understanding, one processing device may be described as being used, those skilled in the art will appreciate that a processing device may include multiple processing elements and/or multiple types of processing elements. You will understand. For example, a processing device may include multiple processors or a processor and a controller. Other processing configurations are also possible, such as parallel processors.

Software may include computer programs, code, instructions, or a combination of one or more of these that configure or, independently or collectively, instruct a processing device to perform a desired operation. You may do so. The software and/or data may be embodied in a machine, component, physical device, computer storage medium or device of any kind for being interpreted by or providing instructions or data to a processing device. good. The software may be distributed on computer systems connected by a network, and may be recorded or executed in a distributed manner. The software and data may be recorded on one or more computer readable storage media.

Methods according to embodiments may be implemented in the form of program instructions executable by various computer means and recorded on computer-readable media. Here, the medium may be one that continuously records a computer-executable program, or one that temporarily records it for execution or download. Also, the medium may be a variety of recording or storage means in the form of a single or multiple hardware combinations, and is not limited to a medium directly connected to a computer system, but may be distributed over a network. It may also exist. Examples of media include magnetic media such as hard disks, floppy disks, and magnetic tape, optical media such as CD-ROMs and DVDs, magneto-optical media such as floptical disks, and It may include ROM, RAM, flash memory, etc., and may be configured to record program instructions. Further, other examples of the medium include an application store that distributes applications, a site that supplies or distributes various other software, and a recording medium or storage medium managed by a server.

As mentioned above, although the embodiments have been described based on limited embodiments and drawings, those skilled in the art will be able to make various modifications and variations based on the above description. For example, the techniques described may be performed in a different order than in the manner described, and/or components of the systems, structures, devices, circuits, etc. described may be performed in a different form than in the manner described. Even when combined or combined, opposed or replaced by other components or equivalents, suitable results can be achieved.

Therefore, even if the embodiments are different, if they are equivalent to the scope of the claims, they fall within the scope of the appended claims.

510: Device registration unit 520: Notification generation unit 530: Notification transmission unit

Claims (18)

A method performed by a computer system, the method comprising:
The computer system includes at least one processor configured to execute computer-readable instructions contained in memory;
The method includes:
registering, by the at least one processor, at least one other device on which the application is not installed for use by a user of the device on which the application is installed; transmitting a notification to the other device in a simple notification in the form of a unidirectional notification , and the registering step includes:
A method comprising registering the other device by authenticating with the application installed on the device . The simple notification omits a function that requires data synchronization work related to the application.
The method according to claim 1. The step of registering includes:
providing a notification application to the other device after authenticating with the other device; and registering the other device on which the notification application is installed as a device for transmitting the simple notification. , the method of claim 1. The method includes:
2. The method of claim 1, further comprising: generating a notification message by the at least one processor using information condensed from notification content when an event requiring notification occurs. The generating step includes:
separately generating a notification message to be transmitted to the device and a notification message to be transmitted to the other device;
The method according to claim 4 . The generating step includes:
generating a notification message to be transmitted to the other device as information that is more condensed than the notification message to be transmitted to the device;
The method according to claim 4 . The environment settings for the simple notification are set independently in the notification application, or are set in the same way as the notification environment settings set on the application.
The method according to claim 3 . The notification application displays a batch count indicating the number of unconfirmed simple notifications on the other device, independently of the application.
The method according to claim 3 . The notification application maintains a list of simple notifications received within a recent certain period of time, and displays the list arranged or grouped according to certain criteria.
The method according to claim 3 . A computer program that causes a computer to execute the method according to any one of claims 1 to 9 . a memory; and at least one processor communicatively coupled to the memory and configured to execute computer-readable instructions contained in the memory;
The at least one processor includes:
a device registration unit that registers at least one other device on which the application is not installed, which is used by a user of the device on which the application is installed; and a device registration unit that registers at least one other device on which the application is not installed; A computer system comprising: a notification transmission unit that transmits a notification to the other device, wherein the device registration unit registers the other device through authentication with the application installed on the device . The simple notification omits a function that requires data synchronization work related to the application.
The computer system according to claim 11 . The device registration section includes:
After authenticating the other device, providing a notification application to the other device;
registering another device on which the notification application is installed as a device for transmitting the simple notification;
The computer system according to claim 11 . The at least one processor includes:
12. The computer system according to claim 11 , further comprising: a notification generation unit that generates a notification message using information obtained by condensing notification contents when an event requiring notification occurs. The notification generation unit includes:
separately generating a notification message to be transmitted to the device and a notification message to be transmitted to the other device;
A computer system according to claim 14 . The notification generation unit includes:
generating a notification message to be transmitted to the other device as information that is more condensed than the notification message to be transmitted to the device;
A computer system according to claim 14 . The environment settings for the simple notification are set independently in the notification application, or are set in the same way as the notification environment settings set on the application.
The computer system according to claim 13 . The notification application displays a batch count indicating the number of unconfirmed simple notifications on the other device, independently of the application.
The computer system according to claim 13 .

Images