KR100925636B1 - The networking method between non-pc device and server for providing the application services - Google Patents

Abstract

The present invention relates to a method of communication between a non-pc terminal and a server for providing an application service, and provides content, service, and terminal control for a non-pc type terminal having a low specification. It is intended to provide a communication method between a non-PC type terminal and a server for providing an application service, which provides a communication protocol between a non-PC type terminal and a server required for providing various application services.

To this end, the present invention, in the communication method between the non-PC-type terminal and the server for providing an application service, the sequence number (SN) in the AuthRequest packet as the server is requested to communicate to the non-PC-type terminal; Inserting challenge information 1 (C1) and transmitting it to the PC-type terminal; The server receives the challenge information 2 (C2) and the hash value of the AuthResponse packet as the server receives the AuthResponse packet including the challenge information 2 (C2) and the hash value from the non-PC type terminal as a result of the AuthRequest packet transmission. Inspecting and performing first terminal authentication; And inserting a hash value calculated using a sequence number (SN), challenge information 2 (C2), a user password, and a payload in the request packet into the corresponding request packet as the server succeeds in the first terminal authentication. -Sending to the PC-type terminal.

Non-pc type, terminal, server, low specification, communication protocol (WDCP), application service (WADS service), work operation

Description

The networking method between non-pc device and server for providing the application services

The present invention relates to a communication method between a non-pc type terminal (non-pc device) and a server (server) for providing an application service, and more specifically, to provide content, services for non-pc type terminal having a low specification The present invention relates to a communication method between a non-PC type terminal and a server for providing an application service, which provides a communication protocol between a non-PC type terminal and a server required for providing various application services such as provision and terminal control.

A non-pc type terminal refers to a terminal commonly used for providing a specific application service except for a general PC (eg, a desktop PC, a notebook PC, etc.), and is an intelligent ubiquitous robot (eg; Net toy, edu toy, cleaning robot, pet robot, etc.), electronic picture frame, pet feeding machine, wireless camera, PDA, PSP, PMP, MP3, digital home appliances and the like.

On the other hand, the non-PC-type terminal is configured in a home network built in the home or connected to the corresponding server on the Internet through a specific communication network connection device, such as performing the function under the control of the server, for example to provide content Service provision, terminal control, and the like. Here, the non-PC type terminal is equipped with a function for connecting to any one communication network, such as a wired LAN, wireless LAN, portable Internet (aka WiBro), wireless Internet through mobile communication, home network, and the like.

Meanwhile, a technology for allowing a user to control a robot by giving a robot control command by operating a computer is disclosed in Korean Patent No. 565208 (name of the invention: "Robot Control Method in PC"), and on a network A robot control technique for controlling a robot is disclosed in Korean Patent Laid-Open Publication No. 2006-79092 (name of the invention: "Communication Control System and Method Using Terminal Data Format").

However, the communication protocol between the terminal and the server required for providing various application services such as terminal-server communication, for example, content provision, service provision, terminal control, etc. proposed in the above-described prior arts, the terminal has a high specification (eg, It is implemented under the premise of having a high performance CPU, a large memory, a high resource rate, etc., and there is a problem in that it is not suitable for a non-PC type terminal having a low specification.

That is, in the above conventional technologies, the server sends the terminal control information as an XML document from the server to the terminal in controlling the terminal. In this case, the non-PC type terminal performs an operation such as parsing and reading an XML document. Because of the considerable resources and time, there is a problem that the application service does not work properly.

Therefore, in providing various application services such as content provision, service provision, and terminal control between a non-PC type terminal and a server, terminal-server communication that can be efficiently used by a non-PC type terminal having a low specification as described above. Protocol development is urgently needed.

Accordingly, the present invention has been proposed to solve the above problems and meet the above requirements, and provides various application services such as content provision, service provision, and terminal control for non-PC terminals having low specification specifications. It is an object of the present invention to provide a communication method between a non-PC type terminal and a server for providing an application service, which provides a communication protocol between the non-PC type terminal and the server required for the purpose.

The objects of the present invention are not limited to the above-mentioned objects, and other objects and advantages of the present invention which are not mentioned above can be understood by the following description, and will be more clearly understood by the embodiments of the present invention. Also, it will be readily appreciated that the objects and advantages of the present invention may be realized by the means and combinations thereof indicated in the claims.

A first method of the present invention for achieving the above object is a communication method between a non-PC terminal and a server for providing an application service, AuthRequest packet as the server is requested to communicate to the non-PC terminal Inserting a sequence number (SN) and challenge information 1 (C1) into the non-PC type terminal; The server receives the challenge information 2 (C2) and the hash value of the AuthResponse packet as the server receives the AuthResponse packet including the challenge information 2 (C2) and the hash value from the non-PC type terminal as a result of the AuthRequest packet transmission. Inspecting and performing first terminal authentication; And inserting a hash value calculated using a sequence number (SN), challenge information 2 (C2), a user password, and a payload in the request packet into the corresponding request packet as the server succeeds in the first terminal authentication. -Sending to the PC-type terminal.

In addition, the first method of the present invention, the server, the operation result performed by the non-PC-type terminal as a result of the request packet transmission, the sequence number (SN), challenge information 2 (C2), user password and response Upon receiving the response packet including the hash value calculated by using the payload in the packet from the non-PC terminal, the challenge information 2 (C2) and the hash value of the response packet are examined to verify the second terminal. Performing; And ending the communication between the non-PC-type terminals by processing the terminal operation result of the payload of the response packet as the server succeeds in the second terminal authentication.

On the other hand, the second method of the present invention, in the communication method between the non-PC-type terminal and the server for providing an application service, the non-PC-type terminal from the server to the sequence number (SN) and the challenge information 1 (C1) Confirming a sequence number (SN) of the AuthRequest packet according to the received AuthRequest packet, and performing a first server authentication through challenge information 1 (C1) of the AuthRequest packet; As the non-PC type terminal succeeds in the first server authentication, a hash value is generated using the sequence number SN, the challenge information 1 C1, and its user password, and its challenge information 2 C2. Generating c); Inserting, by the non-PC type terminal, the generated hash value and challenge information 2 (C2) into an AuthResponse packet and transmitting it to the server; As the non-PC type terminal receives the request packet including the challenge information 2 (C2) and the hash value from the server as a result of the AuthResponse packet transmission, the challenge information 2 (C2) and the hash value of the request packet are received. Performing a second server authentication through; And performing the corresponding work process according to the data content of the payload of the request packet as the non-PC type terminal succeeds in the second server authentication.

In addition, the second method of the present invention includes a sequence number (SN), challenge information 2 (C2), a user password and the response packet in a corresponding response packet into which the non-PC type terminal inserts the work result. And inserting the hash value calculated using the payload and transmitting the hash value to the server.

