Business data management method, device, equipment and storage medium for business SBB

Abstract

The embodiment of the present invention provides a business data management method, device, equipment and storage medium for a business SBB, which can extend the business data setting interface. When the business data needs to be set, the business data setting instruction can be received through the business data setting interface, and according to the business identification information and the business data to be set in the business data setting instruction, the business data to be set is added to the business data set of the business corresponding to the business identification information; thereby improving the convenience and efficiency of business data setting; and when it is detected that the business SBB needs to configure business data, the corresponding business data can be directly configured for the business SBB from the business data set corresponding to the business SBB, that is, the set business data can take effect immediately and can be called by the corresponding SBB in real time, further improving the real-time nature of business data setting and effectiveness.

Description

Technical Field

[0001] The present invention relates to the field of communication technology, and in particular to a service data management method, device, equipment and storage medium of a service SBB (Service Building Block). Background Art

[0002] JSLEE (JAIN (Java APIs for Integrated Networks, JAVA application programming interface for intelligent networks) SLEE (Service Logic Execution Environment) technology, abbreviated as JSLEE) defines a system architecture specification for development. As long as the services developed by various manufacturers comply with the JSLEE specification, they can run in the JSLEE container.

[0003] At present, the JSLEE specification provides a way to configure the call entry env-entry in the sbb-jar.xml file for the business SBB. In this way, after the business SBB is installed, the business data of the business SBB cannot be modified and can only be read through the directory interface JNDI. To modify the business data of the business SBB, you can only uninstall the business, modify the sbb-jar.xml in the business du package, and then reinstall the business. It can be seen that the current business data setting operation of the business SBB is cumbersome and inefficient, and it is impossible to set the business data when the business is running, which affects the operation of the business. Summary of the invention

[0004] The embodiments of the present invention provide a method, device, equipment and storage medium for managing business data of a business SBB, which solves the problem in related technologies that the setting of business data of the business SBB requires uninstalling and reinstalling the business, resulting in cumbersome operations, low efficiency and affecting the normal operation of the business.

[0005] In order to solve the above technical problems, an embodiment of the present invention provides a service data management method of a service SBB, comprising:

[0006] Receiving a service data setting instruction through a service data setting interface, wherein the service data setting instruction includes service identification information and service data to be set;

[0007] Adding the service data to be set in the service data set of the service corresponding to the service identification information;

[0008] When the service SBB needs to be configured with service data, the corresponding service data is configured for the service SBB from the service data set corresponding to the service SBB.

[0009] In order to solve the above technical problems, an embodiment of the present invention provides a service data management device for a service SBB, comprising:

[0010] A receiving module, configured to receive a service data setting instruction through a service data setting interface, wherein the service data setting instruction includes service identification information and service data to be set;

[0011] The management module is used to add the business data to be set in the business data set of the business corresponding to the business identification information, and to configure the corresponding business data for the business SBB from the business data set corresponding to the business SBB when the business SBB needs to configure business data.

[0012] To solve the above technical problems, an embodiment of the present invention further provides a communication device, including a processor, a memory and a communication bus;

[0013] The communication bus is used to connect the processor and the memory;

[0014] The processor is used to execute the computer program stored in the memory to implement the steps of the service data management method of the service SBB as described above.

[0015] To solve the above technical problems, an embodiment of the present invention further provides a computer-readable storage medium, which stores one or more computer programs. The one or more computer programs can be executed by one or more processors to implement the steps of the business data management method of the business SBB as described above.

[0016] Beneficial Effects

[0017] According to the business data management method, device, equipment and storage medium of the business SBB provided in the embodiment of the present invention, the business data setting interface can be extended. When the business data needs to be set, the business data setting instruction can be received through the business data setting interface. According to the business identification information and the business data to be set in the business data setting instruction, the business data to be set is added to the business data set of the business corresponding to the business identification information, so as to realize the setting of the business data of the business SBB, and there is no need to uninstall and reinstall the business, thereby improving the convenience and efficiency of the business data setting, and avoiding the situation that the business cannot run normally due to the uninstallation of the business; and when the business SBB needs to configure the business data, the corresponding business data can be configured for the business SBB directly from the business data set corresponding to the business SBB, that is, the set business data can take effect immediately and can be called by the corresponding SBB in real time, further improving the real-time nature of the business data setting and effectiveness.

[0018] Other features and corresponding beneficial effects of the present invention are described in the latter part of the specification, and it should be understood that at least part of the beneficial effects become obvious from the description in the specification of the present invention. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] Figure 1 This is a flow chart of a method for managing business data of a business SBB according to a first embodiment of the present invention;

