Display control program, display control method, and information processing device

Abstract

To reduce a load on a server associated with execution of push notifications.SOLUTION: When a processing unit 11 of an information processing device 10 receives first distribution information 1, which is push-distributed from a server 21 and includes a message 1a and identification information 1b indicating whether server access is required, the processing unit 11 determines whether server access is required on the basis of the identification information 1b. When the processing unit 11 determines that server access is not required, the processing unit 11 displays the message 1a on the display device. On the other hand, when the processing unit 11 determines that server access is required, the processing unit 11 requests the server 22 to transmit second distribution information 2 corresponding to the first distribution information 1, and upon receiving the second distribution information 2 from the server 22, the processing unit 11 displays display information on the basis of the second distribution information 2 on the display device.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to a display control program, a display control method, and an information processing device. [Background technology]

[0002] 2. Description of the Related Art Push notification services, which are push-type message delivery services, are known as services for mobile devices such as smartphones. As an example of related technology, an information processing device has been proposed that, upon receiving a user operation in response to a push notification including a notification regarding event options, launches an application to display the options, and, upon receiving a user operation in response to the options, outputs information about the selected option to a management server and displays the linked content associated with the selected option.

[0003] Furthermore, a notification program has also been proposed that is executed on each mobile device that obtains information from the distribution system, that starts a process in response to a notification from the distribution system, that waits for a predetermined time so as to distribute the waiting time of the mobile devices, and that executes a process to obtain a predetermined message from the distribution system after the predetermined time has elapsed. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Patent No. 7339706 specification [Patent Document 2] Japanese Patent Application Laid-Open No. 2017-49730 Summary of the Invention [Problem to be solved by the invention]

[0005] In the above-described push notification service, when a message is pushed to a mobile device, the message is displayed on the mobile device's display device. Furthermore, when a selection operation is performed on a displayed message, the server is accessed by the application processing corresponding to the message, and detailed content of the message may be obtained from the server and displayed on the display device. In such processing, the server is frequently accessed by the mobile device to which the push notification is sent, which poses a problem of increased access load on the server. In particular, when messages are pushed to a large number of mobile devices simultaneously, the access load on the server can become extremely large.

[0006] In one aspect, the present invention aims to provide a display control program, a display control method, and an information processing device that can reduce the load of accessing a server associated with executing a push notification. [Means for solving the problem]

[0007] In one proposal, a display control program is provided that causes a computer to execute a process in which, when the computer receives first distribution information that is push-distributed from a first server and includes a message and identification information indicating whether server access is required, the program determines whether server access is required based on the identification information, and if it determines that server access is not required, the program displays the message on the computer's display device, and if it determines that server access is required, the program requests a second server to send second distribution information corresponding to the first distribution information, and upon receiving the second distribution information from the second server, displays display information based on the second distribution information on the display device.

[0008] Also, one proposal provides a display control method in which, when a computer receives first distribution information push-distributed from a first server, the first distribution information including a message and identification information indicating whether server access is required, the computer determines whether server access is required based on the identification information, and if it determines that server access is not required, the computer displays the message on a display device of the computer, and if it determines that server access is required, the computer requests a second server to send second distribution information corresponding to the first distribution information, and upon receiving the second distribution information from the second server, the computer displays display information based on the second distribution information on the display device.

[0009] Furthermore, in one proposal, an information processing device that executes processing similar to the above-described display control method is provided. [Effects of the Invention]

[0010] On the one hand, it reduces the load on the server that is required to execute push notifications. [Brief explanation of the drawings]

[0011] [Figure 1] 1 illustrates a configuration example and a processing example of an information processing system according to a first embodiment; [Figure 2] FIG. 10 illustrates an example of a configuration of an information processing system according to a second embodiment. [Figure 3] FIG. 2 is a diagram illustrating an example of the hardware configuration of a user terminal. [Figure 4] FIG. 10 is a sequence diagram illustrating a comparative example of a message delivery process using a push notification. [Figure 5] FIG. 2 is a diagram illustrating an example of the configuration of processing functions included in a user terminal. [Figure 6] FIG. 10 is a diagram illustrating an example of a data configuration of push notification message information. [Figure 7] FIG. 10 is a sequence diagram illustrating a first example of a message delivery process using a push notification. [Figure 8] FIG. 10 is a sequence diagram illustrating a second example of a message delivery process using a push notification. [Figure 9]FIG. 10 is a diagram showing a first display example of a message. [Figure 10] FIG. 10 is a diagram showing a second display example of a message. [Figure 11] FIG. 10 is a sequence diagram illustrating an example of processing when a start-up operation of a patient support application is performed. [Figure 12] 10 is a flowchart illustrating an example of processing by an OS processing unit of a user terminal. [Figure 13] 10 is a first flowchart showing an example of processing by an application processing unit of a user terminal. [Figure 14] 10 is a second flowchart illustrating an example of processing by an application processing unit of the user terminal. DETAILED DESCRIPTION OF THE INVENTION

[0012] Hereinafter, an embodiment of the present invention will be described with reference to the drawings. [First embodiment] Fig. 1 is a diagram illustrating an example of the configuration and processing of an information processing system according to a first embodiment. The information processing system illustrated in Fig. 1 includes an information processing device 10 and servers 21 and 22. This information processing system realizes a push notification service, which is a push-type message delivery service.

