CN111240734A - Method and device for realizing interface with separated front end and back end - Google Patents
Method and device for realizing interface with separated front end and back end Download PDFInfo
- Publication number
- CN111240734A CN111240734A CN202010019143.2A CN202010019143A CN111240734A CN 111240734 A CN111240734 A CN 111240734A CN 202010019143 A CN202010019143 A CN 202010019143A CN 111240734 A CN111240734 A CN 111240734A
- Authority
- CN
- China
- Prior art keywords
- data
- interface
- user authentication
- request
- 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.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 39
- 238000001914 filtration Methods 0.000 claims abstract description 7
- 238000002347 injection Methods 0.000 claims description 7
- 239000007924 injection Substances 0.000 claims description 7
- 230000008569 process Effects 0.000 claims description 6
- 230000006870 function Effects 0.000 description 8
- 238000013461 design Methods 0.000 description 5
- 238000000926 separation method Methods 0.000 description 5
- 239000000243 solution Substances 0.000 description 5
- 238000011161 development Methods 0.000 description 3
- 238000012986 modification Methods 0.000 description 3
- 230000004048 modification Effects 0.000 description 3
- 238000012795 verification Methods 0.000 description 3
- 230000003287 optical effect Effects 0.000 description 2
- 239000008186 active pharmaceutical agent Substances 0.000 description 1
- 230000004075 alteration Effects 0.000 description 1
- 238000013459 approach Methods 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 238000004590 computer program Methods 0.000 description 1
- 239000012141 concentrate Substances 0.000 description 1
- 230000001419 dependent effect Effects 0.000 description 1
- 238000010586 diagram Methods 0.000 description 1
- 239000000835 fiber Substances 0.000 description 1
- 230000010354 integration Effects 0.000 description 1
- 235000012149 noodles Nutrition 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
- 230000004044 response Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
Abstract
The embodiment of the invention provides a method and a device for realizing an interface with separated front and back ends, wherein the method comprises the following steps: at the input end of the interface, the data type of each request parameter in the input request data is limited, and user authentication is set for the interface needing user authentication; and at the output end of the interface, adding a timestamp field and an interface version number field to the return data corresponding to the request data, performing data filtering on the return data by using a preset data layer data file, and if the data variable of the return data is the declared data variable in the data file, returning the return data. According to the technical scheme of the invention, the front end and the back end are clearly separated by a front-end and back-end separated mode, the front end uses an asynchronous request mode to access the back end interface, and the back end only needs to correctly provide interface data in a relation without needing to care about the code of the front end and more attentively output data.
Description
Technical Field
The invention relates to the field of data processing, in particular to a method and a device for realizing a front-end and back-end separated interface.
Background
Laravel is a compact and elegant PHP Web development Framework (PHP Web Framework). The code can be released from the messy code like noodles; the method can help you to construct a perfect network APP, and each line of code can be concise and rich in expressive force.
There is already a set of advanced PHP ActiveRecord implementations- -Eloquet ORM in Laravel. It can conveniently apply "constraints" to both parties in a relationship so that you have full control over the data and enjoy all the convenience of ActiveRecord. The Eloquet native supports all methods of query-builder in Fluent, while utilizing injection-dependent principles to allow integration of large third-party libraries.
However, many design modes need to be understood by using the framework, the learning cost is large, the whole framework becomes large due to too many dependency relationships, the response (QPS) becomes slow, the deployment is troublesome, and the separation project at the front end and the back end is too bulky.
Disclosure of Invention
The embodiment of the invention provides a method and a device for realizing a front-end and back-end separated interface.
In one aspect, an embodiment of the present invention provides a method for implementing an interface with a front end and a back end separated from each other, where the method includes:
at the input end of the interface, the data type of each request parameter in the input request data is limited, and user authentication is set for the interface needing user authentication;
and at the output end of the interface, adding a timestamp field and an interface version number field to the return data corresponding to the request data, performing data filtering on the return data by using a preset data layer data file, and if the data variable of the return data is the declared data variable in the data file, returning the return data.
On the other hand, an embodiment of the present invention provides an interface implementation apparatus with a front end and a back end separated, where the apparatus includes:
the input unit is arranged at the input end of the interface and used for limiting the data type of each request parameter in the input request data and setting user authentication for the interface needing the user authentication;
and the output unit is arranged at the output end of the interface and used for adding a timestamp field and an interface version number field to the return data corresponding to the request data, performing data filtering on the return data by using a preset data layer data file, and returning the return data if the data variable of the return data is a declared data variable in the data file.
The technical scheme has the following beneficial effects:
according to the technical scheme of the application, through the mode that the front end and the back end are separated, the front end and the back end are clearly separated, the front end uses an asynchronous request mode to access the back end interface, the back end only needs the interface data provided by the relation to be correct, the code of the front end does not need to be concerned, and the output data is more concentrated. Meanwhile, parameters input by each interface user can be subjected to data type constraint, and meanwhile, a verification switch is started aiming at an interface needing to be verified, so that the safety of the system is ensured; the output end is filtered through the data file, so that the safety and reliability of system output are ensured; the system is completely lightweight, extremely simple in deployment and extremely low in learning curve, and the QPS can be very high due to the lightness of the system.
Drawings
In order to more clearly illustrate the embodiments of the present invention 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 invention, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.
FIG. 1 is a flow chart of a front-end and back-end separated interface implementation method according to an embodiment of the present invention;
fig. 2 is a schematic structural diagram of an interface implementation apparatus with a front-end and a back-end separated according to an embodiment of the present invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the 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 invention.
Abbreviations and Key term definitions
API: (Application Programming Interface). Refers to the engagement of different components of a software system in order to provide the ability for applications and developers to access a set of routines based on certain software or hardware
The web framework: a Web application framework (Web application framework) is a development framework for supporting the development of dynamic websites, Web applications, and Web services. The type of which has two frameworks based on request and based on component
Protocol: rules, standards, or conventions established for conducting data exchanges in the network.
JSON: is a lightweight data exchange format.
JWT: JSON Web Token (JWT) is currently the most popular cross-domain authentication solution
As shown in fig. 1, the method for implementing an interface with a separated front end and a separated back end provided by the present invention includes:
101. and at the input end of the interface, limiting the data type of each request parameter in the input request data, and setting user authentication for the interface needing user authentication.
Preferably, a container for injection dependence is preset, a module needing to be loaded in the data input and output process is declared in the container, and when the module is loaded, route matching is carried out through a module path tracking method; namely, carrying out route matching according to a method of a controller/file class/module method; and the modules needing to be loaded comprise intermediate plug-ins which are loaded when preset conditions are met, and the intermediate plug-ins comprise a database and a log module.
The invention adopts an injection dependence mode to realize the loading of each module, the injection dependence needs a container, the module needing to be loaded is declared in the container, and the loading is carried out when the project is started. In consideration of the efficiency during loading, the invention does not adopt a regular mode to match the route, but has a head to start matching, and matches according to a controller/class/method, so compared with the regular mode, a large amount of time is saved, and the efficiency is improved.
It is further preferred that the data type of each request parameter is defined by setting a rule function and whether user authentication is required. For strong constraint of user input, each parameter can be constrained when a user requests, the rigidness of data input by the user is reduced due to weak constraint of data types of php, aiming at the constraint, the parameter input by the user of each interface can be constrained by the data types, meanwhile, an authentication switch is opened aiming at an interface needing to be authenticated, and the user can access the api only by inputting a correct token, so that the safety of the system is ensured. In each controller, the user may define a rule function, and the main function of the rule function is to define the restriction conditions in the controller, such as whether the received request method is POST or GET, whether the data type of the received request parameter is necessary, and whether the request needs to provide a verifiable token to ensure the identity of the user.
Further preferably, for the interface requiring user authentication, the user authentication is set by accessing the cross-domain authentication specification JWT system. The invention solves the problems of user state, project cross-region and the like in the back-end separation project by adopting a stateless token mode aiming at the front-end separation project and the back-end separation project.
102. And at the output end of the interface, adding a timestamp field and an interface version number field to the return data corresponding to the request data, performing data filtering on the return data by using a preset data layer data file, and if the data variable of the return data is the declared data variable in the data file, returning the return data.
The concept of data is added in the invention, the data required to be returned by the interface is filtered, and only the data variable stated in the data file is output, thereby ensuring the safety and reliability of system output.
Preferably, the return data is output and returned in a form of a Json character string. The user only needs to define the output state code and data, the output module automatically adds a time stamp, and contents such as api version number and the like are output in a Json character string mode.
Preferably, by setting a configuration module, in the configuration module, a user can configure various frame parameters.
As shown in fig. 2, corresponding to the above method, the interface implementation apparatus with separated front and back ends provided by the present invention includes:
an input unit 21, provided at an input end of the interface, for defining a data type of each request parameter in the input request data, and setting user authentication for an interface requiring user authentication;
and the output unit 22 is arranged at the output end of the interface, and is used for adding a timestamp field and an interface version number field to the return data corresponding to the request data, performing data filtering on the return data by using a preset data layer data file, and returning the return data if the data variable of the return data is a declared data variable in the data file.
The system further comprises a loading unit, a route matching unit and a route matching unit, wherein the loading unit is used for presetting a container for injection dependence, declaring a module needing to be loaded in the data input and output processes in the container, and carrying out route matching by a module path tracking method when the module is loaded;
and the modules needing to be loaded comprise intermediate plug-ins which are loaded when preset conditions are met, and the intermediate plug-ins comprise a database and a log module.
Further, the input unit is specifically configured to: and defining the data type of each request parameter and defining whether user authentication is required or not by setting a rule function.
Further, the input unit is specifically further configured to: for the interface needing user authentication, the JWT system is set up with user authentication by accessing the cross-domain authentication specification.
Further, the output unit is further configured to: and outputting the return data in a Json character string mode and returning.
Examples of applications are as follows:
the container module, in which we claim an instance, in which we bind the configuration module, the request module, the output module, the data class module and the database module, thus ensuring the operation of the above modules when the framework is operated:
rule making: for example, the method for setting index method acceptance is POST and GET, the required request parameters are name and password, the name is set to be int type and necessary, the password is set to be string type and necessary, the api interface 'authentication' is false, and verification is not required:
and (3) loading a middleware module, wherein each controller can load the middleware as required, for example, a default database is loaded as follows, and the loading as required ensures the efficiency of the framework when being started:
protected$middleware＝array('database'＝>array())；
obtaining the request value, because the set parameter is already set in the set rule, the parameter value can be obtained through the context only by knowing the parameter name in the method obtained by us, and if other parameters are needed to be obtained, the parameter value can be obtained through the $ this- > input- > data array:
$ name ═ this- > name; // obtaining the value of the parameter declared in the rerule
$ name ═ this- > input- > data [ 'name' ]; // obtaining other values
User authentication, if user selects authentication, authentication is performed by integrating JWT libraries
By adopting the framework, developers can concentrate on the design of the back-end api more, have more rigorous input parameters and more friendly output, integrate stateless token for user verification, better separate the mobile end from the front end and the back end, and the framework has a simple structure and extremely low learning curve.
Loading of each module is realized by injecting a dependency mode, the route loading efficiency is high, and a front-end and back-end separation project user identity authentication solution (JWT) is realized; the corresponding interface rule can be set according to the interface, so that the project is more rigorous and efficient; the framework is light and the learning curve is small.
It should be understood that the specific order or hierarchy of steps in the processes disclosed is an example of exemplary approaches. Based upon design preferences, it is understood that the specific order or hierarchy of steps in the processes may be rearranged without departing from the scope of the present disclosure. The accompanying method claims present elements of the various steps in a sample order, and are not intended to be limited to the specific order or hierarchy presented.
In the foregoing detailed description, various features are grouped together in a single embodiment for the purpose of streamlining the disclosure. This method of disclosure is not to be interpreted as reflecting an intention that the claimed embodiments of the subject matter require more features than are expressly recited in each claim. Rather, as the following claims reflect, invention lies in less than all features of a single disclosed embodiment. Thus, the following claims are hereby expressly incorporated into the detailed description, with each claim standing on its own as a separate preferred embodiment of the invention.
The previous description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the present invention. To those skilled in the art; various modifications to these embodiments will be readily apparent, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the disclosure. Thus, the present disclosure is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
What has been described above includes examples of one or more embodiments. It is, of course, not possible to describe every conceivable combination of components or methodologies for purposes of describing the aforementioned embodiments, but one of ordinary skill in the art may recognize that many further combinations and permutations of various embodiments are possible. Accordingly, the embodiments described herein are intended to embrace all such alterations, modifications and variations that fall within the scope of the appended claims. Furthermore, to the extent that the term "includes" is used in either the detailed description or the claims, such term is intended to be inclusive in a manner similar to the term "comprising" as "comprising" is interpreted when employed as a transitional word in a claim. Furthermore, any use of the term "or" in the specification of the claims is intended to mean a "non-exclusive or".
Those of skill in the art will further appreciate that the various illustrative logical blocks, units, and steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or combinations of both. To clearly illustrate the interchangeability of hardware and software, various illustrative components, elements, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends upon the particular application and design requirements of the overall system. 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 embodiments.
The various illustrative logical blocks, or elements, described in connection with the embodiments disclosed herein may be implemented or performed with a general purpose processor, a digital signal processor, an Application Specific Integrated Circuit (ASIC), a field programmable gate array or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, e.g., a digital signal processor and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a digital signal processor core, or any other similar configuration.
The steps of a method or algorithm described in connection with the embodiments disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module may be stored in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. For example, a storage medium may be coupled to the processor such the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium may be integral to the processor. The processor and the storage medium may reside in an ASIC, which may be located in a user terminal. In the alternative, the processor and the storage medium may reside in different components in a user terminal.
In one or more exemplary designs, the functions described above in connection with the embodiments of the invention may be implemented in hardware, software, firmware, or any combination of the three. If implemented in software, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Computer-readable media includes both computer storage media and communication media that facilitate transfer of a computer program from one place to another. Storage media may be any available media that can be accessed by a general purpose or special purpose computer. For example, such computer-readable media can include, but is not limited to, RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to carry or store program code in the form of instructions or data structures and which can be read by a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor. Additionally, any connection is properly termed a computer-readable medium, and, thus, is included if the software is transmitted from a website, server, or other remote source via a coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL), or wirelessly, e.g., infrared, radio, and microwave. Such discs (disk) and disks (disc) include compact disks, laser disks, optical disks, DVDs, floppy disks and blu-ray disks where disks usually reproduce data magnetically, while disks usually reproduce data optically with lasers. Combinations of the above may also be included in the computer-readable medium.
The above-mentioned embodiments are intended to illustrate the objects, technical solutions and advantages of the present invention in further detail, and it should be understood that the above-mentioned embodiments are merely exemplary embodiments of the present invention, and are not intended to limit the scope of the present invention, and any modifications, equivalent substitutions, improvements and the like made within the spirit and principle of the present invention should be included in the scope of the present invention.
Claims (10)
1. A front-end and back-end separated interface implementation method is characterized by comprising the following steps:
at the input end of the interface, the data type of each request parameter in the input request data is limited, and user authentication is set for the interface needing user authentication;
and at the output end of the interface, adding a timestamp field and an interface version number field to the return data corresponding to the request data, performing data filtering on the return data by using a preset data layer data file, and if the data variable of the return data is the declared data variable in the data file, returning the return data.
2. The method for implementing an interface with separated front and back ends according to claim 1, wherein a container with injection dependence is preset, and a module to be loaded in the data input and output process is declared in the container, wherein when the module is loaded, the routing matching is performed by a module path tracking method;
and the modules needing to be loaded comprise intermediate plug-ins which are loaded when preset conditions are met, and the intermediate plug-ins comprise a database and a log module.
3. The method as claimed in claim 2, wherein a rule function is set to define the data type of each request parameter and to define whether user authentication is required.
4. The method of claim 3, wherein the user authentication is set for the interface requiring user authentication by accessing a cross-domain authentication specification JWT system.
5. The method for implementing front-end and back-end separated interface as claimed in one of claims 1 to 4, wherein the return data is returned in the form of Json character string.
6. An interface implementation apparatus with separated front and back ends, the apparatus comprising:
the input unit is arranged at the input end of the interface and used for limiting the data type of each request parameter in the input request data and setting user authentication for the interface needing the user authentication;
and the output unit is arranged at the output end of the interface and used for adding a timestamp field and an interface version number field to the return data corresponding to the request data, performing data filtering on the return data by using a preset data layer data file, and returning the return data if the data variable of the return data is a declared data variable in the data file.
7. The device according to claim 6, further comprising a loading unit, configured to preset a container for injection dependency, and declare a module to be loaded in data input and output processes in the container, wherein when the module is loaded, the routing matching is performed by a module path tracing method;
and the modules needing to be loaded comprise intermediate plug-ins which are loaded when preset conditions are met, and the intermediate plug-ins comprise a database and a log module.
8. The device according to claim 7, wherein the input unit is specifically configured to: and defining the data type of each request parameter and defining whether user authentication is required or not by setting a rule function.
9. The device according to claim 8, wherein the input unit is further configured to: for the interface needing user authentication, the JWT system is set up with user authentication by accessing the cross-domain authentication specification.
10. The device as claimed in any one of claims 6 to 9, wherein the output unit is further configured to: and outputting the return data in a Json character string mode and returning.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010019143.2A CN111240734A (en) | 2020-01-08 | 2020-01-08 | Method and device for realizing interface with separated front end and back end |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010019143.2A CN111240734A (en) | 2020-01-08 | 2020-01-08 | Method and device for realizing interface with separated front end and back end |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111240734A true CN111240734A (en) | 2020-06-05 |
Family
ID=70877669
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010019143.2A Pending CN111240734A (en) | 2020-01-08 | 2020-01-08 | Method and device for realizing interface with separated front end and back end |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111240734A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112632513A (en) * | 2020-12-29 | 2021-04-09 | 光大兴陇信托有限责任公司 | Identity authentication implementation method based on front-end and back-end separation |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105681126A (en) * | 2015-12-30 | 2016-06-15 | 合一网络技术(北京)有限公司 | Automatic test method and system based on protocol interface |
| CN106155697A (en) * | 2016-07-30 | 2016-11-23 | 北京慧摩尔科技有限公司 | A kind of service-oriented Development Framework (YC Framework) |
| CN107071032A (en) * | 2017-04-20 | 2017-08-18 | 上海极链网络科技有限公司 | The framework NFBD developed in interdynamic video based on node streaming |
| US20180053401A1 (en) * | 2016-08-22 | 2018-02-22 | Rapidsos, Inc. | Predictive analytics for emergency detection and response management |
| CN110442326A (en) * | 2019-08-11 | 2019-11-12 | 西藏宁算科技集团有限公司 | A kind of method and its system simplifying separation permission control in front and back end based on Vue |
| CN110532019A (en) * | 2019-06-27 | 2019-12-03 | 北京大学 | A kind of method of software code fragment history retrospect |
-
2020
- 2020-01-08 CN CN202010019143.2A patent/CN111240734A/en active Pending
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105681126A (en) * | 2015-12-30 | 2016-06-15 | 合一网络技术(北京)有限公司 | Automatic test method and system based on protocol interface |
| CN106155697A (en) * | 2016-07-30 | 2016-11-23 | 北京慧摩尔科技有限公司 | A kind of service-oriented Development Framework (YC Framework) |
| US20180053401A1 (en) * | 2016-08-22 | 2018-02-22 | Rapidsos, Inc. | Predictive analytics for emergency detection and response management |
| CN107071032A (en) * | 2017-04-20 | 2017-08-18 | 上海极链网络科技有限公司 | The framework NFBD developed in interdynamic video based on node streaming |
| CN110532019A (en) * | 2019-06-27 | 2019-12-03 | 北京大学 | A kind of method of software code fragment history retrospect |
| CN110442326A (en) * | 2019-08-11 | 2019-11-12 | 西藏宁算科技集团有限公司 | A kind of method and its system simplifying separation permission control in front and back end based on Vue |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112632513A (en) * | 2020-12-29 | 2021-04-09 | 光大兴陇信托有限责任公司 | Identity authentication implementation method based on front-end and back-end separation |
| CN112632513B (en) * | 2020-12-29 | 2024-01-12 | 光大兴陇信托有限责任公司 | Front-end and back-end separation-based identity authentication implementation method |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108306877B (en) | NODE JS-based user identity information verification method and device and storage medium | |
| US20230328109A1 (en) | Data access policies | |
| JP2021511560A (en) | Methods, devices, and electronic devices for performing transactions based on the blockchain | |
| US10276168B2 (en) | Voiceprint verification method and device | |
| EP3694175B1 (en) | System and method for delegating authority through coupled devices | |
| CN108491475A (en) | Data rapid batch introduction method, electronic device and computer readable storage medium | |
| US20130305327A1 (en) | Method and apparatus to assist user input based on a mobile terminal browser | |
| CN104205721A (en) | A context-aware adaptive authentication method and apparatus | |
| US20160044490A1 (en) | Method and system for automatically switching subscriber mode through identifying imsi | |
| CN108965341A (en) | The method, apparatus and system of login authentication | |
| CN105993156B (en) | Server access verification method and device | |
| US20180063140A1 (en) | Configuration based client for oauth authorization with arbitrary services and applications | |
| CN111404695B (en) | Token request verification method and device | |
| CN111523102A (en) | Applet login method, device, equipment and computer readable storage medium | |
| CN111240734A (en) | Method and device for realizing interface with separated front end and back end | |
| US10270771B1 (en) | Mid-session live user authentication | |
| US11023565B2 (en) | System and protocol for integrating multiple service providers across various domains using a platform | |
| KR101944698B1 (en) | Method for auto login of single sign on using the login result of computer operating system, and computer readable recording medium applying the same | |
| WO2022033079A1 (en) | Pico base station configuration method and apparatus, and storage medium and electronic apparatus | |
| CN110912865A (en) | Security access control method, server and electronic equipment | |
| CN107484191A (en) | Communication control method and device, computer installation and readable storage medium storing program for executing | |
| CN103685259A (en) | Method and device for account logging in | |
| WO2015131680A1 (en) | Multi-card multi-standy communication terminal, method and device for network locking thereof, and computer storage medium | |
| CN116094814A (en) | VPN access method, device, electronic equipment and storage medium | |
| CN112788017B (en) | Security verification method, device, equipment and 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 | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20200605 |