A data processing method and apparatus

Abstract

The application provides a data processing method and device. A superior tenant can achieve unified management and control of a service model. For example, the superior tenant can not modify a model identifier of a first service model deployed in a platform of the superior tenant, and a subordinate tenant can not actively update the first service model deployed in a platform of the subordinate tenant. In this way, the subordinate tenant does not actively modify the model identifier of the first service model deployed in the platform of the subordinate tenant, and the platform of the subordinate tenant is passively updated according to scheduling of the platform of the superior tenant to deploy the first service model, so that the model identifier of a new first service model deployed in the platform of the superior tenant and a new second service model deployed in the platform of the subordinate tenant are always the same. In turn, the situation that the second service model deployed in the platform of the subordinate tenant cannot be updated according to the scheduling of the superior tenant can be avoided.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of computer, in particular to a data processing method and device. BACKGROUND

[0002] With the rapid development of technology, various service models have been rapidly developed. Vendors can develop various service models and open them to the public for tenants to rent. Tenants can rent the service models opened by vendors, and tenants can also develop some service codes by themselves, and then generate their own service models according to the self-developed codes. Then, the tenants can generate applications according to the rented service models and the self-developed service models, and then provide services based on the applications. For example, the tenants can deploy the applications on their platforms to provide services to the general public through the applications deployed on the platforms. For example, in the scenario where the tenant's platform provides services to the general public, the tenant's platform can determine the service model of the application involved in the online data of the customer, and then call the determined service model to process the online data of the customer to provide services to the customer. SUMMARY

[0003] The present application shows a data processing method and device.

[0004] In a first aspect, a data processing method is shown, which is applied to a platform of a superior tenant. The platform of the superior tenant has a first service model deployed therein. The method comprises: receiving an update message sent by a platform of a subordinate tenant which is cascaded by the superior tenant, the update message being obtained by the platform of the subordinate tenant in a case where a second service model is newly deployed in the platform of the subordinate tenant, and the update message at least comprising a second model identifier of the second service model; obtaining the second model identifier of the second service model newly deployed in the platform of the subordinate tenant according to the update message, and obtaining first model identifiers of each first service model deployed in the platform of the superior tenant; in a case where the second model identifier is same as at least one first model identifier, the platform of the superior tenant outputs a same prompt information, and the same prompt information is used to indicate that the second model identifier is same as at least one first model identifier.

[0005] In a second aspect, a data processing method is shown, applied to a platform of a lower-level tenant, a first service model is deployed in a platform of an upper-level tenant to which the lower-level tenant is cascaded, and the method comprises: in a case where a second service model is newly deployed in the platform of the lower-level tenant, obtaining an update message, the update message comprising at least a second model identifier of the second service model; sending the update message to the platform of the upper-level tenant, so that the platform of the upper-level tenant receives the update message, obtains the second model identifier of the second service model newly deployed in the platform of the lower-level tenant according to the update message, and obtains first model identifiers of respective first service models deployed in the platform of the upper-level tenant, and in a case where the second model identifier is same as at least one of the first model identifiers, outputting same prompt information, the same prompt information being used to indicate that the second model identifier is same as at least one of the first model identifiers.

[0006] In a third aspect, a data processing method is shown, applied to a platform of an upper-level tenant, a first service model is deployed in the platform of the upper-level tenant, a second service model is deployed in a platform of a lower-level tenant to which the upper-level tenant is cascaded, and the second service model is same as or obtained by updating the first service model; the method comprises: obtaining a first update request, the first update request carrying a first model identifier of the first service model and a first base service framework of a first field that needs to be updated in the first service model; searching for the first service model deployed in the platform of the upper-level tenant according to the first model identifier; hot updating the first base service framework in the first service model, so as to hot update the first field in the first service model and obtain a new first service model; synchronizing the new first service model and the first model identifier to at least part of the platforms of the lower-level tenants to which the upper-level tenant is cascaded, so that the platforms of the lower-level tenants search for the second service model deployed in the platforms of the lower-level tenants according to the first model identifier, wherein a model identifier of the second service model is the first model identifier, the second service model deployed in the platforms of the lower-level tenants is hot updated using the new first service model, and a new second service model is obtained.

[0007] In a fourth aspect, a data processing method is shown, applied to a lower-level tenant platform, the second service model is deployed in the lower-level tenant platform, the first service model is deployed in an upper-level tenant platform to which the lower-level tenant is cascaded, the second service model is the same as the first service model or is obtained by updating the first service model; the method comprises: receiving a new first service model and a first model identifier sent by the upper-level tenant platform to which the lower-level tenant is cascaded; the new first service model and the first model identifier are sent by the upper-level tenant platform after the upper-level tenant platform obtains a first update request, the first service model deployed in the upper-level tenant platform is searched according to the first model identifier, the first basic service framework is hot-updated in the first service model to realize hot-updating of the first field in the first service model, and the new first service model is obtained; the first update request carries the first model identifier of the first service model and the first basic service framework of the first field that needs to be updated in the first service model; the second service model deployed in the lower-level tenant platform is searched according to the first model identifier, wherein the model identifier of the second service model is the first model identifier; the second service model deployed in the lower-level tenant platform is hot-updated using the new first service model to obtain a new second service model.

[0008] In a fifth aspect, a data processing apparatus is shown, applied to an upper-level tenant platform, the first service model is deployed in the upper-level tenant platform; the apparatus comprises: a first receiving module, configured to receive an update message sent by a lower-level tenant platform to which the upper-level tenant is cascaded, the update message is obtained by the lower-level tenant platform in a case that the second service model is newly deployed in the lower-level tenant platform, and the update message at least comprises a second model identifier of the second service model; a first obtaining module, configured to obtain the second model identifier of the second service model newly deployed in the lower-level tenant platform according to the update message, and obtain first model identifiers of the first service models deployed in the upper-level tenant platform; and a first output module, configured to output the same prompt information by the upper-level tenant platform in a case that the second model identifier is the same as at least one first model identifier, the same prompt information is used to indicate that the second model identifier is the same as at least one first model identifier.

[0009] In a sixth aspect, a data processing apparatus is shown, applied to a platform of a subordinate tenant, a first service model being deployed in a platform of a superior tenant to which the subordinate tenant is cascaded, the apparatus comprising: a second acquisition module, configured to acquire an update message in a case that a second service model is newly deployed in the platform of the subordinate tenant, the update message comprising at least a second model identifier of the second service model; and a second sending module, configured to send the update message to the platform of the superior tenant, so that the platform of the superior tenant receives the update message, acquires the second model identifier of the second service model newly deployed in the platform of the subordinate tenant according to the update message, and acquires first model identifiers of respective first service models deployed in the platform of the superior tenant, and in a case that the second model identifier is identical to at least one of the first model identifiers, outputs identical prompt information, the identical prompt information being used to indicate that the second model identifier is identical to at least one of the first model identifiers.

[0010] In a seventh aspect, a data processing apparatus is shown, applied to a platform of a superior tenant, a first service model being deployed in the platform of the superior tenant, a second service model being deployed in a platform of a subordinate tenant to which the superior tenant is cascaded, the second service model being identical to the first service model or the second service model being obtained by updating the first service model; the apparatus comprising: a third acquisition module, configured to acquire a first update request, the first update request carrying a first model identifier of the first service model and a first base service framework of a first field needed to be updated in the first service model; a first searching module, configured to search for the first service model deployed in the platform of the superior tenant according to the first model identifier; a first hot updating module, configured to hot update the first base service framework in the first service model, so as to realize hot updating of the first field in the first service model and obtain a new first service model; and a synchronizing module, configured to synchronize the new first service model and the first model identifier to at least part of the platforms of the subordinate tenants to which the superior tenant is cascaded, so that the platforms of the subordinate tenants search for the second service model deployed in the platforms of the subordinate tenants according to the first model identifier, wherein a model identifier of the second service model is the first model identifier, the second service model deployed in the platforms of the subordinate tenants is hot updated using the new first service model, and a new second service model is obtained.

[0011] In an eighth aspect, a data processing apparatus is shown, applied to a lower-level tenant platform, a second service model is deployed in the lower-level tenant platform, a first service model is deployed in an upper-level tenant platform to which the lower-level tenant is cascaded, the second service model is the same as the first service model or the second service model is obtained after the first service model is updated; the apparatus comprises: a fourth receiving module configured to receive a new first service model and a first model identifier sent by the upper-level tenant platform to which the lower-level tenant is cascaded; the new first service model and the first model identifier are sent to the lower-level tenant platform after the upper-level tenant platform obtains a first update request, searches the first service model deployed in the upper-level tenant platform according to the first model identifier, and hot-updates the first basic service framework in the first service model to achieve hot-updating the first field in the first service model to obtain the new first service model; the first update request carries the first model identifier of the first service model and the first basic service framework of the first field that needs to be updated in the first service model; a second searching module configured to search the second service model deployed in the lower-level tenant platform according to the first model identifier, wherein the model identifier of the second service model is the first model identifier; and a second hot-updating module configured to hot-update the second service model deployed in the lower-level tenant platform using the new first service model to obtain a new second service model.

[0012] In a ninth aspect, an electronic device is shown, comprising: a processor; a memory for storing processor-executable instructions; wherein the processor is configured to execute the method shown in any one of the preceding aspects.

[0013] In a tenth aspect, a non-transitory computer-readable storage medium is shown, when instructions in the storage medium are executed by a processor of an electronic device, the electronic device can execute the method shown in any one of the preceding aspects.

