CN111901403B - Session management method and device, electronic equipment and medium - Google Patents

Abstract

The present disclosure provides a session management method. The method comprises the following steps: responding to a session request for expanding a session for a first service in a user session, and reading information of N data packets needed to be used when the session is carried out for the first service from session configuration information; wherein N is an integer greater than or equal to 1; determining an incremental data packet in the N data packets, wherein the incremental data packet is a data packet which is not loaded into a session object in the N data packets, and the session object is used for managing the user session; and loading the incremental data packet into the session object. The disclosure also provides a session management device, an electronic device and a medium.

Description

Session management method and device, electronic equipment and medium

Technical Field

The present disclosure relates to the field of internet technology, and more particularly, to a session management method, a session management apparatus, an electronic device, and a computer-readable storage medium.

Background

The session object stores attributes and configuration information required for a particular user session for managing the user session in a web application. With the continuous popularization of mobile terminals, users are increasingly popular to obtain services by connecting various application programs on the mobile terminals with a back-end server, the scale is continuously enlarged, and session data is gradually increased, so that the occupied space of session objects is continuously increased, and pressure is gradually generated on the server.

For example, mobile banking is becoming an important platform for electronic banking in the field of network finance. In the prior art, after a user logs in a mobile banking, all session data are loaded into session objects. I.e. all session data is already contained in the session object after user login. With the gradual increase of the number of users, the access of hundreds of millions of users can generate a large number of session objects and occupy a large amount of space, and huge pressure is generated on a background server of a mobile phone bank.

Disclosure of Invention

In view of this, the embodiments of the present disclosure provide a session management method and apparatus, an electronic device, and a medium that can reduce the space occupied by a session object.

In one aspect of the disclosed embodiments, a session management method is provided. The method comprises the following steps: responding to a session request for expanding a session for a first service in a user session, and reading information of N data packets needed to be used when the session is carried out for the first service from session configuration information; wherein N is an integer greater than or equal to 1; determining an incremental data packet in the N data packets, wherein the incremental data packet is a data packet which is not loaded into a session object in the N data packets, and the session object is used for managing the user session; and loading the incremental data packet into the session object.

According to an embodiment of the present disclosure, the method further comprises: creating the session object based on the request for creating the user session; and in response to the creation of the session object, loading a basic data packet into the session object, wherein the basic data packet at least comprises user data required to be used when the user session is created.

According to an embodiment of the present disclosure, the method further comprises: splitting user data related to the user session into a plurality of data packets, wherein the plurality of data packets comprise the N data packets and the basic data packet.

According to an embodiment of the present disclosure, the splitting the user data related to the user session into a plurality of data packets includes: and based on the use frequency and/or the use range of the data, packaging the user data meeting the preset conditions to obtain the basic data packet.

According to an embodiment of the disclosure, the determining the incremental data packet of the N data packets includes: inquiring a loading record of each data packet in the N data packets based on the information of the N data packets, wherein the loading record is used for recording whether the corresponding data packet is loaded into the session object; and determining the data packet which is not loaded into the session object as the incremental data packet based on the loading record.

According to an embodiment of the present disclosure, the N data packets are stored in a distributed cache. The loading the incremental data packet into the session object includes: the distributed cache acquires the incremental data packet and loads the incremental data packet into the session object.

According to an embodiment of the present disclosure, the method further comprises: the session configuration information is configured, wherein the session configuration information comprises information of data packets which are needed to be used when a session is conducted for at least one service, and the first service is any one service in the at least one service.

In another aspect of the disclosed embodiments, a session management apparatus is provided. The device comprises a reading module, a determining module and a first loading module. The reading module is used for responding to a session request for expanding a session for a first service in a user session, and reading information of N data packets needed to be used when the session is carried out for the first service from session configuration information; wherein N is an integer of 1 or more. The determining module is configured to determine an incremental data packet in the N data packets, where the incremental data packet is a data packet in the N data packets that is not loaded into a session object, and the session object is used to manage the user session. The first loading module is used for loading the incremental data packet into the session object.

According to an embodiment of the disclosure, the method further comprises a creation module and a second loading module. The creation module is used for creating the session object based on the request for creating the user session. The second loading module is configured to load a basic data packet into the session object in response to the creation of the session object, where the basic data packet includes at least user data that needs to be used when the user session is created.

According to an embodiment of the disclosure, the apparatus further comprises a splitting module. The splitting module is configured to split user data related to the user session into a plurality of data packets, where the plurality of data packets includes the N data packets and the base data packet.

According to an embodiment of the disclosure, the apparatus further comprises a configuration module. The configuration module is configured to configure the session configuration information, where the session configuration information includes information of a data packet that needs to be used when a session is performed for at least one service, and the first service is any one service of the at least one service.

In another aspect of the disclosed embodiments, an electronic device is provided. The electronic device includes one or more memories, and one or more processors. The memory has stored thereon computer executable instructions. The processor executes the instructions to implement the method as described above.

Another aspect of the disclosed embodiments provides a computer-readable storage medium storing computer-executable instructions that, when executed, are configured to implement a method as described above.

Another aspect of the disclosed embodiments provides a computer program comprising computer executable instructions which, when executed, are for implementing a method as described above.

One or more of the above embodiments have the following advantages or benefits: the method can load data into the session object according to the increment requirement in the user session process, reduce the redundancy of the session object, only load the data required by the session at each time when the data is loaded in the session object, and not load useless data, thereby reducing the size of a single session object and further reducing the storage pressure of a large number of session objects in a server.

Drawings

The above and other objects, features and advantages of the present disclosure will become more apparent from the following description of embodiments thereof with reference to the accompanying drawings in which:

fig. 1 schematically illustrates an application scenario of a session management method and apparatus according to an embodiment of the present disclosure;

FIG. 2 schematically illustrates a flow diagram of a session management method according to an embodiment of the present disclosure;

FIG. 3 schematically illustrates a flow chart of a session management method according to another embodiment of the present disclosure;

FIG. 4 schematically illustrates a flow chart of a session management method according to yet another embodiment of the present disclosure;

FIG. 5 schematically illustrates a flow chart for determining incremental data packets in a session management method according to an embodiment of the disclosure;

FIG. 6 schematically illustrates a flow chart of loading delta data packets into a session object in a session management method according to an embodiment of the present disclosure;

FIG. 7 schematically illustrates one exemplary system architecture to which a session management method according to an embodiment of the present disclosure is applied;

fig. 8 schematically illustrates a block diagram of a session management apparatus according to an embodiment of the present disclosure; and

fig. 9 schematically illustrates a block diagram of an electronic device according to an embodiment of the disclosure.

Detailed Description

Hereinafter, embodiments of the present disclosure will be described with reference to the accompanying drawings. It should be understood that the description is only exemplary and is not intended to limit the scope of the present disclosure. In the following detailed description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the embodiments of the present disclosure. It may be evident, however, that one or more embodiments may be practiced without these specific details. In addition, in the following description, descriptions of well-known structures and techniques are omitted so as not to unnecessarily obscure the concepts of the present disclosure.

The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the disclosure. The terms "comprises," "comprising," and/or the like, as used herein, specify the presence of stated features, steps, operations, and/or components, but do not preclude the presence or addition of one or more other features, steps, operations, or components.

All terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art unless otherwise defined. It should be noted that the terms used herein should be construed to have meanings consistent with the context of the present specification and should not be construed in an idealized or overly formal manner.

Where expressions like at least one of "A, B and C, etc. are used, the expressions should generally be interpreted in accordance with the meaning as commonly understood by those skilled in the art (e.g.," a system having at least one of A, B and C "shall include, but not be limited to, a system having a alone, B alone, C alone, a and B together, a and C together, B and C together, and/or A, B, C together, etc.). Where a formulation similar to at least one of "A, B or C, etc." is used, in general such a formulation should be interpreted in accordance with the ordinary understanding of one skilled in the art (e.g. "a system with at least one of A, B or C" would include but not be limited to systems with a alone, B alone, C alone, a and B together, a and C together, B and C together, and/or A, B, C together, etc.).

In the process of realizing the conception of the present disclosure, the inventor takes mobile banking application as an example to intensively study the reason that the existing session occupies a large space, and found that although the functions provided in mobile banking are numerous, different users can select to use part of the functions according to their own needs after logging in, and not all the functions are always used. In the prior art, after a user logs in a mobile banking, all user data related to a session are loaded into a session object. However, after logging in, different users can choose to use part of the functions according to own requirements, and not all functions are usually used. This results in that most of the user data loaded into the session object is not used for the current transaction, even from the current log-in to log-out operation. This means that only a part of the actually useful user data is loaded into the session object, and that other large amounts of user data have no effect on the user session, but rather result in an increased session footprint. And the access quantity of billions of users in the mobile banking makes billions of session objects occupy huge space.

In view of the fact that different users can select to use part of functions according to own requirements after logging in a mobile phone bank, the inventor considers that the user data needed for the service session can be correspondingly loaded in the session object each time according to the service function selected by the user in the process of the user session, and therefore data redundancy in the session object can be effectively reduced.

Based on the above conception, the embodiment of the disclosure provides a session management method and device, electronic equipment and medium capable of reducing the occupied space of session objects. The method comprises the steps of responding to a session request for a first service to develop a session in a user session, reading information of N data packets needed to be used when the session is conducted for the first service from session configuration information, judging whether the N data packets have data packets which are not loaded in a session object or not, if so, determining the data packets which are not loaded in the session object in the N data packets as incremental data packets, and loading the incremental data packets into the session object.

In this way, the incremental loading of data into the session object according to the requirement in the user session process can be realized, the redundancy of the session object is reduced, only the data required to be used for the session at this time can be loaded when the data is loaded in the session object each time, and unnecessary data is not loaded, so that the size of a single session object can be reduced, and the storage pressure of a large number of session objects in a server is further reduced.

It should be noted that the mobile banking application illustrated above is only one example, and does not limit the present disclosure in any way.

Fig. 1 schematically illustrates an application scenario 100 of a session management method and apparatus according to an embodiment of the present disclosure. It should be noted that fig. 1 is only an example of a system architecture to which embodiments of the present disclosure may be applied to assist those skilled in the art in understanding the technical content of the present disclosure, but does not mean that embodiments of the present disclosure may not be used in other devices, systems, environments, or scenarios.

As shown in fig. 1, an application scenario 100 according to this embodiment may include terminal devices 101, 102, 103, a network 104, and a server (cluster) 105. The network 104 is a medium used to provide communication links between the terminal devices 101, 102, 103 and the server (cluster) 105. The network 104 may include various connection types, such as wired, wireless communication links, or fiber optic cables, among others.

A user may interact with a server (cluster) 105 via a network 104 using terminal devices 101, 102, 103 to receive or send messages etc. Various communication client applications, such as a mobile banking application, a shopping class application, a web browser application, a search class application, an instant messaging tool, a mailbox client, social platform software, etc., may be installed on the terminal devices 101, 102, 103, as examples only.

The terminal devices 101, 102, 103 may be a variety of electronic devices having a display screen and supporting web browsing, including but not limited to smartphones, tablets, laptop and desktop computers, and the like.

The server (cluster) 105 may be a server providing various services, such as a background management server (by way of example only) providing support for websites browsed by users using the terminal devices 101, 102, 103. The background management server may analyze and process the received data such as the user request, and feed back the processing result (e.g., the web page, information, or data obtained or generated according to the user request) to the terminal device.

Upon receiving the user request, the server (cluster) 105 creates a session object for managing the user session while establishing the user session. The session object may load user data used in the user session process. For example, for a mobile banking application, the information in the user data related to the user session may include: user dimension information, such as user account number, mobile phone number, birthday, nationality, occupation, etc.; card holding information of the user, such as information of a deposit card, a credit card, or a financial account; transaction-related information such as the type of the cipher media, transaction-related parameters, or the inquiry operation of the last session, etc.; various types of business (e.g., investment business) information, such as assessment information, user ratings, guest ratings, such as investment history information, etc.

According to various embodiments of the present disclosure, user data related to a user session may be split into individual small data packets. In the process of user session, according to the service selected by the user in the session process, the information of a plurality of data packets needed to be used when the session is performed for the corresponding service is read, then whether the data packets which are not loaded in the session object exist in the plurality of data packets is judged, if so, the data packets which are not loaded in the session object are determined to be incremental data packets, and the incremental data packets are loaded in the session object.

