WO2018201978A1 - Procédé de traitement de données d'appel d'interface, appareil, dispositif informatique et support de stockage - Google Patents

Procédé de traitement de données d'appel d'interface, appareil, dispositif informatique et support de stockage Download PDF

Info

Publication number
WO2018201978A1
WO2018201978A1 PCT/CN2018/084762 CN2018084762W WO2018201978A1 WO 2018201978 A1 WO2018201978 A1 WO 2018201978A1 CN 2018084762 W CN2018084762 W CN 2018084762W WO 2018201978 A1 WO2018201978 A1 WO 2018201978A1
Authority
WO
WIPO (PCT)
Prior art keywords
interface
information
call
log
log file
Prior art date
Application number
PCT/CN2018/084762
Other languages
English (en)
Chinese (zh)
Inventor
陈林
张国辉
Original Assignee
平安科技（深圳）有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 平安科技（深圳）有限公司 filed Critical 平安科技（深圳）有限公司
Publication of WO2018201978A1 publication Critical patent/WO2018201978A1/fr

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/10—File systems; File servers
    • G06F16/18—File system types
    • G06F16/1805—Append-only file systems, e.g. using logs or journals to store data
    • G06F16/1815—Journaling file systems

Definitions

  • the present application relates to the field of computer technologies, and in particular, to an interface call data processing method, apparatus, computer device, and storage medium.
  • the registration center is used as a third party to judge and forward the interface call request.
  • an interface call data processing method, apparatus, computer apparatus, and non-transitory computer readable storage medium are provided.
  • An interface call data processing method including:
  • the formatted call parameters are allocated to the corresponding target interface for calling processing.
  • An interface calls a data processing device, including:
  • An acquiring module configured to receive an interface call request, obtain a target interface code in the interface call request, and obtain a target data format corresponding to the target interface code
  • a format conversion module configured to perform a corresponding format conversion on the calling parameter in the interface call request according to the obtained target data format
  • An interface address mapping module configured to obtain an interface address corresponding to the target interface code according to a mapping relationship between an interface code and an interface address set in the interface routing service
  • the processing module is configured to allocate the formatted call parameters to the corresponding target interface according to the interface address for calling processing.
  • a computer device comprising a memory and one or more processors, the memory storing computer readable instructions, the computer readable instructions being executed by the processor, causing the one or more processors to execute The following steps:
  • the formatted call parameters are allocated to the corresponding target interface for calling processing.
  • One or more non-transitory computer readable storage mediums storing computer readable instructions, when executed by one or more processors, cause one or more processors to perform the steps of:
  • the formatted call parameters are allocated to the corresponding target interface for calling processing.
  • FIG 1 is an application environment diagram of an interface call data processing method in accordance with one or more embodiments.
  • FIG. 2 is a block diagram of a computer device in accordance with one or more embodiments.
  • FIG. 3 is a flow diagram of an interface call data processing method in accordance with one or more embodiments.
  • FIG. 4 is a flow diagram of a callback step of returning data in accordance with one or more embodiments.
  • FIG. 5 is a flow diagram of a log file generation step in accordance with one or more embodiments.
  • FIG. 6 is a flow diagram of a log file generation step in accordance with another or more embodiments.
  • FIG. 7 is a block diagram of an interface call data processing apparatus in accordance with one or more embodiments.
  • FIG. 8 is a block diagram of an interface call data processing apparatus in accordance with another or more embodiments.
  • FIG. 9 is a block diagram of an interface call data processing apparatus in accordance with yet one or more embodiments.
  • FIG. 1 is an application environment diagram of an interface call data processing method in an embodiment.
  • the application environment includes an interface 110 and a called platform 120 that are connected through a network.
  • the interface invoking device 110 refers to a device that initiates an interface call request to request an interface in the called platform 120.
  • the interface invoking device 110 can be either a terminal or a server.
  • the called platform 120 refers to a platform system that provides an interface called by the interface calling device 110. For example, when the interface invoking device 110 needs to use a certain function in the called platform 120, an interface call request is sent to the called platform 120 to request to call the corresponding interface in the called platform 120 for implementing the function.
  • the interface is not limited to being invoked by the called platform. It can be understood that the called platform 120 can also have the capability of calling interfaces of other devices or platforms.
  • the called platform 120 receives the interface call request sent by the interface invoking device 110, obtains the target interface code in the interface call request, and obtains the target format corresponding to the target interface code; according to the acquired target format, the interface call request Call the parameters for the corresponding format conversion.
  • the called platform 120 obtains the interface address corresponding to the target interface code according to the mapping relationship between the interface code and the interface address configured in the interface routing service. And according to the interface address, the formatted call parameters are allocated to the corresponding target interface in the called platform 120 for call processing.
  • the computer device may be the called platform 120 in FIG. 1, and the called platform 120 may be implemented by a separate server or a server cluster composed of multiple physical servers.
  • the computer device includes a processor, memory, and network interface coupled by a system bus.
  • the processor of the computer device is used to provide computing and control capabilities.
  • the memory of the computer device includes a non-volatile storage medium, an internal memory.
  • a non-volatile storage medium of a computer device stores an operating system and computer readable instructions.
  • the internal memory in the computer device provides an environment for the operation of the operating system and computer readable instructions in the non-volatile storage medium.
  • the computer readable instructions when executed by a processor, cause the processor to perform an interface call data processing method.
  • the network interface is used to connect to the network for communication, such as receiving an interface call request.
  • FIG. 2 is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation of the computer device to which the solution of the present application is applied.
  • the specific computer device may It includes more or fewer components than those shown in the figures, or some components are combined, or have different component arrangements.
  • an interface call data processing method is provided. This embodiment is mainly illustrated by the method applied to the called platform in FIG. 1 above. Referring to FIG. 3, the interface calling data processing method specifically includes the following steps:
  • the interface calling device sends an interface call request to the called platform when the interface of the called platform is to be called, and the interface call request includes the target interface code.
  • the target interface is the interface that is requested to be called.
  • the target interface encoding is used to uniquely identify the target interface.
  • the target interface code in the interface call request may be one or more, that is, the called platform may receive calls to multiple interfaces in parallel.
  • the target data format is a data format conforming to the interface specification of the interface corresponding to the target interface encoding.
  • the correspondence between the interface code and the data format is pre-stored in the called platform, and the called platform acquires the target data format corresponding to the target interface code according to the correspondence.
  • the call parameters are included in the interface call request.
  • the call parameter refers to the parameter related to the interface call processing. It can be understood that the called interface can perform corresponding call processing according to the calling parameter to obtain data that the interface calls the device to call.
  • the calling parameter in the interface call request needs to be converted according to the target data format corresponding to the target interface, that is, converted into a target. Interface specification data.
  • the interface routing service is set in the called platform.
  • An interface routing service is a program that can be used to implement interface routing addressing.
  • the interface route addressing function refers to the function of routing the address to the address of the corresponding interface according to the interface code. It can be understood that the interface routing service does not only have the interface routing address function, and the interface routing service can also have other functions.
  • the mapping relationship between the interface code and the interface address is preset in the interface routing service.
  • the interface code corresponds to the interface address mapping.
  • the called platform acquires an interface address corresponding to the target interface code according to the mapping relationship. Interface address, used to find the corresponding interface in the called platform.
  • the corresponding interface is found in the called platform, and the found interface is the target interface.
  • the called platform allocates the formatted call parameters to the found target interface, and the target interface performs corresponding call processing according to the formatted call parameters.
  • the above interface invokes a data processing method, and by setting an interface routing service in the called platform itself, when receiving an interface call request, the mapping relationship between the interface code and the interface address set in the service may be directly obtained according to the interface reason, that is, the interface may be obtained.
  • the target interface can be found according to the interface address.
  • the registration center needs to be specially set to make the interface call, which greatly reduces the cost of the interface call processing.
  • the call parameter in the interface call request is subjected to corresponding format conversion; and the call parameter transfer after the format transfer refers to the target interface corresponding to the interface address, thereby avoiding the The calling interface does not recognize the error caused by the data.
  • the method further includes a step of invoking data return, specifically including the following steps:
  • the initial data format of the call parameter in the interface call request refers to the data format of the call parameter in the interface call request before the format conversion according to the target format.
  • the initial data format including the calling parameter in the interface call request may be, and the called platform may directly obtain the initial data format of the calling parameter included in the interface call request.
  • the called platform performs format analysis on the calling parameters before the format conversion to extract the corresponding format data, and obtains the corresponding initial data format according to the extracted format data combination.
  • a plurality of data format templates may be preset in the called platform, and the calling parameters before the format conversion are matched and analyzed with each data format template, and the data format template with the highest matching degree is used as the calling parameter before the format conversion.
  • the initial data format may be preset in the called platform, and the calling parameters before the format conversion are matched and analyzed with each data format template, and the data format template with the highest matching degree is used as the calling parameter before the format conversion.
  • step S402 is not limited to being performed after step S310, and step S402 can be performed after step S302 and any step before step S404.
  • S404 Perform format conversion on the data obtained after the call processing based on the initial data format.
  • the called platform may perform call processing according to the call parameter converted by the format interface by the target interface, and obtain corresponding data after the call processing, and the data obtained by the call processing is data required by the interface calling device.
  • the called platform can perform corresponding format conversion on the data obtained after the call is processed according to the initial data format. It can be understood that the data converted according to the initial data format conforms to the data format requirements of the interface calling device.
  • the called platform may return the format converted data directly to the interface calling device according to the data channel established between the two when the interface calling device sends the interface call request.
  • the called platform can also return the format converted data to the interface calling device by other means.
  • the implementation manner of returning the format converted data to the interface calling device by the called platform is not limited, as long as the format converted data is returned to the interface calling device.
  • the initial data format of the calling parameter in the interface call request is automatically obtained, and after the called data is acquired, the data obtained after the processing is automatically converted according to the initial data format, and then returned, that is, The called platform end completes the conversion of the data format, and does not need to perform data format conversion on the interface calling device side, which reduces the requirement for the interface calling device, thereby improving the applicability of the called platform.
  • the method further includes: invoking log information according to the interface routing service record interface; the recorded interface call log information includes call log information of any interface in the invoked platform.
  • the interface invokes log information, including interface call time information, interface information of the requested call, and returned data information.
  • the interface calls time information which may include the interface call start time and the time of returning the called data or the duration of the interface call.
  • the interface information requested to be invoked may include the target interface encoding of the requested call.
  • the returned data information returned may include information such as the size or format of the data being called.
  • the interface routing service in the called platform has an interface call log information management function.
  • the interface invokes the log information management function, which may include a record function for calling the log of the interface.
  • the interface call log information management function may further include an access authority verification function for the interface call log, a function of integrating the call log information, and a function of outputting the call log information to generate a corresponding log file.
  • the interface routing service can uniformly record the interface call log information.
  • the interface calls log information, which is the log information related to the interface call.
  • the log information is called according to the interface recorded by the interface routing service, including the call log information of any interface in the called platform.
  • the interface routing service uniformly records the interface call logs uniformly, and implements unified management of the call log information of the interface, thereby avoiding the independent management of the self-log information of the programs corresponding to the interfaces, and the interface call is caused.
  • the log information is mixed with other massive log information without using the query of the log information for the interface.
  • the program corresponding to each interface is also prevented from independently managing the interface call log information, and the interface call log information is too scattered, which is not conducive to the analysis of the interface call.
  • the interface routing service uniformly records the interface call logs uniformly, which implements centralized management of the interface call log information, and improves the efficiency of query log information and interface call problem analysis.
  • the method further includes a log file generating step, which specifically includes the following steps:
  • the interface invokes a log file generation request for requesting the generation of an interface to call the relevant log file.
  • the user (such as a technician) can perform an interface call log file generating operation on the terminal, and the terminal generates and sends a corresponding interface call log file generating request to the called platform in response to the operation.
  • the interface call log file generation request includes a user identifier, and the user identifier is used to uniquely identify a user who performs an interface call log file generation operation.
  • the correspondence between the user identifier and the rights profile is preset in the called platform.
  • a rights profile is a file that describes the operation rights information of the corresponding user.
  • the called platform obtains a rights configuration file corresponding to the user identifier in the interface call log file generation request according to the correspondence between the user identifier and the rights configuration file.
  • the permission information obtained by the called platform to resolve the permission configuration file may include permission information for accessing the log information of the interface, and may also include other operation authority information of the user.
  • the permission information for accessing the log information of the interface may include operation permission information such as querying, filtering, or outputting the log information of the interface.
  • the log information corresponding to the interface call log file generation authority information is obtained from the interface routing service and output, and the corresponding log file is generated.
  • the interface calls the log file generation permission, which refers to the corresponding log information output and the permission to generate the log file.
  • the called platform may determine, according to the permission information, whether the interface call log file generation authority is satisfied, and if yes, obtain log information corresponding to the interface call log file generation permission from the interface call log information recorded in the interface routing service, and output the log information. To generate the corresponding log file, if not, you can return the prompt message that the interface call log file generation request failed or not process.
  • the called platform determines whether the interface call log file generation permission is satisfied according to the permission information, and may determine whether the interface permission log file generation permission is included in the permission information.
  • the log information corresponding to the interface call log file generation permission is an interface call log information that can be queried and outputted to generate a log file. It can be understood that the interface invokes the log file generation permission, which may be a log file generation permission for calling the log information of all the interfaces recorded in the interface call service, or may be a log file generation of the interface call log information recorded in the interface call service. Permissions.
  • the log file generation authority is generated, and when the interface call log file generation permission is satisfied, the log information corresponding to the interface call log file generation authority information is obtained from the interface routing service and output. Generate the appropriate log file. Greatly improved security.
  • step S508 specifically includes the following steps:
  • the permission information is multi-level permission information, and the permission information may include role level rights, function level rights, data level rights, and operation level rights.
  • a role is the work or location of a user in an organization or task.
  • the permissions for different roles can be different.
  • the head of the human resources department and the general manager of the human resources department are in different roles.
  • Function level permission refers to the user's permission to use some functions.
  • the access interface call log belongs to a function permission.
  • Data level permissions refer to the permissions of the data content that can be accessed. For example, you can access all interface call log information, which belongs to data level permissions.
  • Operation level permissions refer to the operation rights to accessible data, such as output permissions, such as output, add, and delete.
  • the authority information is controlled according to the following hierarchical relationship: role level level authority -> function level level authority -> data level level authority -> operation level level authority. That is, the role level authority is the top level authority management level, and the operation level authority is the lowest level authority management level.
  • the called platform obtains data and/or permission judgment according to the authority information, it may sequentially perform the hierarchical order of the role level authority->function level level authority->data level level authority->operation level level authority.
  • the function permission of the access interface call log refers to the access function of the call log to the interface.
  • the called platform determines, according to the permission information, whether the function level permission corresponding to the acquired user role includes the function permission of the access interface call log, and if yes, the user role has the function permission to access the interface call log.
  • the called platform When the user role has the function permission to access the interface call log, the called platform further obtains the content access authority information of the interface call log corresponding to the user role according to the permission information.
  • the content access permission information of the interface call log refers to the access right (equivalent to the data level level authority) of the content of the interface call log, which is used to represent the accessible interface call log information.
  • the called platform determines whether the user role has the log file generation permission for the accessible interface call log information represented by the content access authority information according to the permission information.
  • Log file generation permission refers to the permission to output log information to the interface to generate log files (equivalent to operation level permissions).
  • the called platform acquires the interface call log represented by the content access permission information and corresponding to the log file generation authority. Information, that is, get the interface call log information that can be accessed and output.
  • the interface call log information that is represented by the obtained content access right information and corresponds to the log file generation authority may be the interface call log information corresponding to one or more interfaces in the called platform.
  • the invoked platform may directly output the obtained interface call log information according to a log file generation format to generate a corresponding log file.
  • the invoked platform may sort the output of the acquired interface call log information by an interface dimension or by an occurrence timing of the interface call log information to generate a corresponding log file.
  • the called platform may also select the corresponding interface call log information to output the corresponding interface call log information according to the preset rule or other requirements in the interface call log generation request to generate a corresponding log file.
  • the multi-level authority information of the role level permission->function level authority->data level level authority->operation level level authority is refined, and the granularity of the authority control of the generation of the log file is refined, so that the authority management is more controlled. Effective, and thus improved security.
  • the interface call log file generation request further includes a log information query condition.
  • Step S608 comprising: querying corresponding log information from the acquired interface call log information according to the log information query condition; outputting the invoked interface call log information to generate an interface call log file.
  • the log information query condition refers to the filter condition for invoking log information on the interface. Specifically, when the user invokes the log file generation operation, the user can input the log information query condition in the terminal interface to obtain the interface call log information that meets the requirements. In the terminal interface, the user can input the log information query condition or manually input the customized log information query condition by selecting the method.
  • the log information query condition further refines the query of the log information, improves the validity and flexibility of the log information query, and avoids the resources caused by the queried log information not meeting the user requirements. waste.
  • an interface call data processing apparatus 700 includes an acquisition module 702, a format conversion module 704, an interface address mapping module 706, and a call processing module 708, where:
  • the obtaining module 702 is configured to receive an interface call request, obtain a target interface code in the interface call request, and obtain a target data format corresponding to the target interface code.
  • the format conversion module 704 is configured to perform corresponding format conversion on the calling parameter in the interface call request according to the acquired target data format
  • the interface address mapping module 706 is configured to obtain an interface address corresponding to the target interface code according to the mapping relationship between the interface code and the interface address set in the interface routing service.
  • the calling processing module 708 is configured to allocate the formatted call parameters to the corresponding target interface according to the interface address for calling processing.
  • the obtaining module 702 is further configured to obtain an initial data format of the calling parameter in the interface call request.
  • the format conversion module 704 is further configured to perform format conversion on the data obtained after the call processing based on the initial data format; and return the data obtained after the format conversion.
  • the apparatus 700 further includes:
  • the log information recording module 710 is configured to invoke log information according to the interface routing service record interface; the recorded interface call log information includes call log information of any interface in the called platform.
  • the obtaining module 702 is further configured to obtain an interface call log file generation request, and obtain a rights configuration file corresponding to the user identifier in the interface call log file generation request.
  • the apparatus 700 further includes:
  • the permission information parsing module 712 is configured to parse the rights configuration file to obtain corresponding authority information.
  • the log file generating module 714 is configured to: when it is determined that the interface call log file generation permission is satisfied according to the permission information, obtain log information corresponding to the interface call log file generation authority information from the interface routing service, and output the corresponding log file.
  • the log file generating module 714 is further configured to acquire a user role corresponding to the user identifier according to the rights information; and when the user role has the function permission of the access interface to invoke the log, obtain the interface call log corresponding to the user role.
  • the content access permission information when the user role invokes the log information on the accessible interface represented by the content access permission information, and has the log file generation permission, the content access permission information is represented, and the log file generation authority is corresponding.
  • the interface invokes log information; the corresponding log file is generated according to the obtained interface call log information.
  • the interface call log file generation request further includes a log information query condition.
  • the log file generating module 714 is further configured to: according to the log information query condition, query the corresponding log information from the acquired interface call log information; output the query interface call log information, and generate an interface call log file.
  • Each of the modules in the above-described interface call data processing apparatus may be implemented in whole or in part by software, hardware, and combinations thereof.
  • Each of the above modules may be embedded in or independent of the processor in the computer device, or may be stored in a memory in the computer device in a software form, so that the processor invokes the operations corresponding to the above modules.
  • a computer apparatus comprising a memory and one or more processors having stored therein computer readable instructions that, when executed by the processor, cause one or more processors The following steps are performed: receiving an interface call request, obtaining a target interface code in the interface call request, acquiring a target data format corresponding to the target interface code, and performing a format conversion on the call parameter in the interface call request according to the acquired target data format.
  • the interface address corresponding to the target interface code is obtained; according to the interface address, the formatted call parameter is allocated to the corresponding target interface for calling processing.
  • the computer readable instructions further cause the processor to: obtain an initial data format of the call parameters in the interface call request; format convert the data obtained after the call processing based on the initial data format; return format The data obtained after conversion.
  • the computer readable instructions further cause the processor to perform the step of: invoking log information in accordance with an interface routing service record interface; the recorded interface call log information includes call log information for any of the interfaces in the invoked platform.
  • the computer readable instructions further cause the processor to: obtain an interface call log file generation request; obtain a rights configuration file corresponding to the user identifier in the interface call log file generation request; and resolve the rights configuration file The corresponding permission information is obtained.
  • the permission to generate the interface call log file is determined according to the permission information
  • the log information corresponding to the interface call log generation authority information is obtained from the interface routing service and output, and the corresponding log file is generated.
  • the log information corresponding to the interface call log file generation authority information is obtained from the interface routing service and output, and the corresponding information is generated.
  • the log file includes: obtaining a user role corresponding to the user identifier according to the permission information; and obtaining the content access permission information of the interface call log corresponding to the user role when the user role has the function permission of the access interface to invoke the log; Invoking log information to the accessible interface represented by the content access permission information, and having the log file generation permission, acquiring the interface calling log information represented by the content access permission information and corresponding to the log file generating permission; Call the log information to generate the corresponding log file.
  • the interface call log file generation request further includes a log information query condition; the processor performs a log file according to the acquired interface call log information, and includes: obtaining the corresponding log file according to the log information query condition.
  • the interface calls the log information to query the corresponding log information; the queried interface calls the log information output, and generates an interface call log file.
  • a storage medium storing computer readable instructions, when executed by one or more processors, causes one or more processors to perform the steps of: receiving an interface call Requesting, obtaining the target interface code in the interface call request; obtaining the target data format corresponding to the target interface code; performing the format conversion on the call parameter in the interface call request according to the acquired target data format; setting according to the interface routing service
  • the mapping relationship between the interface code and the interface address obtains the interface address corresponding to the target interface code; according to the interface address, the format converted call parameter is allocated to the corresponding target interface for calling processing.
  • the computer readable instructions further cause the processor to: obtain an initial data format of the call parameters in the interface call request; format convert the data obtained after the call processing based on the initial data format; return format The data obtained after conversion.
  • the computer readable instructions further cause the processor to perform the step of: invoking log information in accordance with an interface routing service record interface; the recorded interface call log information includes call log information for any of the interfaces in the invoked platform.
  • the computer readable instructions further cause the processor to: obtain an interface call log file generation request; obtain a rights configuration file corresponding to the user identifier in the interface call log file generation request; and resolve the rights configuration file The corresponding permission information is obtained.
  • the permission to generate the interface call log file is determined according to the permission information
  • the log information corresponding to the interface call log generation authority information is obtained from the interface routing service and output, and the corresponding log file is generated.
  • the log information corresponding to the interface call log file generation authority information is obtained from the interface routing service and output, and the corresponding information is generated.
  • the log file includes: obtaining a user role corresponding to the user identifier according to the permission information; and obtaining the content access permission information of the interface call log corresponding to the user role when the user role has the function permission of the access interface to invoke the log; Invoking log information to the accessible interface represented by the content access permission information, and having the log file generation permission, acquiring the interface calling log information represented by the content access permission information and corresponding to the log file generating permission; Call the log information to generate the corresponding log file.
  • the interface call log file generation request further includes a log information query condition; the processor performs a log file according to the acquired interface call log information, and includes: obtaining the corresponding log file according to the log information query condition.
  • the interface calls the log information to query the corresponding log information; the queried interface calls the log information output, and generates an interface call log file.
  • Non-volatile memory can include read only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), or flash memory.
  • Volatile memory can include random access memory (RAM) or external cache memory.
  • RAM is available in a variety of formats, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronization chain.
  • SRAM static RAM
  • DRAM dynamic RAM
  • SDRAM synchronous DRAM
  • DDRSDRAM double data rate SDRAM
  • ESDRAM enhanced SDRAM
  • Synchlink DRAM SLDRAM
  • Memory Bus Radbus
  • RDRAM Direct RAM
  • DRAM Direct Memory Bus Dynamic RAM
  • RDRAM Memory Bus Dynamic RAM

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Data Mining & Analysis (AREA)
  • Databases & Information Systems (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Telephonic Communication Services (AREA)

Abstract

L'invention concerne un procédé de traitement de données d'appel d'interface, comprenant les étapes suivantes : recevoir une demande d'appel d'interface, et acquérir un code d'interface cible dans ladite demande d'appel d'interface ; acquérir un format de données cible correspondant au code d'interface cible ; effectuer une conversion de format correspondante des paramètres d'appel dans ladite demande d'appel d'interface selon le format de données cible acquis ; acquérir une adresse d'interface correspondant au code d'interface cible selon un mappage entre des codes d'interface et des adresses d'interface configuré dans un service de routage d'interface ; selon l'adresse d'interface, attribuer les paramètres d'appel au format converti à une interface cible correspondante pour un traitement d'appel.
PCT/CN2018/084762 2017-05-04 2018-04-27 Procédé de traitement de données d'appel d'interface, appareil, dispositif informatique et support de stockage WO2018201978A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710309458.9 2017-05-04
CN201710309458.9A CN108255905B (zh) 2017-05-04 2017-05-04 接口调用数据处理方法、装置和计算机设备

Publications (1)

Publication Number Publication Date
WO2018201978A1 true WO2018201978A1 (fr) 2018-11-08

Family

ID=62721793

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/084762 WO2018201978A1 (fr) 2017-05-04 2018-04-27 Procédé de traitement de données d'appel d'interface, appareil, dispositif informatique et support de stockage

Country Status (2)

Country Link
CN (1) CN108255905B (fr)
WO (1) WO2018201978A1 (fr)

Cited By (31)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109710571A (zh) * 2018-12-27 2019-05-03 腾讯音乐娱乐科技（深圳）有限公司 一种文件解析方法、设备及存储介质
CN110162560A (zh) * 2019-04-16 2019-08-23 深圳壹账通智能科技有限公司 金融数据接口对接方法、装置、计算机设备及存储介质
CN110333984A (zh) * 2019-06-05 2019-10-15 阿里巴巴集团控股有限公司 接口异常检测方法、装置、服务器及系统
CN110825465A (zh) * 2019-11-06 2020-02-21 北京达佳互联信息技术有限公司 日志数据处理方法、装置、电子设备及存储介质
CN111078447A (zh) * 2019-11-24 2020-04-28 杭州安恒信息技术股份有限公司 一种微服务架构中的异常定位方法、装置、设备、介质
CN111190750A (zh) * 2019-12-25 2020-05-22 天津幸福生命科技有限公司 一种数据处理方法以及系统
CN111339466A (zh) * 2020-02-25 2020-06-26 天津满运软件科技有限公司 接口管理方法、装置、电子设备及可读存储介质
CN111339380A (zh) * 2020-03-04 2020-06-26 北京新氧科技有限公司 一种接口耗时数据处理方法及相关装置
CN111341445A (zh) * 2020-02-05 2020-06-26 网宿科技股份有限公司 微服务调用链的健康检测方法和健康检测系统
CN111984713A (zh) * 2020-06-29 2020-11-24 五八到家有限公司 一种数据处理方法、装置、设备和存储介质
CN112052227A (zh) * 2020-09-25 2020-12-08 郑州阿帕斯数云信息科技有限公司 数据变更日志的处理方法、装置和电子设备
CN112187728A (zh) * 2020-09-08 2021-01-05 灵犀科技有限公司 一种基于统一用户权限的网关代理管理方法及装置
CN112217823A (zh) * 2020-10-13 2021-01-12 中国银行股份有限公司 基于dubbo框架的接口权限控制方法及装置
CN112307374A (zh) * 2020-10-30 2021-02-02 康键信息技术（深圳）有限公司 基于待办事项的跳转方法、装置、设备及存储介质
CN112328939A (zh) * 2020-11-16 2021-02-05 北京沃东天骏信息技术有限公司 页面处理方法、装置及存储介质
CN112579428A (zh) * 2019-09-29 2021-03-30 北京沃东天骏信息技术有限公司 接口测试的方法、装置、电子设备和存储介质
CN111413918B (zh) * 2020-03-05 2021-05-28 明珞汽车装备（上海）有限公司 Opc通信标签的创建数据处理方法、系统和存储介质
CN112948474A (zh) * 2019-12-11 2021-06-11 深圳云天励飞技术有限公司 数据导出方法、装置、设备及计算机可读存储介质
CN112988273A (zh) * 2021-03-24 2021-06-18 北京沃东天骏信息技术有限公司 异构系统的调用方法和接口管理平台
CN113542369A (zh) * 2021-06-28 2021-10-22 深圳海付移通科技有限公司 接口数据处理方法、装置、计算机设备和存储介质
CN113703862A (zh) * 2021-07-12 2021-11-26 新华三大数据技术有限公司 基于配置的接口调用方法、装置、设备及存储介质
CN113742300A (zh) * 2020-08-11 2021-12-03 北京沃东天骏信息技术有限公司 日志管理方法、装置、服务端和系统
CN114020319A (zh) * 2021-09-28 2022-02-08 深圳市潮流网络技术有限公司 接口调用的方法、装置、服务器及计算机可读存储介质
CN114598750A (zh) * 2022-01-14 2022-06-07 浙江吉利控股集团有限公司 一种数据请求处理方法、装置及存储介质
CN114780267A (zh) * 2022-06-21 2022-07-22 苏州万店掌网络科技有限公司 一种接口调用方法、装置、设备及存储介质
CN114826865A (zh) * 2022-05-11 2022-07-29 北京鼎泰智源科技有限公司 一种涉税数据应用接口对接方法及装置
CN115080940A (zh) * 2022-07-04 2022-09-20 中国联合网络通信集团有限公司 基于层次状态机用户访问权限的处理方法及装置
CN115185717A (zh) * 2022-09-14 2022-10-14 北京达佳互联信息技术有限公司 接口调用方法、装置、电子设备和存储介质
CN115396492A (zh) * 2022-08-03 2022-11-25 深圳前海环融联易信息科技服务有限公司 服务请求方法、装置、计算机设备及程序产品
CN116069840A (zh) * 2022-11-30 2023-05-05 湖南长银五八消费金融股份有限公司 业务重构迁移中接口重放方法、装置和计算机设备
CN116627486A (zh) * 2023-07-25 2023-08-22 中博信息技术研究院有限公司 简洁配置型rest接口管理与消息转换方法和装置

Families Citing this family (23)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109165486B (zh) * 2018-08-27 2021-06-22 四川长虹电器股份有限公司 一种可配置的接口访问权限控制方法
CN109408337B (zh) 2018-10-31 2021-12-28 京东方科技集团股份有限公司 一种接口运维的方法及装置
CN109857569A (zh) * 2018-11-08 2019-06-07 深圳壹账通智能科技有限公司 接口调用处理方法及装置、存储介质、计算机设备
CN109684103A (zh) * 2018-12-17 2019-04-26 上海曼恒数字技术股份有限公司 一种接口调用方法、装置、服务器及存储介质
CN109614338B (zh) * 2018-12-25 2022-03-18 成都四方伟业软件股份有限公司 外部接口适配方法、装置和外部接口适配器
CN109683878A (zh) * 2018-12-26 2019-04-26 苏州浪潮智能软件有限公司 一种用于Web系统开发适配器组件的实现方法
CN110083582A (zh) * 2019-03-22 2019-08-02 平安普惠企业管理有限公司 输出日志的方法、装置、计算机设备及存储介质
CN110109656B (zh) * 2019-03-25 2024-06-28 平安科技（深圳）有限公司 接口模拟方法、装置、计算机设备和存储介质
CN112099964A (zh) * 2019-06-18 2020-12-18 北京思源政通科技集团有限公司 接口的调用方法、装置、存储介质及电子装置
CN110413423B (zh) * 2019-07-23 2024-07-23 腾讯科技（深圳）有限公司 数据处理方法、相关装置、设备及存储介质
CN110427416A (zh) * 2019-08-12 2019-11-08 东莞市大易产业链服务有限公司 银行接口信息处理方法、装置、计算机设备和存储介质
CN111026563B (zh) * 2019-11-18 2024-03-15 北京飞赛克科技有限公司 调用接口的方法、装置、存储介质及电子设备
CN111158661A (zh) * 2019-12-11 2020-05-15 中国平安财产保险股份有限公司 系统接口对接方法、装置、介质及电子设备
CN111400072B (zh) * 2020-04-22 2023-10-17 Oppo广东移动通信有限公司 接口调用方法、存储介质和相关设备
CN111708684B (zh) * 2020-05-06 2022-11-15 苏宁云计算有限公司 一种页面访问的记录方法、装置及计算机系统
CN111597242A (zh) * 2020-05-13 2020-08-28 上海电机系统节能工程技术研究中心有限公司 供应链数据对接方法、装置、电子设备和存储介质
CN111767261A (zh) * 2020-05-29 2020-10-13 广州视源电子科技股份有限公司 调试日志输出方法、装置、存储介质及电子设备
CN111722947A (zh) * 2020-06-28 2020-09-29 深圳壹账通智能科技有限公司 服务调用方法及系统
CN112181535B (zh) * 2020-09-21 2024-10-18 中国建设银行股份有限公司 一种接口调用方法、装置、服务器及存储介质
CN112860463B (zh) * 2021-03-22 2024-06-14 平安商业保理有限公司 业务请求转发方法、装置、计算机设备和可读存储介质
CN113312242B (zh) * 2021-06-29 2024-05-17 中国农业银行股份有限公司 接口信息管理方法、装置、设备及存储介质
CN114265824B (zh) * 2021-12-27 2022-07-01 众和空间(北京)科技有限责任公司 一种基于映射文件的物联网设备集成方法
CN115941607A (zh) * 2022-12-01 2023-04-07 大箴(杭州)科技有限公司 一种信息录入方法及装置、存储介质、计算机设备

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102193829A (zh) * 2011-05-20 2011-09-21 深圳市江波龙电子有限公司 虚拟机调用本地接口的方法及装置
CN102255961A (zh) * 2011-06-30 2011-11-23 重庆新媒农信科技有限公司 基于J2ME调用Web Service接口的方法
CN105808365A (zh) * 2016-03-22 2016-07-27 深圳市宁远科技股份有限公司 His接口调用方法及his接口配置方法
CN106528400A (zh) * 2016-09-22 2017-03-22 深圳峰创智诚科技有限公司 Mock测试方法和装置

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102193829A (zh) * 2011-05-20 2011-09-21 深圳市江波龙电子有限公司 虚拟机调用本地接口的方法及装置
CN102255961A (zh) * 2011-06-30 2011-11-23 重庆新媒农信科技有限公司 基于J2ME调用Web Service接口的方法
CN105808365A (zh) * 2016-03-22 2016-07-27 深圳市宁远科技股份有限公司 His接口调用方法及his接口配置方法
CN106528400A (zh) * 2016-09-22 2017-03-22 深圳峰创智诚科技有限公司 Mock测试方法和装置

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
YANG, CHENG ET AL.: "A kind of oracle database call interface based on OCI9", MICROCOMPUTER APPLICATIONS, vol. 30, no. 4, 30 April 2009 (2009-04-30), pages 35 - 39 *

Cited By (43)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109710571A (zh) * 2018-12-27 2019-05-03 腾讯音乐娱乐科技（深圳）有限公司 一种文件解析方法、设备及存储介质
CN109710571B (zh) * 2018-12-27 2023-06-23 腾讯音乐娱乐科技（深圳）有限公司 一种文件解析方法、设备及存储介质
CN110162560A (zh) * 2019-04-16 2019-08-23 深圳壹账通智能科技有限公司 金融数据接口对接方法、装置、计算机设备及存储介质
CN110333984A (zh) * 2019-06-05 2019-10-15 阿里巴巴集团控股有限公司 接口异常检测方法、装置、服务器及系统
CN112579428A (zh) * 2019-09-29 2021-03-30 北京沃东天骏信息技术有限公司 接口测试的方法、装置、电子设备和存储介质
CN110825465A (zh) * 2019-11-06 2020-02-21 北京达佳互联信息技术有限公司 日志数据处理方法、装置、电子设备及存储介质
CN110825465B (zh) * 2019-11-06 2024-05-07 北京达佳互联信息技术有限公司 日志数据处理方法、装置、电子设备及存储介质
CN111078447B (zh) * 2019-11-24 2023-09-19 杭州安恒信息技术股份有限公司 一种微服务架构中的异常定位方法、装置、设备、介质
CN111078447A (zh) * 2019-11-24 2020-04-28 杭州安恒信息技术股份有限公司 一种微服务架构中的异常定位方法、装置、设备、介质
CN112948474B (zh) * 2019-12-11 2024-01-05 深圳云天励飞技术有限公司 数据导出方法、装置、设备及计算机可读存储介质
CN112948474A (zh) * 2019-12-11 2021-06-11 深圳云天励飞技术有限公司 数据导出方法、装置、设备及计算机可读存储介质
CN111190750B (zh) * 2019-12-25 2024-04-16 北京懿医云科技有限公司 一种数据处理方法以及系统
CN111190750A (zh) * 2019-12-25 2020-05-22 天津幸福生命科技有限公司 一种数据处理方法以及系统
CN111341445A (zh) * 2020-02-05 2020-06-26 网宿科技股份有限公司 微服务调用链的健康检测方法和健康检测系统
CN111341445B (zh) * 2020-02-05 2024-04-16 网宿科技股份有限公司 微服务调用链的健康检测方法和健康检测系统
CN111339466A (zh) * 2020-02-25 2020-06-26 天津满运软件科技有限公司 接口管理方法、装置、电子设备及可读存储介质
CN111339380A (zh) * 2020-03-04 2020-06-26 北京新氧科技有限公司 一种接口耗时数据处理方法及相关装置
CN111339380B (zh) * 2020-03-04 2023-12-22 北京新氧科技有限公司 一种接口耗时数据处理方法及相关装置
CN111413918B (zh) * 2020-03-05 2021-05-28 明珞汽车装备（上海）有限公司 Opc通信标签的创建数据处理方法、系统和存储介质
CN111984713A (zh) * 2020-06-29 2020-11-24 五八到家有限公司 一种数据处理方法、装置、设备和存储介质
CN113742300A (zh) * 2020-08-11 2021-12-03 北京沃东天骏信息技术有限公司 日志管理方法、装置、服务端和系统
CN112187728A (zh) * 2020-09-08 2021-01-05 灵犀科技有限公司 一种基于统一用户权限的网关代理管理方法及装置
CN112052227A (zh) * 2020-09-25 2020-12-08 郑州阿帕斯数云信息科技有限公司 数据变更日志的处理方法、装置和电子设备
CN112217823A (zh) * 2020-10-13 2021-01-12 中国银行股份有限公司 基于dubbo框架的接口权限控制方法及装置
CN112307374A (zh) * 2020-10-30 2021-02-02 康键信息技术（深圳）有限公司 基于待办事项的跳转方法、装置、设备及存储介质
CN112307374B (zh) * 2020-10-30 2023-10-20 康键信息技术（深圳）有限公司 基于待办事项的跳转方法、装置、设备及存储介质
CN112328939A (zh) * 2020-11-16 2021-02-05 北京沃东天骏信息技术有限公司 页面处理方法、装置及存储介质
CN112988273A (zh) * 2021-03-24 2021-06-18 北京沃东天骏信息技术有限公司 异构系统的调用方法和接口管理平台
CN113542369A (zh) * 2021-06-28 2021-10-22 深圳海付移通科技有限公司 接口数据处理方法、装置、计算机设备和存储介质
CN113703862A (zh) * 2021-07-12 2021-11-26 新华三大数据技术有限公司 基于配置的接口调用方法、装置、设备及存储介质
CN114020319A (zh) * 2021-09-28 2022-02-08 深圳市潮流网络技术有限公司 接口调用的方法、装置、服务器及计算机可读存储介质
CN114598750A (zh) * 2022-01-14 2022-06-07 浙江吉利控股集团有限公司 一种数据请求处理方法、装置及存储介质
CN114598750B (zh) * 2022-01-14 2024-01-30 浙江吉利控股集团有限公司 一种数据请求处理方法、装置及存储介质
CN114826865A (zh) * 2022-05-11 2022-07-29 北京鼎泰智源科技有限公司 一种涉税数据应用接口对接方法及装置
CN114780267A (zh) * 2022-06-21 2022-07-22 苏州万店掌网络科技有限公司 一种接口调用方法、装置、设备及存储介质
CN115080940A (zh) * 2022-07-04 2022-09-20 中国联合网络通信集团有限公司 基于层次状态机用户访问权限的处理方法及装置
CN115396492A (zh) * 2022-08-03 2022-11-25 深圳前海环融联易信息科技服务有限公司 服务请求方法、装置、计算机设备及程序产品
CN115396492B (zh) * 2022-08-03 2023-11-17 深圳前海环融联易信息科技服务有限公司 服务请求方法、装置、计算机设备及程序产品
CN115185717A (zh) * 2022-09-14 2022-10-14 北京达佳互联信息技术有限公司 接口调用方法、装置、电子设备和存储介质
CN115185717B (zh) * 2022-09-14 2023-01-20 北京达佳互联信息技术有限公司 接口调用方法、装置、电子设备和存储介质
CN116069840A (zh) * 2022-11-30 2023-05-05 湖南长银五八消费金融股份有限公司 业务重构迁移中接口重放方法、装置和计算机设备
CN116627486B (zh) * 2023-07-25 2023-10-20 中博信息技术研究院有限公司 简洁配置型rest接口管理与消息转换方法和装置
CN116627486A (zh) * 2023-07-25 2023-08-22 中博信息技术研究院有限公司 简洁配置型rest接口管理与消息转换方法和装置

Also Published As

Publication number Publication date
CN108255905A (zh) 2018-07-06
CN108255905B (zh) 2019-10-01

Similar Documents

Publication Publication Date Title
WO2018201978A1 (fr) Procédé de traitement de données d'appel d'interface, appareil, dispositif informatique et support de stockage
CN109474578B (zh) 报文消息校验方法、装置、计算机设备和存储介质
CN109784922B (zh) 电子合同签署方法、装置、计算机设备和存储介质
WO2020232884A1 (fr) Procédé de migration de table de données, appareil, dispositif informatique et support de stockage
WO2020168692A1 (fr) Procédé de partage de données de masse, plateforme de partage ouverte et dispositif électronique
CN108491367B (zh) 报告文档生成的方法、装置、计算机设备和存储介质
WO2018201887A1 (fr) Procédé de réponse de données, appareil, dispositif terminal et support
CN111782652B (zh) 数据调用方法、装置、计算机设备和存储介质
CN112860778B (zh) 桌面应用程序的数据库管理方法、装置、设备和介质
CN103064960A (zh) 数据库查询方法及设备
CN110765484A (zh) 一种征信数据处理方法及电子设备
CN113037831A (zh) 一种服务网关报文处理方法及装置
US11470068B2 (en) System and methods for securely storing data for efficient access by cloud-based computing instances
CN112511591A (zh) 一种医院接口数据交互的实现方法、装置、设备和介质
CN111818175A (zh) 企业服务总线配置文件生成方法、装置、设备和存储介质
CN113722114A (zh) 一种数据服务的处理方法、装置、计算设备及存储介质
CN114285852A (zh) 基于多级服务平台的服务调用方法及装置
CN112052267B (zh) 一种数据查询方法、设备、服务器及存储介质
WO2020253044A1 (fr) Procédé et appareil de configuration de service, et dispositif informatique et support de stockage
CN111488362A (zh) 一种服务器的资源信息查询方法、系统、设备以及介质
CN111324906A (zh) 基于数据接口的自动接入方法、装置、电子设备
CN116303622A (zh) 一种数据库查询方法、装置、设备及存储介质
CN112583890B (zh) 基于企业办公系统的消息推送方法、装置和计算机设备
CN113032820B (zh) 文件存储方法、访问方法、装置、设备及存储介质
CN109189753B (zh) 一种在hue中添加用户信息的方法及装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 18794936

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 18794936

Country of ref document: EP

Kind code of ref document: A1

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 13.03.2020)

122 Ep: pct application non-entry in european phase

Ref document number: 18794936

Country of ref document: EP

Kind code of ref document: A1