[0014] In an eleventh aspect, a computer program product is shown, when instructions in the computer program product are executed by a processor of an electronic device, the electronic device can execute the method shown in any one of the preceding aspects.

[0015] Compared with the prior art, the present application has the following advantages:

[0016] In the first aspect, the second aspect, the fifth aspect, and the sixth aspect, after the subordinate tenant newly deploys the second service model in the platform of the subordinate tenant, the superior tenant can determine in a timely manner whether the second model identifier of the newly deployed second service model in the platform of the subordinate tenant is the same as the first model identifier of the at least one first service model deployed in the platform of the superior tenant. If the second model identifier of the newly deployed second service model in the platform of the subordinate tenant is the same as the first model identifier of the at least one first service model deployed in the platform of the superior tenant, the superior tenant can be notified in a timely manner that the second model identifier of the newly deployed second service model in the platform of the subordinate tenant is the same as the first model identifier of the at least one first service model deployed in the platform of the superior tenant, so that the superior tenant can intervene in a timely manner (for example, the staff of the superior tenant intervenes or the platform of the superior tenant automatically intervenes), for example, the condition that the second model identifier of the newly deployed second service model in the platform of the subordinate tenant is the same as the first model identifier of the at least one first service model deployed in the platform of the superior tenant is eliminated in a timely manner, that is, the second model identifier of the newly deployed second service model in the platform of the subordinate tenant is different from the first model identifier of each first service model deployed in the platform of the superior tenant, so that the superior tenant can avoid the condition that the one first service model deployed in the platform of the subordinate tenant cannot be updated according to the scheduling of the superior tenant.

[0017] In the third aspect, the fourth aspect, the seventh aspect, and the eighth aspect, when the superior tenant updates the first service model deployed in the platform of the superior tenant, the superior tenant can uniformly control the service model. For example, the superior tenant can not modify the model identifier of the first service model deployed in the platform of the superior tenant, and the subordinate tenant can not actively update the first service model deployed in the platform of the subordinate tenant. In this way, the subordinate tenant does not actively modify the model identifier of the first service model deployed in the platform of the subordinate tenant, and the platform of the subordinate tenant passively updates the first service model deployed in the platform of the subordinate tenant according to the scheduling of the platform of the superior tenant. For example, the subordinate tenant can receive the new first service model synchronized by the superior tenant, and use the new first service model to hot update the corresponding second service model in the platform of the subordinate tenant, so that the model identifier of the new first service model deployed in the platform of the superior tenant is always the same as the model identifier of the new second service model deployed in the platform of the subordinate tenant. In this way, the superior tenant can avoid the condition that the second service model deployed in the platform of the subordinate tenant cannot be updated according to the scheduling of the superior tenant. BRIEF DESCRIPTION OF DRAWINGS

[0018] Figure 1 is a structural block diagram of a data processing system of the present application.

[0019] Figure 2is a step flow chart of a data processing method of the present application.

[0020] Figure 3 is a step flow chart of a data processing method of the present application.

[0021] Figure 4 is a structure block diagram of a data processing device of the present application.

[0022] Figure 5 is a structure block diagram of a data processing device of the present application.

[0023] Figure 6 is a structure block diagram of a data processing device of the present application.

[0024] Figure 7 is a structure block diagram of a data processing device of the present application.

[0025] Figure 8 is a structure block diagram of a device of the present application. DETAILED DESCRIPTION

[0026] In order to make the above objectives, characteristics and advantages of the present application more apparent and easy to understand, the present application is further described in detail below with reference to the drawings and specific embodiments.

[0027] The platform of the tenant has an application for providing services to the outside, and the application is developed by at least the vendor and at least part of the models of the plurality of service models opened to the outside. For example, the vendor develops a plurality of service models and opens a plurality of service models to the outside, and the functions of different service models are different. The tenant can develop the application by at least the service models opened to the outside by the vendor (the application includes the service models developed by the vendor and opened to the outside, and of course, can also include service models developed by the tenant, etc.), and provide services to the general customers based on the application.

[0028] Different tenants can generate their own applications by means of the service models opened to the outside by the vendor, and deploy their own applications in their own platforms, and then provide services to the general customers based on the applications deployed in their own platforms.

[0029] In one scenario, the tenants are not completely independent of each other, and sometimes, some tenants have a hierarchical or belonging cascade relationship (such as a superior-subordinate relationship, etc.), for example, a group has a head office and various branch companies, and the branch companies are subordinate to the head office, and the head office and the branch companies can each be a tenant to develop an application by means of the service models opened to the outside by the vendor, and at the tenant level, the head office and the branch companies are independent tenants.

[0030] However, in order to realize the standardization and unification in the aspect of providing services to the outside and in the aspect of management, the head office needs to control the applications of the branches, for example, the head office needs to control at least the service models in the applications of the branches.

[0031] As a tenant, the head office can select some service models from the service models opened to the outside by the vendor according to the actual needs of the whole group (for example, the standardized service needs of the group, etc.), and secondly, the head office can also develop some computer program codes according to the actual needs of the whole group, and generate service models according to the developed computer program codes (self-developed service models, the functions of the self-developed service models are not possessed by the service models opened to the outside by the vendor), for example, the head office needs some functions in the application, but the service models provided by the vendor cannot realize these functions, then the head office can develop computer program codes by itself to generate service models through the self-developed computer program codes, and then realize these functions.

[0032] In this way, the head office has the service models selected from the service models opened to the outside by the vendor and the self-developed service models, and then can generate applications according to the selected service models and the self-developed service models. The generated applications can be standardized applications of the group, for example, applications capable of processing standardized services involving the whole group, etc., which have the function of standardization, and the service models in the applications developed by the head office can be regarded as baseline models. The head office can deploy the developed applications in the platform of the head office, so that the platform of the head office can provide services to the outside (for example, provide services to the general customers, etc.) based on the applications.

[0033] In addition, after the head office develops the applications, the developed applications can be dispatched to each branch at the same time, so that each branch also has its own application. The branches can deploy the applications dispatched by the head office in the platforms of the branches, and then the platforms of the branches can provide services to the outside (for example, provide services to the general customers, etc.) based on the applications.

[0034] In this way, the platform of the head office and the platforms of the branches in the group can all use the developed applications of the head office to process data. So that the platform of the head office and the platforms of the branches in the group can all process online data (externally sent) according to the requirements of standardization, and the head office and the branches in the group can all provide services to the outside according to the requirements of standardization.

[0035] However, the inventors find that sometimes, the branches in the group are spread all over the world, and the services provided by the branches are not completely the same, but often have some differences, that is, the branches often need to provide personalized services to the outside, so that the functions (such as personalized functions, etc.) involved in the services provided by the branches to the outside are not completely the same, but often have some differences.

[0036] However, when the head office generates an application at least by means of the service model provided by the vendor, it may only consider the standardization of the entire group, and not the differentiation or personalization of the branches in the group, resulting in that the platform of the branches may not be able to meet the actual differentiated or personalized needs of the branches when using the application generated by the head office to provide services to the outside, for example, cannot provide personalized services of the branches to the outside.

[0037] However, in order to realize the standardization and unification in the aspects of providing services to the outside and management of the group, the head office needs to control the applications of the branches, for example, needs to control the service model in the applications of the branches. In this way, the branches cannot abandon the application developed by the head office and cannot redevelop the application by themselves, and the functions of the application used by the branches need to include the functions of the application used by the head office, otherwise it will destroy the standardized services of the entire group.

[0038] Therefore, for the branches, the branches can update the application (the application developed by the head office and dispatched to the branches) deployed in the platform of the branches according to their actual needs.

[0039] For example, the developers of the branches can further update the application (the application developed by the head office and dispatched to the branches) deployed in the platform of the branches (without destroying the standardization of the application deployed in the platform of the branches) to make the application deployed in the platform of the branches meet the personalized needs of the branches, for example, to be able to provide personalized services of the branches to the outside, etc.

[0040] For example, for one of the service models in the application, in order to make the service model meet the personalized needs of the branches, so that the branches can provide personalized services to the outside based on the service model, the branches may need to update the service model according to their actual needs, for example, expand the functions of the service model, etc., for example, add a field in the service model in the application deployed in the platform of the branches, the added field has personalized functions, so that the functions of the service model can be expanded to enable the branches to provide personalized services to the outside based on the service model.

[0041] In addition, after the branch company updates the service model in the application deployed in the platform of the branch company, the model identifier of the service model may be modified.

[0042] For example, in one example, the application deployed in the platform of the branch company (the application developed by the parent company and dispatched to the branch company) includes multiple service models, such as a commodity model, an order model, a user model, and a game model.

[0043] The user model has a username field for managing the username of a user, a user email field for managing the email of the user, and the like.

[0044] In the case where the branch company has a service of selling commodities on the network, the mailing address of a user is often required in the scenario where the platform of the branch company provides services to the outside. Therefore, in view of this requirement, the branch company has an additional requirement of managing the mailing address of a user in the user model in the application deployed in the platform of the branch company. Since the platform of the branch company needs to use the application deployed in the platform of the branch company when providing services to the outside, the branch company can add a user address field to the user model in the application deployed in the platform of the branch company, so that the user model in the application deployed in the platform of the branch company can manage the mailing address of a user based on the user address field, to meet the actual requirements of the branch company, for example, the branch company can manage the mailing address of a user based on the user model in the application.

