Domain name conflict-oriented cdn service management method and system, equipment and storage medium

Abstract

The invention relates to the technical field of computers, and discloses a domain name conflict-oriented cdn service management method and system, equipment and a storage medium, and the method comprises the steps: obtaining a target domain name application request and a cdn service request; judging whether the target domain name application request is registered or not; if not, the client is helped to apply for a corresponding target domain name as a display domain name, and a client domain name is generated; if yes, the client is helped to apply for a client domain name with a client id, and the target domain name serves as a display domain name; recording a corresponding relationship among the customer id, the customer domain name, the display domain name and the cdn service request of each customer; and identifying the customer domain name of the served customer to obtain the cdn service request so as to serve the corresponding served customer. Therefore, the corresponding cdn service request can be identified through the customer domain name, and when the same cdn service management system faces the conflict domain name, the cdn acceleration service can be realized, so that a large amount of manpower cost and equipment cost are saved.

Description

Technical Field

[0001] The present application belongs to the field of computer technology and relates to a CDN service management method, system, device, and storage medium in the face of domain name conflicts. Background Art

[0002] Domain name (English: Domain Name, abbreviated as: Domain), also known as domain name or domain, is the name of a computer or computer group on the Internet composed of a string of characters separated by dots, which is used to identify the electronic location of the computer during data transmission. A domain name can be said to be a synonym for an IP address, the purpose of which is to facilitate the memory of the latter. For example, www.ngaa.com.cn is a domain name. People can directly access www.ngaa.com.cn instead of the IP address, and then the domain name system (DNS) will convert it into an IP address that is easy for the machine to identify. In this way, people only need to remember www.ngaa.com.cn, a string of characters with special meanings, instead of meaningless numbers. If a domain name accesses a large area or has a large number of requests. CDN services can be used to provide acceleration services.

[0003] In the daily operation of CDN business, there will be proxy requests for the same domain name acceleration service from different business channels. This creates the need for different customers to configure the same domain name, serve separately, and be billed separately. In the prior art, two customers will apply for the same domain name, that is, a conflicting domain name, for CDN acceleration service. The general practice is to build two independent CDN system platforms, the first CDN system platform and the second CDN system platform. The main process is that on the first CDN system platform, the first customer applies for the target domain name for the first time. After the application is completed, the first CDN system platform provides CDN services to the first customer. When the second customer applies for a conflicting domain name, it is necessary to go through the offline manual channel and apply offline. The back-end technicians manually configure the new target domain name in the second CDN system platform to provide CDN acceleration services.

[0004] Building another independent CDN system platform, physically isolated from the online independent CDN platform, requires a lot of additional equipment sets, which increases operating costs. In addition, a large number of manual configuration operations by back-end technicians are required, which increases the complexity of the business and the probability of problems, greatly increasing the operating labor costs. Summary of the invention

[0005] In order to provide a basic understanding of some aspects of the disclosed embodiments, a brief summary is given below. The summary is not an extensive review, nor is it intended to identify key / critical components or delineate the scope of protection of these embodiments, but rather serves as a prelude to the detailed description that follows.

[0006] In order to solve the problems existing in the related art, the embodiments of the present disclosure disclose a CDN service management method and system, device, and storage medium in the face of domain name conflicts, which are used to solve the problem in the prior art that CDN acceleration services cannot be provided simultaneously when conflicting domain names are encountered in the same CDN service management system.

[0007] In some embodiments, a CDN service management method in the face of domain name conflicts is provided, the method comprising: a customer service registration step and a service provision step;

[0008] The customer service registration steps include:

[0009] Obtain target domain name application request and CDN service request;

[0010] Determine whether the target domain name application request has been registered;

[0011] If the target domain name has not been registered, we will help the customer apply for the corresponding target domain name as the display domain name and generate a customer domain name;

[0012] If the target domain name has been registered, help the customer apply for a customer domain name with a customer ID, and use the target domain name as the display domain name;

[0013] Record the correspondence between each customer's customer ID, customer domain name, display domain name and CDN service request;

[0014] The steps of providing services include:

[0015] Identify the customer domain name of the served customer to obtain CDN service requests;

[0016] According to the CDN service request, serve the corresponding customer.

[0017] Preferably, identifying the customer domain name of the served customer to obtain the CDN service request includes:

[0018] Find the corresponding customer ID based on the customer domain name of the customer being served;

[0019] Identify the corresponding customer's CDN service request based on the customer ID.