[0013] The information processing device 10 is a device used by a user, and is, for example, a portable information processing terminal. The information processing device 10 has a processing unit 11. The processing unit 11 is, for example, a processor. An OS (Operating System) program 12a and a display control program 12b are installed in the information processing device 10. The OS program 12a and the display control program 12b are executed by the processing unit 11. The display control program 12b is an application program executed on the OS program 12a.

[0014] The server 21 push-distributes the first distribution information 1 to the information processing device 10. The first distribution information 1 includes a message 1a to be displayed on the information processing device 10 and identification information 1b indicating whether server access is required.

[0015] The server 22 transmits second distribution information 2 corresponding to the first distribution information 1 to the information processing device 10. Both the first distribution information 1 and the second distribution information 2 are information related to the display control program 12b. The second distribution information 2 includes, for example, a message to notify the user. In this case, the message 1a included in the first distribution information 1 may be part of the message included in the second distribution information 2. As another example, the message 1a may be the title of the message included in the second distribution information 2 or a sentence that briefly explains the message.

[0016] The server 21 and the server 22 may be realized as the same server. The following describes the processing of the information processing device 10 when the first distribution information 1 is push-distributed from the server 21 to the information processing device 10.

[0017] When the information processing device 10 receives the first distribution information 1, the processing unit 11 of the information processing device 10 determines, in accordance with the display control program 12b, whether or not server access is required based on the identification information 1b included in the first distribution information 1 (step S2a). The determination process of step S2a is performed, for example, in accordance with the following process executed by the processing unit 11 in accordance with the OS program 12a.

[0018] When the information processing device 10 receives the first distribution information 1, the processing unit 11 displays at least a part of the message 1a included in the first distribution information 1 on a display device (not shown) of the information processing device 10 (step S1a). As a result, at least a part of the push-distributed message 1a is automatically displayed on the display device and notified to the user.

[0019] Furthermore, when a selection operation is performed on the displayed message 1a while at least a portion of the message 1a is displayed as described above, the processing unit 11 calls the display control program 12b and executes the processing of step S2a (step S1b). This selection operation is performed, for example, so that the user can check the details of the delivered message 1a. Furthermore, if the information processing device 10 has a touch panel, the selection operation may be, for example, a tap operation on the area where at least a portion of the message 1a is displayed.

[0020] If the processing unit 11 determines in the determination process of step S2a that server access is unnecessary, it causes the display device to display the message 1a included in the first distribution information 1 in accordance with the display control program 12b (step S2b). In this process, the processing unit 11 may cause the display device to display the entire message 1a.

[0021] On the other hand, if the processing unit 11 determines in the determination process of step S2a that server access is necessary, it executes the following process in accordance with the display control program 12b. The processing unit 11 requests the server 22 to transmit second distribution information 2 corresponding to the first distribution information 1 (step S2c). Upon receiving the second distribution information 2 from the server 22, the processing unit 11 causes the display device to display display information based on the second distribution information 2 (step S2d). This display information may include, for example, detailed message content corresponding to the message 1a, or may include link information to a web page, a selection button for accepting a user selection operation, and the like.

[0022] In the above-described processing of the information processing device 10, when the user attempts to further display details of the information displayed in step S1a, access to the server 22 is performed only when necessary based on the identification information 1b. Therefore, compared to the case where the server 22 is always accessed unconditionally, the access load on the server 22 can be reduced, and the processing load on the server 22 can also be reduced.

[0023] In particular, the first distribution information 1 may be push-distributed simultaneously to a large number of information processing devices 10. In each information processing device 10 that receives the first distribution information 1 distributed simultaneously in this manner, if the user attempts to further display details of the information displayed in step S1a, the access load on the server 22 will be extremely high. The above-described processing of the information processing device 10 makes it possible to reduce the probability of such an occurrence.

[0024] Note that there may be cases where the determination process of step S2a is executed in response to the information processing device 10 receiving the first distribution information 1. For example, if the information processing device 10 receives the first distribution information 1 while the display screen of the display control program 12b is displayed in the foreground on the display device, the determination process of step S2a may be executed without waiting for the selection operation of step S1b. Even in this case, the above-described process of the information processing device 10 accesses the server 22 only when necessary, thereby reducing the access load on the server 22.

[0025] Second Embodiment Fig. 2 is a diagram showing an example of the configuration of an information processing system according to the second embodiment. The information processing system shown in Fig. 2 includes user terminals 100a, 100b, 100c, ..., an application management server 210, a message management server 220, and a push notification server 230. These devices are connected to each other via a network 200. In this information processing system, a push notification service, which is a push-type message delivery service, is realized.

[0026] The user terminals 100a, 100b, 100c, etc. are portable information processing terminals used by users, such as smartphones. In this embodiment, the users are patients who visit a hospital. A patient support app (application) that supports the users' hospital visits is installed in the user terminals 100a, 100b, 100c, etc. Furthermore, the user terminals 100a, 100b, 100c, etc. are client terminals that receive a push notification service and are capable of receiving and displaying messages via push notification.