On the other hand, according to the third method of the present invention, in a communication method between a non-PC terminal and a server for providing an application service, a sequence number is included in an AuthRequest packet as the non-PC terminal is requested to communicate with the server. Inserting (SN) and challenge information 1 (C1) and transmitting it to the server; As the non-PC type terminal receives the AuthResponse packet including the hash value and the challenge information 2 (C2) from the server as a result of the AuthRequest packet transmission, the challenge information 2 (C2) and the hash value of the AuthResponse packet are received. Inspecting and performing a first server authentication; And a hash value calculated using a sequence number (SN), a challenge information 2 (C2), a user password, and a payload in the request packet in the corresponding request packet as the non-PC type terminal successfully authenticates the first server. Inserting and transmitting to the server.

In addition, the third method of the present invention, the non-PC-type terminal, the operation result performed by the server as a result of the request packet transmission, the sequence number (SN), challenge information 2 (C2), user password and response Performing the second server authentication by examining the challenge information 2 (C2) and the hash value of the response packet when the response packet including the hash value calculated by using the payload in the packet is received from the server. ; And ending the communication between the servers by processing a server operation result of the payload of the response packet as the non-PC type terminal succeeds in the second server authentication.

On the other hand, according to the fourth method of the present invention, in a communication method between a non-PC terminal and a server for providing an application service, the server transmits a sequence number (SN) and challenge information 1 (C1) from the non-PC terminal. Performing a first terminal authentication through the challenge information 1 (C1) of the AuthRequest packet upon receiving the included AuthRequest packet; Generating a hash value using the sequence number SN, the challenge information 1 C1, and the corresponding user password as the server successfully authenticates the first terminal, and generating its own challenge information 2 C2; ; Inserting, by the server, the generated hash value and challenge information 2 (C2) into an AuthResponse packet and transmitting it to the non-PC type terminal; When the server receives the request packet including the challenge information 2 (C2) and the hash value from the non-PC type terminal, the second terminal authentication is performed through the challenge information 2 (C2) and the hash value of the request packet. Performing; And performing the corresponding job processing according to the data content of the payload of the request packet as the server succeeds in the second terminal authentication.

In addition, the fourth method of the present invention uses the sequence number (SN), the challenge information 2 (C2), the user password and the payload in the response packet in the response packet in which the server inserts the operation result. The method may further include inserting the calculated hash value and transmitting the calculated hash value to the non-PC type terminal.

delete

delete

delete

delete

delete

delete

delete

delete

delete

As described above, the present invention has an effect of allowing a non-PC type terminal having a low specification specification to be efficiently provided with various application services such as content provision, service provision, and terminal control from a server.

In addition, the present invention is a non-PC terminal is provided with a variety of application services can be communicated to the server with only low specification specifications, the processing power, low resources, and the effect that can efficiently process the application service in a small time There is.

The above objects, features, and advantages will become more apparent from the detailed description given hereinafter with reference to the accompanying drawings, and accordingly, those skilled in the art to which the present invention pertains may share the technical idea of the present invention. It will be easy to implement. In addition, in describing the present invention, when it is determined that the detailed description of the known technology related to the present invention may unnecessarily obscure the gist of the present invention, the detailed description thereof will be omitted. Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings.

1 is a configuration diagram of an embodiment of a communication network to which the present invention is applied.

As shown in FIG. 1, a communication network to which the present invention is applied includes a non-pc type terminal 10, a server 20, and a remote terminal 30.

In the communication network as described above, a user uses a function (eg, a wake-up call, a cleaning, etc.) mounted in the non-PC type terminal 10 at home, or receives a service (eg, weather information, etc.) received from the server 20. When provided through the non-PC-type terminal 10 or when going out, the remote terminal 30 is connected to the server 20 to set its own non-PC-type terminal 10 (eg, wake-up call time change, etc.) Do it.

The non-PC type terminal 10 may be an intelligent ubiquitous robot such as a net toy 11, an edutoy 12, a cleaning robot 13, a pet feeding machine 14, a pet robot (not shown), or the like. , An electronic picture frame 15, a wireless camera 16, a PDA (not shown), a PSP (not shown), a PMP (not shown), an MP3 (not shown), and a digital home appliance (not shown).

The remote terminal 30 may be any type of terminal capable of connecting to a server 20 on the Internet, such as a computer 31, a mobile communication terminal 32, a WiBro terminal 33, or the like.

In the present invention, the non-spec having the low specification required for providing various application services (hereinafter, referred to collectively as "non-PC type terminal application service (WADS service)"), such as content provision, service provision, and terminal control. It provides a communication protocol between the PC-type terminal 10 and the server 20.

Hereinafter, the communication protocol proposed in the present invention will be referred to as "Wireless Application Device Service (WADS) Device Control Protocol" or "WDCP", and will be described with reference to the non-PC type terminal 10 with reference to FIGS. 2 and 3. A communication method between the servers 20 will be described in detail. In addition, the non-PC-type terminal 10 is a wireless LAN [eg; For example, the communication with the server 20 through the Nessot (NESPOT) of the Republic of Korea KT will be described as an example.

2 is a flowchart illustrating an example of a communication process when a server initiates communication in a communication method between a non-PC terminal and a server for providing an application service according to the present invention, and FIG. FIG. 1 is a flowchart illustrating a communication process when a non-PC type terminal initiates communication among a non-PC type terminal and a server for providing an application service.

Prior to describing the present invention, terms used in the present invention will be briefly described as follows. "byte" stands for 8-bit array, "AES" stands for "Advanced Encryption Standard", which is the official name for the current American standard encryption algorithm, and "hash value" means input messages of arbitrary length. "MD5" is an abbreviation of "Message Digest 5" and means an algorithm used for data error detection specified in "RFC1321".

First, the operating method of the non-PC type terminal 10, the operating method of the server 20, the initial server connection method of the non-PC type terminal 10, the non-PC type terminal IP address management method of the server 20 Next, the communication process in the case where the server 20 initiates communication will be described with reference to FIG. 2, and the communication process in the case where the non-PC type terminal 10 initiates communication is referred to FIG. This will be described.

The operation method of the non-PC type terminal 10 and the operation method of the server 20 are as follows.

In order to support the communication protocol (WDCP) proposed in the present invention, the non-PC type terminal 10 and the server 20 must be equipped with a communication daemon for WDCP processing, respectively, the non-PC type terminal 10 Communication daemons mounted in the "device daemon" (device daemon) (device daemon), the communication daemon mounted in the server 20 will be defined as "server daemon" (server daemon).

The server daemon of the server 20 communicates directly with the device daemon of the non-PC-type terminal 10, and the communication between the server daemon and the device daemon uses the "UDP" method and the "MD5-Challenge" method. Perform authentication between two-way terminal-server.

The device daemon of the non-PC type terminal 10 uses the IP address of the server 20 when the non-PC type terminal is assigned an IP address through WLAN authentication from a WLAN access system (not shown). After transmitting to the daemon, the communication protocol (WDCP) is started between the server daemon and the device daemon. In addition, when the device daemon of the non-PC-type terminal 10 receives a specific command from the server daemon of the server 20, the device daemon performs a corresponding job processing and transmits the job result to the server daemon. In addition, the device daemon of the non-PC-type terminal 10 transmits the event information to the server daemon when a specific event occurs in the non-PC-type terminal.

The operation operation by the communication protocol (WDCP) proposed in the present invention is described as "status inquiry operation operation", "control operation operation", "notification setting operation operation", "general notification operation operation", "terminal notification operation operation" "," Terminal management operation operation "," test operation operation "and the like, and the specification of the communication protocol (WDCP) for the operation operation will be described later.

The communication protocol (WDCP) proposed in the present invention uses a "UDP" method, and in particular, each operation operation is an "AuthRequest packet", "AuthResponse packet", and "Request" between the non-PC type terminal 10 and the server 20. 4 packet pairs of "packet" and "response packet" are transmitted and received, which is defined as "WADS unit operation" in the present invention. The payload of each of the request packet and the response packet is encrypted by “AES encryption” and transmitted and received. A detailed description thereof will be described later in the corresponding part.

The initial server access method of the non-PC-type terminal 10 is as follows.

The non-PC type terminal 10 needs to transmit the IP address assigned through the WLAN access system to the server 20 so that the non-PC type terminal application service can be provided from the server 20 (aka WADS). Service participation]. Here, when the non-PC type terminal 10 fails to transmit the IP address to the server 20, the non-PC type terminal 10 retransmits the IP address up to a predetermined number of times (for example, 10 times) at intervals of a predetermined time (for example, 1 minute, etc.). If the IP address retransmission fails, the IP address retransmission is restarted when the terminal is rebooted or a new IP address is acquired without performing any further retransmission. Then, when the IP address transmission is successful, the non-PC type terminal 10 periodically transmits its IP address to the server 20 at intervals of a predetermined time (for example, 10 minutes, etc.) and then communicates with the server. Maintain communication.