[0045] In addition, after the branch company adds the user address field to the user model in the application deployed in the platform of the branch company, the model identifier of the user model may be modified.

[0046] However, the inventors have found that after the branch company updates the service model in the application deployed in the platform of the branch company, there may be some problems:

[0047] For example, the application deployed in the platform of the parent company has the service model, the application deployed in the platform of the branch company has the updated service model, but after the branch company updates the service model in the application deployed in the platform of the branch company, if the model identifier of the service model is modified, the model identifier of the service model in the application deployed in the platform of the parent company is different from the model identifier of the updated service model in the application deployed in the platform of the branch company.

[0048] In addition, sometimes the group's standardized services may change with actual needs. The changed standardized services involve the service model, and in order to adapt to the changed standardized services, the head office needs to adaptively update the service model in the application. For example, the functionality of the service model can be extended, such as adding fields to the service model in the application deployed on the head office's platform, and adding fields with the changed standardized functions. In this way, the standardized functions of the extended service model can be achieved.

[0049] However, after the head office updates the service model in the applications deployed on the head office platform, in order to maintain consistency between the applications deployed on the head office platform and the applications deployed on the branch office platforms, the head office will not modify the model identifier of the service model.

[0050] Secondly, the head office was unaware that the service model identifier had been modified after the branch office updated the service model in the application deployed on the branch office's platform, and the head office had no motivation to modify the service model identifier after the branch office updated the service model in the application deployed on the head office's platform.

[0051] For example, in one instance, the application deployed on the head office platform and the application deployed on the branch office platform both include multiple service models, such as product models, order models, user models, and game models.

[0052] The user model includes fields such as username and email. The username field is used to manage user usernames, and the email field is used to manage user email addresses.

[0053] When both the head office and branch offices offer online sales services, the provision of these services on both platforms often requires logistics information. Therefore, both the user models deployed on the head office platform and the user models deployed on the branch office platform need to manage this logistics information. Consequently, a logistics information field can be added to both the user models on the head office platform and the user models on the branch office platform. This allows the user models on the head office platform to manage the logistics information of purchased goods based on this field, thus meeting the head office's needs, and vice versa.

[0054] In order to achieve standardization and uniformity in providing services and management to external parties within the group, the head office needs to control the applications of each branch. For example, the head office needs to control the service models used in the applications of each branch, so that updates to the service models can be initiated and implemented by the head office.

[0055] For example, the head office could first update the service model in the application deployed on the head office's platform to obtain the updated service model.

[0056] The head office can then synchronize the updated service model to the branch office's platform, so that the branch office's platform can receive the updated service model and deploy the updated service model on the branch office's platform.

[0057] For example, the head office platform can send a scheduling instruction to the branch office platform. The scheduling instruction carries the head office's updated service model and the model identifier of the updated service model, instructing the branch office platform to update the service model corresponding to the model identifier deployed on the branch office platform using the head office's updated service model.

[0058] However, from the perspective of the head office, the head office generally assumes that the branch office will not change the model identifier of the service model deployed on the branch office's platform. Therefore, the model identifier carried by the scheduling instruction is the model identifier of the service model before the branch office updated the service model.

[0059] However, if a branch office updates the service model deployed on its platform and then modifies the model identifier of the updated service model deployed on the branch office's platform, the model identifier of the updated service model at the head office will be different from that at the branch office. Consequently, after receiving a scheduling instruction, the branch office will not be able to find the service model corresponding to the model identifier carried by the scheduling instruction in the application deployed on its platform. Therefore, it will be unable to use the updated service model from the head office to update the service model corresponding to the model identifier deployed on the branch office's platform, thus making it impossible to update the service model deployed on the branch office's platform according to the head office's scheduling.

[0060] To avoid the above situation, the inventors came up with the idea of ​​planning and managing the model identifiers of service models deployed in the platforms of various branch offices cascaded by the head office from the perspective of the head office.

[0061] Furthermore, given that branch offices have the need to update applications deployed on their platforms (applications developed by the head office and scheduled to the branch offices) according to their own actual needs, the head office can conduct unified planning and management of the model identification of applications deployed on the branch offices' platforms from the head office's perspective.

[0062] For example, in one scenario, if a branch office needs to update the service model deployed on its platform, it can submit an update request to the head office. The head office can evaluate the update request submitted by the branch office (including evaluating the model identifier of the service model involved in the update, such as evaluating whether the model identifier of the service model after the update is the same as the model identifier of the service model in the application deployed on the head office's platform). If the head office evaluates the update request and allows it (for example, if the model identifier of the service model after the update is the same as the model identifier of the service model in the application deployed on the head office's platform), the branch office can then update the service model in the application deployed on its platform.

[0063] For example, refer to Figure 1 The diagram shows a structural block diagram of a data processing system according to this application. The system includes a platform 01 for an upper-level tenant (e.g., the head office of a group) and a platform 02 for a lower-level tenant (e.g., a branch office of a group) cascaded by the upper-level tenant.

[0064] In this system, the platforms of the upper-level tenants communicate with the platforms of the lower-level tenants that are cascaded by the upper-level tenants.

[0065] The platform of the upper-level tenant can be a platform used by the staff of the upper-level tenant. The staff of the upper-level tenant can update, adjust and otherwise control the service model deployed in the upper-level tenant through the platform of the upper-level tenant.

[0066] The platform of a lower-level tenant cascaded by an upper-level tenant can be a platform used by the staff of the lower-level tenant. The staff of the lower-level tenant can request updates, adjustments and other operations on the service models deployed on the lower-level tenant's platform through the lower-level tenant's platform.

[0067] In one example, the upper-level tenant may include the head office of the aforementioned group, and the lower-level tenant may include the various branches of the aforementioned group, with each branch of the group serving as a separate lower-level tenant.

[0068] A higher-level tenant can cascade with a lower-level tenant, and a lower-level tenant can cascade with an even lower-level tenant, and so on. This application does not limit the specific cascading levels.

[0069] In one scenario, the platform of the upper-level tenant deploys the first service model, and the platforms of the lower-level tenants cascaded by the upper-level tenant deploy the second service model.

[0070] The platform that deploys the second service model for the lower-level tenant can be one or more.

[0071] The second service model is the same as the first service model, or the second service model is obtained by updating the first service model (the second service model has all the functions of the first service model, and the second service model may also have functions that the first service model does not have. For example, the second service model has all the fields of the first service model, and the second service model may also have fields that the first service model does not have).

[0072] The model identifier of the second service model is the same as that of the first service model; for example, both are the first model identifier.

[0073] Sometimes there is a need to update the first service model. The first service model and the second service model can be regarded as corresponding (or related). Thus, updating the first service model can be regarded as at least as updating the first service model deployed in the platform of the upper-level tenant and updating the second service model deployed in the platforms of each lower-level tenant.

[0074] The need to update the first service model can be initiated by an upper-level tenant, or it can be initiated by a lower-level tenant, which in turn triggers the need to update the first service model.

[0075] In this application, when it is necessary to update the first service model, the platform of the upper-level tenant can first update the first service model to obtain a new first service model. Then, the platform of the upper-level tenant can synchronize the new first service model with the platform of the lower-level tenant, so that the platform of the lower-level tenant can use the new first service model to hot update the second service model in the platform of the lower-level tenant to obtain a new second service model.

[0076] In this way, when an upstream tenant updates a service model deployed on its platform, it can achieve unified control over the service model. For example, the upstream tenant may not need to modify the model identifier of the service model deployed on its platform, and the downstream tenant may not need to actively update the service model deployed on its platform. Thus, the downstream tenant's platform passively updates the service model deployed on its platform according to the scheduling of the upstream tenant's platform. For example, the downstream tenant can receive a new service model synchronized by the upstream tenant and use the new service model to hot update the corresponding service model in the downstream tenant's platform, so that the model identifier of the same service model in the upstream tenant's platform and the downstream tenant's platform are always the same.

[0077] Subsequently, after the upstream tenant updates the new service model deployed on its platform to obtain an updated service model (the updated service model is different from the new service model; it can be considered the next version of the new service model), the upstream tenant can synchronize the updated service model to the downstream tenant's platform so that the downstream tenant's platform receives the updated service model. For example, the upstream tenant's platform can send a scheduling instruction to the downstream tenant's platform, carrying the upstream tenant's updated service model and its model identifier, to instruct the downstream tenant's platform to update the service model corresponding to that model identifier deployed on its platform using the upstream tenant's updated service model. The downstream tenant will not update the service model deployed on its platform itself, nor will it modify the model identifier of the service model deployed on its platform. In this way, the model identifier of the updated service model deployed on the upper-level tenant's platform is the same as the model identifier of the corresponding service model on the lower-level tenant's platform. This allows the lower-level tenant's platform to find the service model corresponding to the model identifier carried in the scheduling instruction after receiving it. Consequently, the updated service model deployed on the upper-level tenant's platform can be used to update the service model corresponding to the same model identifier deployed on the lower-level tenant's platform. This achieves the updating of service models deployed on the lower-level tenant's platform according to the upper-level tenant's scheduling, avoiding situations where updating service models deployed on the lower-level tenant's platform is impossible based on the upper-level tenant's scheduling.

