JP5832807B2 - program - Google Patents

program Download PDF

Info

Publication number
JP5832807B2
JP5832807B2 JP2011163926A JP2011163926A JP5832807B2 JP 5832807 B2 JP5832807 B2 JP 5832807B2 JP 2011163926 A JP2011163926 A JP 2011163926A JP 2011163926 A JP2011163926 A JP 2011163926A JP 5832807 B2 JP5832807 B2 JP 5832807B2
Authority
JP
Japan
Prior art keywords
application
user
program
server
mobile terminal
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
JP2011163926A
Other languages
Japanese (ja)
Other versions
JP2013030865A (en
Inventor
大智 野田
大智 野田
Original Assignee
イクス株式会社
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by イクス株式会社 filed Critical イクス株式会社
Priority to JP2011163926A priority Critical patent/JP5832807B2/en
Publication of JP2013030865A publication Critical patent/JP2013030865A/en
Application granted granted Critical
Publication of JP5832807B2 publication Critical patent/JP5832807B2/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Description

  The present invention relates to a program, and more particularly, to a program that provides information so that a user can be surely and immediately recognized.

  In recent years, a highly functional mobile terminal called a smartphone, which is a fusion of a mobile phone and a mobile information terminal, has attracted attention. In a smartphone, an application program (hereinafter simply referred to as an application) can be easily installed from a market or the like and executed on a terminal. There are various types of apps, such as games, music and video viewing, dictionaries, maps, studies, etc. Using a desired app is one of the purposes of using a smartphone. It has become.

  Conventionally, the method of contacting the application creator, for example, the version upgrade information of the application from the application producer, is notified by e-mail using the e-mail address registered by the user on the application producer side. It was common (see, for example, Patent Document 1).

  As a conventional technique for distributing e-mail, for example, a use history such as an e-mail address of a user of a predetermined object is accumulated, and an e-mail address of a transmission partner related to the object is unknown. There is a method of searching for a user that matches a predetermined condition based on the accumulated use history, acquiring an e-mail address of a transmission partner, and transmitting the e-mail (for example, see Patent Document 2). In general, an e-mail is an e-mail addressed to a user held by a server in response to a request from a user terminal that is a client, while suppressing power consumption of the client. A notification method that improves the real-time property of notification has also been proposed (see, for example, Patent Document 3).

JP 2004-342098 A (particularly paragraph 0002) JP 2011-108094 A JP 2010-141851 A

  However, provision of information by e-mail does not transmit the provided information to the user until the user starts an e-mail application (mailer) on the terminal and opens (views) the received message. Therefore, for example, as shown in FIG. 1, a message that is not an email from a friend is not opened, and the transmitted message may not be read. In addition, there is a case where the provided message becomes meaningless, for example, the user has time to open the received message and the effective time limit has passed. In other words, the conventional provision of information by e-mail lacks certainty and immediacy of the information provided.

  This invention is made | formed in view of such a condition, and provides information so that a user may be recognized reliably and immediately.

A program according to an aspect of the present invention is a program that causes a computer of a mobile terminal to execute a predetermined process, and starts up in a resident mode and communicates with a first server when installed in the mobile terminal. The program identification information for identifying the program is acquired from one server, and the acquired program identification information is transmitted to the second server together with the user identification information for identifying the user of the portable terminal, and the program is started by the user. in the execution state after being instructed to transmit the operation history data of the user with respect to the program to the second server, at a predetermined timing in a state where the program is not started instructed by a user of the portable terminal, the first Two servers specify the program identification information and send instructions to the first server It sent from the first server by Rukoto, on the basis of the operation history data receives a message for the user identified by the second server, based on the message received, the dialog display the status bar display Alternatively, a process for executing any one of the programs is executed.

  According to one aspect of the present invention, information can be provided so as to be recognized by a user reliably and immediately.

It is a figure explaining the conventional problem. It is a figure which shows the structural example of one Embodiment of the communication system to which this invention is applied. It is a figure which shows the flow of the whole process in the case of performing a push notification. It is a figure which shows the example of an application information table. It is a figure which shows the example of an action history management table. It is a figure which shows the example of a display of each of the three actions which can be selected as a push notification. It is a detailed flowchart of a push notification. It is a block diagram which shows the functional structural example of an application. It is a block diagram which shows the hardware structural example of a portable terminal.

[Configuration example of communication system to which the present invention is applied]
FIG. 2 shows a configuration example of an embodiment of a communication system to which the present invention is applied.

  The communication system of FIG. 2 can transmit a message to a mobile terminal 1 of a user who has installed a predetermined application program (hereinafter simply referred to as an application) even when the installed application is not activated. System.

  The communication system shown in FIG. 2 includes a mobile terminal 1, a PC (personal computer) 2, an application providing server 3, a management server 4, and a message (MSG) service server 5, such as a mobile telephone communication network and the Internet. The network 6 is connected as necessary, and predetermined information is exchanged between them.

  The mobile terminal 1 is a high-function terminal (mobile phone) that is generally called a smartphone and is a fusion of a mobile phone and a mobile information terminal, and is used by a user who is an owner. One or more applications 10 and applications 11 are downloaded from the application providing server 3 and installed in the mobile terminal 1.

  Here, both the application 10 and the application 11 are application programs executed on the mobile terminal 1, but the application 10 is an application that does not support transmission / reception of messages in a state where the application 10 is not activated by a user's activation operation. On the other hand, the application 11 is an application that can send and receive messages even when it is not activated by a user activation operation. Since the application 10 is the same as a normal application, the following description will be given focusing on the application 11.

  The PC 2 is a computer used by the application creator of the application 11. The application 11 produced (generated) by the application producer of the application 11 is transmitted from the PC 2 to the application providing server 3 via the network 6 and is held by the application providing server 3.

  Further, the application creator of the application 11 can access the management server 4 from the PC 2 and request the management server 4 to transmit a message to the user who installed the application 11. The content of the message to the user who installed the application 11 includes, for example, version upgrade information of the application 11.

  The application providing server 3 is a server that is accessed when a user accesses the market from the mobile terminal 1 and instructs to install the application 11, and holds program data of the application 11. When the user instructs installation of the application 11 in the market accessed by the mobile terminal 1, the program data of the instructed application 11 is installed from the application providing server 3 to the user's mobile terminal 1.

  The management server 4 manages the application 11 installed on the mobile terminal 1. That is, when the application 11 is installed in the mobile terminal 1, the management server 4 acquires the application information of the installed application 11 from the mobile terminal 1 and stores it. Specifically, the management server 4 associates an application ID for identifying the application 11, version information indicating the version of the application 11, date information indicating the date on which the application 11 is installed, and the like with a user ID for identifying the user. And stored as application information.

  The management server 4 can also analyze the usage status of the application 11 installed in the mobile terminal 1. The usage status of the application 11 is, for example, whether or not the installed application 11 has been activated, what screen has been viewed in the activated application 11, and the like. It can be said that the usage status of the application 11 is a user's action history with respect to the application 11. The management server 4 analyzes the action history of the user with respect to the application 11 (the usage status of the application 11) and stores it as action history data. Such an analysis function can also be said to be an access analysis function of the application 11.

  The application information of the application 11 and the user action history data stored in the management server 4 are used for transmission of a message from the application producer of the application 11 to the user (user) of the application 11. That is, the management server 4 accepts a message transmission request from the application producer (PC2) and matches the conditions specified by the application producer based on the user action history data and the application information held therein. The message service server 5 is requested to search for a user and send a message to the notification target user obtained as a result of the search.

  The message service server 5 performs push-type message transmission to the mobile terminal 1 of the user who installed the application 11. Here, the push-type message transmission refers to transmitting a message spontaneously at a predetermined timing without requiring a special request from the mobile terminal 1 as a client, and is also referred to as a push notification below.

  Specifically, the message service server 5 has a terminal ID unique to the mobile terminal 1 and a registration ID issued for each application 11 for each mobile terminal 1, and what application 11 is in which mobile terminal 1. You know if it is installed. The message service server 5 receives a message transmission request from the management server 4. The message transmission request includes a registration ID and the content of the message to be transmitted. The message service server 5 identifies the mobile terminal 1 to be transmitted based on the registration ID, and transmits the content of the message requested from the management server 4 to the application 11 corresponding to the registration ID of the identified mobile terminal 1. To do.

  In the present embodiment, the functions realized by the application providing server 3, the management server 4, and the message service server 5 may be integrated into one or two servers and realized by one or two servers. .

[Overview of the entire push notification process]
FIG. 3 is a diagram illustrating a flow of the entire process when a push notification is made to the mobile terminal 1 of the user who has installed the predetermined application 11.

  The processing flow in the case of performing the push notification is roughly executed by four steps. The following first to fourth steps correspond to the displays (1) to (4) in FIG.

  The first step is a step in which the message service server 5 and the management server 4 acquire information for push notification.

  When the application 11 is installed in the mobile terminal 1, the application 11 communicates with the message service server 5. The message service server 5 communicates with the application 11 at the timing when the application 11 is installed on the mobile terminal 1, recognizes that the application 11 is installed on the mobile terminal 1, and also installs the application 11 installed on the mobile terminal 1. Is issued uniquely, and is transmitted to the portable terminal 1.

  After acquiring the registration ID from the message service server 5, the application 11 of the mobile terminal 1 communicates with the management server 4 and transmits the application information of itself (the application 11). The management server 4 stores the application information acquired from the application 11 of the mobile terminal 1 in the application information table.

[Example of application information table]
FIG. 4 shows an example of the application information table in the management server 4.

  In the application information table, the user ID for identifying the user, the registration ID given by the message service server 5 to the application 11 of the mobile terminal 1, the application ID indicating the application 11, the version information of the application 11, and the application 11 Date information indicating the date of installation on the mobile terminal 1 is stored in association with each other. As the user ID for identifying the user, a terminal ID unique to the portable terminal 1 or identification information unique to the portable terminal 1 assigned by the management server 4 operator or the communication service provider can be adopted.

  In the application information table, the user ID, version information, and date information are used to narrow down the target users of push notifications based on the installation date and version, etc. And only have an app ID. That is, the user ID, version information, and date information can be omitted.

  The first step described above is executed in the background when the application 11 is installed in the mobile terminal 1, even if the application 11 is not activated by the user.

  The second step is a step in which the management server 4 acquires a user action history for the application 11.

  When the user activates and executes the application 11 and performs a predetermined action, the management server 4 obtains an action ID indicating the action performed by the user from the application 11 of the mobile terminal 1 together with the user ID and the application ID. get. Here, the action ID, the user ID, and the application ID transmitted from the application 11 correspond to the behavior history data described above. The action history data transmitted from the application 11 of the mobile terminal 1 is stored in the action history management table in the management server 4.

  What kind of action the user performs on the application 11, in other words, what kind of action occurs in the application 11 when the action history data is transmitted to the management server 4 is determined in the application 11 Pre-programmed with

[Example of action history management table]
FIG. 5 shows an example of an action history management table in the management server 4.

  In the action history management table, a user ID, an application ID, an action ID, and an action occurrence date and time are stored in association with each notified action. In addition, when only the action ID can identify which application 11 is the action, the application ID can be omitted.

  The third step is a step in which the management server 4 receives a push notification request from the application creator's PC 2.

  As an action (display mode) of the push notification, any one of (a) dialog display, (b) status bar display, and (c) automatic activation (forced activation) of the application 11 can be designated.

[Display example of push notification]
FIG. 6 shows a display example of each of three actions that can be designated as push notifications. In FIG. 6, the application name of the application 11 is “AB application”.

  FIG. 6A shows a display example when (a) dialog display is designated as the action of push notification.

  In the dialog 21 shown in FIG. 6A, “Notification from AB application” is displayed as a title. Then, as a message to the user who has installed the application 11 in the mobile terminal 1 but has not yet been activated by the user, “If you use the AB application, you can purchase a product with a 50% to 90% discount. "Would you like to use it?" Is displayed. This dialog 21 can be displayed as long as the application 11 is not activated (once), as long as it is installed in the mobile terminal 1. The dialog 21 is created by resizing one screen of the application 11 to a predetermined screen size.

  FIG. 6B shows a display example when (b) status bar display is designated as the push notification action.

  On the display of the mobile terminal 1, a status bar 22 a that always displays the status of the mobile terminal 1 (for example, the reception state or charging state of radio waves) and informs the user of missed calls or incoming mails is always displayed. The management server 4 can display a specified message on the status bar 22a.

  In addition, when a dragging or flicking operation in the downward direction of the screen by the user is detected with respect to the status bar 22a, the mobile terminal 1 can display the detailed screen 22b of the status bar 22a. FIG. 6B shows the details screen 22b of the status bar 22a with the title “AB app” indicating that the message is from the “AB app” and the “latest version released” that informs that the latest version has been released. An example of displaying the contents of "."

  FIG. 6C shows a display example when (c) automatic activation of the application 11 is designated as the push notification action.

  On the display of the mobile terminal 1 in FIG. 6C, an “AB application” activation screen 23 is displayed.

  The fourth step in FIG. 3 is a step in which the management server 4 executes the push notification based on the request content of the push notification from the app producer in the third step described above.

  Specifically, the management server 4 also searches the application information table of FIG. 4 and the action history management table of FIG. 5 as necessary based on the request content of the push notification, and searches for the corresponding user.

  Then, the management server 4 transmits the registration ID of the user who is the subject of the push notification and the message content of the push notification to the message service server 5. The message service server 5 specifies the mobile terminal 1 and the application 11 to be transmitted based on the registration ID, and transmits the message content to the application 11 of the specified mobile terminal 1.

[Detailed processing flow of push notification]
Next, with reference to a flowchart (sequence diagram) in FIG. 7, details of processing of each device of the communication system in FIG. 2 will be described.

  First, in step S1, the mobile terminal 1 installs the application 11 from the application providing server 3 corresponding to the market based on the user's operation.

  In step S2, the application 11 installed in the mobile terminal 1 is automatically activated in the resident mode when the installation is completed. The application 11 has an execution mode based on a resident mode that operates in the background, in addition to a main activation mode that is an execution mode when an activation instruction is given by the user. The application 11 is executed in the resident mode unless it is deleted from the mobile terminal 1 except when the mobile terminal 1 is powered on and is being executed in the main activation mode.

  In step S3, the resident mode application 11 transmits a registration ID request to the message service server 5 together with a user ID that is information for identifying the mobile terminal 1 (the user). The message service server 5 Receive it.

  In step S4, the message service server 5 issues a registration ID to be assigned to the application 11 of the mobile terminal 1 in response to the request for the registration ID. Then, the message service server 5 transmits the issued registration ID to the application 11 of the mobile terminal 1, and the resident mode application 11 receives it.

  In step S5, the resident mode application 11 transmits the received registration ID to the management server 4 together with the user ID, the application ID indicating the application 11, and the version information of the application 11, and the management server 4 receives the received registration ID. To do.

  In step S6, the management server 4 stores the received registration ID, user ID, application ID, and version information in the application information table (FIG. 4) as application information together with the date information that is the received date information. To do. Note that the date information may also be transmitted by the application 11 of the mobile terminal 1.

  The processes from steps S1 to S6 described above correspond to the first step described in FIG.

  Next, when an operation for starting the application 11 is performed by the user in the mobile terminal 1, the application 11 of the mobile terminal 1 is started in the main start mode in step S7.

  In step S8, the application 11 in the main activation mode determines whether or not a predetermined action to be notified to the management server 4 has occurred, and waits until it is determined that a predetermined action has occurred.

  If it is determined in step S8 that a predetermined action to be notified to the management server 4 has occurred, the process proceeds to step S9, and the application 11 in the main activation mode assigns an action ID indicating the generated action to the user. The ID and the application ID are transmitted to the management server 4, and the management server 4 receives them.

  In step S10, the management server 4 stores the received action ID, user ID, and application ID as action history data in the action history management table together with the received date / time information as the action occurrence date / time.

  A series of processes of steps S8 to S10 are repeatedly executed every time the application 11 is executed by full activation and a predetermined action to be notified to the management server 4 occurs. Then, when the user performs an operation to end the application 11, in step S11, the application 11 ends the activation mode and returns to the resident mode.

  The processes from steps S7 to S11 described above correspond to the second step described with reference to FIG.

  In step S12, the application creator's PC 2 of the application 11 logs in to the management server 4 based on the operation of the application producer, and requests page data of a setting screen (not shown) for setting a push notification.

  In step S <b> 13, the management server 4 transmits the page data of the push notification setting screen to the PC 2 based on the request for page data of the push notification setting screen from the PC 2, and the PC 2 receives it.

  In step S14, the PC 2 displays a push notification setting screen on the display based on the received page data, and accepts input to each item in the setting screen by the application creator.

  Here, items that can be input on the push notification setting screen will be described.

  On the push notification setting screen, first, the application 11 that performs the push notification can be designated. Hereinafter, the designated application 11 is referred to as designated application 11 below.

  On the setting screen, four items of “1. Action selection”, “2. Time setting”, “3. Target user”, and “4.

  In the item “1. Action selection”, an action of push notification can be designated. That is, in the item “1. Action selection”, one of the actions (display form) of “dialog display”, “status bar display”, and “application automatic activation” described with reference to FIG. 6 is designated.

  In the item “2. Time setting”, the time for performing the push notification is designated. Specifically, it is possible to specify either “immediately” that performs push notification immediately after input of the setting screen or “date and time designation” that performs push notification at a specified date and time. .

  In the item “3. target user”, it is possible to specify, in particular, to which user the push notification is to be made among the users who have the designated application 11 installed in the mobile terminal 1.

  Specifically, all users who have the specified application 11 installed, users who have or have not started the specified application 11, users who use the specified application 11 of a predetermined version, etc. Can be specified. Note that the user can be directly designated by a user ID (terminal ID) or the like.

  In the item “4. Notification content”, the content of a message displayed in the push notification can be input. Note that the item “4. Notification content” is omitted when “Automatic application activation” is specified in the item “1. Action selection”.

  When the input (designation) of the push notification setting conditions on the setting screen as described above is completed, in step S15, the PC 2 transmits the input push notification setting conditions to the management server 4, and the management server 4 Receive.

  The processes from steps S12 to S15 described above correspond to the third step described with reference to FIG.

  In step S16, the management server 4 determines whether or not the time specified by the push notification setting condition received in step S15 has come, and waits until the specified time is reached. Specifically, when “immediate” is designated on the setting screen described above, it is determined that the designated time has come in the process of step S16 immediately after the process of step S15. On the other hand, if “date and time designation” is designated on the setting screen, it is determined that the designated time has been reached in the process of step S16 when the designated date and time are reached.

  If it is determined in step S16 that the designated time has come, the process proceeds to step S17, and the management server 4 determines whether the action history management table and the application information table are based on various conditions designated on the setting screen. Search the data and identify the user to be notified. For example, based on the application information table, a user who is in the portable terminal 1 in which the designated application 11 is installed and who meets a condition such as the version of the designated application 11 being older than a predetermined version is specified. Alternatively, when a predetermined action history of the user is a condition, the action history management table is referred to, and, for example, a user who has never been activated is specified as a user to be notified.

  In step S18, the management server 4 determines the content of the notification based on various conditions specified on the setting screen. That is, the management server 4 determines an action of dialog display, status bar display, or application automatic activation based on the item “1. Action selection” on the setting screen. Further, the management server 4 determines a message to be displayed based on the item “4. Notification content” on the setting screen.

  In step S19, the management server 4 transmits to the message service server 5 the registration ID of the user specified in step S17 and the notification content determined in step S18, and the message service server 5 receives it.

  In step S20, the message service server 5 transmits the notification content received from the management server 4 to the designated application 11 of the portable terminal 1 based on the received registration ID, and the resident mode application 11 of the portable terminal 1 is transmitted. Receive it.

  In step S21, the resident mode application 11 analyzes the received notification content and executes an action specified by the notification content.

  Specifically, when the action specified in the notification content is a dialog display, the resident mode application 11 acquires the message input in the item “4. Notification content” on the setting screen, and imitates the dialog. Displayed on the screen.

  When the action specified in the notification content is the status bar display, the resident mode application 11 causes the status bar 22a to display the message input in the item “4. Notification content” on the setting screen.

  When the action specified in the notification content is automatic application activation, the application 11 in the resident mode executes in the main activation mode.

  The processes from steps S16 to S21 described above correspond to the fourth step described with reference to FIG.

  Through the processing described above, in the portable terminal 1 in which the designated application 11 is installed, even if the designated application 11 has not been activated after the installation, push notification can be performed.

[Functional configuration block diagram of application 11]
FIG. 8 is a block diagram illustrating a functional configuration example of the application 11 related to the push notification function described above.

  The application 11 includes a resident mode execution unit 31 and a main activation mode execution unit 32. In the resident mode, only the resident mode execution unit 31 is executed, and in the main activation mode, both the resident mode execution unit 31 and the main activation mode execution unit 32 are executed.

  The resident mode execution unit 31 includes a message transmission / reception control unit 41, a registration ID control unit 42, a notification content analysis unit 43, and a notification content display control unit 44.

  The message transmission / reception control unit 41 controls transmission / reception of messages with the management server 4 and the message service server 5 in the resident mode.

  The registration ID control unit 42 requests and acquires the registration ID from the message service server 5 in the first step described with reference to FIG. 3, and the acquired registration ID together with the user ID and application ID is managed by the management server 4. Control the process to notify.

  The notification content analysis unit 43 performs a process of analyzing the notification content transmitted from the management server 4 via the message service server 5 in the fourth step described with reference to FIG.

  The notification content display control unit 44 controls dialog display, message display, and main activation based on the analysis result by the notification content analysis unit 43.

  The activation mode execution unit 32 includes an action history control unit 51 and a message transmission / reception control unit 52.

  The action history control unit 51 determines whether or not a predetermined action that is determined in advance during programming has occurred in the activation mode, and when the predetermined action occurs, action history data (user ID, application ID) , And action ID).

  The message transmission / reception control unit 52 performs control to transmit the action history data generated by the action history control unit 51 to the management server 4. The message transmission / reception control unit 41 and the message transmission / reception control unit 52 may be the same as a module.