In addition, the non-PC-type terminal 10 and the user password (preferably to be used in conjunction with the password for the WADS service, hereinafter "WADS password") to perform the communication with the server 20 and the It is preferable that the IP address of the server 20 is set on the terminal in advance. This user password and server IP address setting is made through an external port of the non-PC-type terminal 10, which is a well-known technology and its detailed description will be omitted.

The non-PC type terminal IP address management scheme of the server 20 is as follows.

The server 20 manages a terminal IP address received from the non-PC type terminal 10, and stores and manages the IP address and the IP address reception date and time of the corresponding terminal for each non-PC type terminal on the IP address DB. In addition, by searching the IP addresses of all non-PC-type terminals on the IP address DB at a predetermined time / number of times (eg, once a day), server resources may be efficiently managed by deleting IP addresses that are over one day old. .

In addition, when communication with the specific non-PC type terminal 10 is required, the server 20 initiates communication with the terminal through the corresponding non-PC type terminal IP address on the IP address DB. In this case, the server 20 may immediately terminate communication with the terminal when communication is not performed with the corresponding non-PC type terminal IP address or communication according to a communication protocol (WDCP) to be described later. have.

A communication process when the server 20 initiates communication will be described with reference to FIG. 2 as follows. Status inquiry operation operation, control operation operation, notification setting operation operation, terminal management operation operation, and test operation operation during the operation operation by the aforementioned communication protocol (WDCP) correspond to the case where the server 20 initiates communication. . In addition, the test operation operation is applicable even when the non-PC type terminal 10 initiates communication.

First, when communication with the non-PC type terminal 10 is required, the server 20 inquires the corresponding IP address stored in the IP address DB, sets the IP address as a destination, and sets the AuthRequest packet to the non-PC. It transmits to the "20001" UDP port of the type terminal 10 (201). In this case, it is preferable that a "sequence number (SN)" and "challenge (C1)" are inserted into the AuthRequest packet. In addition, the server 20 transmits an AuthRequest packet to the non-PC type terminal 10 using its "# 1 " UDP port.

The sequence number SN is included in all packets according to the communication protocol (WDCP) proposed in the present invention, and the same sequence number SN is used during the same unit operation operation. For example, when the server 20 transmits an AuthRequest packet in which a certain sequence number (SN) is inserted to the non-PC type terminal 10, the non-PC type terminal 10 receiving the AuthRequest packet is connected to the server ( The same sequence number (SN) received from 20) is inserted into the AuthResponse packet and transmitted to the server 20. The sequence number SN is generated by a device (server or non-PC type terminal) that initiates communication related to the work operation, and the initial sequence number (SN) of a 4-byte integer value at the time when each device starts up. ) Is randomly generated and the sequence number SN is incremented by "1" every time the next unit operation is performed.

Accordingly, when the non-PC type terminal 10 receives an AuthRequest packet from the server 20, the non-PC type terminal 10 recognizes that one unit work operation is started through a sequence number SN included in the AuthRequest packet. Server authentication is performed through the challenge information 1 (C1) included in the AuthRequest packet, and the hash is executed using the sequence number (SN), the challenge information 1 (C1), and the user password (WADS password) stored in the user. A value is generated, and a separate " challenge information 2 (challenge (C2)) " is generated, and the challenge information 2 (C2) and the generated hash value are inserted into the AuthResponse packet and transmitted to the server 20 (202). . Here, the non-PC type terminal 10 transmits an AuthResponse packet toward the "No. 1" UDP port of the non-PC type terminal 10 using its "20001" UDP port.

Then, as the server 20 receives the AuthResponse packet from the non-PC type terminal 10, the server 20 checks the challenge information 2 (C2) and the hash value included in the received AuthResponse packet, and then legitimate non-PC type. After authenticating whether the terminal is a terminal, the request packet is transmitted to the non-PC type terminal 10 (203). Here, the request packet is preferably inserted with a sequence number SN, challenge information 2 (C2), a user password (WADS password) and a hash value calculated using the payload in the request packet. In addition, the payload in the request packet is encrypted in an "AES" manner. In addition, the server 20 transmits the request packet toward the " 20001 " UDP port of the non-PC type terminal 10 using its " number 1 " UDP port.

Accordingly, when the non-PC type terminal 10 receives the request packet from the server 20, the non-PC type terminal 10 checks the challenge information 2 (C2) and the hash value included in the received request packet to determine whether it is a legitimate server. After authentication, the payload in the request packet is decrypted in an "AES" manner, and the corresponding work result is processed according to the contents of the data contained in the payload. (204). Here, the response packet preferably includes a sequence number SN, challenge information 2 (C2), a user password (WADS password), and a hash value calculated using the payload in the response packet. In addition, the payload in the response packet is encrypted in an "AES" manner. In addition, the non-PC type terminal 10 transmits a response packet toward the " 1 " UDP port of the server 20 using its " 20001 " UDP port.

