CN112416629A - Data intercommunication method, system and storage medium - Google Patents

Data intercommunication method, system and storage medium Download PDF

Info

Publication number
CN112416629A
CN112416629A CN202011434544.0A CN202011434544A CN112416629A CN 112416629 A CN112416629 A CN 112416629A CN 202011434544 A CN202011434544 A CN 202011434544A CN 112416629 A CN112416629 A CN 112416629A
Authority
CN
China
Prior art keywords
data
application
application data
shared memory
server
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.)
Granted
Application number
CN202011434544.0A
Other languages
Chinese (zh)
Other versions
CN112416629B (en
Inventor
朱智力
张若
段怡枫
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Shenzhen Futu Network Technology Co Ltd
Original Assignee
Shenzhen Futu Network Technology Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Shenzhen Futu Network Technology Co Ltd filed Critical Shenzhen Futu Network Technology Co Ltd
Priority to CN202011434544.0A priority Critical patent/CN112416629B/en
Publication of CN112416629A publication Critical patent/CN112416629A/en
Application granted granted Critical
Publication of CN112416629B publication Critical patent/CN112416629B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/54—Interprogram communication
    • G06F9/547—Remote procedure calls [RPC]; Web services
    • 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)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

The application discloses a data intercommunication method, a system and a storage medium, wherein the method comprises the following steps: the method comprises the steps that a first background server obtains first application data of a user, wherein the first application data are data of a main application used by the user; writing first application data to the shared memory and the first local memory; if the second synchronous server monitors that the first data updating event exists in the shared memory, the first application data are read from the shared memory and stored in the second local memory, and therefore the second synchronous server monitors the data updating event in the shared memory in real time, newly added data can be communicated in time, and user experience of using related applications is improved.

Description

