CN116737235A - Application and platform bridging method, device and readable storage medium - Google Patents
Application and platform bridging method, device and readable storage medium Download PDFInfo
- Publication number
- CN116737235A CN116737235A CN202310764993.9A CN202310764993A CN116737235A CN 116737235 A CN116737235 A CN 116737235A CN 202310764993 A CN202310764993 A CN 202310764993A CN 116737235 A CN116737235 A CN 116737235A
- Authority
- CN
- China
- Prior art keywords
- platform
- service
- application
- field
- service request
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 51
- 238000013499 data model Methods 0.000 claims abstract description 62
- 238000012545 processing Methods 0.000 claims abstract description 26
- 230000006870 function Effects 0.000 claims description 40
- 238000013507 mapping Methods 0.000 claims description 38
- 230000006978 adaptation Effects 0.000 claims description 15
- 230000008571 general function Effects 0.000 claims description 8
- 239000000284 extract Substances 0.000 claims description 6
- 238000010606 normalization Methods 0.000 claims description 4
- 238000013523 data management Methods 0.000 abstract description 13
- 238000011161 development Methods 0.000 abstract description 11
- 230000010354 integration Effects 0.000 abstract description 2
- 230000008520 organization Effects 0.000 description 13
- 238000010586 diagram Methods 0.000 description 12
- 238000004590 computer program Methods 0.000 description 7
- 238000005516 engineering process Methods 0.000 description 7
- 238000004891 communication Methods 0.000 description 6
- 230000000694 effects Effects 0.000 description 6
- 230000008569 process Effects 0.000 description 5
- 230000003993 interaction Effects 0.000 description 4
- 238000012986 modification Methods 0.000 description 4
- 230000004048 modification Effects 0.000 description 4
- 230000005477 standard model Effects 0.000 description 4
- 230000008901 benefit Effects 0.000 description 3
- 230000004075 alteration Effects 0.000 description 2
- 210000001503 joint Anatomy 0.000 description 2
- 238000012423 maintenance Methods 0.000 description 2
- 238000011144 upstream manufacturing Methods 0.000 description 2
- 238000004458 analytical method Methods 0.000 description 1
- 238000006243 chemical reaction Methods 0.000 description 1
- 239000012141 concentrate Substances 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 238000013501 data transformation Methods 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000008447 perception Effects 0.000 description 1
- 230000003252 repetitive effect Effects 0.000 description 1
- 230000004044 response Effects 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/76—Adapting program code to run in a different environment; Porting
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
- G06F9/5005—Allocation of resources, e.g. of the central processing unit [CPU] to service a request
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The application discloses a bridging method, equipment and readable storage medium of an application and a platform, wherein the method comprises the following steps: when the service request sent by the application terminal is received, forwarding the service request to a target platform corresponding to a tenant identifier of the service request; receiving the service data responded by the target platform aiming at the service request; determining a standard data model corresponding to the service data, and carrying out standardization processing on the service data based on the standard data model; and forwarding the standardized field to be output to the application end. The method solves the technical problems that the application and the SaaS platforms in the related art need to be mutually matched one by one, so that the data management is difficult along with the increase of the number of the expansion platforms, realizes the integration of the data difference between different platforms, improves the data management efficiency, and reduces the development difficulty of the platform expansion.
Description
Technical Field
The present application relates to the field of data interaction, and in particular, to a bridging method and apparatus for an application and a platform, and a readable storage medium.
Background
At present, the platform SaaS (Software as a Service ) gradually becomes a trend, and for enterprises, software services provided by other SaaS platforms are generally used to directly output corresponding functions to enterprise users, so that repeated wheel making is avoided, and the enterprises can concentrate on service promotion of the application.
In order for an enterprise to use software services provided by a third party's SaaS platform, each application software needs to modify the data output format for a different SaaS platform, and each SaaS platform also needs to access user data of a different application software of the enterprise. In this case, if there are multiple applications desiring to provide services from multiple platforms, the cost of developing the enterprise and SaaS platforms is high macroscopically, and many of them are repetitive.
In the interaction process, the SaaS platform and the application software are in a many-to-many relationship, the application software needs to process the data difference of different platforms, and the difficulty of integrating the data is increased along with the expansion of the number of new platforms.
Disclosure of Invention
The embodiment of the application solves the technical problems that the application and the SaaS platform are required to be mutually matched one by one before the application and the SaaS platform in the related technology, so that the data management is difficult along with the increase of the number of the expansion platforms, realizes the integration of the data difference between different platforms, improves the data management efficiency and reduces the development difficulty of the platform expansion.
The embodiment of the application provides a bridging method of an application and a platform, which is applied to a bridging module and is arranged between a SaaS platform end and an application end, and is used for forwarding a service request initiated by the application end to the platform end and forwarding service data responded by the platform end to the application end, wherein the bridging method of the application and the platform comprises the following steps:
when the service request sent by the application terminal is received, forwarding the service request to a target platform corresponding to a tenant identifier of the service request;
receiving the service data responded by the target platform aiming at the service request;
determining a standard data model corresponding to the service data, and carrying out standardization processing on the service data based on the standard data model;
and forwarding the standardized field to be output to the application end.
Optionally, when the service request sent by the application end is received, a target platform corresponding to a tenant identifier of the service request is identified, and the step of forwarding the service request includes:
the controller layer distributes the service request to a platform service interface corresponding to the tenant identifier according to the tenant identifier corresponding to the service request;
After receiving the service request, the platform service interface calls a service interface corresponding to a service identifier of the service request;
and the service interface sends the service request to the target platform.
Optionally, before the step of distributing the service request to the platform service interface corresponding to the tenant identifier by the controller layer according to the tenant identifier corresponding to the service request, the method further includes:
acquiring registration information of the application terminal according to the service request;
and when the registration information is unregistered, returning a prompt window without request permission.
Optionally, the step of determining a standard data model corresponding to the service data and performing standardization processing on the service data based on the standard data model includes:
the service layer determines the standard data model according to the service identification of the service data;
determining standard fields and specific fields in the service data according to the standard data model;
based on a standard field mapping rule of the target platform, taking a mapping value of the standard field as the field to be output;
and sending the field to be output to a bridging layer.
Optionally, before the step of sending the field to be output to the bridging layer, the method further includes:
when the special field has a dependency relationship with the application end, determining the privacy attribute of the special field;
and when the special field is not a sensitive field, determining the special field as the field to be output.
Optionally, before the step of determining the standard data model corresponding to the service data and performing the normalization processing on the service data based on the standard data model, the method further includes:
the adaptation layer acquires a function packet corresponding to the platform to be docked, and sends the function packet to the service layer;
after receiving the function packages, the service layer extracts the same function packages in the platforms to be docked as universal function packages;
and establishing the standard data model according to the business relation and the general function package.
Optionally, after the step of forwarding the field to be output after the normalization processing to the application end, the method further includes:
the service layer establishes standard field mapping rules of the platform to be docked based on the standard data model;
extracting the functional package of the platform to be docked to generate a corresponding service interface;
And generating the tenant identification of the platform to be docked according to a preset encryption rule.
Optionally, the step of establishing, by the service layer, a standard field mapping rule of the platform to be docked based on the standard data model includes:
acquiring a first field in the standard data model;
determining that a field with the same semantic meaning as the first field in the platform to be docked is a standard field;
taking the field with the semantic meaning different from that of the first field as a specific field;
the standard field mapping rule between the standard field and the first field is established.
In addition, the application also provides an application and platform bridging device, which comprises a memory, a processor and an application and platform bridging program stored on the memory and capable of running on the processor, wherein the processor realizes the steps of the application and platform bridging method when executing the application and platform bridging program.
In addition, the application also provides a computer readable storage medium, wherein the computer readable storage medium stores an application and platform bridging program, and the application and platform bridging program realizes the steps of the application and platform bridging method when being executed by a processor.
One or more technical solutions provided in the embodiments of the present application at least have the following technical effects or advantages:
1. forwarding the service request by adopting a target platform corresponding to a tenant identifier of the service request when the service request sent by the application terminal is received; receiving the service data responded by the target platform aiming at the service request; determining a standard data model corresponding to the service data, and carrying out standardization processing on the service data based on the standard data model; the fields to be output after standardized processing are forwarded to the application end, so that the technical problems that the number of the expansion platforms is increased and the data management is difficult due to the fact that the application and the SaaS platforms in the related technology need to be mutually matched one by one are effectively solved, the data difference between different platforms is integrated, the data management efficiency is improved, and the platform expansion development difficulty is reduced are further achieved.
2. Because the service layer is adopted and based on the standard data model, standard field mapping rules of the platform to be docked are established; extracting the functional package of the platform to be docked to generate a corresponding service interface; the tenant identification of the platform to be docked is generated according to the preset encryption rule, so that the technical problem that data transformation and data access are required for each application when new platform service is expanded in the related technology is effectively solved, and the technical effects that when the new platform service is expanded, only the data field output mode of the platform is required to be transformed once, and development and maintenance costs are reduced are achieved.
Drawings
FIG. 1 is a flowchart of a bridging method of an application and platform according to an embodiment of the present application;
FIG. 2 is a schematic diagram of a connection relationship between a bridging module and an application end, and between the bridging module and a platform end in an embodiment of a bridging method for an application and a platform of the present application;
FIG. 3 is a schematic diagram of a human model in a third embodiment of a bridging method of an application and platform of the present application;
FIG. 4 is a schematic diagram of a mechanism model in a third embodiment of a bridging method for an application and platform of the present application;
FIG. 5 is a schematic diagram of an enterprise model in a third embodiment of a bridging method for an application and platform of the present application;
FIG. 6 is a flow chart of responding to a service request in a third embodiment of a bridging method of an application and platform of the present application;
fig. 7 is a schematic diagram of a hardware structure related to an embodiment of a bridging device of an application and a platform according to the present application.
Detailed Description
In the related technology, the application and the SaaS platform are in a many-to-many relationship, so that the application end needs to be developed and improved for each platform, the platform end also needs to be improved for data output for each application end, the development and maintenance difficulty is high when a new platform is expanded, and the data management is difficult. The embodiment of the application adopts the main technical scheme that: adapting tenant identifications to each platform end, and forwarding service requests to corresponding target platforms according to tenant identifications when service requests of application ends are received; and when receiving the service data responded by the platform end, carrying out standardized processing on the service data according to the standardized model to obtain a field to be output, and forwarding the field to be output to the application end. Therefore, the technical effects of integrating the data difference between different platforms, improving the data management efficiency and reducing the development difficulty of platform expansion are achieved. Meanwhile, the difference of an upstream SaaS platform is shielded, and the universal capability is abstracted; the SaaS is internally matched with an upstream platform, and standardized data is output to downstream applications; when a new SaaS platform is accessed in the future, the application end does not need to be modified, and the platform can be accessed without perception. The bridging shields the difference between different SaaS platforms, simplifies the process of the butt joint of the application end and the SaaS platforms, and can realize the noninductive expansion of more SaaS platforms after the application end and the SaaS platforms are in one-time butt joint through the bridging module, thereby greatly reducing the development cost.
In order to better understand the above technical solution, exemplary embodiments of the present application will be described in more detail below with reference to the accompanying drawings. While exemplary embodiments of the present application are shown in the drawings, it should be understood that the present application may be embodied in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the application to those skilled in the art.
Example 1
The embodiment of the application discloses a bridging method of an application and a platform, and referring to fig. 1, the bridging method of the application and the platform comprises the following steps:
step S110, when receiving the service request sent by the application end, forwarding the service request to a target platform corresponding to a tenant identifier of the service request;
in this embodiment, a SaaS channel, that is, a bridging module, is disposed between a SaaS platform end and an application end, and is configured to forward a service request initiated by the application end to the platform end, and forward service data responded by the platform end to the application end. And determining a target platform to which the service request needs to be distributed according to the tenant identification.
As an optional implementation manner, when the bridging module receives a service request sent by an application end, a corresponding ServiceProvider interface is determined according to a tenant identifier of the service request, and the service request is forwarded to a corresponding target platform through the interface.
Step S120, receiving the service data responded by the target platform aiming at the service request;
in this embodiment, after receiving the service request, the target platform obtains corresponding service data for the service request, and returns the service data to the application end through the bridging module.
As an alternative implementation manner, the adaptation layer receives the service data responded by the target platform for the service request, and sends the response data to the service layer.
Step S130, determining a standard data model corresponding to the service data, and carrying out standardization processing on the service data based on the standard data model;
in this embodiment, the standard data model is a general capability set of each platform end, for example, divided into a personnel standard model, an organization standard model and an enterprise standard model according to service attributes, wherein a standard output form of a field related to each service is specified.
For the field with the same meaning, the field names designed in different platforms may be inconsistent, for example, for the field name of the enterprise, the field name in the first platform is enterprise identification, and the field name in the second platform is enterprise id, so that according to the fields commonly used in each platform, a standard data model is suggested, different field names are output to the application end in a unified standard field name, and the adaptation pressure of the application end is reduced.
As an optional implementation manner, after receiving the service data, the service layer determines a standard data model according to the service identifier of the service data, determines a standard field mapping rule corresponding to the target platform according to the standard data model, and performs standardization processing on fields in the service data according to the standard field mapping rule.
And step S140, forwarding the standardized field to be output to the application end.
In this embodiment, the service layer performs standardization processing on the service data to obtain a field to be output, and sends the field to be output to the application end through the bridging layer.
As an optional implementation manner, the service layer sends the field to be output obtained after the standardization processing to the bridging layer, and after receiving the field to be output, the bridging layer sends the field to be output to an application end from which the service request is sent according to the service request corresponding to the service data.
In this embodiment, the bridge module may be divided into an adaptation layer, a service layer, and a bridge layer, referring to fig. 2, fig. 2 is a connection relationship between the bridge module and an application end, and a platform end, where SaaS is the bridge module. An adaptation Layer (adaptation Layer) acquires a function packet corresponding to the SaaS platform and transmits the function packet to a service Layer; a service layer (Service Provider Layer) for integrating the received function packages and abstracting out the general function packages corresponding to the function packages; customizing a standard data model based on the generic function package; when receiving a data stream issued by the SaaS platform, standardizing the data stream according to the data output model, and outputting the standardized data stream to a bridging layer; the Bridge Layer (Bridge Layer) receives the standardized data stream issued by the service Layer and sends the standardized data stream to a corresponding application end according to a request identifier corresponding to the standardized data stream; and receiving a data request sent by an application terminal, and forwarding the data request to a corresponding SaaS platform.
The technical scheme provided by the embodiment of the application at least has the following technical effects or advantages:
forwarding the service request by adopting a target platform corresponding to a tenant identifier of the service request when the service request sent by the application terminal is received; receiving the service data responded by the target platform aiming at the service request; determining a standard data model corresponding to the service data, and carrying out standardization processing on the service data based on the standard data model; the fields to be output after standardized processing are forwarded to the application end, so that the technical problems that the number of the expansion platforms is increased and the data management is difficult due to the fact that the fields to be output are required to be mutually matched one by one before application and saas platform application in the related technology are effectively solved, the data difference between different platforms is integrated, the data management efficiency is improved, and the platform expansion development difficulty is reduced are effectively solved.
Example two
Based on the first embodiment, a second embodiment of the present application provides a bridging method between an application and a platform, and step S110 includes:
step S210, the controller layer distributes the service request to a platform service interface corresponding to the tenant identifier according to the tenant identifier corresponding to the service request;
in this embodiment, the bridging layer receives and forwards the service request sent by the application end, where the bridging layer includes, but is not limited to, a controller layer, a platform service interface, and a service interface.
As an optional implementation manner, the controller layer receives the service request sent by the application end, determines the tenant identifier associated with the service request through processing logic in the bridging layer, and sends the service request to the platform service interface corresponding to the tenant identifier.
Step S220, the platform service interface calls a service interface corresponding to a service identifier of the service request after receiving the service request;
step S230, the service interface sends the service request to the target platform.
In this embodiment, the type of service that the service request needs to invoke is determined by the service identifier.
As an optional implementation manner, after the controller layer sends the service request to the platform service interface corresponding to the tenant identifier, the platform service interface determines the service identifier of the service request, sends the service request to the service interface corresponding to the service identifier, and the service interface forwards the service request to the target platform corresponding to the tenant identifier.
Illustratively, after the Service request reaches the inside of the SaaS, the controller layer processes authentication and identifies the tenant identifier, and sends the Service identifier to the corresponding Service layer after authentication. And realizing the business logic of the SaaS Service per se in the Service layer, and entrusting the ServiceProvider calling interface to forward the business request to the business interface according to the tenant identification. The method comprises the steps of realizing a ServiceProvider layer based on a policy mode, and selecting a specific XServiceprovider by a tenant identifier: when the service request is forwarded to the corresponding XServiceProvider according to the tenant identifier, the XServiceProvider entrusts the service interface of the specific module according to the service identifier corresponding to the service request, and sends the service request to the corresponding target platform, so that the application end sends the service request to the SaaS platform end, and the platform end responds to the service request and feeds back the service data.
As another alternative implementation manner, after receiving the service request, the controller layer distributes the service request to the corresponding platform service interface according to the first-level service identifier of the service request; the platform service interface distributes the service request to a service interface under the platform service interface according to the second-level service identifier of the service request; and the service interface sends the service request to a target platform corresponding to the tenant identifier according to the tenant identifier carried by the service request.
The controller layer determines that the first-level service identifier of the service request is queried by personnel after receiving the service request, determines a platform service interface corresponding to the personnel query service, and forwards the service request to the corresponding platform service interface; determining that the second-level service identifier of the service request is queried according to an organization, and sending the service request to a corresponding service interface; and the service interface forwards the service request to a corresponding target platform through the tenant identifier carried by the service request.
Optionally, before step S210, the method further includes:
step S201, obtaining the registration information of the application terminal according to the service request;
step S202, when the registration information is unregistered, a prompt window without request permission is returned.
In this embodiment, whether the application can access the bridge module or not and whether the application has the access right of the platform end or not are verified according to the registration information. Registration information is further added, so that the security of data interaction is enhanced.
As an optional implementation manner, a registration information base stored by an application end in a bridging module is obtained, and whether the application end corresponding to the service request has matched registration information in the registration information base is judged; and when the registration information is unregistered, returning a prompt window without request permission, and returning the service request.
After step S201, when the registration information is registered, step S210 is performed.
The SaaS system records the registered application information of each application terminal on each SaaS platform, and when the service request of the application terminal reaches the SaaS system, the SaaS system judges whether the application is registered or not according to the registered application information, and the unregistered application terminal does not have the right to call the interface. After the registration information is verified to be correct, the SaaS transfers to the ServiceProvider of the corresponding platform according to the tenant identification, and calls the corresponding service interface.
The technical scheme provided by the embodiment of the application at least has the following technical effects or advantages:
the controller layer is adopted to distribute the service request to a platform service interface corresponding to the tenant identifier according to the tenant identifier corresponding to the service request; after receiving the service request, the platform service interface calls a service interface corresponding to a service identifier of the service request; and the service interface sends the service request to the target platform. Based on the refinement setting of the bridging layer in the bridging module, the forwarding logic for the application end to send the service request to the platform end is realized by combining the whole scheme.
Example III
Based on the first embodiment, the third embodiment of the present application provides a bridging method between an application and a platform, and before step S130, the method further includes:
step S310, the adaptation layer acquires a function packet corresponding to a platform to be docked, and sends the function packet to the service layer;
in this embodiment, the function package refers to various services corresponding to the platform. The platform to be docked refers to a SaaS platform end to be docked. There may be multiple platforms to be docked. The general capability model of SaaS communication is divided into two parts: the standard data model is standard data output to downstream applications, and the standard interface is a unified universal interface which is formed by extracting common capabilities provided by different SaaS (software as a service) platforms. By establishing a general capability model, the SaaS-based platform data difference can be shielded inside the SaaS.
As an optional implementation manner, the adaptation layer obtains each function packet corresponding to the platform to be docked based on various services of the platform to be docked, and sends each function packet to the service layer.
Step S320, after receiving the function packages, the service layer extracts the same function packages in each platform to be docked as a general function package;
And step S330, establishing the standard data model according to the business relation and the general function package.
As an optional implementation manner, after receiving the function package, the service layer extracts the function package corresponding to the same service from each platform to be docked as a general function package based on the service type; and establishing a standard data model by the functional package based on the service relation corresponding to the same service.
By way of example, the services provided by different SaaS platforms are obtained, and three standard data models are abstracted based on the common capabilities among the services: personnel models, institution models, and enterprise models.
According to the function package obtained from each platform end, determining the service of outputting personnel information, each platform end can output fields for representing the enterprise ID recorded at the platform end, the staff number in the enterprise and the staff number registered at the platform end, the field names in each platform end can be different, and extracting the fields as standard fields: platform-level enterprise ID, enterprise-level employee number, and platform-level employee number, and generates a personnel standard model. Meanwhile, other fields of the service of outputting personnel information in each platform are marked as special fields, and special fields with private attributes are marked as private fields.
Referring to fig. 3, the person model includes fields of: platform-level enterprise ID, enterprise-level employee number, and platform-level employee number.
Referring to generating an organization model and an enterprise model, wherein referring to fig. 4, the organization model includes fields of: the enterprise organization comprises an organization ID, a superior organization ID, an enterprise organization name, a path ID composed of the organization ID, a parent enterprise organization ID, a path composed of the enterprise organization ID, a full path name composed of the organization name, and a parent organization name. Referring to FIG. 5, the enterprise model includes fields that are: platform-level business ID, business name.
Optionally, step S130 includes:
step S340, the service layer determines the standard data model according to the service identification of the service data;
step S350, determining standard fields and specific fields in the service data according to the standard data model;
step S360, based on the standard field mapping rule of the target platform, taking the mapping value of the standard field as the field to be output;
step S370, sending the field to be output to a bridging layer.
Referring to fig. 6, in this embodiment, after a bridging layer of a bridging module receives a service request sent by an application end, the bridging layer forwards the service request to a corresponding SaaS platform according to a tenant identifier corresponding to the request, and after receiving service data responded by the SaaS platform, the bridging layer dynamically maps the service data to a field to be output and outputs the field to the application.
As an optional implementation manner, after receiving the service data, the service layer determines a standard field model corresponding to the service identifier according to the service identifier of the service data, and determines standard fields and specific fields in all fields of the service data according to the standard field model. And according to the standard data model, determining a standard field mapping rule of the target platform aiming at the standard data model, mapping the standard field into a field to be output based on the standard field mapping rule so as to complete the standardized processing of the service data, and sending the field to be output to the bridging layer.
Optionally, before step S370, the method further includes:
step S301, when a dependency relationship exists between the special field and the application end, determining a privacy attribute of the special field;
step S302, when the unique field is not a sensitive field, determining that the unique field is the field to be output.
As an optional implementation manner, it is determined whether a dependency relationship exists between a specific field and an application segment corresponding to a service request, when the dependency relationship exists, it is determined whether the specific field is a sensitive field, and when the specific field is not a sensitive field, the specific field is also used as a field to be output.
For the specific fields, part of application ends may have dependence, judging the dependence relationship of the specific fields and whether the specific fields are sensitive fields, and taking the fields which have the dependence relationship with the application ends and are not sensitive fields in the specific fields as the fields to be output; and intercepting the other special fields.
The adaptation layer is adopted to acquire a function packet corresponding to the platform to be docked, and the function packet is sent to the service layer; after receiving the function packages, the service layer extracts the same function packages in the platforms to be docked as universal function packages; according to the business relation and the general function package, the standard data model is established, so that the technical problems that the data management is difficult along with the increase of the number of the expansion platforms due to the mutual adaptation before application and saas conversion of the related technologies are effectively solved, the data difference between different platforms is integrated, the data management efficiency is improved, and the platform expansion development difficulty is reduced are effectively solved.
Example IV
Based on the first embodiment, a fourth embodiment of the present application provides a bridging method between an application and a platform, and after step S140, the method further includes:
Step S410, the service layer establishes standard field mapping rules of the platform to be docked based on the standard data model;
in this embodiment, the SaaS gateway establishes a field mapping record for each SaaS platform, establishes a one-to-one mapping relationship between fields in different standard data models and fields of the platform end, and dynamically standardizes and outputs data according to configured mapping after the SaaS gateway obtains service data responded by the platform end at the adaptation layer.
As an optional implementation manner, when the bridge module has completed adapting to the existing platform end and needs to adapt to a new platform to be docked, the service layer establishes standard field mapping rules of the platform to be docked under different service identifiers based on the standard data model.
Optionally, step S410 includes:
step S411, a first field in the standard data model is acquired;
step S412, determining that, in the platform to be docked, a field with the same semantic meaning as the first field is a standard field;
step S413, using the field having a semantic different from the first field as a unique field;
step S414, establishing the standard field mapping rule between the standard field and the first field.
In this embodiment, the first field refers to a field in the standard data model.
As an optional implementation manner, each field in the standard data model is obtained to be used as a first field, a field with the same semantic meaning as the first field in the fields of the platform to be docked is determined to be used as a standard field based on a semantic analysis algorithm, and a field with the different semantic meaning as a special field is determined to be used as a special field; and establishing a mapping relation between the standard field and the first field, and storing the mapping relation as a standard field mapping rule in association with a standard data model.
Illustratively, a first field in the personnel model is obtained: platform-level enterprise ID, enterprise-level employee number, and platform-level employee number. Determining fields in a platform to be docked, acquiring fields with the same semantics as the platform-level enterprise ID, the enterprise-level employee number and the platform-level employee number as standard fields, such as the enterprise ID, the employee ID and the platform-level employee number, establishing a mapping between the enterprise ID and the platform-level enterprise ID, establishing a mapping between the employee ID and the enterprise-level employee number, establishing a mapping between the platform-level employee number and the platform-level employee number, arranging the mapping into standard field mapping rules, and storing the standard field mapping rules in association with a personnel model and the platform to be docked.
Step S420, extracting the functional package of the platform to be docked, and generating a corresponding service interface;
step S430, generating the tenant identification of the platform to be docked according to a preset encryption rule.
As an optional implementation manner, the adaptation layer obtains the functional package of the platform to be docked, generates a corresponding service interface according to the service corresponding to the functional package, generates the tenant identification of the platform to be docked according to a preset encryption rule, and stores the tenant identification in association with the platform service interface and the service interface.
Because the service layer is adopted and based on the standard data model, standard field mapping rules of the platform to be docked are established; extracting the functional package of the platform to be docked to generate a corresponding service interface; the tenant identification of the platform to be docked is generated according to the preset encryption rule, so that the technical problem that development efficiency is low due to the fact that each application needs to carry out adaptation development aiming at data output of each platform in the related technology is effectively solved, and the technical effects of integrating data differences among different platforms and improving data management efficiency are achieved.
The application further provides a bridging device of the application and the platform, and referring to fig. 7, fig. 7 is a schematic structural diagram of the bridging device of the application and the platform of the hardware running environment related to the embodiment of the application.
As shown in fig. 7, the application and platform bridging device may include: a processor 1001, such as a central processing unit (Central Processing Unit, CPU), a communication bus 1002, a user interface 1003, a network interface 1004, a memory 1005. Wherein the communication bus 1002 is used to enable connected communication between these components. The user interface 1003 may include a Display, an input unit such as a Keyboard (Keyboard), and the optional user interface 1003 may further include a standard wired interface, a wireless interface. The network interface 1004 may optionally include a standard wired interface, a WIreless interface (e.g., a WIreless-FIdelity (WI-FI) interface). The Memory 1005 may be a high-speed random access Memory (Random Access Memory, RAM) Memory or a stable nonvolatile Memory (NVM), such as a disk Memory. The memory 1005 may also optionally be a storage device separate from the processor 1001 described above.
Those skilled in the art will appreciate that the structure shown in fig. 7 is not limiting of the application to a bridging device of a platform and may include more or fewer components than shown, or may combine certain components, or a different arrangement of components.
Optionally, the memory 1005 is electrically connected to the processor 1001, and the processor 1001 may be configured to control operation of the memory 1005, and may also read data in the memory 1005 to implement bridging between an application and a platform.
Alternatively, as shown in fig. 7, an operating system, a data storage module, a network communication module, a user interface module, and an application-platform bridging program may be included in the memory 1005 as one storage medium.
Optionally, in the application and platform bridging device shown in fig. 7, the network interface 1004 is mainly used for data communication with other devices; the user interface 1003 is mainly used for data interaction with a user; the processor 1001 and the memory 1005 in the application and platform bridging device of the present application may be disposed in the application and platform bridging device.
As shown in fig. 7, the application-platform bridging device invokes, through the processor 1001, an application-platform bridging program stored in the memory 1005, and executes the relevant step operations of the application-platform bridging method provided by the embodiment of the present application:
when the service request sent by the application terminal is received, forwarding the service request to a target platform corresponding to a tenant identifier of the service request;
Receiving the service data responded by the target platform aiming at the service request;
determining a standard data model corresponding to the service data, and carrying out standardization processing on the service data based on the standard data model;
and forwarding the standardized field to be output to the application end.
Optionally, the processor 1001 may call the application and platform bridging program stored in the memory 1005, and further perform the following operations:
the controller layer distributes the service request to a platform service interface corresponding to the tenant identifier according to the tenant identifier corresponding to the service request;
after receiving the service request, the platform service interface calls a service interface corresponding to a service identifier of the service request;
and the service interface sends the service request to the target platform.
Optionally, the processor 1001 may call the application and platform bridging program stored in the memory 1005, and further perform the following operations:
acquiring registration information of the application terminal according to the service request;
and when the registration information is unregistered, returning a prompt window without request permission.
Optionally, the processor 1001 may call the application and platform bridging program stored in the memory 1005, and further perform the following operations:
The service layer determines the standard data model according to the service identification of the service data;
determining standard fields and specific fields in the service data according to the standard data model;
based on a standard field mapping rule of the target platform, taking a mapping value of the standard field as the field to be output;
and sending the field to be output to a bridging layer.
Optionally, the processor 1001 may call the application and platform bridging program stored in the memory 1005, and further perform the following operations:
when the special field has a dependency relationship with the application end, determining the privacy attribute of the special field;
and when the special field is not a sensitive field, determining the special field as the field to be output.
Optionally, the processor 1001 may call the application and platform bridging program stored in the memory 1005, and further perform the following operations:
the adaptation layer acquires a function packet corresponding to the platform to be docked, and sends the function packet to the service layer;
after receiving the function packages, the service layer extracts the same function packages in the platforms to be docked as universal function packages;
and establishing the standard data model according to the business relation and the general function package.
Optionally, the processor 1001 may call the application and platform bridging program stored in the memory 1005, and further perform the following operations:
the service layer establishes standard field mapping rules of the platform to be docked based on the standard data model;
extracting the functional package of the platform to be docked to generate a corresponding service interface;
and generating the tenant identification of the platform to be docked according to a preset encryption rule.
Optionally, the processor 1001 may call the application and platform bridging program stored in the memory 1005, and further perform the following operations:
acquiring a first field in the standard data model;
determining that a field with the same semantic meaning as the first field in the platform to be docked is a standard field;
taking the field with the semantic meaning different from that of the first field as a specific field;
the standard field mapping rule between the standard field and the first field is established.
In addition, the embodiment of the application also provides a computer readable storage medium, wherein the computer readable storage medium stores an application and platform bridging program, and the application and platform bridging program realizes the relevant steps of any embodiment of the application and platform bridging method when being executed by a processor.
It will be appreciated by those skilled in the art that embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
It should be noted that in the claims, any reference signs placed between parentheses shall not be construed as limiting the claim. The word "comprising" does not exclude the presence of elements or steps not listed in a claim. The word "a" or "an" preceding an element does not exclude the presence of a plurality of such elements. The application may be implemented by means of hardware comprising several distinct elements, and by means of a suitably programmed computer. In the unit claims enumerating several means, several of these means may be embodied by one and the same item of hardware. The use of the words first, second, third, etc. do not denote any order. These words may be interpreted as names.
While preferred embodiments of the present application have been described, additional variations and modifications in those embodiments may occur to those skilled in the art once they learn of the basic inventive concepts. It is therefore intended that the following claims be interpreted as including the preferred embodiments and all such alterations and modifications as fall within the scope of the application.
It will be apparent to those skilled in the art that various modifications and variations can be made to the present application without departing from the spirit or scope of the application. Thus, it is intended that the present application also include such modifications and alterations insofar as they come within the scope of the appended claims or the equivalents thereof.
Claims (10)
1. The bridging method of the application and the platform is characterized by being applied to a bridging module and arranged between a SaaS platform end and an application end, and is used for forwarding a service request initiated by the application end to the platform end and forwarding service data responded by the platform end to the application end, and the bridging method of the application and the platform comprises the following steps:
when the service request sent by the application terminal is received, forwarding the service request to a target platform corresponding to a tenant identifier of the service request;
Receiving the service data responded by the target platform aiming at the service request;
determining a standard data model corresponding to the service data, and carrying out standardization processing on the service data based on the standard data model;
and forwarding the standardized field to be output to the application end.
2. The application and platform bridging method according to claim 1, wherein when receiving the service request sent by the application end, the step of forwarding the service request includes:
the controller layer distributes the service request to a platform service interface corresponding to the tenant identifier according to the tenant identifier corresponding to the service request;
after receiving the service request, the platform service interface calls a service interface corresponding to a service identifier of the service request;
and the service interface sends the service request to the target platform.
3. The application and platform bridging method of claim 2, wherein the controller layer, before the step of distributing the service request to the platform service interface corresponding to the tenant identifier according to the tenant identifier corresponding to the service request, further comprises:
Acquiring registration information of the application terminal according to the service request;
and when the registration information is unregistered, returning a prompt window without request permission.
4. The application and platform bridging method according to claim 1, wherein the step of determining a standard data model corresponding to the service data and performing normalization processing on the service data based on the standard data model includes:
the service layer determines the standard data model according to the service identification of the service data;
determining standard fields and specific fields in the service data according to the standard data model;
based on a standard field mapping rule of the target platform, taking a mapping value of the standard field as the field to be output;
and sending the field to be output to a bridging layer.
5. The application and platform bridging method according to claim 4, wherein before the step of sending the field to be output to a bridging layer, further comprising:
when the special field has a dependency relationship with the application end, determining the privacy attribute of the special field;
and when the special field is not a sensitive field, determining the special field as the field to be output.
6. The application and platform bridging method according to claim 1, wherein before the step of determining a standard data model corresponding to the service data and performing normalization processing on the service data based on the standard data model, further comprises:
the adaptation layer acquires a function packet corresponding to the platform to be docked, and sends the function packet to the service layer;
after receiving the function packages, the service layer extracts the same function packages in the platforms to be docked as universal function packages;
and establishing the standard data model according to the business relation and the general function package.
7. The application and platform bridging method according to claim 1, wherein after the step of forwarding the standardized field to be output to the application end, the method further comprises:
the service layer establishes standard field mapping rules of the platform to be docked based on the standard data model;
extracting the functional package of the platform to be docked to generate a corresponding service interface;
and generating the tenant identification of the platform to be docked according to a preset encryption rule.
8. The application and platform bridging method of claim 7, wherein the service layer establishes standard field mapping rules for the platform to be docked based on the standard data model, comprising:
Acquiring a first field in the standard data model;
determining that a field with the same semantic meaning as the first field in the platform to be docked is a standard field;
taking the field with the semantic meaning different from that of the first field as a specific field;
the standard field mapping rule between the standard field and the first field is established.
9. An application and platform bridging device comprising a memory, a processor and an application and platform bridging program stored on the memory and executable on the processor, the processor implementing the steps of the application and platform bridging method according to any one of claims 1 to 8 when executing the application and platform bridging program.
10. A computer readable storage medium, wherein an application and platform bridging program is stored on the computer readable storage medium, and the application and platform bridging program, when executed by a processor, implements the steps of the application and platform bridging method according to any one of claims 1 to 8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310764993.9A CN116737235A (en) | 2023-06-26 | 2023-06-26 | Application and platform bridging method, device and readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310764993.9A CN116737235A (en) | 2023-06-26 | 2023-06-26 | Application and platform bridging method, device and readable storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN116737235A true CN116737235A (en) | 2023-09-12 |
Family
ID=87916703
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202310764993.9A Pending CN116737235A (en) | 2023-06-26 | 2023-06-26 | Application and platform bridging method, device and readable storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN116737235A (en) |
-
2023
- 2023-06-26 CN CN202310764993.9A patent/CN116737235A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10957326B2 (en) | Device identifier dependent operation processing of packet based data communication | |
| KR102514325B1 (en) | Model training system and method, storage medium | |
| US20200177572A1 (en) | Sending cross-chain authenticatable messages | |
| CN101809562B (en) | Service-oriented pipeline based architecture | |
| CN104081748B (en) | Document communication runtime interface | |
| EP3953834A1 (en) | Systems, devices, and methods for dlt-based data management platforms and data products | |
| CN113037831B (en) | Service gateway message processing method and device | |
| CN110602056A (en) | Service parameter transmission method and device | |
| CN111698205A (en) | Service calling method and related equipment | |
| CN111988418B (en) | Data processing method, device, equipment and computer readable storage medium | |
| CN109697370A (en) | Database data encipher-decipher method, device, computer equipment and storage medium | |
| JP2007148471A (en) | Service notification system | |
| WO2021036583A1 (en) | Blockchain-based clearing method, apparatus and device, and computer storage medium | |
| CN111552568A (en) | Cloud service calling method and device | |
| CN112150030A (en) | Account management method based on multiple units and multiple identities, terminal equipment and storage medium | |
| CN106506568B (en) | Information interaction system | |
| CN108092947B (en) | Method and device for identity authentication of third-party application | |
| CN110955905A (en) | Block chain based asset transfer method, device, equipment and readable storage medium | |
| CN107579990A (en) | Measure of managing contract and server | |
| WO2023208132A1 (en) | Api conversion system and access request processing method therefor, and electronic device and medium | |
| US20110202668A1 (en) | Methods for Creating and Using a Telecommunications Link between Two Users of a Telecommunications Network | |
| US11290575B2 (en) | Connecting computer processing systems and transmitting data | |
| CN109525550B (en) | Data message processing method, device and system | |
| CN116737235A (en) | Application and platform bridging method, device and readable storage medium | |
| US11573808B2 (en) | Methods of providing an integrated interface that includes a virtual mobile device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |