WO2016112793A1 - 并发多业务会话的方法及其系统 - Google Patents
并发多业务会话的方法及其系统 Download PDFInfo
- Publication number
- WO2016112793A1 WO2016112793A1 PCT/CN2016/070132 CN2016070132W WO2016112793A1 WO 2016112793 A1 WO2016112793 A1 WO 2016112793A1 CN 2016070132 W CN2016070132 W CN 2016070132W WO 2016112793 A1 WO2016112793 A1 WO 2016112793A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- session
- service
- service session
- client
- business
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Ceased
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/40—Support for services or applications
Definitions
- the present invention relates to communication technologies, and more particularly to a method and system for concurrent multi-service sessions.
- the existing WEB Internet technology relies only on the system sessioin (session) mechanism to associate multiple request-responses (request-response, referred to as "req-res”) between client-servers, which results in multiple sessions in the same system session. Business activities interfere with each other,
- system sessions are often used to share data across multiple req-res.
- the sharing process generally involves writing data to the system session in a particular req-res, and then reading the data from the system session in a subsequent req-res.
- TAB label
- an embodiment of the present invention discloses a method for concurrent multi-service session, in which a client simultaneously performs multiple service sessions in the same system session, and each service session is set with a unique service session identifier, and the method Includes the following steps:
- the server receives the service session identifier of the service session sent by the client when receiving the request of the client in each service session;
- the server sends a service to the client when responding to the client's request in each business session.
- the business session identifier of the message is a service that specifies the business session.
- the embodiment of the present invention further discloses a system for concurrent multi-service sessions, wherein the system controls the client to perform multiple service sessions simultaneously in the same system session, and each service session is provided with a unique service session identifier, and the system includes:
- a receiving module configured to receive a service session identifier of a service session sent by the client when the server receives the request of the client in each service session;
- the sending module is configured to control, when the server responds to the request of the client in each service session, send a service session identifier of the service session to the client.
- a plurality of different service sessions are distinguished by setting a service session identifier in the same system session, so that when multiple service sessions are simultaneously performed, each service session can be isolated according to each service session identifier, and concurrently While completing multiple services, mutual coverage of business data is avoided.
- each service data can only be read and written by the corresponding service session identifier, so that each service data does not overlap each other.
- the creation is started at the beginning of each service session, and the corresponding service session identifier and service data are deleted at the end, which is convenient and flexible.
- FIG. 1 is a schematic diagram of a prior art multi-service session.
- FIG. 2 is a schematic flow chart of a method for concurrent multi-service conversation in the first embodiment of the present invention.
- FIG. 3 is a schematic structural diagram of a system for concurrent multi-service sessions in a third embodiment of the present invention.
- a first embodiment of the invention relates to a method of concurrent multi-service sessions.
- 2 is a schematic flow chart of a method for concurrent concurrent multi-service sessions.
- the client simultaneously performs multiple service sessions in the same system session, and each service session is set with a unique service session identifier.
- system session represents the period from when the browser opens a site to when the browser is closed. During this time, all request-response operations share the same session, that is, the data stored in the system session can be in multiple reqs. -res sharing.
- a business session is a supplement to an existing system session mechanism.
- a business session corresponds to a complete life cycle of a business activity from start to finish, that is, a business session is created in the initial task of the business activity, and the business session is destroyed after the completion of the task. .
- a typical payment business activity includes three tasks of login, cashier payment, and payment result presentation, so a new business session is created in the login task, and the business session is destroyed after the payment result display task is completed.
- the business session identifier uniquely identifies a business activity.
- the method includes the following steps:
- the server receives the service session identifier of the service session sent by the client when receiving the request of the client in each service session.
- the information related to the service session carries the relevant service session identifier to distinguish the service session to which each message belongs.
- the request message sent by the client to the server is generally of many types, and the service session identifier may be carried in the request message.
- the various request messages are themselves prior art and will not be described in detail herein.
- the server sends the service session identifier of the service session to the client when responding to the request of the client in each service session.
- the response message sent by the server to the client includes the service session identifier (obtained from the request message that triggered the response message).
- the client obtains the service session identifier by analyzing the response message.
- the response message sent by the server to the client may be of many types. If it is related to the service session, it generally carries the service session identifier.
- the various response messages are themselves prior art and will not be described in detail herein.
- multiple service sessions are distinguished by setting a service session identifier in the same system session, so that when multiple service sessions are simultaneously performed, each service session can be isolated according to each service session identifier.
- the mutual coverage of business data is avoided. Because the service session identifier is carried in both the request and response messages related to the service, the client can know the service session corresponding to each message, and the related service data can be stored in the dedicated storage area (or storage file) of the corresponding service session. Medium, so each business session can be successfully isolated, and business data of different services will not be covered by each other.
- a second embodiment of the present invention is directed to a method of concurrent multi-service sessions.
- the second embodiment differs from the first embodiment in that:
- Each service data can only be read and written by the corresponding service session identifier, so that each service data does not overlap each other. Specifically:
- the server When the server receives the client's request in each business session, the server obtains the business session object from the system session object through the service session identifier received from the client, and stores the service data into the service session object.
- a session object is an object created in a session.
- the server is created at the beginning of each service session. At the end, the corresponding service session identifier and service data are deleted, which is convenient and flexible. Specifically:
- the above method also includes the following steps:
- the server creates a new business session in the start task of each business activity and sets a unique business session ID for the new business session.
- the above method further includes the following steps:
- the server deletes the corresponding business session ID and business data.
- the corresponding service session identifier and service data may not be deleted to facilitate the query.
- the service data is associated with the service sessionId when storing data visible in such a service instance (That is, the business session ID), not the system sessionId (that is, the system session ID).
- the specific plan is as follows:
- Service sessionId generation At the beginning of the service activity node, a session variable is created in the current session, and a session session variable is uniquely identified for the session variable.
- Service sessionId sharing different from the system sessionId can be saved by cookie and shared between req-res, the business sessionId can not be placed in the cookie, it needs to be returned to the browser every time the response is sent, and then in the browser next request, then The business sessionId is submitted to the server.
- ⁇ Write business data Obtain the business session object from the system session through the business sessionId, and store the business data into the business session object.
- Reading business data The business session object is read from the system session using the business sessionId, and then the business data is read from the business session object.
- a business session starts with the first business activity of the business instance and ends with the end of the business instance; each system session has a unique system. sessionId, correspondingly, we assign a unique business sessionId to the business session.
- the method embodiments of the present invention can all be implemented in software, hardware, firmware, and the like. Regardless of whether the invention is implemented in software, hardware, or firmware, the instruction code can be stored in any type of computer-accessible memory (eg, permanent or modifiable, volatile or non-volatile, solid state Or non-solid, fixed or replaceable media, etc.). Similarly, the memory may be, for example, Programmable Array Logic ("PAL"), Random Access Memory (RAM), or Programmable Read Only Memory (PROM). "), Read-Only Memory (“ROM”), Electrically Erasable Programmable ROM (“EEPROM”), Disk, CD, Digital Versatile Disc , referred to as "DVD”) and so on.
- PAL Programmable Array Logic
- RAM Random Access Memory
- PROM Programmable Read Only Memory
- ROM Read-Only Memory
- EEPROM Electrically Erasable Programmable ROM
- Disk CD
- DVD Digital Versatile Disc
- FIG. 3 is a schematic structural diagram of a system for concurrent concurrent multi-service sessions.
- the system control client of the concurrent multi-service session simultaneously performs multiple service sessions in the same system session, and each service session is set with a unique service session identifier.
- the system includes:
- the receiving module is configured to receive a service session identifier of the service session sent by the client when the server receives the request of the client in each service session. as well as
- the sending module is configured to control, when the server responds to the request of the client in each service session, send a service session identifier of the service session to the client.
- multiple service sessions are distinguished by setting a service session identifier in the same system session, so that when multiple service sessions are simultaneously performed, each service session can be isolated according to each service session identifier.
- each service session can be isolated according to each service session identifier.
- the first embodiment is a method embodiment corresponding to the present embodiment, and the present embodiment can be implemented in cooperation with the first embodiment.
- the related technical details mentioned in the first embodiment are still effective in the present embodiment, and are not described herein again in order to reduce repetition. Accordingly, the related art details mentioned in the present embodiment can also be applied to the first embodiment.
- a fourth embodiment of the present invention is directed to a system for concurrent multi-service sessions.
- the fourth embodiment differs from the third embodiment in that:
- Each service data can only be read and written by the corresponding service session identifier, so that each service data does not overlap each other. Specifically:
- the above system further includes a writing module, configured to control the server to obtain a service session object from the system session object through the service session identifier received from the client when receiving the client request in each service session, and store the service data into the service.
- a writing module configured to control the server to obtain a service session object from the system session object through the service session identifier received from the client when receiving the client request in each service session, and store the service data into the service.
- a writing module configured to control the server to obtain a service session object from the system session object through the service session identifier received from the client when receiving the client request in each service session, and store the service data into the service.
- a writing module configured to control the server to obtain a service session object from the system session object through the service session identifier received from the client when receiving the client request in each service session, and store the service data into the service.
- the conversation object configured to control the server to obtain a service session object from the system session object through the service session identifier received from the client when receiving the client request
- the system further includes a reading module configured to control the server to obtain a business session object from the system session object and read from the service session object by receiving the service session identifier from the client when responding to the client request in each business session. Take business data.
- the above system also includes a creation module for controlling the server to create a new business session in the initial task of each business activity and to set a unique business session identifier for the new business session.
- system further includes a deleting module, configured to control the server to delete the corresponding service session identifier and service data at the end of each service session.
- a deleting module configured to control the server to delete the corresponding service session identifier and service data at the end of each service session.
- the corresponding service session identifier and service data may not be deleted to facilitate the query.
- the second embodiment is a method embodiment corresponding to the present embodiment, and the present embodiment can be implemented in cooperation with the second embodiment.
- the related technical details mentioned in the second embodiment are still effective in the present embodiment, and are not described herein again in order to reduce repetition. Accordingly, the related art details mentioned in the present embodiment can also be applied to the second embodiment.
- the present invention introduces a service session mechanism based on the system session mechanism, that is, embedding a service session in a system session, and isolating multiple business activities in the same system session through a dual session mechanism. It can be understood that this dual session mechanism can be applied to other session applications other than Internet pages.
- each module mentioned in each device implementation manner of the present invention is a logic module.
- a logic module may be a physical module, a part of a physical module, or multiple physical entities.
- the combined implementation of modules, the physical implementation of these logic modules themselves is not the most important, the combination of the functions implemented by these logic modules is the key to solving the technical problems raised by the present invention.
- the above-mentioned various device embodiments of the present invention do not introduce a module that is not closely related to solving the technical problem proposed by the present invention, which does not indicate that the above device implementation does not have other Module.
Landscapes
- Engineering & Computer Science (AREA)
- Multimedia (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer And Data Communications (AREA)
Abstract
本发明涉及通信技术，公开了一种并发多业务会话的方法及其系统。在本发明中，在同一个系统会话中通过设置业务会话标识来区分多个不同的业务会话，从而在同时进行多个业务会话时，可以根据各业务会话标识将各业务会话进行隔离，在并发完成多个业务的同时，避免了业务数据的相互覆盖。此外，在各业务会话开始时进行创建，结束时即将相应的业务会话标识和业务数据删除，方便灵活。
Description
本发明涉及通信技术，特别涉及并发多业务会话的方法及其系统。
现有WEB互联网技术仅依赖系统sessioin(会话)机制来把客户端-服务器之间的多个request-response(请求－响应，简称“req-res”)关联起来，这导致同一系统session中多个业务活动相互干扰，
在互联网应用中，通常使用系统session在多个req-res间共享数据。如图1所示，共享过程一般为：在某一个特定的req-res中向系统session中写入数据，然后在后续某个req-res中从系统session中读取数据。由于浏览器开放性，用户可以在同一个浏览器中开多个TAB(标签)页，例如TAB页1和TAB页2，同时并发地完成多个业务，在这种情况下就会发生图1所示的业务数据相互覆盖的问题。
发明内容
本发明的目的在于提供一种并发多业务会话的方法及其系统，在并发完成多个业务的同时，避免业务数据的相互覆盖。
为解决上述技术问题，本发明的实施方式公开了一种并发多业务会话的方法，客户端在同一个系统会话中同时进行多个业务会话，每个业务会话设置有唯一的业务会话标识，方法包括以下步骤：
服务器在每个业务会话中接收客户端的请求时，接收客户端发送的业务会话的业务会话标识；
服务器在每个业务会话中响应客户端的请求时，向客户端发送业务会
话的业务会话标识。
本发明的实施方式还公开了一种并发多业务会话的系统，该系统控制客户端在同一个系统会话中同时进行多个业务会话，每个业务会话设置有唯一的业务会话标识，系统包括：
接收模块，用于控制服务器在每个业务会话中接收客户端的请求时，接收客户端发送的业务会话的业务会话标识；以及
发送模块，用于控制服务器在每个业务会话中响应客户端的请求时，向客户端发送业务会话的业务会话标识。
本发明实施方式与现有技术相比，主要区别及其效果在于：
在本发明中，在同一个系统会话中通过设置业务会话标识来区分多个不同的业务会话，从而在同时进行多个业务会话时，可以根据各业务会话标识将各业务会话进行隔离，在并发完成多个业务的同时，避免了业务数据的相互覆盖。
进一步地，各业务数据仅能通过相应的业务会话标识进行读写操作，从而各业务数据不会相互覆盖。
进一步地，在各业务会话开始时进行创建，结束时即将相应的业务会话标识和业务数据删除，方便灵活。
图1是现有的一种多业务会话的示意图。
图2是本发明第一实施方式中一种并发多业务会话的方法的流程示意图。
图3是本发明第三实施方式中一种并发多业务会话的系统的结构示意图。
在以下的叙述中，为了使读者更好地理解本申请而提出了许多技术细节。但是，本领域的普通技术人员可以理解，即使没有这些技术细节和基于以下各实施方式的种种变化和修改，也可以实现本申请各权利要求所要求保护的技术方案。
为使本发明的目的、技术方案和优点更加清楚，下面将结合附图对本发明的实施方式作进一步地详细描述。
本发明第一实施方式涉及一种并发多业务会话的方法。图2是该并发多业务会话的方法的流程示意图。在该并发多业务会话的方法中，客户端在同一个系统会话中同时进行多个业务会话，每个业务会话设置有唯一的业务会话标识。
可以理解，系统会话代表从浏览器打开一个站点开始到关闭浏览器为止这段时间段，这段时间内所有request-response操作共享同一个会话，即存放在系统会话中的数据可以在多个req-res间共享。
业务会话是对现有系统会话机制的补充，一个业务会话对应一次业务活动从开始到结束完整的生命周期，即在业务活动的起始任务中创建业务会话，并在结束任务完成后销毁业务会话。以支付为例，一次典型的支付业务活动包括登录、收银台付款、支付结果展示三个任务，因此在登录任务中创建一个新业务会话，并在支付结果展示任务完成后销毁这个业务会话。而业务会话标识唯一标识一次业务活动。
如图2所示，该方法包括以下步骤：
在步骤201中，服务器在每个业务会话中接收客户端的请求时，接收客户端发送的业务会话的业务会话标识。客户端与服务器之间会有各种交互消
息，在与业务会话相关的消息中携带相关的业务会话标识，以区别各消息所属的业务会话。基于不同的业务类型，客户端向服务器发送的请求消息一般有很多类型，在请求消息中可以携带业务会话标识。各种请求消息本身是现有技术，在此不进行详细说明了。
此后进入步骤202，服务器在每个业务会话中响应客户端的请求时，向客户端发送业务会话的业务会话标识。服务器向客户端发送的响应消息中包含业务会话标识(从触发该响应消息的请求消息中取得的)，客户端收到响应消息时，通过对响应消息的分析，得到业务会话标识。服务器向客户端发送的响应消息可能有很多类型，如果是与业务会话相关的，一般要携带业务会话标识。各种响应消息本身是现有技术，在此不进行详细说明了。
此后结束本流程。
在本实施方式的方法中，在同一个系统会话中通过设置业务会话标识来区分多个不同的业务会话，从而在同时进行多个业务会话时，可以根据各业务会话标识将各业务会话进行隔离，在并发完成多个业务的同时，避免了业务数据的相互覆盖。因为与业务相关的请求和响应消息中都携带了业务会话标识，所以客户端可以知道每一个消息所对应的业务会话，相关的业务数据可以存储在相应业务会话的专用存储区域(或存储文件)中，所以可以将各业务会话成功地隔离，不同业务的业务数据不会相互覆盖。
本发明第二实施方式涉及一种并发多业务会话的方法。第二实施方式与第一实施方式相比，其区别在于：
各业务数据仅能通过相应的业务会话标识进行读写操作，从而各业务数据不会相互覆盖。具体地说：
服务器在每个业务会话中接收客户端的请求时，通过从客户端接收的业务会话标识从系统会话对象中获取业务会话对象，并把业务数据存入业务会话对象中。
服务器在每个业务会话中响应客户端的请求时，通过从客户端接收的业务会话标识从系统会话对象中获取业务会话对象，并从业务会话对象中读取业务数据。可以理解，会话对象是在会话中创建的对象。
服务器在各业务会话开始时进行创建，结束时即将相应的业务会话标识和业务数据删除，方便灵活。具体地说：
上述方法还包括以下步骤：
服务器在每个业务活动的起始任务中创建新的业务会话，并为新的业务会话设置唯一的业务会话标识。
可选地，上述方法还包括以下步骤：
在每个业务会话结束时，服务器删除相应的业务会话标识和业务数据。
可以理解，在本发明的其他实施方式中，在业务会话结束时，也可以不删除相应的业务会话标识和业务数据，以方便查询。
在本发明的一个优选的例子中，业务实例执行过程中，如果产生的业务数据仅在当前业务实例内可见，那么在存储这类业务实例内可见的数据时，把业务数据关联到业务sessionId(即业务会话标识)，而不是系统sessionId(即系统会话标识)。具体方案如下：
●业务sessionId生成：在业务的开始活动节点，在当前session中创建一个session变量，并为该session变量分配一个唯一标识该业务实例的业务sessionId。
●业务sessionId共享：不同于系统sessionId可以通过cookie保存并在req-res间共享，业务sessionId不能放在cookie中，需要在每次response时返回给浏览器然后在浏览器下一个request时，再把业务sessionId提交给服务器。
●写业务数据：通过业务sessionId从系统session中获取业务session对象，把业务数据存入业务session对象。
●读业务数据：使用业务sessionId从系统session中读取业务session对象，然后从业务session对象中读取业务数据。
为了达到把不同业务实例的业务数据隔离的目的，引入业务session的概念，一个业务session开始于业务实例的第一个业务活动，止于业务实例的结束活动；每个系统session有一个唯一的系统sessionId,相应的，我们为业务session分配一个唯一的业务sessionId。
可以理解，以上各改进组合后形成本发明的较佳实施例，但各改进也可以分别使用。
本发明的各方法实施方式均可以以软件、硬件、固件等方式实现。不管本发明是以软件、硬件、还是固件方式实现，指令代码都可以存储在任何类型的计算机可访问的存储器中(例如永久的或者可修改的，易失性的或者非易失性的，固态的或者非固态的，固定的或者可更换的介质等等)。同样，存储器可以例如是可编程阵列逻辑(Programmable Array Logic，简称“PAL”)、随机存取存储器(Random Access Memory，简称“RAM”)、可编程只读存储器(Programmable Read Only Memory，简称“PROM”)、只读存储器(Read-Only Memory，简称“ROM”)、电可擦除可编程只读存储器(Electrically Erasable Programmable ROM，简称“EEPROM”)、磁盘、光盘、数字通用光盘(Digital Versatile Disc，简称“DVD”)等等。
本发明第三实施方式涉及一种并发多业务会话的系统。图3是该并发多业务会话的系统的结构示意图。该并发多业务会话的系统控制客户端在同一个系统会话中同时进行多个业务会话，每个业务会话设置有唯一的业务会话标识。如图3所示，该系统包括：
接收模块，用于控制服务器在每个业务会话中接收客户端的请求时，接收客户端发送的业务会话的业务会话标识。以及
发送模块，用于控制服务器在每个业务会话中响应客户端的请求时，向客户端发送业务会话的业务会话标识。
在本实施方式的系统中，在同一个系统会话中通过设置业务会话标识来区分多个不同的业务会话，从而在同时进行多个业务会话时，可以根据各业务会话标识将各业务会话进行隔离，在并发完成多个业务的同时，避免了业务数据的相互覆盖。
第一实施方式是与本实施方式相对应的方法实施方式，本实施方式可与第一实施方式互相配合实施。第一实施方式中提到的相关技术细节在本实施方式中依然有效，为了减少重复，这里不再赘述。相应地，本实施方式中提到的相关技术细节也可应用在第一实施方式中。
本发明第四实施方式涉及一种并发多业务会话的系统。第四实施方式与第三实施方式相比，其区别在于：
各业务数据仅能通过相应的业务会话标识进行读写操作，从而各业务数据不会相互覆盖。具体地说：
上述系统还包括写入模块，用于控制服务器在每个业务会话中接收客户端的请求时，通过从客户端接收的业务会话标识从系统会话对象中获取业务会话对象，并把业务数据存入业务会话对象中。
上述系统还包括读取模块，用于控制服务器在每个业务会话中响应客户端的请求时，通过从客户端接收的业务会话标识从系统会话对象中获取业务会话对象，并从业务会话对象中读取业务数据。
在各业务会话开始时进行创建，结束时即将相应的业务会话标识和业务数据删除，方便灵活。具体地说
上述系统还包括创建模块，用于控制服务器在每个业务活动的起始任务中创建新的业务会话，并为新的业务会话设置唯一的业务会话标识。
可选地，上述系统还包括删除模块，用于控制服务器在每个业务会话结束时，删除相应的业务会话标识和业务数据。
可以理解，在本发明的其他实施方式中，在业务会话结束时，也可以不删除相应的业务会话标识和业务数据，以方便查询。
第二实施方式是与本实施方式相对应的方法实施方式，本实施方式可与第二实施方式互相配合实施。第二实施方式中提到的相关技术细节在本实施方式中依然有效，为了减少重复，这里不再赘述。相应地，本实施方式中提到的相关技术细节也可应用在第二实施方式中。
综上，本发明在系统session机制基础上引入业务session机制，即在系统session中嵌入业务session，通过双重session机制把同一系统session中的多个业务活动隔离开来。可以理解，这种双重session机制可以应用于除互联网网页外的其他会话应用中。
通过本发明可以做到一个系统session中多笔业务活动之间相互隔离，避免在并发情况下各业务数据相互覆盖。
需要说明的是，本发明各设备实施方式中提到的各模块都是逻辑模块，在物理上，一个逻辑模块可以是一个物理模块，也可以是一个物理模块的一部分，还可以以多个物理模块的组合实现，这些逻辑模块本身的物理实现方式并不是最重要的，这些逻辑模块所实现的功能的组合才是解决本发明所提出的技术问题的关键。此外，为了突出本发明的创新部分，本发明上述各设备实施方式并没有将与解决本发明所提出的技术问题关系不太密切的模块引入，这并不表明上述设备实施方式并不存在其它的模块。
需要说明的是，在本专利的权利要求和说明书中，诸如第一和第二等之类的关系术语仅仅用来将一个实体或者操作与另一个实体或操作区分开
来，而不一定要求或者暗示这些实体或操作之间存在任何这种实际的关系或者顺序。而且，术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、物品或者设备不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、物品或者设备所固有的要素。在没有更多限制的情况下，由语句“包括一个”限定的要素，并不排除在包括所述要素的过程、方法、物品或者设备中还存在另外的相同要素。
虽然通过参照本发明的某些优选实施方式，已经对本发明进行了图示和描述，但本领域的普通技术人员应该明白，可以在形式上和细节上对其作各种改变，而不偏离本发明的精神和范围。
Claims (10)
- 一种并发多业务会话的方法，其特征在于，客户端在同一个系统会话中同时进行多个业务会话，每个业务会话设置有唯一的业务会话标识，所述方法包括以下步骤：服务器在每个业务会话中接收所述客户端的请求时，接收所述客户端发送的所述业务会话的业务会话标识；所述服务器在每个业务会话中响应所述客户端的请求时，向所述客户端发送所述业务会话的业务会话标识。
- 根据权利要求1所述的并发多业务会话的方法，其特征在于，所述服务器在每个业务会话中接收所述客户端的请求时，通过从所述客户端接收的所述业务会话标识从系统会话对象中获取业务会话对象，并把业务数据存入所述业务会话对象中。
- 根据权利要求1所述的并发多业务会话的方法，其特征在于，所述服务器在每个业务会话中响应所述客户端的请求时，通过从所述客户端接收的所述业务会话标识从系统会话对象中获取业务会话对象，并从所述业务会话对象中读取业务数据。
- 根据权利要求1所述的并发多业务会话的方法，其特征在于，所述方法还包括以下步骤：所述服务器在每个业务活动的起始任务中创建新的业务会话，并为所述新的业务会话设置唯一的业务会话标识。
- 根据权利要求1所述的并发多业务会话的方法，其特征在于，所述方法还包括以下步骤：在每个业务会话结束时，所述服务器删除相应的业务会话标识和业务 数据。
- 一种并发多业务会话的系统，其特征在于，该系统控制客户端在同一个系统会话中同时进行多个业务会话，每个业务会话设置有唯一的业务会话标识，所述系统包括：接收模块，用于控制所述服务器在每个业务会话中接收所述客户端的请求时，接收所述客户端发送的所述业务会话的业务会话标识；以及发送模块，用于控制所述服务器在每个业务会话中响应所述客户端的请求时，向所述客户端发送所述业务会话的业务会话标识。
- 根据权利要求6所述的并发多业务会话的系统，其特征在于，所述系统还包括写入模块，用于控制所述服务器在每个业务会话中接收所述客户端的请求时，通过从所述客户端接收的所述业务会话标识从系统会话对象中获取业务会话对象，并把业务数据存入所述业务会话对象中。
- 根据权利要求6所述的并发多业务会话的系统，其特征在于，所述系统还包括读取模块，用于控制所述服务器在每个业务会话中响应所述客户端的请求时，通过从所述客户端接收的所述业务会话标识从系统会话对象中获取业务会话对象，并从所述业务会话对象中读取业务数据。
- 根据权利要求6所述的并发多业务会话的系统，其特征在于，所述系统还包括创建模块，用于控制所述服务器在每个业务活动的起始任务中创建新的业务会话，并为所述新的业务会话设置唯一的业务会话标识。
- 根据权利要求6所述的并发多业务会话的系统，其特征在于，所述系统还包括删除模块，用于控制所述服务器在每个业务会话结束时，删除相应的业务会话标识和业务数据。
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510014870.9 | 2015-01-12 | ||
| CN201510014870.9A CN105847217B (zh) | 2015-01-12 | 2015-01-12 | 并发多业务会话的方法及其系统 |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| WO2016112793A1 true WO2016112793A1 (zh) | 2016-07-21 |
Family
ID=56405237
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| PCT/CN2016/070132 Ceased WO2016112793A1 (zh) | 2015-01-12 | 2016-01-05 | 并发多业务会话的方法及其系统 |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN105847217B (zh) |
| WO (1) | WO2016112793A1 (zh) |
Families Citing this family (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106357791A (zh) * | 2016-09-30 | 2017-01-25 | 华为技术有限公司 | 业务处理方法、装置及系统 |
| CN110650203B (zh) * | 2019-09-26 | 2022-10-14 | 广州视源电子科技股份有限公司 | 数据传输方法、装置和系统、计算机存储介质及电子设备 |
| CN110740351B (zh) * | 2019-11-14 | 2022-05-24 | 普联技术有限公司 | 一种传输流媒体数据的方法、设备及存储介质 |
| CN111580476B (zh) * | 2020-04-30 | 2021-05-11 | 联宝(合肥)电子科技有限公司 | 一种智能生产管理的方法、设备及计算机可读介质 |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101753592A (zh) * | 2008-11-28 | 2010-06-23 | 国际商业机器公司 | 用于数据处理的方法和系统 |
| US8200833B1 (en) * | 2011-10-05 | 2012-06-12 | Google Inc. | Security mode based management of cookie data stores |
| CN102622348A (zh) * | 2011-01-26 | 2012-08-01 | 腾讯科技（深圳）有限公司 | 实现多个窗口同时对网络页面进行解析显示的方法和装置 |
| CN103198142A (zh) * | 2013-04-17 | 2013-07-10 | 华为技术有限公司 | 页面数据更新处理方法、客户端及服务器 |
| US20140108667A1 (en) * | 2012-10-15 | 2014-04-17 | Dell Products L.P. | Techniques for Generating Different Sessions for Multiple Tabs of a Single Browser Window |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101635672B (zh) * | 2008-07-21 | 2013-05-08 | 中兴通讯股份有限公司 | 一种群组方式下实现融合业务会话的装置和方法 |
| CN102638582B (zh) * | 2012-04-12 | 2015-07-08 | 华为技术有限公司 | 数据通信方法及通信端 |
-
2015
- 2015-01-12 CN CN201510014870.9A patent/CN105847217B/zh active Active
-
2016
- 2016-01-05 WO PCT/CN2016/070132 patent/WO2016112793A1/zh not_active Ceased
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101753592A (zh) * | 2008-11-28 | 2010-06-23 | 国际商业机器公司 | 用于数据处理的方法和系统 |
| CN102622348A (zh) * | 2011-01-26 | 2012-08-01 | 腾讯科技（深圳）有限公司 | 实现多个窗口同时对网络页面进行解析显示的方法和装置 |
| US8200833B1 (en) * | 2011-10-05 | 2012-06-12 | Google Inc. | Security mode based management of cookie data stores |
| US20140108667A1 (en) * | 2012-10-15 | 2014-04-17 | Dell Products L.P. | Techniques for Generating Different Sessions for Multiple Tabs of a Single Browser Window |
| CN103198142A (zh) * | 2013-04-17 | 2013-07-10 | 华为技术有限公司 | 页面数据更新处理方法、客户端及服务器 |
Also Published As
| Publication number | Publication date |
|---|---|
| CN105847217B (zh) | 2019-09-06 |
| CN105847217A (zh) | 2016-08-10 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108681965A (zh) | 离线节点的区块链网络交易处理方法和接收方节点 | |
| CN112000741A (zh) | 内外网数据交换系统、方法、装置、计算机设备和介质 | |
| US9286307B2 (en) | Document management apparatus improved in efficiency of deletion of files, method of controlling the same, and storage medium | |
| CN105847447A (zh) | 消息推送方法和装置 | |
| WO2016112793A1 (zh) | 并发多业务会话的方法及其系统 | |
| CN108512930A (zh) | 一种共享文件的管理方法、装置、服务器和存储介质 | |
| JP2020524869A (ja) | 仮想マシン管理 | |
| CN110910237B (zh) | 区块链中的数据处理方法、装置及智能终端、存储介质 | |
| WO2016110203A1 (zh) | 一种文件路径的存储和本地文件的访问方法及装置 | |
| CN108289074B (zh) | 用户账号登录方法及装置 | |
| CN113342863B (zh) | 业务单据处理方法、装置、计算机设备和存储介质 | |
| CN107580032B (zh) | 数据处理方法、装置及设备 | |
| US20150058935A1 (en) | Out-of-Path, Content-Addressed Writes with Untrusted Clients | |
| CN106921708B (zh) | 群组管理方法及装置 | |
| WO2023050676A1 (zh) | 对象处理方法以及电子设备 | |
| CN112083972B (zh) | 一种bmc系统配置方法、装置、设备及可读存储介质 | |
| US20170331912A1 (en) | Multi-account login and communication | |
| JP2017517804A (ja) | データ一意性制御及び情報記憶 | |
| CN106993015A (zh) | 交易的同步方法、系统及证券服务器 | |
| JP5528955B2 (ja) | 入力支援装置、入力支援方法、およびプログラム | |
| CN113536326A (zh) | 一种去中心化的协同办公方法、设备及介质 | |
| CN109032694A (zh) | 一种数据加载方法及终端 | |
| CN112015805B (zh) | 一种用户消息同步方法、装置、服务器及计算机存储介质 | |
| HK1228119B (zh) | 并发多业务会话的方法及其系统 | |
| CN115426509B (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: 16737019 Country of ref document: EP Kind code of ref document: A1 |
|
| NENP | Non-entry into the national phase |
Ref country code: DE |
|
| 122 | Ep: pct application non-entry in european phase |
Ref document number: 16737019 Country of ref document: EP Kind code of ref document: A1 |