[0020] Preferably, the step of providing services further includes:

[0021] Real-time statistics of CDN service data.

[0022] Preferably, the step of providing services further includes:

[0023] Calculate CDN service fees in real time.

[0024] In some embodiments, a CDN service management system facing domain name conflicts is disclosed, a console module for receiving customer registration information;

[0025] The back-end system includes multiple device groups providing CDN services, a back-end management and control module and a database. The back-end management and control module is used to manage customer domain names, display domain names, customer IDs and CDN service requests, and provide customers' CDN service requests to the device group, and send customer domain names, display domain names, customer IDs, CDN service requests and CDN service data to the database for storage.

[0026] Preferably, the backend control module includes:

[0027] Statistics module, used to collect statistics of CDN service data in real time.

[0028] Preferably, the backend control module includes:

[0029] The billing module is used to calculate CDN service fees in real time.

[0030] Preferably, the console module is also used to display the CDN service status, including CDN service data and CDN service fees.

[0031] In some embodiments, a device is disclosed, including a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the program, the CDN service management method in the face of domain name conflicts as described above is performed.

[0032] In some embodiments, a computer-readable storage medium is disclosed, on which a computer program is stored, and the program is executed by a processor as described above as a CDN service management method in the face of domain name conflicts.

[0033] The CDN service management method, system, device, and storage medium provided by the embodiments of the present disclosure in the face of domain name conflicts can achieve the following technical effects:

[0034] When facing a CDN service request with a conflicting domain name, the disclosed embodiment will use the target domain name as the customer's display domain name, write the customer ID into another customer domain name, and record the corresponding relationship between each customer's customer ID, customer domain name, display domain name, and CDN service request; by identifying the customer domain name of the served customer, the CDN service request is obtained, and then the corresponding served customer is served. In this way, the corresponding CDN service request can be identified by the customer domain name, and when facing a conflicting domain name in the same CDN service management system, CDN acceleration services can be implemented separately, thereby saving a lot of manpower costs and equipment costs.

[0035] The above general description and the following description are exemplary and explanatory only and are not intended to limit the present application. BRIEF DESCRIPTION OF THE DRAWINGS

[0036] One or more embodiments are exemplarily described by corresponding drawings, which do not limit the embodiments. Elements with the same reference numerals in the drawings are shown as similar elements, and the drawings do not constitute a scale limitation, and wherein:

[0037] Figure 1 It is a schematic diagram of a CDN service management system facing a domain name conflict provided by an embodiment of the present disclosure;

[0038] Figure 2 It is a flow chart of a CDN service management method facing a domain name conflict provided by an embodiment of the present disclosure;

[0039] Figure 3 It is a schematic diagram of a CDN service management device facing a domain name conflict provided by an embodiment of the present disclosure. DETAILED DESCRIPTION

[0040] In order to be able to understand the features and technical contents of the embodiments of the present disclosure in more detail, the implementation of the embodiments of the present disclosure is described in detail below in conjunction with the accompanying drawings. The attached drawings are for reference only and are not used to limit the embodiments of the present disclosure. In the following technical description, for the convenience of explanation, a full understanding of the disclosed embodiments is provided through multiple details. However, one or more embodiments can still be implemented without these details. In other cases, to simplify the drawings, well-known structures and systems can be simplified for display.

[0041] The following description and accompanying drawings fully illustrate specific embodiments of the present invention so that those skilled in the art can practice them. Other embodiments may include structural, logical, electrical, process and other changes. The examples represent possible changes only. Unless explicitly required, separate components and functions are optional, and the order of operations may vary. The parts and features of some embodiments may be included in or replace the parts and features of other embodiments. The scope of the embodiments of the present invention includes the entire scope of the claims, and all available equivalents of the claims. In this article, each embodiment may be represented individually or generally by the term "invention", which is only for convenience, and if more than one invention is disclosed in fact, it is not intended to automatically limit the scope of the application to any single invention or inventive concept. In this article, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, without requiring or implying any actual relationship or order between these entities or operations. Moreover, the terms "comprises", "includes" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method or device including a series of elements includes not only those elements, but also includes other elements not explicitly listed, or also includes elements inherent to such process, method or device. In the absence of further restrictions, the elements defined by the sentence "including a..." do not exclude the presence of other identical elements in the process, method or device including the elements. The various embodiments herein are described in a progressive manner, and each embodiment focuses on the differences from other embodiments, and the same and similar parts between the various embodiments can be referred to each other. For the methods, products, etc. disclosed in the embodiments, since they correspond to the method part disclosed in the embodiments, the description is relatively simple, and the relevant parts can be referred to the method part description.

