WO2011023020A1 - 客户端/服务端架构中服务端和客户端的业务执行方法及系统 - Google Patents
客户端/服务端架构中服务端和客户端的业务执行方法及系统 Download PDFInfo
- Publication number
- WO2011023020A1 WO2011023020A1 PCT/CN2010/073834 CN2010073834W WO2011023020A1 WO 2011023020 A1 WO2011023020 A1 WO 2011023020A1 CN 2010073834 W CN2010073834 W CN 2010073834W WO 2011023020 A1 WO2011023020 A1 WO 2011023020A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- user
- client
- server
- decision
- service execution
- Prior art date
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/16—Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
- H04L69/161—Implementation details of TCP/IP or UDP/IP stack architecture; Specification of modified or new header fields
- H04L69/162—Implementation details of TCP/IP or UDP/IP stack architecture; Specification of modified or new header fields involving adaptations of sockets based mechanisms
Definitions
- the present invention relates to inter-process communication technologies in the field of communication and computer software, and in particular to a client/server (Client/Server) , referred to as C/S), the service execution method and system of the server and the client.
- C/S client/server
- Background technique
- the C/S architecture known as the client and the client architecture. It is a software system architecture.
- the client and the client perform the business execution method: Once the client is started, it waits for the service execution request sent by the client at any time; the client is responsible for the interface display and User interaction, when the user needs to issue an operation request to the server to perform the service, the client sends a service execution request to the server according to the user request, and waits to receive the execution process information or the execution result information sent from the server; Responsible for receiving and executing the service execution request sent by the client, performing the service execution according to the service execution request, and feeding back the service execution result to the client after the execution is completed.
- the client can no longer impose a pre-emptive process on the service execution process of the server. Under normal circumstances, this does not affect the use of the C / S architecture to meet the client's business needs, but there are exceptions.
- the user may be required to perform the service through the client's thousand pre-servers. For example, the user may wish to determine the subsequent business execution behavior or execution process of the server according to different situations that occur after the server service is executed to a certain stage. . However, at present, the client cannot control the server during the execution of the task on the server.
- a main object of the present invention is to provide a service execution method and system for a server and a client in a C/S architecture, which are used to solve the problem that a user in the C/S architecture in the prior art cannot pass the client through the client.
- the execution behavior or process problem of the business is provided, which includes the following steps: When the server executes to a preset user decision point during the execution of the service, the service execution is interrupted and initiated to the client.
- the user decision request includes information requesting a user to determine a service execution behavior after the user decision point; after receiving the user decision information made by the client to the user decision request, performing the user decision decision information and the service execution Corresponding relationship between the rules, determining a service execution behavior corresponding to the received user decision information, and performing the service according to the determined service execution behavior.
- a service execution method of a client in a C/S architecture including the following steps: receiving a service execution request from a user and sending it to a server, requesting the server to start service execution; Receiving information from the server during the execution of the service, prompting the user to make a decision and waiting for the user to respond to the user's decision request when the information is a user decision request, the user decision request including information requesting the user to decide the subsequent service execution behavior; Receiving user decision information made by the user on the user decision request, the client sends the user decision information to the server.
- a service execution system for a server and a client in a C/S architecture
- the system comprising: a client service execution unit, configured to initiate a service execution request to the server, and receive a user from the server When making a request, the user is prompted to make a decision and wait for the user's response to the user's decision request, and the user's decision information made by the user to the user's decision request is sent to the server; the server service execution unit is used for receiving After the business execution request from the client starts executing the business, when executing to a preset user decision point during the execution of the business, the business execution is interrupted and a user decision request is initiated to the client, and the client makes a decision request to the user.
- FIG. 1 is a flow chart of a service execution method of a client in a C/S architecture according to an embodiment of the present invention
- FIG. 2 is a flowchart showing a service execution method of a client in a C/S architecture according to an embodiment of the present invention
- FIG. 3 is a structural diagram of a server service execution unit according to Embodiment 1 of the present invention
- FIG. 4 is a structural diagram of a client service execution unit according to Embodiment 1 of the present invention
- FIG. 6 is a flowchart of a method for executing a service of a client in a C/S architecture according to Embodiment 2 of the present invention.
- S 101 When the server executes a pre-set user decision point during the service execution process, the service execution is interrupted.
- the client initiates a user decision request, where the user decision request includes information requesting the user to determine the service execution behavior after the user decision point;
- S102 after receiving the user decision information made by the client to the user decision request, according to the user
- the correspondence between the decision decision information and the service execution rule determines the service execution behavior corresponding to the received user decision information, and executes the service according to the determined service execution behavior. As shown in FIG.
- the method for executing a service of a client in a C/S architecture includes the following steps: S201: Receive a service execution request from a user and send it to a client, requesting a service. Ending the service execution; S202, receiving information from the server during the execution of the service, prompting the user to make a decision and waiting for the response of the user to the user decision request, where the user decision request includes the requesting user Determining information about the execution behavior of the subsequent service; S203: Receive user decision information made by the user in response to the user decision request, and the client sends the user decision information to the server.
- the client user needs to initiate a service execution request to the server actively; after the server starts, the event loop is used to monitor the information from the client, and the service is started when the information is executed for the service; In business The business execution status information is fed back to the client during the execution to the end.
- the client receives the service execution status information from the server, it returns to the user through the interface.
- the service execution system of the client and the client in the C/S architecture provided by the embodiment of the present invention includes: a client service execution unit, configured to initiate a service execution request to the server, when receiving a user decision request from the server Prompting the user to make a decision and waiting for the user's response to the user's decision request, and sending the user decision information made by the user to the user decision request to the server; the server service execution unit, for receiving the client from the client After the service execution request starts to execute the service, when the user execution process reaches the preset user decision point, the service execution is interrupted and the user decision request is initiated to the client, and the user decision information made by the client to the user decision request is received.
- FIG. 3 is a structural diagram of a server service execution unit in the embodiment, where the server service execution unit includes: 301, a decision point setting unit, configured to set a user that needs a user to make a decision during a service execution process.
- a decision point initiating unit configured to: when the server performs a pre-set user decision point during the execution of the service, interrupting the service execution and initiating a user decision request to the client, where the user decision request includes requesting the user to make a decision
- the information about the service execution behavior of the user after the decision point 303, the execution unit, configured to determine, according to the corresponding relationship between the user decision decision information and the service execution rule, after receiving the user decision information made by the client to the user decision request The service execution behavior corresponding to the received user decision information is performed, and the service is executed according to the determined service execution behavior.
- the client service execution unit includes: a service execution request unit 401, configured to initiate a service execution request to the server according to the user requirement, requesting a service request
- the receiving unit 402 is configured to receive information from the server during the execution of the service; the requesting determining unit 403 is configured to prompt the user to make a decision and wait for the user to the user when the received information is a user decision request
- the response unit 404 is configured to send the user decision information obtained by the user to respond to the user decision request to the server.
- the user decision point may be set by the server according to the service execution condition or configured by the client, if the server is configured according to the service execution condition, such as setting the user decision when detecting that the service execution has a security risk.
- Point requesting the user to decide whether the subsequent service is executed, this method is more flexible; if the user determines the user decision point of the business execution process, it can better meet the customer's needs, and the flexibility is relatively poor.
- the user decision request may include thousands of different flag bit information requesting the user to make a selection, and different flag bit information corresponds to different service execution behaviors in the service execution rule; the user decision information is the selected one of the flag bit information.
- the server can be based on The received flag bit information determines the business execution behavior after the user's decision point and executes according to the business execution rule.
- the user decision request is not limited to the above-mentioned form, and may be any other form of the delivery requesting user to determine the subsequent service execution behavior.
- the method and system proposed by the embodiments of the present invention are applicable to the C/S architecture, regardless of the C/S architecture.
- a network system, or a software system having a C/S architecture is applicable to all embodiments of the present invention.
- the server and the client use different types of messages in the program to represent the service execution request, the user decision information, and the service.
- Execution status information and user decision requests are a classification, including: A1, a service execution request message, which indicates a service execution request, that is, what service the user wants the server to perform; A2
- the user decides the message, and the message represents the user decision information, that is, the response of the user to the user decision request sent by the server.
- the message sent by the server to the client is also classified, and includes: B1, a service execution status message, where the message indicates service execution status information, that is, the service execution result or the middle of the service execution performed by the server according to the service execution request sent by the user.
- the feedback of the status information can be used to feedback whether the user's business execution request is successfully executed or executed.
- the business execution status message can be further divided into prompt messages, warning messages, error messages, progress messages, and execution for different services.
- Requesting a corresponding event response message; B2 a user decision request message, the message indicating a user decision request, that is, when the server executes to a preset user decision point, the user is required to decide a subsequent service execution action or process.
- the client and the server communicate the above different types of messages through a message channel, and the message channel may be a socket, a pipe, a message queue, or another carrier for inter-process communication.
- So-called sockets also commonly referred to as “sockets” are used to describe IP addresses and ports and are handles to a communication chain.
- Applications typically make requests to the network or respond to network requests via “sockets.”
- the client randomly requests a socket, and the network system assigns a socket number (hereinafter referred to as client_sock); the client has a globally recognized socket (hereinafter referred to as server_sock), and any client can send a connection request to it.
- server_sock globally recognized socket
- the port can be arbitrarily specified, waiting for the client to connect to the request, after the connection with the client, the session is generated; after completing the session, close the connection.
- the client uses client_sock to make a connection request to the server port on the network. Once the connection is successful, the session is opened. After the session is completed, the client sock is closed.
- a pipe is a shared memory area used for interprocess communication. One process writes information to the pipe, while another process reads information from the pipe.
- a message is a unit of data that is transferred between two computers. The message is sent to the queue. Message queue is a container for saving messages during the transmission of messages. The main purpose of message queues is to provide routing and ensure the delivery of messages.
- the message structure sent by the client to the server and the message structure sent by the server to the client may be separately defined or unified into one structure.
- the server and the client utilize event loops in the program for message supervision.
- the client uses the third event loop to monitor the message from the user indicating the service execution request and the message indicating the user decision information, that is, the third event loop monitors the user event on the client interface; the fourth event loop is used to monitor the server from the server.
- a message indicating a user's decision request and a message indicating service execution status information, that is, the fourth event loop is a monitoring message channel.
- the fourth event loop of the client monitoring message channel is referred to as CL1. Since the event loop of the client not only monitors the interface user event but also monitors the message channel, which involves the fusion of the third event and the fourth event loop, in this embodiment, the third event loop is used as the main event loop, and the event is used.
- the driving mode of the driver, the fourth event cycle uses the method of timed query.
- the first event loop is used to monitor the message from the client to indicate the service execution request.
- the layer of the message channel monitoring of the server is called SL1
- the server executes the request message according to the received different service.
- the different processing functions are called to perform different business activities or processes.
- the second event loop is used to monitor the message from the client to represent the user's decision information.
- the layer monitoring of the monthly server is called SL2.
- the service execution method of the client and the client, the SL1 continuously monitors the message channel between the client and the client, and after the message indicating the service execution request is monitored, the server starts the service execution.
- Event loop SL2 monitoring the message channel; the client uses the fourth event loop to monitor the user decision request message sent by the server, pops up the query interface, waits for the user response; the third event loop of the client captures the user response (user decision message) When the message loop is sent to the server, the user decides the message; after the event loop SL2 of the server monitors the user decision message, the server executes the corresponding service according to the rule according to the user decision information, and exits and destroys the event loop SL2, and restores Event loop SL1. Waiting for the service execution request message sent by the client.
- the event loop SL1 or the event loop SL2 loop of the server may receive all the messages sent by the client to the server through the message channel, but here, the event loop SL1 is designed to receive only the service execution request message. If the user decision message is received and discarded directly, the event loop SL1 is always present until the server process terminates. In this embodiment, the event loop SL2 is designed to receive only the user decision message. If the service execution request message is received, it is directly discarded. The event loop SL2 is quit and destroyed after the server receives the user decision message. Through the method in this embodiment, the user can pre-empt or influence the business execution behavior or process of the client.
- the monthly service client sends a user decision request message to the client when executing to the user decision point, and simultaneously initiates an event loop at the user decision point to monitor the message channel. Waiting for the user to decide the message, achieving the purpose of the client's pre-emptive or influencing the business execution behavior or process of the server.
- the foregoing method of this embodiment is not limited to an operating system platform or a use environment, and the method may be used as long as the operating system supports inter-process communication; nor is it limited to a one-to-one C/S architecture, and is also applicable to Different client business execution requests start a different-to-one C/S architecture that can be extended by different threads to service.
- the service execution method of the client and the client in the C/S architecture taking the package installation service execution on the linux platform smart phone as an example, all the software packages are placed on a network server.
- the package management program on the mobile terminal downloads this configuration file to obtain all software.
- the package management program on the mobile terminal is based on the C/S architecture.
- the client graphical interface is based on the gtk+ development package, and the server is implemented in C language.
- the carrier of the message channel between the client and the server selects the socket.
- the client and the server use a one-to-one model, but those skilled in the art should understand that the present invention is not limited to the above-described features of business execution, and the C/S architecture is not limited to the one-to-one model.
- the carrier of the message channel is also not limited to the socket mode.
- the above MD5 is used to ensure information transmission. MD5 is most widely used for password authentication and key identification of various software. The popular saying is that the serial number is complete and consistent. It is often seen in a software information on some software download sites that its MD5 value, its role is that after downloading the software, you can use the special software (such as Windows MD5 Check, etc.) to do a MD5 school on the downloaded files. To ensure that the files obtained are the same as the files provided by the site.
- the service execution method of the client in the C/S architecture of this embodiment includes the following steps: S501: Defining a message structure used for transmitting a message between a client and a server.
- the message sent by the client to the server and the message sent by the server to the client are used in the same structure.
- the program is as follows: typedef struct ⁇
- Type t type Context t content; ⁇ Message_t;
- the structure has two member variables, type is an enumeration variable, indicating the classification of the message, specifically, when the client sends a message to the server, it indicates the service execution request.
- Message user decision message;
- the server sends a message to the client, it indicates a user decision request message, a service execution status message, and the like.
- Content is a structure that represents the specific content carried by the message.
- the socket channel is created, and the client_sock is obtained, and the client sock is connected to the server, so that the message channel between the client and the server is established.
- the third event loop is defined to implement interface monitoring, so the client can obtain the user action (that is, capture the service execution request message and the user decision message) through the third event loop of the monitoring interface, and send the message to the server;
- the client adds a timer, defines to use the fourth event loop to implement data reading on the socket port, and the fourth event loop uses a timed reading method to monitor the fourth event loop of the message channel, and specifically uses the timing reading
- the sample code is: gtk timeout add (500, get_pending_message, NULL)
- the function of the get_pending_message function is to read the message sent by the client on the socket (including the user decision request message and the service execution status message), and according to The classification of the message invokes different processing functions. For example, after monitoring the user decision request message, the pop-up interface requests the user to make a decision, and when the service execution status message is monitored, the user feeds back through the interface;
- the service execution request information is captured through the third event loop, and the service execution request information is sent to the network server.
- the network server serves as the server, and the mobile phone acts as the client, and simultaneously uses the fourth event loop to monitor the message channel.
- the service execution request is a message for requesting installation.
- the mobile phone sends a message requesting installation to the network server, and the network server downloads the software package to the local device after receiving the request. (ie mobile phone)
- the user interface acts as the client, and the package installation program in the background is the server;
- the service execution method of the server in the C/S architecture of this embodiment includes the following steps:
- the message structure used to transmit the message between the client and the server is defined.
- the message sent by the client to the server and the message sent by the server to the client are used in the same structure.
- Messagej it is specifically as described in the above step S501.
- the socket channel is established by a name that is well known or can be found by the client.
- the classification calls different processing functions; here specifically defines a first event loop to monitor a service execution request message from the client, and a second event loop to monitor a user decision message from the client;
- the service execution request message is captured through the first event loop, and the service execution request message starts to perform the service execution; for example, before the software package is not installed,
- the mobile phone acts as the client, and the network server acts as the server.
- the network server After receiving the message from the mobile phone requesting the installation, the network server will start executing the package from the server.
- the network server downloads the local service, and downloads the software package from the network server to the local area. Since the package management program on the mobile terminal is based on the C/S architecture, the user interface acts as a client during the installation process of the software package. End, the background package installer is the server;
- the package installation program in the background is the MD5 value of the server detection package is consistent with the configuration file on the server. If they are consistent, the package is not included. If the three parties have changed, you can install it with confidence; if it is inconsistent, it means that the software package may be modified by a third party, there is a security risk.
- the service execution of the server requires user decision, and the server sends a user decision request message to the client.
- the server detects the security of the software package installation according to the service execution situation. If there is a security risk, the user decision point is set to interrupt the service and request the user to decide whether to install. If there is no security risk, the user decision point is not interrupted. And install directly.
- the user decision request includes two different flag bit information requesting the user to make a selection, where one flag bit information corresponds to the service execution behavior of the continuation software package in the service execution rule, and another flag bit information is in the service execution rule. Corresponding to the business execution behavior of not installing the software package;
- the second event loop monitors that the server_sock has data, reads and converts into a Message_t message structure, and parses the message content to obtain user decision information.
- the user decision information is the selected one of the flag bit information, and the server end According to the received user decision, the subsequent business execution behavior is determined, and the second event loop is exited and returned to the first event loop.
- the process performed by the client's 1000 pre-server ends.
- steps S607 and S608 are repeated.
- the server may return service execution status information to the client during the execution of the service.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer And Data Communications (AREA)
- Information Transfer Between Computers (AREA)
- Stored Programmes (AREA)
Description
客户端 /月良务端架构中月良务端和客户端的业务执行方法及系统 技术领域 本发明涉及通信和计算机软件领域的进程间通信技术， 具体涉及一种客 户端 /服务端（Client/Server, 简称为 C/S )架构中服务端和客户端的业务执行 方法及系统。 背景技术
C/S 架构， 即被所熟知的客户端和月艮务端架构。 它是一种软件系统体系 结构。 通常的， 在 C/S架构中， 客户端与月艮务端的业务执行方法为： 月艮务端一 旦被启动， 就随时等待响应客户端发来的业务执行请求； 客户端负责界面显 示和与用户交互， 当用户需要对服务端发出操作请求来执行业务时， 客户端 根据用户请求向服务端其发出业务执行请求， 并等待接收从服务端发来的执 行过程信息或执行结果信息； 服务端负责接收和执行客户端发来的业务执行 请求， 根据业务执行请求进行业务执行， 执行完成后向客户端反馈业务执行 结果。 一般来说， 月艮务端在才艮据接收的业务执行请求执行业务的过程中， 客户 端无法再对艮务端的业务执行过程施加千预。 在通常情况下， 这并不影响使 用 C/S架构来满足客户端的业务需求， 但也有例外。 在一些软件需求中， 可 能会要求用户可以通过客户端千预服务端的业务执行， 比如： 用户可能希望 根据服务端业务执行到一定阶段后出现的不同情况决定服务端后续的业务执 行行为或执行流程。 但是目前， 在服务端在执行任务的过程中， 客户端还不能对服务端进行 控制。 发明内容 本发明的主要目的在于提供一种 C/S架构中服务端和客户端的业务执行 方法及系统， 用以解决现有技术中 C/S架构中用户不能根据需求通过客户端 千预或影响月艮务端业务执行行为或流程问题。
据此， 一方面， 提供了一种 C/S架构中服务端的业务执行方法， 包括以 下步骤： 服务端在业务执行过程中执行到预先设置的用户决策点时， 中断业务执 行并向客户端发起用户决策请求， 所述用户决策请求包含请求用户决策所述 用户决策点后业务执行行为的信息； 在接收到客户端对用户决策请求所作出的用户决策信息后， 根据用户决 策决策信息与业务执行规则的对应关系， 确定出接收的用户决策信息对应的 业务执行行为， 并按该确定出的业务执行行为执行业务。 另一方面， 还还提供了一种 C/S架构中客户端的业务执行方法， 包括以 下步 4聚： 接收来自用户的业务执行请求并将其发送到服务端， 请求服务端开始业 务执行； 在业务执行过程中接收来自服务端的信息， 在所述信息为用户决策请求 时， 提示用户需要决策并等待用户对用户决策请求的响应， 所述用户决策请 求包含请求用户决策后续业务执行行为的信息； 接收用户对所述用户决策请求所作出的用户决策信息， 客户端将该用户 决策信息发送到服务端。 又一方面， 还提供了一种 C/S架构中服务端和客户端的业务执行系统， 该系统包括： 客户端业务执行单元， 用于向服务端发起业务执行请求， 在接收到来自 服务端的用户决策请求时， 提示用户需要决策并等待用户对用户决策请求的 响应， 并将用户对所述用户决策请求所作出的用户决策信息发送到月艮务端； 服务端业务执行单元， 用于在接收来自客户端的业务执行请求后开始执 行业务， 在业务执行过程中执行到预先设置的用户决策点时， 中断业务执行 并向客户端发起用户决策请求， 在接收到客户端对用户决策请求所作出的用 户决策信息后， 根据用户决策决策信息确定用户决策点后的业务执行行为。 通过本发明， 釆用了服务端的业务执行流程中设置用户决策点， 用户可 以在用户决策点进行决策， 根据该决策来改变后续的业务执行行为或流程。
实现了客户端千预或影响服务端的业务执行行为或流程的目的。 附图说明 图 1为才艮据本发明实施例的 C/S架构中月艮务端的业务执行方法流程图； 图 2为才艮据本发明实施例的 C/S架构中客户端的业务执行方法流程图； 图 3为本发明实施例一中服务端业务执行单元的结构图； 图 4为本发明实施例一中客户端业务执行单元的结构图； 图 5为本发明实施例二中 C/S架构中客户端的业务执行方法流程图； 图 6为本发明实施例二中 C/S架构中月艮务端的业务执行方法流程图。 具体实施方式 下文中将参考附图并结合实施例来详细说明本发明。 需要说明的是， 在 不冲突的情况下， 本申请中的实施例及实施例中的特征可以相互组合。 本发明实施例所提供 C/S架构中服务端的业务执行方法， 如图 1 , 包括 如下步骤： S 101 ,服务端在业务执行过程中执行到预先设置的用户决策点时， 中断业务执行并向客户端发起用户决策请求， 所述用户决策请求包含请求用 户决策所述用户决策点后业务执行行为的信息； S 102, 在接收到客户端对用 户决策请求所作出的用户决策信息后， 根据用户决策决策信息与业务执行规 则的对应关系， 确定出接收的用户决策信息对应的业务执行行为， 并按该确 定出的业务执行行为执行业务。 如图 2所示， 为本发明实施例所提供的 C/S架构中客户端的业务执行方 法， 包括如下步骤： S201 , 接收来自用户的业务执行请求并将其发送到月艮务 端， 请求服务端开始业务执行； S202, 在业务执行过程中接收来自服务端的 信息， 在所述信息为用户决策请求时， 提示用户需要决策并等待用户对用户 决策请求的响应， 所述用户决策请求包含请求用户决策后续业务执行行为的 信息； S203 , 接收用户对所述用户决策请求响应所作出的用户决策信息， 客 户端将该用户决策信息发送到服务端。 由于釆用 C/S架构， 优选客户端用户 需求主动向服务端发起业务执行请求； 服务端启动后利用事件循环来监控来 自客户端的信息， 在该信息为业务执行请求时开始业务执行； 服务端在业务
执行开始到结束过程中反馈业务执行状态信息到客户端。 客户端接收到在来 自服务端的业务执行状态信息时， 通过界面返回给用户。 本发明实施例所提供的 C/S 架构中月艮务端和客户端的业务执行系统包 括： 客户端业务执行单元， 用于向服务端发起业务执行请求， 在接收到来自 服务端的用户决策请求时， 提示用户需要决策并等待用户对用户决策请求的 响应， 并将用户对所述用户决策请求所作出的用户决策信息发送到月艮务端； 服务端业务执行单元， 用于在接收来自客户端的业务执行请求后开始执行业 务， 在业务执行过程中执行到预先设置的用户决策点时， 中断业务执行并向 客户端发起用户决策请求， 在接收到客户端对用户决策请求所作出的用户决 策信息后， 根据用户决策决策信息确定用户决策点后的业务执行行为。 如图 3所示为本实施例中服务端业务执行单元的结构图， 该服务端业务 执行单元包括： 301 , 决策点设置单元， 用于设置服务端在业务执行过程中 需要用户进行决策的用户决策点； 302 , 决策请求发起单元， 用于服务端在 业务执行过程中执行到预先设置的用户决策点时， 中断业务执行并向客户端 发起用户决策请求， 所述用户决策请求包含请求用户决策所述用户决策点后 业务执行行为的信息； 303 , 执行单元， 用于在接收到客户端对用户决策请 求所作出的用户决策信息后， 根据用户决策决策信息与业务执行规则的对应 关系， 确定出接收的用户决策信息对应的业务执行行为， 并按该确定出的业 务执行行为执行业务。 如图 4所示为本实施例中客户端业务执行单元的结构 图， 该客户端业务执行单元包括： 业务执行请求单元 401 , 用于根据用户需 求向 艮务端发起业务执行请求， 请求艮务端开始业务执行； 接收单元 402 , 用于在业务执行过程中接收来自月艮务端的信息； 请求决策单元 403 , 用于在 接收的信息为用户决策请求时， 提示用户需要决策并等待用户对用户决策请 求的响应； 发送单元 404 , 用于将用户对所述用户决策请求响应后所得到用 户决策信息发送到月艮务端。 优选地， 用户决策点可以由服务端根据业务执行情况设定或由客户端配 置， 若由 艮务端才艮据业务执行情况设定， 如在检测到业务执行存在安全风险 时设定用户决策点， 请求用户决策后续的业务是否执行， 这种方式灵活性比 较高； 若由客户端配置业务执行流程的用户决策点， 则更能满足客户的需要， 灵活性相对较差一些。 上述用户决策请求可以包含请求用户作出选择的若千 个不同的标志位信息， 不同的标志位信息在业务执行规则中对应不同的业务 执行行为； 用户决策信息为所选择的一个标志位信息。 因此服务端可以根据
接收的标志位信息按业务执行规则来确定用户决策点后的业务执行行为并执 行。 当然， 用户决策请求不限于上述形式， 可以是传递请求用户决策后续业 务执行行为的任何其它形式， 本发明实施例所提出的方法及系统适用于 C/S 架构， 不管是具有 C/S架构的网络系统， 还是具有 C/S架构的软件系统， 本 发明实施例均适用。 依照本发明的实施例一， C/S架构中客户端和月艮务端的业务执行方法中， 服务端和客户在程序中釆用不同类型的消息来表示上述业务执行请求、 用户 决策信息、 业务执行状态信息及用户决策请求。 在客户端和服务端的业务执行过程中， 客户端向服务端发送的消息是分 类， 包括： A1 , 业务执行请求消息， 该消息表示业务执行请求， 即表示用户 希望服务端来执行什么业务； A2, 用户决策消息， 该消息表示用户决策信息， 即表示用户对月艮务端发送的用户决策请求的响应。 服务端向客户端发送的消息也是分类的， 包括： B1 , 业务执行状态消息， 该消息表示业务执行状态信息， 即表示服务端在根据用户发送的业务执行请 求进行业务执行的业务执行结果或中间状态信息的反馈， 可以反馈用户的业 务执行请求是否成功执行或执行到什么阶段； 业务执行状态消息还可以更细 化的分为提示消息、 警告消息、 错误消息、 进度消息和针对不同的业务执行 请求对应的事件响应消息； B2 , 用户决策请求消息， 该消息表示用户决策请 求， 即表示服务端执行到预先设置的用户决策点时， 需要用户来决策后续的 业务执行动作或流程。 本实施例中客户端和服务端之间通过消息通道来传递上述不同类型的消 息， 消息通道可以是 socket, 管道、 消息队列或其他进程间通信的载体。 所谓 socket通常也称作"套接字"， 用于描述 IP地址和端口， 是一个通信 链的句柄。 应用程序通常通过"套接字 "向网络发出请求或者应答网络请求。 客户端随机申请一个 socket , 网络系统为之分配一个 socket号 （在下文中称 为 client_sock ); 月艮务端拥有全局公认的 socket (在下文中称为 server_sock ), 任何客户端都可以向它发出连接请求和信息请求。 具体为： 服务端， 使用 server_sock监听指定的端口， 端口可以随意指定， 等待客户端连接请求， 与 客户端连接后，会话产生；在完成会话后，关闭连接。客户端，使用 client_sock 对网络上服务端的端口发出连接请求， 一旦连接成功， 打开会话； 会话完成 后, 关闭 client sock。
管道 （pipe ) 是用于进程间通信的共享内存区域。 一个进程向管道写入 信息， 而另外一个进程从管道读取信息。 消息是在两台计算机间传送的数据单位。 消息被发送到队列中。 消息队 列是在消息的传输过程中保存消息的容器， 消息队列主要目的是提供路由并 保证消息的传递。 本实施例中客户端向服务端发送的消息结构和服务端向客户端发送的消 息结构可以单独定义或是统一到一种结构中。 本实施例中服务端和客户端在程序中利用事件循环来进行消息监管。 客 户端利用第三事件循环监控来自用户的表示业务执行请求的消息及表示用户 决策信息的消息， 即第三事件循环监控客户端端界面上的用户事件； 第四事 件循环用于监控来自服务端的表示用户决策请求的消息及表示业务执行状态 信息的消息， 即第四事件循环是监控消息通道的。 本实施例中将客户端监控 消息通道的第四事件循环称为 CL1。 由于客户端的事件循环既要监控界面用 户事件， 又要监控消息通道， 涉及到第三事件和第四事件循环的融合问题， 本实施例中釆用第三事件循环充当主事件循环， 釆用事件驱动的监控方式， 第四事件循环釆用定时查询的方式。 在服务端，第一事件循环用于监控来自客户端表示业务执行请求的消息， 本实施例中将服务端的这层消息通道监控称为 SL1 , 服务端根据接收到的不 同的业务执行请求消息，调用不同的处理函数，执行不同的业务行为或流程； 第二事件循环用于监控来自客户端表示用户决策信息的消息， 本实施例中将 月艮务端这层监控称为 SL2。在 C/S架构中月艮务端和客户端的业务执行方法中， SL1持续循环监控月艮务端与客户端间的消息通道， 在监控到表示业务执行请 求的消息后服务端开始业务执行，在业务执行过程中在执行到用户决策点时， 发现需要用户参与决策， 中断业务执行并向客户端发起用户决策请求消息， 等待客户端对用户决策请求的响应， 同时将事件循环 SL1阻塞并开启事件循 环 SL2 ,监控消息通道； 客户端利用第四事件循环监控到服务端发来的用户 决策请求消息后， 弹出询问界面， 等待用户响应； 客户端的第三事件循环捕 捉到用户响应 （用户决策消息） 时， 通过消息通道向服务端发送用户决策消 息； 服务端的事件循环 SL2监控到用户决策消息后， 服务端根据用户决策信 息按所述规则执行相应的业务， 并退出和销毁事件循环 SL2, 恢复事件循环 SL1。 等待客户端发来的业务执行请求消息。
本实施例中服务端的事件循环 SL1或事件循环 SL2循环原则上可以接收 客户端所有通过消息通道发到月艮务端的消息， 但在此处， 事件循环 SL1被设 计成只接收业务执行请求消息的， 如果收到用户决策消息， 直接丢弃， 事件 循环 SL1是一直存在的， 直到服务端进程终止。 本实施例事件循环 SL2被设 计成只接收用户决策消息的， 如果收到业务执行请求消息， 直接丢弃， 事件 循环 SL2在服务端收到用户决策消息后， 会被退出和销毁。 通过本实施例中的方法用户通过客户端可以千预或影响月艮务端的业务执 行行为或流程。 月艮务端在才艮据业务执行请求来进行业务执行的过程中， 当执 行到用户决策点时， 向客户端发送用户决策请求消息， 同时在用户决策点起 一事件循环， 监控消息通道， 等待用户决策消息， 实现了客户端千预或影响 服务端的业务执行行为或流程的目的。 本实施例的上述方法并不限于操作系统平台或使用环境， 只要操作系统 支持进程间通信， 均可使用该方法； 也不局限于一对一 C/S架构， 也适用于 通过在服务端对不同的客户端业务执行请求启动不同的线程来服务即可扩展 的多对一 C/S架构。 依照本发明的实施例二， C/S架构中客户端和月艮务端的业务执行方法中， 以 linux平台智能手机上软件包安装业务执行为例， 所有软件包被放置于一 网络服务器上， 并有一配置文件表明所有软件的相关信息， 包括软件包名、 版本号、 MD5 ( Message-digest Algorithm 5 , 信息 -摘要算法）值等， 手机终 端上的包管理程序会下载这个配置文件获得所有软件包信息。 手机终端上的 包管理程序是基于 C/S架构的， 客户端图形界面基于 gtk+开发包， 服务端釆 用 C语言实现， 客户端和服务端之间的消息通道的载体选用 socket。 客户端 和服务端釆用一对一模型， 但本领域技术人员应该明白本发明并不限于上述 特点业务执行， C/S 架构也不局限于一对一模型。 消息通道的载体也不局限 于 socket方式。 上述 MD5用于确保信息传输。 MD5最广泛被用于各种软件的密码认证 和钥匙识别上。 通俗的讲就是所说的序列号完整一致。 常常在某些软件下载 站点的某软件信息中看到其 MD5值， 它的作用就在于可以在下载该软件后， 对下载回来的文件用专门的软件 (如 Windows MD5 Check等）做一次 MD5 校验， 以确保获得的文件与该站点提供的文件为同一文件。 如图 5所示，本实施例 C/S架构中客户端的业务执行方法包括以下步骤：
S501: 定义客户端和月艮务端之间传递消息所釆用的消息结构体, 本实施例釆用客户端向服务端发送的消息和服务端向客户端发送的消息 釆用相同结构的原则， 统一为 Message_t , 程序如下： typedef struct {
Type t type; Context t content; }Message_t; 该结构有两个成员变量， type是一个枚举变量， 表示消息的分类， 具体 来说就是， 当客户端向服务端发送消息时， 表示业务执行请求消息、 用户决 策消息； 当服务端向客户端发送消息时， 表示用户决策请求消息、 业务执行 状态消息等。 content是一个结构体， 表示消息携带的具体内容。
S502, 客户端启动后， 创建 socket通道， 得到 client_sock, client sock 连接到月艮务端， 这样客户端和月艮务端之间的消息通道就建立了。 S503 , 定义第三事件循环实现界面监控， 因此客户端可以通过监控界面 的第三事件循环，获得用户动作（即捕获业务执行请求消息和用户决策消息）， 发送到服务端；
S504, 客户端添加定时器， 定义利用第四事件循环实现 socket端口上的 数据读取， 第四事件循环釆用定时读取的方法， 监控消息通道的第四事件循 环， 具体釆用定时读取的方法， 示例代码是： gtk timeout add (500, get_pending_message , NULL) , get_pending_message函数的功能是读取 socket上月艮务端发来的消息（包 括用户决策请求消息和业务执行状态消息），并根据消息的分类调用不同的处 理函数， 如在监控到用户决策请求消息后， 弹出界面请求用户作出决策， 在 监控到业务执行状态消息时， 通过界面反馈给用户；
S505 , 在上述步骤的基础上， 当客户端的用户有某种特定的需求时， 首
先通过第三事件循环捕获业务执行请求信息， 并将该业务执行请求信息发送 到网络服务器， 此时， 网络服务器作为服务端， 手机作为客户端， 同时利用 第四事件循环监控消息通道， 对于本实施例中业务执行请求为请求安装的消 息， 当用户在手机选中一软件包， 请求网络服务器安装时， 手机向网络服务 器发送请求安装的消息，网络服务器接收到该请求后将软件包下载到本地（即 手机） 开始安装时， 由于手机终端上的包管理程序是基于 C/S架构的， 所以 在软件包的安装过程中， 用户界面作为客户端，后台的包安装程序为服务端；
S506, 在第四事件循环监控到用户决策请求消息后， 弹出对话框或字符 界面请求用户决策， 利用第三事件循环获得用户决策信息后发送到服务端； S507, 在第四事件循环监控到业务执行状态消息后， 通过界面反馈给用 户。 如反馈下载成功或下载失败的业务执行结果给用户。 如图 6所示，本实施例 C/S架构中服务端的业务执行方法包括以下步骤：
5601 , 定义客户端和服务端之间传递消息所釆用的消息结构体， 本实施 例釆用客户端向服务端发送的消息和服务端向客户端发送的消息釆用相同结 构的原则， 统一为 Messagej, 具体同上述步骤 S501中所述。
5602 , 启动月艮务端后， 以一个众所周知或客户端可以查到的名字建立 socket通道。
5603 , 绑定并侦听步骤 S602建立的 socket通道；
5604 , 在侦听客户端的连接请求后， 得到一个连接后的 socket 标识 server—sock;
5605 , 定义利用事件循环来监控 server_sock, 这里事件循环的示例代码 是通过一个 while(wait_message())循环实现的， wait—message函数的功能是读 取 socket上客户端发来的消息并根据消息的分类调用不同的处理函数； 这里 具体定义第一事件循环监控来自客户端的业务执行请求消息， 定义第二事件 循环监控来自客户端的用户决策消息；
5606, 在上述步骤的基础上， 当客户端的用户有某种特定的需求时， 首 先通过第一事件循环捕获业务执行请求消息， 居业务执行请求消息开始业 务执行； 如在未安装软件包之前， 手机作为客户端， 网络服务器作为服务端， 网络服务器接收到来自手机的请求安装的消息后， 会开始执行把该软件包从
网络服务器下载到本地的业务， 将软件包从网络服务器下载到本地后开始安 装， 由于手机终端上的包管理程序是基于 C/S架构的， 所以在软件包的安装 过程中， 用户界面作为客户端， 后台的包安装程序为服务端；
5607, 在执行到用户决策点时， 暂时中断业务执行， 即将第一事件循环 挂起， 发送用户决策请求到客户端， 开启第二事件循环来监控来自客户端的 用户决策信息， 如在将软件包从网络服务器下载到本地后开始安装后， 后台 的包安装程序作为 艮务端检测软件包的 MD5值是否与网络艮务器上配置文 件中的是否一致， 如果一致， 表示该软件包没有被第三方改动过， 可以放心 安装； 如果不一致， 表示该软件包可能被第三方改动过， 存在安全风险， 这 时服务端的业务执行需要用户决策，服务端发送用户决策请求消息到客户端， 同时在此处调用 wait_message函数， 开启第二事件循环， 等待用户响应。 本 实施例中服务端根据业务执行情况， 检测软件包安装的安全， 若存在安全风 险， 则设置用户决策点中断业务并请求用户决策是否安装，若没有安全风险， 则不设置用户决策点中断业务而直接进行安装。 本实施例中用户决策请求包 含请求用户作出选择的两个不同的标志位信息， 其中一个标志位信息在业务 执行规则中对应继续软件包的业务执行行为， 另一个标志位信息在业务执行 规则中对应不进行软件包安装的业务执行行为；
5608 , 在第二事件循环监控到 server_sock 有数据时， 读取并转化为 Message_t 消息结构， 解析消息内容得到用户决策信息， 在本实施例中用户 决策信息为所选择的一个标志位信息， 服务端根据收到的用户决策， 确定后 续的业务执行行为， 并退出第二事件循环， 重新回到第一事件循环中。 至此， 本次客户端千预服务端执行的流程结束。当再需要客户端千预服务端执行时， 重复步骤 S607和 S608。 上述服务端在业务执行过程中， 可以返回业务执行状态信息到客户端。 显然， 本领域的技术人员可以对本发明进行各种改动和变型而不脱离本 发明的精神和范围。 这样， 倘若本发明的这些修改和变型属于本发明权利要 求及其等同技术的范围之内， 则本发明也意图包含这些改动和变型在内。
Claims
1. 一种客户端 艮务端架构中月艮务端的业务执行方法， 其特征在于， 包括： 服务端在业务执行过程中执行到预先设置的用户决策点时， 中断业 务执行并向客户端发起用户决策请求， 所述用户决策请求包含请求用户 决策所述用户决策点后业务执行行为的信息；
在接收到所述客户端对用户决策请求所作出的用户决策信息后， 根 据用户决策决策信息与业务执行规则的对应关系， 确定出接收的用户决 策信息对应的业务执行行为， 并按该确定出的业务执行行为执行业务。
2. 根据权利要求 1所述的方法， 其特征在于，
所述用户决策请求包含请求用户作出选择的不同的标志位信息， 不 同的标志位信息在业务执行规则中对应不同的业务执行行为；
所述用户决策信息为所选择的一个标志位信息。
3. 根据权利要求 1或 2所述的方法， 其特征在于，
所述用户决策点由所述月艮务端才艮据业务执行情况设定或由所述客户 端配置。
4. 如权利要求 1所述的方法， 其特征在于，
该方法应用于手机上 C/S架构软件包的安装， 在软件包的安装过程 中， 用户界面作为所述客户端， 后台的软件包安装程序为所述服务端； 所述服务端在软件包的过程中根据业务执行情况， 检测软件包安装 的安全， 若存在安全风险， 则设置用户决策点中断业务执行并向所述客 户端发送用户决策请求， 由所述客户端提示用户决策是否安装， 所述服 务端在接收到所述客户端发送的是否安装的用户决策信息后确定是否继 续进行软件包的安装。
5. —种客户端 /服务器架构中客户端的业务执行方法， 其特征在于， 包括： 接收来自用户的业务执行请求并将其发送到服务端， 请求所述服务 端开始业务执行； 在业务执行过程中接收来自所述服务端的信息， 在所述信息为用户
决策请求时，提示用户需要决策并等待用户对所述用户决策请求的响应， 所述用户决策请求包含请求用户决策后续业务执行行为的信息；
接收用户对所述用户决策请求所作出的用户决策信息， 所述客户端 将该用户决策信息发送到所述服务端。
6. 如权利要求 5所述的方法， 其特征在于，
该方法应用于手机上 C/S架构软件包的安装， 在软件包的安装过程 中， 用户界面作为所述客户端， 后台的软件包安装程序为所述服务端； 在软件包的安装过程中， 在所述客户端接收到所述月艮务端由于检测 到安全风险而发送的用户决策请求后， 所述客户端提示用户需要决策是 否继续进行软件包安装并等待用户所作出的用户决策信息， 将用户决策 信息发送到所述艮务端。
7. —种客户端 /服务端架构中服务端和客户端的业务执行系统， 其特征在 于， 包括：
客户端业务执行单元， 用于向服务端发起业务执行请求， 在接收到 来自所述服务端的用户决策请求时， 提示用户需要决策并等待用户对用 户决策请求的响应， 并将用户对所述用户决策请求所作出的用户决策信 息发送到所述艮务端；
月艮务端业务执行单元， 用于在接收来自所述客户端的业务执行请求 后开始执行业务， 在业务执行过程中执行到预先设置的用户决策点时， 中断业务执行并向所述客户端发起用户决策请求， 在接收到所述客户端 对用户决策请求所作出的用户决策信息后， 根据用户决策决策信息确定 用户决策点后的业务执行行为。
8. 如权利要求 7所述的系统， 其特征在于， 所述艮务端业务执行单元包括： 决策点设置单元， 用于设置所述服务端在业务执行过程中需要用户 进行决策的用户决策点；
决策请求发起单元， 用于在所述服务端在业务执行过程中执行到预 先设置的用户决策点时， 中断业务执行并向所述客户端发起用户决策请 求， 所述用户决策请求包含请求用户决策所述用户决策点后业务执行行 为的信息；
执行单元， 用于在接收到所述客户端对用户决策请求所作出的用户
决策信息后， 根据用户决策决策信息与业务执行规则的对应关系， 确定 出接收的用户决策信息对应的业务执行行为， 并按该确定出的业务执行 行为执行业务。
9. 如权利要求 8所述的系统， 其特征在于，
所述决策点设置单元包括服务端设置单元或客户端设置单元， 所述月艮务端设置单元， 用于在业务执行流程中由月艮务端才艮据业务执 行情况设定用户决策点；
所述客户端设置单元， 用于在业务执行流程中由客户端配置用户决 策点。
10. 如权利要求 7或 8所述的系统， 其特征在于， 所述客户端业务执行单元 包括：
业务执行请求单元， 用于根据用户需求向所述服务端发起业务执行 请求， 请求服务端开始业务执行； 接收单元， 用于在业务执行过程中接收来自所述月艮务端的信息； 请求决策单元， 用于在接收的信息为用户决策请求时， 提示用户需 要决策并等待用户对用户决策请求的响应， 用户决策请求包含请求用户 决策后续业务执行行为的信息；
发送单元， 用于将用户对所述用户决策请求所作出的用户决策信息 发送到服务端。
11. 如权利要求 7所述的系统， 其特征在于，
该系统应用于手机上客户端 /服务端架构软件包的安装， 在软件包的 安装过程中， 用户界面作为所述客户端， 后台的软件包安装程序为所述 服务端；
所述艮务端业务执行单元， 在软件包的过程中才艮据所述艮务端的业 务执行情况， 检测软件包安装的安全， 若存在安全风险， 则设置用户决 策点中断业务执行并向客户端发送用户决策请求， 由所述客户端提示用 户决策是否安装， 在接收到所述客户端发送的是否安装的用户决策信息 后确定是否继续进行软件包的安装；
所述客户端业务执行单元， 在接收到所述月艮务端由于检测到安全风
险而发送的用户决策请求后， 所述客户端提示用户需要决策是否继续进 行软件包安装并等待用户所作出的用户决策信息， 将用户决策信息发送 到服务端。
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| US13/259,220 US8732694B2 (en) | 2009-08-26 | 2010-06-11 | Method and system for performing services in server and client of client/server architecture |
| RU2012108556/08A RU2554570C2 (ru) | 2009-08-26 | 2010-06-11 | Способ и система выполнения услуг на сервере и клиенте клиент-серверной архитектуры |
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN200910167153.4 | 2009-08-26 | ||
| CN200910167153.4A CN101635726B (zh) | 2009-08-26 | 2009-08-26 | C/s架构中服务端和客户端的业务执行方法及系统 |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| WO2011023020A1 true WO2011023020A1 (zh) | 2011-03-03 |
Family
ID=41594784
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| PCT/CN2010/073834 WO2011023020A1 (zh) | 2009-08-26 | 2010-06-11 | 客户端/服务端架构中服务端和客户端的业务执行方法及系统 |
Country Status (4)
| Country | Link |
|---|---|
| US (1) | US8732694B2 (zh) |
| CN (1) | CN101635726B (zh) |
| RU (1) | RU2554570C2 (zh) |
| WO (1) | WO2011023020A1 (zh) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| RU2656735C1 (ru) * | 2017-05-17 | 2018-06-06 | Федеральное государственное бюджетное учреждение науки Институт проблем управления им. В.А. Трапезникова Российской академии наук | Способ организации взаимодействия клиента с сервером приложений с использованием сервис-браузера |
Families Citing this family (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101635726B (zh) | 2009-08-26 | 2012-07-04 | 中兴通讯股份有限公司 | C/s架构中服务端和客户端的业务执行方法及系统 |
| US9811371B2 (en) | 2012-06-29 | 2017-11-07 | International Business Machines Corporation | Concurrent execution of a computer software application along multiple decision paths |
| CN105790975A (zh) * | 2014-12-22 | 2016-07-20 | 阿里巴巴集团控股有限公司 | 一种业务处理操作的执行方法及装置 |
| CN106027609B (zh) * | 2016-05-05 | 2019-04-02 | 深圳大数点科技有限公司 | 一种物联网服务系统 |
| CN106959887B (zh) * | 2017-02-16 | 2021-05-25 | 上海瀚银信息技术有限公司 | 一种分布式程序的业务流程协作系统及方法 |
| CN107395659B (zh) | 2017-03-28 | 2021-08-24 | 创新先进技术有限公司 | 一种业务受理及共识的方法及装置 |
| WO2019164644A1 (en) * | 2018-02-23 | 2019-08-29 | Idac Holdings, Inc. | Device-initiated service deployment through mobile application packaging |
| CN110049001A (zh) * | 2019-02-27 | 2019-07-23 | 新奥特（北京）视频技术有限公司 | 一种实现WebService服务的方法、装置、存储介质和服务器 |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6202206B1 (en) * | 1998-05-14 | 2001-03-13 | International Business Machines Corporation | Simultaneous installation and configuration of programs and components into a network of server and client computers |
| CN1598781A (zh) * | 2003-09-15 | 2005-03-23 | 英业达股份有限公司 | 软件保护方法及系统 |
| CN101141303A (zh) * | 2007-09-24 | 2008-03-12 | 华为技术有限公司 | 一种网络管理系统中的客户端升级方法、服务器、客户端 |
| CN101635726A (zh) * | 2009-08-26 | 2010-01-27 | 中兴通讯股份有限公司 | C/s架构中服务端和客户端的业务执行方法及系统 |
Family Cites Families (24)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US5761380A (en) * | 1996-02-12 | 1998-06-02 | International Business Machines Corporation | Coordinating installation of distributed software components |
| US5950010A (en) * | 1996-11-25 | 1999-09-07 | J.D. Edwards World Source Co. | System and method for customized application package building and installation |
| US6018725A (en) * | 1997-09-30 | 2000-01-25 | Pitney Bowes Inc. | Method and system of implementing a carrier manager registry |
| US6301707B1 (en) * | 1997-09-30 | 2001-10-09 | Pitney Bowes Inc. | Installing software based on a profile |
| JPH11120135A (ja) * | 1997-10-14 | 1999-04-30 | Canon Inc | 情報処理装置及びその方法、及びそのプログラムを記憶した記憶媒体 |
| KR100258969B1 (ko) * | 1997-11-20 | 2000-06-15 | 윤종용 | 무선 통신기기의 펌웨어 업그레이드 방법 및 기지국에서의펌웨어 업그레이드 지원방법 |
| US7073172B2 (en) * | 1998-09-21 | 2006-07-04 | Microsoft Corporation | On demand patching of applications via software implementation installer mechanism |
| US6324691B1 (en) * | 1998-11-12 | 2001-11-27 | Hewlett-Packard Company | Manufacture of software distribution media packages from components resident on a remote server source |
| US6493871B1 (en) * | 1999-09-16 | 2002-12-10 | Microsoft Corporation | Method and system for downloading updates for software installation |
| US6606744B1 (en) * | 1999-11-22 | 2003-08-12 | Accenture, Llp | Providing collaborative installation management in a network-based supply chain environment |
| US6963908B1 (en) * | 2000-03-29 | 2005-11-08 | Symantec Corporation | System for transferring customized hardware and software settings from one computer to another computer to provide personalized operating environments |
| US6854016B1 (en) * | 2000-06-19 | 2005-02-08 | International Business Machines Corporation | System and method for a web based trust model governing delivery of services and programs |
| US6918112B2 (en) * | 2000-11-29 | 2005-07-12 | Microsoft Corporation | System and method to facilitate installation of components across one or more computers |
| US7185334B2 (en) * | 2000-11-29 | 2007-02-27 | Microsoft Corporation | Method and software tool for intelligent operating system installation |
| BR0102842A (pt) * | 2001-05-22 | 2003-03-05 | Brasil Compressores Sa | Lâmina e arranjo de lâminas para motor linear |
| US7430736B2 (en) * | 2001-10-03 | 2008-09-30 | Toshiba Tec Kabushiki Kaisha | Download and installation of software from a network printer |
| KR100420601B1 (ko) * | 2001-11-22 | 2004-03-02 | 에스케이 텔레콤주식회사 | 비디오 데이터 스트리밍 서비스 방법 |
| US6954930B2 (en) * | 2002-02-19 | 2005-10-11 | International Business Machines Corporation | Remote validation of installation input data |
| US8216071B2 (en) * | 2002-03-20 | 2012-07-10 | Intel Corporation | Method and apparatus for software delivery and management |
| US7430590B1 (en) * | 2002-04-17 | 2008-09-30 | Everdream Corporation | Method and system to manage services for multiple managed computer systems |
| US7797434B2 (en) * | 2002-12-31 | 2010-09-14 | International Business Machines Corporation | Method and system for user-determind attribute storage in a federated environment |
| US10162618B2 (en) * | 2004-12-03 | 2018-12-25 | International Business Machines Corporation | Method and apparatus for creation of customized install packages for installation of software |
| US7818734B2 (en) * | 2005-01-21 | 2010-10-19 | Callwave, Inc. | Methods and systems for transferring data over a network |
| US7596610B2 (en) * | 2005-03-15 | 2009-09-29 | Microsoft Corporation | Method and system for installing applications via a display page |
-
2009
- 2009-08-26 CN CN200910167153.4A patent/CN101635726B/zh not_active Expired - Fee Related
-
2010
- 2010-06-11 US US13/259,220 patent/US8732694B2/en not_active Expired - Fee Related
- 2010-06-11 RU RU2012108556/08A patent/RU2554570C2/ru active
- 2010-06-11 WO PCT/CN2010/073834 patent/WO2011023020A1/zh active Application Filing
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6202206B1 (en) * | 1998-05-14 | 2001-03-13 | International Business Machines Corporation | Simultaneous installation and configuration of programs and components into a network of server and client computers |
| CN1598781A (zh) * | 2003-09-15 | 2005-03-23 | 英业达股份有限公司 | 软件保护方法及系统 |
| CN101141303A (zh) * | 2007-09-24 | 2008-03-12 | 华为技术有限公司 | 一种网络管理系统中的客户端升级方法、服务器、客户端 |
| CN101635726A (zh) * | 2009-08-26 | 2010-01-27 | 中兴通讯股份有限公司 | C/s架构中服务端和客户端的业务执行方法及系统 |
Non-Patent Citations (1)
| Title |
|---|
| GU, ZHENLI.: "installation and configuration of network software supporting multi-computer sharing one line.", JURNAL OF XUCHANG TEACHERS COLLEGE., vol. 19, no. 5, September 2000 (2000-09-01), pages 80 - 81 * |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| RU2656735C1 (ru) * | 2017-05-17 | 2018-06-06 | Федеральное государственное бюджетное учреждение науки Институт проблем управления им. В.А. Трапезникова Российской академии наук | Способ организации взаимодействия клиента с сервером приложений с использованием сервис-браузера |
Also Published As
| Publication number | Publication date |
|---|---|
| RU2554570C2 (ru) | 2015-06-27 |
| US20120144387A1 (en) | 2012-06-07 |
| CN101635726A (zh) | 2010-01-27 |
| CN101635726B (zh) | 2012-07-04 |
| US8732694B2 (en) | 2014-05-20 |
| RU2012108556A (ru) | 2013-10-10 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| WO2011023020A1 (zh) | 客户端/服务端架构中服务端和客户端的业务执行方法及系统 | |
| US10871953B2 (en) | Application update method and apparatus | |
| US8838812B2 (en) | Network security enhancement methods, apparatuses, system, media, signals and computer programs | |
| US10142425B2 (en) | Session reliability for a redirected USB device | |
| US6687817B1 (en) | Configuration of a network device via the network | |
| JP4864333B2 (ja) | ソフトウェアの脆弱性の悪用を防止するように通信をフィルタ処理するための方法およびシステム | |
| US7519950B2 (en) | Method and system for version negotiation of distributed objects | |
| KR20080068647A (ko) | 이형, 분산 컴퓨팅 시스템에 서비스 애플리케이션 실행환경을 형성하기 위한 방법 및 시스템, 그리고 상기 서비스애플리케이션 실행 환경에서 실행하는 사용자 친화적데이터 전달 서비스 애플리케이션 | |
| JP2001516479A (ja) | 機能するオペレーティング・システムなしにコンピュータのリモート管理を可能にするネットワーク機能拡張ｂｉｏｓ | |
| JP2019522282A (ja) | クラウドコンピューティングノードのセキュアな設定 | |
| US20060248180A1 (en) | Techniques for managing terminal services sessions | |
| US10404568B2 (en) | Agent manager for distributed transaction monitoring system | |
| WO2017193926A1 (zh) | 数据传输方法及装置 | |
| WO2017166906A1 (zh) | 一种管理eUICC中的签约信息集的方法及相关设备 | |
| JP4071098B2 (ja) | ネットワークフィルタドライバのためのアーキテクチャおよびランタイム環境 | |
| CN105162667B (zh) | 虚拟机配置方法和装置 | |
| JP2013246817A (ja) | 同期サーバ側スクリプティングを用いた遠隔カードコンテンツ管理 | |
| WO2013102397A1 (zh) | 搭建应用运行环境的方法、装置及存储介质 | |
| CN109918140A (zh) | 一种云应用操作控制方法和装置 | |
| US8051191B2 (en) | Ethernet extensibility | |
| CN111615819B (zh) | 一种传输数据的方法和装置 | |
| US7568194B2 (en) | Method and system for availability checking on distributed objects | |
| JP2017187963A (ja) | 電子機器およびシステム | |
| US10291717B2 (en) | Prioritizing VDI sessions and redirected devices in software defined networks | |
| CN106331051A (zh) | 文件传输方法和系统以及接收文件装置、发送文件装置 |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| 121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 10811180 Country of ref document: EP Kind code of ref document: A1 |
|
| WWE | Wipo information: entry into national phase |
Ref document number: 13259220 Country of ref document: US |
|
| NENP | Non-entry into the national phase |
Ref country code: DE |
|
| WWE | Wipo information: entry into national phase |
Ref document number: 2251/CHENP/2012 Country of ref document: IN |
|
| WWE | Wipo information: entry into national phase |
Ref document number: 2012108556 Country of ref document: RU |
|
| 122 | Ep: pct application non-entry in european phase |
Ref document number: 10811180 Country of ref document: EP Kind code of ref document: A1 |