[0078] For example, when an upstream tenant updates the first service model deployed on its platform, unified management of the service model can be achieved. For instance, the upstream tenant may not modify the model identifier of the first service model deployed on its platform, and the downstream tenant may not actively update the first service model deployed on its platform. Thus, the downstream tenant's platform passively updates the first service model deployed on its platform according to the scheduling of the upstream tenant's platform. For example, the downstream tenant may receive the new first service model synchronized by the upstream tenant and use the new first service model to hot-update the corresponding second service model on its platform, so that the model identifiers of the new first service model deployed on the upstream tenant's platform and the new second service model deployed on the downstream tenant's platform are always the same.

[0079] Subsequently, after the upper-level tenant updates the new first service model deployed on its platform to obtain an updated first service model (the updated first service model is different from the new first service model; it can be considered the next version of the new first service model), the upper-level tenant can synchronize the updated first service model to the lower-level tenant's platform so that the lower-level tenant's platform receives the updated first service model. For example, the upper-level tenant's platform can send a scheduling instruction to the lower-level tenant's platform, carrying the upper-level tenant's updated first service model and its model identifier, to instruct the lower-level tenant to use the upper-level tenant's updated first service model to update the new second service model corresponding to that model identifier deployed on the lower-level tenant's platform. The lower-level tenant will not update the new second service model deployed on its platform itself, nor will it modify the model identifier of the new second service model deployed on its platform. In this way, the model identifier of the updated first service model deployed on the upper-level tenant's platform is the same as the model identifier of the new second service model deployed on the lower-level tenant's platform. This allows the lower-level tenant's platform to find the new second service model corresponding to the model identifier carried in the scheduling instruction after receiving it. The updated first service model deployed on the upper-level tenant's platform can then be used to update the new second service model corresponding to the same model identifier deployed on the lower-level tenant's platform. This achieves the updating of the second service model deployed on the lower-level tenant's platform according to the upper-level tenant's scheduling, avoiding situations where the second service model deployed on the lower-level tenant's platform cannot be updated according to the upper-level tenant's scheduling.

[0080] In this scenario, refer to Figure 2 The diagram illustrates a flowchart of a data processing method according to this application. This method is applied to... Figure 1 In the system shown, the method includes:

[0081] In step S101, the platform of the upper-level tenant obtains the first update request. The first update request carries the first model identifier of the first service model and the first basic service framework of the first field that needs to be updated in the first service model.

[0082] In one embodiment of this application, the upstream tenant may need to standardize and update the first service model according to actual needs. For example, if the upstream tenant needs to update a first field in the first service model, it can submit a first update request to its platform. The upstream tenant's platform can then obtain this first update request. In this embodiment, the update to the first service model is initiated by the upstream tenant.

[0083] Updating the first field in the first service model includes adding the first field to the first service model or modifying the first field in the first service model (if the first field already exists in the first service model).

[0084] Alternatively, in another embodiment of this application, the lower-level tenant may need to update the first service model according to actual needs. For example, if the lower-level tenant needs to update a first field in the first service model, it can submit a first update request to its platform. The lower-level tenant's platform can then receive the first update request submitted by the lower-level tenant. In this embodiment, to control the service model of the lower-level tenant based on the upper-level tenant, the lower-level tenant needs to update the first field in the first service model through the upper-level tenant to obtain a new first service model. Then, the upper-level tenant's platform synchronizes the new first service model to the lower-level tenant's platform. For example, the lower-level tenant's platform can upload the first update request to the upper-level tenant's platform, and then the upper-level tenant's platform can receive the first update request uploaded by the lower-level tenant's platform. In this embodiment, the update of the first service model is initiated by the lower-level tenant.

[0085] The first basic service framework includes the basic functional components needed to implement the functionality of the first field. These functional components include classes and functions required to implement the functionality of the first field.

[0086] In step S102, the platform of the upper-level tenant locates the first service model deployed in the platform of the upper-level tenant based on the first model identifier.

[0087] In this application, the platform of the upper-level tenant may deploy multiple different service models. Therefore, the platform of the upper-level tenant can index out the first service model in the platform of the upper-level tenant based on the first model identifier.

[0088] In step S103, the first basic service framework is hot-updated in the first service model to achieve hot-updating of the first field of the first service model and obtain a new first service model.

[0089] In this application, a first basic service framework can be hot-integrated into the first service model to achieve hot updating of the first field of the first service model and obtain a new first service model. In this way, the new first service model deployed in the platform of the upper-level tenant has the function corresponding to the first field.

[0090] The model identifier for the new first service model is the first model identifier.

[0091] Both the model identifier of the first service model and the model identifier of the second service model can be the first model identifier, etc.

[0092] In step S104, the platform of the upper-level tenant synchronizes the new first service model and the first model identifier with the platforms of at least some of the lower-level tenants that are cascaded to the upper-level tenant.

[0093] For any one of the platforms of at least some of the lower-level tenants, the platform of the upper-level tenant has a communication connection with the platform of that lower-level tenant. Thus, the platform of the upper-level tenant can send a new first service model and a first model identifier to the platform of that lower-level tenant through the communication connection between the platform of the upper-level tenant and the platform of that lower-level tenant.

[0094] In this application, there are many service models deployed on the upper-level tenant platform and many service models deployed on the lower-level tenant platform.

[0095] For lower-level tenants, some service models deployed on their platforms are core models related to standardized services, while other service models deployed on their platforms are personalized models. Personalized models are deployed by lower-level tenants on their platforms to meet their specific personalized needs.

[0096] Each sub-tenant's platform has a core model related to standardized services deployed. Some sub-tenants' platforms do not have personalized models deployed, while others do. Furthermore, the personalized models deployed on each of the other sub-tenants' platforms are not entirely the same.

[0097] In one embodiment, if the first service model is a core model related to standardized services, then each subordinate tenant's platform deploys a second service model (the second service model is the same as the first service model or is an updated version of the first service model). Therefore, the second service model needs to be hot-updated using the new first service model on each subordinate tenant's platform. In this way, the upper-level tenant's platform can synchronize the new first service model and its identifier to all subordinate tenants cascaded with the upper-level tenant.

[0098] Alternatively, in another embodiment, if the first service model is a personalized model (in which case the second service model is also a personalized model), since not every subordinate tenant's platform may have a personalized model deployed, that is, not every subordinate tenant's platform may have a second service model deployed (the second service model is the same as the first service model or the second service model is an update of the first service model), it is necessary to determine the subordinate tenant's platform with the second service model deployed among multiple subordinate tenants' platforms, and then synchronize the new first service model and the first model identifier to the subordinate tenant's platform with the second service model deployed.

[0099] In the case where the first service model is a personalized model (in which case the second service model is also a personalized model), the platform of the lower-level tenant that has deployed the second service model tends to subscribe to the first service model, while the platform of the lower-level tenant that has not deployed the second service model tends not to subscribe to the first service model.

[0100] If a lower-level tenant's platform subscribes to the first service model, then after the upper-level tenant's platform updates the first service model, the new first service model and the first model identifier can be synchronized to the lower-level tenant's platform.

[0101] Alternatively, if a lower-level tenant's platform has not subscribed to the first service model, then after the upper-level tenant's platform updates the first service model, the new first service model and the first model identifier may not be synchronized to the lower-level tenant's platform.

[0102] Thus, when synchronizing the new first service model and first model identifier to the platforms of at least some of the lower-level tenants cascaded to the upper-level tenant, the lower-level tenants that have subscribed to the first service model can be selected from among the multiple lower-level tenants cascaded to the upper-level tenant, and then the new first service model and first model identifier can be synchronized to the platforms of the lower-level tenants that have subscribed to the first service model.

[0103] In this application, whenever a subordinate tenant subscribes to a first service model from a superior tenant's platform, the superior tenant's platform can store the subordinate tenant's tenant identifier in the subscription list corresponding to the first service model. Different subordinate tenants have different tenant identifiers.

[0104] Thus, when filtering the sub-tenants who subscribe to the first service model, the tenant identifier in the subscription list corresponding to the first service model can be obtained, and the sub-tenant corresponding to the obtained tenant identifier can be used as the sub-tenant who subscribes to the first service model.

[0105] Sub-tenants subscribing to the first service model include those who submit the first update request.

[0106] Alternatively, in another embodiment, if the first update request is submitted by the platform of the target lower-level tenant to the platform of the upper-level tenant, then the new first service model and the first model identifier can be synchronized to the platform of the target lower-level tenant, wherein the target lower-level tenant includes one of the multiple lower-level tenants cascaded by the upper-level tenant.

[0107] Specifically, for any one of the platforms of at least some of the lower-level tenants, the process of steps S104 to S105 can be executed, and the same applies to the platforms of each other lower-level tenant in the platform of some of the lower-level tenants.

[0108] In step S105, the lower-level tenant's platform receives the new first service model and the first model identifier synchronized from the upper-level tenant's platform.

[0109] The lower-level tenant's platform can receive the new first service model and first model identifier sent by the upper-level tenant's platform through the communication connection between the lower-level tenant's platform and the upper-level tenant's platform.

[0110] In step S106, the lower-level tenant's platform locates the second service model deployed in the lower-level tenant's platform based on the first model identifier, wherein the model identifier of the second service model is the first model identifier.

[0111] In step S107, the lower-level tenant's platform uses the new first service model to hot update the second service model deployed in the lower-level tenant's platform, thus obtaining the new second service model.

[0112] The model identifier for the new second service model is the same as the model identifier for the new first service model.

[0113] In one embodiment of this application, each field of the second service model deployed in the lower-level tenant platform is a field of the first service model deployed in the upper-level tenant platform. In this case, the second service model can be replaced by the new first service model in the lower-level tenant platform.

[0114] Furthermore, in another embodiment of this application, after the second service model deployed in the lower-level tenant's platform is hot-updated using the new first service model on the lower-level tenant's platform, it may further include:

[0115] The lower-level tenant's platform generates a first notification message, indicating that the second service model deployed on the lower-level tenant's platform has been hot-updated using the new first service model and that the new second service model has been obtained. The lower-level tenant's platform sends the first notification message to the upper-level tenant's platform. The upper-level tenant's platform receives the first notification message.

[0116] The upper-level tenant's platform outputs a first notification message. For example, the first notification message is displayed on the lower-level tenant's platform so that the lower-level tenant's staff can be informed that the second service model deployed on the lower-level tenant's platform has been hot-updated using the new first service model and obtain the new second service model. This prevents the lower-level tenant's staff from unknowingly sending the first update request from the lower-level tenant's platform to the upper-level tenant's platform.

[0117] Additionally, first notification messages can be pushed to the staff of lower-level tenants via at least one of the following methods: SMS, in-site messaging, push channels, and social applications. Alternatively, at least two or more of the above methods can be selected simultaneously to push first notification messages to the staff of lower-level tenants, ensuring that the first notification messages are delivered to them as much as possible.

[0118] In one embodiment, when generating the first notification message, old fields already integrated in the second service model can be retrieved before the second service model deployed in the lower-level tenant's platform is hot-updated using the new first service model. The first concatenation relationship between the old fields is retrieved. The second concatenation relationship between the old fields and the first field is retrieved. A first schematic diagram can then be generated, indicating the first concatenation relationship, indicating the second concatenation relationship, and marking the first field as a hot-updated field. The first notification message is obtained based on the first schematic diagram; for example, the first schematic diagram can be used as the first notification message.

[0119] In this way, the staff of the upper-level tenant can see the first schematic diagram and quickly understand the first cascade relationship between the old fields and the second cascade relationship between the old fields and the first field based on the first schematic diagram. This allows them to have a macroscopic understanding of the first cascade relationship, the second cascade relationship, and the first field of the hot update in the second cascade relationship, thereby improving the convenience of the upper-level tenant's staff to have a macroscopic control over the fields in the first service model before the hot update and the fields in the new first service model.

[0120] The first visual diagram allows the staff of the upper-level tenant to quickly identify the cascading links of fields in the first service model before the hot update and the cascading links of fields in the new first service model. It can also quickly compare the differences between the cascading links of fields in the first service model before the hot update and the cascading links of fields in the new first service model, thereby improving the convenience and efficiency of comparison.

[0121] In another scenario, the platform of the upper-level tenant deploys the first service model, and the platform of the lower-level tenant cascaded by the upper-level tenant deploys the second service model.

[0122] The second service model is the same as the first service model, or the second service model is obtained by updating the first service model (the second service model has all the functions of the first service model, and the second service model may also have functions that the first service model does not have. For example, the second service model has all the fields of the first service model, and the second service model may also have fields that the first service model does not have).

[0123] The first service model and the second service model can be seen as corresponding (or related).

[0124] Sometimes, lower-level tenants need to update the second service model. In such cases, the lower-level tenant can directly update the second service model deployed on its platform.

[0125] However, as mentioned above, during the process of a lower-level tenant directly updating the second service model deployed on the lower-level tenant's platform, the model identifier of the second service model deployed on the lower-level tenant's platform may be modified. As a result, after the lower-level tenant updates the second service model deployed on the lower-level tenant's platform and obtains a new second service model, the model identifier of the new second service model deployed on the lower-level tenant's platform is different from the model identifier of the first service model deployed on the upper-level tenant's platform.

[0126] For example, a second service model is deployed in the platform of a lower-level tenant. The second service model is a service model involved in standardized services, not a service model involved in personalized services of the lower-level tenant's platform. The service model involved in standardized services is developed by the platform of the upper-level tenant and scheduled to the platform of the lower-level tenant. Thus, the second service model can be developed by the platform of the upper-level tenant and scheduled to the platform of the lower-level tenant.

[0127] In one embodiment of this application, the platform of the lower-level tenant can be configured or the second service model involved in the standardized service can be configured to prevent the second service model involved in the standardized service deployed in the lower-level tenant's platform from being updated. This avoids the lower-level tenant from updating the second service model involved in the standardized service deployed in the lower-level tenant's platform, thereby avoiding the situation mentioned above where the service model deployed in the lower-level tenant's platform cannot be updated according to the scheduling of the upper-level tenant.

[0128] Alternatively, in another embodiment, if the platform of the lower-level tenant updates the second service model (including modifying the model identifier of the second service model, adding new fields in the second service model, deleting existing fields in the second service model, and modifying existing fields in the second service model, etc.).

[0129] Therefore, after a lower-level tenant directly updates the second service model deployed on its platform and obtains a new second service model (including modifying the model identifier of the second service model, etc.), a change message can be sent to the upper-level tenant's platform. The change message is used to notify the lower-level tenant that it has directly updated the second service model deployed on its platform and obtained a new second service model. The change message can include relevant information about the new second service model deployed on the lower-level tenant's platform (including the model identifier, etc.), so that the upper-level tenant's platform can be aware of the event that "the lower-level tenant has directly updated the second service model deployed on its platform and obtained a new second service model". Afterwards, the upper-level tenant's platform can directly intervene or notify the upper-level tenant's staff to roll the second service model deployed in the lower-level tenant back to its state before the update (including rolling the second model identifier of the second service model deployed in the lower-level tenant back to the model identifier before the update, etc.).

[0130] For example, the platform of the upper-level tenant can receive a rollback command (which can be entered by the staff of the upper-level tenant in the platform). The rollback command is used to instruct the second service model deployed in the lower-level tenant to be rolled back to the state before the update (including the second model identifier of the second service model deployed in the lower-level tenant to the model identifier before the update, etc.). Then, the platform sends the rollback command to the platform of the lower-level tenant. The platform of the lower-level tenant receives the rollback command sent by the platform of the upper-level tenant and, according to the rollback command, rolls the second service model deployed in the lower-level tenant to the state before the update (including the second model identifier of the second service model deployed in the lower-level tenant to the model identifier before the update, etc.).

[0131] Subsequently, after the upstream tenant updates the new service model deployed on its platform to obtain an updated service model (the new service model differs from the updated one; the updated service model can be considered the next version of the new service model), the upstream tenant can synchronize the updated service model to the downstream tenant's platform, ensuring that the downstream tenant's platform receives the updated service model. For example, the upstream tenant's platform can send a scheduling instruction to the downstream tenant's platform, carrying the upstream tenant's updated service model and its model identifier, instructing the downstream tenant to update the service model corresponding to that model identifier deployed on its platform using the upstream tenant's updated service model. The downstream tenant will not update the service model deployed on its platform itself, nor will it modify the model identifier of the service model deployed on its platform. In this way, the model identifier of the updated service model deployed on the upper-level tenant's platform is the same as the model identifier of the corresponding service model on the lower-level tenant's platform. This allows the lower-level tenant's platform to find the service model corresponding to the model identifier carried in the scheduling instruction after receiving it. Consequently, the updated service model deployed on the upper-level tenant's platform can be used to update the service model corresponding to the same model identifier deployed on the lower-level tenant's platform. This achieves the updating of service models deployed on the lower-level tenant's platform according to the upper-level tenant's scheduling, avoiding situations where updating service models deployed on the lower-level tenant's platform is impossible based on the upper-level tenant's scheduling.

[0132] In another embodiment of this application, referring to Figure 3, a flowchart illustrating a data processing method of this application is shown. This method is applied to... Figure 1 In the system shown, the first service model is deployed on the platform of the upper-level tenant. The method includes:

[0133] In step S201, if a second service model is newly deployed on the platform of a lower-level tenant, the lower-level tenant's platform receives an update message. The update message includes at least the second model identifier of the second service model.

[0134] This application allows sub-tenants to directly add service models to their platforms based on their actual needs. For example, this application allows sub-tenants to directly add service models related to personalized services to their platforms based on their actual needs. In this way, sub-tenants can deploy a second service model on their platforms, and the newly deployed second service model has a second model identifier.

[0135] When a second service model is newly deployed in the platform of a lower-level tenant, the platform of the lower-level tenant can obtain the update message and then execute step S202.

[0136] In step S202, the lower-level tenant's platform sends an update message to the upper-level tenant's platform.

[0137] The platform of a lower-level tenant has a communication connection with the platform of the upper-level tenant. Thus, the platform of the lower-level tenant can send update messages to the platform of the upper-level tenant through the communication connection between the platform of the lower-level tenant and the platform of the upper-level tenant.

[0138] In step S203, the platform of the upper-level tenant receives the update message sent by the platform of the lower-level tenant.

[0139] The platform of an upper-level tenant can receive update messages based on the communication connection between it and the platform of a lower-level tenant.

[0140] In step S204, the upper-level tenant's platform obtains the second model identifier of the second service model newly deployed in the lower-level tenant's platform according to the update message, and obtains the first model identifier of each first service model deployed in the upper-level tenant's platform.

[0141] Specifically, the upper-level tenant's platform can extract the second model identifier of the newly deployed second service model in the lower-level tenant's platform from the update message. Furthermore, the upper-level tenant's platform deploys at least one service model, which can be considered as a first service model. Each first service model has its own model identifier, which can be considered as a first model identifier, and the first model identifiers of the different first service models are different.