Data intercommunication method, system and storage medium
Technical Field
The present application relates to the field of data processing, and in particular, to a data interworking method, system, and storage medium.
Background
At present, more and more applications are associated with other applications, and the requirements of fusion and intercommunication of service data exist, the associated applications may be domestic version and overseas version applications developed by the same company, or functions developed by the same company have associated applications, such as payment applications, shopping applications, different social applications developed by the same company, and the like, intercommunication is required on application data, along with diversification of application functions, the application data required to be intercommunicated is more and more complex and diversified, and once pulling is adopted more, incremental data intercommunication is not supported, so that the interactive experience of a user on the data intercommunication function is poor.
Disclosure of Invention
The embodiment of the application provides a data intercommunication method, a data intercommunication system and a storage medium, which can intercommunicate newly added data in time and improve the experience of using associated applications by a user.
In a first aspect, an embodiment of the present application provides a data interworking method, which is applied to a data interworking system, where the data interworking system includes a master application, at least one slave application, a first background server corresponding to the master application, a first local storage, a second synchronization server corresponding to the slave application, a second local storage, and a shared storage, and the method includes:
the first background server acquires first application data of a user, wherein the first application data is data of the user using the main application; the first background server writes the first application data into the shared memory and the first local memory;
and if the second synchronous server monitors that a first data updating event exists in the shared memory, reading the first application data from the shared memory, and storing the first application data to the second local memory.
In a second aspect, an embodiment of the present application provides a data interworking system, where the data interworking system includes a master application, at least one slave application, a first background server corresponding to the master application, a first local storage, a second synchronization server corresponding to the slave application, a second local storage, and a shared storage, where,
the first background server is used for acquiring first application data of a user, wherein the first application data is data of the main application used by the user; the first background server writes the first application data into the shared memory and the first local memory;
the second synchronous server is used for reading the first application data from the shared memory and storing the first application data to the second local memory if monitoring that a first data updating event exists in the shared memory.
In a third aspect, an embodiment of the present application provides a data interworking method, which is applied to a first background server corresponding to a host application, and the method includes:
acquiring first application data of a user, wherein the first application data is data of the user using the main application; the first background server writes the first application data into the shared memory and the first local memory; the first application data is used for reading the first application data from the shared memory and storing the first application data into a second local memory if a second synchronous server monitors that a first data updating event exists in the shared memory.
In a fourth aspect, embodiments of the present application provide a server, including a processor, a memory, a communication interface, and one or more programs, where the one or more programs are stored in the memory and configured to be executed by the processor, and the program includes instructions for performing the steps of the method according to the third aspect of the embodiments of the present application.
In a fifth aspect, embodiments of the present application provide a computer-readable storage medium for storing a computer program, where the computer program is executed by a processor to implement some or all of the steps described in the method according to the first aspect of the embodiments of the present application.
In a sixth aspect, embodiments of the present application provide a computer program product comprising a non-transitory computer readable storage medium storing a computer program operable to cause a computer to perform some or all of the steps described in the method according to the first aspect of embodiments of the present application. The computer program product may be a software installation package.
By adopting the embodiment of the application, the following beneficial effects are achieved:
it can be seen that the data interworking method, system, and storage medium described in the embodiments of the present application are applied to a data interworking system, where the data interworking system includes a master application, at least one slave application, a first background server corresponding to the master application, a first local storage, a second synchronization server corresponding to the slave application, a second local storage, and a shared storage, where the first background server obtains first application data of a user, and the first application data is data of the master application used by the user; writing first application data to the shared memory and the first local memory; if the second synchronous server monitors that the first data updating event exists in the shared memory, the first application data are read from the shared memory and stored in the second local memory, and therefore the second synchronous server monitors the data updating event in the shared memory in real time, newly added data can be communicated in time, and user experience of using related applications is improved.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present application, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.
Fig. 1 is a schematic structural diagram of a data interworking system according to an embodiment of the present application;
fig. 2 is a flowchart illustrating a data interworking method according to an embodiment of the present application;
fig. 3 is a flowchart illustrating another data interworking method according to an embodiment of the present application;
fig. 4 is a flowchart illustrating another data interworking method according to an embodiment of the present application;
fig. 5 is a schematic structural diagram of a first backend server according to an embodiment of the present application;
fig. 6 is a schematic structural diagram of a second synchronization server according to an embodiment of the present application.
Detailed Description
In order to make the technical solutions better understood by those skilled in the art, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only partial embodiments of the present application, but not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
The following are detailed below.
The terms "first," "second," "third," and "fourth," etc. in the description and claims of this application and in the accompanying drawings are used for distinguishing between different objects and not for describing a particular order. Furthermore, the terms "include" and "have," as well as any variations thereof, are intended to cover non-exclusive inclusions. For example, a process, method, system, article, or apparatus that comprises a list of steps or elements is not limited to only those steps or elements listed, but may alternatively include other steps or elements not listed, or inherent to such process, method, article, or apparatus.
Reference herein to "an embodiment" means that a particular feature, structure, or characteristic described in connection with the embodiment can be included in at least one embodiment of the application. The appearances of the phrase in various places in the specification are not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive of other embodiments. It is explicitly and implicitly understood by one skilled in the art that the embodiments described herein can be combined with other embodiments.
The following describes embodiments of the present application in detail.
Referring to fig. 1, a system architecture diagram of a data interworking system according to an embodiment of the present invention is shown, where the data interworking system includes a master application, at least one slave application, a first background server, a first local storage, a first synchronization server corresponding to the master application, a second synchronization server, a second background server, a second local storage, and a shared storage, where,
the first background server is used for acquiring first application data of a user, wherein the first application data is data of the main application used by the user; the first background server writes the first application data into the shared memory and the first local memory;
the second synchronous server is used for reading the first application data from the shared memory and storing the first application data to the second local memory if monitoring that a first data updating event exists in the shared memory.
The master application and the slave application are interchangeable in an actual application, and the master application and the slave application are different in that the master application can be used for performing read-write operation of an Object Storage Service (OSS).
In a specific implementation, both the master application and the at least one slave application may be set on a client of a User, where the client where the master application is located and the client where the slave application is located may be the same client or different clients, and the embodiments of the present application are not limited thereto, where the clients may include various handheld devices (Mobile phones, tablet computers, and the like) having a wireless communication function, vehicle-mounted devices, wearable devices (e.g., smart watches, smart glasses, and the like), computing devices, or other processing devices connected to a wireless modem, and various forms of User Equipment (UE), Mobile Stations (MS), virtual reality/augmented reality devices, terminal devices (terminal devices), and the like.
Optionally, in a specific implementation, the master application may be a native application of the same functional application, and the slave application may be an overseas application, or the master application may be an overseas application, and the slave application may be a native application; for example, the master and slave applications may be respectively domestic and overseas versions of stock exchange software developed for the same company;
or,
the master application and the slave application may be first social software and second social software developed by one company, respectively, or the master application and the slave application may be shopping software and payment software developed by one company, respectively. The application types or functions of the master application and the slave application are not limited in the embodiments of the present application.
In practical application, both the master application and the slave application can be used as a data source side and a data receiving side for data intercommunication, and the data receiving side can synchronize first application data from the data source side to realize a data intercommunication function.
The first background server can be used for writing the application data of the main application into the shared memory; the second backend server may be used to write application data for the slave application to the shared memory.
The shared memory is used as a channel for application data intercommunication, so that the first background server can write the application data of the master application into the shared memory, and the second background server can write the application data of the slave application into the shared memory; and if the second synchronous server monitors that the first data updating event exists in the shared memory, the first application data is stored in the second local memory.
The first synchronous server and the second synchronous server are used for monitoring data updating events in the shared memory; the first synchronous server is used for writing the read application data into the first local server; and the second synchronous server is used for writing the read application data into the second local server.
Therefore, after the second synchronization server stores the first application data in the second local storage, the second background server can read the first application data from the second local server and transmit the first application data to the second client corresponding to the slave application for displaying.
The first background server is also used for performing read-write operation with the first local server; the second background server is also used for performing read-write operation with the second local server.
Optionally, in the process that the first background server writes the first application data into the shared memory, the method further includes:
the first background server adds a first update time and/or a first update source location at which the first application data is written to the shared memory to a shared memory data table in the shared memory.
Wherein the first update source location refers to a source application of the first application data, e.g., the first application data may be sourced from a master application or sourced from a slave application.
Optionally, the data interworking system further includes a first synchronization server corresponding to the primary application, and when the second synchronization server stores the first application data in the second local storage, the method further includes:
if the second synchronous server writes the first application data into the shared memory; adding a second update time and/or a second update source location at which the first application data is written to the shared memory to a shared memory data table in the shared memory;
if the first synchronization server monitors that a second data updating event exists in the shared memory, whether the position of the first updating source is consistent with that of the second updating source is judged, and if so, the first synchronization server does not update the first application data any more; and if the first data updating event is not consistent with the second data updating event, the first synchronization server adds second application data corresponding to the second data updating event to a shared storage data table in the shared storage.
In the embodiment of the application, the second synchronization server may write the first application data into the shared memory, trigger the first synchronization server to perform a new round of application data synchronization, and may trigger the secondary application synchronization service update again, causing the data update to fall into a cycle, therefore, if the first synchronization server monitors that the second data update event exists in the shared memory, the location of the first update source may be compared with the location of the second update source, if the first update source is consistent with the second update source, it indicates that the same application data of the two data update events are from the same application, there is a repeated synchronization service update, the first synchronization server does not update the first application data, and reports an exception of the second data update event that the synchronization service update exists, if the second update event is not consistent, it indicates that the data of the two data update events are from different applications, and belong to a normal synchronization service update, second application data corresponding to the second data update event may be added to the shared memory.
Optionally, in this embodiment of the application, if the first synchronization server monitors that the second data update event exists in the shared memory, the second data update event may be determined to be an application data update of the second application according to the second update time and the first update time, and then the first synchronization server may add the second application data corresponding to the second data update event to the shared storage data table in the shared memory. Therefore, whether new application data are updated or not can be judged only through the updating time, when the second updating time is determined to be inconsistent with the first updating time, normal synchronous service updating can be determined, and the second application data corresponding to the second data updating event are added to the shared memory, so that the service transformation difficulty and workload can be reduced, and the efficiency of synchronous data sharing is improved.
Optionally, after the second synchronization server reads the first application data from the shared memory, before storing the first application data in the second local memory, the method further includes:
the second synchronous server carries out the following processing on the first application data: processing by a general component; and/or, processing by a custom component; wherein the generic component is to perform the following: permission checking, and/or sensitive word filtering.
The customized component is used for processing, customized processing steps can be executed according to the data type and configuration, for example, interaction with a cloud server is performed, and in specific implementation, if the customized component processing is not required, the step is skipped.
Optionally, if the processing performed by the general component includes permission verification, the processing the first application data by the general component includes:
determining a first data type corresponding to the first application data;
if the preset white list comprises the first data type, the authority passes the verification, and the first application data is reserved; otherwise, filtering the first application data.
Wherein the first data type may be at least one of: comment, like, follow, focus on, vote.
Optionally, if the processing performed by the general component includes permission verification, the processing the first application data by the general component includes:
determining a first data type corresponding to the first application data;
determining an audit state corresponding to the first data type audited from the application;
if the audit state is that the audit is passed, the authority verification is passed; otherwise, the check fails.
In a specific implementation, the auditing status may include: audit not passed, not audited, masked, etc.
Optionally, the first application corresponds to a first usage area, and the second application corresponds to a second usage area, and the method further includes:
the first background server determines whether the first application data comprises keywords in a first keyword set corresponding to the first use region, and if so, shields or does not display data items comprising the keywords in the first application data; if not, sending the first application data to a first client corresponding to the main application for display;
the processing the first application data by the common component includes:
the second synchronous server determines whether the first application data comprises keywords in a second keyword set corresponding to the second use region, and if so, shields or does not display data items comprising the keywords in the first application data;
if not, acquiring first account information of the user, determining whether a preset blacklist corresponding to the second use region comprises the first account information, and if so, shielding or not displaying the first application data;
and if not, executing the operation of storing the first application data to the second local memory.
Optionally, if the first application data is first account information of the user in the primary application, the method further includes:
when the second background server receives an account login request aiming at the secondary application from a client, extracting login account information from the account login request;
and matching the login account information with the first account information, and if the matching is successful, sending feedback information that the account verification is passed to a second client corresponding to the slave application, wherein the feedback information is used for indicating the login operation authorization of the second client to the login account information.
In the embodiment of the application, the account numbers between the master application and the slave application can be logged in.
Optionally, the data interworking system further includes a second background server corresponding to the slave application, and if the first application data is the notification of the master application, the method further includes:
and the second background server determines whether the slave application is in a login online state, and if so, sends the notification to a second client corresponding to the slave application, wherein the second client is used for displaying the notification.
If the slave application is not in the login online state, the notification is not sent.
Optionally, after the second synchronization server stores the first application data to the second local storage, the method further comprises:
the second background server acquires the first application data from the first local storage;
converting the display parameters of the first application data to obtain converted first application data;
and transmitting the converted first application data to a second client corresponding to the slave application, wherein the second client is used for displaying the converted first application data.
In specific implementation, the style of the application data displayed by the master application and the slave application is different, so that the display parameter of the first application data can be converted to obtain the converted first application data, and the converted first application data is displayed on an application interface of the slave application.
It can be seen that the data interworking system described in the embodiment of the present application includes a master application, at least one slave application, a first background server corresponding to the master application, a first local storage, a second synchronization server corresponding to the slave application, a second local storage, and a shared storage, where the first background server obtains first application data of a user, and the first application data is data of the user using the master application; writing first application data to the shared memory and the first local memory; if the second synchronous server monitors that the first data updating event exists in the shared memory, the first application data are read from the shared memory and stored in the second local memory, and therefore the second synchronous server monitors the data updating event in the shared memory in real time, newly added data can be communicated in time, and user experience of using related applications is improved.
Referring to fig. 2, fig. 2 is a flowchart illustrating a data interworking method according to an embodiment of the present application, and the data interworking method is applied to the data interworking system shown in fig. 1, and the data interworking method specifically includes the following steps:
201. a first background server acquires first application data of a user, wherein the first application data is data of the user using the main application; the first background server writes the first application data into the shared memory and the first local memory.
Wherein the first application data may include at least one of: the user's profile, the user's interaction information, which may include comments, praise, vote, concern, etc., entered on the host application by the user, notifications, and other application data generated by the user when using the host application.
In one possible example, during the writing of the first application data to the shared memory by the first backend server, the method further comprises:
the first background server adds a first update time and/or a first update source location at which the first application data is written to the shared memory to a shared memory data table in the shared memory.
Wherein the first update source location refers to a source application of the first application data, e.g., the first application data is sourced from a primary application.
In a specific implementation, the first update time and/or the first update source location are added to the shared storage data table in the shared memory, so that when the second synchronization server monitors a data update event, whether data intercommunication is required to be performed on the updated data can be determined according to the first update time and/or the first update source location.
202. And if the second synchronous server monitors that a first data updating event exists in the shared memory, reading the first application data from the shared memory, and storing the first application data to the second local memory.
The second synchronization server may monitor a data update event in the shared memory, and if the first data update event is monitored, may read the first application data from the shared memory and store the first application data in the second local memory.
In one possible example, the data interworking system further includes a first synchronization server corresponding to the primary application, and when the second synchronization server stores the first application data in the second local storage, the method further includes:
the second synchronization server writing the first application data to the shared memory; adding a second update time and/or a second update source location at which the first application data is written to the shared memory to a shared memory data table in the shared memory;
if the first synchronization server monitors that a second data updating event exists in the shared memory, whether the position of the first updating source is consistent with that of the second updating source is judged, and if so, the first synchronization server does not update the first application data any more; and if the first data updating event is not consistent with the second data updating event, the first synchronization server adds second application data corresponding to the second data updating event to a shared storage data table in the shared storage.
The second synchronization server may write the first application data into the shared memory, trigger the first synchronization server to perform a new round of application data synchronization, and may trigger the secondary application synchronization service update again, causing the data update to fall into a cycle, so that if the first synchronization server monitors that a second data update event exists in the shared memory, the location of the first update source may be compared with the location of the second update source, and if the first update source is consistent with the second update source, it indicates that the same application data updated by the two data update events is from the same application, there is a repeated synchronization service update, the first synchronization server does not update the first application data any more, and reports an abnormality that the synchronization service update exists in the second data update event; if the data updating events are inconsistent, the data updated by the two data updating events are from different applications and belong to normal synchronous service updating, and the second application data corresponding to the second data updating event can be added to the shared memory.
It can be seen that by comparing the first update source location with the second update source location, a cycle of data interworking can be prevented.
In one possible example, after the second synchronization server reads the first application data from the shared memory, before storing the first application data to the second local memory, the method further comprises:
the second synchronous server carries out the following processing on the first application data: processing by a general component; and/or, processing by a custom component; wherein the generic component is to perform the following: permission checking, and/or sensitive word filtering.
Different authority check or sensitive word filtering rules can be set for different types of first application data.
Optionally, the permission check is performed through a general component, and may include: if the master application is a domestic application and the slave application is an overseas application, verifying whether the login account information of the slave application is bound with a domestic mobile phone number, and if so, determining that the permission verification is passed; or if the master application is the home application and the slave application is the home application, verifying whether the slave application is in an account login online state, and if so, determining that the permission check is passed.
In specific implementation, for overseas slave applications, if the slave applications need to display first application data through data intercommunication, whether the login account information of the slave applications is bound with an in-home mobile phone number or not can be determined, if yes, the login account of the slave applications is subjected to overseas real-name authentication, so that permission verification can be determined, and the slave applications are authorized to display the first application data from the master application; for the slave application of the home version, only the slave application needs to be determined to be in the account login online state, the permission check can be determined to pass, and then the first application data derived from the master application is displayed in the slave application.
For example, the master application is a domestic edition of a stock trading application, and the slave application is a overseas edition of a stock trading application, the first application data may include at least one of: the list page data of the master application, the detail page of the master application, the personal data of the user on the master application, comments input by the user on the master application and the like can verify whether the login account information of the slave application is bound with the domestic mobile phone number, if so, the login account information of the slave application is authenticated by the overseas real name, the permission verification can be determined to be passed, and then the first application data can be displayed on the second client corresponding to the slave application.
Optionally, if the processing performed by the general component includes sensitive word filtering, the processing the first application data by the general component includes:
determining a first data type corresponding to the first application data;
if the preset white list comprises the first data type, the first application data is reserved; otherwise, filtering the first application data.
In specific implementation, if the first application data is a comment or a notification of the first application, the notification type is as follows: comment, like, pay attention to, vote, etc., confirm the type of notice; judging whether a preset white list comprises a notification type, if so, retaining the notification; otherwise, the notification is filtered.
In specific implementation, if the first application data is stock market information and stock transaction information, whether a preset white list comprises data types of the stock market information and the stock transaction information is judged, if yes, the authority check is passed, and the first application data is reserved.
Optionally, if the processing performed by the general component includes permission verification, the processing the first application data by the general component includes:
determining a second data type corresponding to the first application data;
determining an audit state corresponding to the second data type audited from the application;
if the audit state is that the audit is passed, the authority verification is passed; otherwise, the check fails.
In a specific implementation, the second data type may include: comments, personal data, community contents and the like can be checked on the data of the second data type through preset checking rules to obtain a checking state, and if the checking state is that the checking is passed, the permission verification is passed; otherwise, the check fails.
Optionally, the first application corresponds to a first usage area, and the second application corresponds to a second usage area, and the method further includes:
the first background server determines whether the first application data comprises keywords in a first keyword set corresponding to the first use region, and if so, shields or does not display data items comprising the keywords in the first application data; if not, sending the first application data to a first client corresponding to the main application for display;
the processing the first application data by the common component includes:
the second synchronous server determines whether the first application data comprises keywords in a second keyword set corresponding to the second use region, and if so, shields or does not display data items comprising the keywords in the first application data;
if not, acquiring first account information of the user, determining whether a preset blacklist corresponding to the second use region comprises the first account information, and if so, shielding or not displaying the first application data;
and if not, executing the operation of storing the first application data to the second local memory.
The first usage region may be domestic and the second usage region may be overseas, or the first usage region may be overseas and the second usage region may be domestic.
In specific implementation, if the first application data includes a keyword in a first keyword set corresponding to the first usage region, if so, the data item including the keyword in the first application data is shielded or not displayed. If the first application data comprises keywords in a second keyword set corresponding to a second use region, shielding or not displaying the data items comprising the keywords in the first application data; if not, acquiring first account information of the user, determining whether a preset blacklist corresponding to a second use region comprises the first account information, and if so, shielding or not displaying the first application data.
Optionally, the data interworking system further includes a second background server corresponding to the slave application, and if the first application data is first account information of the user in the master application, the method further includes:
when the second background server receives an account login request aiming at the secondary application from a client, extracting login account information from the account login request;
and matching the login account information with the first account information, and if the matching is successful, sending feedback information that the account verification is passed to a second client corresponding to the slave application, wherein the feedback information is used for indicating the login operation authorization of the second client to the login account information.
The login account information is matched with the first account information, if the matching is successful, feedback information that account verification is passed is sent to a second client corresponding to the slave application, and the second client can authorize login operation of the login account information, so that account login between the master application and the slave application is achieved, namely one account information can be communicated between the two applications.
Optionally, the data interworking system further includes a second background server corresponding to the slave application, and if the first application data is the notification of the master application, the method further includes:
and the second background server determines whether the slave application is in a login online state, and if so, sends the notification to a second client corresponding to the slave application, wherein the second client is used for displaying the notification.
And if the slave application is not in the login online state, the notification is not sent.
Optionally, after the second synchronization server stores the first application data to the second local storage, the method further comprises:
the second background server acquires the first application data from the first local storage;
converting the display parameters of the first application data to obtain converted first application data;
and transmitting the converted first application data to a second client corresponding to the slave application, wherein the second client is used for displaying the converted first application data.
The display parameter of the first application data can be converted to obtain the converted first application data, so that the converted first application data can be displayed on the application interface of the slave application.
Optionally, the writing, by the first background server, the first application data into the shared memory includes:
the first background server determines a target priority corresponding to the data type of the first application data according to a mapping relation between a preset data type and the priority;
adding a target address node in a target layer corresponding to the target priority in a preset address tree, wherein the target address node comprises a target address, and the target address and a reference address included by an adjacent node of the target address node are in the same storage area, the preset address tree comprises a plurality of layers of address nodes, and each layer corresponds to one priority;
storing the first application data to the target address node;
the second synchronization server reads the first application data from the shared memory, including:
traversing the address tree by the second synchronous server to obtain at least one newly added address node, wherein the at least one newly added address node comprises the target address node;
and reading the first application data and other synchronously updated application data according to the at least one newly added address node.
And the target address node is further used for storing the first updating time, the first updating source position and the data identifier corresponding to the first application data.
In specific implementation, considering that the types of first application data are various, different types of data are actually read, written and displayed at a client corresponding to an application, different data channels can be allocated, a first background server can divide the application data according to priority level regions based on the relation of storage addresses between nodes of each layer in a preset address tree, allocates target addresses according to the adjacent relation of the nodes of each layer, and stores the same type of data in the same storage region, so that a second synchronous server can read the first application data according to the address tree; the second synchronization server can traverse the address tree to obtain at least one newly added address node according to the priority sequence of the data types, and therefore when a plurality of newly added application data exist, data can be read according to the priority sequence of the data types, and therefore the data reading efficiency can be improved.
It can be seen that the data interworking method described in the embodiment of the present application is applied to a data interworking system, where the data interworking system includes a master application, at least one slave application, a first background server corresponding to the master application, a first local storage, a second synchronization server corresponding to the slave application, a second local storage, and a shared storage, the first background server obtains first application data of a user, and the first application data is data of the master application used by the user; writing first application data to the shared memory and the first local memory; if the second synchronous server monitors that the first data updating event exists in the shared memory, the first application data are read from the shared memory and stored in the second local memory, and therefore the second synchronous server monitors the data updating event in the shared memory in real time, newly added data can be communicated in time, and user experience of using related applications is improved.
Referring to fig. 3, in accordance with the embodiments shown in fig. 1-fig. 2, fig. 3 is another data interworking method provided in the embodiment of the present application, which is applied to a first background server corresponding to a host application, and specifically includes the following steps:
301. and acquiring first application data of a user, wherein the first application data is data of the user using the main application.
302. The first background server writes the first application data into the shared memory and the first local memory; the first application data is used for reading the first application data from the shared memory and storing the first application data into a second local memory if a second synchronous server monitors that a first data updating event exists in the shared memory.
Optionally, in the process that the first background server writes the first application data into the shared memory, the method further includes:
the first background server adds a first update time and/or a first update source location at which the first application data is written to the shared memory to a shared memory data table in the shared memory.
Optionally, the method further comprises:
the first background server determines whether the first application data comprises keywords in a first keyword set corresponding to the first use region, and if so, shields or does not display data items comprising the keywords in the first application data; and if not, sending the first application data to a first client corresponding to the main application for display.
The detailed description of steps 301 to 302 may refer to the corresponding steps of the data interworking method described in fig. 2, and will not be described herein again.
It can be seen that, in the data interworking method described in the embodiment of the present application, first application data of a user is obtained, where the first application data is data of the user using the main application; writing first application data to the shared memory and a first local memory; the first application data is used for reading the first application data from the shared memory by the second synchronous server if the second synchronous server monitors that the shared memory has the first data updating event, storing the first application data into the second local memory, and monitoring the data updating event in the shared memory in real time through the second synchronous server, so that the newly added data can be communicated in time, and the experience of using the associated application by a user is improved.
Referring to fig. 4, in accordance with the embodiments shown in fig. 1 to fig. 3, fig. 4 is another data interworking method provided in the embodiment of the present application, applied to a second synchronization server corresponding to a slave application, and specifically includes the following steps:
401. and if the second synchronous server monitors that a first data updating event exists in the shared memory, reading the first application data from the shared memory, wherein the first application data is data of a main application used by a user, and the first application data is obtained by a first background server and is written into the shared memory and the first local memory.
402. Storing the first application data to the second local memory.
Optionally, the method further comprises:
the second synchronization server writing the first application data to the shared memory; adding a second update time and/or a second update source location at which the first application data is written to the shared memory to a shared memory data table in the shared memory; the second update time and the second update source location are used for judging whether the first update source location is consistent with the second update source location if the first synchronization server monitors that a second data update event exists in the shared memory, and if so, the first synchronization server does not update the first application data any more; and if the first data updating event is not consistent with the second data updating event, the first synchronization server adds second application data corresponding to the second data updating event to a shared storage data table in the shared storage.
Optionally, after the second synchronization server reads the first application data from the shared memory, before storing the first application data in the second local memory, the method further includes:
the second synchronous server carries out the following processing on the first application data: processing by a general component; and/or, processing by a custom component; wherein the generic component is to perform the following: permission checking, and/or sensitive word filtering.
Optionally, if the processing performed by the general component includes sensitive word filtering, the processing the first application data by the general component includes:
determining a first data type corresponding to the first application data;
if the preset white list comprises the first data type, the first application data is reserved; otherwise, filtering the first application data.
Optionally, if the processing performed by the general component includes permission verification, the processing the first application data by the general component includes:
determining a second data type corresponding to the first application data;
determining an audit state corresponding to the second data type audited from the application;
if the audit state is that the audit is passed, the authority verification is passed; otherwise, the check fails.
Optionally, the processing the first application data by a general component includes:
the second synchronous server determines whether the first application data comprises keywords in a second keyword set corresponding to the second use region, and if so, shields or does not display data items comprising the keywords in the first application data;
if not, acquiring first account information of the user, determining whether a preset blacklist corresponding to the second use region comprises the first account information, and if so, shielding or not displaying the first application data;
and if not, executing the operation of storing the first application data to the second local memory.
The detailed description of the steps 401 to 402 may refer to the corresponding steps of the data interworking method described in fig. 2, and will not be described herein again.
It can be seen that, in the data interworking method described in the embodiment of the present application, if the second synchronization server monitors that the shared memory has the first data update event, the first application data is read from the shared memory, where the first application data is data of the main application used by the user, and the first application data is obtained by the first background server, and is written into the shared memory and the data of the first local memory, and the first application data is stored in the second local memory, and the second synchronization server monitors the data update event in the shared memory in real time, so that the new data can be timely interworked, and the experience of the user in using the associated application is improved.
Referring to fig. 5 in keeping with the embodiments shown in fig. 1-4, fig. 5 is a schematic structural diagram of a first backend server provided in an embodiment of the present application, and as shown in the figure, the first backend server includes a processor, a memory, a communication interface, and one or more programs, where the one or more programs are stored in the memory and configured to be executed by the processor, and the program includes instructions for performing the following steps:
acquiring first application data of a user, wherein the first application data is data of the user using the main application; the first background server writes the first application data into the shared memory and the first local memory; the first application data is used for reading the first application data from the shared memory and storing the first application data into a second local memory if a second synchronous server monitors that a first data updating event exists in the shared memory.
It can be seen that, the first background server described in the embodiment of the present application obtains first application data of a user, where the first application data is data of the user using the main application; writing first application data to the shared memory and a first local memory; the first application data is used for reading the first application data from the shared memory by the second synchronous server if the second synchronous server monitors that the shared memory has the first data updating event, storing the first application data into the second local memory, and monitoring the data updating event in the shared memory in real time through the second synchronous server, so that the newly added data can be communicated in time, and the experience of using the associated application by a user is improved.
In one possible example, during the writing of the first application data to the shared memory by the first backend server, the program further includes instructions for:
adding a first update time and/or a first update source location at which the first application data is written to the shared memory to a shared memory data table in the shared memory.
In one possible example, the program further includes instructions for performing the steps of:
determining whether the first application data comprises keywords in a first keyword set corresponding to the first use region, and if so, shielding or not displaying data items comprising the keywords in the first application data; and if not, sending the first application data to a first client corresponding to the main application for display.
Referring to fig. 6 in keeping with the embodiments shown in fig. 1-5, fig. 6 is a schematic structural diagram of a second synchronization server provided in an embodiment of the present application, and as shown, the second synchronization server includes a processor, a memory, a communication interface, and one or more programs, where the one or more programs are stored in the memory and configured to be executed by the processor, and the programs include instructions for performing the following steps:
if the second synchronous server monitors that a first data updating event exists in the shared memory, reading the first application data from the shared memory, wherein the first application data is data of a main application used by a user, and the first application data is obtained by a first background server and is written into the shared memory and the first local memory; storing the first application data to the second local memory.
It can be seen that, in the second synchronization server described in the embodiment of the present application, if the second synchronization server monitors that a first data update event exists in the shared memory, the first application data is read from the shared memory, where the first application data is data of a main application used by a user, the first application data is obtained by the first background server, and is written into the shared memory and the data of the first local memory, the first application data is stored in the second local memory, and the second synchronization server monitors the data update event in the shared memory in real time, so that new data can be communicated in time, and the experience of the user in using the associated application is improved.
In one possible example, the program further includes instructions for performing the steps of:
writing the first application data to the shared memory; adding a second update time at which the first application data is written to the shared memory and/or a second update source location to a shared memory data table in the shared memory; the second update time and the second update source location are used for judging whether the first update source location is consistent with the second update source location if the first synchronization server monitors that a second data update event exists in the shared memory, and if so, the first synchronization server does not update the first application data any more; and if the first data updating event is not consistent with the second data updating event, the first synchronization server adds second application data corresponding to the second data updating event to a shared storage data table in the shared storage.
In one possible example, after the second synchronization server reads the first application data from the shared memory and before the first application data is stored in the second local memory, the program further includes instructions for performing the following steps:
carrying out the following processing on the first application data: processing by a general component; and/or, processing by a custom component; wherein the generic component is to perform the following: permission checking, and/or sensitive word filtering.
In one possible example, if the processing performed by the generic component includes sensitive word filtering, the program includes instructions for performing the following steps in the processing of the first application data by the generic component:
determining a first data type corresponding to the first application data; if the preset white list comprises the first data type, the first application data is reserved; otherwise, filtering the first application data.
In one possible example, if the processing performed by the generic component includes permission checking, in terms of the processing of the first application data by the generic component, the program includes instructions for performing the following steps:
determining a second data type corresponding to the first application data; determining an audit state corresponding to the second data type audited from the application; if the audit state is that the audit is passed, the authority verification is passed; otherwise, the check fails.
In one possible example, in said processing of said first application data by a generic component, the above program comprises instructions for performing the following steps:
determining whether the first application data comprises keywords in a second keyword set corresponding to the second use region, and if so, shielding or not displaying data items comprising the keywords in the first application data;
if not, acquiring first account information of the user, determining whether a preset blacklist corresponding to the second use region comprises the first account information, and if so, shielding or not displaying the first application data;
and if not, executing the operation of storing the first application data to the second local memory.
The above description has introduced the solution of the embodiment of the present application mainly from the perspective of the method-side implementation process. It is understood that the electronic device comprises corresponding hardware structures and/or software modules for performing the respective functions in order to realize the above-mentioned functions. Those of skill in the art will readily appreciate that the present application is capable of hardware or a combination of hardware and computer software implementing the various illustrative elements and algorithm steps described in connection with the embodiments provided herein. Whether a function is performed as hardware or computer software drives hardware depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.
In the embodiment of the present application, the electronic device may be divided into the functional units according to the method example, for example, each functional unit may be divided corresponding to each function, or two or more functions may be integrated into one processing unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit. It should be noted that the division of the unit in the embodiment of the present application is schematic, and is only a logic function division, and there may be another division manner in actual implementation.
The present application also provides a computer-readable storage medium, where the computer-readable storage medium stores a computer program for electronic data exchange, where the computer program makes a computer perform some or all of the steps described in the electronic device in the above method embodiments.
Embodiments of the present application also provide a computer program product, where the computer program product includes a non-transitory computer-readable storage medium storing a computer program, and the computer program is operable to cause a computer to perform some or all of the steps described in the electronic device in the above method. The computer program product may be a software installation package.
The steps of a method or algorithm described in the embodiments of the present application may be implemented in hardware, or may be implemented by a processor executing software instructions. The software instructions may be comprised of corresponding software modules that may be stored in Random Access Memory (RAM), flash Memory, Read Only Memory (ROM), Erasable Programmable ROM (EPROM), Electrically Erasable Programmable ROM (EEPROM), registers, a hard disk, a removable disk, a compact disc Read Only Memory (CD-ROM), or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor such the processor can read information from, and write information to, the storage medium. Of course, the storage medium may also be integral to the processor. The processor and the storage medium may reside in an ASIC. Additionally, the ASIC may reside in an access network device, a target network device, or a core network device. Of course, the processor and the storage medium may reside as discrete components in an access network device, a target network device, or a core network device.
Those skilled in the art will appreciate that in one or more of the examples described above, the functionality described in the embodiments of the present application may be implemented, in whole or in part, by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When loaded and executed on a computer, cause the processes or functions described in accordance with the embodiments of the application to occur, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored on a computer readable storage medium or transmitted from one computer readable storage medium to another, for example, from one website, computer, server, or data center to another website, computer, server, or data center via wire (e.g., coaxial cable, fiber optic, Digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device, such as a server, a data center, etc., that incorporates one or more of the available media. The usable medium may be a magnetic medium (e.g., floppy Disk, hard Disk, magnetic tape), an optical medium (e.g., Digital Video Disk (DVD)), or a semiconductor medium (e.g., Solid State Disk (SSD)), among others.
The above-mentioned embodiments are intended to illustrate the objects, technical solutions and advantages of the embodiments of the present application in further detail, and it should be understood that the above-mentioned embodiments are only specific embodiments of the present application, and are not intended to limit the scope of the embodiments of the present application, and any modifications, equivalent substitutions, improvements and the like made on the basis of the technical solutions of the embodiments of the present application should be included in the scope of the embodiments of the present application.

Claims (12)

1. A data intercommunication method is applied to a data intercommunication system, wherein the data intercommunication system comprises a master application, at least one slave application, a first background server corresponding to the master application, a first local storage, a second synchronous server corresponding to the slave application, a second local storage and a shared storage, and the method comprises the following steps:
the first background server acquires first application data of a user, wherein the first application data is data of the user using the main application; the first background server writes the first application data into the shared memory and the first local memory;
and if the second synchronous server monitors that a first data updating event exists in the shared memory, reading the first application data from the shared memory, and storing the first application data to the second local memory.
2. The method of claim 1, wherein during the writing of the first application data to the shared memory by the first backend server, the method further comprises:
the first background server adds a first update time and/or a first update source location at which the first application data is written to the shared memory to a shared memory data table in the shared memory.
3. The method of claim 2, wherein the data interworking system further comprises a first synchronization server corresponding to the primary application, and wherein when the second synchronization server stores the first application data in the second local storage, the method further comprises:
the second synchronization server writing the first application data to the shared memory; adding a second update time and/or a second update source location at which the first application data is written to the shared memory to a shared memory data table in the shared memory;
if the first synchronization server monitors that a second data updating event exists in the shared memory, whether the position of the first updating source is consistent with that of the second updating source is judged, and if so, the first synchronization server does not update the first application data any more; and if the first data updating event is not consistent with the second data updating event, the first synchronization server adds second application data corresponding to the second data updating event to a shared storage data table in the shared storage.
4. The method of any of claims 1-3, wherein after the second synchronization server reads the first application data from the shared memory, and before storing the first application data to the second local memory, the method further comprises:
the second synchronous server carries out the following processing on the first application data: processing by a general component; and/or, processing by a custom component; wherein the generic component is to perform the following: permission checking, and/or sensitive word filtering.
5. The method of claim 4, wherein if the processing performed by the generic component includes sensitive word filtering, the processing of the first application data by the generic component includes:
determining a first data type corresponding to the first application data;
if the preset white list comprises the first data type, reserving the first application data and reserving the first application data; otherwise, filtering the first application data.
6. The method according to claim 4, wherein if the processing performed by the generic component includes permission checking, the processing the first application data by the generic component includes:
determining a first data type corresponding to the first application data;
determining an audit state corresponding to the first data type audited from the application;
if the audit state is that the audit is passed, the authority verification is passed; otherwise, the check fails.
7. The method of claim 4, wherein the first application corresponds to a first region of use and the second application corresponds to a second region of use, the method further comprising:
the first background server determines whether the first application data comprises keywords in a first keyword set corresponding to the first use region, and if so, shields or does not display data items comprising the keywords in the first application data; if not, sending the first application data to a first client corresponding to the main application for display;
the processing the first application data by the common component includes:
the second synchronous server determines whether the first application data comprises keywords in a second keyword set corresponding to the second use region, and if so, shields or does not display data items comprising the keywords in the first application data;
if not, acquiring first account information of the user, determining whether a preset blacklist corresponding to the second use region comprises the first account information, and if so, shielding or not displaying the first application data;
and if not, executing the operation of storing the first application data to the second local memory.
8. The method according to any one of claims 5 to 7, wherein the data interworking system further includes a second background server corresponding to the slave application, and if the first application data is first account information of the user in the master application, the method further includes:
when the second background server receives an account login request aiming at the secondary application from a client, extracting login account information from the account login request;
and matching the login account information with the first account information, and if the matching is successful, sending feedback information that the account verification is passed to a second client corresponding to the slave application, wherein the feedback information is used for indicating the login operation authorization of the second client to the login account information.
9. The method of any of claims 5-7, wherein the data interworking system further comprises a second background server corresponding to the slave application, and if the first application data is a notification of the master application, the method further comprises:
and the second background server determines whether the slave application is in a login online state, and if so, sends the notification to a second client corresponding to the slave application, wherein the second client is used for displaying the notification.
10. The method of claims 5-7, wherein after the second synchronization server stores the first application data to the second local storage, the method further comprises:
the second background server acquires the first application data from the first local storage;
converting the display parameters of the first application data to obtain converted first application data;
and transmitting the converted first application data to a second client corresponding to the slave application, wherein the second client is used for displaying the converted first application data.
11. A data intercommunication system is characterized in that the data intercommunication system comprises a main application, at least one slave application, a first background server corresponding to the main application, a first local memory, a second synchronous server corresponding to the slave application, a second local memory and a shared memory, wherein,
the first background server is used for acquiring first application data of a user, wherein the first application data is data of the main application used by the user; the first background server writes the first application data into the shared memory and the first local memory;
the second synchronous server is used for reading the first application data from the shared memory and storing the first application data to the second local memory if monitoring that a first data updating event exists in the shared memory.
12. A computer-readable storage medium, characterized in that the computer-readable storage medium is used to store a computer program, which is executed by a processor to implement the method according to any of claims 1-10.
CN202011434544.0A 2020-12-10 2020-12-10 Data intercommunication method, system and storage medium Active CN112416629B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202011434544.0A CN112416629B (en) 2020-12-10 2020-12-10 Data intercommunication method, system and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202011434544.0A CN112416629B (en) 2020-12-10 2020-12-10 Data intercommunication method, system and storage medium

Publications (2)

Publication Number Publication Date
CN112416629A true CN112416629A (en) 2021-02-26
CN112416629B CN112416629B (en) 2023-07-25

Family

ID=74776451

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202011434544.0A Active CN112416629B (en) 2020-12-10 2020-12-10 Data intercommunication method, system and storage medium

Country Status (1)

Country Link
CN (1) CN112416629B (en)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20110296011A1 (en) * 2010-05-28 2011-12-01 Openpeak Inc. Shared heartbeat service for managed devices
CN103262057A (en) * 2010-10-01 2013-08-21 Flex Electronics ID Co.,Ltd. Cross-environment communication framework
CN104077265A (en) * 2013-03-25 2014-10-01 通用电气航空系统有限责任公司 Method of hybrid message passing with shared memory
CN104427105A (en) * 2013-08-28 2015-03-18 中兴通讯股份有限公司 Data synchronism method, device, and terminal in dual system
CN106021142A (en) * 2015-03-24 2016-10-12 国际商业机器公司 Method and system for sharing memory between guests

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20110296011A1 (en) * 2010-05-28 2011-12-01 Openpeak Inc. Shared heartbeat service for managed devices
CN103262057A (en) * 2010-10-01 2013-08-21 Flex Electronics ID Co.,Ltd. Cross-environment communication framework
CN104077265A (en) * 2013-03-25 2014-10-01 通用电气航空系统有限责任公司 Method of hybrid message passing with shared memory
CN104427105A (en) * 2013-08-28 2015-03-18 中兴通讯股份有限公司 Data synchronism method, device, and terminal in dual system
CN106021142A (en) * 2015-03-24 2016-10-12 国际商业机器公司 Method and system for sharing memory between guests

Also Published As

Publication number Publication date
CN112416629B (en) 2023-07-25

Similar Documents

Publication Publication Date Title
CN109981619A (en) Data capture method, device, medium and electronic equipment
CN111062024B (en) Application login method and device
CN106341234B (en) Authorization method and device
CN107026860B (en) Login authentication method, device and system
US11461752B2 (en) Wifi sharing system with mesh network functionality
US10853786B2 (en) Multi-factor identity authentication
CN105323237A (en) Authority delegation system, method and authentication server system
CN111177112A (en) Database blocking method and device based on operation and maintenance management system and electronic equipment
US9471896B2 (en) Memo synchronization system, mobile system, and method for synchronizing memo data
TWI839875B (en) Payment method, user terminal, device, equipment, system and medium
CN105119886A (en) Account ownership determination method and device
CN110798544B (en) Method and device for verifying validity of mobile terminal, terminal and storage medium
CN104065674A (en) Terminal device and information processing method
CN107229875A (en) Terminal method for secret protection and system
CN110198540A (en) Authentication method and device
CN102299945A (en) Gateway configuration page registration method, system thereof and portal certificate server
CN110366164B (en) Method for remotely controlling terminal, server, terminal and computing equipment
CN112488707A (en) Service flow supervision method and system
CN111901299A (en) Application authentication method and device, electronic equipment and storage medium
CN111709857A (en) House resource sharing method and device and electronic equipment
CN116305217A (en) Multi-tenant management method, device, computer equipment and storage medium
CN112416629A (en) Data intercommunication method, system and storage medium
US20100222022A1 (en) Communication method, communication system and access method to service provider base
US11800168B2 (en) Generic streaming media device configured as set top box
CN113794678A (en) Method and device compatible with multiple login modes and computer storage medium

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
GR01 Patent grant
GR01 Patent grant