[0020] Figure 2 This is a schematic diagram of a business data query process in accordance with the first embodiment of the present invention;

[0021] Figure 3 A schematic diagram of a business data deletion process according to a first embodiment of the present invention;

[0022] Figure 4 This is a schematic diagram of a service data clearing process according to Embodiment 1 of the present invention;

[0023] Figure 5 This is a schematic diagram of the operating state of the second embodiment of the present invention;

[0024] Figure 6-1 Schematic diagram of the service parameter configuration interface of the second embodiment of the present invention Figure 1 ;

[0025] Figure 6-2 Schematic diagram of the service parameter configuration interface of the second embodiment of the present invention Figure 2 ;

[0026] Figure 7 This is a schematic diagram of the structure of a service data management device for service SBB according to Embodiment 3 of the present invention;

[0027] Figure 8 This is a schematic diagram of the structure of a communication device according to Embodiment 4 of the present invention. DETAILED DESCRIPTION

[0028] In order to make the purpose, technical solution and advantages of the present invention more clearly understood, the following is a further detailed description of the embodiments of the present invention through specific implementation methods combined with the accompanying drawings. It should be understood that the specific embodiments described herein are only used to explain the present invention and are not used to limit the present invention.

[0029] Embodiment 1:

[0030] The current setting of business data for the SBB service requires uninstalling and reinstalling the service, which results in cumbersome operations, low efficiency, and affects the normal operation of the service. This embodiment can extend the business data setting interface. When the business data needs to be set, the business data can be set through the business data setting interface without uninstalling and reinstalling the service, thereby improving the convenience and efficiency of business data setting and ensuring the normal operation of the SBB service. When it is detected that the business SBB needs to configure business data, the corresponding business data can be directly configured for the business SBB from the business data set corresponding to the business SBB, further improving the real-time nature of business data setting and effectiveness. For ease of understanding, this embodiment is described below in conjunction with Figure 1 The business data management method of the business SBB shown is described as an example.

[0031] See also Figure 1 As shown, the service data management method of the service SBB provided in this embodiment includes:

[0032] S101: receiving a service data setting instruction through a service data setting interface, wherein the service data setting instruction includes service identification information and service data to be set.

[0033] The business data setting interface in this embodiment is an extended interface, and it can be flexibly set according to the language used in the development technology. For example, for an open architecture and system using JAVA, the business data setting interface can be extended at the MBeanServer layer, that is, the business data setting interface is an extended MBean interface.

[0034] The business data setting instructions in this embodiment may be, but are not limited to, sent by the configuration client, and the configuration client may also be flexibly set according to specific application scenarios. For example, for an open architecture and system using JAVA, the configuration client may be, but is not limited to, a JMX (Java Management Extensions) client. Of course, in some examples, the business data setting instructions may also be flexibly issued when needed through other devices other than the configuration client.

[0035] In this embodiment, the service identification information included in the service data setting instruction is the service identification of the service for which the service data is to be set, and the service identification can be used to determine which service or services need to set the service data. It should be understood that the service data to be set in this embodiment can be at least one of any data that the service SBB needs to call. It should be understood that in this embodiment, a service data setting instruction can be set to include only one service identification information, that is, the service data of one service is set through one service data setting instruction; in other examples, a service data setting instruction can also be set to include only two or more service identification information, so as to achieve the setting of service data for multiple services.

[0036] The business data to be set included in the business data setting instruction in this embodiment is also the business data to be added. According to the above example, the business data to be set included in the business data setting instruction in this embodiment can be business data of one business or business data of multiple businesses, which can be flexibly set according to needs.

[0037] S102: Add the business data to be set to the business data set of the business corresponding to the business identification information in the business data setting instruction.

[0038] In this embodiment, the business data corresponding to each business respectively constitutes the business data set corresponding to each business. That is, in this embodiment, the same business identifier, such as business ID, can be set for each business data in the business data set of a business, so that the business data with the same business ID constitutes the business data set of a business.

[0039] It should be understood that the business data in the business data set corresponding to a certain business may be empty, or may be one, or multiple, etc. And in this embodiment, according to the business identification information and the business data, the way of adding business data to the business data set of the business corresponding to the business identification information can also be flexibly set. For example, an example setting process may include but is not limited to:

