【正文】
es the context pages according to the screen size of the mobile device. It also filters the pages according to mobile devices and then browses the adopted content from the context server to the mobile web browser. The mobile context server reconfigures contents offered by the web server. Figure 1 The System Architecture B. Web Service Security Model Web service security can be applied at three levels : ? Platform/transportlevel (pointtopoint) security。 ? Messagelevel (endtoend) security. Each approach has different strengths and weaknesses. The choice of the approach is largely dependent on the characteristics of the architecture and platforms involved in the message exchange. This system focuses on platform and applicationlevel security, so the two security levels are described. (pointtopoint) security The transport channel between two endpoints (web service client and web service) can be used to provide pointtopoint security as illustrated in Figure 2. Figure 2 Platform/transportlevel security In the platformlevel model, the client sends an XML format request to the web server. The XML message is not encrypted by the client. When the message is transported in the transport channel, the work encrypts the entire data stream to make sure that the transport is secure. This system uses a tightly coupled Microsoft Windows operating system environment. The Inter Information Server (IIS) provides basic, integrated and certificate authentication. The web service inherits some of the authentication and authorization features. The Secure Sockets Layer (SSL) is used to provide message integrity and confidentiality. 2 .Applicationlevel security With applicationlevel security, the application controls security with custom security features (Figure 3). Figure 3 Applicationlevel security In the applicationlevel security model, for example, an application can use a custom SOAP header to pass user credentials to authenticate the user with each web service request. A mon approach is to pass a ticket (or user name or license) in the SOAP header. The application has the flexibility to generate its own principal object that contains roles. The application can optionally encrypt what it needs to, although this requires secure key storage and developers must have knowledge of the relevant cryptography APIs. An alternative technique uses SSL to provide confidentiality and integrity it with custom SOAP headers to perform authentication. The system uses the SOAP Toolkit by Microsoft, which provides support for inter security based on the IIS security infrastructure to implement the applicationlevel security model. C. The Implementation of the System The whole system was built using the Microsoft .NET framework and .NET pact framework. Server application was implemented by Microsoft based on C, the database was served by Microsoft SQL server 2021. The context server connected to the web server acted as IIS as the web server. The function modules of this system mainly consist of 5 parts: system management, food management, client management, food ordering management and finance management, as shown in Figure 4.