WO2019028673A1

WO2019028673A1 - B/s architecture-based data communication system and method, web server, and monitoring system

Info

Publication number: WO2019028673A1
Application number: PCT/CN2017/096413
Authority: WO
Inventors: 宁运琨; 赵国如; 张咪; 李慧奇; 梁升云
Original assignee: 深圳先进技术研究院
Priority date: 2017-08-08
Filing date: 2017-08-08
Publication date: 2019-02-14

Abstract

The present application relates to a B/S architecture-based data communication system and method, a web server, and a monitoring system. The data communication system comprises a client, a communication server, and a web server for connecting the client and the communication server. The web server is provided with an intermediate communication component. A browser of the client initiates an HTTP request to the intermediate communication component of the web server. The intermediate communication component processes the HTTP request and establishes a socket communication with the communication server. The intermediate communication component passes a socket request corresponding to the HTTP request to the communication server by means of a TCP/IP protocol. The communication server processes the socket request, and returns corresponding result data to display the result data via the browser of the client. In the above manner, a client in the present application does not need to download an application and perform related operations, and does not need to be updated frequently, bringing convenience to users and reducing maintenance costs.

Description

Data communication system, method, web server and monitoring system based on B/S architecture

Technical field

The present application relates to the field of communications technologies, and in particular, to a data communication system, method, web server, and monitoring system based on a B/S architecture.

Background technique

In the field of communication such as the Internet of Things, wearable devices are becoming more and more popular, so remote control of wearable devices is particularly important. At present, in the manipulation of the wearable remote terminal, whether the communication between the wearable device and the server or the communication between the remote monitoring platform and the server is based on the TCP (Transmission Control Protocol)-based C/ The S architecture (Client/Server structure, client and server structure) is implemented.

For the communication between the remote monitoring platform and the server, if it is implemented by C/S architecture, it is mostly applicable to the local area network. This method requires special technology for remote access, and the system is specially designed to handle distributed data. Relative to the rapid development of the Internet, there is a lack of certain scalability. In addition, the C/S architecture can be seen as a "fat" client architecture, because the client needs to implement most of the business logic and interface presentation. In this architecture, the client needs to bear a lot of pressure, the user is When using, you need to install monitoring platform software to achieve communication between the two. There are also restrictions on the operating system of the client. In addition, every time the system is upgraded, all client programs need to be changed and upgraded.

It is not difficult to see that the need for C/S architecture will result in users needing to install and download the corresponding client software to achieve remote control of the wearable terminal, which will require a lot of traffic and time costs, and bring certain personal information to the user. The risk of leakage; at the same time, the client needs to update and upgrade from time to time, resulting in high maintenance costs, and the operation is troublesome and inconvenient for the user.

Therefore, there is a need in the art to provide a new data communication system to solve the above technical problems.

Summary of the invention

Based on this, it is necessary to provide a data communication system, method, web server and monitoring system based on the B/S architecture for the above problems, and the client does not need to download the application program and related operations, and does not need to update frequently. Bring convenience to users, reduce maintenance costs, etc.

A data communication system based on a B/S architecture, the data communication system comprising a client, a communication server, and a web server for connecting the client and the communication server, the web server having an intermediate communication component:

The browser of the client initiates an HTTP request to the intermediate communication component of the web server;

The intermediate communication component processes the HTTP request and establishes a Socket communication with the communication server;

The intermediate communication component transmits a Socket request corresponding to the HTTP request to the communication server by using a TCP/IP protocol;

The communication server processes the Socket request and returns corresponding result data to display the result data through a browser of the client.

A data communication method based on a B/S architecture, the data communication method comprising:

The intermediate communication component of the web server obtains an HTTP request initiated by the client's browser;

The intermediate communication component transmits a Socket request corresponding to the HTTP request to the communication server through a TCP/IP protocol.

A web server for a data communication system based on a B/S architecture, the data communication system includes a client, a communication server, the web server is configured to connect the client and a communication server, and the web server is provided Intermediate communication component:

The intermediate communication component acquires an HTTP request initiated by a browser of the client;

The intermediate communication component processes the HTTP request and establishes a Socket communication with the communication server letter;

A wearable device-based monitoring system, the monitoring system comprising a wearable device, and the above-described B/S architecture-based data communication system, the wearable device establishing a network data connection with the communication server, the client The end is used for remote monitoring of the wearable device:

