CN111817887B - Data private SaaS system and working method thereof - Google Patents
Data private SaaS system and working method thereof Download PDFInfo
- Publication number
- CN111817887B CN111817887B CN202010604507.3A CN202010604507A CN111817887B CN 111817887 B CN111817887 B CN 111817887B CN 202010604507 A CN202010604507 A CN 202010604507A CN 111817887 B CN111817887 B CN 111817887B
- Authority
- CN
- China
- Prior art keywords
- saas
- container
- container platform
- software
- module
- 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.)
- Expired - Fee Related
Links
- 238000000034 method Methods 0.000 title claims abstract description 14
- 238000004891 communication Methods 0.000 claims description 18
- 238000012423 maintenance Methods 0.000 abstract description 3
- 238000010586 diagram Methods 0.000 description 2
- 238000013459 approach Methods 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0876—Aspects of the degree of configuration automation
- H04L41/0886—Fully automatic configuration
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0803—Configuration setting
- H04L41/0813—Configuration setting characterised by the conditions triggering a change of settings
- H04L41/082—Configuration setting characterised by the conditions triggering a change of settings the condition being updates or upgrades of network functionality
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0893—Assignment of logical groups to network elements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/20—Network architectures or network communication protocols for network security for managing network security; network security policies in general
-
- 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)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Security & Cryptography (AREA)
- Computer Hardware Design (AREA)
- Computing Systems (AREA)
- General Engineering & Computer Science (AREA)
- Automation & Control Theory (AREA)
- Information Transfer Between Computers (AREA)
- Stored Programmes (AREA)
Abstract
The invention belongs to the technical field of software service systems and discloses a data private software as a service (SaaS) system and a working method thereof. The invention solves the problems that the upgrading and maintenance are inconvenient after the proprietary deployment of the SaaS software in the prior art, and a user can not prevent the SaaS software server from returning data to a manufacturer.
Description
Technical Field
The invention belongs to the technical field of software service systems, and particularly relates to a data private SaaS system and a working method thereof.
Background
SaaS is an abbreviated name for Software-as-a-Service, meaning that Software is a Service, i.e., a Software Service is provided over a network. Traditionally, saaS vendors have deployed software on their own servers, and after a user orders from a vendor, the software services provided by the SaaS vendor are used over the network. The software is deployed on the vendor's server, and in most cases, the data is also stored at the SaaS vendor.
Under the scene that both software and data are in the SaaS manufacturer, there is a data security risk that user data are read, leaked and even tampered by the SaaS manufacturer. Although there are relevant legal regulations to restrict SaaS vendors, this data security risk remains a primary reason for users not being dared to use SaaS on core business and data.
In order to let users be confident about data privacy, some SaaS software provides a privately deployed solution, but this approach has the inconvenience of: the upgrading and maintenance of the SaaS software after privatization deployment are not convenient; the user cannot prevent the SaaS software server from returning data to the manufacturer.
Disclosure of Invention
The present invention aims to solve at least to some extent one of the above technical problems.
Therefore, the invention aims to provide a data proprietary SaaS system and a working method thereof, which solve the problems that the upgrading and maintenance are inconvenient after the proprietary deployment of the SaaS software in the prior art, and a user cannot prevent the SaaS software server from returning data to manufacturers.
The technical scheme adopted by the invention is as follows:
the SaaS system with private data comprises a SaaS container platform and a user private unit, wherein the SaaS container platform comprises a SaaS container platform control module, a SaaS container platform access module, a SaaS container platform external service module and a container pool, and the user private unit comprises a file module, a database and a message queue module;
the container pool is respectively in communication connection with the SaaS container platform control module, the SaaS container platform access module, the SaaS container platform external service module, the file module, the database and the message queue module, the external client is in communication connection with the SaaS container platform access module, and the SaaS container platform external service module is in communication connection with an external network server.
Further, the container pool comprises a plurality of SaaS software containers, and the SaaS software containers are respectively in communication connection with the file module, the database and the message queue module.
Further, the external client is in communication connection with the SaaS container platform access module through an API interface, and the SaaS container platform is in communication connection with an external network server through the API interface to the external service module.
Further, the API interface is an internal API interface and is located inside the SaaS container platform.
Further, the SaaS container platform is an independently built platform, wherein the container pool is used for storing SaaS software from a SaaS software manufacturer, and the user private unit is provided by a user and cannot be accessed by the SaaS software manufacturer.
A data private SaaS system working method comprises the following steps:
s1: receiving a user request sent by a client by using a SaaS container platform access module;
s2: user authentication is carried out on the user request by using the SaaS container platform, the user request is input into a container pool after the user authentication is passed, and the user request is input into a corresponding SaaS software container;
s3: performing read-write operation on the private unit of the user by using the SaaS software in the corresponding SaaS software container according to the user request;
s4: and judging whether the SaaS software sends an external service request or not, if so, using the SaaS container platform to send the external service request to an external network server, and ending the current task, otherwise, directly ending the current task.
Further, in step S4, the external service module sends the external service request to the external network server through a preset internal API interface by using the SaaS container platform.
Further, the internal API interface is authenticated by the user of the SaaS container platform.
Further, in step S2, the user request of the trusted SaaS software is directly input into the SaaS software container corresponding to the container pool.
Further, in step S4, the trusted SaaS software directly accesses a preset external API to send an external service request to the extranet server, where the external API is located outside the SaaS container platform and the interface information is on a preset whitelist of the SaaS container platform.
The beneficial effects of the invention are as follows:
the invention provides a data private SaaS system and a working method thereof, which can lead users to enjoy the convenience of deployment-free and maintenance-free, and simultaneously can also privately own data without worrying about the security risk of reading, leakage and even tampering the data by SaaS manufacturers, and concretely comprises the following steps:
1) The data belongs to the privacy of the user: the storage system is purchased by a user, naturally belongs to the privacy of the user, and the SaaS software can be read and written but cannot be directly accessed by a SaaS software manufacturer;
2) The data will not be acquired by SaaS software vendors: the SaaS software can be controlled to run through the network limitation and external service of the SaaS container platform, the data can not be returned to the SaaS software manufacturer, and the SaaS software manufacturer is forbidden to bypass a path for calling the API to acquire the data through user authentication;
3) The relative privatization deployment is more convenient: the user purchases the SaaS software on the SaaS container platform, the platform can be deployed automatically, and when the user selects to upgrade, the SaaS container platform can execute the processes of data backup, data upgrade, saaS software container upgrade and the like, so that the user and the SaaS software manufacturer do not need excessive intervention, and the SaaS software platform is more convenient.
Other advantageous effects of the present invention will be described in detail in the detailed description.
Drawings
In order to more clearly illustrate the embodiments of the invention or the technical solutions in the prior art, the drawings that are required in the embodiments or the description of the prior art will be briefly described, it being obvious that the drawings in the following description are only some embodiments of the invention, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
FIG. 1 is a block diagram of a system architecture of an embodiment of the present invention;
fig. 2 is a flow chart of the method of operation of the present invention.
Detailed Description
The invention will be further elucidated with reference to the drawings and to specific embodiments. The present invention is not limited to these examples, although they are described in order to assist understanding of the present invention. Functional details disclosed herein are merely for describing example embodiments of the invention. This invention may, however, be embodied in many alternate forms and should not be construed as limited to the embodiments set forth herein.
It is to be understood that the terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of example embodiments of the invention. The terms "comprises," "comprising," "includes," and/or "including," when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, and do not preclude the presence or addition of one or more other features, amounts, steps, operations, elements, components, and/or groups thereof.
It should be appreciated that in some alternative embodiments, the functions/acts noted may occur out of the order noted in the figures. For example, two figures shown in succession may in fact be executed substantially concurrently or the figures may sometimes be executed in the reverse order, depending upon the functionality/acts involved.
It should be understood that specific details are provided in the following description to provide a thorough understanding of the example embodiments. However, it will be understood by those of ordinary skill in the art that the example embodiments may be practiced without these specific details. For example, a system may be shown in block diagrams in order to avoid obscuring the examples with unnecessary detail. In other instances, well-known processes, structures, and techniques may be shown without unnecessary detail in order to avoid obscuring the example embodiments.
Example 1
As shown in fig. 1, the embodiment provides a data private SaaS system, which includes a SaaS container platform and a user private unit, wherein the SaaS container platform includes a SaaS container platform control module, a SaaS container platform access module, a SaaS container platform external service module and a container pool, and the user private unit includes a file module, a database and a message queue module;
the container pool is respectively in communication connection with the SaaS container platform control module, the SaaS container platform access module, the SaaS container platform external service module, the file module, the database and the message queue module, the external client is in communication connection with the SaaS container platform access module, and the SaaS container platform external service module is in communication connection with an external network server; the SaaS container platform is an independently built platform, wherein the container pool is used for storing SaaS software from SaaS software manufacturers, the user private unit is provided by a user, and the SaaS software manufacturers cannot access.
A SaaS container platform is built outside a SaaS manufacturer, after a user purchases SaaS software on the SaaS container platform, the SaaS container platform can automatically deploy and configure the SaaS software by using a container technology, as for a database, a cache, a file system and other storage systems used for storing or caching data of the SaaS software, the user can directly purchase on the SaaS container platform, can purchase on a cloud manufacturer, can also purchase the SaaS container platform by himself or can perform private deployment, and the storage systems are configured on the SaaS container platform, so that the SaaS software can normally operate, and the data private scheme of the invention is as follows:
1) The user's storage system is selected or built by the user, and SaaS manufacturer can not directly log in to access the user's storage system, and the invention uses the user private unit to realize the privatization of data such as files, databases, message queues and the like;
the SaaS software manufacturer can only upload the container mirror image of the SaaS software, the deployment position of the container is controlled by the SaaS container platform, the SaaS software manufacturer cannot log in the cloud server of the SaaS container platform, and can not access the database as the container naturally, the database is private to the user, and the user only needs to open the authority of the SaaS container platform, so that the SaaS software container can access the SaaS software to meet the requirement, the authority of the database does not need to be opened for the SaaS software manufacturer, the data privacy of the user can be protected as far as possible, and the SaaS software manufacturer is prevented from logging in the database;
2) The SaaS software can read and write the storage system, but the SaaS software cannot actively access the outside, and cannot actively leak data;
the SaaS software is arranged in a containerized way by the SaaS container platform, so that the containers can be controlled to only access the appointed addresses, such as the appointed database and the file system, and the SaaS software cannot transmit the data back to the manufacturer;
3) The SaaS software performs authentication on the external API, and besides the SaaS software itself, the SaaS container platform also performs identity authentication on a user, so that a SaaS manufacturer cannot steal user data in a manner of directly accessing the SaaS software API; the invention carries out user authentication on the input user request and the API interface;
when a user uses SaaS software, the Web end/client end/App end of the software generally interacts with the SaaS software server through an API, and there may be a vulnerability that a SaaS software vendor obtains data through the API of the SaaS software server, and in order to solve this problem, the SaaS container platform specifies that the API of the SaaS software server needs to be additionally authenticated by the SaaS container platform for user authentication.
Preferably, the container pool comprises a plurality of SaaS software containers, and the SaaS software containers are respectively in communication connection with the file module, the database and the message queue module.
Preferably, the external client is in communication connection with the SaaS container platform access module through an API interface, and the SaaS container platform is in communication connection with an external network server through the API interface to the external service module.
Preferably, the API interface is an internal API interface and is located inside the SaaS container platform.
The working method of the SaaS system with proprietary data, as shown in fig. 2, comprises the following steps:
s1: receiving a user request sent by a client by using a SaaS container platform access module;
s2: user authentication is carried out on the user request by using the SaaS container platform, the user request is input into a container pool after the user authentication is passed, and the user request is input into a corresponding SaaS software container;
s3: performing read-write operation on the private unit of the user by using the SaaS software in the corresponding SaaS software container according to the user request;
s4: judging whether the SaaS software sends an external service request or not, if so, using the SaaS container platform to send the external service request to an external network server by using an external service module, and ending the current task, otherwise, directly ending the current task;
and sending an external service request to an external network server by using the external service module through a preset internal API (application program interface) by using the SaaS container platform, wherein the internal API passes through user authentication of the SaaS container platform.
Preferably, in step S2, the user request of the trusted SaaS software is directly input into the SaaS software container corresponding to the container pool, without performing user authentication on the user request through the SaaS container platform.
Preferably, in step S3, the private user unit further includes a data storage module of a cache type in addition to the file module, the database and the message queue module.
Preferably, in step S4, the trusted SaaS software directly accesses a preset external API interface to send the external service request to the extranet server, without passing through the SaaS container platform to the external service module, where the external API interface is located outside the SaaS container platform and its IP or domain name is on a preset whitelist of the SaaS container platform.
It will be apparent to those skilled in the art that the modules or steps of the invention described above may be implemented in a general purpose computing device, they may be concentrated on a single computing device, or distributed across a network of computing devices, or they may alternatively be implemented in program code executable by computing devices, such that they may be stored in a memory device for execution by the computing devices, or they may be separately fabricated into individual integrated circuit modules, or multiple modules or steps within them may be fabricated into a single integrated circuit module. Thus, the present invention is not limited to any specific combination of hardware and software.
The embodiments described above are merely illustrative and may or may not be physically separate if reference is made to the unit being described as a separate component; if a component is referred to as being a unit, it may or may not be a physical unit, may be located in one place, or may be distributed over multiple network elements. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment. Those of ordinary skill in the art will understand and implement the present invention without undue burden.
The above embodiments are only for illustrating the technical solution of the present invention, and are not limiting; although the invention has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical scheme described in the foregoing embodiments can be modified or some of the technical features thereof can be replaced by equivalents. Such modifications and substitutions do not depart from the spirit and scope of the technical solutions of the embodiments of the present invention.
The invention is not limited to the alternative embodiments described above, but any person may derive other various forms of products in the light of the present invention. The above detailed description should not be construed as limiting the scope of the invention, which is defined in the claims and the description may be used to interpret the claims.
Claims (2)
1. A data proprietary SaaS system, characterized by: the system comprises a SaaS container platform and a user private unit, wherein the SaaS container platform comprises a SaaS container platform control module, a SaaS container platform access module, a SaaS container platform external service module and a container pool, and the user private unit comprises a file module, a database and a message queue module;
the container pool is respectively in communication connection with a SaaS container platform control module, a SaaS container platform access module, a SaaS container platform external service module, a file module, a database and a message queue module, an external client is in communication connection with the SaaS container platform access module, and the SaaS container platform external service module is in communication connection with an external network server;
the container pool comprises a plurality of SaaS software containers, and the SaaS software containers are respectively in communication connection with the file module, the database and the message queue module;
the external client is in communication connection with the SaaS container platform access module through an API interface, and the SaaS container platform external service module is in communication connection with an external network server through the API interface;
the API interface is an internal API interface and is positioned in the SaaS container platform;
the SaaS container platform is an independently built platform, wherein the container pool is used for storing SaaS software from SaaS software manufacturers, the user private unit is provided by a user, and the SaaS software manufacturers cannot access.
2. A data private SaaS system working method based on the data private SaaS system as claimed in claim 1, characterized in that: the method comprises the following steps:
s1: receiving a user request sent by a client by using a SaaS container platform access module;
s2: user authentication is carried out on the user request by using the SaaS container platform, the user request is input into a container pool after the user authentication is passed, and the user request is input into a corresponding SaaS software container;
directly inputting a user request of the trusted SaaS software into a SaaS software container corresponding to the container pool;
s3: performing read-write operation on the private unit of the user by using the SaaS software in the corresponding SaaS software container according to the user request;
s4: judging whether the SaaS software sends an external service request or not, if so, using the SaaS container platform to send the external service request to an external network server by using an external service module, and ending the current task, otherwise, directly ending the current task;
an external service module sends an external service request to an external network server through a preset internal API interface by using a SaaS container platform;
the internal API interface passes through user authentication of the SaaS container platform;
the trusted SaaS software directly accesses a preset external API interface to send an external service request to an external network server, the external API interface is positioned outside the SaaS container platform, and interface information is on a preset white list of the SaaS container platform.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010604507.3A CN111817887B (en) | 2020-06-29 | 2020-06-29 | Data private SaaS system and working method thereof |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010604507.3A CN111817887B (en) | 2020-06-29 | 2020-06-29 | Data private SaaS system and working method thereof |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111817887A CN111817887A (en) | 2020-10-23 |
| CN111817887B true CN111817887B (en) | 2023-06-23 |
Family
ID=72855299
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010604507.3A Expired - Fee Related CN111817887B (en) | 2020-06-29 | 2020-06-29 | Data private SaaS system and working method thereof |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111817887B (en) |
Families Citing this family (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115309440A (en) * | 2022-05-31 | 2022-11-08 | 广州仕邦人力资源有限公司 | RPA software generation method based on SaaS |
| CN117055905A (en) * | 2023-10-12 | 2023-11-14 | 北京谷器数据科技有限公司 | A method for rapid localized deployment of SaaS platforms |
| CN117806680B (en) * | 2023-12-29 | 2025-05-09 | 北京字跳网络技术有限公司 | Business data upgrade method, device, medium and electronic equipment for business application |
Family Cites Families (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8271615B2 (en) * | 2009-03-31 | 2012-09-18 | Cloud Connex, Llc | Centrally managing and monitoring software as a service (SaaS) applications |
| CN102135883B (en) * | 2011-03-14 | 2014-05-14 | 山东大学 | Software-as-a-service (SaaS) application generation and deployment supporting method and device |
| US9100345B2 (en) * | 2012-12-21 | 2015-08-04 | Software Ag Usa, Inc. | Systems and/or methods for supporting a generic framework for integration of on-premises and SaaS applications with security, service mediation, administrative, and/or monitoring capabilities |
| US9043458B2 (en) * | 2013-03-19 | 2015-05-26 | Cognizant Technology Solutions India Pvt. Ltd. | Framework for facilitating implementation of multi-tenant SaaS architecture |
| US9430672B2 (en) * | 2014-12-05 | 2016-08-30 | Cisco Technology, Inc. | Stack fusion architecture including distributed software clusters to enable software communication services |
| US9826100B2 (en) * | 2015-06-10 | 2017-11-21 | Flexera Software Llc | Usage tracking for software as a service (SaaS) applications |
| US10356076B2 (en) * | 2017-05-02 | 2019-07-16 | International Business Machines Corporation | Scalable authentication between heterogeneous services |
| US10521612B2 (en) * | 2017-06-21 | 2019-12-31 | Ca, Inc. | Hybrid on-premises/software-as-service applications |
| US20190141022A1 (en) * | 2017-11-07 | 2019-05-09 | International Business Machines Corporation | On-premise and off-premise communication |
| CN110826077A (en) * | 2018-08-10 | 2020-02-21 | 姚庆梅 | Technical architecture scheme for protecting SaaS (software as a service) user data security |
| US11153306B2 (en) * | 2018-11-08 | 2021-10-19 | Citrix Systems, Inc. | Systems and methods for secure SaaS redirection from native applications |
-
2020
- 2020-06-29 CN CN202010604507.3A patent/CN111817887B/en not_active Expired - Fee Related
Also Published As
| Publication number | Publication date |
|---|---|
| CN111817887A (en) | 2020-10-23 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11720393B2 (en) | Enforcing compliance rules using guest management components | |
| US10833949B2 (en) | Extension resource groups of provider network services | |
| CN101196974B (en) | Method and system for auto-configuratoin of software application program | |
| JP4411076B2 (en) | Localized read-only storage for distributing files across a network | |
| US20160359859A1 (en) | System For Secure File Access | |
| US9787718B2 (en) | Policy-based runtime control of a software application | |
| CN106127043B (en) | The method and apparatus that security sweep is carried out to data storage device from remote server | |
| US8935764B2 (en) | Network system for implementing a cloud platform | |
| US20070006325A1 (en) | Method, system and computer program for controlling access to resources in web applications | |
| CN111817887B (en) | Data private SaaS system and working method thereof | |
| US20170134436A1 (en) | System and method for preventing data loss using virtual machine wrapped applications | |
| US20200092332A1 (en) | Enabling webapp security through containerization | |
| US20140380406A1 (en) | Polymorphic virtual appliance rule set | |
| US10255092B2 (en) | Managed virtual machine deployment | |
| US20090228962A1 (en) | Access control and access tracking for remote front panel | |
| JP2022522678A (en) | Secure execution guest owner environment control | |
| US20210397700A1 (en) | Method and apparatus for isolating sensitive untrusted program code on mobile device | |
| EP4124978B1 (en) | Update of an operating system in a security element | |
| US20210406376A1 (en) | Firmware password management | |
| CN115499308B (en) | Distributed FTP container deployment method, device, terminal and storage medium | |
| CN113268450A (en) | File access method and device, electronic equipment and storage medium | |
| US9571564B2 (en) | Network system for implementing a cloud platform | |
| US11977753B2 (en) | BIOS NVRAM storage extension system and method for secure and seamless access for various boot architectures | |
| CN112464222A (en) | Security device, corresponding system, method and computer program product | |
| CN110008186A (en) | For file management method, device, terminal and the medium of more ftp data sources |
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 | ||
| TA01 | Transfer of patent application right | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20230425 Address after: 518000 a309-k24, Rongchao economic and Trade Center, No. 4028, Jintian Road, Fuzhong community, Lianhua street, Futian District, Shenzhen, Guangdong Province Applicant after: Shenzhen baoxingxing Technology Co.,Ltd. Address before: 2 / F, building 21, Guangqian Industrial Zone, No.165, longzhusan Road, Taoyuan Street, Nanshan District, Shenzhen, Guangdong 518000 Applicant before: Shenzhen pole Information Technology Co.,Ltd. |
|
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| CF01 | Termination of patent right due to non-payment of annual fee | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20230623 |