[0027] In the following description, when the user terminals 100a, 100b, 100c, . . . are referred to without distinction, they may be referred to as "user terminals 100." The application management server 210 is a server device that provides services to users through patient support applications and is capable of communicating with the user terminal 100 on which the patient support application is installed. The application management server 210 also accepts a delivery request for a message to be sent to a user from a message creator (e.g., a hospital official) and requests the message management server 220 to deliver the message.

[0028] The message management server 220 is a server device that manages the delivery of messages. The message management server 220 creates message information for push notification based on a delivery request from the application management server 210, and transmits the created message information to the push notification server 230 to request delivery.

[0029] The push notification server 230 is a server device that executes message delivery by push notification. The push notification server 230 delivers message information received from the message management server 220 to the destination user terminal 100 by push notification (push delivery).

[0030] The user terminals 100 (100a, 100b, 100c, etc.) are an example of the information processing device 10 in FIG. 1. The push notification server 230 is an example of the server 21 in FIG. 1. The application management server 210 is an example of the server 22 in FIG. 1.

[0031] At least one of the application management server 210, the message management server 220, and the push notification server 230 may be, for example, a virtual server on the cloud. At least two of the application management server 210, the message management server 220, and the push notification server 230 may be the same server.

[0032] Fig. 3 is a diagram showing an example of the hardware configuration of a user terminal. The user terminal 100 is realized, for example, as a computer as shown in Fig. 3. The user terminal 100 shown in Fig. 3 includes a processor 101, a RAM (Random Access Memory) 102, a flash memory 103, a display device 104, an input device 105, and a wireless communication interface (I / F) 106.

[0033] The processor 101 (processor circuit) performs overall control of the entire user terminal 100. The processor 101 is, for example, a central processing unit (CPU), a micro processing unit (MPU), a digital signal processor (DSP), an application specific integrated circuit (ASIC), or a programmable logic device (PLD). The processor 101 may also be a combination of two or more elements of a CPU, MPU, DSP, ASIC, or PLD.

[0034] The RAM 102 is used as the main storage device of the user terminal 100. The RAM 102 temporarily stores at least a part of the OS and application programs to be executed by the processor 101. The RAM 102 also stores various data necessary for processing by the processor 101.

[0035] The flash memory 103 is used as an auxiliary storage device for the user terminal 100. The flash memory 103 stores the OS, application programs, and various data. Note that other types of non-volatile storage devices, such as a hard disk drive (HDD), can also be used as the auxiliary storage device.

[0036] The display device 104 displays an image in accordance with an instruction from the processor 101. The display device 104 may be a liquid crystal display or an organic EL (ElectroLuminescence) display.

[0037] The input device 105 receives an input operation from a user and transmits a signal corresponding to the input operation to the processor 101. In this embodiment, the input device 105 includes, for example, a touch panel that is integrally provided with the display device 104.

[0038] The wireless communication interface 106 wirelessly transmits and receives data to and from other devices such as the application management server 210 and the push notification server 230 via the network 200 .

[0039] The above hardware configuration can realize the processing functions of the user terminal 100. Note that the application management server 210, the message management server 220, and the push notification server 230 can also be realized as computers including a processor, a main storage device, an auxiliary storage device, and the like.

[0040] As described above, a patient support app is installed on the user terminal 100. The user terminal 100 can also receive messages corresponding to the patient support app via push notification. Such push notification can, for example, notify the patient of the date and time of an appointment in advance, notify the number of patients waiting for their appointment on the day of the appointment, or notify the hospital of announcements such as closed days.

[0041] In the following description, a comparative example of a message delivery process using a push notification will first be shown using FIG. 4, and the message delivery process in this embodiment will be described from FIG. 5 onwards. FIG. 4 is a sequence diagram showing a comparative example of a message delivery process using a push notification.

[0042] [Step S11] When the application management server 210 receives a delivery request for a message to be sent to a user from the message creator, the application management server 210 requests the message management server 220 to deliver the message. This delivery request includes a user ID that identifies the destination user and token information that identifies the user terminal of the user.

[0043] [Step S12] The message management server 220 stores message information indicating the content of the message requested for delivery. Hereinafter, this message information will be referred to as "detailed message information."

[0044] Based on this detailed message information, the message management server 220 also creates message information for push notification that conforms to the push notification data format. Hereinafter, this message information will be referred to as "push notification message information." Token information that identifies the user terminal of the user to whom the push notification message information is to be delivered is set in the push notification message information. The message management server 220 sends the created push notification message information to the push notification server 230, requesting a push notification to the user terminal.

[0045] [Step S13] The push notification server 230 delivers the push notification message information to the user terminal indicated by the token information by push notification. [Step S14] When the user terminal 100 receives the push notification message information, the OS processes the message to display it on the display device 104. Here, it is assumed that the user terminal 100 is in a locked state in which input operations are restricted, and the message is displayed on the lock screen (standby screen).

[0046] [Step S15] When the user sees the message display, he or she performs a predetermined selection operation (tap operation in this case) on the message display area to check the details of the message. Then, the patient support app is called by the OS processing in the user terminal 100. It is assumed here that the patient support app is running and that the user has already logged in to the app management server 210 using a user ID.

[0047] [Step S16] The user terminal 100, through processing of the patient support application, requests the application management server 210 to acquire the original message information (the detailed message information stored in the message management server 220 in step S11).