In this way, user data required by the service used by the user can be correspondingly loaded in the session object each time, but not all user data, so that the data can be incrementally loaded in the session object according to the service function selected by the user in the session process.

It should be noted that the session management method provided by the embodiments of the present disclosure may be generally performed by the server (cluster) 105. Accordingly, the session management apparatus provided by the embodiments of the present disclosure may be generally disposed in the server (cluster) 105. The session management method provided by the embodiments of the present disclosure may also be performed by a server or a server cluster that is different from the server (cluster) 105 and is capable of communicating with the terminal devices 101, 102, 103 and/or the server (cluster) 105. Accordingly, the session management apparatus provided by the embodiments of the present disclosure may also be provided in a server or a server cluster, which is different from the server (cluster) 105 and is capable of communicating with the terminal devices 101, 102, 103 and/or the server (cluster) 105.

It should be understood that the number of terminal devices, networks and servers in fig. 1 is merely illustrative. There may be any number of terminal devices, networks, and servers, as desired for implementation.

Fig. 2 schematically illustrates a flow chart of a session management method according to an embodiment of the present disclosure.

As shown in fig. 2, the session management method may include operations S210 to S230.

In operation S210, in response to a session request for expanding a session for a first service in a user session, information of N data packets required to be used when conducting a session for the first service is read from session configuration information; wherein N is an integer of 1 or more. In the operation of the user session process, when a session is to be deployed in the user session process for a first service based on a user selection operation, information of N data packets is read from session configuration information.

The session configuration information may be recorded, for example, in a session configuration file. The various services of the application program can configure the names of the data packets that need to be loaded for transaction according to the requirements of the functions of the application program. Examples of session profiles are as follows:

in operation S220, an incremental data packet of the N data packets is determined, where the incremental data packet is a data packet of the N data packets that is not loaded into a session object, and the session object is used to manage a user session.

In operation S230, the delta packet is loaded into the session object.

After the user establishes a session with the server (cluster) 105 via the terminal devices 101, 102, 103, the user may choose to enter different service functions according to the user operation. According to the embodiment of the disclosure, when a certain service is streamed, the information of a data packet required by the service can be acquired according to session configuration information, and when the data packet which is not loaded in the current session exists in the information, the information is loaded into a session object in an increment mode.

Fig. 3 schematically illustrates a flow chart of a session management method according to another embodiment of the present disclosure.

As shown in fig. 3, the session management method may include operations S310 to S320, and operations S210 to S230.

First, in operation S310, a session object is created based on a request to create a user session. For example, when the server (cluster) 105 receives a login request of a user, a session control session object for managing a user session corresponding to the user is created while a process of the user session is created.

Then in operation S320, in response to the creation of the session object, a base packet is loaded into the session object, the base packet including at least user data that needs to be used when creating the user session.

Next, operations S210 to S230 are performed, and the specific content is the same as the foregoing, and will not be described here again.

In this embodiment, the data in the basic data packet is constantly loaded into the session object, and each service can be directly used without being loaded separately.

According to an embodiment of the present disclosure, a session object is created while a user session is created, and a base packet is loaded in the session object. And then in the subsequent user session process, the data packet is loaded in the session object in an increment mode according to the service selected by the user to enter. In this way, the redundancy of data in the session object can be reduced.

Fig. 4 schematically illustrates a flow chart of a session management method according to a further embodiment of the present disclosure.

As shown in fig. 4, the session management method according to an embodiment of the present disclosure may include operations S410, S310 to S320, S420, and S210 to S230.

First, in operation S410, user data related to a user session is split into a plurality of data packets including N data packets and a base data packet.

According to an embodiment of the present disclosure, splitting user data related to a user session into a plurality of data packets may specifically include encapsulating, based on a frequency of use and/or a range of use of the data, the user data satisfying a preset condition to obtain a base data packet.

For example, user data (e.g., high frequency transaction related data) whose frequency of use is higher than a preset value, or user data whose range of use satisfies certain requirements (e.g., data to which all transactions must be used) may be encapsulated into the base data packet. In one embodiment, the data in the base data packet may include, for example, but is not limited to, a user login account, a user's client version number, a client's IP address, a client number, and the like.

