WO2020244513A1 - 业务sbb的业务数据管理方法、装置、设备及存储介质 - Google Patents

业务sbb的业务数据管理方法、装置、设备及存储介质 Download PDF

Info

Publication number
WO2020244513A1
WO2020244513A1 PCT/CN2020/093990 CN2020093990W WO2020244513A1 WO 2020244513 A1 WO2020244513 A1 WO 2020244513A1 CN 2020093990 W CN2020093990 W CN 2020093990W WO 2020244513 A1 WO2020244513 A1 WO 2020244513A1
Authority
WO
WIPO (PCT)
Prior art keywords
service
data
business
sbb
business data
Prior art date
Application number
PCT/CN2020/093990
Other languages
English (en)
French (fr)
Inventor
曹迎春
何君臣
陈俊
梅君君
吴豫宁
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Priority to EP20819502.4A priority Critical patent/EP3961385A4/en
Priority to US17/615,826 priority patent/US11882007B2/en
Publication of WO2020244513A1 publication Critical patent/WO2020244513A1/zh

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/448—Execution paradigms, e.g. implementations of programming paradigms
    • G06F9/4482—Procedural
    • G06F9/4484—Executing subprograms
    • G06F9/4486—Formation of subprogram jump address
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5003—Managing SLA; Interaction between SLA and QoS
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/20—Software design
    • G06F8/24—Object-oriented
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/448—Execution paradigms, e.g. implementations of programming paradigms
    • G06F9/4488—Object-oriented
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H04L41/0806—Configuration setting for initial configuration or provisioning, e.g. plug-and-play
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0893—Assignment of logical groups to network elements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/34—Network arrangements or protocols for supporting network services or applications involving the movement of software or configuration parameters 
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]