[0042] In the daily operation of CDN business, there will be proxy requests for the same domain name acceleration service from different business channels. This creates the need for different customers to configure the same domain name, serve separately, and be billed separately. In the prior art, two customers will apply for the same domain name, that is, a conflicting domain name, for CDN acceleration service. The general practice is to build two independent CDN system platforms, the first CDN system platform and the second CDN system platform. The main process is that on the first CDN system platform, the first customer applies for the target domain name for the first time. After the application is completed, the first CDN system platform provides CDN services to the first customer. When the second customer applies for a conflicting domain name, it is necessary to go through the offline manual channel and apply offline. The back-end technicians manually configure the new target domain name in the second CDN system platform to provide CDN acceleration services.

[0043] Building another independent CDN system platform, physically isolated from the online independent CDN platform, requires a lot of additional equipment sets, which increases operating costs. In addition, a large number of manual configuration operations by back-end technicians are required, which increases the complexity of the business and the probability of problems, greatly increasing the operating labor costs.

[0044] In order to solve the problems existing in the related art, the embodiments of the present disclosure disclose a CDN service management method and system, device, and storage medium in the face of domain name conflicts, which are used to solve the problem in the prior art that CDN acceleration services cannot be provided simultaneously when conflicting domain names are encountered in the same CDN service management system.

[0045] Combination Figure 1 As shown, an embodiment of the present disclosure provides a schematic diagram of a CDN service management system facing a domain name conflict. The CDN service management system facing a domain name conflict includes a console module for receiving customer registration information; a back-end system including a plurality of device groups providing CDN services, a back-end management and control module, and a database. The back-end management and control module is used to manage customer domain names, display domain names, customer IDs, and CDN service requests, and provide customer CDN service requests to the device group, and send customer domain names, display domain names, customer IDs, CDN service requests, and CDN service data to the database for storage.

[0046] Combination Figure 2 As shown, the embodiment of the present disclosure provides a CDN service management method facing a domain name conflict, including: a customer service registration step and a service provision step;

[0047] The customer service registration steps include:

[0048] S210, the console module obtains the target domain name application request and the CDN service request.

[0049] S220, the backend system determines whether the target domain name application request has been registered.

[0050] S230, if the target domain name has not been registered, the backend system helps the customer apply for the corresponding target domain name as a display domain name and generates a customer domain name.

[0051] S240, if the target domain name has been registered, the backend system helps the customer apply for a customer domain name with a customer ID, and uses the target domain name as a display domain name.

[0052] S250, the backend system records the correspondence between each customer's customer ID, customer domain name, display domain name and CDN service request.

[0053] The steps of providing services include:

[0054] S260, the backend system identifies the customer domain name of the served customer to obtain the CDN service request.

[0055] S270, the backend system serves the corresponding service customer according to the CDN service request.

[0056] It should be understood that the console module is an interactive module for input and output. In actual applications, customers fill in the target domain name application request and CDN service request through the console module. In addition, customers can view the CDN service status, including CDN service data and CDN service fees, through the console module. The target domain name is the domain name that the customer needs to display, that is, the conflicting domain names between multiple customers. The display domain name is an alias of the customer domain name.

[0057] The backend system and the console module are connected to each other and transmit data to each other. It should be noted that each customer will correspond to two domain names, one is the display domain name, which is the conflicting domain name applied by the customer and is used for external display; the other is the customer domain name, which is the domain name displayed inside the backend system. By recording the corresponding relationship between the customer domain name and the CDN service request, the corresponding CDN service is performed.

[0058] The customer service registration step should be understood as establishing a corresponding relationship database through customer registration information; the service provision step should be understood as performing accelerated CDN services for customers.

[0059] Further, the customer domain name of the served customer is identified to obtain the CDN service request, including: finding the corresponding customer ID according to the customer domain name of the served customer; and identifying the CDN service request of the corresponding customer according to the customer ID.

[0060] It should be understood that the customer domain name is accompanied by a customer ID, and each customer ID also corresponds to the customer's CDN service request. Therefore, the corresponding CDN service request can be identified by the customer domain name in the backend system, and the corresponding CDN service can be performed.

