WO2016173451A1 - 生成域名解析的方法、装置及服务器 - Google Patents

生成域名解析的方法、装置及服务器 Download PDF

Info

Publication number
WO2016173451A1
WO2016173451A1 PCT/CN2016/079866 CN2016079866W WO2016173451A1 WO 2016173451 A1 WO2016173451 A1 WO 2016173451A1 CN 2016079866 W CN2016079866 W CN 2016079866W WO 2016173451 A1 WO2016173451 A1 WO 2016173451A1
Authority
WO
WIPO (PCT)
Prior art keywords
parsing
task
original
same
tasks
Prior art date
Application number
PCT/CN2016/079866
Other languages
English (en)
French (fr)
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 WO2016173451A1 publication Critical patent/WO2016173451A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/45—Network directories; Name-to-address mapping
    • H04L61/4505—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols
    • H04L61/4511—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols using domain name system [DNS]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/58—Caching of addresses or names

Definitions

  • the present application relates to the field of network communication technologies, and in particular, to a method, an apparatus, and a server for generating domain name resolution.
  • Cloud service is an increase, use and delivery mode of Internet-based related services.
  • VM Virtual Machine
  • Each virtualization platform can correspond to a VM (Virtual Machine).
  • each VM on the cloud server can correspond to a primary domain name of a website, and each primary domain name may correspond to multiple subdomains, so that the user can access the website resources corresponding to the primary domain name or the subdomain name.
  • the domain name resolution server needs to generate corresponding domain name resolutions for these domain names, so as to point these domain names to the IP (Internet Protocol) addresses of the corresponding websites, so that the users can access the website resources corresponding to the primary domain names or subdomains.
  • the server that generates the domain name resolution process performs the domain name resolution for different domain names by performing the resolution task. Because different resolution tasks of the same domain name have time-dependent dependencies during execution, the server needs to follow these resolution tasks. The chronological order is generated in a single queue, so that when a large number of parsing tasks are concurrent, the efficiency of generating domain name resolution is low, and the generated resources on the server are wasted.
  • the present invention provides a method, an apparatus, and a server for generating a domain name resolution, so as to solve the problem that the existing domain name resolution is low, and the resource generated on the server is easily wasted.
  • a method for generating domain name resolution includes:
  • Domain name resolution of different domain names is generated by performing distributed processing on the independent resolution tasks.
  • an apparatus for generating domain name resolution includes:
  • An obtaining unit configured to obtain an original parsing task of different domain names from a cache queue
  • a merging unit configured to merge the original parsing tasks according to a preset rule to generate an independent parsing task of the different domain name
  • a generating unit configured to generate domain name resolution of different domain names by performing distributed processing on the independent parsing task.
  • a server including:
  • processor a memory for storing the processor executable instructions
  • processor is configured to:
  • Domain name resolution of different domain names is generated by performing distributed processing on the independent resolution tasks.
  • the original parsing task is cached, so that the original parsing task of the cache can be uniformly analyzed, so that the original parsing tasks with dependencies in time can be merged to generate independent parsing tasks, and independently parsed.
  • Distributed processing can be used between tasks to perform parallel processing to generate domain name resolution for different domain names. Since the number of parsing tasks that need to be processed can be reduced by merging the original parsing tasks, and because the single independent queue processing of the merged independent parsing tasks is not required, the distributed processing manner is used to parallelize different independent parsing tasks. While making full use of the generated resources on the server, the efficiency of domain name resolution is effectively improved.
  • FIG. 1 is a schematic diagram of an application scenario for generating domain name resolution in the present application
  • FIG. 2 is a flowchart of an embodiment of a method for generating domain name resolution according to the present application
  • FIG. 3A is a flowchart of another embodiment of a method for generating domain name resolution according to the present application.
  • FIG. 3B is a schematic diagram of distributed processing of an independent parsing task in FIG. 3A;
  • FIG. 4 is a hardware structural diagram of a server where a device for generating domain name resolution is provided in the present application
  • FIG. 5 is a block diagram of an embodiment of an apparatus for generating domain name resolution according to the present application.
  • FIG. 6 is a block diagram of another embodiment of an apparatus for generating domain name resolution according to the present application.
  • first, second, third, etc. may be used to describe various information in this application, such information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other.
  • first information may also be referred to as the second information without departing from the scope of the present application.
  • second information may also be referred to as the first information.
  • word "if” as used herein may be interpreted as "when” or “when” or “in response to a determination.”
  • FIG. 1 is a schematic diagram of an application scenario for generating domain name resolution by applying the embodiment of the present application:
  • a cloud service system is shown in FIG. 1.
  • the embodiment of the present application generates a domain name resolution based on the cloud service system, where the cloud server system includes a cloud server and a server for generating domain name resolution (hereinafter referred to as a generation server in the embodiment of the present application). ).
  • n a natural number greater than 1
  • VMs are set on the cloud server, and each VM can be provided to a website for storing website resources of the website, and each website is identified by the assigned IP address.
  • the user can access the website resource by inputting the domain name registered by the website.
  • the DNS server can convert the domain name into the IP address of the website, thereby completing the above access. Therefore, to implement the user to access different website resources through the domain name, the server needs to generate the domain name resolution task in advance, so as to generate domain name resolution for different domain names, so as to follow the generated domain name resolution result from the domain name to the IP address. Conversion.
  • the generation server when generating the domain name resolution of each domain name, the generation server performs the parsing task of different domain names in a single queue processing manner, so the efficiency is low.
  • the generation server may combine the parsing tasks of different domain names, and use the distributed queue to process the merged parsing tasks. Therefore, the processing efficiency is high, and the parsing resources on the generating server may be fully utilized.
  • FIG. 2 it is a flowchart of an embodiment of a method for generating domain name resolution according to the present application. The embodiment is described from the generation server side:
  • Step 201 Obtain an original parsing task of different domain names from the cache queue.
  • each domain name corresponds to multiple resolution tasks.
  • Domain name resolution is generated by performing these parsing tasks. These parsing tasks may include: configuring the resolution task of the A (Address) record, the A record is used to specify the IP address corresponding to the domain name, the resolution task of the CNAME (alias) record is configured, and the CNAME record is used to map multiple domain names to the same.
  • the IP address of the MX (Mailbox) record is configured.
  • the MX record is used to indicate the route of the mail server corresponding to the domain name.
  • the specific content and configuration of the above-mentioned resolution task are the same as those in the prior art, and are not described here.
  • the generating queues in the embodiment of the present application may be configured with a cache queue in advance. After receiving the parsing tasks of different domain names, the parsing tasks may be added to the cache queue according to the received chronological order.
  • the server can obtain the cached parsing task from the cache queue. In order to distinguish it from the subsequent parsing task, the parsing task cached in the cache queue is called the original parsing task.
  • Step 202 Combine the original parsing tasks according to a preset rule to generate an independent parsing task of different domain names.
  • the cache queue caches multiple resolution tasks of different domain names, you can obtain the original resolution tasks of the same domain name in the original resolution tasks. You can use the different domain names as keywords to search for the same from the cache queue.
  • the original parsing task of the same domain name, the original parsing task of the same RR (Resource Record) type, the RR type may include: WWW type and mail type;
  • the original resolution task of the same RR type has a resolution task with a dependency on the time. Therefore, the original resolution tasks of the same RR type can be combined to generate an independent resolution task corresponding to the same RR type.
  • the domain name A contains two A configuration task belonging to the WWW type is configured to record A records and configure CNAME records.
  • Step 203 Generate domain name resolution of different domain names by performing distributed processing on the independent resolution task.
  • each independent parsing task in the merged independent parsing task may be sent to the corresponding distributed processing queue, and then each distributed processing queue corresponding to the parsing production thread is called to each distributed processing queue.
  • the independent resolution task in the process is parsed, and the corresponding domain name resolution is generated, and the generated domain name resolutions belonging to the same domain name are summarized, and the domain name resolution corresponding to the same domain name is obtained.
  • the method for parsing different independent parsing tasks is consistent with the description in the prior art, and is not described here.
  • the difference between the current embodiment and the existing single-queue processing parsing task is that the distributed processing queue is used. Parallel processing of multiple independent resolution tasks to improve the efficiency of domain name resolution.
  • this embodiment caches the original parsing task, so the original cache can be used.
  • the initial parsing task is unified analysis, so that the original parsing tasks with dependencies in time can be merged to generate independent parsing tasks, and the independent parsing tasks can be processed in a distributed manner to perform parallel processing to generate domain names of different domain names. Analysis. Since the number of parsing tasks that need to be processed can be reduced by merging the original parsing tasks, and because the single independent queue processing of the merged independent parsing tasks is not required, the distributed processing manner is used to parallelize different independent parsing tasks. While making full use of the generated resources on the server, the efficiency of domain name resolution is effectively improved.
  • FIG. 3A is a flowchart of another embodiment of a method for generating domain name resolution according to the present application. This embodiment describes a process for generating domain name resolution in detail:
  • Step 301 Receive original parsing tasks of different domain names.
  • the embodiment of the present application can be completed on the generation server, and the generation server communicates with the cloud server to generate domain name resolution for the registered domain name of the website corresponding to different VMs on the cloud server, where each domain name corresponds to multiple resolutions.
  • the task generates domain name resolution by performing these parsing tasks.
  • These parsing tasks may include: configuring the parsing task of the A record, the A record is used to specify the IP address corresponding to the domain name; configuring the parsing task of the CNAME record, the CNAME record is used to map multiple domain names to the same IP address; configuring the parsing of the MX record The MX record is used to indicate the route of the mail server corresponding to the domain name.
  • the parsing task received before the merge processing is referred to as the original parsing task, in order to distinguish it from the parsing task that is subsequently merged.
  • Step 302 Add the original parsing task to the cache queue according to the received chronological order.
  • a cache queue is preset on the build server, which is used to cache the original parsing tasks of different domain names. After the generating server receives the original parsing task of different domain names, the original parsing task may be added to the cache queue according to the received chronological order.
  • Step 303 Obtain an original parsing task of different domain names from the cache queue.
  • Step 304 Acquire original parsing tasks belonging to the same domain name in the original parsing task.
  • the cache queue caches multiple resolution tasks of different domain names
  • the original resolution task of different domain names is obtained from the cache queue
  • the original domain name belonging to the same domain name can be searched from the cache queue by using different domain names as keywords. task.
  • Step 305 Analyze the original parsing task of the same RR type in the original parsing task of the same domain name.
  • the RR type may include: a WWW type and a mail type.
  • Step 306 Combine the original resolution tasks belonging to the same RR type to generate an independent resolution task corresponding to the same RR type.
  • the original parsing task of the same RR type has the resolving task of the same RR type. Therefore, the original parsing tasks of the same RR type can be merged to generate independent parsing tasks corresponding to the same RR type. Correlation and conflict.
  • the generating server can analyze the original parsing task of the same resolving task type in the original parsing task of the same RR type.
  • the parsing task type of the WWW type can include: A record, CNAME record, etc.;
  • the last parsing task that joins the cache queue can be selected from the original parsing tasks belonging to the same parsing task type as an independent parsing task, and the original parsing tasks belonging to the same parsing task type are deleted except for independent parsing.
  • Other original parsing tasks for the task For example, the A record resolution task whose domain name is "my3w.com” and whose RR type is "WWW" is obtained from the cache queue.
  • the order of joining the cache queue is the A of "www.my3w.com".
  • the record is configured to point to the IP address "1.2.3.4”
  • the A record of "www.my3w.com” is configured to point to the IP address "2.2.2.2", in which case it can be reserved according to the chronological order, "www.my3w.
  • the A record of com is configured to point to the IP address "2.2.2.2", and deletes the A record of "www.my3w.com” to point to the IP address "1.2.3.4".
  • the generation server can retain the original resolution task with the highest priority among the original resolution tasks of the same RR type as the independent resolution task, and delete the original resolution tasks belonging to the same RR type.
  • Other original parsing tasks in addition to the independent parsing tasks.
  • the A record resolution task and the CNAME resolution task whose domain name is "my3w.com” and whose RR type is "WWW" are obtained from the cache queue.
  • the configuration task of configuring the A record needs to be "www.my3w.com”.
  • Step 307 Send each independent resolution task in the independent resolution task to the corresponding distributed processing queue.
  • step 306 After the merge process of the foregoing step 306, conflicts and dependencies are eliminated between the original parsing tasks originally cached in the cache queue, and several independent parsing tasks are generated. In this step, several independent parsing tasks are respectively sent to the corresponding distributed processing queue for processing.
  • Step 308 Invoke the parsing production thread corresponding to each distributed processing queue to parse the independent parsing task in each distributed processing queue, and generate corresponding domain name resolution.
  • Step 309 The generated domain name resolutions of the same domain name are summarized, and the domain name resolution corresponding to the same domain name is obtained.
  • FIG. 3B a schematic diagram of distributed processing of independent parsing tasks in steps 307 to 309 above is shown.
  • the manner in which the parsing of the production thread to parse the independent parsing task in the embodiment is consistent with the description in the prior art, and details are not described herein again.
  • the embodiment caches the original parsing task, so that the original parsing task of the cache can be uniformly analyzed, so that the original parsing tasks having dependencies in time can be merged to generate an independent parsing task.
  • the independent resolution tasks can be distributed processing, and parallel processing can be performed to generate domain name resolution of different domain names. Since the number of parsing tasks that need to be processed can be reduced by merging the original parsing tasks, and because the single independent queue processing of the merged independent parsing tasks is not required, the distributed processing manner is used to parallelize different independent parsing tasks. While making full use of the generated resources on the server, the efficiency of domain name resolution is effectively improved.
  • An embodiment of the apparatus for generating domain name resolution in the present application can be applied to a generation server.
  • the device embodiment may be implemented by software, or may be implemented by hardware or a combination of hardware and software. Taking the software implementation as an example, as a logical means, the processor of the device in which it is located reads the corresponding computer program instructions in the non-volatile memory into the memory. From a hardware level, as shown in FIG. 4, a hardware structure diagram of a generation server where the device for generating domain name resolution is generated by the present application, except for the processor, the memory, the network interface, and the non-volatile memory shown in FIG. In addition, the generation server where the device is located in the embodiment usually includes other hardware according to the actual function of the device, which is not shown in FIG. 4 .
  • FIG. 5 it is a block diagram of an embodiment of an apparatus for generating domain name resolution according to the present application:
  • the apparatus includes an acquisition unit 510, a merging unit 520, and a generating unit 530.
  • the obtaining unit 510 is configured to obtain an original parsing task of different domain names from the cache queue.
  • the merging unit 520 is configured to combine the original parsing tasks according to a preset rule to generate an independent parsing task of the different domain name.
  • the generating unit 530 is configured to generate domain name resolution of different domain names by performing distributed processing on the independent parsing task.
  • FIG. 6 a block diagram of another embodiment of an apparatus for generating domain name resolution according to the present application is as follows:
  • the apparatus includes: a receiving unit 610, an adding unit 620, an obtaining unit 630, a merging unit 640, and a generation list Yuan 650.
  • the receiving unit 610 is configured to receive an original parsing task of different domain names.
  • the adding unit 620 is configured to add the original parsing task to the cache queue according to the received chronological order;
  • the obtaining unit 630 is configured to obtain an original parsing task of different domain names from the cache queue.
  • the merging unit 640 is configured to combine the original parsing tasks according to a preset rule to generate an independent parsing task of the different domain name.
  • the generating unit 650 is configured to generate domain name resolution of different domain names by performing distributed processing on the independent parsing task.
  • the merging unit 640 can include (not shown in FIG. 6):
  • a task obtaining sub-unit configured to separately acquire an original parsing task belonging to the same domain name in the original parsing task
  • a task analysis sub-unit configured to analyze an original parsing task of the same resource record RR type in the original parsing task of the same domain name
  • the task merging sub-unit is configured to combine the original parsing tasks belonging to the same RR type to generate independent parsing tasks corresponding to the same RR type.
  • the task merging sub-unit may be specifically configured to analyze an original parsing task belonging to the same parsing task type in the original parsing task of the same RR type, and have a dependency relationship between the original parsing tasks belonging to the same parsing task type. And selecting, from the original parsing task belonging to the same parsing task type, the last parsing task that joins the caching queue as an independent parsing task, and deleting the original parsing task belonging to the same parsing task type, except the independent parsing Other original parsing tasks for the task.
  • the task merging sub-unit may be specifically configured to: when the original parsing tasks belonging to the same RR type have a conflict relationship, retain the original parsing task with the highest priority among the original parsing tasks of the same RR type as independent analysis. The task, and deleting other original parsing tasks of the original parsing task belonging to the same RR type except the independent parsing task.
  • the generating unit 650 can include (not shown in FIG. 6):
  • the task is sent to the sub-unit, and each of the independent parsing tasks is sent to the corresponding sub-segment Cloth processing queue;
  • the thread calling subunit is configured to call the parsing production thread corresponding to each distributed processing queue to parse the independent parsing task in each distributed processing queue, and generate corresponding domain name resolution;
  • the summary generation sub-unit is configured to summarize the generated domain name resolutions belonging to the same domain name, and obtain domain name resolution corresponding to the same domain name.
  • the device embodiment since it basically corresponds to the method embodiment, reference may be made to the partial description of the method embodiment.
  • the device embodiments described above are merely illustrative, wherein the units described as separate components may or may not be physically separate, and the components displayed as units may or may not be physical units, ie may be located A place, or it can be distributed to multiple network units. Some or all of the modules may be selected according to actual needs to achieve the objectives of the present application. Those of ordinary skill in the art can understand and implement without any creative effort.
  • the original parsing task of the cache can be uniformly analyzed, so that the original parsing tasks with dependencies in time can be merged to generate independent parsing tasks, and independently parsed.
  • Distributed processing can be used between tasks to perform parallel processing to generate domain name resolution for different domain names. Since the number of parsing tasks that need to be processed can be reduced by merging the original parsing tasks, and because the single independent queue processing of the merged independent parsing tasks is not required, the distributed processing manner is used to parallelize different independent parsing tasks. While making full use of the generated resources on the server, the efficiency of domain name resolution is effectively improved.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