Definitions

  • the present invention relates to the field of communication technology, and in particular to a business data management method, device, equipment and storage medium of a business SBB (Service Building Block, service building block).
  • SBB Service Building Block, service building block
  • JSLEE Java APIs for Integrated Networks, JAVA application programming interface of intelligent network
  • SLEE Service Logic Execution Environment, business logic execution environment
  • JSLEE defines a developed system architecture specification, and the business developed by each manufacturer As long as it follows the JSLEE specification, it can run in the JSLEE container.
  • the JSLEE specification provides a way to configure and call the entry env-entry in the sbb-jar.xml file for the business SBB.
  • the business data of the business SBB cannot be modified and can only be read through the directory interface JNDI If you want to modify the business data of the business SBB, you can only uninstall the business, then modify the sbb-jar.xml in the business du package, and then reinstall the business. It can be seen that the current business SBB business data setting operation is cumbersome and inefficient, and it is impossible to set business data in the business running state, which affects the operation of the business.
  • the embodiment of the present invention provides a business data management method, device, equipment and storage medium of the business SBB, which solves the need to uninstall and reinstall the business in the setting of the business data of the business SBB in the related technology, resulting in cumbersome operation, low efficiency, and impact Problems with normal business operations.
  • an embodiment of the present invention provides a service data management method of service SBB, which includes:
  • an embodiment of the present invention provides a service data management device for service SBB, including:
  • a receiving module configured to receive a business data setting instruction through a business data setting interface, where the business data setting instruction includes business identification information and business data to be set;
  • the management module is configured to add the service data to be set to the service data set of the service corresponding to the service identification information, and to obtain the service data corresponding to the service SBB when the service SBB needs to configure the service data In the set, the corresponding service data is configured for the service SBB.
  • an embodiment of the present invention also provides a communication device, including a processor, a memory, and a communication bus;
  • the communication bus is configured to connect the processor and the memory
  • the processor is configured 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.
  • embodiments of the present invention also provide a computer-readable storage medium.
  • the computer-readable storage medium stores one or more computer programs, and the one or more computer programs can be used by one or more Each processor executes to implement the steps of the service data management method of the service SBB as described above.
  • FIG. 1 is a schematic flowchart of a business data management method of a business SBB according to an embodiment of the present invention
  • FIG. 2 is a schematic diagram of a business data query process according to an embodiment of the present invention.
  • Figure 3 is a schematic diagram of a business data deletion process according to an embodiment of the present invention.
  • FIG. 4 is a schematic diagram of a service data clearing process according to an embodiment of the present invention.
  • Figure 5 is a schematic diagram of the operating state of the embodiment of the present invention.
  • Figure 6-1 is a schematic diagram 1 of a service parameter configuration interface according to an embodiment of the present invention.
  • Figure 6-2 is the second schematic diagram of the service parameter configuration interface of the embodiment of the present invention.
  • FIG. 7 is a schematic structural diagram of a service data management device for service SBB according to an embodiment of the present invention.
  • Fig. 8 is a schematic structural diagram of a communication device according to an embodiment of the present invention.
  • the business data setting of the current business SBB requires uninstalling and reinstalling the business, resulting in cumbersome operations, low efficiency, and problems affecting the normal operation of the business;
  • this embodiment can expand 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, and there is no need to uninstall and reinstall the business, thereby improving the convenience and efficiency of business data setting and ensuring the normal operation of the business SBB; and
  • it can directly configure the corresponding business data for the business SBB from the business data set corresponding to the business SBB, further improving the real-time performance of the business data setting and effectiveness.
  • this embodiment will be described below with reference to the service data management method of the service SBB shown in FIG. 1 as an example.
  • the service data management method of the service SBB provided in this embodiment includes:
  • S101 Receive a business data setting instruction through a business data setting interface, where the business data setting instruction includes business identification information and business data to be set.
  • the service data setting interface in this embodiment is an extended interface, and it can be flexibly set according to the language adopted by the development technology.
  • the business data setting interface can be extended at the MBean Server layer, that is, the business data setting interface is an extended MBean interface.
  • the service data setting instruction in this embodiment can be, but not limited to, sent by the configuration client, and the configuration client can also be flexibly set according to specific application scenarios.
  • the configuration client can be, but not limited to, a JMX (Java Management Extensions, Java Management Extensions) client.
  • the service data setting instruction can also be flexibly issued when needed by configuring other devices other than the client.
  • 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 which service or services need to be set for business data can be determined according to the service identification.
  • the service data to be set in this embodiment may be at least one of any data that the service SBB needs to call.
  • a business data setting instruction can be set to include only one business identification information, that is, the business data of a business can be set through a business data setting instruction; in other examples, a business data can also be set.
  • the data setting instruction only includes two or more service identification information, thereby realizing the setting of service data of multiple services.
  • the service data to be set included in the service data setting instruction in this embodiment is also the service data to be added.
  • the service data to be set included in the service data setting instruction in this embodiment may be the service data of one service or the service data of multiple services, which can be flexibly set according to requirements.
  • the business data corresponding to each business respectively constitute a business data set corresponding to each business. That is, in this embodiment, the same service identifier, such as a service ID, can be set for each service data in the service data set of a service, so that the service data with the same service ID constitutes a service data set of a service.
  • the same service identifier such as a service ID
  • the business data in the business data set corresponding to a certain business may be empty, or may be one or more.
  • the way of adding service data to the service data set of the service corresponding to the service identification information can also be flexibly set.
  • the setting process may include but not limited to:
  • the business data to be set in the business data setting instruction may also include storing the business data to be set in a storage file for persistent storage of business data. It can ensure that the business data configured before the business is obtained when the system restarts.
  • the steps in S103 may include the following situations:
  • the business data acquisition interface can also be extended, and the business data acquisition interface allows the business SBB to acquire the corresponding business data; that is, the business SBB can call the business data through the business data acquisition interface, and when needed ,
  • the business SBB sends a business data acquisition request through the business data acquisition interface, and the business data acquisition request may include service identification information.
  • configuring the corresponding service data for the service SBB may also include the following situations:
  • the service SBB can be allocated corresponding service data from the service data set of the corresponding service according to the service identification information in the service data obtaining request.
  • allocating corresponding service data to the service SBB from the service data set of the corresponding service may include:
  • the version number is included in the business data acquisition request (that is, the business SBB has been bound to the version number)
  • assign the version number corresponding to the business SBB otherwise, it means that the business SBB is not currently bound to the version number.
  • the business data query interface can also be expanded, and when necessary, the business data query instruction can be issued through the business data query interface to query corresponding business data.
  • the service data query interface in this embodiment can also be flexibly set according to the language used in the development technology.
  • 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.
  • the business data management method of the business SBB is shown in Figure 2, which may also include:
  • S201 Receive a business data query instruction through the business data query interface, where the business data query instruction includes indication information of the business data to be queried.
  • the service data query command in this example can be sent by the configuration client through the service data query interface, or sent by other devices.
  • the indication information of the service data to be queried may include the service ID, or service ID and version number of the service to be queried.
  • S202 Feed back the business data corresponding to the instruction information of the business data to be queried to the querying party.
  • the service data deletion interface can also be expanded, and when necessary, a service data deletion instruction can be issued through the service data deletion interface to delete corresponding business data.
  • the service data deletion interface in this embodiment can also be flexibly set according to the language used in the development technology.
  • 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.
  • the business data management method of business SBB is shown in Figure 3, which may also include:
  • S301 Receive a business data deletion instruction through the business data deletion interface, where the business data deletion instruction includes instruction information of the business data to be deleted.
  • the service data deletion instruction in this example can be sent by the configuration client through the service data deletion interface, or 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.
  • S302 Perform deletion processing on the business data to be deleted according to the instruction information of the business data to be deleted.
  • the deletion processing of the business data to be deleted according to the instruction information of the business data to be deleted in S302 may include but is not limited to:
  • the business data called by the business SBB that currently calls the business data to be deleted is cleared, and the business data to be deleted is currently the latest added For business data, set the version number 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 in the background in a unified manner, and When the business data is stored in the storage file, it is also cleared in the storage file.
  • it may also include collecting the business data of the business according to set rules (for example, timing), the business data that is not currently called by the business SBB, and the business data that is not currently called by the business SBB.
  • set rules for example, timing
  • the version number is deleted.
  • the setting rule in this embodiment may be timed extraction, such as every 2 minutes, 3 minutes, 5 minutes, or 10 minutes.
  • S402 Obtain the absolute complement set of the second version number set in the first version number set, and delete the obtained version number in the absolute supplement set and the business data corresponding to the version number in the absolute supplement set. This step is also about 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 has not been called by the business SBB, that is, it is unnecessary business data) Business data is deleted.
  • the service data management method of the service SBB provided in this embodiment can use the above-mentioned expanded service data setting interface, service data query interface, service data deletion interface, service data acquisition interface and other interfaces used for service management data.
  • the corresponding business data can be obtained through the business data acquisition interface, and the corresponding configuration client and business data setting interface, business data query interface, and business data deletion interface can be used to realize the addition, query and deletion of business data without uninstalling and re-installing.
  • the installation of business can improve the real-time performance of business data setting and effective.
  • a business data acquisition interface is added to the SbbContext interface, and the business SBB can use the business data acquisition interface to acquire business data;
  • a JMX management interface is provided, including a business data setting interface and a business data query interface , Business data delete interface, you can directly set, query or delete business data through the JMX client, which can easily realize the flexible management of business data and take effect immediately without uninstalling and reinstalling the business.
  • the setting of the service data can be during the running of the service or when the service is not running.
  • 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 business data, that is, when setting, the business data acquired by the currently running business SBB is the configuration value before modification, and the new business SBB triggered after the business data setting is completed
  • the data is the modified configuration value; there should not be a running business SBB, and the business data obtained before and after is not of one version (in this example, each time the management data is set, one version is generated).
  • getServiceData is the service data acquisition interface: used to obtain a service data value 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.
  • the JSLEE standard business management MBean interface can also be extended to add business data operation related interfaces, including business data setting interface, business data query interface, and business data deletion interface, so as to provide the JMX method to set business data: , Delete, query.
  • business management interface defined in the JSLEE specification in an example is as follows:
  • ServiceManagementMBeaninterface An example description of the above business management interface (ServiceManagementMBeaninterface) is as follows:
  • the extended service management interface is as follows:
  • the new interface description of the service management interface is as follows:
  • 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, and return the content of all business data of the business (the business data of a specific version of the business can also be obtained), which can be expressed in the form of ConfigProperties .
  • the service data setting interface It can be used to set the service data corresponding to a certain service.
  • the parameter id represents the service ID
  • the parameter properties represents the content of the service data after setting.
  • the business data deletion interface used to delete the business data corresponding to a certain business, and the parameter id represents the business ID.
  • JMX client that is, a sample configuration client
  • server with JSLEE container
  • the business data part in Figure 5 is responsible for the maintenance of business data, including the maintenance of multiple versions of the same business (for example, business data A1 and business data A2 in Figure 5 represent management data of different versions of business A; business data B1, business data B2 Represents the management data of different versions of business B), and the latest business data is persistently stored in the storage file.
  • the SBB entity part is responsible for providing the business SBB to obtain the business data of the corresponding version of the business.
  • the specific implementation logic can include:
  • the business data obtained in one business operation can only be the data modified at the same time, and the business data of each business needs to be managed in multiple versions.
  • the latest version of the business data it also needs to be in the memory Save the business data of the old version set in the past, so that when it is modified, the business SBB currently running can still get the business data of the old version;
  • the business data setting can be realized through the business data setting interface.
  • the business SBB can obtain the corresponding business data through the business data acquisition interface.
  • the corresponding business data can be deleted through the business data delete interface.
  • the newly set business data needs to be deleted (that is, the data to be deleted is the latest social business data)
  • a version is generated for the newly set business data to be deleted
  • traverse the business SBB to confirm which business SBB is using the newly set business data, and update the business data called by these business SBB to empty, and delete the corresponding latest set business data in the storage file; and the real memory
  • the latest business data can be deleted while the background timer is running.
  • the background runs regularly (For example, it can be performed every 5 minutes), traverse all SBB entities of a business, record the version numbers bound to all SBB entities to obtain the second version number set, which is composed of all the version numbers of the business data of the business. Compare the version numbers in the version number set. If the 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), then clear the version number A and the version number A corresponding Business data.
  • OMM Organic Metadata Management, metadata management
  • the business management data can be set for business A in the OMM management interface.
  • An example of a code that uses business data for business SBB of business A is as follows:
  • 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 implement the business. Adding, querying, and deleting data does not require uninstalling and reinstalling services, which can improve the real-time performance of business data settings and validation.
  • a service data management device of the service SBB is also provided.
  • the service data management device of the service SBB may be set in a communication device, and the communication device may be a communication device serving as a server. See Figure 7, which includes:
  • the receiving module 701 is configured to receive a business data setting instruction through a business data setting interface, where the business data setting instruction includes business identification information and business data to be set.
  • the service data setting interface in this embodiment is an extended interface, and it can be flexibly set according to the language adopted by the development technology.
  • the service data setting instruction in this embodiment can be, but not limited to, sent by the configuration client, and the configuration client can also be flexibly set according to specific application scenarios.
  • the configuration client can be but not limited to a JMX (Java Management Extensions, Java Management Extensions) client.
  • the service data setting instruction can also be flexibly issued when needed by configuring other devices other than the client.
  • 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 or services need to be set based on the service identification.
  • the service data to be set in this embodiment may be at least one of any data that needs to be called by the service SBB.
  • a business data setting instruction can be set to include only one business identification information, that is, the business data of a business can be set through a business data setting instruction; in other examples, a business data can also be set.
  • the data setting instruction only includes two or more service identification information, so that the service data of multiple services can be set.
  • the service data included in the service data setting instruction in this embodiment is the service data to be set, and the setting here is also to increase.
  • the service data to be set included in the service data setting instruction in this embodiment may be the service data of one service or the service data of multiple services, which can be flexibly set according to requirements.
  • the management module 702 is set to add the business data to be set in the business data set of the business corresponding to the business identification information in the business data setting instruction, and is used for when the business SBB needs to configure the business data, from the business corresponding to the business SBB In the data set, configure the corresponding business data for the business SBB.
  • the business data corresponding to each business respectively constitute a business data set corresponding to each business. That is, in this embodiment, the same service identifier can be set for each service data in the service data set of a service. 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 more. And in this embodiment, according to the service identification information and the service data, the way of adding service data to the service data set of the service corresponding to the service identification information can also be flexibly set.
  • an example setting process may include but not limited to:
  • 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.
  • the management module 702 may also include storing the business data to be set in a storage file for persistent storage of business data. In this way, it can ensure that the business data configured before the business is obtained when the system restarts.
  • the management module 702 sets the version number for the business data added last time in the business data set of the business
  • the business SBB corresponding to the business currently has a business SBB with no version number bound
  • it can provide these The business SBB allocates the business data added last time, and binds these business SBBs with the version number set for the business data added last time.
  • the business data acquisition interface can also be extended, and the business data acquisition interface allows the business SBB to acquire the corresponding business data; that is, the business SBB can call the business data through the business data acquisition interface, and when needed ,
  • the business SBB sends a business data acquisition request through the business data acquisition interface, and the business data acquisition request may include service identification information.
  • configuring the corresponding service data for the service SBB may also include the following situations: the management module 702 receives the service data through the service data acquisition interface When it arrives at the service data acquisition request sent by the service SBB, the 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.
  • the management module 702 allocates 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, which may include: the management module 702 obtains the service data When the request includes the version number (that is, the service SBB has been bound to the version number), the service data set corresponding to the service identification information in the service data acquisition request is assigned to the service SBB with the service data corresponding to the version number; Otherwise, it means that the business SBB is not currently bound to the version number. From the business data set of the business corresponding to the business identification information in the business data acquisition request, assign the newly added business data to the business SBB, that is, assign the latest business to the business SBB data.
  • the business data query interface can also be expanded, and when necessary, the business data query instruction can be issued through the business data query interface to query corresponding business data.
  • the management module 702 receives a business data query instruction through a business data query interface, and the business data query instruction includes 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 inquiring party.
  • the service data deletion interface can also be expanded, and when necessary, a service data deletion instruction can be issued through the service data deletion interface to delete corresponding business data.
  • the management module 702 receives a business data deletion instruction through a business data deletion interface, and the business data deletion instruction includes instruction information of the business data to be deleted.
  • the service data deletion instruction in this example can be sent by the configuration client through the service data deletion interface, or sent by other devices.
  • the management module 702 deletes the business data to be deleted according to the instruction information of the business data to be deleted.
  • the management module 702 deletes the business data to be deleted according to the instruction information of the business data to be deleted, which may include but is not limited to: the management module 702 determines that the instruction information of the business data to be deleted corresponds to the instruction to be deleted.
  • the management module 702 is also set to collect the business data of the business according to set rules (for example, timing), the business data that is not currently called by the business SBB, and the business data that is not currently called by the business SBB.
  • the version number of the business data is deleted.
  • the management module 702 can periodically extract the version numbers of the current service data in the service data set of the service to obtain the first version number set, and extract the version numbers currently bound to each service SBB corresponding to the service.
  • the business data management device of the business SBB 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, and business SBB can use
  • the business data acquisition interface acquires the corresponding business data
  • the corresponding configuration client and business data setting interface, business data query interface, and business data delete interface can be used to add, query, and delete business data without uninstalling and reinstalling the business. , Can improve the real-time performance of business data setting and effective.
  • a communication device is also provided.
  • the communication device may be a device serving as a server. As shown in FIG. 8, it includes a processor 801, a memory 802, and a communication bus 803;
  • the communication bus 803 is configured to implement a communication connection between the processor 801 and the memory 802;
  • the processor 801 may be configured 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.
  • the function of at least one module of the service data management apparatus of the service SBB can be realized by the above-mentioned processor.
  • This embodiment also provides a computer-readable storage medium.
  • the computer-readable storage medium includes those implemented in any method or technology for storing information (such as computer-readable instructions, data structures, computer program modules, or other data). Volatile or non-volatile, removable or non-removable media.
  • Computer-readable storage media include but are not limited to RAM (Random Access Memory), ROM (Read-Only Memory, read-only memory), EEPROM (Electrically Erasable Programmable read only memory, charged Erasable Programmable Read-Only Memory) ), flash memory or other storage technology, CD-ROM (Compact Disc Read-Only Memory), digital versatile disk (DVD) or other optical disk storage, magnetic cassettes, magnetic tapes, magnetic disk storage or other magnetic storage devices, Or any other medium that can be used to store desired information and can be accessed by a computer.
  • the computer-readable storage medium in this embodiment can be used to store one or more computer programs, and the one or more computer programs can be executed by one or more processors to implement the The steps of the business data management method of business SBB.
  • This embodiment also provides a computer program (or computer software).
  • the computer program can be distributed on a computer-readable medium and executed by a computable device to realize the business data management of the business SBB shown in the above embodiments. At least one step of the method; and in some cases, at least one step shown or described may be performed in a different order than described in the above-mentioned embodiment.
  • This embodiment also provides a computer program product, including a computer-readable device, and the computer-readable device stores the computer program as shown above.
  • the computer-readable device in this embodiment may include the computer-readable storage medium as shown above.
  • the service data setting interface can be expanded.
  • the service data setting instruction can be received through the service data setting interface,
  • the business data to be set is added to the business data set of the business corresponding to the business identification information to realize the setting of the business data of the business SBB, and there is no need to set the business data.
  • Uninstallation and reinstallation can improve the convenience and efficiency of business data setting, and at the same time can avoid the situation that the business cannot run normally due to business uninstallation; and when the business SBB needs to configure the business data, it can be directly from the business SBB corresponding
  • the corresponding business data is configured for the business SBB, that is, the set business data can take effect immediately and can be called by the corresponding SBB in real time, which further improves the real-time performance of business data setting and effectiveness.
  • the functional modules/units in the system, and the device can be implemented as software (which can be implemented by computer program code executable by a computing device ), firmware, hardware and their appropriate combination.
  • the division between functional modules/units mentioned in the above description does not necessarily correspond to the division of physical components; for example, one physical component may have multiple functions, or one function or step may consist of several physical components. The components are executed cooperatively.
  • Some physical components 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 as hardware, or as an integrated circuit, such as an application specific integrated circuit .
  • communication media usually contain computer-readable instructions, data structures, computer program modules, or other data in a modulated data signal such as a carrier wave or other transmission mechanism, and may include any information delivery medium. Therefore, the present invention is not limited to any specific combination of hardware and software.
  • the service data management method, device, equipment and storage medium of the service SBB provided by the embodiments of the present invention have the following beneficial effects: the service data setting interface can be expanded, and the service data can be set through the service
  • the data setting interface receives the business data setting instruction, and adds the business data to be set to the business data set of the business corresponding to the business identification information according to the business identification information in the business data setting instruction and the business data to be set; thereby improving the business data Convenience and efficiency of setting; and when it is detected that the business SBB needs to configure business data, it can directly configure the corresponding business data for the business SBB from the business data set corresponding to the business SBB, that is, the set business data can be instantly It takes effect and can be called by the corresponding SBB in real time, further improving the real-time performance of business data setting and taking effect.