The browser of the client initiates an HTTP request to the intermediate communication component of the web server when acquiring the operation of the user;

The communication server processes the Socket request, acquires result data corresponding to the wearable device according to the Socket request, and returns the result data to be displayed by a browser of the client.

The data communication system, method, web server and monitoring system based on the B/S architecture, the browser of the client initiates an HTTP request to the intermediate communication component of the web server, and the intermediate communication component processes the HTTP request And establishing a socket communication with the communication server, the intermediate communication component transmitting a Socket request corresponding to the HTTP request to the communication server by using a TCP/IP protocol, the communication server processing the Socket request, and returning Corresponding result data, the result data is finally displayed by the browser of the client. In this way, the client of the present application does not need to download the application and related operations, nor does it need to update frequently, which brings convenience to the user, reduces maintenance costs, and the like, and the user only needs to operate through the browser. Remote monitoring and operation of wearable devices.

DRAWINGS

1 is a block diagram of a data communication system based on a B/S architecture in an embodiment;

2 is a flowchart of a data communication method based on a B/S architecture in an embodiment;

3 is a block diagram of a Web server of a data communication system based on a B/S architecture in an embodiment;

4 is a block diagram of an implementation example of a specific application example of a data communication system based on a B/S architecture;

5 is a flowchart showing an implementation of a communication server in the data communication system of FIG. 4;

6 is a flowchart of an event processing of a new client initiating a TCP connection request in the data communication system of FIG. 4;

7 is a flow chart of event processing of the intermediate communication component in the data communication system of FIG. 4;

8 is a flow chart showing the processing mechanism of the communication between the client browser and the intermediate communication component in the data communication system of FIG. 4.

Detailed ways

In one embodiment, please refer to FIG. 1. FIG. 1 is a block diagram of a data communication system based on a B/S architecture in an embodiment. The data communication system based on the B/S architecture in this embodiment includes but is not limited to a client. 11. A communication server 13 and a web server 12 for connecting the client 11 and the communication server 13, the web server 12 being provided with an intermediate communication component 121.

It should be noted that, in this embodiment, the B/S architecture refers to a browser/server architecture, the web server refers to a web server, and HTTP refers to a hypertext transfer protocol (HyperText Transfer Protocol). The TCP/IP protocol refers to the Transmission Control Protocol/Internet Protocol, and the Socket refers to the socket.

It should be noted that the browser of the client 11 initiates an HTTP request to the intermediate communication component 121 of the web server 12, and the intermediate communication component 121 processes the HTTP request and establishes with the communication server 13. Socket communication, the intermediate communication component 121 passes a Socket request corresponding to the HTTP request to the communication server 13 via a TCP/IP protocol, the communication server 13 processes the Socket request, and returns corresponding result data, To pass the guest The browser of the client 11 presents the result data.

In a preferred embodiment, the client 11 is a mobile terminal conveniently used by a user, and may specifically be a handheld mobile phone, a tablet computer or the like with a browser installed thereon.

It should be noted that, when receiving the HTTP request initiated by the browser, the intermediate communication component 121 creates a socket and establishes a TCP/IP connection with the communication server 13, and if the connection fails, the connection fails. The information is returned to the front end page of the browser, and if the connection is successful, the Socket request corresponding to the HTTP request is sent to the communication server 13.

It is worth mentioning that the intermediate communication component 121 in this embodiment can create a socket by using a socket creation function, for example, an existing socket creation function can be utilized:

$socket=socket_create(AF_INET, SOCK_STREAM, SOL_TCP)

In addition, the intermediate communication component 121 of this embodiment may send the Socket request to the communication server 13 through a socket write function, for example, socket_write ($socket, $message) may be utilized.

The intermediate communication component 121 sets a timeout period for the socket to wait for the first time, and receives the result data returned by the communication server 13 according to the Socket request, if the second time does not reach the first time If the result data returned by the communication server 13 is not received, the information of the failed data transmission is returned to the front page of the browser, and if the result data returned by the communication server 13 is received at the first time, the data is closed. Socket communication, whether the format of the detection result data is valid. If the format is incorrect, the information in response to the data exception is returned to the front page of the browser. If the format is correct, the returned result data is parsed and packaged into a predetermined one. The format data is sent to the front page of the browser. The first time may be 10 seconds, the second time may be 5 seconds, or the combination of the first time is 8 seconds and the second time is 4 seconds, which is not limited herein. In a specific embodiment, the intermediate communication component 121 can receive the result data returned by the communication server 13 according to the Socket request through a socket read function, for example, by using $msg=socket_read($socket, 1024). The predetermined format data may be json data (JavaScript Object Notation).