本申请公开了生成域名解析的方法、装置及服务器，所述方法包括：从缓存队列中获取不同域名的原始解析任务；按照预设规则对所述原始解析任务进行合并，生成所述不同域名的独立解析任务；通过对所述独立解析任务进行分布式处理，生成不同域名的域名解析。本申请实施例通过对原始解析任务合并可以减少需要处理的解析任务的数量，并且由于无需对合并后的独立解析任务进行单队列处理，而是采用分布式处理方式对不同的独立解析任务进行并行处理，因此在充分利用服务器上的生成资源的同时，有效提高了域名解析的生成效率。

Description

生成域名解析的方法、装置及服务器
本申请要求2015年04月28日递交的申请号为201510209833.3、发明名称为“生成域名解析的方法、装置及服务器”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及网络通信技术领域，尤其涉及生成域名解析的方法、装置及服务器。
背景技术
云服务是基于互联网的相关服务的增加、使用和交付模式，随着虚拟技术的发展，在云服务系统中，可以通过虚拟化技术在一台云服务器的硬件平台上虚拟出若干虚拟化平台，每个虚拟化平台可以对应一台VM(Virtual Machine，虚拟机)。现有技术中，云服务器上的每台VM都可以对应一个网站的主域名，进一步每个主域名下可能对应多个子域名，为了使用户可以访问这些主域名或者子域名对应的网站资源，生成域名解析的服务器需要为这些域名生成相应的域名解析，以便将这些域名指向对应网站的IP(Internet Protocol，互联网协议)地址，从而可以使用户可以访问到这些主域名或者子域名对应的网站资源。
但是，生成域名解析的服务器在通过执行解析任务，为不同域名生成域名解析的过程中，由于同一域名的不同解析任务在执行时会存在时间上的先后依赖关系，因此需要服务器对这些解析任务按照其产生的时间先后顺序，进行单队列处理，从而在有大量解析任务并发时，会导致生成域名解析的效率较低，浪费服务器上的生成资源。
发明内容
本申请提供生成域名解析的方法、装置及服务器，以解决现有生成域名解析的效率较低，容易浪费服务器上生成资源的问题。
根据本申请实施例的第一方面，提供一种生成域名解析的方法，所述方法包括：
从缓存队列中获取不同域名的原始解析任务；
按照预设规则对所述原始解析任务进行合并，生成所述不同域名的独立解析任务；
通过对所述独立解析任务进行分布式处理，生成不同域名的域名解析。
根据本申请实施例的第二方面，提供一种生成域名解析的装置，所述装置包括：
获取单元，用于从缓存队列中获取不同域名的原始解析任务；
合并单元，用于按照预设规则对所述原始解析任务进行合并，生成所述不同域名的独立解析任务；
生成单元，用于通过对所述独立解析任务进行分布式处理，生成不同域名的域名解析。
根据本申请实施例的第三方面，提供一种服务器，包括：
处理器；用于存储所述处理器可执行指令的存储器；
其中，所述处理器被配置为：
从缓存队列中获取不同域名的原始解析任务；
按照预设规则对所述原始解析任务进行合并，生成所述不同域名的独立解析任务；
通过对所述独立解析任务进行分布式处理，生成不同域名的域名解析。
应用本申请实施例，通过对原始解析任务进行缓存，因此可以对缓存的原始解析任务进行统一分析，从而可以将在时间上具有依赖关系的原始解析任务进行合并，生成独立解析任务，并且独立解析任务之间可以采用分布式处理方式，进行并行处理从而生成不同域名的域名解析。由于通过对原始解析任务合并可以减少需要处理的解析任务的数量，并且由于无需对合并后的独立解析任务进行单队列处理，而是采用分布式处理方式对不同的独立解析任务进行并行处理，因此在充分利用服务器上的生成资源的同时，有效提高了域名解析的生成效率。
应当理解的是，以上的一般描述和后文的细节描述仅是示例性和解释性的，并不能限制本申请。
附图说明
此处的附图被并入说明书中并构成本说明书的一部分，示出了符合本申请的实施例，并与说明书一起用于解释本申请的原理。
图1为本申请生成域名解析的应用场景示意图；
图2为本申请生成域名解析的方法的一个实施例流程图；
图3A为本申请生成域名解析的方法的另一个实施例流程图
图3B为图3A中对独立解析任务进行分布式处理的示意图；
图4为本申请生成域名解析的装置所在服务器的一种硬件结构图；
图5为本申请生成域名解析的装置的一个实施例框图；
图6为本申请生成域名解析的装置的另一个实施例框图。
具体实施方式
在本申请使用的术语是仅仅出于描述特定实施例的目的，而非旨在限制本申请。在本申请和所附权利要求书中所使用的单数形式的“一种”、“所述”和“该”也旨在包括多数形式，除非上下文清楚地表示其他含义。还应当理解，本文中使用的术语“和/或”是指并包含一个或多个相关联的列出项目的任何或所有可能组合。
应当理解，尽管在本申请可能采用术语第一、第二、第三等来描述各种信息，但这些信息不应限于这些术语。这些术语仅用来将同一类型的信息彼此区分开。例如，在不脱离本申请范围的情况下，第一信息也可以被称为第二信息，类似地，第二信息也可以被称为第一信息。取决于语境，如在此所使用的词语“如果”可以被解释成为“在……时”或“当……时”或“响应于确定”。
参见图1，为应用本申请实施例生成域名解析的应用场景示意图：
图1中示出了一种云服务系统，本申请实施例基于该云服务系统生成域名解析，该云服务器系统中包括云服务器和生成域名解析的服务器(后续本申请实施例中简称为生成服务器)。其中，在云服务器上设置了n(n为大于1的自然数)个VM，每个VM可以提供给一个网站，用于存储该网站的网站资源，每个网站通过所分配的IP地址进行标识。用户可以通过输入网站注册的域名对网站资源进行访问，在访问过程中DNS服务器可以将域名转换为网站的IP地址，从而完成对上述访问。由此可知，要实现用户通过域名访问到不同的网站资源，需要生成服务器预先执行不同域名的解析任务，从而为不同域名生成域名解析，以便后续遵循生成的域名解析结果完成从域名到IP地址的转换。
现有技术中生成服务器在生成每个域名的域名解析时，采用单队列处理方式执行不同域名的解析任务，因此效率较低。本申请实施例中，生成服务器可以对不同域名的解析任务进行合并，并采用分布式队列处理合并后的解析任务，因此处理效率较高，可以充分利用生成服务器上的解析资源。下面结合附图对本申请生成域名解析的实施例进行详细描述。
参见图2，为本申请生成域名解析的方法的一个实施例流程图，该实施例从生成服务器侧进行描述：
步骤201：从缓存队列中获取不同域名的原始解析任务。
生成服务器在为不同域名生成域名解析的过程中，每个域名都会对应多个解析任务， 通过执行这些解析任务，从而生成域名解析。这些解析任务可以包括：配置A(Address，地址)记录的解析任务，A记录用于指定域名对应的IP地址；配置CNAME(别名)记录的解析任务，CNAME记录用于将多个域名映射到同一IP地址；配置MX(Mailbox，邮箱)记录的解析任务，MX记录用于指示域名对应的邮件服务器的路由；上述解析任务的具体内容和配置方式与现有技术一致，在此不再赘述。
本申请实施例中的生成服务器上可以预先设置缓存队列，当接收到不同域名的解析任务后，可以按照接收的时间先后顺序将这些解析任务添加到缓存队列中，当要生成域名解析时，生成服务器可以从缓存队列中获取已缓存的解析任务，为了区别于后续经过合并处理的解析任务，将缓存队列中缓存的解析任务称为原始解析任务。
步骤202：按照预设规则对原始解析任务进行合并，生成不同域名的独立解析任务。
由于缓存队列中缓存了不同域名的多个解析任务，因此可以先分别获取这些原始解析任务中属于同一域名的原始解析任务，此时可以以不同的域名为关键字从缓存队列中搜索出属于同一域名的解析任务；对于同一域名的原始解析任务，可以分析这些原始解析任务中属于同一RR(Resource Record，资源记录)类型的原始解析任务，其中RR类型可以包括：WWW类型和mail类型；通常属于同一RR类型的原始解析任务中存在时间上具有依赖关系的解析任务，因此可以将属于同一RR类型的原始解析任务进行合并，生成同一RR类型对应的独立解析任务，例如，域名A下包含两条属于WWW类型的解析任务，分别为配置A记录和配置CNAME记录，由于上述两个解析任务冲突，即同一域名不能同时即配置A记录又配置CNAME记录，因此保留优先级较高的配置A记录的解析任务，并删除配置CNAME记录的解析任务，从而完成将属于同一RR类型的两条原始解析任务合并为一条该RR类型对应的独立解析任务。
步骤203：通过对独立解析任务进行分布式处理，生成不同域名的域名解析。
本实施例中，可以将合并后的独立解析任务中的每个独立解析任务下发给对应的分布式处理队列，然后调用每个分布式处理队列对应的解析生产线程对每个分布式处理队列中的独立解析任务进行解析，生成对应的域名解析，将所生成的属于同一域名的域名解析进行汇总，得到对应同一域名的域名解析。其中，对不同的独立解析任务进行解析的方式与现有技术中的描述一致，在此不再赘述，本申请实施例与现有采用单队列方式处理解析任务的不同在于，采用分布式处理队列对多个独立解析任务进行并行处理，从而提高域名解析的生成效率。
由上述实施例可见，该实施例通过对原始解析任务进行缓存，因此可以对缓存的原 始解析任务进行统一分析，从而可以将在时间上具有依赖关系的原始解析任务进行合并，生成独立解析任务，并且独立解析任务之间可以采用分布式处理方式，进行并行处理从而生成不同域名的域名解析。由于通过对原始解析任务合并可以减少需要处理的解析任务的数量，并且由于无需对合并后的独立解析任务进行单队列处理，而是采用分布式处理方式对不同的独立解析任务进行并行处理，因此在充分利用服务器上的生成资源的同时，有效提高了域名解析的生成效率。
参见图3A，为本申请生成域名解析的方法的另一个实施例流程图，该实施例对生成域名解析的过程进行详细描述：
步骤301：接收不同域名的原始解析任务。
结合图1可知，本申请实施例可以在生成服务器上完成，生成服务器与云服务器进行通信，统一为云服务器上不同VM所对应网站的注册域名生成域名解析，其中每个域名都会对应多个解析任务，通过执行这些解析任务，从而生成域名解析。这些解析任务可以包括：配置A记录的解析任务，A记录用于指定域名对应的IP地址；配置CNAME记录的解析任务，CNAME记录用于将多个域名映射到同一IP地址；配置MX记录的解析任务，MX记录用于指示域名对应的邮件服务器的路由；上述解析任务的具体内容和配置方式与现有技术一致，在此不再赘述。其中，为了区别于后续经过合并处理的解析任务，将合并处理前接收到的解析任务称为原始解析任务。
步骤302：将原始解析任务按照接收的时间先后顺序添加到缓存队列中。
生成服务器上预先设置了缓存队列，该缓存队列用于缓存不同域名的原始解析任务。当生成服务器接收到不同域名的原始解析任务后，可以将原始解析任务按照接收的时间先后顺序添加到上述缓存队列中。
步骤303：从缓存队列中获取不同域名的原始解析任务。
步骤304：分别获取原始解析任务中属于同一域名的原始解析任务。
由于缓存队列中缓存了不同域名的多个解析任务，因此在从缓存队列中获取到不同域名的原始解析任务后，可以以不同的域名为关键字从缓存队列中搜索出属于同一域名的原始解析任务。
步骤305：分析同一域名的原始解析任务中，属于同一RR类型的原始解析任务。
对于同一域名的原始解析任务，可以分析这些原始解析任务中属于同一RR类型的原始解析任务，以便后续对同一RR类型的原始解析任务进行合并。其中RR类型可以包括：WWW类型和mail类型。
步骤306：将属于同一RR类型的原始解析任务进行合并，生成同一RR类型对应的独立解析任务。
通常属于同一RR类型的原始解析任务中存在时间上具有依赖关系的解析任务，因此可以将属于同一RR类型的原始解析任务进行合并，生成同一RR类型对应的独立解析任务，以消除原始解析任务之间的相关性和冲突性。
在一个可选的实现方式中：
生成服务器可以分析同一RR类型的原始解析任务中，属于同一解析任务类型的原始解析任务，其中RR类型为WWW类型的解析任务类型可以包括：A记录、CNAME记录等；当属于同一解析任务类型的原始解析任务之间具有依赖关系时，可以从属于同一解析任务类型的原始解析任务中选择最后一个加入缓存队列的解析任务作为独立解析任务，删除属于同一解析任务类型的原始解析任务中除独立解析任务的其他原始解析任务。例如，从缓存队列中获取到两条域名为“my3w.com”，RR类型为“WWW”的A记录解析任务，按照其加入缓存队列的先后顺序分别为将“www.my3w.com”的A记录配置为指向IP地址“1.2.3.4”，以及将“www.my3w.com”的A记录配置为指向IP地址“2.2.2.2”，此时可以根据时间先后顺序，保留将“www.my3w.com”的A记录配置为指向IP地址“2.2.2.2”，并删除将“www.my3w.com”的A记录配置为指向IP地址“1.2.3.4”。
在另一个可选的实现方式中：
当属于同一RR类型的原始解析任务之间具有冲突关系时，生成服务器可以保留同一RR类型的原始解析任务中优先级最高的原始解析任务作为独立解析任务，并删除属于同一RR类型的原始解析任务中除所述独立解析任务的其他原始解析任务。例如，从缓存队列中分别获取到两条域名为“my3w.com”，RR类型为“WWW”的A记录解析任务和CNAME解析任务，其中配置A记录的解析任务需要将“www.my3w.com”指向IP地址1，而配置CNAME的解析任务需要将“www.my3w.com”指向IP地址2，因此上述两个解析任务之间发生冲突，由于A记录的解析任务优先级高于CNAME记录的解析任务，因此保留将“www.my3w.com”指向IP地址1，完成配置A记录的解析任务，并且从缓存队列中删除为“www.my3w.com”配置CNAME记录的解析任务。
步骤307：将独立解析任务中的每个独立解析任务下发给对应的分布式处理队列。
在通过前述步骤306的合并处理后，缓存队列中原来缓存的原始解析任务之间消除了冲突和依赖，生成了若干独立解析任务。本步骤中，将若干独立解析任务分别下发给对应的分布式处理队列进行处理。
步骤308：调用每个分布式处理队列对应的解析生产线程对每个分布式处理队列中的独立解析任务进行解析，生成对应的域名解析。
步骤309：将所生成的属于同一域名的域名解析进行汇总，得到对应同一域名的域名解析。
参见图3B，为上述步骤307至步骤309中对独立解析任务进行分布式处理的示意图。本实施例中调用解析生产线程对独立解析任务进行解析的方式与现有技术中的描述一致，在此不再赘述。
由上述实施例可见，该实施例通过对原始解析任务进行缓存，因此可以对缓存的原始解析任务进行统一分析，从而可以将在时间上具有依赖关系的原始解析任务进行合并，生成独立解析任务，并且独立解析任务之间可以采用分布式处理方式，进行并行处理从而生成不同域名的域名解析。由于通过对原始解析任务合并可以减少需要处理的解析任务的数量，并且由于无需对合并后的独立解析任务进行单队列处理，而是采用分布式处理方式对不同的独立解析任务进行并行处理，因此在充分利用服务器上的生成资源的同时，有效提高了域名解析的生成效率。
本申请生成域名解析的装置的实施例可以应用在生成服务器上。装置实施例可以通过软件实现，也可以通过硬件或者软硬件结合的方式实现。以软件实现为例，作为一个逻辑意义上的装置，是通过其所在设备的处理器将非易失性存储器中对应的计算机程序指令读取到内存中运行形成的。从硬件层面而言，如图4所示，为本申请生成域名解析的装置所在生成服务器的一种硬件结构图，除了图4所示的处理器、内存、网络接口、以及非易失性存储器之外，实施例中装置所在的生成服务器通常根据器实际功能，还可以包括其他硬件，图4中不再一一示出。
参见图5，为本申请生成域名解析的装置的一个实施例框图：
该装置包括：获取单元510、合并单元520和生成单元530。
期中，获取单元510，用于从缓存队列中获取不同域名的原始解析任务；
合并单元520，用于按照预设规则对所述原始解析任务进行合并，生成所述不同域名的独立解析任务；
生成单元530，用于通过对所述独立解析任务进行分布式处理，生成不同域名的域名解析。
参见图6，为本申请生成域名解析的装置的另一个实施例框图：
该装置包括：接收单元610、添加单元620、获取单元630、合并单元640和生成单 元650。
其中，接收单元610，用于接收不同域名的原始解析任务；
添加单元620，用于将所述原始解析任务按照接收的时间先后顺序添加到所述缓存队列中；
获取单元630，用于从缓存队列中获取不同域名的原始解析任务；
合并单元640，用于按照预设规则对所述原始解析任务进行合并，生成所述不同域名的独立解析任务；
生成单元650，用于通过对所述独立解析任务进行分布式处理，生成不同域名的域名解析。
在一个可选的实现方式中：
所述合并单元640可以包括(图6中未示出)：
任务获取子单元，用于分别获取所述原始解析任务中属于同一域名的原始解析任务；
任务分析子单元，用于分析所述同一域名的原始解析任务中，属于同一资源记录RR类型的原始解析任务；
任务合并子单元，用于将所述属于同一RR类型的原始解析任务进行合并，生成所述同一RR类型对应的独立解析任务。
在另一个可选的实现方式中：
所述任务合并子单元，可以具体用于分析所述同一RR类型的原始解析任务中，属于同一解析任务类型的原始解析任务，当所述属于同一解析任务类型的原始解析任务之间具有依赖关系时，从所述属于同一解析任务类型的原始解析任务中选择最后一个加入所述缓存队列的解析任务作为独立解析任务，并删除所述属于同一解析任务类型的原始解析任务中除所述独立解析任务的其他原始解析任务。
在另一个可选的实现方式中：
所述任务合并子单元，可以具体用于当所述属于同一RR类型的原始解析任务之间具有冲突关系时，保留所述同一RR类型的原始解析任务中优先级最高的原始解析任务作为独立解析任务，并删除所述属于同一RR类型的原始解析任务中除所述独立解析任务的其他原始解析任务。
在另一个可选的实现方式中：
所述生成单元650可以包括(图6中未示出)：
任务下发子单元，用于将所述独立解析任务中的每个独立解析任务下发给对应的分 布式处理队列；
线程调用子单元，用于调用每个分布式处理队列对应的解析生产线程对每个分布式处理队列中的独立解析任务进行解析，生成对应的域名解析；
汇总生成子单元，用于将所生成的属于同一域名的域名解析进行汇总，得到对应同一域名的域名解析。
上述装置中各个单元的功能和作用的实现过程具体详见上述方法中对应步骤的实现过程，在此不再赘述。
对于装置实施例而言，由于其基本对应于方法实施例，所以相关之处参见方法实施例的部分说明即可。以上所描述的装置实施例仅仅是示意性的，其中所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部模块来实现本申请方案的目的。本领域普通技术人员在不付出创造性劳动的情况下，即可以理解并实施。
由上述实施例可见，通过对原始解析任务进行缓存，因此可以对缓存的原始解析任务进行统一分析，从而可以将在时间上具有依赖关系的原始解析任务进行合并，生成独立解析任务，并且独立解析任务之间可以采用分布式处理方式，进行并行处理从而生成不同域名的域名解析。由于通过对原始解析任务合并可以减少需要处理的解析任务的数量，并且由于无需对合并后的独立解析任务进行单队列处理，而是采用分布式处理方式对不同的独立解析任务进行并行处理，因此在充分利用服务器上的生成资源的同时，有效提高了域名解析的生成效率。
本领域技术人员在考虑说明书及实践这里公开的发明后，将容易想到本申请的其它实施方案。本申请旨在涵盖本申请的任何变型、用途或者适应性变化，这些变型、用途或者适应性变化遵循本申请的一般性原理并包括本申请未公开的本技术领域中的公知常识或惯用技术手段。说明书和实施例仅被视为示例性的，本申请的真正范围和精神由下面的权利要求指出。
应当理解的是，本申请并不局限于上面已经描述并在附图中示出的精确结构，并且可以在不脱离其范围进行各种修改和改变。本申请的范围仅由所附的权利要求来限制。