[0142] In step S205, if the second model identifier is the same as at least one first model identifier, the platform of the upper-level tenant outputs the same prompt information, which is used to indicate that the second model identifier is the same as at least one first model identifier.

[0143] For example, the same notification message can be displayed on the platform of the upstream tenant so that the staff of the upstream tenant can know that the second model identifier is the same as at least one first model identifier, thus enabling earlier intervention. Alternatively, the same notification message can be pushed to the staff of the upstream tenant via at least one of the following methods: SMS, in-site message, push channel, and social applications. Of course, at least two or more of the above methods can be selected simultaneously to push the same notification message to the staff of the upstream tenant, to ensure that the same notification message is delivered to the staff of the upstream tenant as much as possible.

[0144] Among these measures, the staff of the upper-level tenant can communicate with the staff of the lower-level tenant as soon as possible and notify them to modify the second model identifier of the second service model deployed in the lower-level tenant's platform, so that the modified second model identifier is different from each first model identifier.

[0145] Alternatively, the platform of the upper-level tenant can send a modification instruction to the platform of the lower-level tenant. The modification instruction is used to instruct the modification of the second model identifier of the second service model deployed in the lower-level tenant. The platform of the lower-level tenant receives the modification instruction and then modifies the second model identifier of the second service model deployed in the lower-level tenant according to the modification instruction, so that the modified second model identifier is different from each first model identifier.

[0146] In order to ensure that the modified second model identifier is different from each first model identifier when the lower-level tenant's platform is modified only once, the modification command can also carry the first model identifiers of each first service model deployed in the upper-level tenant's platform. This allows the lower-level tenant to directly refer to the first model identifiers of each first service model deployed in the upper-level tenant's platform when modifying the second model identifier of the second service model deployed in the lower-level tenant's platform, so that the modified second model identifier is different from each first model identifier when the lower-level tenant's platform is modified only once.

[0147] Subsequently, the upper-level tenant's platform may simultaneously schedule at least some of the first service models deployed in the upper-level tenant's platform to be deployed in the lower-level tenant's platform. For example, the upper-level tenant's platform may schedule one of the first service models deployed in the upper-level tenant's platform to be deployed in the lower-level tenant's platform. If the second model identifier of the second service model deployed in the lower-level tenant's platform is the same as the first model identifier of the first service model, then there will be two service models with the same model identifier deployed in the lower-level tenant's platform. For example, there will be a situation where the model identifier of the second service model is the same as the model identifier of the first service model deployed in the lower-level tenant's platform.

[0148] Subsequently, the upper-level tenant may update the first service model deployed on its platform according to actual needs, resulting in an updated first service model. The upper-level tenant may then synchronize the updated first service model to the lower-level tenant's platform, so that the lower-level tenant's platform can obtain the updated first service model and use it to update the first service model already deployed on the lower-level tenant's platform.

[0149] For example, an upper-level tenant's platform can send a scheduling instruction to a lower-level tenant's platform. The scheduling instruction carries the upper-level tenant's updated first service model and the model identifier of the updated first service model, instructing the service model corresponding to the model identifier deployed in the lower-level tenant's platform to use the updated first service model (the purpose is to update the first service model corresponding to the model identifier).

[0150] However, because the model identifier of the second service model deployed in the lower-level tenant's platform is the same as the model identifier of the first service model, after receiving the scheduling instruction, the lower-level tenant may first find the second service model instead of the first service model among the service models deployed in the lower-level tenant's platform based on the model identifier. After finding the service model in the lower-level tenant's platform based on the model identifier, it will not continue to search for service models in the lower-level tenant's platform based on the model identifier. In this way, the updated first service model will be used to update the second service model corresponding to the model identifier deployed in the lower-level tenant's platform, instead of using the updated first service model to update the first service model deployed in the lower-level tenant's platform. As a result, it is impossible to update the first service model deployed in the lower-level tenant's platform according to the scheduling of the upper-level tenant.

[0151] In this application, after a lower-level tenant deploys a second service model on its platform, the upper-level tenant can promptly determine whether the second model identifier of the newly deployed second service model is the same as the first model identifier of at least one first service model deployed on the upper-level tenant's platform. If the second model identifier of the newly deployed second service model is the same as the first model identifier of at least one first service model deployed on the upper-level tenant's platform, the upper-level tenant can promptly notify the upper-level tenant that the second model identifier of the newly deployed second service model is the same as the first model identifier of at least one first service model deployed on the upper-level tenant's platform. The identifiers are identical to ensure timely intervention (e.g., intervention by staff of the upper-level tenant or automatic intervention by the upper-level tenant's platform). For example, it can promptly eliminate situations where the second model identifier of a newly deployed second service model in the lower-level tenant's platform is the same as the first model identifier of at least one first service model deployed in the upper-level tenant's platform. In other words, it can ensure that the second model identifier of a newly deployed second service model in the lower-level tenant's platform is different from the first model identifier of each first service model deployed in the upper-level tenant's platform. This can prevent situations where it is impossible to update the first service model deployed in the lower-level tenant's platform according to the upper-level tenant's scheduling.

[0152] It should be noted that, for the sake of simplicity, the method embodiments are all described as a series of actions. However, those skilled in the art should understand that this application is not limited to the described order of actions, because according to this application, some steps can be performed in other orders or simultaneously. Secondly, those skilled in the art should also understand that the embodiments described in the specification are all optional embodiments, and the actions involved are not necessarily required by this application.

[0153] Reference Figure 4 This diagram illustrates a structural block diagram of a data processing apparatus according to this application, applied to the platform of an upper-level tenant, in which a first service model is deployed. The apparatus includes: a first receiving module 11, configured to receive an update message sent by the platform of a lower-level tenant cascaded by the upper-level tenant, the update message being obtained by the lower-level tenant's platform when a second service model is newly deployed in the lower-level tenant's platform, the update message including at least a second model identifier of the second service model; a first obtaining module 12, configured to obtain the second model identifier of the second service model newly deployed in the lower-level tenant's platform according to the update message, and to obtain the first model identifiers of each first service model deployed in the upper-level tenant's platform; and a first output module 13, configured to output the same prompt information when the second model identifier is the same as at least one first model identifier, the same prompt information indicating that the second model identifier is the same as at least one first model identifier.

[0154] In an optional implementation, the apparatus further includes: a first sending module, configured to send a modification instruction to a lower-level tenant's platform, the modification instruction indicating that a second model identifier of a second service model deployed in the lower-level tenant is modified, so that the lower-level tenant's platform receives the modification instruction and modifies the second model identifier of the second service model deployed in the lower-level tenant according to the modification instruction, so that the modified second model identifier is different from each first model identifier.

[0155] Reference Figure 5This diagram illustrates a structural block diagram of a data processing apparatus according to this application, applied to a lower-level tenant's platform, where a first service model is deployed in the platform of an upper-level tenant cascaded by the lower-level tenant. The apparatus includes: a second acquisition module 21, configured to acquire an update message when a second service model is newly deployed in the lower-level tenant's platform, the update message including at least a second model identifier of the second service model; and a second sending module 22, configured to send the update message to the upper-level tenant's platform so that the upper-level tenant's platform receives the update message, acquire the second model identifier of the newly deployed second service model in the lower-level tenant's platform based on the update message, and acquire the first model identifiers of each first service model deployed in the upper-level tenant's platform, and output identical prompt information when the second model identifier is the same as at least one first model identifier, the identical prompt information indicating that the second model identifier is the same as at least one first model identifier.

[0156] In an optional implementation, the apparatus further includes: a second receiving module, configured to receive a modification instruction sent by the platform of the upper-level tenant, the modification instruction indicating the modification of the second model identifier of the second service model deployed in the lower-level tenant; and a modification module, configured to modify the second model identifier of the second service model deployed in the lower-level tenant according to the modification instruction, so that the modified second model identifier is different from each of the first model identifiers.

[0157] for Figure 4 and Figure 5 In the illustrated embodiment, after a lower-level tenant deploys a second service model on its platform, the upper-level tenant can promptly determine whether the second model identifier of the newly deployed second service model is the same as the first model identifier of at least one first service model deployed on the upper-level tenant's platform. If the second model identifier of the newly deployed second service model is the same as the first model identifier of at least one first service model deployed on the upper-level tenant's platform, the upper-level tenant can promptly notify the upper-level tenant that the second model identifier of the newly deployed second service model is the same as the first model identifier of at least one first service model deployed on the upper-level tenant's platform. The identifiers are identical to ensure timely intervention (e.g., intervention by staff of the upper-level tenant or automatic intervention by the upper-level tenant's platform). For example, it can promptly eliminate situations where the second model identifier of a newly deployed second service model in the lower-level tenant's platform is the same as the first model identifier of at least one first service model deployed in the upper-level tenant's platform. In other words, it can ensure that the second model identifier of a newly deployed second service model in the lower-level tenant's platform is different from the first model identifier of each first service model deployed in the upper-level tenant's platform. This can prevent situations where it is impossible to update the first service model deployed in the lower-level tenant's platform according to the upper-level tenant's scheduling.