Then, in operation S310, a session object is created based on the request for creating the user session. In response to the creation of the session object, a base packet is loaded into the session object, the base packet including at least user data that needs to be used when creating the user session in operation S320. The specific contents of operations S310 to S320 are described above.

Next, in operation S420, session configuration information is configured, wherein the session configuration information includes information of a data packet that needs to be used when a session is performed for at least one service, and wherein the first service is any one of the at least one service.

According to one embodiment of the present disclosure, operation S320 and operation S420 may be performed simultaneously. That is, after the session object is created, the base packet may be loaded simultaneously and the session configuration information may be configured simultaneously (e.g., a session configuration file is added).

Operations S210 to S230 are then performed so that when a session is deployed for a specific service, if there is an incremental packet in the packets required for the session that is deployed for that service, the incremental packet is loaded in the session object.

Fig. 5 schematically illustrates a flowchart of determining an incremental data packet in operation S220 in a session management method according to an embodiment of the present disclosure.

As shown in fig. 5, operation S220 may include operations S221 to S222 according to an embodiment of the present disclosure.

In operation S221, based on the information of the N data packets, a loading record of each of the N data packets is queried, where the loading record is used to record whether the corresponding data packet is loaded into the session object.

In operation S222, a packet that is not loaded into the session object is determined as an incremental packet based on the loading record. For example, after each data packet is loaded into the session object, the data packet is marked accordingly. Thus, it may be determined whether each data packet is marked by a lookup, and if not, it is determined that the corresponding data packet needs to be loaded into the session object.

Fig. 6 schematically illustrates a flowchart of loading an incremental data packet into a session object in operation S230 in a session management method according to an embodiment of the present disclosure.

As shown in fig. 6, according to an embodiment of the present disclosure, N data packets are stored in a distributed cache, and operation S230 may include operations S231 to S232.

In operation S231, an incremental data packet is acquired from the distributed cache.

In operation S232, the delta packet is loaded into the session object.

According to embodiments of the present disclosure, individual data packets to be loaded into a session object may be cached in a distributed cache system. The distributed cache system can be independent of the server (cluster) 105, so that corresponding data packets are pulled from the distributed cache system to be loaded when the data packets need to be loaded, and the pressure of the server (cluster) 105 in the transaction proceeding process can be effectively relieved.

Fig. 7 schematically illustrates one exemplary system architecture 700 to which the session management method according to an embodiment of the present disclosure is applied.

As shown in fig. 7, in conjunction with fig. 1, the architectural composition of server (cluster) 105 is shown in system architecture 700. In particular, the server (cluster) 105 may be split into a base group server 701 and one or more service group servers 702, with different types of servers being responsible for different service functions. When a user connects with a server (cluster) 105 through a terminal device 101, 102, 103, a session may jump between the various servers in the system architecture 700, depending on the service selected by the user. When the jump occurs, the corresponding session object and session process need to be re-established in the server after the jump.

In the system architecture 700, the base group server 701 is mainly responsible for high frequency transactions such as user login, bank card list, transfer function, inquiring balance, etc. The business group server 702 may be responsible for transactions of a particular business, such as an investment business, a credit card business, or a financing business, for example.

Based on the classification of the server groups in the system architecture 700, the user data related to the user session may be split into multiple tiers accordingly according to the usage scenario of the user session, the servers involved, and the synchronization scope. The user data may be divided into, for example, base group private session data B0, group public session data B1, and service group private session data B2.

The base group private session data B0 contains session data used only in the user session of the base group server 701, such as data used for login transactions. This portion of the data does not relate to synchronization with the service group server 702.

The group public session data B1 may include user data that is used by user sessions in both the base group server 701 and the one or more service group servers 702, such as data used by inter-application communication mechanisms. The data of the part are synchronized among groups, and each group can be acquired and used. In some embodiments, to maintain data consistency, group common session data B1 may be set to be updated only by base group server 701 and then synchronized by traffic group server 702.

The traffic group private session data B2 may contain data that is only used within the respective traffic group server 702 and is not synchronized with other group servers.