Then, when the server 20 receives the response packet from the non-PC type terminal 10, the server 20 checks the challenge information 2 (C2) and the hash value included in the received response packet, and then justifies the non-PC type. After authenticating the terminal, the payload in the response packet is decrypted in an "AES" manner, and the communication with the non-PC terminal 10 is terminated after processing the non-PC terminal operation result carried in the payload. .

On the other hand, each of the server 20 and the non-PC-type terminal 10, if there is a data error in the received packet or the hash value is wrong [in the case of an abnormal packet] to the other device that transmitted the packet. Communication is terminated without a separate response, and when there is an abnormality in the payload in the packet, it is preferable to transmit an error message (ErrMsg) packet to the other device.

A communication process when the non-PC type terminal 10 initiates communication will be described with reference to FIG. 3 as follows. The general notification operation, the terminal notification operation operation, and the test operation operation during the operation operation by the aforementioned communication protocol (WDCP) correspond to the case where the non-PC type terminal 10 initiates communication.

First, when the non-PC-type terminal 10 needs to communicate with the server 20, the corresponding server IP address stored in itself is set as a destination, and the AuthRequest packet is transmitted to the "representative" UDP port of the server 20. (301). Here, it is preferable that a sequence number SN and challenge information 1 C1 are inserted into the AuthRequest packet. In addition, the non-PC type terminal 10 transmits an AuthRequest packet using different port numbers according to the corresponding operation operation. In the case of the normal notification operation operation, the non-PC type terminal 10 transmits its own " 20002 " UDP port to the terminal notification operation. In case of operation, the corresponding AuthRequest packet is transmitted to the server 20 by using its own " 20003 " UDP port and in case of a test operation, its own " 20004 " UDP port.

Accordingly, as the server 20 receives the AuthRequest packet from the non-PC type terminal 10, a new UDP to use for the corresponding unit work processing (that is, the corresponding sequence number) with the non-PC type terminal 10. Generate a port number (e.g., " 2 " UDP port shown in FIG. 3), perform terminal authentication through the challenge information 1 (C1) included in the AuthRequest packet, and perform the sequence number SN and the challenge. The hash value is generated using the information 1 (C1) and the user password (WADS password) stored in the user, and the challenge information 2 (C2) is generated to generate the challenge information 2 (C2) and the generated hash value. Is inserted into the AuthResponse packet and transmitted to the non-PC type terminal 10 (302).

Then, when the non-PC type terminal 10 receives the AuthResponse packet from the server 20, the non-PC type terminal 10 checks the challenge information 2 (C2) and the hash value included in the received AuthResponse packet and authenticates whether it is a legitimate server. After that, the request packet is transmitted to the server 20 (303). Here, the request packet is preferably inserted with a sequence number SN, challenge information 2 (C2), a user password (WADS password) and a hash value calculated using the payload in the request packet. In addition, the payload in the request packet is encrypted in an "AES" manner.

Accordingly, when the server 20 receives the request packet from the non-PC type terminal 10, the server 20 examines the challenge information 2 (C2) and the hash value included in the received request packet, thereby validating the non-PC. After authenticating whether it is a mobile terminal or not, the payload in the request packet is decrypted in an "AES" manner, and the corresponding work process is performed according to the contents of the data contained in the payload. The transmission is transmitted to the terminal 10 (304). Here, it is preferable that the response packet includes a sequence number SN, a challenge information 2 (C2), a user password (WADS password), and a hash value calculated using a payload in the response packet. In addition, the payload in the response packet is encrypted in an "AES" manner.

Then, when the non-PC terminal 10 receives the response packet from the server 20, the non-PC type terminal 10 checks the challenge information 2 (C2) and the hash value included in the received response packet to authenticate whether the server is legitimate. After that, the payload in the response packet is decoded in an "AES" manner, and the communication with the server 20 is terminated after processing the server operation result loaded in the payload.

On the other hand, each of the server 20 and the non-PC-type terminal 10, if there is a data error in the received packet or the hash value is wrong [in the case of an abnormal packet] to the other device that transmitted the packet. Communication is terminated without a separate response, and when there is an abnormality in the payload in the packet, it is preferable to transmit an error message (ErrMsg) packet to the other device.

Next, the packet basic structure according to the communication protocol (WDCP) proposed in the present invention, and the structure of each packet, for example, an AuthRequest packet, an AuthResponse packet, an InfoRequest packet, an InfoResponse packet, a ControlRequest packet, a ControlResponse packet, It describes in detail the NotiSetRequest packet, NotiSetResponse packet, NotiRequest packet, NotiResponse packet, DevNotiRequest packet, DevNotiResponse packet, DevMngRequest packet, DevMngResponse packet, TestRequest packet, TestResponse packet, ServiceRequest packet, ServiceResponse packet, and ErrMsg packet which is an error message packet. .

First, all packets according to the communication protocol (WDCP) proposed in the present invention have a common packet basic structure as shown in Table 1 below.

In Table 1, the packet consists of "6" header fields and payloads, and a network byte order follows a conventional big-endian scheme. Of the header fields, only the "P_Code" field has a text format, and all remaining header fields have a binary format.

In the above [Table 1], the “Type” field of the header field indicates the type (use) of the corresponding packet and is defined as shown in the following [Table 2].

In [Table 2], packets designated as "not used" in the "remarks" means packets not used in the communication protocol (WDCP) proposed in the present invention, it is used in the communication protocol between different terminal-server Consider that the packet is defined in the present communication protocol (WDCP).

In [Table 1], a sequence number SN is inserted into the “SN” field of the header field to match a transmission / reception packet (a request packet and a response packet) according to one unit operation operation.

In the above [Table 1], the beer field of the device (server or non-PC type terminal) corresponding to the destination or source of the packet is inserted in the "MAC" field of the header field.

In [Table 1], a product code of a device (server or non-PC type terminal) corresponding to the destination or source of the packet is inserted in the "P_Code" field of the header field. Here, the product code refers to a unique number given when a corresponding device is registered in a non-PC type terminal application service (WADS service). For example, if the product code is "NP-CAM-00001-001", "NP" is the Nespot, "CAM" is the device type number 3-digit character pointing to the camera, and "00001" is the product identification within the device type. "001" represents a version identification number of the corresponding product, respectively. In addition, if the device does not correspond to a destination or source for a particular packet, all bytes of the "P_Code" field are filled with "0x00".

In Table 1, a hash value obtained by using the MD5 method from a challenge information, a user password (WADS password), a payload, or the like is inserted into the "Hash" field of the header field. In addition, the hash value is preferably calculated from data before performing AES encryption. In particular, in the present invention, the process of generating a hash value according to each packet is different from each other, which will be described in detail later in the description of the packet.

In [Table 1], the "Length" field of the header field indicates the number of bytes of the payload following the header field. In particular, in the case of the request packet and the response packet, the number of bytes of the payload without AES encryption is performed. "Is inserted into the field.

In Table 1, data of various contents according to the type of each packet is inserted into the payload of the packet, and in particular, the payload of each request packet and the response packet except for the AuthRequest packet and the AuthResponse packet is AES encrypted. The payload of such a packet will be described later in detail in the following description of the packet.

