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
Claims
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) | 機能するオペレーティング・システムなしにコンピュータのリモート管理を可能にするネットワーク機能拡張bios | |
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 |