[Configuration block diagram of portable terminal 1]
FIG. 9 is a block diagram illustrating a hardware configuration example of the mobile terminal 1.

  In FIG. 9, a CPU (Central Processing Unit) 71 is an arithmetic processing unit that executes various processes. The CPU 71 also executes the application 10, the application 11, and the like. The CPU 71 is connected to a ROM (Read Only Memory) 72, a RAM (Random Access Memory) 73, and an NVRAM (Non Volatile RAM) 74 via a bus 75. An input / output interface 76 is also connected to the bus 75, and a storage unit 77 and a drive 78 are connected to the input / output interface 76.

  The ROM 72 stores basic programs such as an OS (Operating System) and data in advance. The RAM 73 and the NVRAM 74 are loaded with application programs and data stored in the ROM 72 and the storage unit 77. The RAM 73 and NVRAM 74 also appropriately store data necessary for the CPU 71 to execute various processes. The storage unit 77 is configured by a flash memory or the like, and stores at least the application 11.

  The drive 78 reads data from a removable medium 79 such as a semiconductor memory that is mounted as necessary, and supplies the data to the CPU 71 via the input / output interface 76 or the like, and the data supplied from the CPU 71 to the removable medium 79. Write. Data to be read and written may include data of an application program to be installed.

  An input unit 80, a voice input / output unit 71, a touch screen 82, a wireless communication unit 83, a telephone line network communication unit 84, and a photographing unit 85 are connected to the input / output interface 76.

  The input unit 80 includes a keyboard, operation buttons, and the like. The input unit 80 receives input by a user operation and supplies the input to the CPU 71 and the like. The voice input / output unit 81 includes a speaker, a microphone, and the like, and inputs and outputs voice for a call.

  The touch screen 82 includes a display unit 82A and a position detection unit 82B, and can perform various displays and operation inputs by bringing a finger or the like in close proximity or in contact (touch).

  The display unit 82A is configured by a device (display device) such as a liquid crystal panel, and displays an image according to data supplied via the input / output interface 86.

  The position detection unit 82B is configured by a device having a function of receiving (detecting) an external input (proximity / contact) such as an electrostatic touch panel.

  In the touch screen 82, the display unit 82A and the position detection unit 82B as described above are integrated, and an image is displayed on the display unit 82A, and the image displayed on the display unit 82A is displayed on the position detection unit 82B. External operation inputs (touch and proximity) can be accepted.

  The position signal output from the position detection unit 82B is supplied to the CPU 71 via the input / output interface 86. The CPU 71 recognizes what operation input has been made based on the position signal from the position detection unit 82B. Various processes are performed according to the operation input.

  The wireless communication unit 83 performs wireless communication using a WiFi method or the like. The telephone line network communication unit 84 performs voice communication or packet communication with other devices via the mobile telephone communication network. The imaging unit 85 includes an imaging element such as a CCD (Charge Coupled Device) or a CMOS (Complementary Mental Oxide Semiconductor) sensor. The photographing unit 85 photographs a subject and supplies image data of the photographed subject to the CPU 71 and the like via the input / output interface 76.

  In the mobile terminal 1 configured as described above, a message is transmitted from the server to the computer (CPU 71) at a predetermined timing when the application 11 is not instructed to be activated by the user of the mobile terminal 1. (Push notification) is received, and based on the received message, a process for displaying a dialog notifying the predetermined content is executed. Thereby, information (message) can be provided so that the user can be surely and immediately recognized.

  The mobile terminal 1 includes a non-contact communication unit that performs non-contact communication using electromagnetic induction at a proximity distance of about several centimeters, a wireless communication unit that uses a Bluetooth (registered trademark) system, and an infrared that performs infrared communication. You may make it further provide other structures, such as a communication part.

  In the above-described embodiment, the mobile terminal 1 is described as a smartphone. However, the mobile terminal 1 is not limited to a smartphone, and may be a tablet terminal such as a PND (Portable Navigation Device) or an electronic book reader. Any portable information processing terminal that can be downloaded and executed may be used.

  Although illustration of the hardware configuration of each of the application providing server 3, the management server 4, and the message service server 5 is omitted, each of these servers has a storage unit such as a CPU, a ROM, a RAM, and a hard disk. Each server can execute various processes including the above-described series of processes in accordance with a program loaded in the RAM from a program stored in the storage unit or the ROM. Each server also includes a communication unit that performs data communication by connecting to a LAN or the Internet, an input unit including a keyboard and a mouse, and an output unit including a speaker and a display.

  In the above-described embodiment, an example has been described in which the application creator transmits a predetermined message to the user who installed the application 11 using the push notification. However, the push notification user is not limited to the app creator as described above.

  For example, the operator of the management server 4 that performs access analysis of the application 11 can set the push notification execution in response to a request from the application producer or the like. Alternatively, the push notification execution program of the management server 4 may be incorporated so that the push notification is automatically executed periodically or irregularly, for example, “send on the first Sunday of the month”. Good. In such a case, the application creator's PC 2 is not required.

  Also, for example, when friends have installed the application 11 with each other and information such as the other party's user ID is known, the friend A accesses the management server 4 and uses the push notification. Then, it can be used as a communication tool such as sending a predetermined message to friend B. In this case, the application 11 itself can be regarded as a communication application having certainty and immediacy.

  In this specification, the steps described in the flowchart are not necessarily processed in chronological order, but are performed in parallel or when they are called in chronological order according to the described order. It may be executed at a necessary timing.

  In the present specification, the term “system” represents the entire apparatus constituted by a plurality of apparatuses.

  The embodiments of the present invention are not limited to the above-described embodiments, and various modifications can be made without departing from the scope of the present invention.

