CN113285920B - Service access method, device, equipment and storage medium - Google Patents
Service access method, device, equipment and storage mediumDownload PDFInfo
- Publication number
- CN113285920B CN113285920BCN202110423880.3ACN202110423880ACN113285920BCN 113285920 BCN113285920 BCN 113285920BCN 202110423880 ACN202110423880 ACN 202110423880ACN 113285920 BCN113285920 BCN 113285920B
- Authority
- CN
- China
- Prior art keywords
- domain name
- service request
- unified domain
- unified
- target service
- Prior art date
- Legal status (The legal status 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 status listed.)
- Active
Links
- 238000000034methodMethods0.000titleclaimsabstractdescription59
- 238000004891communicationMethods0.000claimsdescription15
- 238000004590computer programMethods0.000claimsdescription12
- 230000008569processEffects0.000description6
- 238000010586diagramMethods0.000description5
- 230000004044responseEffects0.000description4
- 230000009471actionEffects0.000description3
- 238000005516engineering processMethods0.000description3
- 238000012545processingMethods0.000description3
- 239000000284extractSubstances0.000description2
- 238000009434installationMethods0.000description2
- 239000000203mixtureSubstances0.000description2
- 230000002093peripheral effectEffects0.000description2
- 238000013500data storageMethods0.000description1
- 238000000802evaporation-induced self-assemblyMethods0.000description1
- 230000006870functionEffects0.000description1
- 230000010354integrationEffects0.000description1
- 238000012986modificationMethods0.000description1
- 230000004048modificationEffects0.000description1
- 238000012544monitoring processMethods0.000description1
- 230000003287optical effectEffects0.000description1
- 239000013307optical fiberSubstances0.000description1
- 239000004065semiconductorSubstances0.000description1
- 239000007787solidSubstances0.000description1
Images
Classifications
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/10—Network architectures or network communication protocols for network security for controlling access to devices or network resources
- 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
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/34—Network arrangements or protocols for supporting network services or applications involving the movement of software or configuration parameters
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Hardware Design (AREA)
- Computer Security & Cryptography (AREA)
- Computing Systems (AREA)
- General Engineering & Computer Science (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
Description
Technical Field
The present disclosure relates to the field of computer technologies, and in particular, to a service access method, apparatus, device, and storage medium.
Background
In the current internet technology, different service servers are generally adopted to provide different service access services for an application program, for example, a first service server is adopted to provide login services for the application program in a client, a second service server is adopted to provide download services for the application program, and the like, so when the application program sends different service access requests, different domain names are configured for the different service access requests, so that the domain name server can find the service server corresponding to the service access request according to the domain name, and the service server responds to the service access request. However, each time a service access request is sent, domain name resolution, connection establishment, request sending, response receiving, and the like are required, which is time-consuming.
Disclosure of Invention
The application provides a service access method, a device, equipment and a storage medium, which are used for solving the problem of high time consumption caused by the steps of performing domain name resolution, establishing connection, sending a request, receiving a response and the like when a service access request is sent each time in the related technology.
In a first aspect, a service access method is provided, including:
the client obtains a first target service request with a unified domain name based on an access instruction to an access object; transmitting the first target service request to a domain name server by adopting unified domain name connection corresponding to the unified domain name;
the domain name server obtains the first target service request sent by the client; analyzing the first target service request to obtain the unified domain name; forwarding the first target service request to gateway equipment corresponding to the unified domain name;
the gateway equipment acquires the first target service request sent by the domain name server; acquiring path data of the first target service request; acquiring effective data representing an original service request from the path data, wherein the effective data comprises target data representing a service server address and service data; generating the original service request corresponding to the effective data; and sending the original service request to a service server corresponding to the target data.
Optionally, the client obtains a first target service request with a domain name being a uniform domain name based on an access instruction to the access object, including:
the client acquires a service request corresponding to the access instruction;
the client acquires the unified domain name corresponding to the access object;
the client changes the domain name of the service request into the unified domain name to obtain the first target service request, wherein the path data of the first target service request comprises target data representing the address of the service server.
Optionally, the client obtains a first target service request including a unified domain name based on an access instruction to the access object, including:
the client acquires the unified domain name corresponding to the access object;
the client generates the first target service request based on the unified domain name, wherein path data of the first target service request includes target data characterizing a service server address.
Optionally, the client sends the first target service request to a domain name server by adopting a unified domain name connection corresponding to the unified domain name, including:
the client judges whether the unified domain name connection corresponding to the unified domain name exists in the connection pool;
If the unified domain name connection exists, the client acquires the unified domain name connection from the connection pool;
if the unified domain name connection does not exist, the client creates the unified domain name connection corresponding to the unified domain name;
and the client side sends the first target service request to the domain name server by adopting the unified domain name connection.
Optionally, the client creates the unified domain name connection corresponding to the unified domain name, including:
and the client generates the unified domain name connection according to the HTTP/2 protocol.
Optionally, after the client sends the first target service request to the domain name server by adopting the unified domain name connection, the method further includes:
the client judges whether to adopt the unified domain name connection to send a second target service request in the timing time of the timing unit;
if not, the client sends keep-alive data to the domain name server, wherein the keep-alive data comprises a heartbeat packet and/or a preset request;
if yes, the client refreshes the timing unit so as to count time again.
A second aspect provides a service access method, applied to a client, including:
Obtaining a first target service request with a unified domain name based on an access instruction to an access object;
and transmitting the first target service request to a domain name server by adopting unified domain name connection corresponding to the unified domain name.
Optionally, based on an access instruction to the access object, obtaining a first target service request with a domain name being a uniform domain name includes:
acquiring a service request corresponding to the access instruction;
acquiring the unified domain name corresponding to the access object;
and changing the domain name of the service request into the unified domain name to obtain the first target service request, wherein the path data of the first target service request comprises target data representing the address of the service server.
Optionally, based on the access instruction to the access object, obtaining the first target service request including the unified domain name includes:
acquiring the unified domain name corresponding to the access object;
and generating the first target service request based on the unified domain name, wherein the path data of the first target service request comprises target data representing a service server address.
Optionally, sending the first target service request to a domain name server by adopting a unified domain name connection corresponding to the unified domain name, including:
Judging whether the unified domain name connection corresponding to the unified domain name exists in the connection pool;
if the unified domain name connection exists, acquiring the unified domain name connection from the connection pool;
if the unified domain name connection does not exist, creating the unified domain name connection corresponding to the unified domain name;
and transmitting the first target service request to the domain name server by adopting the unified domain name connection.
Optionally, creating the unified domain name connection corresponding to the unified domain name includes:
and generating the unified domain name connection according to the HTTP/2 protocol.
Optionally, after the sending the first target service request to the domain name server by adopting the unified domain name connection, the method further includes:
judging whether to adopt the unified domain name connection to send a second target service request in the timing time of the timing unit;
if not, sending keep-alive data to the domain name server, wherein the keep-alive data comprises a heartbeat packet and/or a preset request;
if so, refreshing the timing unit so as to reckon.
In a third aspect, a service access method is provided, applied to a gateway device, and includes:
acquiring the first target service request sent by a domain name server;
Acquiring path data of the first target service request;
acquiring effective data representing an original service request from the path data, wherein the effective data comprises target data representing a service server address and service data;
generating the original service request corresponding to the effective data;
and sending the original service request to a service server corresponding to the target data.
A fourth aspect provides a service access system, comprising:
the system comprises a client, a domain name server, gateway equipment and a service server;
the client obtains a first target service request with a unified domain name based on an access instruction to an access object; transmitting the first target service request to a domain name server by adopting unified domain name connection corresponding to the unified domain name;
the domain name server obtains the first target service request sent by the client; analyzing the first target service request to obtain the unified domain name; forwarding the first target service request to the gateway equipment corresponding to the unified domain name;
the gateway equipment acquires the first target service request sent by the domain name server; acquiring path data of the first target service request; acquiring effective data representing an original service request from the path data, wherein the effective data comprises target data representing the service server address and service data; generating the original service request corresponding to the effective data; and sending the original service request to the service server corresponding to the target data.
A fifth aspect provides a service access apparatus, comprising:
the obtaining unit is used for obtaining a first target service request with a unified domain name based on an access instruction to an access object;
and the first sending unit is used for sending the first target service request to a domain name server by adopting unified domain name connection corresponding to the unified domain name.
A sixth aspect is a service access apparatus, including:
the first acquisition unit is used for acquiring the first target service request sent by the domain name server;
the second acquisition unit is used for acquiring the path data of the first target service request;
a third obtaining unit, configured to obtain, from the path data, valid data representing an original service request, where the valid data includes target data representing a service server address and service data;
a generating unit, configured to generate the original service request corresponding to the valid data;
and the second sending unit is used for sending the original service request to the service server corresponding to the target data.
A seventh aspect provides a client, including: the device comprises a processor, a memory and a communication bus, wherein the processor and the memory are communicated with each other through the communication bus; the memory is used for storing a computer program; the processor is configured to execute the program stored in the memory, and implement the service access method according to the second aspect.
An eighth aspect provides a gateway device, including: the device comprises a processor, a memory and a communication bus, wherein the processor and the memory are communicated with each other through the communication bus; the memory is used for storing a computer program; the processor is configured to execute the program stored in the memory, and implement the service access method according to the third aspect.
A ninth aspect provides a computer-readable storage medium storing a computer program which, when executed by a processor, implements the service access method of the second aspect.
In a tenth aspect, there is provided a computer readable storage medium storing a computer program which, when executed by a processor, implements the service access method of the third aspect.
Compared with the prior art, the technical scheme provided by the embodiment of the application has the following advantages:
according to the technical scheme provided by the embodiment of the application, when an access instruction for an access object exists, a first target service request is obtained, the first target service request is sent to a domain name server through unified domain name connection, the first target service request is sent to gateway equipment through the domain name server, the gateway equipment obtains path data from the first target service request, obtains effective data representing an original service request from the path data, generates the original service request corresponding to the effective data, and forwards the first target service request to a service server corresponding to the target data. Because the domain name of the obtained first target service request is a unified domain name, that is, the domain names of the service requests of different services can be converged into the unified domain name by adopting the scheme of the application, and the first target service request is sent through the unified domain name connection, when different service requests of access objects need to be sent, the stages of domain name analysis, connection establishment and the like do not need to be executed each time, and the sending request stage is directly executed, so that the speed of the network request is improved.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the invention and together with the description, serve to explain the principles of the invention.
Fig. 1 is a schematic structural diagram of a service access system in an embodiment of the present application;
fig. 2 is a schematic flow chart of a service access method in an embodiment of the present application;
fig. 3 is a schematic flow chart of another service access method in the embodiment of the present application;
fig. 4 is a schematic flow chart of another service access method in the embodiment of the present application;
fig. 5 is a schematic flow chart of another service access method in the embodiment of the present application;
fig. 6 is a schematic structural diagram of a service access device in an embodiment of the present application;
fig. 7 is a schematic structural diagram of a service access device according to another embodiment of the present application;
fig. 8 is a schematic structural diagram of an electronic device in an embodiment of the present application.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present application more clear, the technical solutions of the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application.
For a better understanding of aspects of embodiments of the present application, related terms and concepts that may be related to embodiments of the present application are described below.
The clients described in the embodiments of the present application may include smart phones (such as Android mobile phones, iOS mobile phones, windows Phone mobile phones, etc.), tablet computers, palm computers, notebook computers, video matrixes, monitoring platforms, mobile internet devices (MID, mobile Internet Devices), wearable devices, etc., which are merely examples, but not exhaustive, including but not limited to the above devices.
A service access method in the embodiments of the present application is described below with reference to fig. 1, and fig. 1 is a schematic system architecture diagram of a service access method provided in the embodiments of the present application, where the system architecture 100 includes aclient 110, adomain name server 120, and agateway device 130, where theclient 110 and thedomain name server 120 are in communication connection, and where thedomain name server 120 is in communication connection with thegateway device 130.
Wherein, theclient 110 obtains a first target service request with a uniform domain name based on an access instruction to an access object; a first target service request is sent to thedomain name server 120.
In this embodiment, the access object includes, but is not limited to, an application or a website.
When the access object includes an application:
in one example, the application is an installed application in the client.
At this time, the access instruction of the application program may be a login instruction, a file download instruction, or an instruction for delivering statistical information of the application program, and correspondingly, the first target service request may be a login request, a file download request, or a request for delivering statistical information of the application program.
In another example, the application is an uninstalled application in the client.
At this time, the access instruction of the application may be an installation package download instruction or the like, and accordingly, the first target service request may be an installation package download request or the like.
When the access object includes a website:
the access instruction to the application program may be a login instruction of a website, a file downloading instruction, an instruction for delivering statistical information, or the like, and correspondingly, the first target service request may be a login request of the website, a file downloading request, a request for delivering statistical information, or the like.
In this embodiment, each access object corresponds to a unique unified domain name, where the unified domain name includes, but is not limited to, the secondary domain name of the access object.
The secondary domain name is a web name when the access object is networked, for example, when the access object is a, the secondary domain name of the access object may be a.com.
Optionally, the present embodiment provides two methods for obtaining the first target service request:
first, based on the access instruction to the access object, a first target service request is directly generated.
Specifically, a unified domain name corresponding to an access object is obtained; a first target service request is generated based on the unified domain name, wherein path data of the first target service request includes target data characterizing a service server address.
In this embodiment, the first target service request includes, but is not limited to, a URL (Uniform Resource Locator ) address.
In practice, URLs typically include protocol data, domain name data, and path data. The protocol data defines a protocol used when acquiring resources, the domain name data corresponds to an IP address of a host, and the path data indicates the resources of the requested server. In this embodiment, since the domain name of the first target service request converges to the unified domain name, the target data representing the address of the service server is placed in the path data of the first target service request when the first target service request is generated.
Second, the original service request is changed to obtain a first target service request.
Specifically, a service request corresponding to an access instruction is obtained; acquiring a unified domain name corresponding to an access object; and changing the domain name of the service request into a unified domain name to obtain a first target service request, wherein the path data of the first target service request comprises target data representing the address of the service server.
In this case, the client directly generates a service request corresponding to the access instruction based on the access instruction of the access object, where the domain name of the service request is the target data representing the server address. After the domain name of the service request is changed, the domain name of the first target service request is changed into a unified domain name, and meanwhile, the domain name of the service request is changed into path data.
In practical application, the first target service request can be obtained in one of the two modes optionally; of course, the first target service request may be obtained by selecting one mode from two modes according to the service requested by the access instruction, which is not limited in this embodiment.
When one mode is selected from two modes according to the service requested by the access instruction, considering that the current existing service corresponding to the access object directly generates the service request corresponding to the access instruction, the first target service request can be obtained by adopting a second mode for the current existing service; and for accessing the service corresponding to the subsequent new addition, the first mode can be adopted to obtain the first target service request when the service request corresponding to the service is generated.
Taking an access object as an application program A as an example, assuming that the current existing service of the application program A is a login service and a file downloading service, and obtaining a first target service request corresponding to the current existing service of the application program A in a second mode for the service; assuming that a service person writing the application program a newly increases a recording service for the application program a in the future, the service person may set to obtain the first target service request according to the first mode while newly increasing the recording service, so that the first target service request is obtained according to the first mode when an access instruction for the recording service exists.
The following illustrates the procedure for obtaining the first target service request in two ways:
for example, for the access object a, the unified domain name may be api.a.com, and when the access instruction is directed to the login service of the access object a, the first manner is adopted to directly obtain the first target service request: api.a. com/logic.a. com/path = value; and if the second mode is adopted, firstly obtaining the service request corresponding to the access instruction: and secondly, changing the domain name of the service request based on the unified domain name, wherein the obtained first target service request is api.A.com/log.A.com/path=value.
In this embodiment, the unified domain name connection refers to a connection established between the unified domain name and the domain name server, and in the establishment process, the phase of resolving the unified domain name and establishing the connection is performed.
In this embodiment, once the unified domain name connection is established successfully, the unified domain name connection is stored in the connection pool, so that the service request of the access object can be multiplexed later.
Where a connection pool is a buffer pool that creates and manages connections that can be used by threads or processes that need them.
The unified domain name connection in the connection pool can be established when the first target service request is sent for the first time, or can be established in advance.
In order to realize multiplexing of the service request of the access object to the unified domain name connection, when the unified domain name connection is established for the first time, the HTTP/2 protocol is started, and after domain name resolution is performed for the first time and connection is established, the established connection can be multiplexed by the subsequent service request.
It will be appreciated that the HTTP protocol is based on the TCP protocol, so that when a unified domain name connection is created, HTTP requests are sent based on the HTTP/2 protocol, and HTTP establishes a connection channel to the corresponding server via TCP.
It will be appreciated that an HTTP2 connection may simultaneously transmit (send and/or receive) data streams for multiple service requests, and that the number of data streams simultaneously transmitted may be set by a client.
When multiple data streams are transmitted through the HTTP2 connection, the data packets of the multiple data streams can be mixed together and transmitted through the HTTP2 connection, and when the data packets reach the domain name resolution server, the domain name resolution server can extract each data stream from the multiple data streams.
Based on the two occasions of the establishment of the unified domain name connection, when the unified domain name connection corresponding to the unified domain name is adopted to send the first target service request to the domain name server, as shown in fig. 2, the method may include the following steps:
Alternatively, in this embodiment, one connection pool may store one unified domain name connection, or may store a plurality of unified domain name connections.
When a unified domain name connection is stored in the connection pool, determining the connection pool corresponding to the access object, and when the connection pool is not empty, determining that the unified domain name connection exists in the connection pool, otherwise, determining that the unified domain name connection exists in the connection pool.
When a plurality of unified domain name connections are stored in the connection pool, the unified domain name connections can be searched from the connection pool according to the unified domain name corresponding to the unified domain name connections.
For example, the unified domain name connection stored in the connection pool includes an a connection and a B connection, and when the unified domain name connection corresponding to the unified domain name api.a.com needs to be searched for from the connection pool, since the a connection corresponds to the unified domain name api.a.com, it is confirmed that the connection corresponding to the unified domain name api.a.com exists in the connection pool, and the a connection is regarded as the connection corresponding to the unified domain name api.a.com.
To ensure the multiplexing rate of the unified domain name connection, the unified domain name connection may be keep alive so that it survives as long as possible.
Optionally, referring to fig. 3, after sending the first target service request to the domain name server by using the unified domain name connection corresponding to the unified domain name, the method may further include the following steps:
Alternatively, the timing unit may be a timer in the client.
Alternatively, the timing time may be set empirically by humans.
Wherein the keep-alive data comprises heartbeat packets and/or preset requests.
Illustratively, the heartbeat package may be a client-custom command word.
The preset request may be, for example, a short request comprising a single byte.
When the keep-alive data comprises a heartbeat packet, the heartbeat packet can be sent to a corresponding server through a connection channel established by TCP;
when the keep-alive data comprises a preset request, the keep-alive data and the unified domain name are spliced to generate a corresponding unified domain name request, and the unified domain name request is sent to a domain name server through unified domain name connection.
In addition, since the server side has different configurations for the holding time of the TCP/HTTP, the TCP and HTTP disconnection times are different. Thus, based on the difference between the holding time of TCP and the holding time of HTTP configured at the server side, this embodiment provides the following two possibilities of sending keep-alive data:
Firstly, if TCP holding time is greater than HTTP holding time, then sending preset request of HTTP to keep alive the same domain name connection;
and secondly, if the TCP holding time is less than the HTTP holding time, the TCP heartbeat packet is sent to keep alive before the TCP holding time is up, and when the HTTP holding time is up, the preset request of HTTP is sent to keep alive.
Thedomain name server 120 obtains a first target service request sent by theclient 110; analyzing the first target service request to obtain a unified domain name; the first target service request is forwarded to thegateway device 130 corresponding to the unified domain name.
The domain name server extracts a domain name in the first target service request, namely a unified domain name, determines an IP address corresponding to the unified domain name as an address of thegateway device 130 through a pre-stored address table comprising correspondence between domain names and IP addresses, and sends the first target service request to thegateway device 130.
When the first target service request is implemented in a URL, the domain name server may parse the first target service request to obtain a unified domain name according to a composition format of the URL.
Wherein when the first target service request is implemented in URL, the gateway device may acquire path data from the first target service request according to a composition format of URL.
In this embodiment, when the domain name of the service request needs to converge to the unified domain name, the gateway device and the client may pre-agree on the format of the valid data in the first target service request, so that the gateway device may acquire the valid data from the first target service request according to the agreed format.
Wherein the pre-agreed format includes, but is not limited to, the location of valid data in the path data.
In this embodiment, the gateway device maintains a server cluster formed by at least one service server, where the server cluster is configured to respond to a service request corresponding to an access object. After the target data is acquired, determining the IP address of the server corresponding to the target data, and forwarding the first target service request to the service server corresponding to the IP address.
It should be noted that, the service server corresponding to the IP address may be one server or a server group formed by at least two servers.
After the service server obtains the first target service request, a service response of the first target service request is obtained, and the service response is sent to the client through the gateway equipment.
According to the technical scheme provided by the embodiment of the application, when an access instruction for an access object exists, a first target service request is obtained, the first target service request is sent to a domain name server through unified domain name connection, the first target service request is sent to gateway equipment through the domain name server, the gateway equipment obtains path data from the first target service request, obtains effective data representing an original service request from the path data, generates the original service request corresponding to the effective data, and forwards the first target service request to a service server corresponding to the target data. Because the domain name of the obtained first target service request is a unified domain name, that is, the domain names of the service requests of different services can be converged into the unified domain name by adopting the scheme of the application, and the first target service request is sent through the unified domain name connection, when different service requests of access objects need to be sent, the stages of domain name analysis, connection establishment and the like do not need to be executed each time, and the sending request stage is directly executed, so that the speed of the network request is improved.
The service access method in the embodiments of the present application is described below from the client side and the gateway device side, respectively, and, in view of the detailed description of the methods of the client side and the gateway device side in the above embodiments, detailed descriptions of these two schemes are not repeated here, and detailed descriptions of the above embodiments are omitted.
The following describes a service access method in an embodiment of the present application from a client side, referring to fig. 4, the method may include the following steps:
step 401, obtaining a first target service request with a unified domain name based on an access instruction to an access object;
step 402, a first target service request is sent to a domain name server by adopting unified domain name connection corresponding to the unified domain name.
Optionally, based on an access instruction to the access object, obtaining a first target service request with a domain name being a uniform domain name includes:
acquiring a service request corresponding to the access instruction;
acquiring a unified domain name corresponding to an access object;
and changing the domain name of the service request into a unified domain name to obtain a first target service request, wherein the path data of the first target service request comprises target data representing the address of the service server.
Optionally, based on the access instruction to the access object, obtaining the first target service request including the unified domain name includes:
acquiring a unified domain name corresponding to an access object;
a first target service request is generated based on the unified domain name, wherein path data of the first target service request includes target data characterizing a service server address.
Optionally, sending the first target service request to the domain name server by using a unified domain name connection corresponding to the unified domain name includes:
judging whether unified domain name connection corresponding to the unified domain name exists in the connection pool;
if the unified domain name connection exists, acquiring the unified domain name connection from the connection pool;
if the unified domain name connection does not exist, creating the unified domain name connection corresponding to the unified domain name;
and sending the first target service request to the domain name server by adopting the unified domain name connection.
Optionally, creating a unified domain name connection corresponding to the unified domain name includes:
according to the HTTP/2 protocol, a unified domain name connection is generated.
Optionally, after the first target service request is sent to the domain name server by adopting the unified domain name connection, the method further includes:
judging whether a uniform domain name connection is adopted to send a second target service request in the timing time of the timing unit;
if not, sending keep-alive data to the domain name server, wherein the keep-alive data comprises a heartbeat packet and/or a preset request;
if so, the timing unit is refreshed to be re-clocked.
The service access method in the embodiment of the present application is described below from the gateway device side, referring to fig. 5, the method may include the following steps:
and 505, sending the original service request to a service server corresponding to the target data.
Based on the same inventive concept, an embodiment of the present application provides a service access apparatus, as shown in fig. 6, which may include:
an obtainingunit 601, configured to obtain a first target service request with a domain name being a uniform domain name based on an access instruction to an access object;
and the first sendingunit 602 is configured to send a first target service request to the domain name server by using a unified domain name connection corresponding to the unified domain name.
Based on the same inventive concept, an embodiment of the present application provides a service access apparatus, as shown in fig. 7, which may include:
a first obtainingunit 701, configured to obtain a first target service request sent by a domain name server;
a second obtainingunit 702, configured to obtain path data of the first target service request;
A third obtainingunit 703, configured to obtain, from the path data, valid data representing an original service request, where the valid data includes target data representing a service server address and service data;
agenerating unit 704, configured to generate an original service request corresponding to the valid data;
and thesecond sending unit 705 is configured to send the original service request to a service server corresponding to the target data.
Based on the same concept, the embodiment of the application also provides an electronic device, as shown in fig. 8, where the electronic device mainly includes: aprocessor 801, amemory 802, and acommunication bus 803, wherein theprocessor 801 and thememory 802 complete communication with each other through thecommunication bus 803. Thememory 802 stores a program executable by theprocessor 801, and theprocessor 801 executes the program stored in thememory 802 to implement the following steps:
obtaining a first target service request with a unified domain name based on an access instruction to an access object; a unified domain name connection corresponding to the unified domain name is adopted to send a first target service request to a domain name server;
or alternatively, the first and second heat exchangers may be,
acquiring a first target service request sent by a domain name server; acquiring path data of a first target service request; acquiring effective data representing an original service request from path data, wherein the effective data comprises target data representing a service server address and service data; generating an original service request corresponding to the effective data; and sending the original service request to a service server corresponding to the target data.
Thecommunication bus 803 mentioned in the above-mentioned electronic device may be a peripheral component interconnect standard (Peripheral Component Interconnect, abbreviated to PCI) bus or an extended industry standard architecture (Extended Industry Standard Architecture, abbreviated to EISA) bus, or the like. Thecommunication bus 803 may be divided into an address bus, a data bus, a control bus, and the like. For ease of illustration, only one thick line is shown in fig. 8, but not only one bus or one type of bus.
Thememory 802 may include random access memory (Random Access Memory, simply RAM) or may include non-volatile memory (non-volatile memory), such as at least one disk memory. Optionally, the memory may also be at least one storage device located remotely from theaforementioned processor 801.
Theprocessor 801 may be a general-purpose processor including a central processing unit (Central Processing Unit, CPU), a network processor (Network Processor, NP), a digital signal processor (Digital Signal Processing, DSP), an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), a Field programmable gate array (Field-Programmable Gate Array, FPGA), or other programmable logic device, discrete gate or transistor logic device, or discrete hardware components.
In yet another embodiment of the present application, there is also provided a computer-readable storage medium having stored therein a computer program which, when run on a computer, causes the computer to perform the person identification method described in the above embodiment.
In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer instructions are loaded and executed on a computer, the processes or functions described in accordance with the embodiments of the present application are produced in whole or in part. The computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable apparatus. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, by a wired (e.g., coaxial cable, optical fiber, digital Subscriber Line (DSL)), or wireless (e.g., infrared, microwave, etc.) means from one website, computer, server, or data center to another. The computer readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that contains an integration of one or more available media. The usable medium may be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape, etc.), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid state disk), etc.
It should be noted that in this document, relational terms such as "first" and "second" and the like are used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Moreover, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
The foregoing is only a specific embodiment of the invention to enable those skilled in the art to understand or practice the invention. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the invention. Thus, the present invention is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
Claims (20)
1. A service access method, comprising:
the client obtains a first target service request with a unified domain name based on an access instruction to an access object; transmitting the first target service request to a domain name server by adopting unified domain name connection corresponding to the unified domain name;
the domain name server obtains the first target service request sent by the client; analyzing the first target service request to obtain the unified domain name; forwarding the first target service request to gateway equipment corresponding to the unified domain name;
the gateway equipment acquires the first target service request sent by the domain name server; acquiring path data of the first target service request; acquiring effective data representing an original service request from the path data, wherein the effective data comprises target data representing a service server address and service data; generating the original service request corresponding to the effective data; the original service request is sent to a service server corresponding to the target data;
once the unified domain name connection is established successfully, multiplexing of the unified domain name connection can be performed; the unified domain name connection is established when the first target service request is sent for the first time; or, pre-established.
2. The method according to claim 1, wherein the client obtains the first target service request with the uniform domain name based on the access instruction to the access object, including:
the client acquires a service request corresponding to the access instruction;
the client acquires the unified domain name corresponding to the access object;
the client changes the domain name of the service request into the unified domain name to obtain the first target service request, wherein the path data of the first target service request comprises target data representing the address of the service server.
3. The method according to claim 1, wherein the client obtains the first target service request including the unified domain name based on the access instruction to the access object, including:
the client acquires the unified domain name corresponding to the access object;
the client generates the first target service request based on the unified domain name, wherein path data of the first target service request includes target data characterizing a service server address.
4. The method of claim 1, wherein the client sending the first target service request to a domain name server using a unified domain name connection corresponding to the unified domain name, comprising:
The client judges whether the unified domain name connection corresponding to the unified domain name exists in the connection pool;
if the unified domain name connection exists, the client acquires the unified domain name connection from the connection pool;
if the unified domain name connection does not exist, the client creates the unified domain name connection corresponding to the unified domain name;
and the client side sends the first target service request to the domain name server by adopting the unified domain name connection.
5. The method of claim 4, wherein the client creating the unified domain name connection corresponding to the unified domain name comprises:
and the client generates the unified domain name connection according to the HTTP/2 protocol.
6. The method of claim 1, wherein after the client sends the first target service request to the domain name server using the unified domain name connection, further comprising:
the client judges whether to adopt the unified domain name connection to send a second target service request in the timing time of the timing unit;
if not, the client sends keep-alive data to the domain name server, wherein the keep-alive data comprises a heartbeat packet and/or a preset request;
If yes, the client refreshes the timing unit so as to count time again.
7. A service access method, applied to a client, comprising:
obtaining a first target service request with a unified domain name based on an access instruction to an access object;
the first target service request is sent to a domain name server by adopting unified domain name connection corresponding to the unified domain name, so that the domain name server obtains the first target service request, analyzes the first target service request to obtain the unified domain name, and forwards the first target service request to gateway equipment corresponding to the unified domain name; the gateway equipment is enabled to acquire the first target service request sent by the domain name server; acquiring path data of the first target service request; acquiring effective data representing an original service request from the path data, wherein the effective data comprises target data representing a service server address and service data; generating the original service request corresponding to the effective data; sending the original service request to the service server corresponding to the target data;
Once the unified domain name connection is established successfully, multiplexing of the unified domain name connection can be performed; the unified domain name connection is established when the first target service request is sent for the first time; or, pre-established.
8. The method of claim 7, wherein obtaining the first target service request with the domain name being a uniform domain name based on the access instruction to the access object comprises:
acquiring a service request corresponding to the access instruction;
acquiring the unified domain name corresponding to the access object;
and changing the domain name of the service request into the unified domain name to obtain the first target service request, wherein the path data of the first target service request comprises target data representing the address of the service server.
9. The method of claim 7, wherein obtaining the first target service request including the unified domain name based on the access instruction to the access object comprises:
acquiring the unified domain name corresponding to the access object;
and generating the first target service request based on the unified domain name, wherein the path data of the first target service request comprises target data representing a service server address.
10. The method of claim 7, wherein sending the first target service request to a domain name server using a unified domain name connection corresponding to the unified domain name comprises:
judging whether the unified domain name connection corresponding to the unified domain name exists in the connection pool;
if the unified domain name connection exists, acquiring the unified domain name connection from the connection pool;
if the unified domain name connection does not exist, creating the unified domain name connection corresponding to the unified domain name;
and transmitting the first target service request to the domain name server by adopting the unified domain name connection.
11. The method of claim 10, wherein creating the unified domain name connection corresponding to the unified domain name comprises:
and generating the unified domain name connection according to the HTTP/2 protocol.
12. The method of claim 7, wherein after sending the first target service request to the domain name server using the unified domain name connection, further comprising:
judging whether to adopt the unified domain name connection to send a second target service request in the timing time of the timing unit;
if not, sending keep-alive data to the domain name server, wherein the keep-alive data comprises a heartbeat packet and/or a preset request;
If so, refreshing the timing unit so as to reckon.
13. A service access method, applied to a gateway device, comprising:
acquiring a first target service request sent by a domain name server, wherein the first target service request is sent by a unified domain name connection corresponding to a unified domain name, and once the unified domain name connection is successfully established, multiplexing of the unified domain name connection can be performed; the unified domain name connection is established when the first target service request is sent for the first time; or, pre-established;
acquiring path data of the first target service request;
acquiring effective data representing an original service request from the path data, wherein the effective data comprises target data representing a service server address and service data;
generating the original service request corresponding to the effective data;
and sending the original service request to a service server corresponding to the target data.
14. A service access system, comprising:
the system comprises a client, a domain name server, gateway equipment and a service server;
the client obtains a first target service request with a unified domain name based on an access instruction to an access object; transmitting the first target service request to a domain name server by adopting unified domain name connection corresponding to the unified domain name;
The domain name server obtains the first target service request sent by the client; analyzing the first target service request to obtain the unified domain name; forwarding the first target service request to the gateway equipment corresponding to the unified domain name;
the gateway equipment acquires the first target service request sent by the domain name server; acquiring path data of the first target service request; acquiring effective data representing an original service request from the path data, wherein the effective data comprises target data representing the service server address and service data; generating the original service request corresponding to the effective data; sending the original service request to the service server corresponding to the target data;
once the unified domain name connection is established successfully, multiplexing of the unified domain name connection can be performed; the unified domain name connection is established when the first target service request is sent for the first time; or, pre-established.
15. A service access apparatus, comprising:
the obtaining unit is used for obtaining a first target service request with a unified domain name based on an access instruction to an access object;
The first sending unit is used for sending the first target service request to a domain name server by adopting unified domain name connection corresponding to the unified domain name, so that the domain name server obtains the first target service request, analyzes the first target service request to obtain the unified domain name, and forwards the first target service request to gateway equipment corresponding to the unified domain name; the gateway equipment is enabled to acquire the first target service request sent by the domain name server; acquiring path data of the first target service request; acquiring effective data representing an original service request from the path data, wherein the effective data comprises target data representing a service server address and service data; generating the original service request corresponding to the effective data; sending the original service request to the service server corresponding to the target data; once the unified domain name connection is established successfully, multiplexing of the unified domain name connection can be performed; the unified domain name connection is established when the first target service request is sent for the first time; or, pre-established.
16. A service access apparatus, comprising:
The first obtaining unit is used for obtaining a first target service request sent by the domain name server, wherein the first target service request is sent by a unified domain name connection corresponding to a unified domain name, and once the unified domain name connection is successfully established, multiplexing of the unified domain name connection can be carried out; the unified domain name connection is established when the first target service request is sent for the first time; or, pre-established;
the second acquisition unit is used for acquiring the path data of the first target service request;
a third obtaining unit, configured to obtain, from the path data, valid data representing an original service request, where the valid data includes target data representing a service server address and service data;
a generating unit, configured to generate the original service request corresponding to the valid data;
and the second sending unit is used for sending the original service request to the service server corresponding to the target data.
17. A client, comprising: the device comprises a processor, a memory and a communication bus, wherein the processor and the memory are communicated with each other through the communication bus; the memory is used for storing a computer program; the processor is configured to execute a program stored in the memory, and implement the service access method according to any one of claims 7 to 12.
18. A gateway device, comprising: the device comprises a processor, a memory and a communication bus, wherein the processor and the memory are communicated with each other through the communication bus; the memory is used for storing a computer program; the processor is configured to execute a program stored in the memory, and implement the service access method of claim 13.
19. A computer readable storage medium storing a computer program, wherein the computer program when executed by a processor implements the service access method of any of claims 7 to 12.
20. A computer readable storage medium storing a computer program, which when executed by a processor implements the service access method of claim 13.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110423880.3ACN113285920B (en) | 2021-04-20 | 2021-04-20 | Service access method, device, equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110423880.3ACN113285920B (en) | 2021-04-20 | 2021-04-20 | Service access method, device, equipment and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113285920A CN113285920A (en) | 2021-08-20 |
| CN113285920Btrue CN113285920B (en) | 2023-06-30 |
Family
ID=77276869
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110423880.3AActiveCN113285920B (en) | 2021-04-20 | 2021-04-20 | Service access method, device, equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113285920B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114124891B (en)* | 2021-10-25 | 2023-12-19 | 青岛海尔科技有限公司 | Network request processing method and device, storage medium and electronic device |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105306609A (en)* | 2014-06-26 | 2016-02-03 | 优视科技有限公司 | Network loading processing method and device |
| CN109981817A (en)* | 2019-03-21 | 2019-07-05 | 网宿科技股份有限公司 | The processing method and processing device of access request, server |
Family Cites Families (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7421489B2 (en)* | 2000-12-29 | 2008-09-02 | Nortel Network Limited | Network protocols for distributing functions within a network |
| CN103152369A (en)* | 2011-12-07 | 2013-06-12 | 中国移动通信集团浙江有限公司 | Internet access method, system, mobile station, gateway GPRS support node (GGSN) and wireless application protocol (WAP) gateway |
| CN108449442A (en)* | 2018-03-10 | 2018-08-24 | 北京酷我科技有限公司 | A kind of iOS Network Optimization Strategies |
| CN108462760B (en)* | 2018-03-21 | 2020-01-10 | 平安科技（深圳）有限公司 | Electronic device, automatic cluster access domain name generation method and storage medium |
- 2021
- 2021-04-20CNCN202110423880.3Apatent/CN113285920B/enactiveActive
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105306609A (en)* | 2014-06-26 | 2016-02-03 | 优视科技有限公司 | Network loading processing method and device |
| CN109981817A (en)* | 2019-03-21 | 2019-07-05 | 网宿科技股份有限公司 | The processing method and processing device of access request, server |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113285920A (en) | 2021-08-20 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10382543B2 (en) | System and device for enabling any network functionality client or server in a HTML5 application | |
| US8239571B2 (en) | Request routing using network computing components | |
| CN102932352B (en) | The method of communicating with the client and the server | |
| CN102884764B (en) | Message receiving method, deep packet inspection device, and system | |
| WO2017004947A1 (en) | Method and apparatus for preventing domain name hijacking | |
| CN102904903B (en) | Communication system and communication means | |
| CN108234639A (en) | A kind of data access method and device based on content distributing network CDN | |
| CA2930087C (en) | Wireless network service type | |
| CN102763373A (en) | Method and apparatus for using service of home network device based on remote access | |
| CN112261111A (en) | Method and system for realizing cross-domain access of browser in application program | |
| CN102300017A (en) | Cable modem and scanning method thereof | |
| US9203704B2 (en) | Discovering a server device, by a non-DLNA device, within a home network | |
| TW201733314A (en) | Method for executing request and associated server | |
| CN108886533B (en) | Accelerates connections to host servers | |
| CN113285920B (en) | Service access method, device, equipment and storage medium | |
| JP6185918B2 (en) | Gateway, method corresponding to gateway, computer program, and storage means | |
| Carlson et al. | An ad-hoc smart gateway platform for the web of things | |
| CN113301081B (en) | Data processing method and device for content distribution network and electronic equipment | |
| CN110476401B (en) | Device and method for providing multimedia service content | |
| WO2017067373A1 (en) | Data push method and apparatus | |
| CN101764829A (en) | Network resource acquisition method for browser and browser | |
| US9634987B2 (en) | Obtaining a MAC address from an external source | |
| CN114666413A (en) | Routing method, apparatus, device and readable storage medium | |
| CN107979611B (en) | Method and device for judging file hijacking | |
| CN111405350B (en) | A kind of multimedia access processing method, set-top box and gateway |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |