KR102612067B1 - Method, system, and non-transitory computer readable record medium for providing notice in multi-device environment - Google Patents

Abstract

A method and system for providing notifications in a multi-device environment and a non-transitory computer-readable recording medium are disclosed. The notification providing method includes registering at least one other device on which the application is not installed, which is used by a user of a device on which the application is installed; And it may include delivering a notification related to the application to the other device as a simple notification in the form of a one-way notification (simplex notice).

Description

Method and system for providing notification in a multi-device environment and non-transitory computer-readable recording medium

The description below relates to technology that provides notifications in a multi-device environment.

The use of messengers for sending and receiving instant messages continues to increase, and has now become one of the main means of communication along with telephones and mobile phones.

Instant messenger, a common communication tool, is software that can send and receive messages or data in real time. Users can register conversation partners on the messenger and send and receive messages in real time with people on the conversation partner list.

Messenger is a means of communication that has the advantage of being able to easily exchange document files, picture files, etc. in real time in addition to general text messages.

The use of these messenger functions is becoming widespread not only on PCs but also in the mobile environment of mobile communication devices.

For example, Korean Patent Publication No. 10-2002-0074304 (published on September 30, 2002) discloses a mobile messenger service system for mobile terminals using a wireless communication network that allows messenger services to be provided between mobile messengers installed in mobile terminals, and A method is disclosed.

Typically, a messenger outputs a message reception notification when a message is received. At this time, message reception notification consists of a voice notification or vibration notification, and depending on the notification environment settings, the message may be displayed as a pop-up screen on the terminal screen immediately upon receiving the message, or a notification badge may be displayed on the messenger icon.

Messenger notifications can be provided in a multi-device environment, including devices that do not have the messenger installed.

It is possible to provide a service that allows users to catch messenger notifications through the device they own, regardless of the device on which they are actually using the messenger.

Implementation complexity can be significantly reduced by providing messenger notifications one-way to multiple devices and not requiring data synchronization.

In a method executed on a computer system, the computer system includes at least one processor configured to execute computer-readable instructions included in a memory, and the method includes, by the at least one processor, a device on which an application is installed. registering at least one other device used by a user on which the application is not installed; and transmitting, by the at least one processor, a notification related to the application to the other device in the form of a simplex notice.

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

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

According to another aspect, the registering step includes providing a notification application to the other device after authenticating the other device; And it may include registering another device on which the notification application is installed as a device for delivering the simple notification.

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

According to another aspect, the generating step may be performed by distinguishing between a notification message delivered to the device and a notification message delivered to the other device.

According to another aspect, the generating step may generate a notification message delivered to the other device with more condensed information than the notification message delivered to the device.

According to another aspect, the environment settings for the simple notification may be set independently through the notification application, or may be set identically to the notification environment settings set on the application.

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

According to another aspect, the notification application may maintain a list of simple notifications received over a recent period of time and display the list by sorting or grouping it based on a certain standard.

Provided is a non-transitory computer-readable recording medium on which a program for executing the above method on a computer is recorded.

Memory; and at least one processor connected to the memory and configured to execute computer-readable instructions included in the memory, wherein the at least one processor is used by a user of a device on which the application is installed and at least one processor on which the application is not installed. a device register registering one other device; and a notification delivery unit that delivers a notification related to the application to the other device as a simple notification in the form of a one-way notification.

1 is a diagram illustrating an example of a network environment according to an embodiment of the present invention.
Figure 2 is a block diagram for explaining the internal configuration of an electronic device and a server according to an embodiment of the present invention.
Figure 3 is a diagram showing an example of the overall system environment for messenger notifications.
Figure 4 is a diagram illustrating an example of an overall system environment for providing messenger notifications to multiple devices in an embodiment of the present invention.
Figure 5 is a block diagram showing an example of components that a processor of a server may include according to an embodiment of the present invention.
Figure 6 is a flowchart showing an example of a method that a server can perform according to an embodiment of the present invention.
Figure 7 shows an example of a notification pop-up of a messenger.
Figures 8 and 9 show an example of a notification pop-up of a notification application according to an embodiment of the present invention.
Figure 10 shows an example of a notification list of a notification application according to an embodiment of the present invention.

Hereinafter, embodiments of the present invention will be described in detail with reference to the attached drawings.

Embodiments of the present invention relate to technology for providing notifications in a multi-device environment.

Embodiments including those specifically disclosed in this specification can provide messenger notifications through a multi-device environment, including devices on which the messenger is not installed, and thereby provide convenience, efficiency, improvement in implementation complexity, cost reduction, etc. Significant advantages can be achieved in this regard.

1 is a diagram illustrating an example of a network environment according to an embodiment of the present invention. The network environment in FIG. 1 shows an example including a plurality of electronic devices 110, 120, 130, and 140, a plurality of servers 150 and 160, and a network 170. Figure 1 is an example for explaining the invention, and the number of electronic devices or servers is not limited as in Figure 1.

The plurality of electronic devices 110, 120, 130, and 140 may be fixed terminals or mobile terminals implemented with a computer system. Examples of the plurality of electronic devices 110, 120, 130, and 140 include smart phones, mobile phones, navigation devices, computers, laptops, digital broadcasting terminals, Personal Digital Assistants (PDAs), and Portable Multimedia Players (PMPs). ), tablet PCs, game consoles, wearable devices, IoT (internet of things) devices, VR (virtual reality) devices, AR (augmented reality) devices, etc. For example, in FIG. 1, the shape of a smartphone is shown as an example of the electronic device 110. However, in embodiments of the present invention, the electronic device 110 actually communicates with other devices through the network 170 using a wireless or wired communication method. It may refer to one of various physical computer systems capable of communicating with electronic devices 120, 130, 140 and/or servers 150, 160.

The communication method is not limited, and may include not only a communication method utilizing communication networks that the network 170 may include (e.g., mobile communication network, wired Internet, wireless Internet, broadcasting network, satellite network, etc.), but also short-range wireless communication between devices. You can. For example, the network 170 may include a personal area network (PAN), a local area network (LAN), a campus area network (CAN), a metropolitan area network (MAN), a wide area network (WAN), and a broadband network (BBN). , may include one or more arbitrary networks such as the Internet. Additionally, the network 170 may include any one or more of network topologies including a bus network, star network, ring network, mesh network, star-bus network, tree or hierarchical network, etc. Not limited.

Each of the servers 150 and 160 is a computer device or a plurality of computers that communicate with a plurality of electronic devices 110, 120, 130, 140 and a network 170 to provide commands, codes, files, content, services, etc. It can be implemented with devices. 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 through the network 170, and the server 160 also provides a network ( It may be a system that provides a second service to a plurality of electronic devices 110, 120, 130, and 140 connected through 170). As a more specific example, the server 150 provides a service (for example, a messenger service, etc.) targeted by the application through an application as a computer program installed and running on a plurality of electronic devices 110, 120, 130, and 140. As a first service, it can be provided through a plurality of electronic devices 110, 120, 130, and 140. As another example, the server 160 may provide a service for distributing files for installing and running the above-described application to a plurality of electronic devices 110, 120, 130, and 140 as a second service.

Figure 2 is a block diagram for explaining the internal configuration of an electronic device and a server according to an embodiment of the present invention. In FIG. 2 , the internal configuration of the electronic device 110 and the server 150 will be described as an example of an electronic device. Additionally, other electronic devices 120, 130, and 140 or the server 160 may also have the same or similar internal configuration as the electronic device 110 or the server 150 described above.

The electronic device 110 and the server 150 may include memories 211 and 221, processors 212 and 222, communication modules 213 and 223, and input/output interfaces 214 and 224. The memory 211, 221 is a non-transitory computer-readable recording medium, such as random access memory (RAM), read only memory (ROM), disk drive, solid state drive (SSD), flash memory, etc. It may include a permanent mass storage device. Here, non-perishable mass storage devices such as ROM, SSD, flash memory, disk drive, etc. may be included in the electronic device 110 or server 150 as a separate persistent storage device that is distinct from the memories 211 and 221. In addition, the memories 211 and 221 include an operating system and at least one program code (for example, code for a browser installed and running on the electronic device 110 or an application installed on the electronic device 110 to provide a specific service, etc.) can be saved. These software components may be loaded from a computer-readable recording medium separate from the memories 211 and 221. Such separate computer-readable recording media may include computer-readable recording media such as floppy drives, disks, tapes, DVD/CD-ROM drives, and memory cards. In another embodiment, software components may be loaded into the memories 211 and 221 through the communication modules 213 and 223 rather than a computer-readable recording medium. For example, at least one program is a computer program installed by files provided through the network 170 by developers or a file distribution system that distributes installation files for applications (e.g., the server 160 described above). It may be loaded into the memories 211 and 221 based on (for example, the application described above).

