BMT M603, Руководство пользователя

Страница: 7 / 8

CONFIDENTIAL
Copyright(C) 2012- Bridge Motion Tomorrow Co., Ltd. All rights reserved.
4.1.3 Pi-messanger Sequence & Setting Data
The following sessions summaries the format of messages between the BMT back end server and
the M603 devices. Each of the messages is in JSON format. When sending the message with the Java
client library. To send a message, the message source application need to specify the destination,
message type, and message content. Destination is specified by a string. It could be a server name, or
a MAC address of an Android device. Message type is an integer that identifies the meaning of
message content. The message content (if any) is a UTF8 encoded String
Destination: for server, the M603 destination is specified by MAC address. The Pi-Messenger server
will know where the message will be delivered by the MAC address.)
Message Type that let recipient know the type content without parsing it.)
The message content is a JSON string in UTF-8 encoding.)
Relevant part is item number 16, 17)
4.1.4 Message Summary
Message Direction Implementation Style at M603
App List Request 1
M603 → Server Context.startService
App List Update 2
Server →M603 Unconditional broadcast
Theme Update 3
Server →M603 Targeted broadcast
App Log Report 4
M603 → Server Context.startService
Movie Log Report 5
M603→ Server Context.startService
Payment Result 6
M603 → Server Context.startService
Payment Query Request 7
M603 → Server Context.startService
Payment Query Response 8
Server →M603 Context.startService with PendingIntent
Price Update Request 9
M603 → Server Context.startService
Price Update 10 Server →M603 Context.startService with PendingIntent
App Installation 11 Server →M603 Unconditional broadcast
App Uninstallation 12 Server →M603 Unconditional broadcast
App Termination 13 Server →M603 Unconditional broadcast
Apps Status request 14 Server →M603 Unconditional broadcast
Apps Status report 15 M603 → Server Context.startService