[0040] A version number is set for the business data last added to the business data set of the business, and the business data to be set in the received business data setting instruction is added to the business data set of the business, that is, for the business data in a business data set, except for the latest business data set, the previously set business data are all set with corresponding version numbers (of course, in some instances, a version number can also be set for the latest business data set or an identifier used to identify it as the latest business data set). In this embodiment, after the business data to be set in the business data setting instruction is added to the business data set of the business, it can also include storing the business data to be set in a storage file used for persistent storage of business data, so that the business data previously configured by the business can be obtained when the system is restarted.

[0041] S103: When the service SBB needs to be configured with service data, the corresponding service data is configured for the service SBB from the service data set corresponding to the service SBB.

[0042] For example, in some instances, the steps in S103 may include the following situations:

[0043] After setting a version number for the last added business data in the business data set of the business in the above S102, when it is detected that there are currently business SBBs with no bound version number in the business SBB corresponding to this business, the last added business data can be allocated to these business SBBs, and these business SBBs can be bound to the version number set for the last added business data.

[0044] In other examples of this embodiment, a business data acquisition interface can be extended, and the business data acquisition interface can be used by the business SBB to obtain corresponding business data; that is, the business SBB can call business data through the business data acquisition interface, and when necessary, the business SBB sends a business data acquisition request through the business data acquisition interface, and the business data acquisition request may include business identification information. At this time, when the business SBB needs to configure business data in S103, configuring the corresponding business data for the business SBB from the business data set corresponding to the business SBB may also include the following situations:

[0045] When a service data acquisition request sent by a service SBB is received through the service data acquisition interface, corresponding service data can be allocated to the service SBB from the service data set of the corresponding service according to the service identification information in the service data acquisition request.

[0046] In an example of this embodiment, according to the service identification information in the service data acquisition request, allocating corresponding service data to the service SBB from the service data set of the corresponding service may include:

[0047] When the version number is included in the business data acquisition request (that is, the business SBB is already bound to the version number), the business data corresponding to the version number is allocated to the business SBB from the business data set of the business corresponding to the business identification information in the business data acquisition request; otherwise, it indicates that the business SBB is not currently bound to the version number, and the latest added business data is allocated to the business SBB from the business data set of the business corresponding to the business identification information in the business data acquisition request, that is, the most recent business data is allocated to the business SBB.

[0048] Optionally, in some examples of this embodiment, the business data query interface can be extended, and when necessary, the business data query instruction can be issued through the business data query interface to query the corresponding business data. The business data query interface in this embodiment can also be flexibly set according to the language used in the development technology. For example, for an open architecture and system using JAVA, the business data query interface can be extended at the MBean Server layer, that is, the business data query interface can also be an extended MBean interface. In this example, the business data management method of the business SBB is shown in Figure 2 As shown, it may also include:

[0049] S201: receiving a business data query instruction through a business data query interface, where the business data query instruction includes indication information of the business data to be queried.

[0050] The service data query instruction in this example may be sent by the configuration client through the service data query interface, or may be sent by other devices. The indication information of the service data to be queried may include the service ID of the service to be queried, or the service ID and version number, etc.

[0051] S202: Feedback the service data corresponding to the indication information of the service data to be queried to the querying party.

[0052] Optionally, in some examples of this embodiment, the business data deletion interface can be extended, and when necessary, the business data deletion instruction can be issued through the business data deletion interface to delete the corresponding business data. The business data deletion interface in this embodiment can also be flexibly set according to the language used in the development technology. For example, for an open architecture and system using JAVA, the business data deletion interface can also be extended at the MBean Server layer, that is, the business data deletion interface can also be an extended MBean interface. In this example, the business data management method of the business SBB is described in detail in the following. Figure 3 As shown, it may also include:

[0053] S301: receiving a business data deletion instruction through a business data deletion interface, where the business data deletion instruction includes indication information of the business data to be deleted.

[0054] The service data deletion instruction in this example may be sent by the configuration client through the service data deletion interface, or may be sent by other devices. The indication information of the service data to be deleted may include the service ID of the service to be deleted, or the service ID and version number, etc.

[0055] S302: Deleting the business data to be deleted according to the indication information of the business data to be deleted.

[0056] In an example of this embodiment, the deletion process of the to-be-deleted service data according to the indication information of the to-be-deleted service data in S302 may include but is not limited to:

[0057] When it is determined that the business data to be deleted indicated by the indication information of the business data to be deleted is currently called by the business SBB, the business data called by the business SBB that currently calls the business data to be deleted is cleared, and when the business data to be deleted is the latest business data added, a version number is set for the business data to be deleted; in some instances, the determined data to be deleted can be directly deleted, and in other examples, the business data to be deleted can also be cleared uniformly through the background later, and when the business data is stored in the storage file, it is also cleared from the storage file.