The processors 212 and 222 may be configured to process instructions of a computer program by performing basic arithmetic, logic, and input/output operations. Commands may be provided to the processors 212 and 222 by the memories 211 and 221 or the communication modules 213 and 223. For example, the processors 212 and 222 may be configured to execute received instructions according to program codes stored in a recording device such as the memory 211 and 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 through the network 170, and the electronic device 110 and/or the server 150 may communicate with each other through the network 170. A function for communicating with an electronic device (e.g., electronic device 120) or another server (e.g., server 160) may be provided. For example, a request generated by the processor 212 of the electronic device 110 according to a program code stored in a recording device such as the memory 211 is sent to the server 150 through the network 170 under the control of the communication module 213. ) can be transmitted. Conversely, control signals, commands, content, files, etc. provided under the control of the processor 222 of the server 150 pass through the communication module 223 and the network 170 to the communication module 213 of the electronic device 110. ) can be received by the electronic device 110. For example, control signals, commands, content, files, etc. of the server 150 received through the communication module 213 may be transmitted to the processor 212 or memory 211, and the content or files may be transmitted to the electronic device ( 110) may be stored in a storage medium (the above-described persistent storage device) that may further include.

The input/output interface 214 may be a means for interfacing with the input/output device 215. For example, input devices may include devices such as a keyboard, mouse, microphone, and camera, and output devices may include devices such as a display, speaker, and haptic feedback device. As another example, the input/output interface 214 may be a means for interfacing with a device that integrates input and output functions, such as a touch screen. The input/output device 215 may be configured as a single device with the electronic device 110. Additionally, the input/output interface 224 of the server 150 may be connected to the server 150 or may be a means for interfacing with an input or output device (not shown) that the server 150 may include. As a more specific example, a service configured using data provided by the server 150 or the electronic device 120 when the processor 212 of the electronic device 110 processes commands of a computer program loaded in the memory 211 A screen or content may be displayed on the display through the input/output interface 214.

Additionally, in other embodiments, the electronic device 110 and the server 150 may include more components than those shown in FIG. 2 . However, there is no need to clearly show most prior art components. For example, the electronic device 110 is implemented to include at least some of the above-described input/output devices 215 or other components such as a transceiver, a Global Positioning System (GPS) module, a camera, various sensors, a database, etc. More may be included. 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, a button using a touch panel, an input/output port, and a vibrator for vibration. Various components such as these may be implemented to be further included in the electronic device 110.

Hereinafter, specific embodiments of a method and system for providing application notifications in a multi-device environment will be described.

The application according to the present invention includes a function to provide notifications regarding data exchanged between clients or data exchanged between a server and a client through the application. For example, the application may include a social media application that provides social networking services such as messenger, timeline, etc. As another example, the application may include a content providing application that provides content such as a blog, webtoon, or news through a web feed or news feed.

Below, a specific embodiment is described using messenger as a representative example of an application, but it is not limited to this and the features related to the present invention can be applied to all applications that include a notification function in addition to messenger.

Figure 3 is a diagram showing an example of the overall system environment for messenger notifications.

Figure 3 assumes that User A has device 1 (311) with the PC version of the messenger installed, device 2 (312) with the mobile version of the messenger installed, and device 3 (313) and device 4 (314) without the messenger installed. And, assume a situation where User B sends a message to User A.

Referring to FIG. 3, when User B transmits a message to User A through device 320 on which the mobile version of Messenger is installed, the server 350 sends the message sent by User B to device 1 (on which Messenger is installed) among User A's devices. 311) and device 2 (312).