Claims (13)

  1. 一种生成域名解析的方法，其特征在于，所述方法包括：
    从缓存队列中获取不同域名的原始解析任务；
    按照预设规则对所述原始解析任务进行合并，生成所述不同域名的独立解析任务；
    通过对所述独立解析任务进行分布式处理，生成不同域名的域名解析。
  2. 根据权利要求1所述的方法，其特征在于，还包括：
    接收不同域名的原始解析任务；
    将所述原始解析任务按照接收的时间先后顺序添加到所述缓存队列中。
  3. 根据权利要求1所述的方法，其特征在于，所述按照预设规则对所述原始解析任务进行合并，生成所述不同域名的独立解析任务，包括：
    分别获取所述原始解析任务中属于同一域名的原始解析任务；
    分析所述同一域名的原始解析任务中，属于同一资源记录RR类型的原始解析任务；
    将所述属于同一RR类型的原始解析任务进行合并，生成所述同一RR类型对应的独立解析任务。
  4. 根据权利要求3所述的方法，其特征在于，所述将所述属于同一RR类型的原始解析任务进行合并，生成所述同一RR类型对应的独立解析任务，包括：
    分析所述同一RR类型的原始解析任务中，属于同一解析任务类型的原始解析任务；
    当所述属于同一解析任务类型的原始解析任务之间具有依赖关系时，从所述属于同一解析任务类型的原始解析任务中选择最后一个加入所述缓存队列的解析任务作为独立解析任务；
    删除所述属于同一解析任务类型的原始解析任务中除所述独立解析任务的其他原始解析任务。
  5. 根据权利要求3所述的方法，其特征在于，所述将所述属于同一RR类型的原始解析任务进行合并，生成所述同一RR类型对应的独立解析任务，包括：
    当所述属于同一RR类型的原始解析任务之间具有冲突关系时，保留所述同一RR类型的原始解析任务中优先级最高的原始解析任务作为独立解析任务；
    删除所述属于同一RR类型的原始解析任务中除所述独立解析任务的其他原始解析任务。
  6. 根据权利要求1至5任一所述的方法，其特征在于，所述通过对所述独立解析任务进行分布式处理，生成不同域名的域名解析，包括：
    将所述独立解析任务中的每个独立解析任务下发给对应的分布式处理队列；
    调用每个分布式处理队列对应的解析生产线程对每个分布式处理队列中的独立解析任务进行解析，生成对应的域名解析；
    将所生成的属于同一域名的域名解析进行汇总，得到对应同一域名的域名解析。
  7. 一种生成域名解析的装置，其特征在于，所述装置包括：
    获取单元，用于从缓存队列中获取不同域名的原始解析任务；
    合并单元，用于按照预设规则对所述原始解析任务进行合并，生成所述不同域名的独立解析任务；
    生成单元，用于通过对所述独立解析任务进行分布式处理，生成不同域名的域名解析。
  8. 根据权利要求7所述的装置，其特征在于，所述装置还包括：
    接收单元，用于接收不同域名的原始解析任务；
    添加单元，用于将所述原始解析任务按照接收的时间先后顺序添加到所述缓存队列中。
  9. 根据权利要求7所述的装置，其特征在于，所述合并单元包括：
    任务获取子单元，用于分别获取所述原始解析任务中属于同一域名的原始解析任务；
    任务分析子单元，用于分析所述同一域名的原始解析任务中，属于同一资源记录RR类型的原始解析任务；
    任务合并子单元，用于将所述属于同一RR类型的原始解析任务进行合并，生成所述同一RR类型对应的独立解析任务。
  10. 根据权利要求9所述的装置，其特征在于，所述任务合并子单元，具体用于分析所述同一RR类型的原始解析任务中，属于同一解析任务类型的原始解析任务，当所述属于同一解析任务类型的原始解析任务之间具有依赖关系时，从所述属于同一解析任务类型的原始解析任务中选择最后一个加入所述缓存队列的解析任务作为独立解析任务，并删除所述属于同一解析任务类型的原始解析任务中除所述独立解析任务的其他原始解析任务。
  11. 根据权利要求9所述的装置，其特征在于，所述任务合并子单元，具体用于当所述属于同一RR类型的原始解析任务之间具有冲突关系时，保留所述同一RR类型的原始解析任务中优先级最高的原始解析任务作为独立解析任务，并删除所述属于同一 RR类型的原始解析任务中除所述独立解析任务的其他原始解析任务。
  12. 根据权利要求7至11任一所述的装置，其特征在于，所述生成单元包括：
    任务下发子单元，用于将所述独立解析任务中的每个独立解析任务下发给对应的分布式处理队列；
    线程调用子单元，用于调用每个分布式处理队列对应的解析生产线程对每个分布式处理队列中的独立解析任务进行解析，生成对应的域名解析；
    汇总生成子单元，用于将所生成的属于同一域名的域名解析进行汇总，得到对应同一域名的域名解析。
  13. 一种服务器，其特征在于，包括：
    处理器；用于存储所述处理器可执行指令的存储器；
    其中，所述处理器被配置为：
    从缓存队列中获取不同域名的原始解析任务；
    按照预设规则对所述原始解析任务进行合并，生成所述不同域名的独立解析任务；
    通过对所述独立解析任务进行分布式处理，生成不同域名的域名解析。