Next, each packet-specific structure used for each operation operation by the communication protocol (WDCP) proposed in the present invention will be described, and all numbers in the following tables are values in the form of "Hex".

[Table 3] below shows the structure of an AuthRequest packet regarding a work operation start request.

In Table 3, " SN " represents a sequence number SN, and the apparatus for initiating communication regarding the work operation generates this sequence number SN.

In [Table 3], the hash value is inserted as "0x00", "Length" is inserted as "0x10", and the payload is a randomly generated 16-byte challenge generated by the device transmitting the corresponding AuthRequest packet. The challenge is inserted.

[Table 4] below shows the structure of an AuthResponse packet regarding accepting a work operation start.

In Table 4, "SN" represents a sequence number SN, which is a sequence number SN included in an AuthRequest packet received from an opposite device.

In the above [Table 4], the hash value is a 16-byte long value encoded by the sequence number (SN), the user password (WADS password) and the challenge information of the AuthRequest packet by MD5 method. For example, the hash value generation function may be expressed as "Hash = MD5 (SN + PW + Challenge)".

In Table 4, "Length" is inserted as "0x10", and the payload is not randomly generated by the corresponding device to send this AuthResponse packet to the other device, not the challenge information of the AuthRequest packet received from the other device. 16-byte long challenge information is inserted.

[Table 5] below shows the structure of an InfoRequest packet regarding a status inquiry request.

In [Table 5], "SN" is a sequence number (SN) included in an AuthRequest packet received from an opposite device.

In Table 5, the hash value is a sequence number (SN), a user password (WADS password), the challenge information of the AuthResponse packet and the 16-byte length value of the payload of the InfoRequest packet by MD5 scheme. For example, the hash value generation function may be expressed as "Hash = MD5 (SN + PW + Challenge + Payload)".

In Table 5, an Info Number defined for each device to send the InfoRequest packet to the other device is inserted in the payload, and "0" and "1" of the Info Numbers are reserved. For example, "0" is used to request information corresponding to all the info numbers defined for each device, and "1" is used to request notification setting information of the corresponding device.

[Table 6] below shows the structure of the InfoResponse packet regarding the status inquiry response.

In Table 6, "SN" is a sequence number (SN) included in the AuthRequest packet received from the other device.

In Table 6, the hash value is a 16-byte long value obtained by encoding the sequence number (SN), the user password (WADS password), the challenge information of the AuthResponse packet, and the payload of the InfoResponse packet in an MD5 manner. For example, the hash value generation function may be expressed as "Hash = MD5 (SN + PW + Challenge + Payload)".

In the above [Table 6], the payload is inserted with the status information of the device to send this InfoResponse packet to the other device, as shown in the following [Table 7]. Table 7 is defined as an info unit in the present invention.

In the above [Table 7], "0" is inserted into the "Info Result" when the acquisition of the status information is successful, and an arbitrary value is inserted when the acquisition of the status information is failed, and the length of the immediately following "Info Result Data" field is inserted into the "Length". In addition, additional result information for the status information request is inserted into the "Info Result Data", which may be omitted.

In [Table 7], “device status information” has a format as shown in [Table 8] below, and additional status information is not inserted when status information transmission fails.

In the above [Table 8], when the info number of the InfoRequest packet received from the other device is "0", the info unit for all the info numbers described in the specification (function definition) of the device to which the InfoResponse packet is to be sent must be inserted. do. On the other hand, when the info number of the InfoRequest packet received from the opposite device is not "0", the field value of "Info Unit Count" is always inserted as "1". On the other hand, when the info number of the InfoRequest packet received from the other device is "1", the notification setting information info unit must be included, as shown in Table 9 below.

[Table 10] below shows the structure of a ControlRequest packet regarding a control request.

In Table 10, "SN" is a sequence number (SN) included in an AuthRequest packet received from an opposite device.

In Table 10, the hash value is a sequence number (SN), a user password (WADS password), the challenge information of the AuthResponse packet and the 16-byte length value of the payload of the ControlRequest packet by MD5 encoding. For example, the hash value generation function may be expressed as "Hash = MD5 (SN + PW + Challenge + Payload)".

In Table 10, control information for controlling an opponent device is inserted into the payload, as shown in Table 11 below. [Table 11] is defined as a control unit in the present invention.

[Table 12] shows the structure of ControlResponse packet regarding control response.

In Table 12, "SN" is a sequence number (SN) included in an AuthRequest packet received from an opposite device.

In Table 12, the hash value is a 16-byte long value obtained by MD5 encoding the sequence number (SN), the user password (WADS password), the challenge information of the AuthResponse packet, and the payload of the ControlResponse packet. For example, the hash value generation function may be expressed as "Hash = MD5 (SN + PW + Challenge + Payload)".

In [Table 12], the device control result is inserted into the payload. In the "Control Result Data" field as shown in [Table 13], the "device status information" shown in [Table 8] is shown together with the corresponding control result. It is further included and inserted.

In [Table 13], “Control Result” is inserted with “0” when the control succeeds, and an arbitrary value is inserted when the control fails. “Length” is inserted with the length of the immediately following “Control Result Data” field. If the status information acquisition fails, the "device status information" is omitted.

Table 14 below shows the structure of a NotiSetRequest packet for a notification set request.

In Table 14, "SN" is a sequence number (SN) included in an AuthRequest packet received from an opposite device.

In Table 14, the hash value is a 16-byte long value obtained by encoding the sequence number (SN), the user password (WADS password), the challenge information of the AuthResponse packet, and the payload of the NotiSetRequest packet in an MD5 manner. For example, the hash value generation function may be expressed as "Hash = MD5 (SN + PW + Challenge + Payload)".

In Table 14, notification setting information to be sent to the opposite device is inserted into the payload, as shown in Table 15 below. In the present invention, Table 15 is defined as a NotiSet Unit.

In [Table 15], "NotiNumber" is a notification setting distinguishing number of a corresponding device, and "Noti Flag" is a value distinguishing setting / cancellation in the notification setting. If it is "0x00", it is set to cancel, and if it is "0x01", it is set. Means.

[Table 16] below shows the structure of a NotiSetResponse packet regarding a notification set response.

In [Table 16], "SN" is a sequence number (SN) included in an AuthRequest packet received from an opposite device.

In Table 16, the hash value is a 16-byte long value obtained by MD5 encoding the sequence number (SN), the user password (WADS password), the challenge information of the AuthResponse packet, and the payload of the NotiSetResponse packet. For example, the hash value generation function may be expressed as "Hash = MD5 (SN + PW + Challenge + Payload)".

In Table 16, a notification setting result is inserted into a payload. As shown in Table 17, a "0" is inserted into a "NotiSet Result" and a random value is inserted into a notification setting failure. The length of the immediately following "NotiSet Result Data" field is inserted in "Length".

[Table 18] below shows the structure of a NotiRequest packet for a general notification request.