At this time, the server 350 may deliver a message reception notification to a device for which user authentication has been completed through login, etc. In other words, if User A is logging in and using the messenger installed on device 2 (312) among device 1 (311) and device 2 (312), the notification of the message received from User B is sent to device 2 (312). It will be delivered to . If multi-device use is supported, it is also possible for message reception notification to be delivered to all devices on which the messenger is installed, that is, device 1 (311) and device 2 (312).

However, if User A is currently using a device on which Messenger is not installed, for example, device 3 (313), the moment of notification received on device 1 (311) and/or device 2 (312) may not be caught. You can.

Therefore, if User A is using a device (313 or 314) on which the messenger is not installed, he or she may not recognize the messenger's message reception notification and may miss important messages.

In order to use multiple devices, a messenger must be installed on all devices used by User A to implement the entire messenger-related service, including data transmission and reception. Service implementation for a multi-device environment becomes complicated because it requires not only synchronization of message reading processing for each message across all devices used by User A, but also data synchronization between devices.

In the present invention, it is possible to provide a separate notification application that can receive only messenger notifications separately from the messenger, and a one-way simple notification that does not require data synchronization for messenger notifications to multiple devices through the notification application. It can be provided in a form (hereinafter referred to as a ‘simplex notice’).

To support multi-device use, a notification application (hereinafter referred to as 'noti version') that can receive simple notifications with simple authentication through a messenger can be provided.

The noti version only includes the function of delivering messenger notifications as simple notifications, and in addition, a series of functions included in messenger notifications, such as the message read receipt processing function, reply function, and data transmission function, are all omitted, and the data transfer function is omitted. By not requiring synchronization operations, implementation complexity for multi-device use can be significantly reduced.

Figure 4 is a diagram illustrating an example of an overall system environment for providing messenger notifications to multiple devices in an embodiment of the present invention.

Figure 4 assumes that User A has device 1 (311) with the PC version of the messenger installed, device 2 (312) with the mobile version of the messenger installed, and device 3 (313) and device 4 (314) without the messenger installed. And, assume a situation where User B sends a message to User A.

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

On device 3 (313) and device 4 (314) where messenger is not installed, the noti version is installed after device authentication through the messenger PC version installed on device 1 (311) or the messenger mobile version installed on device 2 (312). It can be. In other words, the server 350 can authenticate the devices 313 and 314 owned by the messenger user using the messenger and then provide the noti version to the successfully authenticated device.

Referring to FIG. 4, when User B transmits a message to User A through device 320 on which the mobile version of Messenger is installed, the server 350 sends a notification about the message sent by User B to device 1 (311) on which Messenger is installed. It can be delivered not only to device 2 (312), but also to device 3 (313) and device 4 (314), which do not have the messenger installed but have the noti version installed.

The messenger installed on device 1 (311) and device 2 (312) requires data synchronization between the server 350 or other devices, and can provide message reading processing functions, reply functions, data transmission functions, etc. through this.

Meanwhile, the noti version installed on device 3 (313) and device 4 (314) only includes the function of receiving one-way notifications from the server 350, and all other functions except the notification reception function are omitted.

Even if User A is currently using a device on which Messenger is not installed, for example, device 3 (313), notifications received on device 1 (311) and/or device 2 (312) are sent together through device 3 (313). You can receive notifications from messengers right away.

Therefore, even while User A is using another device (313 or 314) that does not have the messenger installed, he can receive notifications from the messenger through the noti version, which only allows him to receive notifications, allowing him to quickly check important messages that he might otherwise miss at the right time. there is.

FIG. 5 is a block diagram showing an example of components that the processor of a server may include according to an embodiment of the present invention, and FIG. 6 is an example of a method that the server may perform according to an embodiment of the present invention. This is a flow chart showing.

The server 350 according to this embodiment can deliver messenger notifications as simple notifications by linking with a notification application, that is, the noti version, installed on a plurality of devices that are clients.

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

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

The server 350 can perform the notification providing method according to FIG. 6, and for this purpose, the processor 222 of the server 350 is a component, as shown in FIG. 5, including a device registration unit 510 and a notification generating unit. 520, and may include a notification delivery unit 530. Depending on the embodiment, components of the processor 222 may be selectively included in or excluded from the processor 222. Additionally, depending on the embodiment, components of the processor 222 may be separated or merged to express the functions of the processor 222.