In the present embodiment, the data transmission format between the intermediate communication component 121 and the communication server 13 Need to be consistent, first, the client 11 needs to send a packet of the format "HEL; xxxxxxxxxxx; @" to the communication server 13 to mean that the client 11 goes online, and then sends a packet of the format "DATA; xxxxxxxxxxx; @" to the communication server 13 Used to transfer the data requested by the client 11.

In summary, both the wearer's wearable device and the web application of the front-end user act as a client for the communication server 13. When transmitting data between the two, the client 11 and the wearable device are first required to go online. After the online connection is successful, the data is transmitted to the communication server 13 according to a predetermined data transmission format, and even after the transmission of the data is completed, the Socket communication is closed. The intermediate communication component 121 can be implemented by the php language (Universal Open Source Scripting Language), which can run on an Apache (Web Server Software) server.

Further, the communication server 13 in this embodiment may be based on the Epoll communication model and run on a Linux system. The Epoll of this embodiment is an improved poll for the Linux kernel to process large batch file descriptors. In this way, the embodiment can significantly improve the system CPU utilization when the program has only a small amount of active in a large number of concurrent connections.

The communication server 13 initializes the Socket communication parameter, establishes the listening Socket descriptor, initializes the Epoll communication model, creates a linked list containing only the head node, initializes and starts the system timing of controlling the heartbeat packet, before processing the Socket request. , invokes the Epoll_wait function, and waits for the triggering of the client communication event in a blocking manner. In this embodiment, the Socket descriptor of the communication server 13 may use socket_fd, and the Epoll_wait function may use the Epoll_wait function.

It is worth noting that the triggering of the communication event needs to satisfy one of the following events, the main program of the communication server 13 will exit the Epoll_waiting function, trigger the response to the client, and then, for example, can dynamically calculate the number of online clients. The change in the number of online clients is mainly due to the occurrence and processing of communication events of the following clients, including but not limited to:

(1) The new client initiates a TCP (Transmission Control Protocol) connection request;

(2) A request has been made to disconnect the TCP connection from the client that has established the connection;

(3) The client that has established the connection has data (command) transmission;

(4) The client that has established the connection abnormally disconnects the TCP connection;

It should be noted that when the new client initiates the TCP connection request, the Epoll_wait function of the communication server 13 finds that the communication event to be processed is equal to listening to the Socket descriptor, and is accepted according to the Socket descriptor. The function returns a new Socket Descriptor, and the intercepted Socket Descriptor is added to the Epoll handle via the Epoll_Event Registration Function to communicate bi-directionally with the new client that has established a connection using the Socket Descriptor. The acceptance function is an accept function, and the event registration function is an Epoll_ctl function.

It should be noted that the webpage of the browser of the client 11 in this embodiment may adopt a JQuery (JavaScript code library, or JavaScript framework) framework, and communicate with the intermediate communication component 121 via AJAX (Asynchronous Javascript And XML). The asynchronous JavaScript and XML) engine implements a communication connection to enable the web page to be asynchronously updated. In this embodiment, the AJAX engine can be used to create a fast dynamic webpage, and the webpage can be asynchronously updated by performing a small amount of data exchange with the server in the background. In other words, in this embodiment, the entire webpage can be reloaded without reloading the entire webpage. The update of a certain part of the webpage does not cause the webpage to be stuck. This application can further improve the user experience in this way.

In the present embodiment, when the user clicks the browser's transmission request button or the like, a communication event with the intermediate communication component 121 is triggered. Specifically, the browser of the client 11 implements and sets parameters of the request address, the request data, the request mode, and the timeout period by using the $.ajax() method, and when an HTTP request is initiated when the user's operation is obtained, if If the front-end webpage of the browser does not receive the return data within the timeout period, the current network abnormality is prompted. If the returned data is received within the timeout period, it is determined whether the data is a connection failure (connect_error), and if so, the server connection failure is prompted. If not, then it is determined whether the returned data is a data exception (data_error), and if so, it prompts a return data exception. If not, it determines whether the returned data is timeout (overtime), and if so, prompts to wait for the return data to time out, if not, then The obtained result data is parsed and displayed on the browser web page.