Abstract

一种业务SBB的业务数据管理方法、装置、设备及存储介质，可扩展业务数据设置接口，在需要对业务数据进行设置时，可通过业务数据设置接口接收业务数据设置指令，根据业务数据设置指令中的业务标识信息和待设置的业务数据，在该业务标识信息所对应业务之业务数据集合中增加待设置的业务数据；从而提升业务数据设置的便捷性和效率；且在检测到业务SBB需要配置业务数据时，可直接从该业务SBB所对应的业务数据集合中为业务SBB配置对应的业务数据，也即所设置的业务数据可即时生效并可供相应的SBB实时调用，进一步提升业务数据设置和生效的实时性。

Description

业务SBB的业务数据管理方法、装置、设备及存储介质 技术领域
本发明涉及通信技术领域，尤其涉及一种业务SBB(Service Building Block，服务构建基块)的业务数据管理方法、装置、设备及存储介质。
背景技术
JSLEE(JAIN(Java APIs for Integrated Networks，智能网的JAVA应用编程接口)SLEE(Service Logic Execution Environment，业务逻辑执行环境)技术，简称JSLEE)定义了一种开发的系统架构规范，各个厂商开发的业务只要是遵循JSLEE规范，就可以运行在JSLEE容器中。
目前JSLEE规范对业务SBB提供了在sbb-jar.xml文件中配置调用入口env-entry的方式，这种方式在业务SBB安装后，该业务SBB的业务数据不可修改，只能通过目录接口JNDI读取，要想修改业务SBB的业务数据，只能卸载业务，再修改业务du包中的sbb-jar.xml，再重新安装业务。可见目前业务SBB的业务数据的设置操作繁琐且效率低，也做不到业务运行状态下进行业务数据的设置，影响业务的运行。
发明内容
本发明实施例提供的一种业务SBB的业务数据管理方法、装置、设备及存储介质，解决相关技术中业务SBB的业务数据的设置需要对业务进行卸载重装，导致操作繁琐、效率低，影响业务正常运行的问题。
为解决上述技术问题，本发明实施例提供一种业务SBB的业务数据管理方法，包括：
通过业务数据设置接口接收业务数据设置指令，所述业务数据设置指令中包括业务标识信息以及待设置的业务数据；
在所述业务标识信息所对应业务之业务数据集合中增加所述待设置的业务数据；
当业务SBB需要配置业务数据时，从所述业务SBB所对应的业务数据集合中，为所述业务SBB配置对应的业务数据。
为解决上述技术问题，本发明实施例提供一种业务SBB的业务数据管理装置，包括：
接收模块，设置为通过业务数据设置接口接收业务数据设置指令，所述业务数据设置指令中包括业务标识信息以及待设置的业务数据；
管理模块，设置为在所述业务标识信息所对应业务之业务数据集合中增加所述待设置的业务数据，以及用于在业务SBB需要配置业务数据时，从所述业务SBB所对应的业务数据集合中，为所述业务SBB配置对应的业务数据。
为解决上述技术问题，本发明实施例还提供了一种通信设备，包括处理器、存储器和通信总线；
所述通信总线设置为将所述处理器和存储器连接；
所述处理器设置为执行所述存储器中存储的计算机程序，以实现如上所述的业务SBB的业务数据管理方法的步骤。
为解决上述技术问题，本发明实施例还提供了一种计算机可读存储介质，所述计算机可读存储介质存储有一个或多个计算机程序，所述一个或多个计算机程序可被一个或多个处理器执行，以实现如上所述的业务SBB的业务数据管理方法的步骤。
本发明其他特征和相应的有益效果在说明书的后面部分进行阐述说 明，且应当理解，至少部分有益效果从本发明说明书中的记载变的显而易见。
附图说明
图1为本发明实施例的业务SBB的业务数据管理方法流程示意图；
图2为本发明实施例的业务数据查询流程示意图；
图3为本发明实施例的业务数据删除流程示意图；
图4为本发明实施例的业务数据清除流程示意图；
图5为本发明实施例的运行状态示意图；
图6-1为本发明实施例的业务参数配置界面示意图一；
图6-2为本发明实施例的业务参数配置界面示意图二；
图7为本发明实施例的业务SBB的业务数据管理装置结构示意图；
图8为本发明实施例的通信设备结构示意图。
具体实施方式
为了使本发明的目的、技术方案及优点更加清楚明白，下面通过具体实施方式结合附图对本发明实施例作进一步详细说明。应当理解，此处所描述的具体实施例仅仅用以解释本发明，并不用于限定本发明。
在一个示例性实施例中，针对目前业务SBB的业务数据的设置需要对业务进行卸载重装，导致操作繁琐、效率低，影响业务正常运行的问题；本实施例可扩展业务数据设置接口，在需要对业务数据进行设置时，可通过业务数据设置接口进行业务数据的设置，并不需要对业务进行卸载重装，从而提升业务数据设置的便捷性和效率和保证业务SBB的正常运行；且 在检测到业务SBB需要配置业务数据时，可直接从业务SBB所对应的业务数据集合中为业务SBB配置对应的业务数据，进一步提升业务数据设置和生效的实时性。为了便于理解，本实施例下面结合图1所示的业务SBB的业务数据管理方法为示例进行说明。
请参见图1所示，本实施例所提供的业务SBB的业务数据管理方法包括：
S101：通过业务数据设置接口接收业务数据设置指令，业务数据设置指令中包括业务标识信息以及待设置的业务数据。
本实施例中的业务数据设置接口为扩展的接口，且其根据开发技术所采用的语言可以灵活设置。例如对于利用JAVA的开放架构与系统，业务数据设置接口可在MBean Server层扩展，也即业务数据设置接口为扩展的MBean接口。
本实施例中的业务数据设置指令可以为但不限于配置客户端发送的，且配置客户端也可根据具体应用场景灵活设置。例如对于利用JAVA的开放架构与系统，配置客户端可以为但不限于JMX(Java Management Extensions，Java管理扩展)客户端。当然，在一些示例中，业务数据设置指令也可通过配置客户端之外的其他设备在需要时灵活下发。
本实施例中，业务数据设置指令中包括的业务标识信息为待设置业务数据的业务之业务标识，可以根据业务标识确定出需要对哪个或些业务进行业务数据设置。且应当理解的是，本实施例中待设置的业务数据可以为业务SBB需要调用到的任意数据中的至少一种。且应当理解的是，本实施例中可以设置一个业务数据设置指令仅包括一个业务标识信息，也即通过一个业务数据设置指令设置一个业务的业务数据；在另一些示例中，也 可设置一个业务数据设置指令仅包括两个或两个以上的业务标识信息，从而实现对多个业务的业务数据进行设置。
本实施例中的业务数据设置指令包括的待设置的业务数据也即为待增加的业务数据。根据上述示例可知，本实施例中业务数据设置指令包括的待设置的业务数据可以为一个业务的业务数据，也可为多个业务的业务数据，具体可根据需求灵活设置。
S102：在业务数据设置指令中的业务标识信息所对应业务之业务数据集合中增加待设置的业务数据。
本实施例中各业务各自对应的业务数据分别组成各业务对应的业务数据集合。也即在本实施例中，针对一个业务的业务数据集合中的各业务数据可以设置相同的业务标识，例如业务ID，这样具有相同业务ID的业务数据则构成一个业务的业务数据集合。
应当理解的是，某一个业务对应的业务数据集合中的业务数据可能为空，也可能为1个，或者多个等。且在本实施例中，根据业务标识信息和业务数据，在业务标识信息所对应业务之业务数据集合中增加业务数据的方式也可灵活设定，例如，在一个示例中，设置过程可包括但不限于：
为业务之业务数据集合中上一次所增加的业务数据设置版本号，并将接收到的业务数据设置指令中待设置的业务数据增加到业务之业务数据集合，也即对于一个业务数据集合中的业务数据，除了当前最新所设置的业务数据，之前所设置的业务数据都设置有对应的版本号(当然在一些实例中也可为当前最新所设置的业务数据也设置版本号或设置用于标识其为最新设置的业务数据的标识)。在本实施例中，将业务数据设置指令中待设置的业务数据增加到业务之业务数据集合后，还可包括将待设置的业 务数据存储于用于持久化存储业务数据的存储文件中，这样可以保证系统重启时获取业务之前配置的业务数据。
S103：当业务SBB需要配置业务数据时，从业务SBB所对应的业务数据集合中，为业务SBB配置对应的业务数据。
例如，在一些实例中，S103中的步骤可包括以下情况：
在上述S102中为业务之业务数据集合中上一次所增加的业务数据设置版本号后，检测到这一业务对应的业务SBB中当前存在未绑定版本号的业务SBB时，可为这些业务SBB分配上一次所增加的业务数据，并将这些业务SBB与为上一次所增加的业务数据设置的版本号绑定。
在本实施例的另一些示例中，还可扩展业务数据获取接口，业务数据获取接口可供业务SBB获取对应的业务数据；也即业务SBB可通过业务数据获取接口调用业务数据，且在需要时，业务SBB通过业务数据获取接口发送业务数据获取请求，业务数据获取请求中可包括业务标识信息。此时，S103中当业务SBB需要配置业务数据时，从业务SBB所对应的业务数据集合中，为业务SBB配置对应的业务数据还可包括以下情况：
通过业务数据获取接口接收到业务SBB发送的业务数据获取请求时，则可根据业务数据获取请求中的业务标识信息，从对应业务之业务数据集合中为业务SBB分配对应的业务数据。
在本实施例的一种示例中，根据业务数据获取请求中的业务标识信息，从对应业务之业务数据集合中为业务SBB分配对应的业务数据可包括：
在业务数据获取请求中包括版本号时(也即业务SBB已经绑定了版本号)，从业务数据获取请求中的业务标识信息所对应的业务之业务数据集合中，为业务SBB分配版本号对应的业务数据；否则表明业务SBB当 前未绑定版本号，从业务数据获取请求中的业务标识信息所对应的业务之业务数据集合中，为业务SBB分配最新增加的业务数据，也即为业务SBB分配最近的业务数据。
可选的，在本实施例的一些示例中，还可扩展业务数据查询接口，在需要时可通过业务数据查询接口下发业务数据查询指令进行对应业务数据的查询。本实施例中的业务数据查询接口也可根据开发技术所采用的语言可以灵活设置。例如对于利用JAVA的开放架构与系统，业务数据查询接口可在MBean Server层扩展，也即业务数据查询接口也可为扩展的MBean接口。在本示例中，业务SBB的业务数据管理方法请参见图2所示，还可包括：
S201：通过业务数据查询接口接收业务数据查询指令，业务数据查询指令中包括待查询业务数据的指示信息。
本示例中的业务数据查询指令可为配置客户端通过业务数据查询接口发送的，也可为其他设备发送的。待查询业务数据的指示信息可以包括待查询业务的业务ID，或业务ID和版本号等。
S202：向查询方反馈待查询业务数据的指示信息所对应的业务数据。
可选的，在本实施例的一些示例中，还可扩展业务数据删除接口，在需要时可通过业务数据删除接口下发业务数据删除指令进行对应业务数据的删除。本实施例中的业务数据删除接口也可根据开发技术所采用的语言可以灵活设置。例如对于利用JAVA的开放架构与系统，业务数据删除接口也可在MBean Server层扩展，也即业务数据删除接口也可为扩展的MBean接口。在本示例中，业务SBB的业务数据管理方法请参见图3所示，还可包括：
S301：通过业务数据删除接口接收业务数据删除指令，业务数据删除指令中包括待删除业务数据的指示信息。
本示例中的业务数据删除指令可为配置客户端通过业务数据删除接口发送的，也可为其他设备发送的。待删除业务数据的指示信息可以包括待删除业务的业务ID，或业务ID和版本号等。
S302：根据待删除业务数据的指示信息对待删除业务数据进行删除处理。
在本实施例的一种示例中，S302中根据待删除业务数据的指示信息对待删除业务数据进行删除处理可包括但不限于：
在确定待删除业务数据的指示信息指示的待删除业务数据当前被业务SBB调用时，将当前调用待删除业务数据的业务SBB所调用的业务数据清空，并在待删除业务数据为当前最新增加的业务数据时，为待删除业务数据设置版本号；在一些实例中，可以直接对确定的待删除数据进行直接删除，在另一些示例中也可在后续通过后台统一对待删除业务数据进行清除，且当业务数据在存储文件有存储时，也在存储文件中对其进行一并清除。
例如，在本实施例的一些示例中，还可包括按设定规则(例如定时)将业务之业务数据集合中，当前未被业务SBB调用的业务数据，以及当前未被业务SBB调用的业务数据之版本号删除。例如一种示例的实现方式参见图4所示的业务数据统一清除过程，包括：
S401：按设定规则提取业务之业务数据集合中当前各业务数据的版本号得到第一版本号集合，以及提取业务对应的各业务SBB当前所绑定的版本号得到第二版本号集合；该第二本版号集合必然为第一版本号集合的 子集。
本实施例中的设定规则可以为定时提取，例如每间隔2分钟、3分钟、5分钟或10分钟等。
S402：获取第二版本号集合在第一版本号集合内的绝对补集，并将得到的绝对补集中的版本号，以及绝对补集中的版本号所对应的业务数据删除。该步骤也即将第一版本号集合中，在第二版本号集合内不存在的版本号(表明这些版本号对应的业务数据未被业务SBB调用，也即为不需要的业务数据)所对应的业务数据删除。
也即本实施例所提供的业务SBB的业务数据管理方法可以通过上述扩展的业务数据设置接口、业务数据查询接口、业务数据删除接口、业务数据获取接口等用于业务管理数据的接口，业务SBB可通过业务数据获取接口获取对应的业务数据，也可对应的配置客户端以及业务数据设置接口、业务数据查询接口、业务数据删除接口实现业务数据的增加、查询以及删除，并不需要卸载和重新安装业务，可提升业务数据设置和生效的实时性。
为了便于理解，还提供了另一个实施例，该本实施例在上述实施例的基础上，结合JSLEE定义开发的系统架构规范，结合上述实施例所示例的业务SBB的业务数据管理方法所涉及的JSLEE容器进行说明。
本实施例中，在SbbContext接口中增加了业务数据获取接口，业务SBB可使用业务数据获取接口获取业务数据；在本实施例中，再提供JMX管理接口，包括业务数据设置接口、业务数据查询接口、业务数据删除接口，可以通过JMX客户端直接设置、查询或删除业务数据，这样可以很 容易实现业务数据的灵活管理，并立即生效，而不需要卸载和重新安装业务。
在本实施例中，对于业务数据的设置可以是在业务运行过程中，也可以是业务未运行时。当然在业务运行过程中时，由于业务SBB本身是无状态的，业务SBB运行过程中可能多次获取对应的业务数据。因此为了保证业务数据的一致性，也就是保证在设置时，当前已正在运行的业务SBB获取到的业务数据是修改前的配置值，而业务数据设置完成之后新触发的新业务SBB所获取到的数据则是修改后的配置值；不应出现一个运行中的业务SBB，前后获取的业务数据不是一个版本的(本示例中每设置一次管理数据，产生一个版本)。
例如，在一种应用场景中，可对JSLEE1.1规范接口进行以下扩展
对JSLEE规范中SbbContext接口增加获取业务数据的业务数据获取接口(业务数据获取接口是提供给业务SBB使用的)，这样业务SBB可以通过业务数据获取接口实时获取到最新的业务数据。
例如假设一种示例中的JSLEE范中定义的SbbContext接口如下：
Figure PCTCN2020093990-appb-000001
Figure PCTCN2020093990-appb-000002
以上接口的说明(SbbContext interface)如下：
Figure PCTCN2020093990-appb-000003
在本示例中，对上述SbbContext接口扩展如下：
public interface SbbContextExt extends SbbContext{
public Object getServiceData(String name)；
}
上述扩展的接口中，getServiceData为业务数据获取接口：用于获取业务SBB对应业务的一项业务数据值，参数name可为业务数据名称，返回业务数据对应的值。
在本实施例中，还可扩展JSLEE规范业务管理MBean接口，增加业务数据操作相关接口，包括业务数据设置接口、业务数据查询接口、业务数据删除接口，从而提供通过JMX方式对业务数据进行：设置、删除、查询。
例如一种示例中JSLEE规范中定义的业务管理接口如下：
Figure PCTCN2020093990-appb-000004
以上业务管理接口的一种示例说明(ServiceManagementMBeaninterface)如下：
Figure PCTCN2020093990-appb-000005
在本实施例中，扩展业务管理接口如下：
Figure PCTCN2020093990-appb-000006
业务管理接口新增接口说明如下：
getServiceProperties，即业务数据查询接口：可用于获取某个业务对应的业务数据，参数id可表示业务ID，返回业务所有业务数据的内容(也可获取业务特定版本的业务数据)，可以ConfigProperties的形式表示。
setServiceProperties，即业务数据设置接口：可用于设置某个业务对应 的业务数据，参数id表示业务ID，参数properties表示设置后的业务数据内容。
removeServiceProperties，即业务数据删除接口：用于删除某个业务对应的业务数据，参数id表示业务ID。
基于上述示例设置和应用场景，一种JMX客户端、服务端的运行状态示意图请参见图5所示，其中：JMX客户端(也即一种示例的配置客户端)、服务端(具有JSLEE容器)配合完成业务数据的查询、设置、删除的远程调用。
图5中的业务数据部分负责业务数据的维护，包括同一业务多版本数据的维护(例如图5中业务数据A1、业务数据A2表示业务A的不同版本的管理数据；业务数据B1、业务数据B2表示业务B不同版本的管理数据)，以及最新业务数据的在存储文件中持久化保存。
SBB实体部分负责提供给业务SBB获取对应业务对应版本的业务数据。其中，具体的实现逻辑可包括：
为了保证业务数据的一致性，即一次业务的运行获取到的业务数据只能是同一次修改的数据，需要对各个业务的业务数据进行多版本管理，除了最新版本的业务数据，还需要在内存中保存以往设置的老版本业务数据，这样修改时，当前正在运行的业务SBB还能取到老版本的业务数据；
通过业务数据查询接口可实现查询内存中各个业务的最新版本业务数据或所有业务数据或指定的其他版本的业务数据；
通过业务数据设置接口可实现业务数据的设置，在本示例中可首先为当前需要设置的业务上一次设置的业务数据生成一个版本号，再遍历这一业务当前所有的业务SBB，如果某一业务SBB还没有绑定一个版本号则 为之绑定刚生成的版本号；对于已经绑定版本号的业务SBB，则忽略(说明此业务SBB使用的业务数据是当前版本号之前的版本号对应的业务数据)；然后更新这一业务最新的业务数据为待设置的业务数据，同时把最新的业务数据更新到持久化存储的存储文件，以供系统重启时获取。
业务SBB可通过业务数据获取接口获取对应的业务数据，本示例中可先确定业务SBB对应的SBB实体是否已绑定业务数据的版本号，如果已绑定，则获取此版本号对应的业务数据；否则，获取业务对应的最新设置的业务数据。
通过业务数据删除接口可实现对应业务数据的删除，例如对于最新设置的业务数据需要删除(也即待删除数据为最新社会自的业务数据)时，为该待删除的最新设置的业务数据生成版本号，并遍历业务SBB确认哪些业务SBB在使用最新设置的业务数据，并将这些业务SBB调用的业务数据更新为空，同时将存储文件中对应的最新设置的业务数据也删除；而真正内存中最新业务数据的删除，可在后台定时器运行时进行。
随着系统的运行，业务数据的版本可能越来越多，因此在实施例中还可对需要对那些没有在使用的老版本数据或者当前需要删除的最新版本的数据进行清除；其中后台运行定时器(例如可以每5分钟进行一次)，遍历一个业务的所有的SBB实体，记录下所有SBB实体绑定的版本号得到第二版本号集合，与业务的业务数据的所有版本号组成的第一版本号集合中的版本号进行比较，如果第一版本号集合中的版本号A不在第二版本号集合(也即当前绑定的版本号集合中)，则清除版本号A以及版本号A对应的业务数据。
基于上述原理，一种示例的配置业务A的业务数据(也即图6-1和图 6-2中的业务管理数据)的OMM(Oracle Metadata Management，元数据管理)管理界面可参见图6-1和图6-2所示，在OMM管理界面可对业务A进行业务管理数据的设置。而业务A的业务SBB使用业务数据的一种代码举例如下：
Object value＝((SbbContextExt)this.sbbContext).getServiceData(key)；
可见通过本实施提供的扩展后的JSLEE规范，业务SBB可通过业务数据获取接口获取对应的业务数据，也可对应的配置客户端以及业务数据设置接口、业务数据查询接口、业务数据删除接口实现业务数据的增加、查询以及删除，并不需要卸载和重新安装业务，可提升业务数据设置和生效的实时性。
在一个示例性实施例中，还提供了一种业务SBB的业务数据管理装置，业务SBB的业务数据管理装置可设置于通信设备内，通信设备可为作为服务端的通信设备。请参见图7所示，其包括：
接收模块701，设置为通过业务数据设置接口接收业务数据设置指令，所述业务数据设置指令中包括业务标识信息以及待设置的业务数据。本实施例中的业务数据设置接口为扩展的接口，且其根据开发技术所采用的语言可以灵活设置。
本实施例中的业务数据设置指令可以为但不限于配置客户端发送的，且配置客户端也可根据具体应用场景灵活设置。例如对于利用JAVA的开放架构与系统，配置客户端可以为但不限于JMX(Java Management Extensions，Java管理扩展)客户端。当然，在一些示例中，业务数据设置指令也可通过配置客户端之外的其他设备在需要时灵活下发。本实施例中，业务数据 设置指令中包括的业务标识信息为待设置业务数据的业务之业务标识，可以根据业务标识确定出需要对哪个或些业务进行业务数据设置。且应当理解的是，本实施例中待设置的业务数据可以为业务SBB需要调用到的任意数据中的至少一种。且应当理解的是，本实施例中可以设置一个业务数据设置指令仅包括一个业务标识信息，也即通过一个业务数据设置指令设置一个业务的业务数据；在另一些示例中，也可设置一个业务数据设置指令仅包括两个或两个以上的业务标识信息，从而实现对多个业务的业务数据进行设置。本实施例中的业务数据设置指令包括的业务数据为待设置的业务数据，此处的设置也即为增加。根据上述示例可知，本实施例中业务数据设置指令包括的待设置的业务数据可以为一个业务的业务数据，也可为多个业务的业务数据，具体可根据需求灵活设置。
管理模块702，设置为在业务数据设置指令中的业务标识信息所对应业务之业务数据集合中增加待设置的业务数据，以及用于当业务SBB需要配置业务数据时，从业务SBB所对应的业务数据集合中，为业务SBB配置对应的业务数据。
本实施例中各业务各自对应的业务数据分别组成各业务对应的业务数据集合。也即在本实施例中，针对一个业务的业务数据集合中的各业务数据可以设置相同的业务标识。应当理解的是，某一个业务对应的业务数据集合中的业务数据可能为空，也可能为1个，或者多个等。且在本实施例中，根据业务标识信息和业务数据，在业务标识信息所对应业务之业务数据集合中增加业务数据的方式也可灵活设定，例如，一种示例的中设置过程可包括但不限于：
管理模块702为业务之业务数据集合中上一次所增加的业务数据设置版本号，并将接收到的业务数据设置指令中待设置的业务数据增加到业务 之业务数据集合。在本实施例中，管理模块702将业务数据设置指令中待设置的业务数据增加到业务之业务数据集合后，还可包括将待设置的业务数据存储于用于持久化存储业务数据的存储文件中，这样可以保证系统重启时获取业务之前配置的业务数据。
一种示例中，管理模块702在为业务之业务数据集合中上一次所增加的业务数据设置版本号后，当业务对应的业务SBB中当前存在未绑定版本号的业务SBB时，可为这些业务SBB分配上一次所增加的业务数据，并将这些业务SBB与为上一次所增加的业务数据设置的版本号绑定。
在本实施例的另一些示例中，还可扩展业务数据获取接口，业务数据获取接口可供业务SBB获取对应的业务数据；也即业务SBB可通过业务数据获取接口调用业务数据，且在需要时，业务SBB通过业务数据获取接口发送业务数据获取请求，业务数据获取请求中可包括业务标识信息。此时，管理模块702检测到业务SBB需要配置业务数据时，从业务SBB所对应的业务数据集合中，为业务SBB配置对应的业务数据还可包括以下情况：管理模块702通过业务数据获取接口接收到业务SBB发送的业务数据获取请求时，则可根据业务数据获取请求中的业务标识信息，从对应业务之业务数据集合中为业务SBB分配对应的业务数据。
在本实施例的一种示例中，管理模块702根据业务数据获取请求中的业务标识信息，从对应业务之业务数据集合中为业务SBB分配对应的业务数据可包括：管理模块702在业务数据获取请求中包括版本号时(也即业务SBB已经绑定了版本号)，从业务数据获取请求中的业务标识信息所对应的业务之业务数据集合中，为业务SBB分配版本号对应的业务数据；否则表明业务SBB当前未绑定版本号，从业务数据获取请求中的业务标识信息所对应的业务之业务数据集合中，为业务SBB分配最新增加的业 务数据，也即为业务SBB分配最近的业务数据。
可选的，在本实施例的一些示例中，还可扩展业务数据查询接口，在需要时可通过业务数据查询接口下发业务数据查询指令进行对应业务数据的查询。在本示例中，管理模块702通过业务数据查询接口接收业务数据查询指令，业务数据查询指令中包括待查询业务数据的指示信息。管理模块702向查询方反馈待查询业务数据的指示信息所对应的业务数据。
可选的，在本实施例的一些示例中，还可扩展业务数据删除接口，在需要时可通过业务数据删除接口下发业务数据删除指令进行对应业务数据的删除。在本示例中，管理模块702通过业务数据删除接口接收业务数据删除指令，业务数据删除指令中包括待删除业务数据的指示信息。本示例中的业务数据删除指令可为配置客户端通过业务数据删除接口发送的，也可为其他设备发送的。管理模块702根据待删除业务数据的指示信息对待删除业务数据进行删除处理。
在本实施例的一种示例中，管理模块702根据待删除业务数据的指示信息对待删除业务数据进行删除处理可包括但不限于：管理模块702在确定待删除业务数据的指示信息对应的待删除业务数据当前被业务SBB调用时，将当前调用待删除业务数据的业务SBB所调用的业务数据清空，并在待删除业务数据的指示信息对应的待删除业务数据为当前最新设置的业务数据时，为待删除业务数据设置版本号；在一些实例中，可以直接对确定的待删除数据进行直接删除，在另一些示例中也可在后续通过后台统一对待删除业务数据进行清除，且当业务数据在存储文件有存储时，也在存储文件中对其进行一并清除。
例如，在本实施例的一些示例中，管理模块702还设置为按设定规则 (例如定时)将业务之业务数据集合中，当前未被业务SBB调用的业务数据，以及当前未被业务SBB调用的业务数据之版本号删除。例如，一种示例实现方式可为管理模块702可定时提取业务之业务数据集合中当前各业务数据的版本号得到第一版本号集合，以及提取业务对应的各业务SBB当前所绑定的版本号得到第二版本号集合，然后获取第二版本号集合在第一版本号集合内的绝对补集，将绝对补集中的版本号所对应的业务数据删除。也即将第一版本号集合中，在第二版本号集合内不存在的版本号(表明这些版本号对应的业务数据未被业务SBB调用，也即为不需要的业务数据)所对应的业务数据删除。
本实施例所提供的业务SBB的业务数据管理装置可以通过上述扩展的业务数据设置接口、业务数据查询接口、业务数据删除接口、业务数据获取接口等用于业务管理数据的接口，业务SBB可通过业务数据获取接口获取对应的业务数据，也可对应的配置客户端以及业务数据设置接口、业务数据查询接口、业务数据删除接口实现业务数据的增加、查询以及删除，并不需要卸载和重新安装业务，可提升业务数据设置和生效的实时性。
在一个示例性实施例中，还提供了一种通信设备，通信设备可以是作为服务端的设备，参见图8所示，其包括处理器801、存储器802以及通信总线803；
通信总线803设置为实现处理器801与存储器802之间的通信连接；
一种示例中，处理器801可设置为执行存储器802中存储的一个或者多个计算机程序，以实现如上各实施例中的业务SBB的业务数据管理方法的步骤。
在本示例中，在本示例中，上述业务SBB的业务数据管理装置设置于通信设备中时，业务SBB的业务数据管理装置的至少一个模块的功能可通过上述处理器实现。
本实施例还提供了一种计算机可读存储介质，计算机可读存储介质包括在用于存储信息(诸如计算机可读指令、数据结构、计算机程序模块或其他数据)的任何方法或技术中实施的易失性或非易失性、可移除或不可移除的介质。计算机可读存储介质包括但不限于RAM(Random Access Memory，随机存取存储器)，ROM(Read-Only Memory，只读存储器)，EEPROM(Electrically Erasable Programmable read only memory，带电可擦可编程只读存储器)、闪存或其他存储器技术、CD-ROM(Compact Disc Read-Only Memory，光盘只读存储器)，数字多功能盘(DVD)或其他光盘存储、磁盒、磁带、磁盘存储或其他磁存储装置、或者可以用于存储期望的信息并且可以被计算机访问的任何其他的介质。
在一种示例中，本实施例中的计算机可读存储介质可用于存储一个或者多个计算机程序，一个或者多个计算机程序可被一个或者多个处理器执行，以实现如上各实施例中的业务SBB的业务数据管理方法的步骤。
本实施例还提供了一种计算机程序(或称计算机软件)，计算机程序可以分布在计算机可读介质上，由可计算装置来执行，以实现如上各实施例所示的业务SBB的业务数据管理方法的至少一个步骤；并且在某些情况下，可以采用不同于上述实施例所描述的顺序执行所示出或描述的至少一个步骤。
本实施例还提供了一种计算机程序产品，包括计算机可读装置，计算机可读装置上存储有如上所示的计算机程序。本实施例中计算机可读装置 可包括如上所示的计算机可读存储介质。
根据本发明实施例提供的业务SBB的业务数据管理方法、装置、设备及存储介质，可扩展业务数据设置接口，在需要对业务数据进行设置时，可通过业务数据设置接口接收业务数据设置指令，根据业务数据设置指令中的业务标识信息和待设置的业务数据，在业务标识信息所对应业务之业务数据集合中增加待设置的业务数据，实现业务SBB的业务数据的设置，并不需要对业务进行卸载重装，从而提升业务数据设置的便捷性和效率，同时可避免因业务卸载而导致业务不能正常运行的情况发生；且当业务SBB需要配置业务数据时，可直接从业务SBB所对应的业务数据集合中，为业务SBB配置对应的业务数据，也即所设置的业务数据可即时生效并可供相应的SBB实时调用，进一步提升业务数据设置和生效的实时性。
可见，本领域的技术人员应明白，上文中所公开方法中的全部或某些步骤、系统、装置中的功能模块/单元可以被实施为软件(可以用计算装置可执行的计算机程序代码来实现)、固件、硬件及其适当的组合。在硬件实施方式中，在以上描述中提及的功能模块/单元之间的划分不一定对应于物理组件的划分；例如，一个物理组件可以具有多个功能，或者一个功能或步骤可以由若干物理组件合作执行。某些物理组件或所有物理组件可以被实施为由处理器，如中央处理器、数字信号处理器或微处理器执行的软件，或者被实施为硬件，或者被实施为集成电路，如专用集成电路。
此外，本领域普通技术人员公知的是，通信介质通常包含计算机可读指令、数据结构、计算机程序模块或者诸如载波或其他传输机制之类的调制数据信号中的其他数据，并且可包括任何信息递送介质。所以，本发明不限制于任何特定的硬件和软件结合。
以上内容是结合具体的实施方式对本发明实施例所作的进一步详细说明，不能认定本发明的具体实施只局限于这些说明。对于本发明所属技术领域的普通技术人员来说，在不脱离本发明构思的前提下，还可以做出若干简单推演或替换，都应当视为属于本发明的保护范围。
工业实用性
如上所述，本发明实施例提供的一种业务SBB的业务数据管理方法、装置、设备及存储介质具有以下有益效果：可扩展业务数据设置接口，在需要对业务数据进行设置时，可通过业务数据设置接口接收业务数据设置指令，根据业务数据设置指令中的业务标识信息和待设置的业务数据，在该业务标识信息所对应业务之业务数据集合中增加待设置的业务数据；从而提升业务数据设置的便捷性和效率；且在检测到业务SBB需要配置业务数据时，可直接从该业务SBB所对应的业务数据集合中为业务SBB配置对应的业务数据，也即所设置的业务数据可即时生效并可供相应的SBB实时调用，进一步提升业务数据设置和生效的实时性。