The processor 222 and the components of the processor 222 can control the server 350 to perform steps S610 to S630 included in the notification providing method of FIG. 6. For example, the processor 222 and its components may be implemented to execute instructions according to the code of an operating system included in the memory 221 and the code of at least one program.

Here, the components of the processor 222 may be expressions of different functions of the processor 222 that are performed by the processor 222 according to instructions provided by the program code stored in the server 350. . For example, the device registration unit 510 may be used as a functional representation of the processor 222 that controls the server 350 according to the above-described instructions so that the server 350 registers a device for receiving simple notifications.

The processor 222 may read necessary instructions from the memory 221 where instructions related to control of the server 350 are loaded. In this case, the read command may include an command for controlling the processor 222 to execute steps S610 to S630 that will be described later.

In step S610, the device registration unit 510 may register at least one other device on which the messenger is not installed among the devices owned by the user through authentication through the messenger installed on the user's device for each messenger user. In other words, to support a multi-device environment in which a user uses multiple devices at once, the device registration unit 510 can register a device that does not have a messenger installed as a device for receiving simple notifications. At this time, the device register 510 can use the messenger installed on any one of the devices used by the user to authenticate other devices that do not have the messenger installed, then provide the noti version to that device, and install the noti version. Once completed, you can register the device as a device to receive simple notifications. For example, the device register 510 can build a multi-device authentication system based on a device ID (UUID, unique device identifier), and can establish a multi-device authentication system based on short-distance communication such as Bluetooth or NFC through a device with a messenger installed. After searching for a device, at least one device selected by the user from the searched device list can be registered as a device for receiving simple notifications. Users can install the noti version, which can only receive notifications from the messenger, on devices that do not have the messenger installed among devices used in a multi-device environment.

In step S620, the notification generation unit 520 may generate a notification message related to the event when an event related to the messenger user occurs. For example, the notification generator 520 may predefine a list of events requiring notification and, when a predefined event occurs, generate a notification message notifying the occurrence of the event. For example, if the event is a message reception event, a notification message notifying the receipt of the message can be created. The notification message may be created as abbreviated information that includes only part of the content (for example, a 15-character string from the first letter, etc.) rather than the entire content of the message. Additionally, the notification message may include at least one of the type of notification (e.g., message reception notification, update notification, service announcement notification, etc.), partial contents of the message, the name of the sender who sent the message, and the name of the chat room in which the message was received. there is. For example, the notification generator 520 may generate a notification message that includes abbreviated information, which is part of the content of the message, and the sender's name, or only the sender's name. As another example, the notification generator 520 can also generate a notification message to be delivered through a messenger and a notification message to be delivered as a noti version for the same event. At this time, the notification generator 520 may generate a noti version of the notification message with information that is one step more condensed than the messenger's notification message. For example, a messenger notification message may include part of the content of the message and the sender's name, while a noti version of the notification message may include only the sender's name.

In step S630, the notification delivery unit 530 may deliver the notification message generated in step S620 to another device registered in step S610 in the form of a one-way notification, that is, a simple notification. Simple notifications are implemented as one-way notifications delivered only from the server 350 to the client, and unlike notifications implemented on messengers, the message readout processing function, reply function, and data transmission function are all omitted and the data required for readout processing, etc. It also does not require any synchronization work. The notification delivery unit 530 omits all complex functions required to process messages, such as whether or not to check a message, for devices that do not have a messenger installed, and can simply one-way transmit only the minimum information indicating that a notification has been received in the messenger. . Even while users are using other devices on which the messenger is not installed, they can recognize the messenger's notifications through the noti version, allowing them to immediately check the device on which the messenger is installed.

The preferences for simple notifications can be set independently through the noti version, or they can be synchronized with the notification preferences set in advance on the logged in messenger. Simple notification preferences can be set individually for each messenger chat room or conversation partner, as well as batch settings for the messenger. The preferences for simple notifications include whether to receive notifications, pausing notifications, notification output method (sound, vibration, LED, etc.), notification pop-up timing (pop-up when screen is off, pop-up when screen is on, etc.), notification pop-up. This may include whether or not the contents of the city message are exposed.