The client 11 of the present application does not need to download the application program and related operations, and does not need to update frequently, which brings convenience to the user and reduces maintenance cost. The user only needs to operate through the browser to realize remote monitoring and operation. . Especially for the client 11 for mobile phones, tablets, There is no need to download the application, and it is very space-saving, and it is not necessary to repeatedly update and download the latest client due to the update of the server, which brings great convenience to the client 11.

Please refer to FIG. 2 . FIG. 2 is a flowchart of a data communication method based on the B/S architecture in an embodiment. The data communication method based on the B/S architecture in this embodiment includes but is not limited to the following steps.

S201. The intermediate communication component of the web server obtains an HTTP request initiated by the client's browser.

In S201, when receiving the HTTP request initiated by the browser, the intermediate communication component of the embodiment creates a socket and establishes a TCP/IP connection with the communication server, and if the connection fails, the connection fails. The information is returned to the front end page of the browser, and if the connection is successful, the Socket request corresponding to the HTTP request is sent to the communication server.

The intermediate communication component in this embodiment can create a socket by using a socket creation function, for example, the existing $socket=socket_create (AF_INET, SOCK_STREAM, SOL_TCP) can be utilized. In addition, the intermediate communication component of this embodiment may send the Socket request to the communication server through a socket write function, for example, socket_write ($socket, $message) may be utilized.

S202. The intermediate communication component processes the HTTP request and establishes a Socket communication with the communication server.

S203. The intermediate communication component delivers a Socket request corresponding to the HTTP request to the communication server by using a TCP/IP protocol.

After the step S203, the intermediate communication component of the embodiment sets the timeout period for waiting for the Socket communication to be the first time, and receives the result data returned by the communication server according to the Socket request, if the first time is not reached. If the result data returned by the communication server is not received in the second time, the information of the failed data transmission is returned to the front page of the browser, and if the result returned by the communication server is received at the first time Data, close Socket communication, check whether the format of the result data is valid. If the format is incorrect, return the information in response to the data exception to the front page of the browser. If the format is correct, parse the returned result data, and The packaged into predetermined format data is sent to the front page of the browser. The first time may be 10 seconds, the second time may be 5 seconds, or the first time is 8 seconds, and the second time is 4 seconds. set.

The intermediate communication component may receive the result data returned by the communication server according to the Socket request through a socket read function, for example, by using $msg=socket_read($socket, 1024). The predetermined format data may be json data. Please refer to FIG. 3. FIG. 3 is a block diagram of a Web server of a data communication system based on a B/S architecture in an embodiment. The Web server 12 of this embodiment is provided with an intermediate communication component 121, and the data communication system includes the above. The client 11, the communication server 13, and the web server 12 are used to connect the client 11 and the communication server 13.

The intermediate communication component 121 acquires an HTTP request initiated by the browser of the client 11.

The intermediate communication component 121 processes the HTTP request and establishes a Socket communication with the communication server 13.

The intermediate communication component 121 delivers a Socket request corresponding to the HTTP request to the communication server 13 via a TCP/IP protocol.

The intermediate communication component 121 of this embodiment can create a socket by using a socket creation function, for example, the existing $socket=socket_create (AF_INET, SOCK_STREAM, SOL_TCP) can be utilized. In addition, the intermediate communication component 121 of this embodiment may send the Socket request to the communication server 13 through a socket write function, for example, socket_write ($socket, $message) may be utilized.

Next, the intermediate communication component 121 sets the timeout period for the socket to wait for the first time, and receives the result data returned by the communication server 13 according to the Socket request, if the second time does not reach the first time If the result data returned by the communication server 13 is not received, the information of the failed data transmission is returned to the front page of the browser, and if the result data returned by the communication server 13 is received at the first time, the data is closed. Socket communication, whether the format of the detection result data is valid, and if the format is incorrect, the information in response to the data abnormality is returned to the front page of the browser. If the format is correct, the returned result data is parsed and packaged into a predetermined format data and sent to the front page of the browser. The first time may be 10 seconds, the second time may be 5 seconds, or the combination of the first time is 8 seconds and the second time is 4 seconds, which is not limited herein.