Claims (12)

  1. 一种业务SBB的业务数据管理方法，包括：
    通过业务数据设置接口接收业务数据设置指令，所述业务数据设置指令中包括业务标识信息以及待设置的业务数据；
    在所述业务标识信息所对应业务之业务数据集合中增加所述待设置的业务数据；
    当业务SBB需要配置业务数据时，从所述业务SBB所对应的业务数据集合中，为所述业务SBB配置对应的业务数据。
  2. 如权利要求1所述的业务SBB的业务数据管理方法，其中，所述在所述业务标识信息所对应业务之业务数据集合中增加所述待设置的业务数据包括：
    为所述业务之业务数据集合中上一次所增加的业务数据设置版本号，并将所述待设置的业务数据增加到所述业务之业务数据集合中，以及将所述待设置的业务数据存储于用于持久化存储业务数据的存储文件中。
  3. 如权利要求2所述的业务SBB的业务数据管理方法，其中，所述当业务SBB需要配置业务数据时，从所述业务SBB所对应的业务数据集合中，为所述业务SBB配置对应的业务数据包括：
    所述为所述业务之业务数据集合中上一次所增加的业务数据设置版本号后，当所述业务对应的业务SBB中存在未绑定版本号的业务SBB时，为所述未绑定版本号的业务SBB分配所述上一次所增加的业务数据，并将所述未绑定版本号的业务SBB与所述上一次所增加的业务数据的版本号绑定。
  4. 如权利要求1-3任一项所述的业务SBB的业务数据管理方法，其中，所述当业务SBB需要配置业务数据时，从所述业务SBB所对应的 业务数据集合中，为所述业务SBB配置对应的业务数据包括：
    通过业务数据获取接口接收到业务SBB发送的业务数据获取请求时，根据所述业务数据获取请求中的业务标识信息，从对应业务之业务数据集合中为所述业务SBB分配对应的业务数据。
  5. 如权利要求4所述的业务SBB的业务数据管理方法，其中，所述根据所述业务数据获取请求中的业务标识信息，从对应业务之业务数据集合中为所述业务SBB分配对应的业务数据包括：
    当所述业务数据获取请求中包括版本号时，从所述业务数据获取请求中的业务标识信息所对应的业务之业务数据集合中，为所述业务SBB分配所述版本号对应的业务数据；否则，从所述业务数据获取请求中的业务标识信息所对应的业务之业务数据集合中，为所述业务SBB分配最新增加的业务数据。
  6. 如权利要求1-3任一项所述的业务SBB的业务数据管理方法，其中，还包括：
    通过业务数据查询接口接收业务数据查询指令，所述业务数据查询指令中包括待查询业务数据的指示信息；
    向查询方反馈所述待查询业务数据的指示信息所对应的业务数据。
  7. 如权利要求1-3任一项所述的业务SBB的业务数据管理方法，其中，还包括：
    通过业务数据删除接口接收业务数据删除指令，所述业务数据删除指令中包括待删除业务数据的指示信息；
    根据所述待删除业务数据的指示信息对待删除业务数据进行删除处理。
  8. 如权利要求7所述的业务SBB的业务数据管理方法，其中，所述根据所述待删除业务数据的指示信息对待删除业务数据进行删除处理包括：
    在所述待删除业务数据的指示信息所指示的待删除业务数据当前被业务SBB调用时，将当前调用所述待删除业务数据的业务SBB所调用的业务数据清空，并在所述待删除业务数据为当前最新增加的业务数据时，为所述待删除业务数据设置版本号。
  9. 如权利要求8所述的业务SBB的业务数据管理方法，其中，还包括：
    按设定规则将业务之业务数据集合中，当前未被业务SBB调用的业务数据，以及当前未被业务SBB调用的业务数据之版本号删除。
  10. 一种业务SBB的业务数据管理装置，包括：
    接收模块，设置为通过业务数据设置接口接收业务数据设置指令，所述业务数据设置指令中包括业务标识信息以及待设置的业务数据；
    管理模块，设置为在所述业务标识信息所对应业务之业务数据集合中增加所述待设置的业务数据，以及用于当业务SBB需要配置业务数据时，从所述业务SBB所对应的业务数据集合中，为所述业务SBB配置对应的业务数据。
  11. 一种通信设备，包括处理器、存储器和通信总线；
    所述通信总线设置为将所述处理器和存储器连接；
    所述处理器设置为执行所述存储器中存储的计算机程序，以实现如权利要求1-9任一项所述的业务SBB的业务数据管理方法的步骤。
  12. 一种计算机可读存储介质，所述计算机可读存储介质存储有一个或多个计算机程序，所述一个或多个计算机程序可被一个或多个处理器执行，以实现如权利要求1-9任一项所述的业务SBB的业务数据管理方法的步骤。