Figure 7 shows an example of a notification pop-up of a messenger.

Referring to FIG. 7, when a message reception notification is received from the server 350, the messenger may display a notification pop-up 700 on the screen of the device. At this time, the notification pop-up 700 includes the message reception time 711, The name of the sender of the message 712, at least some contents of the message 713, etc. may be included, and in particular, a menu 721 for a reply function, which is a function requiring data synchronization, may be included.

Figure 8 shows an example of a noti version notification pop-up.

Referring to FIG. 8, the noti version displays a notification pop-up 800 on the screen of the device when a message reception notification is received from the server 350, including only the message reception time 811 and the name of the sender 812. can be displayed. At this time, the message reception notification is a simple notification that does not allow for a reply or feedback, and all functions that require data synchronization, such as a message read processing function, a reply function, and a data transmission function, may be omitted in the notification pop-up 800.

In addition, the noti version can display the unconfirmed number of simple notifications (accumulated number of simple notifications that the user has not confirmed). For example, as shown in Figure 9, the noti version is installed internally in the device regardless of the messenger. A notification badge 920 indicating the number of unconfirmed notifications accumulated to date may be displayed at a predetermined location (e.g., status bar, etc.) on the device screen or on a notification pop-up 800. The noti version does not handle message reading, which requires data synchronization when a user enters a confirmation request for a simple notification, but can initialize the badge count internally in the noti version.

In addition, the noti version can provide a reception list of simple notifications. For example, as shown in FIG. 10, when the user selects the notification pop-up 800, notifications received during the recent certain period of time (e.g., one week) A list 1030 may be provided. The notification list 1030 may consist of a list in which simple notifications are sorted in the order in which they were most recently received, and simple notifications may be grouped and displayed based on unit time (eg, 1 day) or sender. To simplify and simplify the noti version, it is also possible to not support the notification list 1030 and keep only the most recently received simple notifications.

According to embodiments of the present invention, when implementing a service that provides notifications for multiple devices, server tasks can be significantly reduced by applying simple notifications that do not require data synchronization for some devices, thereby lowering implementation complexity. there is.

The device described above may be implemented with hardware components, software components, and/or a combination of hardware components 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), and a programmable logic unit (PLU). It may be implemented using one or more general-purpose or special-purpose computers, such as a logic unit, microprocessor, or any other device capable of executing and responding to instructions. The processing device may execute an operating system (OS) and one or more software applications running on the operating system. Additionally, a processing device may access, store, manipulate, process, and generate data in response to the execution of software. For ease of understanding, a single processing device may be described as being used; however, those skilled in the art will understand that a processing device includes multiple processing elements and/or multiple types of processing elements. It can be seen that it may include. For example, a processing device may include a plurality of processors or one processor and one controller. Additionally, other processing configurations, such as parallel processors, are possible.

Software may include a computer program, code, instructions, or a combination of one or more of these, which may configure a processing unit to operate as desired, or may be processed independently or collectively. You can command the device. The software and/or data may be embodied in any type of machine, component, physical device, computer storage medium or device for the purpose of being interpreted by or providing instructions or data to the processing device. there is. Software may be distributed over networked computer systems and stored or executed in a distributed manner. Software and data may be stored on one or more computer-readable recording media.

The method according to the embodiment may be implemented in the form of program instructions that can be executed through various computer means and recorded on a computer-readable medium. At this time, the medium may continuously store a computer-executable program, or temporarily store it for execution or download. In addition, the medium may be a variety of recording or storage means in the form of a single or several pieces of hardware combined. It is not limited to a medium directly connected to a computer system and may be distributed over a network. Examples of media include magnetic media such as hard disks, floppy disks, and magnetic tapes, optical recording media such as CD-ROMs and DVDs, magneto-optical media such as floptical disks, And there may be something configured to store program instructions, including ROM, RAM, flash memory, etc. Additionally, examples of other media include recording or storage media managed by app stores that distribute applications, sites or servers that supply or distribute various other software, etc.