[0158] Reference Figure 6 This diagram illustrates a structural block diagram of a data processing apparatus according to this application, applied to the platform of an upper-level tenant. The upper-level tenant's platform deploys a first service model, and the platforms of lower-level tenants cascaded by the upper-level tenant deploy a second service model. The second service model is the same as the first service model, or the second service model is an updated version of the first service model. The apparatus includes: a third acquisition module 31, used to acquire a first update request, the first update request carrying a first model identifier of the first service model and a first basic service framework for a first field that needs to be updated in the first service model; and a first search module 32, used to search for the first model identifier in the upper-level tenant's platform. The system includes a first service model, a first hot update module 33 for hot updating the first basic service framework within the first service model to achieve hot updating of the first field of the first service model, resulting in a new first service model, and a synchronization module 34 for synchronizing the new first service model and the first model identifier to at least some of the lower-level tenants' platforms cascaded to the upper-level tenant, so that the lower-level tenants' platforms can find the second service model deployed in the lower-level tenants' platforms based on the first model identifier, wherein the model identifier of the second service model is the first model identifier, and the new first service model is used to hot update the second service model deployed in the lower-level tenants' platforms to obtain a new second service model.

[0159] In one optional implementation, the third acquisition module includes: a first acquisition unit, configured to acquire a first update request submitted by an upper-level tenant to the platform of the upper-level tenant; or, a receiving unit, configured to receive a first update request uploaded by a lower-level tenant's platform, wherein the first update request is submitted by the lower-level tenant to the platform of the lower-level tenant.

[0160] In one optional implementation, the synchronization module includes: a first synchronization unit, configured to filter, among multiple lower-level tenants cascaded by the upper-level tenant, lower-level tenants that subscribe to the first service model; and synchronize the new first service model and the first model identifier to the platform of the lower-level tenant that subscribes to the first service model; or, a second synchronization unit, configured to synchronize the new first service model and the first model identifier to the platform of the target lower-level tenant when the first update request is submitted by the platform of the target lower-level tenant to the platform of the upper-level tenant, wherein the target lower-level tenant includes one of the multiple lower-level tenants cascaded by the upper-level tenant.

[0161] In an optional implementation, the apparatus further includes: a third receiving module, configured to receive a first notification message, the first notification message indicating that a second service model deployed in the lower-level tenant's platform has been hot-updated using a new first service model and a new second service model has been obtained; the first notification message is generated and sent to the upper-level tenant's platform after the lower-level tenant's platform hot-updates the second service model deployed in the lower-level tenant's platform using the new first service model and obtains a new second service model; and a second output module, configured to output the first notification message.

[0162] Reference Figure 7 This diagram illustrates a structural block diagram of a data processing apparatus according to this application, applied to a lower-level tenant's platform. The lower-level tenant's platform deploys a second service model, and the platform of the upper-level tenant cascaded by the lower-level tenant deploys a first service model. The second service model is the same as the first service model, or the second service model is an updated version of the first service model. The apparatus includes: a fourth receiving module 41, used to receive a new first service model and a first model identifier sent by the platform of the upper-level tenant cascaded by the lower-level tenant; the new first service model and the first model identifier are obtained after the upper-level tenant's platform receives a first update request, and the first service model deployed in the upper-level tenant's platform is located based on the first model identifier. The model is used to hot-update the first basic service framework in the first service model to achieve hot-update of the first field of the first service model, and then send the new first service model to the platform of the lower-level tenant. The first update request carries the first model identifier of the first service model and the first basic service framework of the first field that needs to be updated in the first service model. The second lookup module 42 is used to find the second service model deployed in the platform of the lower-level tenant according to the first model identifier, wherein the model identifier of the second service model is the first model identifier. The second hot update module 43 is used to hot-update the second service model deployed in the platform of the lower-level tenant using the new first service model to obtain the new second service model.

[0163] In an optional implementation, the apparatus further includes: a fourth acquisition module for acquiring a first update request submitted by a lower-level tenant to the platform of the lower-level tenant; and an upload module for uploading the first update request to the platform of the upper-level tenant.

[0164] In an optional implementation, the apparatus further includes: a generation module for generating a first notification message, the first notification message indicating that a second service model deployed in the lower-level tenant's platform has been hot-updated using a new first service model and a new second service model has been obtained; and a third sending module for sending the first notification message to the upper-level tenant's platform, so that the upper-level tenant's platform outputs the first notification message.

[0165] In an optional implementation, the generation module includes: a second acquisition unit, configured to acquire old fields already integrated in the second service model before the second service model is hot-updated in the platform of the lower-level tenant using the new first service model; acquire a first concatenation relationship between the old fields; a third acquisition unit, configured to acquire a second concatenation relationship between the old fields and the first field; a generation unit, configured to generate a first schematic diagram, the first schematic diagram indicating the first concatenation relationship, indicating the second concatenation relationship, and marking the first field as a field for hot-updating; and a fourth acquisition unit, configured to acquire a first notification message based on the first schematic diagram.

[0166] for Figure 6 and Figure 7 In the illustrated embodiment, when an upper-level tenant updates the first service model deployed on its platform, unified management of the service model can be achieved. For example, the upper-level tenant may not modify the model identifier of the first service model deployed on its platform, and the lower-level tenant may not actively update the first service model deployed on its platform. Thus, the lower-level tenant's platform passively updates the first service model deployed on its platform according to the scheduling of the upper-level tenant's platform. For instance, the lower-level tenant can receive a new first service model synchronized by the upper-level tenant and use this new first service model to hot-update the corresponding second service model on its platform, ensuring that the model identifiers of the new first service model deployed on the upper-level tenant's platform and the new second service model deployed on the lower-level tenant's platform are always identical. This avoids situations where the second service model deployed on the lower-level tenant's platform cannot be updated according to the upper-level tenant's scheduling.

[0167] This application also provides a non-volatile readable storage medium storing one or more modules (programs). When these modules are applied to a device, they enable the device to execute the instructions for the method steps in this application.

[0168] This application provides one or more machine-readable media storing instructions that, when executed by one or more processors, cause an electronic device to perform one or more methods as described in the above embodiments. In this application, the electronic device includes a server, a gateway, sub-devices, etc., and the sub-devices are devices such as Internet of Things (IoT) devices.

[0169] Embodiments of this disclosure can be implemented as an apparatus with any suitable hardware, firmware, software, or any combination thereof, configured as desired. This apparatus may include electronic devices such as servers (clusters) and terminal devices such as IoT devices.

[0170] Figure 8 An exemplary apparatus 1300 is schematically shown that can be used to implement the various embodiments of this application.

[0171] In one embodiment, Figure 8 An exemplary device 1300 is shown, which includes one or more processors 1302, a control module (chipset) 1304 coupled to at least one of the processors 1302, a memory 1306 coupled to the control module 1304, a non-volatile memory (NVM) / storage device 1308 coupled to the control module 1304, one or more input / output devices 1310 coupled to the control module 1304, and a network interface 1312 coupled to the control module 1304.

[0172] Processor 1302 may include one or more single-core or multi-core processors, and processor 1302 may include any combination of general-purpose processors or special-purpose processors (e.g., graphics processors, application processors, baseband processors, etc.). In some embodiments, device 1300 can function as a server device such as a gateway in the embodiments of this application.

[0173] In some embodiments, apparatus 1300 may include one or more computer-readable media (e.g., memory 1306 or NVM / storage device 1308) having instructions 1314 and one or more processors 1302 that are combined with the one or more computer-readable media and configured to execute the instructions 1314 to implement the module and thus perform the actions in this disclosure.

[0174] In one embodiment, the control module 1304 may include any suitable interface controller to provide any suitable interface to at least one of the processors 1302 and / or any suitable device or component communicating with the control module 1304.

[0175] The control module 1304 may include a memory controller module to provide an interface to the memory 1306. The memory controller module may be a hardware module, a software module, and / or a firmware module.

[0176] Memory 1306 may be used, for example, to load and store data and / or instructions 1314 for device 1300. In one embodiment, memory 1306 may include any suitable volatile memory, such as suitable DRAM. In some embodiments, memory 1306 may include double data rate quad synchronous dynamic random access memory (DDR4 SDRAM).

[0177] In one embodiment, the control module 1304 may include one or more input / output controllers to provide interfaces to the NVM / storage device 1308 and (one or more) input / output devices 1310.

[0178] For example, NVM / storage device 1308 may be used to store data and / or instructions 1314. NVM / storage device 1308 may include any suitable non-volatile memory (e.g., flash memory) and / or may include any suitable (one or more) non-volatile storage devices (e.g., one or more hard disk drives (HDDs), one or more optical disc drives (CDs), and / or one or more digital universal optical disc (DVD) drives).

[0179] NVM / storage device 1308 may include storage resources that are physically part of a device on which device 1300 is mounted, or that can be accessed by the device without needing to be part of the device. For example, NVM / storage device 1308 may be accessed via a network via one or more input / output devices 1310.

[0180] One or more input / output devices 1310 may provide an interface for device 1300 to communicate with any other suitable device. Input / output devices 1310 may include communication components, pinyin components, sensor components, etc. Network interface 1312 may provide an interface for device 1300 to communicate via one or more networks. Device 1300 may wirelessly communicate with one or more components of a wireless network according to any of one or more wireless network standards and / or protocols, such as accessing wireless networks based on communication standards, such as WiFi, 2G, 3G, 4G, 5G, etc., or combinations thereof.

[0181] In one embodiment, at least one of the processors 1302 may be logically packaged with one or more controllers (e.g., memory controller modules) of the control module 1304. In one embodiment, at least one of the processors 1302 may be logically packaged with one or more controllers of the control module 1304 to form a system-in-package (SiP). In one embodiment, at least one of the processors 1302 may be integrated with the logic of one or more controllers of the control module 1304 on the same die. In one embodiment, at least one of the processors 1302 may be integrated with the logic of one or more controllers of the control module 1304 on the same die to form a system-on-a-chip (SoC).