PCT/CN2020/093990 2019-06-03 2020-06-02 业务sbb的业务数据管理方法、装置、设备及存储介质 WO2020244513A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP20819502.4A EP3961385A4 (en) 2019-06-03 2020-06-02 METHOD, APPARATUS AND DEVICE FOR SERVICE DATA MANAGEMENT FOR SERVICE SBB AND STORAGE MEDIA
US17/615,826 US11882007B2 (en) 2019-06-03 2020-06-02 Service data management method and apparatus for SBB, device and storage medium

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910478089.5A CN112035190A (zh) 2019-06-03 2019-06-03 业务sbb的业务数据管理方法、装置、设备及存储介质
CN201910478089.5 2019-06-03

Publications (1)

Publication Number Publication Date
WO2020244513A1 true WO2020244513A1 (zh) 2020-12-10

Family

ID=73575786

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/093990 WO2020244513A1 (zh) 2019-06-03 2020-06-02 业务sbb的业务数据管理方法、装置、设备及存储介质

Country Status (4)

Country Link
US (1) US11882007B2 (zh)
EP (1) EP3961385A4 (zh)
CN (1) CN112035190A (zh)
WO (1) WO2020244513A1 (zh)

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1536818A (zh) * 2003-04-10 2004-10-13 华为技术有限公司 一种业务逻辑运行环境实现的方法
US20080183514A1 (en) * 2007-01-29 2008-07-31 International Business Machines Corporation System and Methods for Using Solution Building Blocks
US20090217299A1 (en) * 2006-02-28 2009-08-27 Telecom Italia S.P.A. Communication Server With a Service Logic Execution Environment
CN106559447A (zh) * 2015-09-25 2017-04-05 中兴通讯股份有限公司 Jslee容器的业务处理方法及系统
CN106888233A (zh) * 2015-12-15 2017-06-23 北京新媒传信科技有限公司 数据更新系统及方法
CN108932126A (zh) * 2017-05-26 2018-12-04 北京国双科技有限公司 一种控件生成方法和装置