PCT/CN2016/079866 2015-04-28 2016-04-21 生成域名解析的方法、装置及服务器 WO2016173451A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201510209833.3A CN106161668B (zh) 2015-04-28 2015-04-28 生成域名解析的方法、装置及服务器
CN201510209833.3 2015-04-28

Publications (1)

Publication Number Publication Date
WO2016173451A1 true WO2016173451A1 (zh) 2016-11-03

Family

ID=57199021

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/079866 WO2016173451A1 (zh) 2015-04-28 2016-04-21 生成域名解析的方法、装置及服务器

Country Status (2)

Country Link
CN (1) CN106161668B (zh)
WO (1) WO2016173451A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021012663A1 (zh) * 2019-07-24 2021-01-28 网宿科技股份有限公司 一种访问日志的处理方法及装置

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107707682B (zh) * 2017-04-19 2018-07-06 贵州白山云科技有限公司 一种bind配置加载优化方法及装置
CN112887442B (zh) * 2021-01-11 2023-02-07 杭州迪普科技股份有限公司 域名解析查询请求的处理方法及装置

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103281409A (zh) * 2013-06-24 2013-09-04 广州菁英信息技术有限公司 基于tcp协议的移动互联网域名解析方法及dns服务器

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101739424B (zh) * 2008-11-13 2013-07-24 中国科学院计算机网络信息中心 一种关键词及其资源记录的转换存储方法和系统
US8224923B2 (en) * 2009-06-22 2012-07-17 Verisign, Inc. Characterizing unregistered domain names
CN103324729B (zh) * 2013-06-27 2017-03-08 小米科技有限责任公司 一种推荐多媒体资源的方法和装置

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103281409A (zh) * 2013-06-24 2013-09-04 广州菁英信息技术有限公司 基于tcp协议的移动互联网域名解析方法及dns服务器

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021012663A1 (zh) * 2019-07-24 2021-01-28 网宿科技股份有限公司 一种访问日志的处理方法及装置
US11272029B2 (en) 2019-07-24 2022-03-08 Wangsu Science & Technology Co., Ltd. Access log processing method and device