As described above, the intermediate communication component 121 in the embodiment can receive the result data returned by the communication server 13 according to the Socket request through a socket read function, for example, by using $msg=socket_read($socket,1024). ). The predetermined format data may be json data.

It should be particularly noted that the overall communication process of the data communication system based on the B/S architecture of the present application may specifically send an HTTP request to the intermediate communication component 121 for the client 11 of the browser, and the intermediate communication component 121 sends a Socket request to the communication server 13 The communication server 13 then sends a Socket request to the wearable device, wherein the communication server 13 and the wearable device transmit through the socket. The wearable device returns data to the communication server 13, to the intermediate communication component 121, and finally to the client 11 of the browser. The intermediate communication component 121 of the present application forwards the data transmission to the Tcp protocol of the HTTP protocol, and the data transmission based on the Tcp protocol between the communication server 13 and the wearable device.

The intermediate communication component 121 is a server, ie, a B/S architectural mode, for the client 11 of the browser to receive the request of the client 11 of the browser. The intermediate communication component 121, for the communication server 13, is a client, that is, a C/S architecture mode, and sends a request to the server (communication server 13).

In addition, the present application further provides a wearable device-based monitoring system, which includes a wearable device, and a data communication system based on the B/S architecture mentioned in any of the above embodiments, preferably, the embodiment Using the data communication system shown in FIG. 1, the wearable device establishes a network data connection with the communication server 13, and the client 11 is configured to remotely monitor the wearable device.

The browser of the client 11 initiates an HTTP request to the intermediate communication component 121 of the web server 12 when acquiring the user's operation.

The intermediate communication component 121 sets a Socket corresponding to the HTTP request through a TCP/IP protocol The request is passed to the communication server 13.

The communication server 13 processes the Socket request, acquires result data corresponding to the wearable device according to the Socket request, and returns the result data for display by the browser of the client 11.

It should be particularly noted that the client 11 uses the client 11 to remotely monitor the wearable device, and the client 11 itself can be a mobile terminal conveniently used by the user, and the specific mobile phone and tablet can be handheld. Computer, of course, with the development of technology, it can also be a wearable device capable of intelligent display and operation, such as a smart watch, a smart helmet, smart glasses, etc. In other words, this embodiment can use a mobile phone, a tablet computer or Wearable devices remotely monitor wearable devices. Referring to FIG. 4 and FIG. 8 , FIG. 4 is a block diagram of an implementation example of a specific application example of a data communication system based on a B/S architecture, and FIG. 5 is a flowchart of implementing a communication server in the data communication system of FIG. 4 . FIG. 7 is a flow chart of event processing for initiating a TCP connection request in a data communication system of FIG. 4, FIG. 7 is a flow chart of event processing of the intermediate communication component in the data communication system of FIG. 4, and FIG. 8 is a client in the data communication system of FIG. The communication mechanism of the browser and the intermediate communication component processes the flow chart.

As shown in FIG. 5, the implementation process of the communication server in the data communication system of the specific application example includes but is not limited to the following steps:

The server socket communication parameter is initialized, and the socket socket socket descriptor socket_fd is established;

Epoll initialization;

The establishment and initialization of a dynamic linked list;

Initialize and start the timer interrupt;

Call the epoll_wait function to see if there is a client communication event trigger; if YES, exit the epoll_wait function, traverse and process the communication event. If NO, block and continue waiting.

As shown in FIG. 6, the event processing procedure for a new client to initiate a TCP connection request in the data communication system of the specific application example includes but is not limited to the following steps:

The Epoll_wait function finds that the event to be processed is triggered to be equal to the listening socket descriptor socket_fd;

Calling the accept function according to socket_fd returns a new socket socket descriptor socket_fd;

Add the new socket descriptor socket_fd that is heard to the Epoll handle via the Epoll_ctl function;

return.

As shown in FIG. 7, the event processing procedure of the intermediate communication component in the data communication system of the specific application example includes but is not limited to the following steps:

Start;

Received an HTTP request from the front end of the browser;

Create socket, socket_create();

Establish a TCP connection, socket_connect();