[0182] In various embodiments, device 1300 may be, but is not limited to, a server, desktop computing device, or mobile computing device (e.g., laptop computing device, handheld computing device, tablet computer, netbook, etc.). In various embodiments, device 1300 may have more or fewer components and / or different architectures. For example, in some embodiments, device 1300 includes one or more cameras, a keyboard, a liquid crystal display (LCD) screen (including a touchscreen display), a non-volatile memory port, multiple antennas, a graphics chip, an application-specific integrated circuit (ASIC), and a speaker.

[0183] This application provides an electronic device, including: one or more processors; and one or more machine-readable media having instructions stored thereon, which, when executed by the one or more processors, cause the electronic device to perform one or more methods as described in this application.

[0184] As the device embodiment is basically similar to the method embodiment, the description is relatively simple, and relevant parts can be found in the description of the method embodiment.

[0185] The various embodiments in this specification are described in a progressive manner, with each embodiment focusing on the differences from other embodiments. The same or similar parts between the various embodiments can be referred to each other.

[0186] This application describes embodiments with reference to flowchart illustrations and / or block diagrams of methods, terminal devices (systems), and computer program products according to embodiments of this application. It should be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable information processing terminal device to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable information processing terminal device, generate instructions for implementing the flowchart illustrations. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0187] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable information processing terminal device to operate in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0188] These computer program instructions can also be loaded onto a computer or other programmable information processing terminal equipment, causing a series of operational steps to be performed on the computer or other programmable terminal equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable terminal equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0189] Although preferred embodiments of the present application have been described, those skilled in the art, upon learning the basic inventive concept, can make other changes and modifications to these embodiments. Therefore, the appended claims are intended to be interpreted as including both the preferred embodiments and all changes and modifications falling within the scope of the embodiments of the present application.

[0190] Finally, it should be noted that in this document, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or terminal device that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or terminal device. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or terminal device that includes the element.

[0191] The data processing method and apparatus provided in this application have been described in detail above. Specific examples have been used to illustrate the principles and implementation methods of this application. The description of the above embodiments is only for the purpose of helping to understand the method and core ideas of this application. At the same time, for those skilled in the art, there will be changes in the specific implementation methods and application scope based on the ideas of this application. Therefore, the content of this specification should not be construed as a limitation of this application.

Claims

1. A data processing method, characterized in that, The method is applied to the platform of the upstream tenant, in which a first service model is deployed; the method includes: Receive update messages sent by the platform of the lower-level tenant cascaded by the upper-level tenant. The update messages are obtained by the lower-level tenant's platform when a second service model is newly deployed in the lower-level tenant's platform. The update messages include at least the second model identifier of the second service model. Based on the update message, obtain the second model identifier of the second service model newly deployed in the platform of the lower-level tenant, and obtain the first model identifier of each first service model deployed in the platform of the upper-level tenant. If the second model identifier is the same as at least one first model identifier, the platform of the upper-level tenant outputs the same prompt message, which is used to indicate that the second model identifier is the same as at least one first model identifier.

2. The method according to claim 1, characterized in that, The method further includes: A modification instruction is sent to the platform of the lower-level tenant. The modification instruction is used to instruct the modification of the second model identifier of the second service model deployed in the lower-level tenant, so that the platform of the lower-level tenant receives the modification instruction and modifies the second model identifier of the second service model deployed in the lower-level tenant according to the modification instruction, so that the modified second model identifier is different from each first model identifier.

3. A data processing method, characterized in that, The method, which is applied to a platform for lower-level tenants, wherein a first service model is deployed in the platform of the upper-level tenants cascaded by the lower-level tenants, includes: When a second service model is newly deployed in the platform of a lower-level tenant, obtain an update message, which includes at least the second model identifier of the second service model; Send an update message to the platform of the upper-level tenant so that the platform of the upper-level tenant receives the update message, obtain the second model identifier of the second service model newly deployed in the platform of the lower-level tenant according to the update message, and obtain the first model identifier of each first service model deployed in the platform of the upper-level tenant. If the second model identifier is the same as at least one first model identifier, output the same prompt message, which is used to indicate that the second model identifier is the same as at least one first model identifier.

4. The method according to claim 3, characterized in that, The method further includes: Receive modification instructions sent by the platform of the upper-level tenant. The modification instructions are used to indicate the modification of the second model identifier of the second service model deployed in the lower-level tenant. The second service model identifier deployed in the lower-level tenant is modified according to the modification instruction, so that the modified second model identifier is different from each first model identifier.

5. A data processing method, characterized in that, The method is applied to the platform of an upstream tenant, where a first service model is deployed, and the platforms of downstream tenants cascaded by the upstream tenant deploy a second service model, wherein the second service model is the same as the first service model or is obtained by updating the first service model; the method includes: Obtain the first update request. The first update request carries the first model identifier of the first service model and the first basic service framework of the first field that needs to be updated in the first service model. Based on the first model identifier, locate the first service model deployed in the platform of the upper-level tenant; In the first service model, the first basic service framework is hot-updated to achieve hot-updating of the first field of the first service model and obtain a new first service model; The platform synchronizes a new first service model and a first model identifier with at least some of the lower-level tenants that are cascaded to the upper-level tenant, so that the lower-level tenant's platform can find the second service model deployed in the lower-level tenant's platform based on the first model identifier, wherein the model identifier of the second service model is the first model identifier, and uses the new first service model to hot update the second service model deployed in the lower-level tenant's platform to obtain the new second service model.

6. The method according to claim 5, characterized in that, The process of obtaining the first update request includes: Get the first update request submitted by the parent tenant to the parent tenant's platform; or, Receive the first update request uploaded by the lower-level tenant's platform. The first update request is submitted by the lower-level tenant to the lower-level tenant's platform.

7. The method according to claim 5, characterized in that, The platform synchronization of the new first service model and the first model identifier for at least some of the lower-level tenants cascaded to the upper-level tenant includes: Among the multiple lower-level tenants cascaded by the upper-level tenant, select the lower-level tenants that subscribe to the first service model; synchronize the new first service model and the first model identifier to the platform of the lower-level tenants that subscribe to the first service model; or, In the case where the first update request is submitted by the target lower-level tenant's platform to the upper-level tenant's platform, the new first service model and the first model identifier are synchronized to the target lower-level tenant's platform. The target lower-level tenant includes one of the multiple lower-level tenants cascaded by the upper-level tenant.

8. The method according to claim 5, characterized in that, The method further includes: Receive a first notification message, which indicates that the second service model deployed in the lower-level tenant's platform has been hot-updated using the new first service model and a new second service model has been obtained; the first notification message is generated and sent to the upper-level tenant's platform after the lower-level tenant's platform hot-updates the second service model deployed in the lower-level tenant's platform using the new first service model and obtains a new second service model. Output the first notification message.

9. A data processing method, characterized in that, The method is applied to a platform for lower-level tenants, where a second service model is deployed, and a first service model is deployed in the platform of the upper-level tenant cascaded by the lower-level tenant. The second service model is the same as the first service model, or the second service model is an updated version of the first service model. The system receives a new first service model and a first model identifier from the platform of the upper-level tenant cascaded by the lower-level tenant. The new first service model and first model identifier are obtained after the upper-level tenant's platform receives the first update request. Based on the first model identifier, the system finds the first service model deployed in the upper-level tenant's platform, hot-updates the first basic service framework in the first service model to achieve hot-update of the first field of the first service model, and then sends the new first service model to the lower-level tenant's platform. The first update request carries the first model identifier of the first service model and the first basic service framework of the first field that needs to be updated in the first service model. Based on the first model identifier, locate the second service model deployed in the platform of the lower-level tenant, wherein the model identifier of the second service model is the first model identifier; The new second service model is obtained by hot-updating the second service model deployed in the platform of the lower-level tenant using the new first service model.

10. The method according to claim 9, characterized in that, Before receiving the new first service model and first model identifier sent by the platform of the cascaded lower-level tenant, the process also includes: Get the first update request submitted by the lower-level tenant to the lower-level tenant's platform; Upload the first update request to the platform of the upstream tenant.

11. The method according to claim 9, characterized in that, The process of hot-updating the second service model deployed in the lower-level tenant's platform using the new first service model, after obtaining the new second service model, further includes: Generate a first notification message, which indicates that the second service model deployed in the lower-level tenant's platform has been hot-updated using the new first service model and the new second service model has been obtained; Send the first notification message to the platform of the upper-level tenant so that the platform of the upper-level tenant outputs the first notification message.

12. The method according to claim 11, characterized in that, The generation of the first notification message includes: Retrieve the old fields that were already integrated in the second service model before the second service model was deployed in the platform of the lower-level tenant using the new first service model; retrieve the first cascading relationship between the old fields; Obtain the second concatenation relationship between the old field and the first field; Generate a first schematic diagram, which is used to indicate the first cascade relationship, the second cascade relationship, and marks the first field as a field that is hot-updated; The first notification message is obtained according to the first schematic diagram.

13. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, The steps of the method as claimed in any one of claims 1 to 12 are implemented when the processor executes the program.

14. A computer-readable storage medium, characterized in that, A computer-readable storage medium stores a computer program that, when executed by a processor, implements the steps of the method as claimed in any one of claims 1 to 12.

Images