A database is required to use the X-PUSH reliability and notification services.

Message Storage Process

Reliability Message

1. A message is received from a provider.

2. The received message is stored in the T_MESSAGE table.

3. The received TOPIC information (TOPIC_TYPE, TOPIC_ID) and matching user are located in the T_TOPIC table.

4. The located user information and message are stored in the T_USER_MESSAGE table.

Notification Message

1. A message is received from a provider.

2. The received message is stored in the T_MESSAGE table.

3. The received TOPIC information (TOPIC_TYPE, TOPIC_ID) and matching user are located in the T_TOPIC table.

4. The located user information and message are stored in the T_USER_MESSAGE table.

5. The user's online/offline status is verified.

6. In the case of online, the notification is not transmitted. In the case of offline, the USER_ID information is obtained from the T_MOBILE table, stored in the T_NOTIFICATION table, and the notification message is transmitted to the device.

Table Description

Five tables are required.

• T_TOPIC

• T_MESSAGE

• T_USER_MESSAGE

• T_MOBILE

• T_NOTIFICATION

T_TOPIC

This table contains user information.

When adding users, one of the methods below is used.

1. An administrator manually adds users to the T_TOPIC table.

   Direct input via query.

insert
   into T_TOPIC
 (PROJECT_ID,USER_ID, TOPIC_TYPE, TOPIC_ID, REGISTER_DATE, MODIFIED_DATE, ACTIVE)
   values
 ('PRO#1','test@test.com, 'NOTI', '1001', '20150102012345', '20150102012345', 'Y')

2. User direct input.

   Users can be added directly via commands in Nexacro Studio.

T_MESSAGE

This table stores reliability messages sent by a provider.

T_USER_MESSAGE

This table stores reliability messages per user.

When a message is received from a provider, the T_TOPIC and T_MESSASGE are combined to create a T_USER_MESSAGE.

T_MOBILE

This table contains mobile user information.

T_NOTIFICATION

This table stores notification messages per user.