In [Table 18], "SN" is inserted into the sequence number (SN) generated by the device for sending the NotiRequest packet, preferably the non-PC-type terminal 10.

In [Table 18], the non-PC type terminal 10 uses the sequence number (SN), the user password (WADS password), the challenge information of the AuthResponse packet received from the server 20, and the payload of the NotiRequest packet. Generates a hash value of 16 bytes in length. For example, the hash value generation function may be expressed as "Hash = MD5 (SN + PW + Challenge + Payload)".

In Table 18, notification information to be transmitted to the server 20 by the non-PC type terminal 10 is inserted into the payload, as shown in Table 19 below. [Table 19] is defined as a noti unit in the present invention.

In Table 19, "Noti Random ID" is generated by using a random number as a unique identification key for the corresponding notification allocated by the non-PC type terminal 10, and in particular, the non-PC type terminal 10 is NotiRequest. When retransmitting a packet, the "Noti Random ID" generated by the original NotiRequest packet should be used.

In [Table 19], when the server 20 receives the same "Noti Random ID" within a predetermined time (for example, a full day) for the same "Noti Number" from the same non-PC-type terminal 10 Do not process the notification.

[Table 20] below shows NotiResponse packet structure related to general notification response.

In [Table 20], "SN" is a sequence number (SN) included in a NotiRequest packet received from the other device, preferably the non-PC type terminal 10.

In Table 20, the hash value is a 16-byte long value obtained by encoding the sequence number (SN), the user password (WADS password), the challenge information of the AuthResponse packet, and the payload of the NotiResponse packet in an MD5 manner. For example, the hash value generation function may be expressed as "Hash = MD5 (SN + PW + Challenge + Payload)".

In [Table 20], a notification transmission result is inserted into a payload, and as shown in [Table 21], a "0" is inserted into a "Noti Result" when a notification transmission succeeds and an arbitrary value when a notification transmission fails. However, when the server 20 has received the notification that has already been processed successfully from the non-PC type terminal 10, the "Noti Result" is set to "1", and the non-PC type terminal 10 is received. When the notification result is not received, the non-PC type terminal 10 includes information for determining whether the notification is resent.

[Table 22] below shows the structure of a DevNotiRequest packet for a terminal notification request.

In [Table 22], "SN" is inserted into the sequence number (SN) generated by the device sending the DevNotiRequest packet, preferably the non-PC-type terminal 10.

In [Table 22], the non-PC type terminal 10 MD5 the sequence number (SN), the user password (WADS password), the challenge information of the AuthResponse packet received from the server 20 and the payload of the DevNotiRequest packet MD5 Generates a hash value of 16 bytes in length. For example, the hash value generation function may be expressed as "Hash = MD5 (SN + PW + Challenge + Payload)".

In Table 22, terminal notification information to be transmitted to the server 20 by the non-PC type terminal 10 is inserted into the payload, as shown in Table 23 below. In the present invention, Table 23 is referred to as a DevNoti Unit.

Examples of the device type unit on the Table 23 may include the following Table 24.

[Table 25] below shows the structure of a DevNotiResponse packet regarding a terminal notification response.

In Table 25, "SN" is a sequence number (SN) included in a DevNotiRequest packet received from the other device, preferably the non-PC terminal 10.

In Table 25, the hash value is a 16-byte length value obtained by MD5 encoding the sequence number (SN), the user password (WADS password), the challenge information of the AuthResponse packet, and the payload of the DevNotiResponse packet. For example, the hash value generation function may be expressed as "Hash = MD5 (SN + PW + Challenge + Payload)".

In [Table 25], the terminal notification processing result is inserted into the payload. As shown in [Table 26], “DevNoti Result” includes “0” when the terminal notification processing succeeds and an arbitrary value when the terminal notification processing fails. Is inserted, the field value of "Length" is always set to "0".

[Table 27] below shows the structure of a DevMngRequest packet for a terminal management request.

In Table 27, "SN" is a sequence number (SN) included in an AuthRequest packet.

In Table 27, the hash value is a 16-byte length value obtained by encoding the sequence number (SN), the user password (WADS password), the challenge information of the AuthResponse packet, and the payload of the DevMngRequest packet in an MD5 manner. For example, the hash value generation function may be expressed as "Hash = MD5 (SN + PW + Challenge + Payload)".

In Table 27, terminal management setting information for non-PC type terminal management is inserted into a payload, as shown in Table 28 below. In the present invention, [Table 28] is defined as a device management unit (DevMng Unit).

Types of the device management unit on the [Table 28] may be the following [Table 29] and the like.

[Table 30] below is a structure of a DevMngResponse packet regarding a terminal management response.

In Table 30, "SN" is a sequence number (SN) included in an AuthRequest packet.

In Table 30, the hash value is a 16-byte length value obtained by MD5 encoding the sequence number (SN), the user password (WADS password), the challenge information of the AuthResponse packet, and the payload of the DevMngResponse packet. For example, the hash value generation function may be expressed as "Hash = MD5 (SN + PW + Challenge + Payload)".

In the above [Table 30], the terminal management processing result is inserted into the "payload". When the terminal management processing succeeds in the "DevMng Result" as shown in the following [Table 31], "0" is arbitrary when the terminal management processing fails. The value is inserted. In the present invention, [Table 31] is defined as a device management result unit (DevMng Result Unit).

Examples of the type of device management resort unit in the above [Table 31] may include the following [Table 32].

[Table 33] is the structure of TestRequest packet related to test request.

In Table 33, "SN" is a sequence number (SN) included in an AuthRequest packet.

In [Table 33], the apparatus for sending the TestRequest packet, for example, the non-PC terminal 10 or the server 20, the sequence number (SN), the user password (WADS password), the AuthResponse received from the server 20 A hash value of 16 bytes in length is generated by encoding the challenge information of the packet and the payload of the TestRequest packet by MD5 method. For example, the hash value generation function may be expressed as "Hash = MD5 (SN + PW + Challenge + Payload)".

In Table 33, test information for a test is inserted into the payload, as shown in Table 34 below. This Table 34 is defined as a test unit in the present invention.

Examples of the test unit on Table 34 may include the following Table 35.

[Table 36] below shows the structure of a TestResponse packet regarding a test response.

In Table 36, "SN" is a sequence number (SN) included in an AuthRequest packet.

In Table 36, the hash value is a 16-byte length value obtained by encoding a sequence number (SN), a user password (WADS password), challenge information of an AuthResponse packet, and a payload of the TestResponse packet in an MD5 manner. For example, the hash value generation function may be expressed as "Hash = MD5 (SN + PW + Challenge + Payload)".

In [Table 36], a response to the test request ("test response") is inserted in the payload. When the test response succeeds in "Test Result" as shown in [Table 37], the test response fails. A random value is inserted at time. Here, when the test response fails, the field value of "Length" is "0". In the present invention, Table 37 is defined as a test result unit.