[0048] [Step S17] The application management server 210 requests the message management server 220 to acquire detailed message information, specifying the requesting user ID. [Step S18] The message management server 220 transmits the detailed message information saved in step S11 to the application management server 210.

[0049] <Step S19> The application management server 210 transmits the received detailed message information to the user terminal 100. [Step S20] The user terminal 100, through processing by the patient support app, displays a message based on the received detailed message information on the display device 104. At this time, the screen of the patient support app is displayed, and the message is displayed on that screen.

[0050] In the above process, when a tap operation is performed on a message delivered to the user terminal 100 by push notification, the user terminal 100 always accesses the application management server 210. In addition, the application management server 210 always accesses the message management server 220. The reason for this is that there are limitations on the content of messages that can be delivered by push notification.

[0051] For example, a message delivered from a hospital to a user may contain, in addition to text information, link information to a uniform resource locator (URL) on a network and a selection operation unit (such as a selection button) for receiving a selection operation from the user. On the other hand, a push notification can contain only text information in the message body. Therefore, in the process of step S12 by the message management server 220, text information to be included in the payload of the push notification is created based on the original detailed message information for which delivery was requested, and set as the push notification message information. In this case, when a message is delivered by push notification, only a portion of the message included in the original detailed message information is notified to the user. Therefore, when a tap operation is performed on a message delivered by push notification, server access is required to obtain the detailed message information.

[0052] Another reason is as follows: Generally, push notifications are often used by a service corresponding to an app to notify a user of new information that the service wants the user to know about. In such cases, when a user notices a message displayed by a push notification, the user taps the message to check the content of the new information. For this reason, in many cases, a natural processing procedure is for the user terminal 100 to access a server to obtain the content of the new information in response to a tap operation on a message by a push notification.

[0053] As described above, in the above process, when a message is delivered by push notification, access is always generated to the application management server 210 and the message management server 220. This increases the processing load on the application management server 210 and the message management server 220, which may cause a delay in transmission of the original message information to the user terminal 100.

[0054] In particular, when messages are delivered by push notification, messages such as notifications of closed days may be delivered to a large number of patients at once. In such cases, the access load on the application management server 210 and the message management server 220 may become extremely high, which may significantly delay or even make it impossible to send detailed message information to the user terminal 100. Furthermore, the processing load on the application management server 210 and the message management server 220 may become excessive, which may affect the entire service.

[0055] To address this problem, in this embodiment, the user terminal 100 that receives a message via push notification accesses the server only when necessary. Specifically, identification information indicating whether server access is required is set in the push notification message information delivered by push notification. Based on this identification information, the user terminal 100 accesses the application management server 210 and requests detailed message information only when server access is required. This reduces the access load on the application management server 210 and the message management server 220.

[0056] 5 is a diagram showing an example of the configuration of processing functions provided in a user terminal 100. The user terminal 100 includes an OS processing unit 110, an application processing unit 120, and a user information storage unit . The processing of the OS processing unit 110 is realized by the processor 101 executing an OS program. The OS processing unit 110 includes a push notification processing unit 111 that executes processing related to a message delivered by push notification.

[0057] The processing of the application processing unit 120 is realized by the processor 101 executing a program of the patient support application. The application processing unit 120 includes a login processing unit 121 and an information display processing unit 122. The login processing unit 121 executes a login process to the application management server 210 using a user ID. The information display processing unit 122 executes a process to acquire a message from the application management server 210.

[0058] The user information storage unit 130 is a storage area allocated in a storage device provided in the user terminal 100, such as the memory 102 or the flash memory 103. The user information storage unit 130 stores information about the user, such as a user ID and a login password. The information stored in the user information storage unit 130 is used, for example, during login processing by the login processing unit 121.

[0059] In the following description, the push notification message information is an example of the first delivery information 1 in FIG. 1, and the detailed message information is an example of the second delivery information 2 in FIG. 6 is a diagram illustrating an example of the data configuration of message information for push notification. The message information for push notification includes, for example, setting items such as "token," "platform," "message," and "extend."

[0060] "Token" is token information that identifies the destination user terminal. "Platform" is OS identification information that identifies the OS installed on the destination user terminal. For example, a setting value of "platform" of 1 indicates OS-A, and a setting value of 2 indicates OS-B. "Message" indicates the content (payload) that will be displayed in the push notification display area, and includes the name of the hospital that created the message, the message title, and the message body. The message body can contain text information of a certain number of bytes or less.

[0061] "Extend" indicates additional information, and includes the additional items "pushUsers" and "type." "PushUsers" indicates the user ID and user name of the recipient user. "Type" indicates the message type of the delivered message.

[0062] For example, if the setting value of "type" is 1, it indicates that the delivered message is a normal message that contains only text information. If the setting value of "type" is 2, it indicates that the corresponding detailed message information contains options to be selected by the user. In this case, the display screen based on the detailed message information contains a selection operation unit, such as a selection button, that accepts selection operations from the user. If the setting value of "type" is 3, it indicates that the detailed message contains link information to a specified URL. If the setting value of "type" is 4, it indicates that the detailed message contains both options and link information.