[0061] It should be noted that for customers who apply for the service for the first time, the customer ID is not included in the customer domain name. However, the customer domain name is the only domain name without a customer ID, and the CDN service request can be matched according to the domain name without a customer ID. For example, a domain name with a customer ID is www11.xiangfa.com.cn, where the number "11" is the customer ID. A domain name without a customer ID is www.xiangfa.com.cn, where there is no number. The above domain name without an ID is identified as a customer who applies for the service for the first time.

[0062] A specific example may be that agent channel 1 registers users through the console module interface or external interface, and applies for standard CDN acceleration service, and the display domain name for acceleration is www.ngaa.com.cn. Among them, the customer id is 21. If it is added successfully, the acceleration service can be provided normally, and the acceleration customer domain name of the backend system is provided: www.ngaa.com.cn. The default acceleration resolution group ngaagslb.cn suffix is ​​used, and the final resolved cname configuration domain is www.ngaa.com.cn.ngaagslb.cn. The cname configuration domain is the domain name for the domain name resolution that the service customer needs to actually dispatch user requests to the CDN service. Agent channel 1 can view statistical data through the console module, check the actual situation of the service, and billing information.

[0063] Agent channel 2 registers users through the console module interface or external interface, and applies for standard CDN acceleration service, and the display domain name for acceleration is www.ngaa.com.cn. Among them, www.ngaa.com.cn is the conflicting display domain name.

[0064] The backend system checks whether the customer domain name has been registered and generates a customer domain name with a customer ID, www76.ngaa.com.cn. The customer ID is 76. The customer domain name is automatically registered in the CDN service management system, and the corresponding alias of this domain name, that is, the display domain name of agent channel 2, is: www.ngaa.com.cn. For the corresponding relationship, see Table 1.

[0065] Table 1

[0066] Service Type Customer domain name Display domain name (alias) Customer ID Customer Name Parsing Group Name Buffer equipment group video www.ngaa.com.cn 21 Agent Channel 1 ngaagslb.cn Default Group video www76.ngaa.com.cn www.ngaa.com.cn 76 Agent Channel 2 acdngslb.cn Conflict Group 1

[0067] The conflicting acceleration resolution group acdngslb.cn suffix is ​​used, and the final resolved cname configuration domain is www76.ngaa.com.cn.acdngslb.cn. Two different acceleration resolution groups will configure corresponding different buffer device groups in advance to serve the actual HTTP requests. The service domain names configured to the two buffer device groups are all www.ngaa.com.cn, and the access log records the billing domain name as well. However, different device groups will record corresponding different customer IDs to distinguish requests from different customers.

[0068] Refer to the accelerated service process of agent channel 2, execute agent channel 3, agent channel 4...

[0069] Combination Figure 3As shown, the embodiment of the present disclosure provides a device for CDN service management in the face of domain name conflicts, including a processor and a memory. Optionally, the device may also include a communication interface and a bus. The processor, the communication interface, and the memory may communicate with each other through the bus. The communication interface may be used for information transmission. The processor may call the logic instructions in the memory to execute the CDN service management method in the face of domain name conflicts of the above embodiment.

[0070] An embodiment of the present disclosure provides a storage medium storing computer executable instructions, wherein the computer executable instructions are configured to execute the CDN service management method facing domain name conflicts.

[0071] The above-mentioned storage medium may be a transient computer-readable storage medium or a non-transient computer-readable storage medium. Non-transient storage media include: a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, and other media that can store program codes, and may also be a transient storage medium.

[0072] When facing a CDN service request with a conflicting domain name, the disclosed embodiment will use the target domain name as the customer's display domain name, write the customer ID into another customer domain name, and record the corresponding relationship between each customer's customer ID, customer domain name, display domain name, and CDN service request; by identifying the customer domain name of the served customer, the CDN service request is obtained, and then the corresponding served customer is served. In this way, the corresponding CDN service request can be identified by the customer domain name, and when facing a conflicting domain name in the same CDN service management system, CDN acceleration services can be implemented separately, thereby saving a lot of manpower costs and equipment costs.