Also Published As

Publication number Publication date
CN106161668B (zh) 2019-06-28
CN106161668A (zh) 2016-11-23

Similar Documents

Publication Publication Date Title
US9917889B2 (en) Enterprise service bus routing system
US10089153B2 (en) Synchronizing load balancing state information
US9244817B2 (en) Remote debugging in a cloud computing environment
US8832271B2 (en) Identity provider instance discovery
US11425054B1 (en) User-configured multi-location service deployment and scaling
US10798222B2 (en) Apparatus for managing SDN-based in-vehicle network and control method thereof
WO2017114206A1 (zh) 短链接处理方法、装置及短链接服务器
US20210049035A1 (en) Resource Manager Integration in Cloud Computing Environments
WO2017157156A1 (zh) 一种用户请求的处理方法和装置
US10956242B1 (en) Automating the migration of web service implementations to a service provider system
CN103685590B (zh) 获取ip地址的方法及系统
WO2013104172A1 (zh) 实现负载均衡的方法、dns服务器和客户端
US9419930B2 (en) Management of connections in a messaging environment
US11030077B1 (en) Framework for testing and validating content generated by applications
CN107135242B (zh) Mongodb集群访问方法、装置及系统
US20190317783A1 (en) Methods, apparatus, and systems for providing access to serial ports of virtual machines in self-deployed virtual applications
CN109120614B (zh) 基于分布式系统的业务处理方法及装置
WO2017166524A1 (zh) 域名解析方法及装置
US11765244B1 (en) Latency-based service discovery and routing for multi-location service-oriented applications
WO2016173452A1 (zh) 解析任务的处理方法、装置及服务器
WO2016173451A1 (zh) 生成域名解析的方法、装置及服务器
US20200104750A1 (en) Hosting machine learning models
CN109413224B (zh) 报文转发方法和装置
US11134117B1 (en) Network request intercepting framework for compliance monitoring
WO2024066503A1 (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: 16785882

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

Country of ref document: EP

Kind code of ref document: A1