CN114996040B - Service interface calling method and device - Google Patents
Service interface calling method and device Download PDFInfo
- Publication number
- CN114996040B CN114996040B CN202210929676.3A CN202210929676A CN114996040B CN 114996040 B CN114996040 B CN 114996040B CN 202210929676 A CN202210929676 A CN 202210929676A CN 114996040 B CN114996040 B CN 114996040B
- Authority
- CN
- China
- Prior art keywords
- corpus
- service interface
- parameter name
- interface
- request
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
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
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2209/00—Indexing scheme relating to G06F9/00
- G06F2209/54—Indexing scheme relating to G06F9/54
- G06F2209/549—Remote execution
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Telephonic Communication Services (AREA)
Abstract
The embodiment of the application discloses a service interface calling method and a device, wherein the method comprises the following steps: the service interface calling end receives the to-be-processed corpus content sent by the server and verifies the legality, and if the to-be-processed corpus content passes the legality verification, a corpus template is obtained from the to-be-processed corpus content; the method comprises the steps of obtaining a pre-stored corpus information list and corpus mapping relation, judging whether a corpus identifier and a corpus code corresponding to a corpus template exist in the corpus information list or not, if not, generating the corresponding corpus code, determining an interface parameter name, a corpus parameter name and an access address of a service interface to be called according to the content of the corpus to be processed, signing the interface parameter name and the corpus parameter name by using a preset signature mode to obtain a request signature value, generating an interface calling request according to the interface parameter name, the corpus parameter name, the access address and the request signature value, and calling the service interface to be called to receive a corpus processing result. The method greatly reduces the research and development workload of manufacturers when processing the corpora.
Description
Technical Field
The present application relates to the field of information security, and in particular, to a service interface calling method and apparatus.
Background
When carrying out online data circulation, can make data circulation information in time confirm through voice broadcast, effectively avoided the emergence of the condition such as hourglass receipts, wrong receipts.
Currently, there are two methods adopted by manufacturers when processing various types of corpus content (e.g., corpus generation, corpus push, corpus deletion, corpus broadcast, etc.): firstly, the processing of the material content is realized through self-research and development technology; secondly, different corpus contents are processed by docking a plurality of services, and different docking codes are developed according to the docked services; in any of the foregoing methods, research and development investment is required, and a large amount of research and development resources are occupied.
Therefore, how to implement corpus processing by using voice broadcast service to reduce the research and development investment of manufacturers becomes a technical problem to be solved urgently.
Disclosure of Invention
The embodiment of the application provides a service interface calling method and a device, and the technical scheme is as follows:
in a first aspect, an embodiment of the present application provides a service interface calling method, where the method includes:
step S1: the service interface calling end receives the to-be-processed corpus content sent by the server, carries out validity verification on the to-be-processed corpus content, acquires a corpus template from the to-be-processed corpus content if the to-be-processed corpus content passes the verification, and executes the step S2, otherwise, the step is finished;
step S2: the service interface calling end acquires a pre-stored corpus information list and a corpus mapping relation, wherein the corpus mapping relation is a one-to-one correspondence relation formed among a corpus template, a corpus identifier and a corpus code;
and step S3: the service interface calling end judges whether the corpus identifier and the corpus code corresponding to the acquired corpus template exist in the corpus information list or not according to the mapping relation between the corpus template and the corpus, if not, the corpus code corresponding to the acquired corpus template is generated, and step S4 is executed;
and step S4: the service interface calling end determines an interface parameter name, a corpus parameter name and an access address of a service interface to be called according to the corpus content to be processed;
step S5: the service interface calling end carries out signature processing on the interface parameter name and the corpus parameter name by using a preset signature mode to obtain a request signature value;
step S6: the service interface calling terminal generates an interface calling request according to the interface parameter name, the corpus parameter name, the access address and the request signature value;
step S7: the service interface calling end calls the service interface to be called based on the interface calling request and receives a corpus processing result returned by the service interface to be called aiming at the corpus content to be processed.
In a second aspect, an embodiment of the present application provides a service interface invoking device, where the device includes:
the corpus content verification module is used for receiving the corpus content to be processed sent by the server, verifying the legality of the corpus content to be processed, acquiring a corpus template from the corpus content to be processed if the verification is passed, and triggering the mapping relation acquisition module, otherwise, ending the mapping relation acquisition module;
the mapping relation obtaining module is used for obtaining a pre-stored corpus information list and a corpus mapping relation, wherein the corpus mapping relation is a one-to-one correspondence relation formed among a corpus template, a corpus identifier and a corpus code;
the list judging module is used for judging whether the corpus identifier and the corpus code corresponding to the obtained corpus template exist in the corpus information list according to the mapping relation between the corpus template and the corpus, if not, the corpus code corresponding to the obtained corpus template is generated, and the parameter name determining module is triggered;
the parameter name determining module is used for determining an interface parameter name, a corpus parameter name and an access address of a service interface to be called according to the corpus content to be processed;
the signature value acquisition module is used for carrying out signature processing on the interface parameter name and the corpus parameter name by using a preset signature mode to obtain a request signature value;
a calling request generating module, configured to generate an interface calling request according to the interface parameter name, the corpus parameter name, the access address, and the request signature value;
and the interface calling module is used for calling the service interface to be called based on the interface calling request and receiving the corpus processing result returned by the service interface to be called aiming at the corpus content to be processed.
In a third aspect, an embodiment of the present application provides a computer-readable storage medium, on which a computer program is stored, where the computer program, when executed by a processor, implements the steps of any one of the methods described above.
In a fourth aspect, an embodiment of the present application provides a service interface calling terminal, including a memory, a processor, and a computer program stored in the memory and executable on the processor, where the processor implements the steps of any one of the methods when executing the program.
The beneficial effects brought by the technical scheme provided by some embodiments of the application at least comprise:
by the service interface calling method, different interfaces of the service can be efficiently and quickly connected, and then the corpus is processed through the service, so that the research and development workload of a manufacturer in corpus processing is greatly reduced.
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 embodiments or the prior art descriptions will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present application, and other drawings can be obtained by those skilled in the art without creative efforts.
Fig. 1 is a schematic flowchart of a service interface calling method according to an embodiment of the present application;
fig. 2 is a schematic flowchart of a service interface calling method according to an embodiment of the present application;
fig. 3 is a schematic structural diagram of a service interface invoking device according to an embodiment of the present application.
Detailed Description
To make the objects, technical solutions and advantages of the present application more clear, embodiments of the present application will be described in further detail below with reference to the accompanying drawings.
When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the application, as detailed in the appended claims.
In the description of the present application, it is to be understood that the terms "first," "second," and the like are used for descriptive purposes only and are not to be construed as indicating or implying relative importance. The specific meaning of the above terms in the present application can be understood in a specific case by those of ordinary skill in the art. Further, in the description of the present application, "a plurality" means two or more unless otherwise specified. "and/or" describes the association relationship of the associated object, indicating that there may be three relationships, for example, a and/or B, which may indicate: a exists alone, A and B exist simultaneously, and B exists alone. The character "/" generally indicates that the former and latter associated objects are in an "or" relationship.
The service interface calling method provided by the embodiment of the present application will be described in detail below with reference to fig. 1 to fig. 2.
Fig. 1 is a schematic flowchart illustrating a service interface calling method according to an embodiment of the present application.
As shown in fig. 1, the method of the embodiment of the present application may include the steps of:
step S1: and the service interface calling end determines the interface parameter name, the corpus parameter name and the access address of the service interface to be called according to the corpus content to be processed.
In the present application, the corpus content to be processed includes, but is not limited to, creating corpus, pushing corpus, updating corpus, deleting corpus, broadcasting corpus, and the like.
The corpus refers to an audio file converted from characters.
Different language material contents to be processed respectively correspond to different service interfaces to be called, and the interface parameter names and the language material parameter names of the different service interfaces to be called are the same and different.
The name of the interface parameter includes, but is not limited to, a signature method, a signature random number, a signature algorithm version, a user key ID, a timestamp, a region where the service interface calling terminal is located, and the like.
For the corpus parameter name, when the corpus content to be processed is a created corpus, the corresponding corpus parameter name includes, but is not limited to, a corpus operation name (CreateSpeech), a product key, a corpus broadcast sound, a corpus type, a corpus text, and the like; when the corpus content to be processed is the pushed corpus, the updated corpus or the deleted corpus, the corresponding corpus parameter name includes but is not limited to the corpus operation name (pushSpeech/UpdateSpeech/deleteSpeech), the product key, the corpus identifier, and the like; when the corpus content to be processed is the acquired corpus list, the corresponding corpus parameter name includes but is not limited to a corpus operation name (querystechlist), a product key, and the like; when the corpus content to be processed is a combined broadcast corpus, the corresponding corpus parameter name includes, but is not limited to, a corpus operation name (spechbycombination), a product key, combined broadcast content, and the like; when the corpus content to be processed is corpus details under a query corpus push task, the corresponding corpus parameter name includes, but is not limited to, a corpus operation name (querystphushjobspech), a product key, a push task ID, and the like; when the corpus content to be processed is the broadcast corpus, the corresponding corpus parameter name includes, but is not limited to, a corpus operation name (Pub), a product key, a title (topic) subscribed by a service interface calling end, message content, and the like; the names of the corpus parameters of other corpus contents to be processed are not listed one by one here.
The access address is generated based on a region code of a service interface calling end, and the access address is, for example, iot.
Step S2: and the service interface calling terminal signs the interface parameter name and the corpus parameter name by using a preset signature mode to obtain a request signature value.
Taking creating corpus as an example, the request signature value is, for example:
cf192cca621ef52642894bea7dac4318a40caa24。
taking the pushed corpus as an example, the request signature value is, for example:
f5c9b9ad3f183b277f1320c0e2632e774dc36b68。
and step S3: and the service interface calling terminal generates an interface calling request according to the interface parameter name, the corpus parameter name, the access address and the request signature value.
The interface call request generated based on the request signature value instance of the corpus is, for example:
https://iot.cn-shanghai.cloudcs.com/ Version=2018-01-20
&Signature=cf192cca621ef52642894bea7dac4318a40caa24
&SignatureMethod=HMAC-SHA1
&SignatureNonce=15215528852396
&SignatureVersion=1.0
&AccessKeyId= LTAI5tD1GSFVRiJDN9oPq51R
&Timestamp=2022-04-20T12:00:00Z
&RegionId=cn-shanghai
&Action=CreateSpeech
&ProductKey=a1xwiZEE2vp
&Voice=Xiaoyun
&SpeechType=custom
&BizCode=ZFDZ
&SpeechRate=0
&Volume=50
& Text = success of data flow
&AudioFormat=MP3。
The interface call request generated based on the request signature value instance of the pushed corpus is, for example:
https://iot.ap-northeast-1.cloudcs.com/ Version=2018-01-20
&Signature=f5c9b9ad3f183b277f1320c0e2632e774dc36b68
&SignatureMethod=HMAC-SHA1
&SignatureNonce=15215528852396
&SignatureVersion=1.0
&AccessKeyId=LTAI5tD1GSFVRiJDN9oPq51R
&Timestamp=2022-04-20T12:00:00Z
&RegionId=ap-northeast-1
&Action=PushSpeech
&ProductKey=a1xwiZEE2vp
&SpeechCode=Md3ZiTL888K9llXDy7890。
and step S4: the service interface calling end calls the service interface to be called based on the interface calling request, and receives a corpus processing result returned by the service interface to be called aiming at the corpus content to be processed.
Specifically, the service interface to be called performs corresponding corpus processing according to the corpus parameter name transmitted from the interface to obtain a corpus processing result;
and returning the corpus processing result to the service interface calling end.
Taking creating a corpus as an example, a corpus processing result returned by the service interface to be called is, for example:
{
"RequestId": "QkI3MUU0NDMtNDQ0Ny00MDI0LUEwMDAtRURFMDk5MjI4OTFF",
"SpeechCode": "Md3ZiTL888K9llXDy7890",
"Success": true
}
wherein, requestId represents a request id; speechCode represents a corpus unique identification ID returned after the corpus is created; success indicates a request processing result.
After receiving the corpus identification, the method further comprises the following steps:
and the service interface calling end updates the corpus information list according to the generated corpus codes and the returned corpus identifications.
Taking the example of pushing the corpus, the corpus processing result returned by the service interface to be called is, for example:
{
"RequestId": "YzcyZjE5OTY1NmVjYzkyZWE1MWI4ODNmMDJjNzRjMmRjYjc3NjhkNw==",
"Success": true
}
the service interface calling method can efficiently and quickly connect different interfaces of the service, and then completes the processing of the corpus through the service, and the method greatly reduces the research and development workload of a manufacturer when processing the corpus.
Please refer to fig. 2, which is a flowchart illustrating a service interface invoking method according to an embodiment of the present disclosure.
As shown in fig. 2, the method of the embodiment of the present application may include the steps of:
step S11-1: and the service interface calling end receives the to-be-processed corpus content sent by the server, carries out validity verification on the to-be-processed corpus content, extracts the corpus template from the to-be-processed corpus content if the to-be-processed corpus content passes the verification, and executes the step S11-2, otherwise, the operation is finished.
A user scans a merchant code card through a held terminal (such as a mobile phone) to carry out data circulation and interact with a server, the server assembles the linguistic data content to be processed according to data circulation information sent by the user terminal, and a related interface is called to send the assembled linguistic data content to be processed to a service interface calling end.
Specifically, the service interface calling end acquires an application identifier and data to be checked from the corpus content to be processed, acquires a corresponding application key according to the application identifier, checks the data to be checked by using the application key, and extracts the corpus template from the corpus content to be processed if the check is successful.
The corpus content to be processed is, for example:
{
"appkey" : "9A0A8659F005D6984697E2CA0A9CF3B7",
"timestamp" :"20181221162001",
"method" : "push",
"devicesn" : "C01202112170000715",
"message" : "1234",
"push_template" : "1",
"nonce" : "dpRxkhjbauiclpKoqt",
"sign" : "1df9e58d88b52a568b79872b3ac54781122b2b91f87c33204c2ad38c486e57f3"
}
the data to be verified is, for example:
1df9e58d88b52a568b79872b3ac54781122b2b91f87c33204c2ad38c486e57f3。
step S11-2: the service interface calling end obtains a pre-stored corpus information list and a corpus mapping relation, wherein the corpus mapping relation is a one-to-one correspondence relation formed among a corpus template, a corpus identification and a corpus coding.
For example: the corpus template is '1', the corpus identification is 'Md 3ZiTL888K9llXDy 7890' and the corpus code is 'ZFDZ'.
The corpus information list is, for example:
[{
"text": success in data flow,
"speechCode": "Md3ZiTL888K9llXDy7890",
"bizCode": "ZFDZ"
},{
"text": a certain message data inflow,
"speechCode": "cf1e60c49b62d01b2cda5",
"bizCode": "MXSK"
}]
step S11-3: and the service interface calling end judges whether the corpus identifier and the corpus code corresponding to the acquired corpus template exist in the corpus information list or not according to the mapping relation between the corpus template and the corpus, if not, the service interface calling end generates the corpus code corresponding to the acquired corpus template and executes the step S11, and if so, executes the step S15.
And (4) the corpus identifier and the corpus code corresponding to the acquired corpus template do not exist in the corpus information list, which indicates that the related corpus information does not exist in the broadcasting equipment, and step S11 is executed.
Step S11: and the service interface calling end determines the interface parameter name, the corpus parameter name and the access address of the service interface to be called according to the corpus content to be processed.
Step S1 may be referred to in this step, and is not described herein again.
Step S12: and the service interface calling end carries out signature processing on the interface parameter name and the corpus parameter name by using a preset signature mode to obtain a request signature value.
Further, the method specifically comprises the following steps:
step S121: and the service interface calling terminal carries out sequencing processing on the interface parameter names and the corpus parameter names according to a preset sequencing rule, and carries out coding processing on the sequenced interface parameter names, the corpus parameter names, the values of the interface parameter names and the values of the corpus parameter names.
The preset ordering rule is specifically as follows: and sequencing the interface parameter names and the corpus parameter names according to the alphabetical order.
For example, the names of the interface parameters corresponding to the broadcast corpuses are as follows:
SignatureMethod、SignatureNonce、SignatureVersion、AccessKeyId、Timestamp、RegionId。
the corpus parameter names corresponding to the broadcast corpuses are as follows:
Action、ProductKey、TopicFullName、MessageContent。
sequencing the parameter names according to the letter sequence, wherein the sequencing result is as follows:
AccessKeyId、Action、MessageContent、ProductKey、RegionId、Timestamp、TopicFullName、SignatureMethod、SignatureNonce、SignatureVersion。
in detail, the service interface calling terminal performs coding processing on the ordered interface parameter name, corpus parameter name, value of the interface parameter name, and value of the corpus parameter name according to a first coding rule.
The first encoding rule is specifically URL encoding.
Step S122: and the service interface calling end carries out splicing processing on the coded interface parameter name, the corpus parameter name, the value of the interface parameter name and the value of the corpus parameter name to obtain the request signature data.
In detail, the service interface calling end splices the encoded interface parameter name, the corpus parameter name, the value of the interface parameter name and the value of the corpus parameter name according to a first splicing rule.
The first splicing rule is specifically as follows: the parameter names and corresponding values after the connection coding are used firstly, and then the parameter names after the connection coding are used.
The request signature data of the broadcast corpus obtained according to the first splicing rule is, for example:
AccessKeyId=LTAI5tD1GSFVRiJDN9oPq51R&Action=Pub&MessageContent=eyJ0ZXN0IjoidGFzayBwdWIgYnJvYWRjYXN0In0=&ProductKey=a1xwiZEE2vp&RegionId=cn-shanghai&Timestamp=2022-05-31T07:43:57Z&TopicFullName=/h25b7iIsxaF/${deviceName}/user/get&SignatureMethod=HMAC-SHA1&SignatureNonce=1521552885223&&SignatureVersion=1.0。
the names of the corpus parameters of different to-be-processed corpus contents are different, and the generation process of the request signature data of the different to-be-processed corpus contents is not further elaborated here.
Step S123: and the service interface calling end acquires an access key of the service interface to be called from the internal storage, and signs the request signature data by using the access key to generate a request signature value.
The access key is for example:
vDvo9PF7T8uO5Yz/wN46PT5dUCA=。
in detail, the signing processing of the request signature data by using the access key specifically includes:
encrypting the request signature data by using the access key to obtain an encryption result;
and coding the encryption result according to a second coding rule to generate a request signature value.
The second encoding rule is specifically Base64 encoding.
Based on the above example, signing the request signature data of the broadcast corpus, and the generated request signature value is: 05a57d27de8b1c80f6f0a202146aa1b9f641ec9a.
Step S13: and the service interface calling end carries out splicing processing on the interface parameter name, the corpus parameter name, the access address and the request signature value to generate an interface calling request.
In detail, the service interface calling terminal splices the interface parameter name, the corpus parameter name, the access address and the request signature value according to a second splicing rule.
Specifically, the interface call request for the broadcast corpus generated by the second concatenation rule concatenation processing is, for example:
https://iot.cn-shanghai.cloudcs.com/ Version=2018-01-20
&Signature=05a57d27de8b1c80f6f0a202146aa1b9f641ec9a
&SignatureMethod=HMAC-SHA1
&SignatureNonce=1521552885223
&SignatureVersion=1.0
&AccessKeyId= LTAI5tD1GSFVRiJDN9oPq51R
&Timestamp=2022-04-20T12:00:00Z
&RegionId=cn-shanghai
&Action=Pub
&ProductKey=a1xwiZEE2vp
&TopicFullName=/h25b7iIsxaF/${deviceName}/user/get
&MessageContent=eyJ0ZXN0IjoidGFzayBwdWIgYnJvYWRjYXN0In0=。
in other embodiments, when the to-be-processed corpus content generated by the service interface calling end is the obtained corpus list, the interface calling request is, for example:
https://iot.cn-shanghai.cloudcs.com/ Version=2018-01-20
&Signature= f5c9b9ad3f183b277f1320c0e2632e774dc36b68
&SignatureMethod=HMAC-SHA1
&SignatureNonce=15215528852396
&SignatureVersion=1.0
&AccessKeyId= LTAI5tD1GSFVRiJDN9oPq51R
&Timestamp=2022-04-20T12:00:00Z
&RegionId=cn-shanghai
&Action=QuerySpeechList
&ProductKey=a1xwiZEE2vp。
in other embodiments, when the to-be-processed corpus content generated by the service interface calling end is the deleted corpus, the interface calling request is, for example:
https://iot.cn-shanghai.cloudcs.com/ Version=2018-01-20
&Signature=2ba371fa2bacb15b66edd2cdbf10db4b28bfb837
&SignatureMethod=HMAC-SHA1
&SignatureNonce=15215528852396
&SignatureVersion=1.0
&AccessKeyId= LTAI5tD1GSFVRiJDN9oPq51R
&Timestamp=2022-04-20T12:00:00Z
&RegionId=cn-shanghai
&Action=DeleteSpeech
&ProductKey=a1xwiZEE2vp
&SpeechId=Md3ZiTL888K9llXDy7890。
in other embodiments, when the to-be-processed corpus content generated by the service interface calling end is the update corpus, the interface calling request is, for example:
https://iot.cn-shanghai.cloudcs.com/ Version=2018-01-20
&Signature=8edf22595a3a89623f1bc875b17714d425c30f1c
&SignatureMethod=HMAC-SHA1
&SignatureNonce=15215528852562
&SignatureVersion=1.0
&AccessKeyId= LTAI5tD1GSFVRiJDN9oPq51R
&Timestamp=2022-04-20T12:00:00Z
&RegionId=cn-shanghai
&Action=UpdateSpeech
&ProductKey=a1xwiZEE2vp
&SpeechCode=Md3ZiTL888K9llXDy7890。
in addition to the above example of interface call requests for a plurality of specific linguistic data contents to be processed, the linguistic data contents to be processed may also be a linguistic data combination replayed, linguistic data deleted in batch, repeated broadcast stopped, and the like, and here, the interface call request generation process for each linguistic data content to be processed is not enumerated one by one.
Step S14: the service interface calling end calls the service interface to be called based on the interface calling request, and receives a corpus processing result returned by the service interface to be called aiming at the corpus content to be processed.
Step S14 specifically includes:
step S141: the service interface calling end calls the service interface to be called based on the interface calling request;
step S142: and the service interface to be called performs corresponding corpus processing according to the corpus parameter name transmitted from the interface, obtains a corpus processing result and returns the corpus processing result.
And the service interface calling end extracts the corpus identification from the corpus processing result, establishes a corresponding relation among the acquired corpus template, the generated corpus code and the extracted corpus identification and stores the corresponding relation.
Taking the corpus content to be processed as an example of obtaining the corpus list, the corpus processing result returned by the service interface to be called is, for example:
{
"RequestId": "66FF51D3-4de-49F1-B1A2-2c367",
"Data": {
"Total": 1,
"AudioFormat":"MP3",
"Voice": "Xiaoyun",
"SpeechList": [{
text that data flow is successful,
"SpeechCode": "Md3ZiTL888K9llXDy7890",
"BizCode": "ZFDZ"
}]
},
"Success": true
}
wherein, requestId represents a request ID; data represents a returned corpus list; total represents the Total number of the linguistic data returned by the query; audioFormat denotes an audio format; voice represents a corpus broadcast sound; speechList represents a corpus list; speechCode represents corpus identification; bizCode represents corpus coding; text represents a corpus Text; success indicates a request processing result.
In addition, the corpus encoding given in the corpus processing result is only an illustrative example, and in other embodiments, the corpus encoding may also be ylsddz, SKCG, or the like.
Taking the corpus content to be processed as the deleted corpus, the corpus processing result returned by the service interface to be called is, for example:
{
"RequestId": "Mjg2NWIzNTQyODY4YjgyNjIyMGQ3MWM0ODYzYmEwM2EzNTFmYTE3NA==",
"Success": true
}
taking the corpus content to be processed as the updated corpus, the corpus processing result returned by the service interface to be called is, for example:
{
"RequestId": "MDUzM2IzZWZmY2RmN2JjN2NhN2Y5ZWY2YzY1NDM3Y2U2YTUyOTlkZg==",
"Success": true
}
in addition to the above-mentioned results of processing a plurality of specific corpus contents to be processed, for other corpus contents to be processed (e.g. replaying a previous corpus combination, deleting corpora in batch, stopping replaying repeatedly, etc.), no response examples are listed here.
The method further comprises the following steps: and the service interface calling end responds to the server according to the return result of the service interface to be called.
In a possible embodiment, after step S14, the method further includes:
if the service interface calling end does not receive the corpus processing result returned by the service interface to be called within the first preset time, continuing to call the service interface to be called based on the interface calling request according to the preset interval time until the service interface calling end receives the corpus processing result returned by the service interface to be called.
The first preset time is, for example, 3s, 5s, etc., and the predetermined interval time is, for example, 5s, 10s, etc.
After continuing to call the service interface to be called based on the interface call request at the preset interval, the method may further include:
and if the corpus processing result returned by the service interface to be called is not received within second preset time, regenerating the interface calling request and calling the service interface to be called based on the regenerated interface calling request, wherein the second preset time is longer than the first preset time.
The second preset time is, for example, 20s, 30s, etc.
In a possible embodiment, after step S141, the method further includes:
step S142': and the service interface calling end receives error information returned by the service interface to be called and positions the reason for calling the error by the interface according to the error information.
Step S15: and the service interface calling end generates a corpus pushing request according to the corpus content to be processed and an internally stored device key, and sends the corpus pushing request to the broadcasting device.
And when the corpus identifier and the corpus code corresponding to the corpus template exist in the corpus information list, indicating that the broadcasting equipment stores related corpus information.
The device key is, for example: fd3678bac94205c272df56e3e73ef71b.
The corpus pushing request is, for example:
{
"pushId":"20190221095350622453353"，
"params":{
"acoustics":"Xiaoyu",
"context": data inflow 1234",
"msg_type":"4",
"speechs":["ZFDZ","{$1234}"],
},
"sign":"1751a76f009791a15429de902bb5413950c3da0657d5a688a9f6df3938a35f144079a4c81ef4262308973993a2ac157acf1e60c49b62d02a0138fd8698c2e5f97290fe5f1b377c57711ceff3682b8ae84cc391cf9f99e8b29e444f71c90c0d5446f929f371565135a75f199af60a6fbc94f489e1a34099b0e81b5e987de6e8360e90055a8a71665cd9f277b307cc5a4ffb6c51fd3b1f411f2cf01a31f31b2408324b74a3f9c4d5cf6fef448b776bbe695c36bc6c8fde05abb1f03fdb2cda5d3615b27c6e3938a5b82efb2dce0971330beb02a842a96785fc59ce0c080f9c615f1bd467a75c49aaeca2f4dab947de640dfd0f546b39e164d3c728b232861cda0a"
}
the service interface calling method can efficiently and quickly connect different interfaces of the service, and then completes the processing of the corpus through the service, and the method greatly reduces the research and development workload of a manufacturer when processing the corpus.
The following are embodiments of the apparatus of the present application that may be used to perform embodiments of the method of the present application. For details which are not disclosed in the embodiments of the apparatus of the present application, reference is made to the embodiments of the method of the present application.
Fig. 3 is a schematic structural diagram of a service interface invoking device according to an exemplary embodiment of the present application. The service interface calling device in the embodiment of the application comprises:
the corpus content verification module is used for receiving the to-be-processed corpus content sent by the server, verifying the legality of the to-be-processed corpus content, acquiring a corpus template from the to-be-processed corpus content if the to-be-processed corpus content passes verification, triggering the mapping relation acquisition module, and otherwise, ending the mapping relation acquisition module;
the mapping relation acquisition module is used for acquiring a pre-stored corpus information list and a corpus mapping relation, wherein the corpus mapping relation is a one-to-one correspondence relation formed among a corpus template, a corpus identifier and a corpus code;
the list judgment module is used for judging whether the corpus identifier and the corpus code corresponding to the obtained corpus template exist in the corpus information list according to the mapping relation between the corpus template and the corpus, if not, the corpus code corresponding to the obtained corpus template is generated, and the parameter name determination module is triggered;
the parameter name determining module is used for determining an interface parameter name, a corpus parameter name and an access address of a service interface to be called according to the corpus content to be processed;
the signature value acquisition module is used for carrying out signature processing on the interface parameter name and the corpus parameter name by using a preset signature mode to obtain a request signature value;
a call request generation module, configured to generate an interface call request according to the interface parameter name, the corpus parameter name, the access address, and the request signature value;
and the interface calling module is used for calling the service interface to be called based on the interface calling request and receiving a corpus processing result returned by the service interface to be called aiming at the corpus content to be processed.
In an optional embodiment, the signature value obtaining module is specifically configured to:
sequencing the interface parameter names and the corpus parameter names according to a preset sequencing rule, and coding the sequenced interface parameter names, the corpus parameter names, the values of the interface parameter names and the values of the corpus parameter names;
splicing the encoded interface parameter name, the corpus parameter name, the value of the interface parameter name and the value of the corpus parameter name to obtain request signature data;
and acquiring an access key of the service interface to be called from an internal storage, and signing the request signature data by using the access key to generate a request signature value.
In an optional embodiment, the signing the request signature data with the access key to generate a request signature value includes:
encrypting the request signature data by using the access key to obtain an encryption result;
and coding the encryption result to generate a request signature value.
The device further comprises:
a corpus identifier extracting module, configured to extract a corpus identifier from the corpus processing result;
and the corresponding relation establishing module is used for establishing and storing the corresponding relation among the acquired corpus template, the generated corpus code and the extracted corpus identification.
In an optional embodiment, the apparatus further comprises:
and the push request generation module is used for generating a corpus push request according to the corpus content to be processed and an internally stored device key, and sending the corpus push request to the broadcasting device.
In an optional embodiment, the invocation request generating module is specifically configured to:
and splicing the interface parameter name, the corpus parameter name, the access address and the request signature value to generate an interface calling request.
In an optional embodiment, the interface calling module is specifically configured to:
calling the service interface to be called based on the interface calling request:
performing corresponding corpus processing according to the input corpus parameter name to obtain a corpus processing result;
and returning the corpus processing result to the service interface calling end.
In an optional embodiment, the interface calling module is further configured to:
if the corpus processing result returned by the service interface to be called is not received within the first preset time, continuing to call the service interface to be called based on the interface calling request according to the preset interval time until the service interface calling end receives the corpus processing result returned by the service interface to be called.
In an optional embodiment, the interface calling module is further configured to:
and if the corpus processing result returned by the service interface to be called is not received within second preset time, regenerating an interface calling request and calling the service interface to be called based on the regenerated interface calling request, wherein the second preset time is longer than the first preset time.
In an optional embodiment, the interface calling module is further configured to:
calling the service interface to be called based on the interface calling request;
and receiving error information returned by the service interface to be called, and positioning the reason for calling the error by the interface according to the error information.
It should be noted that, when the service interface calling apparatus provided in the foregoing embodiment executes the service interface calling method, only the division of the functional modules is illustrated, and in practical applications, the functions may be allocated to different functional modules according to needs, that is, the internal structure of the device may be divided into different functional modules to complete all or part of the functions described above. In addition, the service interface calling device and the service interface calling method provided by the above embodiments belong to the same concept, and details of implementation processes thereof are referred to as method embodiments, which are not described herein again.
The above-mentioned serial numbers of the embodiments of the present application are merely for description and do not represent the merits of the embodiments.
Through the service interface calling device that this application provided, can high-efficient, swiftly dock the different interfaces of service, accomplish the processing to the corpus through the service then, device greatly reduced the research and development work load of firm when handling the corpus.
The embodiments of the present application also provide a computer-readable storage medium, on which a computer program is stored, and the computer program is executed by a processor to implement the steps of the method of any one of the foregoing embodiments. The computer-readable storage medium may include, but is not limited to, any type of disk including floppy disks, optical disks, DVDs, CD-ROMs, microdrive, and magneto-optical disks, ROMs, RAMs, EPROMs, EEPROMs, DRAMs, VRAMs, flash memory devices, magnetic or optical cards, nano-devices (including molecular memory ICs), or any type of media or device suitable for storing instructions and/or data.
The embodiment of the present application further provides a service interface calling end, which includes a memory, a processor, and a computer program that is stored in the memory and can be run on the processor, and when the processor executes the program, the steps of the method according to any of the above embodiments are implemented.
The embodiment of the application provides a service interface calling terminal, which comprises: a processor and a memory.
In this embodiment, the processor is a control center of the computer device, and may be a processor of an entity machine or a processor of a virtual machine. The processor may include one or more processing cores, such as a 4-core processor, an 8-core processor, and so forth. The processor may be implemented in at least one hardware form of DSP (Digital Signal Processing), FPGA (Field-Programmable Gate Array), PLA (Programmable Logic Array). The processor may also include a main processor and a coprocessor, where the main processor is a processor for Processing data in an awake state, and is also called a Central Processing Unit (CPU); a coprocessor is a low power processor for processing data in a standby state.
The memory may include one or more computer-readable storage media, which may be non-transitory. The memory may also include high speed random access memory, as well as non-volatile memory, such as one or more magnetic disk storage devices, flash memory storage devices. In some embodiments of the present application, a non-transitory computer readable storage medium in a memory is used to store at least one instruction for execution by a processor to implement a method in embodiments of the present application.
In some embodiments, the service interface calling end further includes: a peripheral interface and at least one peripheral. The processor, memory and peripheral interface may be connected by bus or signal lines. Each peripheral may be connected to the peripheral interface via a bus, signal line, or circuit board. Specifically, the peripheral device includes: at least one of a display screen, a camera, and an audio circuit.
The peripheral interface may be used to connect at least one peripheral associated with an I/O (Input/Output) to the processor and the memory. In some embodiments of the present application, the processor, memory, and peripheral interface are integrated on the same chip or circuit board; in some other embodiments of the present application, any one or both of the processor, the memory, and the peripheral interface may be implemented on separate chips or circuit boards. The embodiment of the present application is not particularly limited to this.
The display screen is used to display a UI (User Interface). The UI may include graphics, text, icons, video, and any combination thereof. When the display screen is a touch display screen, the display screen also has the ability to capture touch signals on or over the surface of the display screen. The touch signal may be input to a processor as a control signal for processing. In this case, the display screen may also be used to provide virtual buttons and/or a virtual keyboard, also referred to as soft buttons and/or a soft keyboard. In some embodiments of the present application, the number of the display screens may be one, and the display screens are disposed on a front panel of the service interface calling end; in other embodiments of the present application, the number of the display screens may be at least two, and the at least two display screens are respectively disposed on different surfaces of the service interface calling end or are in a folding design; in still other embodiments of the present application, the display screen may be a flexible display screen disposed on a curved surface or a folded surface of the calling end of the service interface. Even, the display screen can be arranged in a non-rectangular irregular figure, namely a special-shaped screen. The Display screen can be made of LCD (Liquid Crystal Display), OLED (Organic Light-Emitting Diode) and other materials.
The camera is used for collecting images or videos. Optionally, the camera comprises a front camera and a rear camera. Generally, the front camera is arranged on the front panel of the client, and the rear camera is arranged on the back of the client. In some embodiments, the number of the rear cameras is at least two, and each rear camera is any one of a main camera, a depth-of-field camera, a wide-angle camera and a telephoto camera, so that the main camera and the depth-of-field camera are fused to realize a background blurring function, and the main camera and the wide-angle camera are fused to realize panoramic shooting and VR (Virtual Reality) shooting functions or other fusion shooting functions. In some embodiments of the present application, the camera may further include a flash. The flash lamp can be a monochrome temperature flash lamp or a bicolor temperature flash lamp. The double-color-temperature flash lamp is a combination of a warm-light flash lamp and a cold-light flash lamp, and can be used for light compensation at different color temperatures.
The audio circuitry may include a microphone and a speaker. The microphone is used for collecting sound waves of a user and the environment, converting the sound waves into electric signals and inputting the electric signals to the processor for processing. For the purpose of stereo sound collection or noise reduction, a plurality of microphones can be arranged at different positions of the calling end of the service interface respectively. The microphone may also be an array microphone or an omni-directional acquisition microphone.
The power supply is used for supplying power to each component in the service interface calling end. The power source may be alternating current, direct current, disposable or rechargeable. When the power source includes a rechargeable battery, the rechargeable battery may be a wired rechargeable battery or a wireless rechargeable battery. The wired rechargeable battery is a battery charged through a wired line, and the wireless rechargeable battery is a battery charged through a wireless coil. The rechargeable battery may also be used to support fast charge technology.
The structural block diagram of the client shown in the embodiment of the present application does not constitute a limitation on the service interface calling side, and the service interface calling side may include more or less components than those shown in the figure, or combine some components, or adopt different component arrangements.
In this application, the terms "first," "second," and the like are used for descriptive purposes only and are not to be construed as indicating or implying a relative importance or order; the term "plurality" means two or more unless explicitly defined otherwise. The terms "mounted," "connected," "fixed," and the like are to be construed broadly, and for example, "connected" may be a fixed connection, a removable connection, or an integral connection; "coupled" may be direct or indirect through an intermediary. The specific meaning of the above terms in the present application can be understood by those of ordinary skill in the art as appropriate.
In the description of the present application, it should be understood that the terms "upper", "lower", and the like indicate orientations or positional relationships based on orientations or positional relationships shown in the drawings, and are only for convenience in describing the present application and simplifying the description, but do not indicate or imply that the referred device or unit must have a specific direction, be configured and operated in a specific orientation, and thus, should not be construed as limiting the present application.
The above description is only for the specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily think of the changes or substitutions within the technical scope of the present application, and shall be covered by the scope of the present application. Accordingly, all equivalent changes which come within the meaning and range of equivalency of the claims are to be embraced within their scope.
Claims (13)
1. A service interface calling method, the method comprising:
step S1: the service interface calling end receives the to-be-processed corpus content sent by the server, carries out validity verification on the to-be-processed corpus content, acquires a corpus template from the to-be-processed corpus content if the to-be-processed corpus content passes the verification, and executes the step S2, otherwise, the step is finished;
step S2: the service interface calling end acquires a pre-stored corpus information list and a corpus mapping relation, wherein the corpus mapping relation is a one-to-one corresponding relation formed among a corpus template, a corpus identifier and a corpus code;
and step S3: the service interface calling end judges whether the corpus identifier and the corpus code corresponding to the acquired corpus template exist in the corpus information list or not according to the mapping relation between the corpus template and the corpus, if not, the corpus code corresponding to the acquired corpus template is generated, and step S4 is executed;
and step S4: the service interface calling end determines an interface parameter name, a corpus parameter name and an access address of a service interface to be called according to the corpus content to be processed;
step S5: the service interface calling end carries out signature processing on the interface parameter name and the corpus parameter name by using a preset signature mode to obtain a request signature value;
step S6: the service interface calling terminal generates an interface calling request according to the interface parameter name, the corpus parameter name, the access address and the request signature value;
step S7: the service interface calling end calls the service interface to be called based on the interface calling request and receives a corpus processing result returned by the service interface to be called aiming at the corpus content to be processed.
2. The method according to claim 1, wherein the step S5 comprises:
step S51: the service interface calling end sequences the interface parameter name and the corpus parameter name according to a preset sequencing rule, and codes the sequenced interface parameter name, corpus parameter name, value of the interface parameter name and value of the corpus parameter name;
step S52: the service interface calling end carries out splicing processing on the coded interface parameter name, the corpus parameter name, the value of the interface parameter name and the value of the corpus parameter name to obtain request signature data;
step S53: and the service interface calling end acquires the access key of the service interface to be called from the internal storage, and signs the request signature data by using the access key to generate a request signature value.
3. The method of claim 2, wherein said signing the request signature data with the access key to generate a request signature value comprises:
encrypting the request signature data by using the access key to obtain an encryption result;
and coding the encryption result to generate a request signature value.
4. The method according to claim 1, wherein after the step S7, further comprising:
the service interface calling end extracts the corpus identification from the corpus processing result;
and the service interface calling end establishes a corresponding relation among the acquired corpus template, the generated corpus code and the extracted corpus identification and stores the corresponding relation.
5. The method according to claim 1, wherein if it is determined that the corpus identifier and the corpus code corresponding to the obtained corpus template exist in the corpus information list, then:
step S8: and the service interface calling end generates a corpus pushing request according to the to-be-processed corpus content and an internally stored device key, and sends the corpus pushing request to the broadcasting device.
6. The method according to claim 1, wherein the step S6 comprises:
and the service interface calling terminal splices the interface parameter name, the corpus parameter name, the access address and the request signature value to generate an interface calling request.
7. The method according to claim 1, wherein the receiving the corpus processing result returned by the to-be-called service interface for the corpus content to be processed includes:
the service interface to be called carries out corresponding corpus processing according to the imported corpus parameter name to obtain a corpus processing result;
and returning the corpus processing result to the service interface calling end.
8. The method according to claim 1, wherein after the step S7, further comprising:
if the service interface calling end does not receive the corpus processing result returned by the service interface to be called within a first preset time, continuing to call the service interface to be called based on the interface calling request according to a preset interval time until the service interface calling end receives the corpus processing result returned by the service interface to be called.
9. The method according to claim 8, further comprising, after continuing to call the service interface to be called based on the interface call request at predetermined intervals, the following steps:
and if the corpus processing result returned by the service interface to be called is not received within second preset time, regenerating an interface calling request and calling the service interface to be called based on the regenerated interface calling request, wherein the second preset time is longer than the first preset time.
10. The method according to claim 1, wherein after the service interface calling terminal calls the service interface to be called based on the interface calling request, the method further comprises:
and the service interface calling end receives the error information returned by the service interface to be called and positions the reason for calling the error by the interface according to the error information.
11. An apparatus for invoking a service interface, the apparatus comprising:
the corpus content verification module is used for receiving the corpus content to be processed sent by the server, verifying the legality of the corpus content to be processed, acquiring a corpus template from the corpus content to be processed if the verification is passed, and triggering the mapping relation acquisition module, otherwise, ending the mapping relation acquisition module;
the mapping relation acquisition module is used for acquiring a pre-stored corpus information list and a corpus mapping relation, wherein the corpus mapping relation is a one-to-one correspondence relation formed among a corpus template, a corpus identifier and a corpus code;
the list judging module is used for judging whether the corpus identifier and the corpus code corresponding to the obtained corpus template exist in the corpus information list according to the mapping relation between the corpus template and the corpus, if not, the corpus code corresponding to the obtained corpus template is generated, and the parameter name determining module is triggered;
the parameter name determining module is used for determining an interface parameter name, a corpus parameter name and an access address of a service interface to be called according to the corpus content to be processed;
the signature value acquisition module is used for carrying out signature processing on the interface parameter name and the corpus parameter name by using a preset signature mode to obtain a request signature value;
a call request generation module, configured to generate an interface call request according to the interface parameter name, the corpus parameter name, the access address, and the request signature value;
and the interface calling module is used for calling the service interface to be called based on the interface calling request and receiving a corpus processing result returned by the service interface to be called aiming at the corpus content to be processed.
12. A computer-readable storage medium, on which a computer program is stored which, when being executed by a processor, carries out the steps of the method according to any one of claims 1 to 10.
13. A service interface caller comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the processor implements the steps of the method of any one of claims 1 to 10 when executing the program.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210929676.3A CN114996040B (en) | 2022-08-04 | 2022-08-04 | Service interface calling method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210929676.3A CN114996040B (en) | 2022-08-04 | 2022-08-04 | Service interface calling method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN114996040A CN114996040A (en) | 2022-09-02 |
| CN114996040B true CN114996040B (en) | 2022-10-04 |
Family
ID=83022039
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210929676.3A Active CN114996040B (en) | 2022-08-04 | 2022-08-04 | Service interface calling method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114996040B (en) |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105808365A (en) * | 2016-03-22 | 2016-07-27 | 深圳市宁远科技股份有限公司 | HIS (Hospital Information System) interface calling method and HIS interface configuration method |
| CN108200077A (en) * | 2018-01-18 | 2018-06-22 | 北京网信云服信息科技有限公司 | A kind of method and device of calling interface |
| CN108365961A (en) * | 2018-01-02 | 2018-08-03 | 深圳壹账通智能科技有限公司 | The response method and server that interface call method and terminal device, interface call |
| CN113836002A (en) * | 2021-08-23 | 2021-12-24 | 青岛海尔科技有限公司 | Test interface verification method and device, storage medium and electronic device |
| WO2022126966A1 (en) * | 2020-12-15 | 2022-06-23 | 平安科技（深圳）有限公司 | Interface parameter verification and conversion method and apparatus, and device and storage medium |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7028312B1 (en) * | 1998-03-23 | 2006-04-11 | Webmethods | XML remote procedure call (XML-RPC) |
-
2022
- 2022-08-04 CN CN202210929676.3A patent/CN114996040B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105808365A (en) * | 2016-03-22 | 2016-07-27 | 深圳市宁远科技股份有限公司 | HIS (Hospital Information System) interface calling method and HIS interface configuration method |
| CN108365961A (en) * | 2018-01-02 | 2018-08-03 | 深圳壹账通智能科技有限公司 | The response method and server that interface call method and terminal device, interface call |
| CN108200077A (en) * | 2018-01-18 | 2018-06-22 | 北京网信云服信息科技有限公司 | A kind of method and device of calling interface |
| WO2022126966A1 (en) * | 2020-12-15 | 2022-06-23 | 平安科技（深圳）有限公司 | Interface parameter verification and conversion method and apparatus, and device and storage medium |
| CN113836002A (en) * | 2021-08-23 | 2021-12-24 | 青岛海尔科技有限公司 | Test interface verification method and device, storage medium and electronic device |
Non-Patent Citations (1)
| Title |
|---|
| 一种语义接口匹配的地理信息Web服务动态组合方法;邬群勇等;《福州大学学报(自然科学版)》;20111028(第05期);全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN114996040A (en) | 2022-09-02 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| EP3151507B1 (en) | Methods and apparatuses for controlling device | |
| EP3848795A1 (en) | Firmware upgrade method and device, and storage medium | |
| US9843667B2 (en) | Electronic device and call service providing method thereof | |
| CN111340482B (en) | Conflict detection method, device, node equipment and storage medium | |
| CN111277714B (en) | Connection calling method, device, storage medium and terminal | |
| CN110825411B (en) | Upgrading method and device for TWS (two way satellite System) earphone system and computer-readable storage medium | |
| CN113206781B (en) | Client control method, device, equipment and storage medium | |
| CN111241115B (en) | Data synchronization method, device, equipment and storage medium | |
| CN114691115A (en) | Business process system generation method and device, electronic equipment and storage medium | |
| CN110289991B (en) | Fault gateway detection method, device, storage medium and terminal | |
| CN105183571A (en) | Function calling method and device | |
| CN116418795A (en) | Processing method of user access request, electronic device, electronic equipment and medium | |
| CN110278273A (en) | Multimedia file method for uploading, device, terminal, server and storage medium | |
| CN114996040B (en) | Service interface calling method and device | |
| CN113709235A (en) | Device registration method and apparatus, electronic device, and storage medium | |
| CN105120117A (en) | Call interaction method and device | |
| CN111723353A (en) | Identity authentication method, device, terminal and storage medium based on face recognition | |
| CN113836082A (en) | Data migration method and device, storage medium and server | |
| CN113420133B (en) | Session processing method, device, equipment and storage medium | |
| CN115220699A (en) | Software architecture generation method, device, terminal and storage medium based on model development | |
| CN110874143B (en) | Sensor data acquisition method, intelligent terminal, storage medium and electronic equipment | |
| CN108038668B (en) | Method and equipment for cooperative office, terminal and readable storage medium | |
| CN111211964B (en) | Instruction transmission method, device, storage medium and server | |
| CN113688374B (en) | Verification method and electronic equipment | |
| CN111949715B (en) | Manufacturing execution system and data communication method |
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 |