[0058] For example, in some examples of this embodiment, the service data that is not currently called by the service SBB and the version number of the service data that is not currently called by the service SBB in the service data set of the service may also be deleted according to a set rule (such as timing). Figure 4 The unified clearing process of business data shown includes:

[0059] S401: Extract the version numbers of the current business data in the business data set of the business according to the set rules to obtain a first version number set, and extract the version numbers currently bound to each business SBB corresponding to the business to obtain a second version number set; the second version number set must be a subset of the first version number set.

[0060] The setting rule in this embodiment may be timed extraction, for example, every 2 minutes, 3 minutes, 5 minutes or 10 minutes.

[0061] S402: Obtain the absolute complement of the second version number set in the first version number set, and delete the obtained version numbers in the absolute complement set and the business data corresponding to the version numbers in the absolute complement set. This step also deletes the business data corresponding to the version numbers in the first version number set that do not exist in the second version number set (indicating that the business data corresponding to these version numbers are not called by the business SBB, that is, they are unnecessary business data).

[0062] That is, the business data management method of the business SBB provided in this embodiment can use the above-mentioned extended business data setting interface, business data query interface, business data deletion interface, business data acquisition interface and other interfaces for business management data. The business SBB can obtain the corresponding business data through the business data acquisition interface, and can also configure the client and the business data setting interface, business data query interface, and business data deletion interface to increase, query and delete business data. There is no need to uninstall and reinstall the business, which can improve the real-time nature of business data setting and effectiveness.

[0063] Embodiment 2:

[0064] For ease of understanding, this embodiment below is based on the above embodiment 1, combined with the system architecture specification defined and developed by JSLEE, and the JSLEE container involved in the business data management method of the business SBB illustrated in the above embodiment to illustrate.

[0065] In this embodiment, a business data acquisition interface is added to the SbbContext interface, and the business SBB can use the business data acquisition interface to obtain business data; in this embodiment, a JMX management interface is provided, including a business data setting interface, a business data query interface, and a business data deletion interface, and business data can be directly set, queried or deleted through the JMX client. This makes it easy to achieve flexible management of business data and takes effect immediately without uninstalling and reinstalling the business.

[0066] In this embodiment, the setting of business data can be during the operation of the business or when the business is not running. Of course, during the operation of the business, since the business SBB itself is stateless, the corresponding business data may be obtained multiple times during the operation of the business SBB. Therefore, in order to ensure the consistency of the business data, that is, to ensure that when setting, the business data obtained by the currently running business SBB is the configuration value before the modification, and the data obtained by the newly triggered new business SBB after the business data setting is completed is the configuration value after the modification; there should not be a running business SBB where the business data obtained before and after are not of the same version (in this example, each time the management data is set, a version is generated).

[0067] For example, in one application scenario, the following extensions can be made to the JSLEE1.1 specification interface:

[0068] A business data acquisition interface for acquiring business data is added to the SbbContext interface in the JSLEE specification (the business data acquisition interface is provided for use by the business SBB), so that the business SBB can obtain the latest business data in real time through the business data acquisition interface.

[0069] For example, suppose the SbbContext interface defined in the JSLEE model in an example is as follows:

[0070]

[0071]

[0072] The description of the above interface (SbbContext interface) is as follows:

[0073]

[0074] In this example, the above SbbContext interface is extended as follows:

[0075]

[0076] In the above extended interface, getServiceData is a service data acquisition interface: it is used to obtain a service data value of a service corresponding to the service SBB. The parameter name can be the name of the service data, and the value corresponding to the service data is returned.

[0077] In this embodiment, the JSLEE standardized business management MBean interface can also be expanded to add business data operation related interfaces, including business data setting interface, business data query interface, and business data deletion interface, thereby providing business data setting, deletion, and query through JMX.

[0078] For example, the business management interface defined in the JSLEE specification is as follows:

[0079]

[0080] An example of the above service management interface (ServiceManagementMBean interface) is as follows:

[0081]

[0082]

[0083] In this embodiment, the extended service management interface is as follows:

[0084]

[0085] The new interface descriptions of the business management interface are as follows:

[0086] getServiceProperties, that is, the business data query interface: it can be used to obtain the business data corresponding to a certain business. The parameter id can represent the business ID. It returns the content of all business data of the business (it can also obtain the business data of a specific version of the business), which can be expressed in the form of ConfigProperties.