[0063] The set value of this "type" is determined by the message management server 220. Furthermore, in the user terminal 100, "type" is used as identification information indicating whether server access is possible. That is, in the user terminal 100, if the set value of "type" is 1, it is determined that server access is not necessary, and if the set value is other than 1, it is determined that server access is necessary.

[0064] The "type" setting may include, for example, a value indicating that the detailed message contains text information with a data volume exceeding the maximum number of bytes that can be included in the message body of a push notification. This setting also requires server access.

[0065] 7 is a sequence diagram showing a first example of a message delivery process using a push notification. Fig. 7 shows an example in which a message is delivered using a push notification without server access from the user terminal 100.

[0066] [Step S31] When the application management server 210 receives a delivery request for a message to be sent to a user from the message creator, the application management server 210 requests the message management server 220 to deliver the message. At this time, a user ID identifying the destination user and token information identifying the user terminal of the user are specified.

[0067] [Step S32] The message management server 220 analyzes the content of the message requested for delivery and determines the message type. In this process, the content of the message body information for displaying the message body on the user terminal 100 is analyzed. Here, it is assumed that the message body information contains only text information with a data volume equal to or less than the number of bytes that can be delivered by push notification. In this case, the message type is determined to be a normal message.

[0068] [Step S33] The message management server 220 creates push notification message information. At this time, token information specified by the application management server 210 is set in "token" of the push notification message information. Furthermore, text information included in the above message body information is set in "message" as the message body. Furthermore, "type" is set to 1. The message management server 220 sends the created push notification message information to the push notification server 230, and requests a push notification to the user terminal.

[0069] [Step S34] The push notification server 230 delivers the push notification message information to the user terminal indicated by the token information by push notification (push delivery). [Step S35] The user terminal 100 receives the push notification message information. At this time, it is assumed that the user terminal 100 is in a locked state and the lock screen is displayed on the display device 104. The OS processing unit 110 of the user terminal 100 superimposes a push notification image including the content set in the "message" of the push notification message information on the lock screen. Note that the push notification image may display text information from the beginning of the message body in the "message" up to a predetermined number of characters.

[0070] [Step S36] The user who views the push notification image taps on the push notification image to check the details of the message. When the OS processing unit 110 receives the tap operation on the push notification image, it calls the patient support app. Here, it is assumed that the patient support app is running and the application processing unit 120 has already started up. It is also assumed that the application processing unit 120 has already logged in to the application management server 210 using a user ID.

[0071] [Step S37] The application processing unit 120 determines the message type based on the value set in the “type” parameter in the push notification message information, and then determines whether server access is required based on the determined message type. In this case, the value set in “type” is 1, and the message type is a normal message, so it is determined that server access is not required.

[0072] [Step S38] The application processing unit 120 displays an application screen corresponding to the patient support application on the display device 104, and displays a message display image including the content set in the "message" field of the push notification message information on the application screen. The entire message text in the "message" field is displayed in this message display image.

[0073] As described above, when the message type of the message to be delivered is a normal message, the application processing unit 120 of the user terminal 100 displays a message display image based on the push notification message information without accessing the server. Therefore, the user terminal 100 does not access the application management server 210, and the associated access from the application management server 210 to the message management server 220 does not occur. This reduces the access load on the application management server 210 and the message management server 220. In particular, when push notification message information is delivered simultaneously to a large number of user terminals 100, it is possible to avoid a situation in which the access load on the application management server 210 and the message management server 220 becomes excessive.

[0074] Fig. 8 is a sequence diagram showing a second example of a message delivery process by push notification. Fig. 8 shows an example in which server access occurs from the user terminal 100 when a message is delivered by push notification.

[0075] [Step S41] When the application management server 210 receives a delivery request for a message to be sent to a user from the message creator, the application management server 210 requests the message management server 220 to deliver the message. At this time, a user ID identifying the destination user and token information identifying the user terminal of the user are specified.

[0076] [Step S42] The message management server 220 analyzes the content of the message requested for delivery and determines the message type. As in step S32 of FIG. 7, the content of the message body information for displaying the message body on the user terminal 100 is analyzed. Here, it is assumed that the message body information includes at least one of link information or options (selection operation section). In this case, the message type is determined to be a type other than a normal message.

[0077] If the message type is determined to be other than a normal message, the message management server 220 creates detailed message information for the message requested to be delivered and stores it in association with the user ID. The detailed message information includes the message body information described above.

[0078] [Step S43] The message management server 220 creates push notification message information. At this time, token information specified by the application management server 210 is set in "token" of the push notification message information. Furthermore, text information with a predetermined number of bytes of data from the beginning of the text information included in the message body information is set in "message" as the message body. Furthermore, one of 2 to 4 is set in "type." The message management server 220 sends the created push notification message information to the push notification server 230, and requests a push notification to the user terminal.

[0079] [Step S44] The push notification server 230 delivers the push notification message information to the user terminal indicated by the token information by push notification (push delivery). [Step S45] The user terminal 100 receives the push notification message information. At this time, it is assumed that the user terminal 100 is in a locked state and a lock screen is displayed on the display device 104. The OS processing unit 110 of the user terminal 100 superimposes a push notification image including the content set in the "message" field of the push notification message information on the lock screen.