Furthermore, the user data of each level can be further divided into a plurality of small data packets according to the function and service classification, such as public data packet of client information, base-pckg of basic data packet, business pckg of data packet, and the like.

The system architecture 700 may also include a distributed cache system 703. The packets in the base group private session data B0, the group public session data B1, and the service group private session data B2 may be stored in the distributed cache system 703 in terms of hierarchical classifications, packet names, and the like.

The basic group server 701 and the service group server 702 may perform the methods of the embodiments of the present disclosure, obtain corresponding data packets from the distributed cache system 703 according to the requirements related to the user session, and load the data packets into respective session objects.

In some embodiments, the base group server 701 and the service group server 702 may also store local sessions in the distributed cache system 703 for updating respective session data, etc.

By splitting the back-end server into a plurality of group servers according to the session hierarchy, the session size can be effectively controlled, memory occupation of each server and server pressure are reduced, the data transmission quantity of session synchronization is reduced, the corresponding speed of functions is increased, and customer experience is improved.

Fig. 8 schematically illustrates a block diagram of a session management apparatus 800 according to an embodiment of the disclosure.

As shown in fig. 8, the session management apparatus 800 may include a reading module 810, a determining module 820, and a first loading module 830 according to an embodiment of the present disclosure. According to further embodiments of the present disclosure, the apparatus 800 may also further include some or all of the creation module 840, the second loading module 850, the splitting module 860, or the configuration module 870. The apparatus 800 may be used to perform the session management method described with reference to fig. 2-7.

The reading module 810 may, for example, perform operation S210, for reading, from session configuration information, information of N data packets that need to be used when conducting a session for a first service, in response to a session request for expanding the session for the first service in a user session; wherein N is an integer of 1 or more.

The determining module 820 may perform, for example, operation S820 to determine an incremental data packet of the N data packets, where the incremental data packet is a data packet of the N data packets that is not loaded into a session object, and the session object is used to manage the user session.

The first loading module 830 may, for example, perform operation S230 for loading the incremental data packet into the session object.

The creation module 840 may perform operation S310, for example, for creating a session object based on a request to create a user session.

The second loading module 850 may, for example, perform operation S320 for loading a base packet into the session object in response to creation of the session object, the base packet including at least user data that needs to be used when creating the user session.

The splitting module 860 may, for example, perform operation S410 for splitting user data related to a user session into a plurality of data packets, the plurality of data packets including N data packets and a base data packet.

The configuration module 870 may perform, for example, operation S420 for configuring session configuration information, where the session configuration information includes information of a data packet that needs to be used when performing a session for at least one service, and the first service is any one service of the at least one service.

Any number of modules, sub-modules, units, sub-units, or at least some of the functionality of any number of the sub-units according to embodiments of the present disclosure may be implemented in one module. Any one or more of the modules, sub-modules, units, sub-units according to embodiments of the present disclosure may be implemented as split into multiple modules. Any one or more of the modules, sub-modules, units, sub-units according to embodiments of the present disclosure may be implemented at least in part as a hardware circuit, such as a Field Programmable Gate Array (FPGA), a Programmable Logic Array (PLA), a system-on-chip, a system-on-substrate, a system-on-package, an Application Specific Integrated Circuit (ASIC), or in any other reasonable manner of hardware or firmware that integrates or encapsulates the circuit, or in any one of or a suitable combination of three of software, hardware, and firmware. Alternatively, one or more of the modules, sub-modules, units, sub-units according to embodiments of the present disclosure may be at least partially implemented as computer program modules, which when executed, may perform the corresponding functions.

