Method and device for configuring route
By obtaining the corresponding relationship information between the domain name and the data channel and determining the routing strategy of the network logical address, the complexity of billing and control of different types of network data traffic in intelligent vehicle systems is solved, and refined management and efficient billing are realized.
Patent Information
- Application Number
- CN202311082869.0
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2023-08-25
- Publication Date
- 2025-03-04
AI Technical Summary
The prior art is difficult to realize the separate billing and control of different types of network data traffic in a convenient and effective manner, especially in intelligent vehicle-mounted systems, where multiple data channels are associated with different payment methods, resulting in complex management.
By obtaining the corresponding relationship information between the domain name and the data channel, a routing policy for the network logical address is determined, so that access is executed based on the policy, thereby realizing separate billing and control of different types of network data traffic.
It realizes refined management of different types of network data traffic, decouples data traffic types and applications, centrally manages data routing functions, simplifies the billing and control process, and improves efficiency and accuracy.
Smart Images

Figure CN119561896A_ABST
Abstract
Description
Technical Field
[0001] Example embodiments of the present disclosure generally relate to the field of computers, and more particularly, to methods, apparatuses, electronic devices, computer storage media, and computer program products for configuring routing. Background Art
[0002] With the rapid development of computer technology and Internet technology, more and more vehicles are equipped with intelligent vehicle systems (also called vehicle systems). With the help of intelligent vehicle systems, vehicles can provide navigation functions, Internet access functions, audio and video functions, etc. to drivers and / or passengers. The network data traffic of intelligent vehicle systems can be divided into different types. Due to the different characteristics of different types of traffic, it is often necessary to access the network through different data channels to achieve separate billing and control. Therefore, how to more conveniently and effectively achieve separate billing and control of different types of traffic has become an urgent problem to be solved. Summary of the invention
[0003] In a first aspect of the present disclosure, a method for configuring routing is provided. In the method, correspondence information between a domain name and a data channel is obtained. The correspondence information at least indicates that a first domain name corresponds to a first data channel among a plurality of data channels for accessing a network. The plurality of data channels are respectively associated with a plurality of payment methods for network data traffic. Further, a first network logical address corresponding to the first domain name is obtained, and based on the correspondence information, a routing policy for the first network logical address is determined. The routing policy indicates that the first network logical address is accessed via the first data channel. In addition, access to the first domain name is performed based on the routing policy.
[0004] In a second aspect of the present disclosure, a device for configuring routing is provided. The device includes an information acquisition module, an address acquisition module, a determination module, and an execution module. The information acquisition module is configured to: obtain correspondence information between a domain name and a data channel, the correspondence information at least indicating that a first domain name corresponds to a first data channel among multiple data channels for accessing a network, and the multiple data channels are respectively associated with multiple payment methods for network data traffic. The address acquisition module is configured to: obtain a first network logical address corresponding to the first domain name. The determination module is configured to: determine a routing policy for the first network logical address based on the correspondence information, the routing policy indicating that the first network logical address is accessed via the first data channel. The execution module is configured to: enable access to the first domain name to be executed based on the routing policy.
[0005] In a third aspect of the present disclosure, an electronic device is provided, comprising: a memory and a processor; wherein the memory is used to store one or more computer instructions, wherein the one or more computer instructions are executed by the processor to implement the method according to the first aspect of the present disclosure.
[0006] In a fourth aspect of the present disclosure, a computer-readable storage medium is provided, on which one or more computer instructions are stored, wherein the one or more computer instructions are executed by a processor to implement the method according to the first aspect of the present disclosure.
[0007] In a fifth aspect of the present disclosure, a computer program product is provided, comprising computer executable instructions, wherein the computer executable instructions implement the method according to the first aspect of the present disclosure when executed by a processor.
[0008] In the scheme for configuring routing according to each embodiment of the present disclosure, based on the correspondence between the domain name and the data channel and the network logical address corresponding to the domain name, a routing policy for the network logical address is determined, and access to the domain name is executed based on the routing policy. In this way, on the one hand, the correspondence between the domain name and the data channel can be used to implement separate billing of different types of network data traffic according to the domain name. In this way, the type of network data traffic can be decoupled from the application, so that the billing of different types of network data traffic can be managed more finely in units of domain names. On the other hand, the data routing function can be centrally managed without coupling the function to each application. In this way, separate billing and control of different types of network data traffic can be implemented more conveniently and efficiently.
[0009] It should be understood that the contents described in the summary of the present invention are not intended to limit the key features or important features of the embodiments of the present disclosure, nor are they intended to limit the scope of the present disclosure. Other features of the present disclosure will become easily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS
[0010] The above and other features, advantages and aspects of the embodiments of the present disclosure will become more apparent with reference to the following detailed description in conjunction with the accompanying drawings. In the accompanying drawings, the same or similar reference numerals represent the same or similar elements, wherein:
[0011] Figure 1 A schematic diagram showing an example environment in which various embodiments of the present disclosure can be implemented;
[0012] Figure 2 shows a signaling diagram for configuring routing according to some embodiments of the present disclosure;
[0013] Figure 3A flowchart of a routing configuration method according to some embodiments of the present disclosure is shown;
[0014] Figure 4 A block diagram illustrating an example apparatus for configuring routing according to some embodiments of the present disclosure; and
[0015] Figure 5 A block diagram is shown of a device in which one or more embodiments of the present disclosure may be implemented. DETAILED DESCRIPTION
[0016] Embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. Although certain embodiments of the present disclosure are shown in the accompanying drawings, it should be understood that the present disclosure can be implemented in various forms and should not be construed as being limited to the embodiments described herein, which are instead provided for a more thorough and complete understanding of the present disclosure. It should be understood that the drawings and embodiments of the present disclosure are only for exemplary purposes and are not intended to limit the scope of protection of the present disclosure.
[0017] In the description of the embodiments of the present disclosure, the term "including" and similar terms should be understood as open inclusion, that is, "including but not limited to". The term "based on" should be understood as "based at least in part on". The term "one embodiment" or "the embodiment" should be understood as "at least one embodiment". The terms "first", "second", etc. may refer to different or the same objects. Other explicit and implicit definitions may also be included below.
[0018] It is understandable that the data involved in this technical solution (including but not limited to the data itself, the acquisition or use of the data) shall comply with the requirements of the relevant laws, regulations and relevant provisions. Before using the technical solutions disclosed in the embodiments of this disclosure, the type, scope of use, and usage scenarios of the personal information involved in this disclosure shall be informed to the user in an appropriate manner in accordance with the relevant laws and regulations and the user's authorization shall be obtained.
[0019] For example, when obtaining any user's personal information, appropriate prompts should be given to the user so that the user can independently choose whether to provide personal information to software or hardware such as an electronic device, application, server or storage medium that executes an embodiment of the present disclosure based on the prompt information.
[0020] As used herein, the term "in response to" refers to a state in which a corresponding event occurs or a condition is satisfied. It will be understood that the timing of executing a subsequent action executed in response to the event or condition is not necessarily strongly related to the time when the event occurs or the condition is satisfied. For example, in some cases, the subsequent action may be executed immediately when the event occurs or the condition is satisfied; while in other cases, the subsequent action may be executed some time after the event occurs or the condition is satisfied.
[0021] As briefly mentioned above, the network data traffic of the smart car system can be divided into different types. For example, the network data traffic of the smart car system can be divided into the following two types: (1) car company paid traffic, which mainly includes traffic generated by the car company's own needs and to improve the basic user experience; (2) user paid traffic, which mainly includes traffic generated by user value-added experience, such as data traffic generated by users using multimedia, games, remote camera viewing and other functions.
[0022] Existing solutions often establish a binding relationship between applications and Internet access data channels. More specifically, an application is pre-bound to a data channel to enable network data traffic of different applications to go through different data channels. However, this solution of binding applications to data channels belongs to a decentralized management method, which requires many applications to make corresponding adaptations, and the adaptation cost is high. In addition, if an application needs to access two data channels at the same time, that is, part of the traffic goes through the enterprise payment channel and the other part of the traffic goes through the personal payment channel, this solution cannot meet this demand.
[0023] To this end, an embodiment of the present disclosure proposes a scheme for configuring routing based on the correspondence between domain names and data channels. Specifically, a scheme for configuring routing is proposed according to each embodiment of the present disclosure. In the scheme, correspondence information between domain names and data channels is obtained. The correspondence information at least indicates that a first domain name corresponds to a first data channel among multiple data channels for accessing a network. Multiple data channels are respectively associated with multiple payment methods for network data traffic. In addition, a first network logical address corresponding to the first domain name is obtained, and based on the correspondence information, a routing policy for the first network logical address is determined. The routing policy indicates that the first network logical address is accessed via the first data channel. Further, access to the first domain name is executed based on the routing policy.
[0024] It will be more clearly understood through the following description that according to an embodiment of the present disclosure, based on the correspondence between the domain name and the data channel and the network logical address corresponding to the domain name, a routing policy for the network logical address is determined, and access to the domain name is executed based on the routing policy. In this way, on the one hand, the correspondence between the domain name and the data channel can be used to implement separate billing of different types of network data traffic according to the domain name. In this way, the type of network data traffic can be decoupled from the application, so that the billing of different types of network data traffic can be managed more finely in units of domain names. On the other hand, the data routing function can be centrally managed without coupling the function to each application. In this way, separate billing and control of different types of network data traffic can be implemented more conveniently and efficiently.
[0025] Some example embodiments of the present disclosure will be described below with continued reference to the accompanying drawings.
[0026] Example Environment
[0027] See first Figure 1 , which shows a schematic diagram of an example environment 100 in which various embodiments of the present disclosure can be implemented. Figure 1 As shown, example environment 100 may generally include a vehicle 110 , a user 120 , and a service provider 150 .
[0028] like Figure 1 As shown, user 120 may be carried by vehicle 110. Figure 1 In the figure, the vehicle 110 is shown as a car, but the vehicle 110 may also include any appropriate type of motor vehicle or non-motor vehicle, examples of which include but are not limited to cars, sedans, trucks, buses, electric vehicles, motorcycles, etc. However, it should be understood that a vehicle is only an example of the vehicle 110. The embodiments of the present disclosure are also applicable to other vehicles other than vehicles, such as ships, trains, etc. In some embodiments, the user 120 may also be other passengers on the vehicle 110.
[0029] like Figure 1As shown, the vehicle 110 is provided with an electronic device 130 and a touch screen 140. The electronic device 130 is used, for example, to implement all or part of the functions of the in-vehicle intelligent system. The user 120 can interact with the in-vehicle intelligent system by operating the touch screen 140, for example, to use the services provided by the service provider 150. In the context of the present disclosure, the service provider 150 represents a provider of Internet service content, application services, etc. Examples of service providers 150 include, but are not limited to, navigation service providers, music content providers, video content providers, and the like. The scope of the present disclosure is not limited in this respect. It should be understood that the intelligent in-vehicle system itself can also actively initiate a request to use the services provided by the service provider 150. The scope of the present disclosure is not limited in this respect.
[0030] It should be understood that the scheme for configuring routing according to each embodiment of the present disclosure can also be applied to other appropriate environments, such as mobile terminals. The mobile terminal can be any type of movable terminal or portable terminal, including a laptop computer, a notebook computer, a netbook computer, a tablet computer, a media computer, a multimedia tablet, a personal communication system (PCS) device, a personal navigation device, a personal digital assistant (PDA), an audio / video player, a digital camera / camcorder, a positioning device, a television receiver, a radio broadcast receiver, an e-book device, a gaming device, or any combination of the foregoing, including accessories and peripherals of these devices or any combination thereof. It should also be understood that the structure and function of the environment 100 are described only for exemplary purposes, and no limitation on the scope of the present disclosure is implied.
[0031] Example routing configuration
[0032] Figure 2 A signaling diagram 200 for configuring routing according to some embodiments of the present disclosure is shown. Figure 2 The exemplary embodiment will be described with reference to routing configuration service 201, domain name resolver 202, and kernel 203. Routing configuration service 201 may be composed of, for example, Figure 1 The electronic device 130 shown in the figure is implemented. The electronic device 130 can also be used to implement the domain name resolver 202 and / or the kernel 203. It should be understood that the signaling diagram 200 can also include actions not shown and / or can omit one (or some) of the actions shown, and the scope of the present disclosure is not limited in this respect.
[0033] At 210, the routing configuration service 201 obtains the correspondence information for the domain name and the data channel. The correspondence information indicates the correspondence between a group of domain names and multiple data channels for accessing the network. The group of domain names may include one or more domain names. Exemplarily, the correspondence information may, for example, indicate that the first domain name in the group of domain names corresponds to the first data channel in the multiple data channels. The multiple data channels are respectively associated with multiple payment methods for network data traffic. In some embodiments, the multiple data channels may, for example, be multiple virtual network cards, or different network card devices, and the like. Multiple payment methods may, for example, include corporate payment and / or user personal payment. Alternatively or additionally, multiple payment methods may include multiple different payment accounts of the user 120. The scope of the present disclosure is not limited in this respect.
[0034] In some embodiments, the correspondence information between the domain name and the data channel and / or the association relationship between the data channel and the payment method can be input by the user 120. In other embodiments, the correspondence information between the domain name and the data channel and / or the association relationship between the data channel and the payment method may have been pre-stored in the electronic device 130. In still other embodiments, the correspondence information between the domain name and the data channel and / or the association relationship between the data channel and the payment method may be generated by the routing configuration service 201. In still other embodiments, the electronic device 130 may also be communicatively coupled to other devices to obtain the correspondence information between the domain name and the data channel and / or the association relationship between the data channel and the payment method from the other devices. The scope of the present disclosure is not limited in this respect.
[0035] In some embodiments, the correspondence information between domain names and data channels can be implemented in the form of a list. For example, the list can record: a first domain name corresponds to a first data channel for a first payment method (e.g., enterprise payment), a second domain name corresponds to a second data channel for a second payment method (e.g., user 120 pays with a first payment account), a third domain name corresponds to a third data channel for a third payment method (e.g., user 120 pays with a second payment account), and so on.
[0036] In other embodiments, the correspondence information between domain names and data channels can be implemented in the form of a domain name whitelist. For example, the domain name whitelist can record a group of domain names, and stipulate that all domain names in the domain name whitelist access the network through the first data channel for the first payment method, and all domain names not included in the domain name whitelist access the network through the second data channel for the second payment method. Alternatively, the correspondence information between domain names and data channels can be implemented in the form of a domain name blacklist. For example, the domain name blacklist can record a group of domain names, and stipulate that all domain names in the domain name blacklist cannot access the network through the first data channel for the first payment method, and all domain names not included in the domain name blacklist can access the network through the first data channel for the first payment method. With the help of a domain name whitelist or a domain name blacklist, the correspondence between domain names and data channels can be expressed and recorded more efficiently and concisely, and the amount of data required to record the correspondence can be reduced.
[0037] It should be understood that the correspondence information between the domain name and the data channel can also be recorded and / or stored in any other suitable manner, and the scope of the present disclosure is not limited in this respect. In the following, for the sake of ease of description, the routing configuration process will be described by taking the first domain name corresponding to the first data channel as an example. It should be understood that the routing configuration process described below is also applicable to the remaining domain names involved in the correspondence information.
[0038] Further, the routing configuration service 201 obtains a first network logical address corresponding to the first domain name. In the context of the present disclosure, a network logical address refers to a logical address assigned to a network or host on the Internet. Examples of network logical addresses include, but are not limited to, Internet Protocol (IP) addresses.
[0039] In some embodiments, the network logical address corresponding to the domain name involved in the above correspondence information may be provided in advance. Figure 2 The actions included in block 206 may be performed. At 215, routing configuration service 201 may read a first network logical address corresponding to the first domain name, for example, from pre-provided information.
[0040] The inventors have noticed that the network logical address corresponding to the same domain name may change. For example, the network logical addresses of the same domain name in different regions (for example, different provinces) may be different. In the application scenario of the intelligent vehicle system, when the vehicle 110 travels across regions, the pre-set network logical address corresponding to the domain name needs to be updated in time, otherwise the billing of network data traffic may be incorrect due to the change in the network logical address. In this regard, in other embodiments, the first network logical address corresponding to the first domain name can be obtained and updated in real time by monitoring the Domain Name System (DNS) request. In such an application scenario, Figure 2 The actions included in block 207 may be performed.
[0041] At 220, routing configuration service 201 may send a registration listening request to domain name resolver 202 to start listening DNS query. At 225, in response to receiving the domain name resolution request for the second domain name, domain name resolver 202 may perform domain name resolution for the second domain name to determine a second network logical address corresponding to the second domain name. Domain name resolver 202 may obtain the network logical address for the domain name by, for example, interacting with a local domain name server or a remote domain name server.
[0042] At 230, the DNS server may report the domain name resolution request event to the routing configuration service 201. For example, the DNS server may send domain name resolution information for the second domain name to the routing configuration service 201. The domain name resolution information may, for example, include at least the second domain name and a second network logical address corresponding to the second domain name. At 235, the routing configuration service 201 may match the received second domain name with the domain name included in the corresponding relationship information obtained at 210. In some embodiments, if the two domain names are the same, the two domain names may be considered to match. Alternatively or additionally, if the two domain names are equivalent, the two domain names may be considered to match.
[0043] Exemplarily, if it is determined that the second domain name matches the first domain name, the routing configuration service 201 may determine the second network logical address as the network logical address corresponding to the first domain name (i.e., the first network logical address). In the example case where the network logical address corresponding to the first domain name has not yet been recorded at the routing configuration service 201, the routing configuration service 201 may directly set the second network logical address to the first network logical address. In addition, in the example case where the first network logical address corresponding to the first domain name has already been recorded at the routing configuration service 201, the routing configuration service 201 may compare the second network logical address with the first network logical address, and if the second network logical address is different from the first network logical address, the second network logical address is used to replace the current first network logical address as the new first network logical address to update the network logical address for the first domain name.
[0044] In this way, the network logical address corresponding to the domain name can be dynamically updated in real time, so that the routing policy configured later can always adapt to the latest network logical address of the domain name. In this way, the accuracy of billing and control of different types of network data traffic can be improved, thereby further improving the user experience.
[0045] At 240, the routing configuration service 201 determines a routing policy for the first network logical address based on the correspondence information between the domain name and the data channel. As described above, assuming that the correspondence information indicates that the first domain name corresponds to the first data channel, the determined routing policy indicates that the first network logical address is accessed via the first data channel. Since the system routing is only effective for the network logical address and cannot be directly effective for the domain name, the above method can efficiently realize the conversion from the correspondence between the domain name and the data channel to the correspondence between the network logical address and the data channel.
[0046] Further, at 245, the routing configuration service 201 enables access to the first domain name to be executed based on the determined routing policy. In some embodiments, if the routing configuration service 201 obtains the network logical address corresponding to the first domain name for the first time, the routing configuration service 201 may send a message to the kernel 203 indicating that the routing policy is added to the routing policy set for multiple data channels. In response to receiving the message, the kernel 203 may add the routing policy determined by the routing configuration service 201 to the routing policy set maintained by the kernel 203. The kernel 203 may then control the forwarding of network traffic packets according to the routing policy set so that the packets accessing the first domain name are transmitted to the network through the first data channel. Exemplarily and not restrictively, the routing policy set may be implemented in the form of a routing table, and the routing configuration service 201 may configure the routing policy by calling the Netlink interface.
[0047] In this way, it is possible to omit the need to pre-configure the routing policy set at the kernel 203, and only when the first domain name is actually requested, the corresponding routing policy is added to the routing policy set. In this way, unnecessary routing configuration can be avoided, thereby realizing separate billing and control of different types of network data traffic more conveniently and efficiently.
[0048] In other embodiments, if the routing configuration service 201 (e.g., at 235) determines that the second domain name matches the first domain name and the second network logical address is different from the first network logical address, the routing configuration service 201 may send a message to the kernel 203. The message indicates that the first network logical address in the routing policy set for multiple data channels is replaced with the second network logical address. It should be noted that the message mentioned above may include one or more messages. In one example, the routing configuration service 201 may send a routing policy deletion message to the kernel 203 so that the kernel 203 deletes the routing policy associated with the first data channel for the first network logical address; and sends a routing policy addition message to the kernel 203 so that the kernel 203 adds the routing policy associated with the first data channel for the updated first network logical address (corresponding to the second network logical address). In another example, the routing configuration service 201 may send a routing policy update message to the kernel 203 so that the kernel 203 directly uses the updated first network logical address (corresponding to the second network logical address) to cover the first network logical address before the update.
[0049] In this way, the applied routing strategy can always be adapted to the latest network logical address of the domain name. In this way, the accuracy of charging and controlling different types of network data traffic can be improved, thereby further improving the user experience.
[0050] The routing configuration process according to various embodiments of the present disclosure has been described above with reference to the routing configuration service 201, the domain name resolver 202, and the kernel 203. It should be understood that the actions performed by one or more of the routing configuration service 201, the domain name resolver 202, and the kernel 203 described above may also be implemented by any other suitable one or more software, hardware, firmware, and combinations thereof, and the scope of the present disclosure is not limited in this respect.
[0051] Through the above combination Figure 1 and Figure 2It can be seen from the description that in the scheme for configuring routing according to each embodiment of the present disclosure, the routing policy for the network logical address is determined based on the correspondence between the domain name and the data channel and the network logical address corresponding to the domain name, and the access to the domain name is executed based on the routing policy. In this way, on the one hand, the correspondence between the domain name and the data channel can be used to implement separate billing of different types of network data traffic according to the domain name. In this way, the type of network data traffic can be decoupled from the application, so that the billing of different types of network data traffic can be managed more finely in units of domain names. On the other hand, the data routing function can be centrally managed without coupling the function to each application. In this way, separate billing and control of different types of network data traffic can be implemented more conveniently and efficiently.
[0052] Example Method
[0053] Figure 3 FIG. 3 is a flowchart of a routing configuration method 300 according to some embodiments of the present disclosure. In some embodiments, the method 300 may be implemented as follows: Figure 1 The method 300 is executed at the electronic device 130. It should be understood that the method 300 may further include additional blocks not shown and / or may omit one (or some) of the blocks shown, and the scope of the present disclosure is not limited in this respect.
[0054] In box 302, obtain the correspondence information between the domain name and the data channel. The correspondence information at least indicates that the first domain name corresponds to the first data channel of the multiple data channels for accessing the network. The multiple data channels are respectively associated with multiple payment methods for network data traffic. In box 304, obtain the first network logical address corresponding to the first domain name. In box 306, determine the routing policy for the first network logical address based on the correspondence information. The routing policy indicates that the first network logical address is accessed via the first data channel. In box 308, access to the first domain name is performed based on the routing policy.
[0055] In some embodiments, obtaining the first network logical address includes: receiving domain name resolution information for the second domain name from a domain name resolver, the domain name resolution information including the second domain name and a second network logical address corresponding to the second domain name; and in response to determining that the second domain name matches the first domain name, determining the second network logical address as the first network logical address.
[0056] In some embodiments, the method 300 further includes: sending a registration listening request to a domain name resolver, wherein the domain name resolution information is received as a response to the registration listening request.
[0057] In some embodiments, enabling access to a first domain name to be performed based on a routing policy includes: in response to determining that a second domain name matches the first domain name and the second network logical address is different from the first network logical address, sending a first message to the kernel, the first message indicating that the first network logical address in a routing policy set for multiple data channels is replaced with the second network logical address.
[0058] In some embodiments, causing access to the first domain name to be performed based on the routing policy includes: in response to first obtaining a network logical address corresponding to the first domain name, sending a second message to the kernel, the second message indicating that the routing policy is added to the routing policy set for multiple data channels.
[0059] In some embodiments, the set of routing policies includes a routing table.
[0060] In some embodiments, the multiple payment methods include at least one of the following: enterprise payment, user personal payment.
[0061] In some embodiments, the correspondence information includes a domain name whitelist, or the first network logical address includes an Internet Protocol (IP) address.
[0062] Example devices and equipment
[0063] The embodiments of the present disclosure also provide corresponding devices and apparatuses for implementing the above methods or processes. Figure 4 A block diagram of an example device 400 for configuring routing according to some embodiments of the present disclosure is shown. The device 400 can be used, for example, to implement the method according to each embodiment of the present disclosure. The device 400 includes an information acquisition module 402, an address acquisition module 404, a determination module 406, and an execution module 408. The information acquisition module 402 is configured to: obtain the correspondence information between the domain name and the data channel. The correspondence information at least indicates that the first domain name corresponds to the first data channel of the multiple data channels for accessing the network. The multiple data channels are respectively associated with multiple payment methods for network data traffic. The address acquisition module 404 is configured to: obtain the first network logical address corresponding to the first domain name. The determination module 406 is configured to: determine the routing policy for the first network logical address based on the correspondence information. The routing policy indicates that the first network logical address is accessed via the first data channel. The execution module 408 is configured to: enable the access to the first domain name to be executed based on the routing policy.
[0064] In some embodiments, the address acquisition module 404 includes a receiving module and an address determination module. The receiving module is configured to: receive domain name resolution information for the second domain name from a domain name resolver, the domain name resolution information including the second domain name and a second network logical address corresponding to the second domain name. The address determination module is configured to: in response to determining that the second domain name matches the first domain name, determine the second network logical address as the first network logical address.
[0065] In some embodiments, the apparatus 400 further comprises a request sending module configured to send a registration listening request to a domain name resolver, wherein the domain name resolution information is received as a response to the registration listening request.
[0066] In some embodiments, the execution module 408 includes a first message sending module configured to: in response to determining that the second domain name matches the first domain name and the second network logical address is different from the first network logical address, send a first message to the kernel. The first message indicates that the first network logical address in the routing policy set for the plurality of data channels is replaced with the second network logical address.
[0067] In some embodiments, the execution module 408 includes a second message sending module configured to: in response to first acquiring the network logical address corresponding to the first domain name, send a second message to the kernel, wherein the second message indicates adding the routing policy to the routing policy set for the plurality of data channels.
[0068] In some embodiments, the set of routing policies includes a routing table.
[0069] In some embodiments, the multiple payment methods include at least one of the following: enterprise payment, user personal payment.
[0070] In some embodiments, the correspondence information includes a domain name whitelist, or the first network logical address includes an Internet Protocol (IP) address.
[0071] The modules and / or units included in the device 400 can be implemented in various ways, including software, hardware, firmware, or any combination thereof. In some embodiments, one or more units can be implemented using software and / or firmware, such as machine executable instructions stored on a storage medium. In addition to or as an alternative to machine executable instructions, some or all of the units in the device 400 can be implemented at least in part by one or more hardware logic components. As an example and not limitation, exemplary types of hardware logic components that can be used include field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), systems on chips (SOCs), complex programmable logic devices (CPLDs), and the like.
[0072] Figure 4The modules and / or units shown in the can be partially or completely implemented as hardware modules, software modules, firmware modules or any combination thereof. In particular, in some embodiments, the processes, methods or procedures described above can be implemented by hardware in the storage system or a host corresponding to the storage system or other computing devices independent of the storage system.
[0073] Figure 5 1 shows a block diagram of a device 500 in which one or more embodiments of the present disclosure may be implemented. It should be understood that Figure 5 The electronic device 500 shown is merely exemplary and should not constitute any limitation on the functionality and scope of the embodiments described herein. Figure 5 The electronic device 500 shown may be used to implement the above-described method.
[0074] like Figure 5 As shown, the electronic device 500 is in the form of a general electronic device. The components of the electronic device 500 may include, but are not limited to, one or more processors or processing units 510, a memory 520, a storage device 530, one or more communication units 540, one or more input devices 550, and one or more output devices 560. The processing unit 510 may be an actual or virtual processor and is capable of performing various processes according to a program stored in the memory 520. In a multi-processor system, multiple processing units execute computer executable instructions in parallel to improve the parallel processing capability of the electronic device 500.
[0075] The electronic device 500 typically includes a plurality of computer storage media. Such media may be any available media accessible to the electronic device 500, including but not limited to volatile and non-volatile media, removable and non-removable media. The memory 520 may be a volatile memory (e.g., a register, a cache, a random access memory (RAM)), a non-volatile memory (e.g., a read-only memory (ROM), an electrically erasable programmable read-only memory (EEPROM), flash memory), or some combination thereof. The storage device 530 may be a removable or non-removable medium, and may include a machine-readable medium, such as a flash drive, a disk, or any other medium, which may be capable of being used to store information and / or data (e.g., training data for training) and may be accessed within the electronic device 500.
[0076] The electronic device 500 may further include additional removable / non-removable, volatile / non-volatile storage media. Figure 5As shown in , a disk drive for reading or writing from a removable, non-volatile disk (e.g., a "floppy disk") and an optical drive for reading or writing from a removable, non-volatile optical disk may be provided. In these cases, each drive may be connected to the bus (not shown) by one or more data media interfaces. The memory 520 may include a computer program product 525 having one or more program modules that are configured to perform various methods or actions of various implementations of the present disclosure.
[0077] The communication unit 540 implements communication with other electronic devices through a communication medium. Additionally, the functions of the components of the electronic device 500 can be implemented in a single computing cluster or multiple computing machines that can communicate through a communication connection. Therefore, the electronic device 500 can operate in a networked environment using a logical connection with one or more other servers, a network personal computer (PC), or another network node.
[0078] The input device 550 may be one or more input devices, such as a mouse, a keyboard, a tracking ball, etc. The output device 560 may be one or more output devices, such as a display, a speaker, a printer, etc. The electronic device 500 may also communicate with one or more external devices (not shown) through the communication unit 540 as needed, such as a storage device, a display device, etc., communicate with one or more devices that allow a user to interact with the electronic device 500, or communicate with any device that allows the electronic device 500 to communicate with one or more other electronic devices (e.g., a network card, a modem, etc.). Such communication may be performed via an input / output (I / O) interface (not shown).
[0079] According to an exemplary implementation of the present disclosure, a computer-readable storage medium is provided, on which computer-executable instructions are stored, wherein the computer-executable instructions are executed by a processor to implement the method described above. According to an exemplary implementation of the present disclosure, a computer program product is also provided, the computer program product is tangibly stored on a non-transitory computer-readable medium and includes computer-executable instructions, and the computer-executable instructions are executed by a processor to implement the method described above. According to an exemplary implementation of the present disclosure, a computer program product is provided, on which a computer program is stored, and when the program is executed by a processor, the method described above is implemented.
[0080] Various aspects of the present disclosure are described herein with reference to the flowcharts and / or block diagrams of the methods, devices, equipment, and computer program products implemented according to the present disclosure. It should be understood that each box in the flowchart and / or block diagram and the combination of each box in the flowchart and / or block diagram can be implemented by computer-readable program instructions.
[0081] These computer-readable program instructions can be provided to a processing unit of a general-purpose computer, a special-purpose computer, or other programmable data processing device, thereby producing a machine, so that when these instructions are executed by the processing unit of the computer or other programmable data processing device, a device that implements the functions / actions specified in one or more boxes in the flowchart and / or block diagram is generated. These computer-readable program instructions can also be stored in a computer-readable storage medium, and these instructions cause the computer, programmable data processing device, and / or other equipment to work in a specific manner, so that the computer-readable medium storing the instructions includes a manufactured product, which includes instructions for implementing various aspects of the functions / actions specified in one or more boxes in the flowchart and / or block diagram.
[0082] Computer-readable program instructions can be loaded onto a computer, other programmable data processing apparatus, or other device so that a series of operational steps are performed on the computer, other programmable data processing apparatus, or other device to produce a computer-implemented process, so that the instructions executed on the computer, other programmable data processing apparatus, or other device implement the functions / actions specified in one or more boxes in the flowchart and / or block diagram.
[0083] The flow chart and block diagram in the accompanying drawings show the possible architecture, function and operation of the system, method and computer program product according to multiple implementations of the present disclosure. In this regard, each square box in the flow chart or block diagram can represent a part of a module, program segment or instruction, and a part of a module, program segment or instruction includes one or more executable instructions for realizing the logical function of the specification. In some implementations as replacements, the function marked in the square box can also occur in a sequence different from that marked in the accompanying drawings. For example, two continuous square boxes can actually be executed substantially in parallel, and they can sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each square box in the block diagram and / or flow chart, and the combination of the square boxes in the block diagram and / or flow chart can be realized by a special hardware-based system that performs the function or action of the specification, or can be realized by a combination of special hardware and computer instructions.
[0084] The above descriptions of various implementations of the present disclosure are exemplary, non-exhaustive, and not limited to the disclosed implementations. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the described implementations. The selection of terms used herein is intended to best explain the principles of the implementations, practical applications, or improvements to the technology in the market, or to enable other persons of ordinary skill in the art to understand the various implementations disclosed herein.
Claims
1. A method for configuring routing, comprising: Acquire correspondence information between a domain name and a data channel, the correspondence information at least indicating that a first domain name corresponds to a first data channel among a plurality of data channels for accessing a network, the plurality of data channels being respectively associated with a plurality of payment methods for network data traffic; Acquire a first network logical address corresponding to the first domain name; Based on the correspondence information, determining a routing strategy for the first network logical address, the routing strategy indicating that the first network logical address is accessed via the first data channel; as well as Access to the first domain name is performed based on the routing policy.
2. The method according to claim 1, wherein obtaining the first network logical address comprises: receiving domain name resolution information for a second domain name from a domain name resolver, the domain name resolution information including the second domain name and a second network logical address corresponding to the second domain name; as well as In response to determining that the second domain name matches the first domain name, the second network logical address is determined to be the first network logical address.
3. The method according to claim 2, further comprising: A registration listening request is sent to the domain name resolver, wherein the domain name resolution information is received as a response to the registration listening request.
4. The method of claim 2, wherein causing access to the first domain name to be performed based on the routing policy comprises: In response to determining that the second domain name matches the first domain name and the second network logical address is different from the first network logical address, a first message is sent to the kernel, wherein the first message indicates that the first network logical address in the routing policy set for the multiple data channels is replaced with the second network logical address.
5. The method of claim 1 , wherein causing access to the first domain name to be performed based on the routing policy comprises: In response to first acquiring a network logical address corresponding to the first domain name, a second message is sent to the kernel, wherein the second message indicates that the routing policy is added to a routing policy set for the plurality of data channels. The method according to claim 4 , wherein the routing policy set comprises a routing table.
7. The method according to any one of claims 1 to 5, wherein the multiple payment methods include at least one of the following: enterprise payment, user personal payment.
8. The method according to any one of claims 1 to 5, wherein the corresponding relationship information includes a domain name whitelist, or the first network logical address includes an Internet Protocol IP address.
9. An apparatus for configuring a route, comprising: The information acquisition module is configured to: acquire correspondence information between a domain name and a data channel, wherein the correspondence information at least indicates that a first domain name corresponds to a first data channel among a plurality of data channels for accessing a network, and the plurality of data channels are respectively associated with a plurality of payment methods for network data traffic; An address acquisition module is configured to: acquire a first network logical address corresponding to the first domain name; a determination module configured to: determine, based on the correspondence information, a routing strategy for the first network logical address, wherein the routing strategy indicates that the first network logical address is accessed via the first data channel; as well as The execution module is configured to: enable access to the first domain name to be executed based on the routing policy.
10. An electronic device comprising: Memory and processor; The memory is used to store one or more computer instructions, wherein the one or more computer instructions are executed by the processor to implement the method according to any one of claims 1 to 8.
11. A computer-readable storage medium having one or more computer instructions stored thereon, wherein the one or more computer instructions are executed by a processor to implement the method according to any one of claims 1 to 8.
12. A computer program product comprising computer executable instructions, wherein the computer executable instructions, when executed by a processor, implement the method according to any one of claims 1 to 8.