[0080] [Step S46] The user who views the push notification image taps on the push notification image to check the details of the message. When the OS processing unit 110 receives the tap operation on the push notification image, it calls the patient support app. Here, as in step S36 of FIG. 7, it is assumed that the patient support app is running and the application processing unit 120 has already started. It is also assumed that the application processing unit 120 has already logged in to the application management server 210 using a user ID.

[0081] [Step S47] The application processing unit 120 determines the message type based on the value set in “type” in the push notification message information, and then determines whether server access is required based on the determined message type. In this case, the value set in “type” is one of 2 to 4, and the message type is a type other than a normal message, so it is determined that server access is required.

[0082] <Step S48> The application processing unit 120 requests the application management server 210 to acquire detailed message information corresponding to the received push notification message information, specifying the user ID of the user.

[0083] [Step S49] The application management server 210 requests the message management server 220 to acquire detailed message information by specifying the user ID. [Step S50] The message management server 220 transmits the detailed message information saved in step S42 to the application management server 210 based on the specified user ID.

[0084] <Step S51> The application management server 210 transmits the received detailed message information to the user terminal 100. [Step S52] The user terminal 100 receives the detailed message information. In response, the application processing unit 120 displays an application screen corresponding to the patient support application on the display device 104, and displays a message display screen based on the detailed message information on the application screen.

[0085] As described above, when the message type of the message to be delivered is a type other than a normal message, the application processing unit 120 of the user terminal 100 accesses the application management server 210 to acquire the detailed message. Accompanying this access, the application management server 210 also accesses the message management server 220.

[0086] 7 and 8, the application processing unit 120 accesses the server only when necessary based on the message type, which reduces the access load on the application management server 210 and the message management server 220 when a message is delivered by push notification.

[0087] 7 and 8 illustrate an example in which a message is delivered by push notification to a specific user terminal 100, but a message may also be delivered simultaneously to a large number of user terminals 100. In this case, it is possible to reduce the possibility that the access load on the application management server 210 and the message management server 220 will become excessive.

[0088] Fig. 9 is a diagram showing a first display example of a message. Fig. 9 shows an example in which a message is delivered by push notification but no server access occurs from the user terminal 100.

[0089] 9 shows an example in which push notification message information is received when the user terminal 100 is in a locked state. At this time, a lock screen 140 is displayed on the display device 104, and a push notification image 141 is superimposed on the lock screen 140. The push notification image 141 includes a title display section 142, a user name display section 143, and a message body display section 144.

[0090] The title display area 142 displays the message title set in "message" of the push notification message information. The user name display area 143 displays the user name set in "pushUsers" of the push notification message information. The message body display area 144 displays the message body set in "message" of the push notification message information. This message body display area 144 may display only a predetermined number of characters from the beginning of the text information of the set message body.

[0091] When the push notification image 141 is tapped, a message display screen 150 by the patient support app is displayed, as shown on the right side of Fig. 9. It is assumed here that the patient support app was already running when the tap was performed. The message display screen 150 includes a hospital name display section 151, a user name display section 152, a message body display section 153, and operation buttons 154.

[0092] The hospital name display section 151 displays the hospital name set in "message" of the push notification message information. The user name display section 152 displays the user name set in "pushUsers" of the push notification message information. The message body display section 153 displays the entire message body (text information) set in "message" of the push notification message information. When an input operation is performed on the operation button 154, the display of the message display screen 150 ends, and, for example, the main screen of the patient support app is displayed.

[0093] Fig. 10 is a diagram showing a second display example of a message. Fig. 10 shows an example in which server access occurs from the user terminal 100 when a message is delivered by push notification.

[0094] The left side of Fig. 10 shows an example of a case where push notification message information is received when the user terminal 100 is in a locked state. At this time, as in the case on the left side of Fig. 9, a lock screen 160 is displayed on the display device 104, and a push notification image 161 is superimposed on the lock screen 160. The push notification image 161 includes a title display area 162, a user name display area 163, and a message body display area 164. The relationship between these display areas and the information in the push notification message information is the same as in the case on the left side of Fig. 9.

[0095] The user taps on the push notification image 161. Here, it is assumed that the patient support app was already running when the tapping operation was performed. In this case, the server is accessed and detailed message information is acquired. As an example, it is assumed that the message type is "Choices and link information included" ("type" setting value = 4).

[0096] When a tap operation is performed on the push notification image 161 and detailed message information is acquired, a message display screen 170 by the patient support app is displayed, as shown on the right side of Fig. 10. The message display screen 170 includes a hospital name display section 171, a user name display section 172, and a message body display section 173.

[0097] The hospital name display section 171 displays the hospital name set in the detailed message information. The user name display section 172 displays the user name set in the detailed message information. The message body display section 173 is displayed based on the message body information included in the detailed message information. The message body display section 173 includes a text display section 173a, a link information display section 173b, selection buttons 173c and 173d, and a send button 173e.

[0098] The text display section 173a displays text information included in the message body information. In this example, text information requesting cooperation with a survey is displayed.

[0099] Link information display section 173b displays link information included in the message body information. This link information is information for linking to a questionnaire response page, and when a selection operation is performed on link information display section 173b, the questionnaire response page is displayed on display device 104.