Family Cites Families (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6779030B1 (en) * 1997-10-06 2004-08-17 Worldcom, Inc. Intelligent network
US6002941A (en) * 1997-12-17 1999-12-14 Motorola, Inc. Method and apparatus for implementing a service in a wireless communication system
US20070150480A1 (en) * 2005-04-11 2007-06-28 Hans Hwang Service delivery platform
US8250531B2 (en) * 2007-04-09 2012-08-21 British Telecommunications Plc Service assembly architecture
US8924559B2 (en) * 2009-12-03 2014-12-30 International Business Machines Corporation Provisioning services using a cloud services catalog
CN105307058B (zh) 2014-06-09 2019-06-18 中兴通讯股份有限公司 业务配置数据的处理方法及装置
CN104125104B (zh) 2014-08-13 2017-05-17 烽火通信科技股份有限公司 一种光网络单元中业务数据的配置方法
US10033702B2 (en) * 2015-08-05 2018-07-24 Intralinks, Inc. Systems and methods of secure data exchange
CN106100917B (zh) 2016-08-30 2019-06-28 成都广达新网科技股份有限公司 一种网管匹配业务配置系统及其数据配置方法

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1536818A (zh) * 2003-04-10 2004-10-13 华为技术有限公司 一种业务逻辑运行环境实现的方法
US20090217299A1 (en) * 2006-02-28 2009-08-27 Telecom Italia S.P.A. Communication Server With a Service Logic Execution Environment
US20080183514A1 (en) * 2007-01-29 2008-07-31 International Business Machines Corporation System and Methods for Using Solution Building Blocks
CN106559447A (zh) * 2015-09-25 2017-04-05 中兴通讯股份有限公司 Jslee容器的业务处理方法及系统
CN106888233A (zh) * 2015-12-15 2017-06-23 北京新媒传信科技有限公司 数据更新系统及方法
CN108932126A (zh) * 2017-05-26 2018-12-04 北京国双科技有限公司 一种控件生成方法和装置

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3961385A4 *

Also Published As

Publication number Publication date
US11882007B2 (en) 2024-01-23
CN112035190A (zh) 2020-12-04
US20220329496A1 (en) 2022-10-13
EP3961385A4 (en) 2022-06-08
EP3961385A1 (en) 2022-03-02

Similar Documents

Publication Publication Date Title
WO2019090523A1 (zh) 一种无服务器架构下业务部署的方法和函数管理平台
RU2429529C2 (ru) Динамическое конфигурирование, выделение и развертывание вычислительных систем
US10158579B2 (en) Resource silos at network-accessible services
US10033816B2 (en) Workflow service using state transfer
JPWO2017170470A1 (ja) ネットワーク機能仮想化管理オーケストレーション装置と方法とプログラム
CN106936899B (zh) 分布式统计分析系统的配置方法及分布式统计分析系统
US7089550B2 (en) Method and system for performing SW upgrade in a real-time system
CN105893115B (zh) 差异化部署虚拟机的方法和系统
BR112016010555B1 (pt) Métodos e sistemas de serviço gerenciado para aquisição, armazenamento e consumo de fluxos de dados em grande escala, e mídias de armazenamento acessíveis por computador não transitório
US10310900B2 (en) Operating programs on a computer cluster
CN108551399B (zh) 一种云环境下服务的部署方法、系统及相关装置
CN110597918A (zh) 一种账户管理方法、装置及计算机可读存储介质
CN111385370B (zh) Id分配方法、装置、存储介质及id分配系统
CN110781149A (zh) 管理直播间信息的方法、装置、设备及存储介质
CN114553960A (zh) 一种数据缓存方法、装置、设备及存储介质
WO2022095844A1 (zh) 一种云硬盘挂载方法及其装置
JP2010272090A (ja) 処理依頼先管理装置、処理依頼先管理プログラムおよび処理依頼先管理方法
CN112181049B (zh) 集群时间同步方法、装置、系统、设备及可读存储介质
WO2020244513A1 (zh) 业务sbb的业务数据管理方法、装置、设备及存储介质
CN112559138B (zh) 一种资源调度系统及方法
WO2021248972A1 (zh) 默认网关管理方法、网关管理器、服务器及存储介质
CN106888244B (zh) 一种业务处理方法及装置
CN110971664B (zh) 一种接口服务管理系统
CN114064317A (zh) 分布式系统中的节点调用方法及相关装置
KR102156656B1 (ko) 가상머신 스택 생성 시스템 및 방법

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 20819502

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2020819502

Country of ref document: EP

Effective date: 20211126

NENP Non-entry into the national phase

Ref country code: DE