Orange GDEP
Slovensky
EnglishGDEP communication protocol
This protocol is used for sending and receiving SMS messages and MMS ones, processing WAP requirements, and playing SMS games.
The protocol is built on the standards such as TCP, HTTP (or HTTPS), and XML. GAP server (GAme Platform) on the Orange side and an application (D2000 KOM process) are the communication partners.
The implementation in D2000 System supports the following messages:
Table 1
Message | Direction | Meaning |
|---|---|---|
HELLO | KOM->GAP | Logging on (name + password) to the GAP platform when starting the connection. |
INQUIRE_LINK | KOM->GAP | Testing the functionality of connection after a longer period of inactivity. |
INQ_RSP | KOM->GAP | Response to INQUIRE. |
RECEIVE (sms) | GAP->KOM | Receiving SMS from GAP server. |
RCV_RSP (sms) | KOM->GAP | Confirmation of receiving SMS by D2000 KOM. |
SEND (sms) | KOM->GAP | Sending SMS message. |
SND_RSP (sms) | GAP->KOM | Confirmation of receiving SMS by GAP server. |
ACCEPTED | GAP->KOM | Confirmation of receiving SMS or MMS by SMS/MMS center. |
ACC_RSP | KOM->GAP | Response to ACCEPTED from D2000 KOM. |
RECEIPT (sms) | GAP->KOM | Confirmation of receiving SMS by an end-user. |
REC_RSP | KOM->GAP | Response to RECEIPT from D2000 KOM. |
BY | KOM->GAP | End of connection by D2000 KOM. |
BY_RSP | GAP->KOM | Response to BY from GAP server. |
NAK | GAP->KOM | An unacceptable message is declined. |
The following messages have not been implemented yet:
Table 2
Message | Direction | Meaning |
|---|---|---|
RECEIVE (wap) | GAP->KOM | Receiving WAP requirement from GAP server. |
RCV_RSP (wap) | KOM->GAP | WAP requirement by D2000 KOM. |
RECEIVE (mms-xml) | GAP->KOM | Receiving MMS from GAP server. |
RCV_RSP (mms-xml) | KOM->GAP | Confirmation of receiving MMS by D2000 KOM. |
SEND (mms-xml) | KOM->GAP | Sending MMS. |
SND_RSP (mms-xml) | GAP->KOM | Confirmation of receiving MMS by GAP server. |
RECEIPT (mms) | GAP->KOM | Confirmation of receiving MMS by an end-user. |
SCORE | KOM->GAP | Changing the player's score. |
SCO_RSP | GAP->KOM | Response to SCORE from GAP server. |
NICK | KOM->GAP | Administration of nicknames: creation, canceling, adding, deleting, and searching. |
NICK_RSP | GAP->KOM | Response to NICK from GAP server. |
Communication line category: TCP/IP-TCP
TCP Parameters:
Host: String max. 80 characters – server name in INET format (name or numerical address a.b.c.d).
Port: TCP port number (1 to 65535).
Line number: Not used, enter any number.
Note: GDEP protocol is built over HTTP or HTTPS protocol. D2000 KOM process does not include HTTPS communication. It uses the stunnel program (modular method). The stunnel program is able to wrap both the client and server communication in the SSL layer. As GDEP protocol needs the implementation of both client and server on each side (both GAP server and D2000 KOM), you must start two stunnel processes:
one of them is in a server mode, which will wait on the connection of the GAP server. After processing the SSL layer, it will send data to the defined port, on which D2000 KOM is waiting as a GDEP server (see the Server Port parameter).
the other one is in a client mode, which waits on the defined port. D2000 KOM (client-side) will be connected with it. After wrapping data in the SSL layer, the stunnel will send them to a target computer and port (server port of GAP server). Therefore, in the Host parameter, there will be localhost and in the Port parameter, there will be the port number on which the stunnel process is waiting in a client mode.
Communication protocol: GDEP
Station address: not used
Note: There must be exactly ONE communication station on the line.