[0087] setServiceProperties, the service data setting interface: can be used to set the service data corresponding to a certain service. The parameter id represents the service ID, and the parameter properties represents the service data content after setting.

[0088] removeServiceProperties, that is, the business data deletion interface: it is used to delete the business data corresponding to a certain business. The parameter id represents the business ID.

[0089] Based on the above example settings and application scenarios, a schematic diagram of the running status of a JMX client and server can be found in Figure 5 As shown, the JMX client (also an example configuration client) and the server (with a JSLEE container) cooperate to complete the remote call of querying, setting, and deleting business data.

[0090] The business data section in the figure is responsible for the maintenance of business data, including the maintenance of multiple versions of the same business data (for example Figure 5 Business data A1 and business data A2 represent different versions of management data of business A; business data B1 and business data B2 represent different versions of management data of business B), and the latest business data is persisted in the storage file.

[0091] The SBB entity part is responsible for providing the business SBB with the business data of the corresponding business version. The specific implementation logic may include:

[0092] In order to ensure the consistency of business data, that is, the business data obtained during the operation of a business can only be the data modified at the same time, it is necessary to manage multiple versions of the business data of each business. In addition to the latest version of the business data, the old version of the business data set previously needs to be saved in the memory, so that when the business data is modified, the currently running business SBB can also obtain the old version of the business data;

[0093] The business data query interface can be used to query the latest version of business data of each business in memory, all business data, or other specified versions of business data;

[0094] Business data can be set through the business data setting interface. In this example, a version number can be first generated for the business data that was last set for the business that needs to be set, and then all current business SBBs of this business can be traversed. If a business SBB has not been bound to a version number, the newly generated version number will be bound to it; for business SBBs that have already been bound to a version number, they will be ignored (indicating that the business data used by this business SBB is the business data corresponding to the version number before the current version number); then the latest business data of this business is updated to the business data to be set, and the latest business data is updated to the storage file of persistent storage for acquisition when the system is restarted.

[0095] Business SBB can obtain the corresponding business data through the business data acquisition interface. In this example, you can first determine whether the SBB entity corresponding to the business SBB has been bound to the version number of the business data. If it has been bound, obtain the business data corresponding to this version number; otherwise, obtain the latest business data corresponding to the business.

[0096] The corresponding business data can be deleted through the business data deletion interface. For example, when the latest business data needs to be deleted (that is, the data to be deleted is the latest business data in the society), a version number is generated for the latest business data to be deleted, and the business SBB is traversed to confirm which business SBBs are using the latest business data, and the business data called by these business SBBs are updated to empty, and the corresponding latest business data in the storage file is also deleted; the actual deletion of the latest business data in the memory can be performed when the background timer is running.

[0097] As the system runs, there may be more and more versions of business data. Therefore, in the embodiment, old version data that is not in use or the latest version of data that currently needs to be deleted can be cleared; a timer runs in the background (for example, it can be performed every 5 minutes), traverses all SBB entities of a business, records the version numbers bound to all SBB entities to obtain a second version number set, and compares it with the version numbers in the first version number set composed of all version numbers of the business data of the business. If version number A in the first version number set is not in the second version number set (that is, the currently bound version number set), version number A and the business data corresponding to version number A are cleared.