DESCRIPTION OF SYMBOLS 1 Mobile terminal 3 Application provision server 4 Management server 5 Message (MSG) service server 11 Application program (application)
31 Resident Mode Execution Unit 32 This Activation Mode Execution Unit 41 Message Transmission / Reception Control Unit 42 Registration ID Control Unit 43 Notification Content Analysis Unit 44 Notification Content Display Control Unit 51 Action History Control Unit 52 Message Transmission / Reception Control Unit

Claims (3)

  1. A program that causes a computer of a mobile terminal to execute predetermined processing,
    At the timing when installed in the mobile terminal, it starts in the resident mode and communicates with the first server, and acquires the program identification information for identifying the program from the first server,
    The acquired program identification information is transmitted to the second server together with user identification information for identifying the user of the portable terminal,
    In the execution state after the program is instructed to be started by the user, the operation history data of the user for the program is transmitted to the second server,
    Transmitted from the first server by the second server specifying the program identification information and instructing transmission to the first server at a predetermined timing when the program is not instructed to be started by the user of the portable terminal And receiving a message for the user specified by the second server based on the operation history data ,
    A program for executing processing for executing any one of dialog display, status bar display, and activation of the program based on the received message.
  2. The user specified by the second server is a user who has never started after installing the program,
    The program according to claim 1 , wherein a display recommending the use of the program is performed based on the received message .
  3. Also sends version information of the program to the second server,
    The program according to claim 1 or 2 , wherein a display notifying the release of the latest version of the program is performed based on the received message .