Examples of the test resort unit on the Table 37 may include the following Table 38.

In [Table 38], when the value of "Test Number" is "0x03", the corresponding device receiving the TestResponse packet (that is, the device that sent the TestRequest packet) responds with the successful reception of the TestResponse packet. Immediately, it sends the requested data by connecting to the other device using the communication method set in the TestRequest packet.

[Table 39] below shows the structure of a ServiceRequest packet regarding a service request.

In Table 39, "SN" is a sequence number (SN) of the AuthRequest packet generated by the apparatus for sending the ServiceRequest packet, preferably the non-PC terminal 10 and transmitted to the server 20. .

In [Table 39], the non-PC type terminal 10 stores the sequence number (SN), the user password (WADS password), the challenge information of the AuthResponse packet received from the server 20, and the payload of the ServiceRequest packet. Generates a hash value of 16 bytes in length. For example, the hash value generation function may be expressed as "Hash = MD5 (SN + PW + Challenge + Payload)".

In Table 39, information for a corresponding service request to be transmitted to the server 20 by the non-PC type terminal 10 is inserted into the "payload", as shown in Table 40 below.

Types of service request information related to the above [Table 40] may include the following [Table 41].

[Table 42] below shows the structure of a ServiceResponse packet regarding a service response.

In Table 42, "SN" is a sequence number (SN) included in an AuthRequest packet.

In Table 42, the hash value is a 16-byte long value obtained by encoding the sequence number (SN), the user password (WADS password), the challenge information of the AuthResponse packet, and the payload of the ServiceResponse packet using the MD5 scheme. For example, the hash value generation function may be expressed as "Hash = MD5 (SN + PW + Challenge + Payload)".

In [Table 42], the response ("service response") of the server 20 to the service request of the non-PC-type terminal 10 is inserted in the payload, as shown in the following [Table 43] "0" is inserted in the service response, and "1" in the service response failure. This Table 43 is defined as a service result unit in the present invention.

Examples of the service resort unit shown in Table 43 may include the following Table 44. FIG.

[Table 45] below shows the structure of an ErrMsg packet regarding an error message.

In [Table 45], each of "SN", "MAC", and "P_Code" is inserted with a corresponding value relating to a packet causing an error, and a hash value is determined according to the type of packet corresponding to the corresponding unit operation operation. Generated by the hash value generation function, the error code has a length of 2 bytes (Length). [Table 46] below shows the error code.

Finally, some additional points in the communication protocol (WDCP) proposed in the present invention will be described.

First, packet timeout and packet retransmission will be described.

In the present invention, a timeout time is set to 5 seconds when one packet is transmitted. In addition, each of the non-PC-type terminal 10 and the server 20 terminates the corresponding unit work operation at the timeout, the connection state information with the other device including the sequence number (SN) for the unit work operation, etc. Delete it.

In the present invention, in principle, all packets are not retransmitted during one unit operation. However, in the general notification work operation, the non-PC type terminal 10 or the server 20 may restart the unit work operation. Here, when retransmitting the packet, for example, the value of the Noti Random ID of the NotiRequest packet uses a value generated from the first NotiRequest packet.

Next, packet encryption will be described.

In the present invention, the payloads of all packets except for the AuthRequest packet and the AuthResponse packet, for example, request packets and response packets, are encrypted using AES and a 128-bit encryption key. Here, the "P_MD5 pseudorandom number generation" method is used to generate a 128-bit encryption key.

The encryption process performed in the present invention is as follows, and the corresponding parameters will be described first.

"PW": A user password (WADS password), which is a 16-byte long padded with "0x00" at the back.

"PD": data in the payload before performing encryption.

"seed": A seed value for random number generation, generated from a sequence number (SN), challenge information of an AuthRequest packet, challenge information of an AuthResponse packet, and the like.

-"AES (x) k": This is the result of encrypting x in AES using the encryption key k.

-"D (x) k": The result of decrypting x in AES using the encryption key k.

-"HMAC_MD5 (secret, seed)": MD5 hash value using secret and predefined seed.

-"P_MD5 (secret, seed)": Result of applying P_MD5 pseudorandom function to secret using seed.

First, pseudo-random value "k" is obtained from "PW" having a length of 16 bytes by using the following [Equation 1].

Then, using the following [Equation 2], the value "m" in which the packet is encrypted using "k" is obtained.

Then, the obtained "m" is transmitted to the other device.

Then, the opponent apparatus obtains "k" from "P", decodes "m", and obtains "PD" using Equation 3 below.

Next, the contents of the terminal report will be described.

As mentioned above, when the non-PC-type terminal 10 receives a report request from the server 20 by the terminal management operation operation, the terminal report in the form of a text file as shown in [Table 47] below “DevMng Result Data "and transmits it to the server 20 as a DevMngResponse packet.

On the other hand, the method of the present invention as described above can be written in a computer program. And the code and code segments constituting the program can be easily inferred by a computer programmer in the art. In addition, the written program is stored in a computer-readable recording medium (information storage medium), and read and executed by a computer to implement the method of the present invention. The recording medium may include any type of computer readable recording medium.

The present invention described above is capable of various substitutions, modifications, and changes without departing from the technical spirit of the present invention for those skilled in the art to which the present invention pertains. It is not limited by the drawings.

1 is a configuration diagram of an embodiment of a communication network to which the present invention is applied;

2 is a flowchart illustrating an example of a communication process when a server initiates communication in a communication method between a non-PC terminal and a server for providing an application service according to the present invention;

3 is a flowchart illustrating a communication process when a non-PC type terminal initiates communication among a non-PC type terminal and a server for providing an application service according to the present invention.

* Explanation of symbols on the main parts of the drawing

10: non-PC type terminal

20: server

Claims (53)