[0073] The above description and the accompanying drawings fully illustrate the embodiments of the present disclosure so that those skilled in the art can practice them. Other embodiments may include structural, logical, electrical, process and other changes. The embodiments represent only possible changes. Unless explicitly required, separate components and functions are optional, and the order of operation may vary. The parts and features of some embodiments may be included in or replace the parts and features of other embodiments. Moreover, the words used in this application are only used to describe the embodiments and are not used to limit the claims. As used in the description of the embodiments and the claims, unless the context clearly indicates, the singular forms of "a", "an" and "the" are intended to include plural forms as well. Similarly, the term "and / or" as used in this application refers to any and all possible combinations of listings containing one or more associated ones. In addition, when used in the present application, the term "comprise" and its variants "comprises" and / or comprising refer to the presence of stated features, wholes, steps, operations, elements, and / or components, but do not exclude the presence or addition of one or more other features, wholes, steps, operations, elements, components and / or groups thereof. In the absence of further restrictions, the elements defined by the sentence "comprising a ..." do not exclude the presence of other identical elements in the process, method or device comprising the elements. In this article, each embodiment may focus on the differences from other embodiments, and the same and similar parts between the various embodiments may refer to each other. For the methods, products, etc. disclosed in the embodiments, if they correspond to the method part disclosed in the embodiments, then the relevant parts can refer to the description of the method part.

[0074] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software may depend on the specific application and design constraints of the technical solution. The technicians may use different methods for each specific application to implement the described functions, but such implementations should not be considered to exceed the scope of the embodiments of the present disclosure. The technicians may clearly understand that, for the convenience and simplicity of description, the specific working processes of the systems, systems and units described above may refer to the corresponding processes in the aforementioned method embodiments, and will not be repeated here.

[0075] The flowchart and block diagram in the accompanying drawings show the possible architecture, function and operation of the system, method and computer program product according to the embodiment of the present disclosure. In this regard, each box in the flowchart or block diagram can represent a module, a program segment or a part of the code, and the module, the program segment or a part of the code contains one or more executable instructions for realizing the specified logical function. In some alternative implementations, the functions marked in the box can also occur in a different order from the order marked in the accompanying drawings. For example, two consecutive boxes can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, which can depend on the functions involved. In the description corresponding to the flowchart and the block diagram in the accompanying drawings, the operations or steps corresponding to different boxes can also occur in a different order from the order disclosed in the description, and sometimes there is no specific order between different operations or steps. For example, two consecutive operations or steps can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, which can depend on the functions involved. Each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, may be implemented by a dedicated hardware-based system that performs the specified functions or actions, or may be implemented by a combination of dedicated hardware and computer instructions.

Claims

1. A CDN service management method facing domain name conflicts, characterized in that: The method comprises: a customer service registration step and a service provision step; The customer service registration steps include: Obtain target domain name application request and CDN service request; Determine whether the target domain name application request has been registered; If the target domain name has not been registered, we will help the customer apply for the corresponding target domain name as the display domain name and generate a customer domain name; If the target domain name has been registered, help the customer apply for a customer domain name with a customer ID, and use the target domain name as the display domain name; Record the correspondence between each customer's customer ID, customer domain name, display domain name and CDN service request; The steps of providing services include: Identify the customer domain name of the served customer to obtain CDN service requests; According to the CDN service request, serve the corresponding customer.

2. The method according to claim 1, characterized in that Identify the customer domain name of the served customer to obtain CDN service requests, including: Find the corresponding customer ID based on the customer domain name of the customer being served; Identify the corresponding customer's CDN service request based on the customer ID.

3. The method according to claim 1, characterized in that The step of providing services also includes: Real-time statistics of CDN service data.

4. The method according to claim 1, characterized in that: The step of providing services also includes: Calculate CDN service fees in real time.

5. A CDN service management system facing domain name conflicts, characterized in that: include: The console module is used to receive the customer's registration information; The back-end system includes multiple device groups providing CDN services, a back-end management and control module and a database. The back-end management and control module is used to manage customer domain names, display domain names, customer IDs and CDN service requests, and provide customers' CDN service requests to the device group, and send customer domain names, display domain names, customer IDs, CDN service requests and CDN service data to the database for storage.

6. The CDN service management system according to claim 5, characterized in that: The backend control module includes: Statistics module, used to collect statistics of CDN service data in real time.

7. The CDN service management system according to claim 5, characterized in that: The backend control module includes: The billing module is used to calculate CDN service fees in real time.

8. The CDN service management system according to claim 5, characterized in that: The console module is also used to display the CDN service status, including CDN service data and CDN service fees.

9. A device, characterized in that: The method comprises a memory, a processor and a computer program stored in the memory and executable on the processor, wherein when the processor executes the program, the method according to any one of claims 1 to 4 is implemented.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the program is executed by a processor, the method according to any one of claims 1 to 4 is implemented.

Images