As described above, although the embodiments have been described with limited examples and drawings, various modifications and variations can be made by those skilled in the art from the above description. For example, the described techniques are performed in a different order than the described method, and/or components of the described system, structure, device, circuit, etc. are combined or combined in a different form than the described method, or other components are used. Alternatively, appropriate results may be achieved even if substituted or substituted by an equivalent.

Therefore, other implementations, other embodiments, and equivalents of the claims also fall within the scope of the claims described below.

Claims (20)

In a method executed on a computer system,
The computer system includes at least one processor configured to execute computer-readable instructions contained in a memory,
The above method is,
registering, by the at least one processor, at least one other device on which the application is not installed, used by a user of a device on which the application is installed; and
Forwarding, by the at least one processor, a notification related to the application to the other device in the form of a simplex notice.
Including,
The delivery step is
Delivering notifications related to the application to multi-devices, including a device on which the application is installed and at least one other device on which the application is not installed,
The notification delivered to the device on which the application is installed includes a function that requires data synchronization work related to the application,
A notification delivered to at least one other device on which the application is not installed omits the function requiring the data synchronization task.
A method characterized by . delete According to paragraph 1,
The registration step is,
Registering the other device through authentication through the application installed on the device
A method characterized by . According to paragraph 1,
The registration step is,
Providing a notification application to the other device after authenticating the other device; and
Registering another device on which the notification application is installed as a device for delivering the simple notification
How to include . According to paragraph 1,
The above method is,
Generating, by the at least one processor, a notification message using abbreviated information of notification content when an event requiring notification occurs.
How to further include . According to clause 5,
The generating step is,
Creating a notification message delivered to the device by distinguishing between a notification message delivered to the other device
A method characterized by . According to clause 5,
The generating step is,
Creating a notification message delivered to the other device with more condensed information than the notification message delivered to the device.
A method characterized by . According to paragraph 4,
The environment settings for the simple notification are set independently through the notification application, or are set identically to the notification environment settings set on the application.
A method characterized by . According to paragraph 4,
The notification application displays a badge count indicating the unconfirmed number of simple notifications on the other device regardless of the application.
A method characterized by . According to paragraph 4,
The notification application maintains a list of simple notifications received over a certain period of time and displays the list by sorting or grouping it by a certain standard.
A method characterized by . A non-transitory computer-readable recording medium on which a program for executing the method of any one of claims 1, 3 to 10 is recorded on a computer. Memory; and
At least one processor coupled to the memory and configured to execute computer-readable instructions contained in the memory
Including,
The at least one processor,
a device registration unit that registers at least one other device on which the application is not installed, used by a user of a device on which the application is installed; and
A notification delivery unit that delivers notifications related to the application to the other device as a simple notification in the form of a one-way notification.
Including,
The notification delivery unit,
Delivering notifications related to the application to multiple devices, including a device on which the application is installed and at least one other device on which the application is not installed,
The notification delivered to the device on which the application is installed includes a function that requires data synchronization work related to the application,
A notification delivered to at least one other device on which the application is not installed omits the function requiring the data synchronization task.
A computer system characterized by . delete According to clause 12,
The device register is,
Registering the other device through authentication through the application installed on the device
A computer system characterized by . According to clause 12,
The device register is,
After authenticating the other device, provide a notification application to the other device,
Registering another device on which the notification application is installed as a device for delivering the simple notification
A computer system characterized by . According to clause 12,
The at least one processor,
When an event requiring notification occurs, a notification generator unit generates a notification message using abbreviated information from the notification content.
A computer system further comprising: According to clause 16,
The notification generator,
Creating a notification message delivered to the device by distinguishing between a notification message delivered to the other device
A computer system characterized by . According to clause 16,
The notification generator,
Generating a notification message delivered to the other device with more condensed information than the notification message delivered to the device.
A computer system characterized by . According to clause 15,
The environment settings for the simple notification are set independently through the notification application, or are set identically to the notification environment settings set on the application.
A computer system characterized by . According to clause 15,
The notification application displays a badge count indicating the unconfirmed number of simple notifications on the other device regardless of the application.
A computer system characterized by .

Images