Is the TCP connection established successfully? If not, return connect_error to the browser front end and close the Socket communication, and end; if yes, send data to the communication server, socket_write();

Set the timeout period, socket_set_option();

Waiting for data returned by the communication server;

Is it waiting for more than 5 seconds? If yes, return overtime to the browser front end, and close the Socket communication and end; if not, obtain the data returned by the communication server;

Is the data valid? If not, return data_error to the browser front end, and close the Socket communication and end; if yes, parse the data and convert it to json format;

Return json data to the browser front end;

Close Socket communication and end.

As shown in FIG. 8, the processing mechanism of the communication mechanism between the client browser and the intermediate communication component in the data communication system of the specific application example includes but is not limited to the following steps:

Start;

Click the send request button;

Trigger a communication event;

Set parameters such as timeout time;

Is the waiting time less than 10 seconds? If not, the user is prompted to be abnormal and ends; if so, the return data is received;

Is the return data a connect_error? If yes, the user is prompted to connect to the server failed and ends; if not, is the data returned as data_error?

If yes, the user is prompted to return a data exception and ends. If not, is the returned data overtime?

If so, the user is prompted to wait for the return data to time out and end, and if not, the returned data is presented to the browser page and ends.

It should be noted that the data communication system of this embodiment may be combined with the related description of any of the foregoing embodiments, and will not be further described in the scope of those skilled in the art.

The application client does not need to download the application and related operations, and does not need to update frequently, which brings convenience to the user, reduces maintenance costs, etc., and the user only needs to operate through the browser to implement the wearable device. Remote monitoring and operation.

The technical solution of the present application or the part that contributes to the prior art or all or part of the technical solution may be embodied in the form of a software product stored in a storage medium, including several instructions. All or part of the steps of the method of the various embodiments of the present application are performed by a computer device (which may be a personal computer, server, or network device, etc.) or a processor. The foregoing storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, and the like. .

The above description is only the embodiment of the present application, and thus does not limit the scope of the patent application, and the equivalent structure or equivalent process transformation made by using the specification and the drawings of the present application, or directly or indirectly applied to other related technologies. The fields are all included in the scope of patent protection of this application.

Claims

A data communication system based on a B/S architecture, characterized in that the data communication system comprises a client, a communication server, and a web server for connecting the client and the communication server, the web server is provided with an intermediate communication Component:

The browser of the client initiates an HTTP request to the intermediate communication component of the web server;

The intermediate communication component processes the HTTP request and establishes a Socket communication with the communication server;

The intermediate communication component transmits a Socket request corresponding to the HTTP request to the communication server by using a TCP/IP protocol;

The communication server processes the Socket request and returns corresponding result data to display the result data through a browser of the client.
The data communication system according to claim 1, wherein said intermediate communication component creates a socket upon establishment of said HTTP request initiated by said browser, and establishes a TCP/IP connection with said communication server If the connection fails, the information of the connection failure is returned to the front page of the browser, and if the connection is successful, the Socket request corresponding to the HTTP request is sent to the communication server.
The data communication system according to claim 2, wherein the intermediate communication component sets a timeout period for waiting for the Socket communication to be the first time, and receives result data returned by the communication server according to the Socket request, if If the result data returned by the communication server is not received within the second time period when the first time is not reached, the information that the data transmission failure is returned to the front page of the browser, if received at the first time The result data returned by the communication server is closed, and the format of the detection result data is valid. If the format is incorrect, the information of the response data abnormality is returned to the front page of the browser. If the format is correct, the format is returned. The resulting data is parsed and packaged into predetermined format data for transmission to the front end web page of the browser.
A data communication system according to any one of claims 1 to 3, wherein said communication The letter server is based on the Epoll communication model and runs on the Linux system. The communication server initializes the Socket communication parameters, establishes the listening Socket descriptor, initializes the Epoll communication model, and creates only the head node before processing the Socket request. Linking the list, initializing and starting the system timer that controls the heartbeat packet, calling the Epoll_waiting function, and waiting for the triggering of the client communication event in a blocking manner.
The data communication system according to claim 4, wherein when the new client initiates the TCP connection request, the Epoll_wait function of the communication server finds that the communication event to be processed is triggered to be equal to listening to the Socket descriptor. Retrieving a new Socket descriptor according to the Socket descriptor call accept function, and adding the intercepted Socket descriptor to the Epoll handle through the Epoll_ event registration function, to utilize the Socket descriptor and the established connection The new client performs two-way communication.
The data communication system according to any one of claims 1 to 3, wherein the webpage of the browser of the client adopts a JQuery framework, and communicates with the intermediate communication component through an AJAX engine, so that The web page implements an asynchronous update.
The data communication system according to claim 6, wherein the browser of the client uses the $.ajax() method to implement and set parameters of the request address, the request data, the request mode, and the timeout period, and obtains the user's When an HTTP request is initiated, if the browser's front-end webpage does not receive the return data within the timeout period, the current network abnormality is prompted. If the returned data is received within the timeout period, it is determined whether the data is a connection failure, and if , the server connection failure is prompted, if not, then it is determined whether the returned data is a data exception, and if so, the data return is abnormal. If not, it is determined whether the returned data is a timeout, and if so, the data is timed out waiting for the return data, if not, then The obtained result data is parsed and displayed on the browser web page.
A data communication method based on a B/S architecture, characterized in that the data communication method comprises:

The intermediate communication component of the web server obtains an HTTP request initiated by the client's browser;

The intermediate communication component processes the HTTP request and establishes a Socket communication with the communication server;

The intermediate communication component transmits a Socket request corresponding to the HTTP request to the communication server through a TCP/IP protocol.
The data communication method according to claim 8, wherein said intermediate communication component creates a socket upon establishment of said HTTP request initiated by said browser, and establishes a TCP/IP connection with said communication server If the connection fails, the information of the connection failure is returned to the front page of the browser, and if the connection is successful, the Socket request corresponding to the HTTP request is sent to the communication server.
The data communication method according to claim 9, wherein the intermediate communication component sets a timeout period for waiting for the Socket communication to be the first time, and receives result data returned by the communication server according to the Socket request, if If the result data returned by the communication server is not received within the second time period when the first time is not reached, the information that the data transmission failure is returned to the front page of the browser, if received at the first time The result data returned by the communication server is closed, and the format of the detection result data is valid. If the format is incorrect, the information of the response data abnormality is returned to the front page of the browser. If the format is correct, the format is returned. The resulting data is parsed and packaged into predetermined format data for transmission to the front end web page of the browser.
A web server for a data communication system based on a B/S architecture, characterized in that the data communication system includes a client, a communication server, and the web server is configured to connect the client and the communication server, The web server has an intermediate communication component:

The intermediate communication component acquires an HTTP request initiated by a browser of the client;

The intermediate communication component processes the HTTP request and establishes a Socket communication with the communication server;

The intermediate communication component transmits a Socket request corresponding to the HTTP request to the communication server through a TCP/IP protocol.
The web server according to claim 11, wherein the intermediate communication component creates a socket and establishes a TCP/IP connection with the communication server upon receiving the HTTP request initiated by the browser. If the connection fails, the information of the connection failure is returned to the front page of the browser. If the connection is successful, the Socket corresponding to the HTTP request is requested. Request to send to the communication server.
The web server according to claim 12, wherein the intermediate communication component sets a timeout period for waiting for the Socket communication to be the first time, and receives result data returned by the communication server according to the Socket request, if not If the result data returned by the communication server is not received within the second time period of the first time, the information that the data failure is returned is returned to the front page of the browser, and if the first time is received, The result data returned by the communication server is closed, the Socket communication is closed, and the format of the detection result data is valid. If the format is incorrect, the information in response to the data abnormality is returned to the front page of the browser. If the format is correct, the returned data is returned. The resulting data is parsed and packaged into predetermined format data for transmission to the front end web page of the browser.
A wearable device-based monitoring system, comprising: a wearable device, and a data communication system based on a B/S architecture according to any one of claims 1-7, the wearable The device establishes a network data connection with the communication server, and the client is configured to remotely monitor the wearable device:

The browser of the client initiates an HTTP request to the intermediate communication component of the web server when acquiring the operation of the user;

The intermediate communication component processes the HTTP request and establishes a Socket communication with the communication server;

The intermediate communication component transmits a Socket request corresponding to the HTTP request to the communication server by using a TCP/IP protocol;

The communication server processes the Socket request, acquires result data corresponding to the wearable device according to the Socket request, and returns the result data to be displayed by a browser of the client.