For example, any number of the reading module 810, the determining module 820, the first loading module 830, the creating module 840, the second loading module 850, the splitting module 860, and the configuring module 870 may be combined in one module to be implemented, or any one of the modules may be split into a plurality of modules. Alternatively, at least some of the functionality of one or more of the modules may be combined with at least some of the functionality of other modules and implemented in one module. According to embodiments of the present disclosure, at least one of the reading module 810, the determining module 820, the first loading module 830, the creating module 840, the second loading module 850, the splitting module 860, and the configuring module 870 may be implemented at least in part as hardware circuitry, such as a Field Programmable Gate Array (FPGA), a Programmable Logic Array (PLA), a system-on-chip, a system-on-substrate, a system-on-package, an Application Specific Integrated Circuit (ASIC), or in hardware or firmware in any other reasonable manner of integrating or packaging the circuitry, or in any one of or a suitable combination of three of software, hardware, and firmware. Alternatively, at least one of the reading module 810, the determining module 820, the first loading module 830, the creating module 840, the second loading module 850, the splitting module 860, and the configuring module 870 may be at least partially implemented as a computer program module, which when executed, may perform the corresponding functions.

Fig. 9 schematically illustrates a block diagram of an electronic device 900 according to an embodiment of the present disclosure. The electronic device 900 illustrated in fig. 9 is merely an example and should not be construed to limit the functionality and scope of use of embodiments of the present disclosure in any way.

As shown in fig. 9, an electronic device 900 according to an embodiment of the present disclosure includes a processor 901 that can perform various appropriate actions and processes according to a program stored in a Read Only Memory (ROM) 902 or a program loaded from a storage portion 908 into a Random Access Memory (RAM) 903. The processor 901 may include, for example, a general purpose microprocessor (e.g., a CPU), an instruction set processor and/or an associated chipset and/or a special purpose microprocessor (e.g., an Application Specific Integrated Circuit (ASIC)), or the like. Processor 901 may also include on-board memory for caching purposes. Processor 901 may include a single processing unit or multiple processing units for performing the different actions of the method flows according to embodiments of the present disclosure.

In the RAM 903, various programs and data necessary for the operation of the electronic device 900 are stored. The processor 901, the ROM 902, and the RAM 903 are connected to each other by a bus 904. The processor 901 performs various operations of the method flow according to the embodiments of the present disclosure by executing programs in the ROM 902 and/or the RAM 903. Note that the program may be stored in one or more memories other than the ROM 902 and the RAM 903. The processor 901 may also perform various operations of the method flow according to embodiments of the present disclosure by executing programs stored in the one or more memories.

According to an embodiment of the disclosure, the electronic device 900 may also include an input/output (I/O) interface 905, the input/output (I/O) interface 905 also being connected to the bus 904. The system 900 may also include one or more of the following components connected to the I/O interface 905: an input section 906 including a keyboard, a mouse, and the like; an output portion 907 including a display such as a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and a speaker; a storage portion 908 including a hard disk or the like; and a communication section 909 including a network interface card such as a LAN card, a modem, or the like. The communication section 909 performs communication processing via a network such as the internet. The drive 910 is also connected to the I/O interface 905 as needed. A removable medium 911 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is installed as needed on the drive 910 so that a computer program read out therefrom is installed into the storage section 908 as needed.

According to embodiments of the present disclosure, the method flow according to embodiments of the present disclosure may be implemented as a computer software program. For example, embodiments of the present disclosure include a computer program product comprising a computer program embodied on a computer readable storage medium, the computer program comprising program code for performing the method shown in the flowcharts. In such an embodiment, the computer program may be downloaded and installed from the network via the communication portion 909 and/or installed from the removable medium 911. The above-described functions defined in the system of the embodiments of the present disclosure are performed when the computer program is executed by the processor 901. The systems, devices, apparatus, modules, units, etc. described above may be implemented by computer program modules according to embodiments of the disclosure.

The present disclosure also provides a computer-readable storage medium that may be embodied in the apparatus/device/system described in the above embodiments; or may exist alone without being assembled into the apparatus/device/system. The computer-readable storage medium carries one or more programs which, when executed, implement methods in accordance with embodiments of the present disclosure.

According to embodiments of the present disclosure, the computer-readable storage medium may be a non-volatile computer-readable storage medium, which may include, for example, but is not limited to: a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this disclosure, a computer-readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. For example, according to embodiments of the present disclosure, the computer-readable storage medium may include ROM 902 and/or RAM 903 and/or one or more memories other than ROM 902 and RAM 903 described above.

The flowcharts and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams or flowchart illustration, and combinations of blocks in the block diagrams or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