[0100] The select button 173c is selected when answering the questionnaire. The select button 173d is selected when not answering the questionnaire. The send button 173e is selected after a selection operation is performed on either the select button 173c or 173d. When the send button 173e is selected after the select button 173c is selected, a link to a questionnaire answer page is performed, and this answer page is displayed on the display device 104. On the other hand, when the send button 173e is selected after the select button 173d is selected, the display of the message display screen 170 ends, and, for example, the main screen of the patient support app is displayed.

[0101] FIG. 11 is a sequence diagram showing an example of processing when a start-up operation of the patient support application is performed. [Step S61] When an operation to start the patient support application (a tap on the icon of the patient support application) is performed on the user terminal 100, the OS processing unit 110 starts the patient support application.

[0102] [Step S62] Execution of the patient support application is started, and the application processing unit 120 is launched. <Step S63> The application processing unit 120 executes a login process for the application management server 210 using the information stored in the user information storage unit 130.

[0103] [Step S64] If the login process is successful, the application management server 210 transmits content data to the user terminal 100. [Step S65] When the content data is received by the user terminal 100, the application processing unit 120 displays the content on the display device 104. For example, the main screen of the patient support application is displayed.

[0104] As described above, when the application processing unit 120 is started in response to the start-up operation of the patient support application, server access is performed for login. Next, the processing of the user terminal 100 will be described using a flowchart.

[0105] FIG. 12 is a flowchart illustrating an example of processing by the OS processing unit of the user terminal. [Step S71] When the user terminal 100 receives push notification message information delivered by push notification from the push notification server 230, the process proceeds to step S72.

[0106] [Step S72] The push notification processing unit 111 of the OS processing unit 110 determines whether the application screen of the patient support application is currently displayed in the foreground. If the application screen is currently displayed, the process proceeds to step S76. If the application screen is not currently displayed (if the lock screen is currently displayed or if the application screen of another application is currently displayed), the process proceeds to step S73.

[0107] [Step S73] The push notification processing unit 111 superimposes a push notification image containing the content set in the “message” field of the push notification message information on the currently displayed screen. This displays at least a part of the message in the text information included in the push notification message information.

[0108] [Step S74] The push notification processing unit 111 determines whether a tap operation on the push notification image has been received. If a tap operation has not been received, the process waits for a predetermined period of time, and then the determination process of step S74 is executed again. On the other hand, if a tap operation has been received, the process proceeds to step S75.

[0109] [Step S75] The push notification processing unit 111 determines whether the patient support app is running (whether the app processing unit 120 is running). If the patient support app is running, the process proceeds to step S76. If the patient support app is not running, the process proceeds to step S77.

[0110] [Step S76] The push notification processing unit 111 calls the currently running patient support application (i.e., the currently running application processing unit 120) and passes the received push notification message to the application processing unit 120.

[0111] [Step S77] The push notification processing unit 111 issues an instruction to start the patient support app, which starts the execution of the patient support app, launches the app processing unit 120, and starts the process shown in FIG.

[0112] 12, when the user terminal 100 receives push notification information while the application screen of the patient support application is displayed (step S72=Yes), the user terminal 100 calls the patient support application without displaying the push notification image (step S76). In this case, the application processing unit 120 starts the process of FIG. 13 without accepting a tap operation on the push notification information.

[0113] FIG. 13 is a first flowchart illustrating an example of processing by the application processing unit of the user terminal. [Step S81] While the application processing unit 120 is running, the information display processing unit 122 of the application processing unit 120 receives an application call from the push notification processing unit 111 of the OS processing unit 110 (step S76 in FIG. 12 ). Then, the process of the next step S82 is executed.

[0114] <Step S82> The information display processing unit 122 obtains the message type (the set value of "type") from the push notification message received from the push notification processing unit 111. [Step S83] The information display processing unit 122 determines whether the message type is a normal message. If the message type is a normal message (if the set value of "type" is 1), the process proceeds to step S84. On the other hand, if the message type is a type other than a normal message (if the set value of "type" is any of 2 to 4), the process proceeds to step S85.

[0115] [Step S84] In this case, it is determined that server access is not required. Therefore, the information display processing unit 122 displays an application screen corresponding to the patient support application on the display device 104, and displays a message display image including the content set in "message" of the push notification message information on the application screen. The entire message body in "message" is displayed in this message display image.

[0116] [Step S85] In this case, it is determined that server access is necessary. Therefore, the information display processing unit 122 requests the application management server 210 to acquire detailed message information corresponding to the received push notification message information.

[0117] <Step S86> The information display processing unit 122 receives the detailed message information. [Step S87] The information display processing unit 122 displays an application screen corresponding to the patient support application on the display device 104, and displays a message display image based on the detailed message information on the application screen.

[0118] 14 is a second flowchart showing an example of processing by the application processing unit of the user terminal, which illustrates processing from the start of the patient support application. [Step S91] In response to a user tapping operation (launch operation) on the icon of the patient support app, or in response to a launch instruction from the push notification processing unit 111 of the OS processing unit 110 (step S77 in FIG. 12), execution of the patient support app is started and the application processing unit 120 is launched.

[0119] [Step S92] The login processing unit 121 of the application processing unit 120 accesses the application management server 210 and executes login processing using the information stored in the user information storage unit 130. If the login processing is successful, the process proceeds to step S93.