In the communication method between the non-PC-type terminal and the server for providing an application service, In response to the server requesting communication to a non-PC type terminal, inserting a sequence number (SN) and challenge information 1 (C1) into an AuthRequest packet and transmitting the non-PC type terminal to the non-PC type terminal; The server receives the challenge information 2 (C2) and the hash value of the AuthResponse packet as the server receives the AuthResponse packet including the challenge information 2 (C2) and the hash value from the non-PC type terminal as a result of the AuthRequest packet transmission. Inspecting and performing first terminal authentication; And As the server successfully authenticates the first terminal, the non--value is inserted into the request packet by inserting a sequence number (SN), challenge information 2 (C2), a user password, and a hash value calculated using the payload in the request packet. Sending to the PC type terminal Communication method between the non-PC terminal and the server for providing an application service comprising a. The method of claim 1, The hash calculated by the server using the work result performed by the non-PC type terminal as a result of the request packet transmission, the sequence number (SN), the challenge information 2 (C2), the user password and the payload in the response packet. Performing a second terminal authentication by examining a challenge information 2 (C2) and a hash value of the response packet when the response packet including the value is received from the non-PC type terminal; And Terminating communication between the non-PC-type terminals by processing the terminal operation result of the payload of the response packet as the server succeeds in the second terminal authentication. Communication method between the non-PC terminal and the server for providing an application service further comprising. In the communication method between the non-PC-type terminal and the server for providing an application service, When the non-PC type terminal receives an AuthRequest packet including the sequence number SN and the challenge information 1 C1 from the server, the non-PC type terminal checks the sequence number SN of the AuthRequest packet, Performing first server authentication through challenge information 1 (C1); As the non-PC type terminal succeeds in the first server authentication, a hash value is generated using the sequence number SN, the challenge information 1 C1, and its user password, and its challenge information 2 C2. Generating c); Inserting, by the non-PC type terminal, the generated hash value and challenge information 2 (C2) into an AuthResponse packet and transmitting it to the server; As the non-PC type terminal receives a request packet including the challenge information 2 (C2) and a hash value from the server as a result of the AuthResponse packet transmission, the challenge information 2 (C2) and the hash of the request packet are received. Performing second server authentication through a value; And Performing, by the non-PC type terminal, a corresponding work process according to the data content of the payload of the request packet as the second server authentication succeeds; Communication method between the non-PC terminal and the server for providing an application service comprising a. The method of claim 3, wherein Inserting a hash value calculated using a sequence number (SN), challenge information 2 (C2), a user password and a payload in the response packet into a corresponding response packet into which the non-PC type terminal inserts the result of the work performed. Transmitting to the server Communication method between the non-PC terminal and the server for providing an application service further comprising. In the communication method between the non-PC-type terminal and the server for providing an application service, When the non-PC type terminal is requested to communicate with the server, inserting a sequence number (SN) and challenge information 1 (C1) into an AuthRequest packet and transmitting the same to the server; As the non-PC type terminal receives the AuthResponse packet including the hash value and the challenge information 2 (C2) from the server as a result of the AuthRequest packet transmission, the challenge information 2 (C2) and the hash value of the AuthResponse packet are received. Inspecting and performing a first server authentication; And As the non-PC type terminal succeeds in the first server authentication, a hash value calculated using a sequence number (SN), challenge information 2 (C2), a user password, and a payload in the request packet is inserted into a corresponding request packet. Transmitting to the server Communication method between the non-PC terminal and the server for providing an application service comprising a. The method of claim 5, wherein The hash value calculated using the work result performed by the server as a result of the request packet transmission by the non-PC type terminal, the sequence number (SN), the challenge information 2 (C2), the user password and the payload in the response packet. Performing a second server authentication by examining a challenge information 2 (C2) and a hash value of the response packet when the response packet is received from the server; And Terminating communication between the servers by processing the server operation result of the payload of the response packet as the non-PC type terminal succeeds in the second server authentication. Communication method between the non-PC terminal and the server for providing an application service further comprising. In the communication method between the non-PC-type terminal and the server for providing an application service, When the server receives an AuthRequest packet including a sequence number (SN) and challenge information 1 (C1) from the non-PC type terminal, the first terminal authentication is performed through the challenge information 1 (C1) of the AuthRequest packet. Performing; Generating a hash value using the sequence number SN, the challenge information 1 C1, and the corresponding user password as the server successfully authenticates the first terminal, and generating its own challenge information 2 C2; ; Inserting, by the server, the generated hash value and challenge information 2 (C2) into an AuthResponse packet and transmitting it to the non-PC type terminal; When the server receives the request packet including the challenge information 2 (C2) and the hash value from the non-PC type terminal, the second terminal authentication is performed through the challenge information 2 (C2) and the hash value of the request packet. Performing; And Performing the corresponding work processing according to the data content of the payload of the request packet as the server succeeds in the authentication of the second terminal; Communication method between the non-PC terminal and the server for providing an application service comprising a. The method of claim 7, wherein The non-PC is inserted into the corresponding response packet into which the server inserts the result of the work performed, and the hash value calculated using the sequence number (SN), the challenge information 2 (C2), the user password and the payload in the response packet. Transmitting to a mobile terminal Communication method between the non-PC terminal and the server for providing an application service further comprising. The method according to any one of claims 1 to 8, The communication between the server and the non-PC type terminal may be any one of a status inquiry operation operation, a control operation operation, a notification setting operation operation, a general notification operation operation, a terminal notification operation operation, a terminal management operation operation, and a test operation operation. A communication method between a non-PC terminal and a server for providing an application service, characterized in that made in relation to. The method of claim 9, As the sequence number SN, the same one sequence number SN is used while communication regarding one unit work operation is performed. And a server or a non-PC type terminal which initiated the communication generates the sequence number (SN). The method according to any one of claims 1 to 8, Communication between the server and the non-PC-type terminal is a communication between the non-PC-type terminal and the server for providing an application service, characterized in that the UDP. The method according to any one of claims 2, 4, 6, and 8, And a payload in the request packet and a payload in the response packet are encrypted and transmitted in an AES manner. The method according to any one of claims 1 to 8, And the non-PC type terminal transmits an IP address allocated from a network access system to the server. The method of claim 13, When the non-PC type terminal fails to transmit the IP address, the IP address is retransmitted up to a predetermined number of times at a predetermined time interval, and when the IP address retransmission fails, the IP address is started upon rebooting the terminal or obtaining a new IP address. A communication method between a non-PC terminal and a server for providing an application service, characterized in that. The method of claim 13, The server stores and manages the IP address received from the non-PC type terminal for each non-PC type terminal, and provides an application service, characterized in that for deleting the IP address exceeding a predetermined time after storing the IP address. Communication method between the non-PC-type terminal and the server for. The method according to any one of claims 1 to 8, Communication between the non-PC type terminal and the server for providing an application service is characterized in that the server and the non-PC type terminal each terminate the communication when there is a data error in the received packet or the corresponding hash value is wrong. Way. The method of claim 16, The server and the non-PC type terminal each responds as an error message packet when the payload in the corresponding packet is abnormal among the data errors, and the communication between the non-PC type terminal and the server for providing an application service. Way. The method according to any one of claims 2, 4, 6, and 8, The request packet includes an InfoRequest packet for a status inquiry request, a ControlRequest packet for a control request, a NotiSetRequest packet for a notification setting request, a NotiRequest packet for a general notification request, a DevNotiRequest packet for a terminal notification request, and a DevMngRequest for a terminal management request. A packet, a TestRequest packet for a test request, and a ServiceRequest packet for a service request, The response packet includes an InfoResponse packet for a status inquiry response, a ControlResponse packet for a control response, a NotiSetResponse packet for a notification setting response, a NotiResponse packet for a general notification response, a DevNotiResponse packet for a terminal notification response, and a DevMngResponse for a terminal management response. And a packet, a TestResponse packet regarding a test response, and a ServiceResponse packet regarding a service response. delete delete delete delete delete delete delete delete delete delete delete delete delete delete delete delete delete delete delete delete delete delete delete delete delete delete delete delete delete delete delete delete delete delete delete

Images