Those skilled in the art will appreciate that the features recited in the various embodiments of the disclosure and/or in the claims may be combined in various combinations and/or combinations, even if such combinations or combinations are not explicitly recited in the disclosure. In particular, the features recited in the various embodiments of the present disclosure and/or the claims may be variously combined and/or combined without departing from the spirit and teachings of the present disclosure. All such combinations and/or combinations fall within the scope of the present disclosure.

The embodiments of the present disclosure are described above. However, these examples are for illustrative purposes only and are not intended to limit the scope of the present disclosure. Although the embodiments are described above separately, this does not mean that the measures in the embodiments cannot be used advantageously in combination. The scope of the disclosure is defined by the appended claims and equivalents thereof. Various alternatives and modifications can be made by those skilled in the art without departing from the scope of the disclosure, and such alternatives and modifications are intended to fall within the scope of the disclosure.

Claims (7)

1. A session management method, comprising:

based on a request for creating a user session, creating a session object for managing the user session while the user session is being created; the session object can load user data used in the user session;

in response to creation of the session object, loading a basic data packet into the session object and adding a session configuration file, wherein session configuration information is recorded in the session configuration file, information of a data packet which needs to be loaded when a session is unfolded for a plurality of services is recorded in the session configuration information, and the basic data packet at least comprises user data which needs to be used when the user session is created and data which is necessarily used by the plurality of services;

responding to a session request for expanding a session for a first service in a user session, and reading information of N data packets needed to be used when the session is carried out for the first service from session configuration information; wherein N is an integer greater than or equal to 1; wherein the first service is any one service among the plurality of services;

determining an incremental data packet in the N data packets, wherein the incremental data packet is a data packet which is not loaded in the session object in the N data packets, and inquiring a loading record of each data packet in the N data packets based on the information of the N data packets, wherein the loading record is used for recording whether the corresponding data packet is loaded in the session object; determining a data packet which is not loaded into the session object as the incremental data packet based on the loading record; after each data packet is loaded to the session object, the data packet is marked correspondingly; and

and loading the incremental data packet into the session object.

2. The method of claim 1, wherein the method further comprises:

splitting user data related to the user session into a plurality of data packets, wherein the plurality of data packets comprise the N data packets and the basic data packet.

3. The method of claim 2, wherein the splitting user data related to the user session into a plurality of data packets comprises:

and based on the use frequency and/or the use range of the data, packaging the user data meeting the preset conditions to obtain the basic data packet.

4. The method of claim 1, wherein the N data packets are stored in a distributed cache; the loading the incremental data packet into the session object includes:

acquiring the incremental data packet from the distributed cache; and

and loading the incremental data packet into the session object.

5. A session management apparatus comprising:

the creation module is used for creating a session object for managing the user session while the user session is established based on a request for creating the user session; the session object can load user data used in the user session;

the second loading module is used for responding to the creation of the session object and loading a basic data packet into the session object, wherein the basic data packet at least comprises user data required to be used when the user session is created and data which are necessarily used by a plurality of services;

the configuration module is used for adding a session configuration file, wherein session configuration information is recorded in the session configuration file, and the session configuration information is recorded with information of data packets which need to be loaded when the session is unfolded for the plurality of services;

the reading module is used for responding to a session request for expanding a session for a first service in a user session, and reading information of N data packets needed to be used when the session is carried out for the first service from session configuration information; wherein N is an integer greater than or equal to 1; wherein the first service is any one service among the plurality of services;

the determining module is used for determining an incremental data packet in the N data packets, wherein the incremental data packet is a data packet which is not loaded into the session object in the N data packets; based on the information of the N data packets, inquiring a loading record of each data packet in the N data packets, wherein the loading record is used for recording whether the corresponding data packet is loaded into the session object; determining a data packet which is not loaded into the session object as the incremental data packet based on the loading record; after each data packet is loaded to the session object, the data packet is marked correspondingly; and

and the first loading module is used for loading the incremental data packet into the session object.

6. An electronic device, comprising:

one or more memories having computer-executable instructions stored thereon;

one or more processors executing the instructions to implement the method of any of claims 1-4.

7. A computer readable storage medium having stored thereon executable instructions which, when executed by a processor, cause the processor to perform the method according to any of claims 1-4.