[0120] [Step S93] The information display processing unit 122 of the application processing unit 120 determines whether the startup in step S91 was in response to a startup instruction from the OS processing unit 110 after receiving the push notification message information (step S77 in FIG. 12). If the startup was in response to the startup instruction, the process proceeds to step S94. If not (if the startup was in response to a tap operation on an icon), the process in FIG. 14 ends.

[0121] [Step S94] The information display processing unit 122 executes the processes from step S82 onward in FIG. The processing functions of the devices (e.g., the information processing device 10, the servers 21 and 22, the user terminal 100, the application management server 210, the message management server 220, and the push notification server 230) shown in the above-described embodiments can be realized by a computer. In this case, a program describing the processing details of the functions that each device should have is provided, and the above-described processing functions are realized on the computer by executing the program on the computer. The program describing the processing details can be recorded on a computer-readable recording medium. Examples of computer-readable recording media include magnetic storage devices, optical discs, and semiconductor memories. Examples of magnetic storage devices include hard disk drives (HDDs) and magnetic tapes. Examples of optical discs include CDs (Compact Discs), DVDs (Digital Versatile Discs), and Blu-ray Discs (BD, registered trademark).

[0122] When distributing a program, for example, the program is recorded on a portable recording medium such as a DVD or CD and sold. Alternatively, the program can be stored in a storage device of a server computer and transferred from the server computer to other computers via a network.

[0123] A computer that executes a program stores, for example, a program recorded on a portable recording medium or a program transferred from a server computer in its own storage device. The computer then reads the program from its own storage device and executes processing in accordance with the program. Note that the computer can also read the program directly from a portable recording medium and execute processing in accordance with that program. The computer can also execute processing in accordance with the program received each time a program is transferred from a server computer connected via a network. [Explanation of symbols]

[0124] 1. First distribution information 1a Message 1b Identification information 2 Second distribution information 10. Information processing equipment 11 Processing section 12a OS program 12b Display control program 21,22 Server Steps S1a, S1b, S2a to S2d

Claims

1. On the computer, When the computer receives first distribution information that is push-distributed from a first server and includes a message and identification information indicating whether server access is required, the computer determines whether server access is required based on the identification information; If it is determined that server access is unnecessary, the message is displayed on a display device of the computer; If it is determined that server access is necessary, a request is made to a second server to transmit second distribution information corresponding to the first distribution information, and upon receiving the second distribution information from the second server, display information based on the second distribution information on the display device. A display control program that executes the process.

2. and when a selection operation is performed on the message in a state in which the computer receives the first distribution information and displays at least a part of the message on the display device, the determination is made based on the identification information. The display control program according to claim 1.

3. When it is determined that server access is unnecessary based on the determination executed in response to the selection operation on the message, the entire message is displayed on the display device.

3. The display control program according to claim 2.

4. The computer, When the display control program is started, the second server is accessed to execute a login process for a user associated with the display control program; After the login process is successful, it is determined whether the display control program is started in response to the selection operation on the message; When the device is started in response to the selection operation, it determines whether or not server access is required based on the identification information.

3. The display control program according to claim 2, further comprising:

5. and when the computer receives the first distribution information while a display screen corresponding to the display control program is displayed in the foreground on the display device, the computer executes the determination based on the identification information. The display control program according to claim 1.

6. the message includes text information; the display information based on the second distribution information includes link information for a specified network address; The display control program according to claim 1.

7. the message includes text information; the display information based on the second distribution information includes a selection operation unit that accepts a selection operation from a user. The display control program according to claim 1.

8. The computer When first distribution information is received, the first distribution information including a message and identification information indicating whether server access is required, and the message is push-distributed from a first server, determining whether server access is required based on the identification information; If it is determined that server access is unnecessary, the message is displayed on a display device of the computer; If it is determined that server access is necessary, a request is made to a second server to transmit second distribution information corresponding to the first distribution information, and upon receiving the second distribution information from the second server, display information based on the second distribution information on the display device. Display control method.

9. When the first distribution information is received, at least a part of the message is displayed on the display device, and when a selection operation is performed on the message while at least a part of the message is displayed, the determination is made based on the identification information. The display control method according to claim 8.

10. When it is determined that server access is unnecessary based on the determination executed in response to the selection operation on the message, the entire message is displayed on the display device. The display control method according to claim 9.

11. If a program for executing the determination based on the identification information is not running when the selection operation on the message is performed, the program is started, the second server is accessed, a login process for a user associated with the program is executed, and then the determination is executed. The display control method according to claim 9.

12. and when the first distribution information is received while a display screen corresponding to a program for executing the determination based on the identification information is displayed in the foreground on the display device, the detection of the selection operation on the message is skipped and the determination is executed. The display control method according to claim 9.

13. An information processing device having a display device and a processing unit, The processing unit When first distribution information is received, the first distribution information including a message and identification information indicating whether server access is required, and the message is push-distributed from a first server, determining whether server access is required based on the identification information; If it is determined that server access is not necessary, the message is displayed on the display device; If it is determined that server access is necessary, a request is made to a second server to transmit second distribution information corresponding to the first distribution information, and upon receiving the second distribution information from the second server, display information based on the second distribution information on the display device. Information processing device.

Images