WO2019105138A1 - Procédé de marquage de service, appareil et dispositif sous système multiservices - Google Patents

Procédé de marquage de service, appareil et dispositif sous système multiservices Download PDF

Info

Publication number
WO2019105138A1
WO2019105138A1 PCT/CN2018/110219 CN2018110219W WO2019105138A1 WO 2019105138 A1 WO2019105138 A1 WO 2019105138A1 CN 2018110219 W CN2018110219 W CN 2018110219W WO 2019105138 A1 WO2019105138 A1 WO 2019105138A1
Authority
WO
WIPO (PCT)
Prior art keywords
service
tracking identifier
user
different
request
Prior art date
Application number
PCT/CN2018/110219
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 WO2019105138A1 publication Critical patent/WO2019105138A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements

Definitions

  • the present application relates to the field of computer technologies, and in particular, to a service marking method, apparatus, and device in a multi-service system.
  • service providers can provide various types of business services to users based on the Internet.
  • the service system In the scenario where the user uses the service service, the service system generates a corresponding service log to record related information in the service process.
  • processing the service request may involve calling multiple service systems to form a corresponding “call chain”, and the service system may generate a call chain identifier for the call chain, ie, traceID.
  • the service system records the trace ID in the service log. Then, in the service logs of different service systems belonging to the same call chain, the service track of the user is tracked according to the traceID.
  • the embodiment of the present specification provides a method, a device, and a device for marking a service in a multi-service system, and a method for marking a user service trajectory in a multi-service system scenario.
  • a method for marking a service in a multi-service system includes:
  • the service log is recorded according to the service tracking identifier, and the service logs belonging to the same user are searched in the service logs of the multiple service systems according to the service tracking identifier.
  • the service marking device in the multi-service system provided by the embodiment of the present specification includes:
  • An identity module configured to determine a unified service tracking identifier for different service requests to complete the same service; wherein the service tracking identifier is transmitted between different service systems required to process different service requests;
  • the recording module records the service log according to the service tracking identifier, and searches for the service logs belonging to the same user in the service logs of the multiple service systems according to the service tracking identifier.
  • a service marking device in a multi-service system provided by the embodiment of the present specification, the device includes:
  • the memory storing a service marking program
  • the processor calls a service tag program stored in the memory and executes:
  • the service log is recorded according to the service tracking identifier, and the service logs belonging to the same user are searched in the service logs of the multiple service systems according to the service tracking identifier.
  • a unified service tracking identifier is generated for a plurality of service requests sent by the user to obtain a certain service service, and the service tracking identifier can be transmitted between the service systems even if the service system called by the different service requests sent by the user is different. . Therefore, when the service logs record the service logs, the service tracking identifiers may be written into the service logs. Then, the service tracking identifiers can query and track the user's service trajectories in the service systems belonging to different call chains. .
  • FIG. 1 is a schematic structural diagram of a service marking method according to a multi-service system according to an embodiment of the present disclosure
  • FIG. 2 is a service marking process in a multi-service system according to an embodiment of the present disclosure
  • FIG. 3 is a schematic diagram of an example of a service tracking identifier provided by an embodiment of the present disclosure
  • FIG. 4 is a schematic diagram of a service tracking identifier delivery process in an actual application scenario according to an embodiment of the present disclosure
  • FIG. 5 is a schematic structural diagram of a service marking apparatus in a multi-service system according to an embodiment of the present disclosure.
  • a certain service request initiated by a user may require multiple service systems to be collaboratively processed, and a “call chain” is formed between the various service systems participating in the process.
  • a call chain is formed between the various service systems participating in the process. For example, if a user logs in to a product website, the user's login request can be regarded as a service request, and the call chain between the business systems provided by the service provider in the background for providing the login service can be as follows:
  • the user's login service can be completed.
  • the same call chain generates the same traceID.
  • the service provider background allocates a corresponding calling thread to implement a call to a different service system.
  • the traceID generated by the service provider in the background for the call chain can be considered as the traceID generated by the calling thread corresponding to the service request.
  • certain business services may require users to send multiple business requests to complete.
  • a user purchases an item online
  • the user needs to initiate a plurality of different service requests, such as an order request and a payment request, for the item to be purchased after the user initiates the login request.
  • the call chain corresponding to each service request may be different (that is, the call thread assigned by the service provider to different service requests is different), so its traceID is also different.
  • the trace ID of the service log is also different.
  • a service tagging method applied to a multi-service system is provided, and the same service tracking can be set for different call chains corresponding to multiple service requests sent by the same user. logo. Then, when the service system writes its own service log, the service tracking identifier can be written into the service log, so that the service track of the user is tracked in the service logs of different service systems through the service tracking identifier.
  • the service provider may be a website, a bank, a telecommunications carrier, a data center, or a service platform, and the like, which can provide service services to users through the Internet.
  • the service architecture adopted by the service provider backend may be as shown in FIG. 1.
  • the architecture includes at least: a business client and multiple business systems. among them:
  • the service client may be a business application (such as a shopping app) or a browser running in the terminal device.
  • client may be a business application (such as a shopping app) or a browser running in the terminal device.
  • the user can obtain the business service of the service provider through the business application, or access the website of the service provider through the browser to obtain the business service of the service provider. This is not specifically limited.
  • the service system can be considered as a system capable of providing corresponding service functions, and is usually composed of a corresponding service server.
  • the service server constituting the service system can adopt a single server, a distributed server, or a cluster.
  • the architecture (characterizing the business system in the form of a single server in FIG. 1) is not specifically limited herein.
  • the business functions provided by a single business system are not sufficient to complete certain business services, so multiple business systems need to be coordinated.
  • the process of performing the service tagging method in the multi-service system described in the embodiment of the present disclosure may be as shown in FIG. 2, and specifically includes the following steps:
  • Step S201 Determine a unified service tracking identifier for different service requests to complete the same service.
  • the service tracking identifier is transmitted between different business systems that are required to process different service requests.
  • the service request can be issued by the client. It can be understood that different service requests for the same service are completed here, usually for the same user. In addition, in the embodiment of the present specification, the different service requests for completing the same service are often associated with each other in the execution order. Generally, the execution of the latter service request depends on the execution of the previous service request. After the business results. As described above, when a user purchases an online product and issues a login request, an order request, and a payment request respectively, the execution of the order request by the business system depends on the registered user account, and the execution of the payment request depends on the generated order number.
  • the service tracking identifier may be in the form of a text character and is unique to the entire network. In some special application scenarios, the service tracking identifier in the form of graphical symbols should also be included in the scope of the embodiments of the present specification. Considering that the user ID of the user (such as the user ID, the account name, the device number of the terminal device used by the user, etc.) is also unique, in a possible implementation manner, the service tracking identifier may be Generated based on the user ID.
  • the service tracking identifier is carried in a process in which multiple service systems transmit intermediate service data to each other to complete the same service. Thereby the service tracking identifier is passed between multiple business systems.
  • a service tracking identifier can also be transmitted therein. Further, an association between service systems of different call chains can be established through the service tracking identifier.
  • Step S203 Record a service log according to the service tracking identifier, and search for a service log belonging to the same user in the service logs of the multiple service systems according to the service tracking identifier.
  • the service tracking identifier is transmitted between multiple service systems. Then, when the service system records the service log, the service tracking identifier can be written into the service log. Subsequently, the service tracking identifier in the service log of different service systems can be used to query and track the user's service trajectory.
  • service systems A to C For example, as shown in FIG. 3, it is assumed that for service systems A to C, service systems A and B are used as call chain I for processing service requests I issued by users; and service systems A and C are used as another call chain II. Used to process the business request II issued by the user.
  • a unified service tracking identifier "LogID" is generated for the service request of the user, and is transmitted between the service systems A to C.
  • the LogID is obtained for both the call chain I and the service system on the call chain II. Therefore, when the service log is recorded, the LogID is also written into the service log. Therefore, the query and tracking of the user service track can be performed through the LogID in the service logs of different service systems.
  • a unified service tracking identifier is generated for multiple service requests sent by the user to obtain a certain service service, and the service tracking identifier can be in each service even if the service system called by the different service requests sent by the user is different. Pass between systems. Therefore, when the service logs record the service logs, the service tracking identifiers may be written into the service logs. Then, the service tracking identifiers can query and track the user's service trajectories in the service systems belonging to different call chains. .
  • the generation of the service tracking identifier may be the first service system that receives the service request.
  • the service system A as the first service system that receives the user service request, may generate a service tracking identifier after receiving the service request I of the user.
  • a corresponding identity generation service is run, and the service is used to generate a globally unique service tracking identifier.
  • the identity generation service may be provided by a server running independently, or the identity generation service may be set in each service system.
  • determining a unified service tracking identifier for different service requests for completing the same service may specifically include: receiving a different service request sent by the user to complete the same service, according to the first received The service request generates the service tracking identifier and delivers to the business system required to process the different service requests.
  • the process of generating the service tracking identifier may include: determining user identification information carried in the service request, and generating the service tracking identifier according to the user identification information.
  • the user identification information includes at least: a user's account name, a user ID, a device hardware MAC address and/or an IP address used by the user.
  • a user makes a different service request using a client on his terminal device.
  • the service request sent by the user may carry device information (such as the MAC address of the device) and network information (such as an IP address). Then, the service is conveniently provided according to the foregoing information carried in the service request. Generate a business tracking ID. If other service requests are subsequently received, and the other service requests also carry the above information, it can be determined that the same device is sent for different service requests, so that a unified service tracking identifier can be used for different service requests from the same device.
  • the user uses the client to make a service request on the mobile phone and uses the client on the tablet to make another service request.
  • the device information and the network information carried in the service request are different. Then, it is generally determined that the service requests are from the same account according to the account information used by the user. Further, a unified service tracking identifier can still be used for different service requests carrying the same account information.
  • the generated service tracking identifier may be time-sensitive, that is, the service tracking identifier may remain valid for a set time, and if the service request from the same account or from the same device is not received within the set time, the The service tracking ID is invalid. In other words, after the service tracking identifier is invalid, if the service system receives the same account or a service request sent by the same device, a new service tracking identifier is generated.
  • the service tracking identifier there is usually a correlation between the original service tracking identifier and the newly generated service tracking identifier, because the newly generated service tracking identifier can also be generated based on the user identifier. Then, in the service log, the service tracking identifier related to the same user can be determined.
  • the time limit of the service tracking identifier may be set according to the needs of the actual application, for example, it is set to several hours, several days, one week, or one month, and the like, and is not specifically limited herein.
  • the service tracking identifier generated by the above content can be transmitted in different business systems.
  • the process of transmitting the service tracking identifier can be referred to FIG. 4.
  • the service system A can generate a service tracking identifier LogID for the service request I, and call the service systems B and D to process the service request I. .
  • the LogID will be passed to business systems B and D.
  • the processing result will be returned to the front-end service system A (the LogID is also returned).
  • the generated LogID can be continuously used and transmitted to the corresponding service system C.
  • the service system C will carry the LogID in the processing result and return to the front-end service system A after performing the business processing.
  • each business system can write the log ID into the service log when the service log is recorded. Then, the LogID can be used to query and track the user's service trajectory in the service logs of each business system.
  • the foregoing process for the other service system required to process the different service request may be: carrying the service tracking identifier for the service system that processes the same service request.
  • the intermediate service data is delivered to other service systems required for processing the service request; for the service system that processes the different service requests, the service result data generated by the previous service request and carrying the service tracking identifier is transmitted to A business system that processes a business request.
  • the embodiment of the present specification further provides a service marking device in a multi-service system, as shown in FIG. 5 .
  • the device includes:
  • the identifier module 501 determines a unified service tracking identifier for different service requests to complete the same service, where the service tracking identifier is transmitted between different service systems that are required to be processed by different service requests;
  • the recording module 502 records the service log according to the service tracking identifier, and searches for the service logs belonging to the same user in the service logs of the multiple service systems according to the service tracking identifier.
  • the identifier module 501 receives a different service request sent by the user to complete the same service, generates the service tracking identifier according to the received first service request, and transmits the service tracking identifier to the processing of the different service request. business system.
  • the identifier module 501 is configured to determine user identifier information carried in the service request, and generate the service tracking identifier according to the user identifier information;
  • the user identification information includes at least: a user's account name, a user ID, a device hardware MAC address and/or an IP address used by the user.
  • the identifier module 501 for the service system that processes the same service request, carries the service tracking identifier in the intermediate service data, and delivers the other service system required for processing the service request;
  • the service result data that is generated by the previous service request and carries the service tracking identifier is transmitted to the service system that processes the latter service request;
  • the intermediate service data includes: an intermediate service request and/or an intermediate service result.
  • the identifier module 501 monitors the time limit of the service tracking identifier, and when the service tracking identifier exceeds the aging time, indicates that the service tracking identifier is invalid.
  • the device shown in FIG. 5 may be implemented by a physical device (such as a server and/or a terminal) in an actual application, and specifically includes: a processor and a memory, where
  • the memory stores a service tagging program under the multi-service system
  • the processor calls a service tagging program under the multi-service system stored in the memory, and executes:
  • the service log is recorded according to the service tracking identifier, and the service logs belonging to the same user are searched in the service logs of the multiple service systems according to the service tracking identifier.
  • PLD Programmable Logic Device
  • FPGA Field Programmable Gate Array
  • HDL Hardware Description Language
  • the controller can be implemented in any suitable manner, for example, the controller can take the form of, for example, a microprocessor or processor and a computer readable medium storing computer readable program code (eg, software or firmware) executable by the (micro)processor.
  • computer readable program code eg, software or firmware
  • examples of controllers include, but are not limited to, the following microcontrollers: ARC 625D, Atmel AT91SAM, The Microchip PIC18F26K20 and the Silicone Labs C8051F320, the memory controller can also be implemented as part of the memory's control logic.
  • the controller can be logically programmed by means of logic gates, switches, ASICs, programmable logic controllers, and embedding.
  • Such a controller can therefore be considered a hardware component, and the means for implementing various functions included therein can also be considered as a structure within the hardware component.
  • a device for implementing various functions can be considered as a software module that can be both a method of implementation and a structure within a hardware component.
  • the system, device, module or unit illustrated in the above embodiments may be implemented by a computer chip or an entity, or by a product having a certain function.
  • a typical implementation device is a computer.
  • the computer can be, for example, a personal computer, a laptop computer, a cellular phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or A combination of any of these devices.
  • embodiments of the present invention can be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment, or a combination of software and hardware. Moreover, the invention can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) including computer usable program code.
  • computer-usable storage media including but not limited to disk storage, CD-ROM, optical storage, etc.
  • the computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device.
  • the apparatus implements the functions specified in one or more blocks of a flow or a flow and/or block diagram of the flowchart.
  • These computer program instructions can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce computer-implemented processing for execution on a computer or other programmable device.
  • the instructions provide steps for implementing the functions specified in one or more of the flow or in a block or blocks of a flow diagram.
  • a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
  • processors CPUs
  • input/output interfaces network interfaces
  • memory volatile and non-volatile memory
  • the memory may include non-persistent memory, random access memory (RAM), and/or non-volatile memory in a computer readable medium, such as read only memory (ROM) or flash memory.
  • RAM random access memory
  • ROM read only memory
  • Memory is an example of a computer readable medium.
  • Computer readable media including both permanent and non-persistent, removable and non-removable media, can be stored by any method or technology.
  • the information can be computer readable instructions, data structures, modules of programs, or other data.
  • Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read only memory. (ROM), electrically erasable programmable read only memory (EEPROM), flash memory or other memory technology, compact disk read only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, Magnetic tape cartridges, magnetic tape storage or other magnetic storage devices or any other non-transportable media can be used to store information that can be accessed by a computing device.
  • computer readable media does not include temporary storage of computer readable media, such as modulated data signals and carrier waves.
  • embodiments of the present application can be provided as a method, system, or computer program product.
  • the present application can take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment in combination of software and hardware.
  • the application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) including computer usable program code.
  • the application can be described in the general context of computer-executable instructions executed by a computer, such as a program module.
  • program modules include routines, programs, objects, components, data structures, and the like that perform particular tasks or implement particular abstract data types.
  • the present application can also be practiced in distributed computing environments where tasks are performed by remote processing devices that are connected through a communication network.
  • program modules can be located in both local and remote computer storage media including storage devices.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Debugging And Monitoring (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

La présente invention concerne un procédé de marquage de service, un appareil et un dispositif sous un système multiservices. Pour de multiples demandes de service envoyées par un utilisateur pour obtenir un service, un identifiant de suivi de service uniforme est généré. Même si des systèmes de service devant être appelés par différentes demandes de service envoyées par l'utilisateur sont différents, l'identifiant de suivi de service peut être transmis entre divers systèmes de service.
PCT/CN2018/110219 2017-11-29 2018-10-15 Procédé de marquage de service, appareil et dispositif sous système multiservices WO2019105138A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201711222032.6 2017-11-29
CN201711222032.6A CN108173706B (zh) 2017-11-29 2017-11-29 一种多业务系统下的业务标记方法、装置及设备

Publications (1)

Publication Number Publication Date
WO2019105138A1 true WO2019105138A1 (fr) 2019-06-06

Family

ID=62524072

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/110219 WO2019105138A1 (fr) 2017-11-29 2018-10-15 Procédé de marquage de service, appareil et dispositif sous système multiservices

Country Status (3)

Country Link
CN (1) CN108173706B (fr)
TW (1) TW201926950A (fr)
WO (1) WO2019105138A1 (fr)

Families Citing this family (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108173706B (zh) * 2017-11-29 2020-06-19 阿里巴巴集团控股有限公司 一种多业务系统下的业务标记方法、装置及设备
CN108920277B (zh) * 2018-06-27 2021-12-07 创新先进技术有限公司 业务执行系统、方法及装置、业务隔离系统
CN109241014B (zh) * 2018-07-04 2022-04-15 创新先进技术有限公司 数据处理方法、装置和服务器
CN109063088B (zh) * 2018-07-26 2020-07-28 阿里巴巴集团控股有限公司 序列号的生成方法及装置
CN111427736B (zh) * 2019-01-09 2024-03-12 北京嘀嘀无限科技发展有限公司 日志监控方法、装置、设备及计算机可读存储介质
CN111625431B (zh) * 2019-02-28 2022-04-22 华为技术有限公司 一种日志信息生成方法、装置及电子设备
CN111460338B (zh) * 2020-03-31 2023-06-23 北京创鑫旅程网络技术有限公司 信息查询方法和装置
CN112463562A (zh) * 2020-11-25 2021-03-09 政采云有限公司 一种全业务追踪实现方法、装置、设备及可读存储介质
CN113301397A (zh) * 2021-02-19 2021-08-24 阿里巴巴集团控股有限公司 基于cdn的音视频传输、播放与延时探测方法及设备
CN115665098A (zh) * 2022-10-11 2023-01-31 浪潮云信息技术股份公司 一种分布式架构下的事务记录方法

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150026238A1 (en) * 2013-07-18 2015-01-22 Netapp, Inc. System and method for managing event tracking
CN105207806A (zh) * 2015-08-20 2015-12-30 百度在线网络技术（北京）有限公司 分布式服务的监控方法及装置
CN105260292A (zh) * 2015-10-09 2016-01-20 中国人民财产保险股份有限公司 一种日志记录方法、装置及系统
CN106254144A (zh) * 2016-09-06 2016-12-21 华为技术有限公司 故障定位平台、故障定位方法及装置
CN108173706A (zh) * 2017-11-29 2018-06-15 阿里巴巴集团控股有限公司 一种多业务系统下的业务标记方法、装置及设备

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104346365B (zh) * 2013-07-30 2017-10-13 阿里巴巴集团控股有限公司 确定与特定业务相关的关联日志的方法和装置
CN106599107A (zh) * 2016-11-28 2017-04-26 北京小米移动软件有限公司 获得用户行为的方法、装置及服务器
CN106850782A (zh) * 2017-01-17 2017-06-13 泰康保险集团股份有限公司 用于日志处理的方法和系统
CN106899666B (zh) * 2017-02-21 2019-12-24 阿里巴巴集团控股有限公司 一种针对业务标识的数据处理方法及装置

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150026238A1 (en) * 2013-07-18 2015-01-22 Netapp, Inc. System and method for managing event tracking
CN105207806A (zh) * 2015-08-20 2015-12-30 百度在线网络技术（北京）有限公司 分布式服务的监控方法及装置
CN105260292A (zh) * 2015-10-09 2016-01-20 中国人民财产保险股份有限公司 一种日志记录方法、装置及系统
CN106254144A (zh) * 2016-09-06 2016-12-21 华为技术有限公司 故障定位平台、故障定位方法及装置
CN108173706A (zh) * 2017-11-29 2018-06-15 阿里巴巴集团控股有限公司 一种多业务系统下的业务标记方法、装置及设备

Also Published As

Publication number Publication date
CN108173706A (zh) 2018-06-15
TW201926950A (zh) 2019-07-01
CN108173706B (zh) 2020-06-19

Similar Documents

Publication Publication Date Title
WO2019105138A1 (fr) Procédé de marquage de service, appareil et dispositif sous système multiservices
WO2018177235A1 (fr) Procédé et dispositif de consensus de chaîne de blocs
WO2018113601A1 (fr) Procédé et appareil de traitement de service
EP3565219B1 (fr) Procédé et dispositif d'exécution de service
US10305899B1 (en) Linking a forwarded contact on a resource to a user interaction on a requesting source item
TW201822033A (zh) 資源處理方法及裝置
JP2019537112A (ja) アカウントログインのための方法、装置及びサーバ
WO2019192258A1 (fr) Procédé, dispositif et appareil de synchronisation de données
WO2019179243A1 (fr) Procédé, appareil et dispositif d'affichage d'informations
TW202121268A (zh) 風險預測和風險預測模型的訓練方法、裝置及電子設備
TW201732657A (zh) 業務執行方法及裝置
CN108599973B (zh) 一种日志关联方法、装置及设备
US10073826B2 (en) Providing action associated with event detected within communication
WO2019169964A1 (fr) Procédé et appareil de recommandation de ressource, procédé et appareil de recommandation commerciale, et dispositif électronique
WO2019095854A1 (fr) Procédé, appareil et dispositif de traitement de données traçables multi-partie
CN110297955B (zh) 一种信息查询方法、装置、设备及介质
WO2021204041A1 (fr) Traitement de données
US20210200806A1 (en) Method and apparatus for parallel processing of information
CN111566638A (zh) 向应用编程接口添加描述性元数据以供智能代理使用
WO2017152752A1 (fr) Procédé de chargement de ressources, et procédé et dispositif de mise en œuvre de fonctions service pour une application (app)
US20170177738A1 (en) Dynamic intent registry
WO2020108152A1 (fr) Procédé, dispositif et équipement électronique pour empêcher l'utilisation abusive de données d'identité
TW201838431A (zh) 資源傳輸方法及裝置
CN113256426B (zh) 一种数据处理方法、装置、设备及介质
CN113495797A (zh) 一种消息队列及消费者动态创建方法及系统

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: 18884381

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: 18884381

Country of ref document: EP

Kind code of ref document: A1