JP2011163926A 2011-07-27 2011-07-27 program Active JP5832807B2 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
JP2011163926A JP5832807B2 (en) 2011-07-27 2011-07-27 program

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
JP2011163926A JP5832807B2 (en) 2011-07-27 2011-07-27 program

Publications (2)

Publication Number Publication Date
JP2013030865A JP2013030865A (en) 2013-02-07
JP5832807B2 true JP5832807B2 (en) 2015-12-16

Family

ID=47787518

Family Applications (1)

Application Number Title Priority Date Filing Date
JP2011163926A Active JP5832807B2 (en) 2011-07-27 2011-07-27 program

Country Status (1)

Country Link
JP (1) JP5832807B2 (en)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103500079A (en) * 2013-09-17 2014-01-08 小米科技有限责任公司 Notification message display method and device and electronic equipment
CN107408050A (en) * 2015-04-14 2017-11-28 索尼公司 Message processing device, information processing method, computer program and server apparatus

Family Cites Families (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2001202310A (en) * 2000-01-20 2001-07-27 Square Co Ltd Information providing method, recording medium with recorded program for providing the same method and information providing system
JP2003303151A (en) * 2002-04-12 2003-10-24 Nec Corp Push-type information delivery system, push-type information delivering method, and program for push- type information delivery
GB0426736D0 (en) * 2004-12-06 2005-01-12 Omnifone Ltd MyFone
JP2006195843A (en) * 2005-01-14 2006-07-27 Takayama Yasuyuki Content delivery system
JP2007004316A (en) * 2005-06-22 2007-01-11 Nec Corp Program distribution system, program distribution server and program used for the same
JP2007233808A (en) * 2006-03-02 2007-09-13 Nec Corp Information exchange system, messenger management server, information exchange method, information exchange program and recording medium
JP5024036B2 (en) * 2007-12-27 2012-09-12 沖電気工業株式会社 Program distribution server, distribution system, distribution method, and distribution target program
JP2009169524A (en) * 2008-01-11 2009-07-30 Panasonic Electric Works Co Ltd Network system for home appliance
JP5241473B2 (en) * 2008-12-22 2013-07-17 株式会社オービックビジネスコンサルタント Information processing system, relay server device, terminal device, relay server processing method, terminal processing method, and program

Also Published As

Publication number Publication date
JP2013030865A (en) 2013-02-07

Similar Documents

Publication Publication Date Title
JP6622863B2 (en) User interface for mobile device application management
US20180367660A1 (en) Operation method and system of mobile terminal
US10289287B2 (en) Communications devices and methods for single-mode and automatic media capture
US20190028418A1 (en) Apparatus and method for providing information
JP6191885B2 (en) Power efficient application notification system
US9449107B2 (en) Method and system for gesture based searching
US10506090B2 (en) Operation method and system of mobile terminal
WO2017206916A1 (en) Method for determining kernel running configuration in processor and related product
JP5865936B2 (en) Additional information providing apparatus and method using caller telephone number
US9459759B2 (en) Method for displaying contents use history and electronic device thereof
KR20160030462A (en) Method for adding application badge and device thereof
EP3041205A2 (en) Method, device and system for displaying content of short message, method and device for determining display of short message
KR101457632B1 (en) Mobile electronic device having program notification function and program notification method thereof
US10013140B2 (en) Methods and apparatus for providing updated content in a user interface
US20200064933A1 (en) Mobile device comprising stylus pen and operation method therefor
JP5449390B2 (en) Separation of received information on locked devices
JP6096992B2 (en) Method, apparatus, program and storage medium for saving storage space
CN102077554B (en) Method, device and user interface for capturing and sharing content
US8117136B2 (en) Relationship management on a mobile computing device
RU2635237C2 (en) Method and device for deleting intelligent script
US20150007157A1 (en) Method and apparatus for updating application
EP2763094A1 (en) Method of displaying user interface on device, and device
KR20160021637A (en) Method for processing contents and electronics device thereof
US9423930B2 (en) Mobile device, network system, and control method for the same
TWI394410B (en) Method and system for filtering incoming messages to a mobile device

Legal Events

Date Code Title Description
A621 Written request for application examination

Free format text: JAPANESE INTERMEDIATE CODE: A621

Effective date: 20140724

A977 Report on retrieval

Free format text: JAPANESE INTERMEDIATE CODE: A971007

Effective date: 20150305

A131 Notification of reasons for refusal

Free format text: JAPANESE INTERMEDIATE CODE: A131

Effective date: 20150421

A521 Written amendment

Free format text: JAPANESE INTERMEDIATE CODE: A523

Effective date: 20150622

TRDD Decision of grant or rejection written
A01 Written decision to grant a patent or to grant a registration (utility model)

Free format text: JAPANESE INTERMEDIATE CODE: A01

Effective date: 20150929

A61 First payment of annual fees (during grant procedure)

Free format text: JAPANESE INTERMEDIATE CODE: A61

Effective date: 20151028

R150 Certificate of patent or registration of utility model

Ref document number: 5832807

Country of ref document: JP

Free format text: JAPANESE INTERMEDIATE CODE: R150

R250 Receipt of annual fees

Free format text: JAPANESE INTERMEDIATE CODE: R250