[0098] Based on the above principle, an example of configuring the service data of service A (ie Figure 6-1 and Figure 6-2 For the OMM (Oracle Metadata Management) management interface of the business management data in Figure 6-1 and Figure 6-2As shown, in the OMM management interface, the business management data of business A can be set. The business SBB of business A uses a code for business data as follows:

[0099] Object value=((SbbContextExt)this.sbbContext).getServiceData(key);

[0100] It can be seen that through the extended JSLEE specification provided by this implementation, the business SBB can obtain the corresponding business data through the business data acquisition interface, and can also use the corresponding configuration client and business data setting interface, business data query interface, and business data deletion interface to implement business data addition, query, and deletion. There is no need to uninstall and reinstall the business, which can improve the real-time nature of business data setting and effectiveness.

[0101] Embodiment three:

[0102] This embodiment provides a service data management device for a service SBB. The service data management device for the service SBB can be set in a communication device, and the communication device can be a communication device serving as a server. Figure 7 As shown, it includes:

[0103] The receiving module 701 is used to receive a business data setting instruction through a business data setting interface, wherein the business data setting instruction includes business identification information and business data to be set. The business data setting interface in the present embodiment is an extended interface, and it can be flexibly set according to the language adopted by the development technology. The business data setting instruction in the present embodiment can be, but not limited to, sent by the configuration client, and the configuration client can also be flexibly set according to the specific application scenario. For example, for an open architecture and system using JAVA, the configuration client can be, but not limited to, a JMX (Java Management Extensions) client. Of course, in some examples, the business data setting instruction can also be flexibly issued when needed by other devices other than the configuration client. In the present embodiment, the business identification information included in the business data setting instruction is the business identification of the business to be set for the business data, and it can be determined according to the business identification which business or businesses need to perform business data setting. And it should be understood that the business data to be set in the present embodiment can be at least one of any data that the business SBB needs to call. And it should be understood that, in this embodiment, a business data setting instruction can be set to include only one business identification information, that is, the business data of one business is set through one business data setting instruction; in other examples, a business data setting instruction can also be set to include only two or more business identification information, so as to achieve the setting of business data for multiple businesses. The business data included in the business data setting instruction in this embodiment is the business data to be set, and the setting here is also an increase. According to the above examples, it can be seen that the business data to be set included in the business data setting instruction in this embodiment can be the business data of one business, or it can be the business data of multiple businesses, and it can be flexibly set according to needs.

[0104] Management module 702 is used to add the business data to be set in the business data set corresponding to the business identification information in the business data setting instruction, and to configure the corresponding business data for the business SBB from the business data set corresponding to the business SBB when the business SBB needs to configure business data.

[0105] In this embodiment, the business data corresponding to each business respectively constitute the business data set corresponding to each business. That is, in this embodiment, the same business identifier can be set for each business data in the business data set of a business. It should be understood that the business data in the business data set corresponding to a certain business may be empty, or may be 1, or more, etc. And in this embodiment, according to the business identification information and business data, the method of adding business data to the business data set of the business corresponding to the business identification information can also be flexibly set. For example, an example setting process may include but is not limited to:

[0106] The management module 702 sets a version number for the business data added last time in the business data set of the business, and adds the business data to be set in the received business data setting instruction to the business data set of the business. In this embodiment, after the management module 702 adds the business data to be set in the business data setting instruction to the business data set of the business, it can also include storing the business data to be set in a storage file for persistent storage of business data, so that the business data previously configured by the business can be obtained when the system is restarted.

[0107] In one example, after the management module 702 sets a version number for the last business data added to the business data set of the business, when there are business SBBs that are not bound to a version number in the business SBB corresponding to the business, the last business data added can be allocated to these business SBBs, and these business SBBs can be bound to the version number set for the last business data added.

[0108] In other examples of this embodiment, the business data acquisition interface can be extended, and the business data acquisition interface can be used by the business SBB to obtain the corresponding business data; that is, the business SBB can call the business data through the business data acquisition interface, and when necessary, the business SBB sends a business data acquisition request through the business data acquisition interface, and the business data acquisition request may include business identification information. At this time, when the management module 702 detects that the business SBB needs to configure business data, the corresponding business data configured for the business SBB from the business data set corresponding to the business SBB may also include the following situation: when the management module 702 receives the business data acquisition request sent by the business SBB through the business data acquisition interface, the corresponding business data can be allocated to the business SBB from the business data set of the corresponding business according to the business identification information in the business data acquisition request.

[0109] In an example of the present embodiment, the management module 702 allocates corresponding business data to the business SBB from the business data set of the corresponding business according to the business identification information in the business data acquisition request, which may include: when the management module 702 includes a version number in the business data acquisition request (that is, the business SBB is already bound to the version number), the business data corresponding to the version number is allocated to the business SBB from the business data set of the business corresponding to the business identification information in the business data acquisition request; otherwise, it indicates that the business SBB is not currently bound to a version number, and the newly added business data is allocated to the business SBB from the business data set of the business corresponding to the business identification information in the business data acquisition request, that is, the most recent business data is allocated to the business SBB.

[0110] Optionally, in some examples of this embodiment, a business data query interface may be extended, and a business data query instruction may be issued through the business data query interface to query the corresponding business data when necessary. In this example, the management module 702 receives the business data query instruction through the business data query interface, and the business data query instruction includes the indication information of the business data to be queried. The management module 702 feeds back the business data corresponding to the indication information of the business data to be queried to the querying party.

[0111] Optionally, in some examples of this embodiment, a business data deletion interface can be extended, and a business data deletion instruction can be issued through the business data deletion interface to delete the corresponding business data when necessary. In this example, the management module 702 receives the business data deletion instruction through the business data deletion interface, and the business data deletion instruction includes indication information of the business data to be deleted. The business data deletion instruction in this example can be sent by the configuration client through the business data deletion interface, or it can be sent by other devices. The management module 702 deletes the business data to be deleted according to the indication information of the business data to be deleted.

[0112] In an example of the present embodiment, the management module 702 may delete the business data to be deleted according to the indication information of the business data to be deleted, including but not limited to: when the management module 702 determines that the business data to be deleted corresponding to the indication information of the business data to be deleted is currently called by the business SBB, the business data called by the business SBB that currently calls the business data to be deleted is cleared, and when the business data to be deleted corresponding to the indication information of the business data to be deleted is the currently latest set business data, a version number is set for the business data to be deleted; in some instances, the determined data to be deleted can be directly deleted, and in other examples, the business data to be deleted can also be cleared uniformly through the background later, and when the business data is stored in the storage file, it is also cleared together in the storage file.

[0113] For example, in some examples of the present embodiment, the management module 702 is also used to delete the business data that is not currently called by the business SBB and the version number of the business data that is not currently called by the business SBB in the business data set of the business according to the set rules (such as timing). For example, an example implementation method may be that the management module 702 can periodically extract the version number of each current business data in the business data set of the business to obtain a first version number set, and extract the version number currently bound to each business SBB corresponding to the business to obtain a second version number set, and then obtain the absolute complement of the second version number set in the first version number set, and delete the business data corresponding to the version number in the absolute complement. That is, the business data corresponding to the version numbers in the first version number set that do not exist in the second version number set (indicating that the business data corresponding to these version numbers have not been called by the business SBB, that is, unnecessary business data) are deleted.

[0114] The business data management device of the business SBB provided in this embodiment can use the above-mentioned extended business data setting interface, business data query interface, business data deletion interface, business data acquisition interface and other interfaces for business management data. The business SBB can obtain the corresponding business data through the business data acquisition interface, and can also configure the client and the business data setting interface, business data query interface, and business data deletion interface to increase, query and delete business data. There is no need to uninstall and reinstall the business, which can improve the real-time nature of business data setting and effectiveness.

[0115] Embodiment 4:

[0116] This embodiment also provides a communication device, which can be a device serving as a server. Figure 8 As shown, it includes a processor 801, a memory 802 and a communication bus 803;

[0117] The communication bus 803 is used to realize the communication connection between the processor 801 and the memory 802;

[0118] In an example, the processor 801 may be used to execute one or more computer programs stored in the memory 802 to implement the steps of the service data management method of the service SBB in the above embodiments.

[0119] In this example, when the service data management device of the service SBB is provided in the communication device, the function of at least one module of the service data management device of the service SBB can be realized by the processor.

[0120] The present embodiment also provides a computer-readable storage medium, which includes volatile or non-volatile, removable or non-removable media implemented in any method or technology for storing information (such as computer-readable instructions, data structures, computer program modules or other data). Computer-readable storage media include, but are not limited to, RAM (Random Access Memory), ROM (Read-Only Memory), EEPROM (Electrically Erasable Programmable read only memory), flash memory or other memory technology, CD-ROM (Compact Disc Read-Only Memory), digital versatile disk (DVD) or other optical disk storage, magnetic cassette, magnetic tape, magnetic disk storage or other magnetic storage device, or any other medium that can be used to store desired information and can be accessed by a computer.

[0121] In one example, the computer-readable storage medium in this embodiment may be used to store one or more computer programs, and the one or more computer programs may be executed by one or more processors to implement the steps of the business data management method of the business SBB in the above embodiments.

[0122] This embodiment also provides a computer program (or computer software), which can be distributed on a computer-readable medium and executed by a computing device to implement at least one step of the business data management method of the business SBB as shown in the above embodiments; and in some cases, at least one of the steps shown or described can be executed in an order different from that described in the above embodiments.

[0123] This embodiment further provides a computer program product, including a computer readable device, on which the computer program shown above is stored. In this embodiment, the computer readable device may include the computer readable storage medium shown above.

[0124] It can be seen that those skilled in the art should understand that all or some of the steps, systems, and functional modules / units in the above disclosed methods can be implemented as software (which can be implemented with computer program code executable by a computing device), firmware, hardware, and appropriate combinations thereof. In hardware implementations, the division between the functional modules / units mentioned in the above description does not necessarily correspond to the division of physical components; for example, a physical component can have multiple functions, or a function or step can be performed by several physical components in cooperation. Some or all physical components can be implemented as software executed by a processor, such as a central processing unit, a digital signal processor, or a microprocessor, or implemented as hardware, or implemented as an integrated circuit, such as an application-specific integrated circuit.

[0125] In addition, it is well known to those skilled in the art that communication media generally contain computer readable instructions, data structures, computer program modules or other data in modulated data signals such as carrier waves or other transmission mechanisms, and may include any information delivery media. Therefore, the present invention is not limited to any specific hardware and software combination.

[0126] The above contents are further detailed descriptions of the embodiments of the present invention in combination with specific implementation methods, and it cannot be determined that the specific implementation of the present invention is limited to these descriptions. For ordinary technicians in the technical field to which the present invention belongs, several simple deductions or substitutions can be made without departing from the concept of the present invention, which should be regarded as falling within the protection scope of the present invention.

Claims

1. A business data management method for business SBB, characterized in that: include: Receiving a service data setting instruction through a service data setting interface, wherein the service data setting instruction includes service identification information and service data to be set; Setting a version number for the business data last added in the business data set of the business, adding the business data to be set to the business data set of the business, and storing the business data to be set in a storage file for persistent storage of business data; When the service SBB needs to be configured with service data, the corresponding service data is configured for the service SBB from the service data set corresponding to the service SBB.

2. The service data management method of the service SBB according to claim 1, characterized in that: When the service SBB needs to configure service data, configuring the corresponding service data for the service SBB from the service data set corresponding to the service SBB includes: After setting the version number for the last added business data in the business data set of the business, when there is a business SBB with no version number in the business SBB corresponding to the business, the business data added last time is allocated to the business SBB with no version number, and the business SBB with no version number is bound to the version number of the last added business data.

3. The service data management method of the service SBB according to any one of claims 1 to 2, characterized in that: When the service SBB needs to configure service data, configuring the corresponding service data for the service SBB from the service data set corresponding to the service SBB includes: When a service data acquisition request sent by a service SBB is received through the service data acquisition interface, corresponding service data is allocated to the service SBB from the service data set of the corresponding service according to the service identification information in the service data acquisition request.

4. The service data management method of the service SBB according to claim 3, characterized in that: The allocating corresponding service data to the service SBB from the service data set of the corresponding service according to the service identification information in the service data acquisition request comprises: When the business data acquisition request includes a version number, the business data corresponding to the version number is allocated to the business SBB from the business data set of the business corresponding to the business identification information in the business data acquisition request; otherwise, the latest added business data is allocated to the business SBB from the business data set of the business corresponding to the business identification information in the business data acquisition request.

5. The service data management method of the service SBB according to any one of claims 1 to 2, characterized in that: Also includes: Receiving a business data query instruction through a business data query interface, wherein the business data query instruction includes indication information of the business data to be queried; The service data corresponding to the indication information of the service data to be queried is fed back to the querying party.

6. The service data management method of the service SBB according to any one of claims 1 to 2, characterized in that: Also includes: Receiving a business data deletion instruction through a business data deletion interface, wherein the business data deletion instruction includes indication information of the business data to be deleted; The service data to be deleted is deleted according to the indication information of the service data to be deleted.

7. The service data management method of the service SBB according to claim 6, characterized in that: The deleting process of the service data to be deleted according to the indication information of the service data to be deleted comprises: When the business data to be deleted indicated by the indication information of the business data to be deleted is currently called by a business SBB, the business data called by the business SBB that currently calls the business data to be deleted is cleared, and when the business data to be deleted is the latest business data added, a version number is set for the business data to be deleted.

8. The service data management method of the service SBB according to claim 7, characterized in that: Also includes: According to the set rules, the business data that is not currently called by the business SBB and the version number of the business data that is not currently called by the business SBB are deleted from the business data set of the business.

9. A service data management device for a service SBB, characterized in that: include: A receiving module, configured to receive a service data setting instruction through a service data setting interface, wherein the service data setting instruction includes service identification information and service data to be set; A management module is used to set a version number for the business data last added to the business data set of the business, add the business data to be set to the business data set of the business, and store the business data to be set in a storage file used for persistent storage of business data, and when the business SBB needs to configure business data, configure the corresponding business data for the business SBB from the business data set corresponding to the business SBB.

10. A communication device, characterized in that: including a processor, a memory and a communication bus; The communication bus is used to connect the processor and the memory; The processor is used to execute the computer program stored in the memory to implement the steps of the service data management method of the service SBB according to any one of claims 1 to 8.

11. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores one or more computer programs, and the one or more computer programs can be executed by one or more processors to implement the steps of the service data management method of the service SBB according to any one of claims 1-8.

Images