A method, device, medium and product for distributing cached data

Abstract

Embodiments of the present disclosure disclose a method, device, medium and product for distributing cached data. The method comprises: in the case that a domain name request carrying a relay domain name is received from an application program, sending a relay IP address corresponding to cached data of the application program to the application program; in the case that it is determined that the application program supports a relay function, receiving a data acquisition request sent by the application program; wherein the data acquisition request carries the relay IP address, and a cache space corresponding to the relay IP address stores hot content of the application program; based on the data acquisition request, determining target cached data corresponding to the data acquisition request according to the relay IP address, and sending the target cached data to the application program.

Description

Technical Field

[0001] This disclosure generally relates to the field of communication technology, and in particular to a method, apparatus, medium and product for distributing cached data. Background Technology

[0002] With the widespread adoption of streaming video services and online broadcasting, the extensive use of smartphones and tablets has driven the demand for mobile access. In scenarios where popular content is accessed in concentrated bursts, a large number of terminal requests repeatedly return to the content platform and CDN (Content Delivery Network) servers, exacerbating network load and transmission latency, making it difficult to meet the business requirements of low latency and high smoothness.

[0003] In related technologies, in content access and resolution mechanisms, processes such as domain name resolution and link establishment are usually executed when the user actually triggers the business. The overall time consumption leads to a significant delay in content loading, and there is a problem of low utilization of cache resources, which makes it impossible to achieve efficient local distribution and rapid response of hot data. Summary of the Invention

[0004] This disclosure addresses some of the shortcomings mentioned in the background art by providing a method, device, medium, and product for distributing cached data.

[0005] In a first aspect, embodiments of this disclosure provide a method for distributing cached data, applied to a relay network element, comprising: Upon receiving a domain name request carrying a relay domain name from an application, send the application a relay IP address carrying the application's cached data; If it is determined that the application supports relay functionality, a data acquisition request sent by the application is received; wherein, the data acquisition request carries the relay IP address, and the cache space corresponding to the relay IP address stores the application's hot content; Based on the data acquisition request, the target cached data corresponding to the data acquisition request is determined according to the relay IP address, and the target cached data is sent to the application.

[0006] In one embodiment of the first aspect, after sending a relay IP address carrying cached data of the application to the application, the method further includes: Receive a connection establishment request sent by the application; wherein the destination IP carried in the connection establishment request is the relay IP address; Upon receiving the connection request, a communication connection is established between the application and the relay IP address.

[0007] In one embodiment of the first aspect, determining the target cached data corresponding to the data acquisition request based on the relay IP address, and sending the target cached data to the application, includes: If the local cache space corresponding to the relay IP address is found to contain the target cache data corresponding to the data acquisition request, the target cache data is sent to the application. If the local cache space does not contain the target cache data corresponding to the data retrieval request, the target cache data is determined in the content delivery network based on the data retrieval request, and the target cache data is sent to the application.

[0008] In one embodiment of the first aspect, the step of determining the target cache data in the content delivery network based on the data retrieval request when the local cache space does not store the target cache data corresponding to the data retrieval request includes: Based on the data acquisition request, an address query request is generated; wherein, the address query request is used to query the IP address of the target cached data requested by the data acquisition request; The address query request is sent to the domain name service server, and the target IP address of the storage location of the target cache data is sent by the domain name service server; A communication connection is established with the content delivery network based on the target IP address, and the target cached data is downloaded from the content delivery network.

[0009] In one embodiment of the first aspect, the method further includes: When an application initiates a domain name request without carrying a relay domain name, the domain name request is sent to the domain name service server for processing.

[0010] In a second aspect, embodiments of this disclosure provide a method for distributing cached data, applied to an application, comprising: Send a domain name request carrying the relay domain name to the relay network element; Receive the relay IP address corresponding to the cached data of the application sent by the relay network element; If it is determined that the application supports relay functionality, a data acquisition request is sent to the relay network element; wherein, the data acquisition request carries the relay IP address, and the cache space corresponding to the relay IP address stores the hot content of the application; The relay network element receives target cached data sent by the relay network element; wherein the target cached data is cached data obtained by the relay network element based on the data acquisition request and according to the local cache space.

[0011] In one embodiment of the second aspect, the method further includes: Receive the ordinary IP address corresponding to the cached data of the application sent by the relay network element; Determine the priority of the relay IP address and the regular IP address; Determine the designated IP address with the highest priority among the relay IP address and the ordinary IP address; A specified data acquisition request is generated based on the specified IP address, and the specified data acquisition request is sent to the relay network element.

[0012] In a third aspect, embodiments of this disclosure provide a cached data distribution apparatus, comprising: The first sending module is used to send a relay IP address carrying the application's cached data to the application when it receives a domain name request carrying a relay domain name from the application. The first receiving module is configured to receive a data acquisition request sent by the application when it is determined that the application supports relay functionality; wherein the data acquisition request carries the relay IP address, and the cache space corresponding to the relay IP address stores the application's hot content; The determination module is used to determine the target cached data corresponding to the data acquisition request based on the relay IP address, and send the target cached data to the application.

[0013] In a fourth aspect, embodiments of this disclosure provide a cached data distribution apparatus, comprising: The second sending module is used to send a domain name request carrying the relay domain name to the relay network element; The second receiving module is used to receive the relay IP address corresponding to the cached data of the application sent by the relay network element; The third sending module is used to send a data acquisition request to the relay network element when it is determined that the application supports the relay function; wherein the data acquisition request carries the relay IP address, and the cache space corresponding to the relay IP address stores the hot content of the application; The third receiving module is used to receive target cached data sent by the relay network element; wherein, the target cached data is cached data obtained by the relay network element based on the data acquisition request and according to the local cache space.

[0014] As will be described in detail below, a method, apparatus, medium, and product for distributing cached data according to embodiments of this disclosure are disclosed. By responding to the application's relay domain name request in advance and returning the corresponding relay IP address, domain name resolution and cache entry preparation are completed before the user triggers the service, avoiding the time-consuming process of temporarily resolving domain names and establishing links when the service is triggered, thus reducing the loading latency of hot content. Simultaneously, by storing hot content in the cache space corresponding to the relay IP address, combined with the application's priority selection of relay IP addresses and data retrieval requests, core network localized distribution of hot data is achieved, reducing repeated origin requests to CDN servers and improving cache resource utilization and network bandwidth efficiency.

[0015] Furthermore, by identifying and adapting the relay function in applications, cache distribution services are provided only to applications that support the relay function, ensuring the compatibility and specificity of the technical solution. Even when the cache misses, data can still be supplied by fetching from the origin server, balancing the optimization of hot content with the stability of regular business access, and improving the overall content access efficiency and user experience in mobile streaming media scenarios. Attached Figure Description

[0016] Figure 1 A flowchart illustrating a method for distributing cached data as provided in this embodiment of the disclosure; Figure 2 A flowchart illustrating a method for distributing cached data as provided in this embodiment of the disclosure; Figure 3 An interaction diagram illustrating a method for distributing cached data according to an embodiment of this disclosure; Figure 4 A schematic diagram of a cached data distribution device provided in an embodiment of this disclosure; Figure 5 A schematic diagram of another cached data distribution apparatus provided in an embodiment of this disclosure; Figure 6 This is a schematic diagram of an electronic device provided in an embodiment of the present disclosure. Detailed Implementation

[0017] The present disclosure will now be described in further detail with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the present disclosure and not intended to limit it. Furthermore, it should be noted that, for ease of description, only the parts relevant to the present disclosure are shown in the drawings, not the entire structure.

[0018] It should be noted that similar labels and letters in the following figures indicate similar items. Therefore, once an item is defined in one figure, it does not need to be further defined and explained in subsequent figures.

[0019] In this document, the term "and / or" merely describes a relationship, indicating that three relationships can exist. For example, A and / or B can represent three cases: A alone, A and B simultaneously, and B alone. Furthermore, the term "at least one" in this document means any combination of at least two of any one or more elements. For example, including at least one of A, B, and C can mean including any one or more elements selected from the set consisting of A, B, and C.

[0020] Research has found that the widespread adoption of streaming video services and online broadcasting, along with the extensive use of smartphones and tablets, has driven the demand for mobile access. In scenarios where popular content is accessed in concentrated bursts, a large number of terminal requests repeatedly originate from the content platform and CDN (Content Delivery Network) servers, exacerbating network load and transmission latency, making it difficult to meet the business requirements of low latency and high smoothness.

[0021] In related technologies, in content access and resolution mechanisms, processes such as domain name resolution and link establishment are usually executed when the user actually triggers the business. The overall time consumption leads to a significant delay in content loading, and there is a problem of low utilization of cache resources, which makes it impossible to achieve efficient local distribution and rapid response of hot data.

[0022] Based on the above research, this disclosure provides a method for distributing cached data. By responding to the application's relay domain name request in advance and returning the corresponding relay IP address, domain name resolution and cache entry preparation are completed before the user triggers the service. This avoids the cumulative time consumption of temporarily resolving domain names and establishing links when the service is triggered, and reduces the loading latency of hot content. Simultaneously, by storing hot content in the cache space corresponding to the relay IP address, combined with the application's priority selection of relay IP addresses and data retrieval requests, core network localized distribution of hot data is achieved, reducing repeated origin requests to CDN servers and improving cache resource utilization and network bandwidth efficiency.

[0023] Furthermore, by identifying and adapting the relay function in applications, cache distribution services are provided only to applications that support the relay function, ensuring the compatibility and specificity of the technical solution. Even when the cache misses, data can still be supplied by fetching from the origin server, balancing the optimization of hot content with the stability of regular business access, and improving the overall content access efficiency and user experience in mobile streaming media scenarios.

[0024] To facilitate understanding of this embodiment, a method for distributing cached data disclosed in this disclosure will first be described in detail. The execution subject of the cached data distribution method provided in this disclosure is generally an electronic device with a certain computing power. In some possible implementations, this cached data distribution method can be implemented by a processor calling computer-readable instructions stored in memory.

[0025] Reference Figure 1 The diagram shows a flowchart of a method for distributing cached data according to an embodiment of this disclosure. The method is applied to a relay network element (i.e., a User Plane Function network element), and includes steps S101 to S103, wherein: S101. Upon receiving a domain name request from the application carrying a relay domain name, send the application the relay IP address carrying the application's cached data.

[0026] In embodiments of this disclosure, the application installed on the terminal can obtain its configuration information from the server. This configuration information includes a list of relay domain names.

[0027] For example, if the application is a short video application, relay domains can be configured for the short video trending content and live streaming trending content corresponding to the application; if the application is a video playback application, relay domains can be configured for the on-demand trending content and various types of video trending content corresponding to the application.

[0028] Here, after the application receives the configuration information, it can parse the configuration information to obtain the list of relay domain names, and generate a domain name request (i.e., a DNS (Domain Name Service) request) based on the list of relay domain names.

[0029] Here, when the application senses a change in the network / UE IP address (i.e., the mobile terminal IP address) of the installed terminal, or in the case of a periodic timer, it sends a request for the domain name to the relay network element.

[0030] Here, after receiving a domain name request, the relay element can resolve the request to obtain the IP address carried in the request. For example, if the IP address carried in the domain name request is "relay.xxx.yyy.com", the domain name with the IP address is determined to be a relay domain name; if the IP address carried in the domain name request is "xxx.yyy.com", the domain name with the IP address is determined to be a regular domain name.

[0031] If the relay network element determines that the domain name with the IP address carried in the domain name request is a relay domain name, the relay network element can fill the relay IP address into the DNS response message and send the DNS response message to the application.

[0032] The relay IP address is the relay IP address corresponding to the application's cached data, for example, RelayIP-a. In this case, the relay IP address "relay.xxx.yyy.com type A 10.1.1.1 / / 10.1.1.1" is used as the IP address when the application accesses the media relay URL (Uniform Resource Locator) service.

[0033] S102. If it is determined that the application supports relay function, receive a data acquisition request sent by the application; wherein the data acquisition request carries the relay IP address, and the cache space corresponding to the relay IP address stores the application's hot content.

[0034] In embodiments of this disclosure, the application may send dynamic service requests to the origin server. These dynamic service requests indicate specific content data corresponding to a video or live stream requested by the application.

[0035] Here, after the origin server receives a dynamic business request, it can parse the dynamic business request to determine the specified content data requested by the application.

[0036] Here, the origin server can determine whether the specified content data is hot content stored in the local cache space corresponding to the relay IP address.

[0037] Here, if the origin server determines that the specified content data is not hot content, it sends a regular URL (Uniform Resource Locator) containing a regular domain name to the application corresponding to the specified content data.

[0038] If the source site determines that the specified content data is hot content, determine whether the application supports relay functionality.

[0039] Here, the origin server can determine whether the application has media relay processing capabilities, i.e., whether it supports relay functionality, by using the application version number carried in the dynamic business request.

[0040] If the application supports relay functionality, send the application a relay URL containing the relay domain name and a regular URL containing the regular domain name corresponding to the specified content data.

[0041] For example, the relay URL corresponding to a relay domain name is "http: / / pull-flv-l11.relay.douyin.com / 00009.FLV"; the ordinary URL corresponding to a regular domain name is "http: / / pull-flv-l10.douyin.com / 00002.FLV".

[0042] Here, the video resolution of the relay URL can be set to 1080p, and there can be multiple regular URLs, each corresponding to specific content data with different video resolutions, such as 720p and 540p.

[0043] Here, when the application selects a relay URL to obtain data, a data retrieval request (i.e., a GET request) is generated based on the relay IP address, and the data retrieval request is sent to the relay network element, that is, the relay IP address is used as the destination IP address of the data retrieval request.

[0044] S103. If it is determined that the application supports relay function, based on the data acquisition request, determine the target cached data corresponding to the data acquisition request according to the relay IP address, and send the target cached data to the application.

[0045] In the embodiments of this disclosure, after receiving a data acquisition request, the relay network element can search the local cache space corresponding to the relay IP address to see if there is cached data corresponding to the data acquisition request.

[0046] Here, when the cached data corresponding to the data retrieval request is found in the local cache space, the relay network element determines the cached data as the target cached data and sends the target cached data to the application.

[0047] Here, if the cached data corresponding to the data retrieval request cannot be found in the local cache space, the relay network element can download the video data corresponding to the data retrieval request from the Content Delivery Network (CDN) and identify the video data as the target cached data.

[0048] In the embodiments of this disclosure, firstly, upon receiving a domain name request carrying a relay domain name sent by an application, a relay IP address carrying the application's cached data is sent to the application; secondly, if it is determined that the application supports relay functionality, a data acquisition request sent by the application is received; wherein the data acquisition request carries a relay IP address, and the cache space corresponding to the relay IP address stores the application's hot content; finally, based on the data acquisition request, the target cached data corresponding to the data acquisition request is determined according to the relay IP address, and the target cached data is sent to the application.

[0049] In the above implementation, by responding to the application's relay domain name request in advance and returning the corresponding relay IP address, domain name resolution and cache entry preparation are completed before the user triggers the service. This avoids the cumulative time consumption of temporarily resolving domain names and establishing links when the service is triggered, and reduces the loading latency of hot content. At the same time, by storing hot content in the cache space corresponding to the relay IP address, combined with the application's priority selection of relay IP addresses and data acquisition requests, core network localized distribution of hot data is achieved, reducing repeated origin requests to CDN servers and improving cache resource utilization and network bandwidth efficiency.

[0050] Furthermore, by identifying and adapting the relay function in applications, cache distribution services are provided only to applications that support the relay function, ensuring the compatibility and specificity of the technical solution. Even when the cache misses, data can still be supplied by fetching from the origin server, balancing the optimization of hot content with the stability of regular business access, and improving the overall content access efficiency and user experience in mobile streaming media scenarios.

[0051] In an optional implementation, after sending the relay IP address carrying the application's cached data to the application, the following steps are also included: First, receive the connection establishment request sent by the application; the destination IP carried in the connection establishment request is the relay IP address; Then, it receives a link establishment request and establishes a communication connection with the application based on the relay IP address.

[0052] In embodiments of this disclosure, when an application chooses to obtain data via a relay URL, it can send a link establishment request to the relay network element.

[0053] Upon receiving a link establishment request, a relay network element can establish a communication connection with the application via its relay IP address. This communication connection can then be used to transmit video data.

[0054] In an optional implementation, based on the data retrieval request, the target cached data corresponding to the data retrieval request is determined according to the relay IP address, and the target cached data is sent to the application, specifically including the following steps: First, if the local cache space corresponding to the relay IP address is found to contain the target cache data corresponding to the data retrieval request, the target cache data is sent to the application. Then, if the local cache space does not store the target cache data corresponding to the data retrieval request, the target cache data is determined in the content delivery network based on the data retrieval request, and the target cache data is sent to the application.

[0055] In the embodiments of this disclosure, the relay network element can quickly locate its corresponding local cache space through the relay IP address, and search the local cache space corresponding to the relay IP address to query whether the local cache space stores the target cache data that matches the data acquisition request.

[0056] If it is determined that the target cached data matching the data retrieval request is stored in the local cache space, the target cached data is sent to the application.

[0057] If the local cache space does not contain the target cache data matching the data retrieval request, the relay network element can download the data corresponding to the data retrieval request from the content delivery network and store the data as the target cache data in the local cache space.

[0058] Subsequently, the relay network element can use the communication connection established with the application to transmit the target cached data to the application.

[0059] In an optional implementation, if the target cached data corresponding to the data retrieval request is not found in the storage space, the target cached data is determined in the content delivery network based on the data retrieval request, specifically including the following steps: First, based on the data retrieval request, an address query request is generated; the address query request is used to query the IP address of the target cached data requested by the data retrieval request. Secondly, the address query request is sent to the domain name service server, and the target IP address of the storage location of the target cache data is received from the domain name service server; Finally, a communication connection is established with the content delivery network based on the target IP address, and the target cached data is downloaded from the content delivery network.

[0060] In embodiments of this disclosure, the relay network element can determine the IP address of the target cached data requested by the data acquisition request, and generate an address query request based on the IP address.

[0061] After generating an address query request, the relay element can send the address query request to the Domain Name Service (DNS) server.

[0062] Here, when the DNS server receives an address query request, it sends data to the relay network element to obtain the actual service address (i.e., the target IP address) of the target cached data requested in the request.

[0063] Here, the relay network element can initiate a link creation request to the content delivery network through the target IP address, and establish a communication connection with the content delivery network if the content delivery network responds to the link creation request.

[0064] After the relay element establishes a communication connection with the content delivery network, the relay element can obtain the target cache data from the content delivery network and save the target cache data to the local cache space.

[0065] Here, after the relay element obtains the target cache data from the content delivery network, it can send the target cache data to the application.

[0066] In an optional implementation, the following steps are also included: When an application initiates a domain name request without carrying a relay domain name, the domain name request is sent to the domain name service server for processing.

[0067] In the embodiments of this disclosure, when a relay network element receives a domain name request for a regular domain name initiated by an application, it forwards the domain name request to the domain name service server for processing.

[0068] After receiving a domain name request forwarded by a relay network element, the domain name service server can resolve the domain name request and then respond.

[0069] Reference Figure 2 The diagram shows a flowchart of a method for distributing cached data according to an embodiment of this disclosure, applied to an application. The method includes steps S201-S204, wherein: S201. Send a domain name request carrying the relay domain name to the relay network element.

[0070] In embodiments of this disclosure, the application installed on the terminal can obtain its configuration information from the server. This configuration information includes a list of relay domain names.

[0071] For example, if the application is a short video application, relay domains can be configured for the short video trending content and live streaming trending content corresponding to the application; if the application is a video playback application, relay domains can be configured for the on-demand trending content and various types of video trending content corresponding to the application.

[0072] Here, after the application receives the configuration information, it can parse the configuration information to obtain the list of relay domain names, and generate a domain name request (i.e., a DNS (Domain Name Service) request) based on the list of relay domain names.

[0073] Here, when the application senses a change in the network / UE IP address (i.e., the mobile terminal IP address) of the installed terminal, or in the case of a periodic timer, it sends a request for the domain name to the relay network element.

[0074] S202, Receive the relay IP address corresponding to the cached data of the application sent by the relay network element.

[0075] Here, after receiving a domain name request, the relay element can resolve the request to obtain the IP address carried in the request. For example, if the IP address carried in the domain name request is "relay.xxx.yyy.com", the domain name with the IP address is determined to be a relay domain name; if the IP address carried in the domain name request is "xxx.yyy.com", the domain name with the IP address is determined to be a regular domain name.

[0076] If the relay network element determines that the domain name in the domain name request is a relay domain name, the relay network element can fill the relay IP address into the DNS response message and send the DNS response message to the application.

[0077] The relay IP address is the relay IP address corresponding to the application's cached data, for example, RelayIP-a. In this case, the relay IP address "relay.xxx.yyy.com type A 10.1.1.1 / / 10.1.1.1" is used as the IP address when the application accesses the media relay URL (Uniform Resource Locator) service.

[0078] S203. If it is determined that the application supports the relay function, a data acquisition request is sent to the relay network element; wherein, the data acquisition request carries the relay IP address, and the cache space corresponding to the relay IP address stores the application's hot content.

[0079] In embodiments of this disclosure, the application may send dynamic service requests to the origin server. These dynamic service requests indicate specific content data corresponding to a video or live stream requested by the application.

[0080] Here, after the origin server receives a dynamic business request, it can parse the dynamic business request to determine the specified content data requested by the application.

[0081] Here, the origin server can determine whether the specified content data is hot content stored in the local cache space corresponding to the relay IP address.

[0082] Here, if the origin server determines that the specified content data is not hot content, it sends a regular URL (Uniform Resource Locator) containing a regular domain name to the application corresponding to the specified content data.

[0083] If the source site determines that the specified content data is hot content, determine whether the application supports relay functionality.

[0084] Here, the origin server can determine whether the application has media relay processing capabilities, i.e., whether it supports relay functionality, by using the application version number carried in the dynamic business request.

[0085] If the application supports relay functionality, send the application a relay URL containing the relay domain name and a regular URL containing the regular domain name corresponding to the specified content data.

[0086] For example, the relay URL corresponding to a relay domain name is "http: / / pull-flv-l11.relay.douyin.com / 00009.FLV"; the ordinary URL corresponding to a regular domain name is "http: / / pull-flv-l10.douyin.com / 00002.FLV".

[0087] Here, the video resolution of the relay URL can be set to 1080p, and there can be multiple regular URLs, each corresponding to specific content data with different video resolutions, such as 720p and 540p.

[0088] Here, when the application selects a relay URL to obtain data, a data retrieval request (i.e., a GET request) is generated based on the relay IP address, and the data retrieval request is sent to the relay network element, that is, the relay IP address is used as the destination IP address of the data retrieval request.

[0089] S204. Receive target cached data sent by the relay network element; wherein, the target cached data is the cached data obtained by the relay network element based on the data acquisition request and the local cache space.

[0090] In the embodiments of this disclosure, after receiving a data acquisition request, the relay network element can search the local cache space corresponding to the relay IP address to see if there is cached data corresponding to the data acquisition request.

[0091] Here, when the cached data corresponding to the data retrieval request is found in the local cache space, the relay network element determines the cached data as the target cached data and sends the target cached data to the application.

[0092] Here, if the cached data corresponding to the data retrieval request cannot be found in the local cache space, the relay network element can download the video data corresponding to the data retrieval request from the Content Delivery Network (CDN) and identify the video data as the target cached data.

[0093] In the above implementation, by responding to the application's relay domain name request in advance and returning the corresponding relay IP address, domain name resolution and cache entry preparation are completed before the user triggers the service. This avoids the cumulative time consumption of temporarily resolving domain names and establishing links when the service is triggered, and reduces the loading latency of hot content. At the same time, by storing hot content in the cache space corresponding to the relay IP address, combined with the application's priority selection of relay IP addresses and data acquisition requests, core network localized distribution of hot data is achieved, reducing repeated origin requests to CDN servers and improving cache resource utilization and network bandwidth efficiency.

[0094] Furthermore, by identifying and adapting the relay function in applications, cache distribution services are provided only to applications that support the relay function, ensuring the compatibility and specificity of the technical solution. Even when the cache misses, data can still be supplied by fetching from the origin server, balancing the optimization of hot content with the stability of regular business access, and improving the overall content access efficiency and user experience in mobile streaming media scenarios.

[0095] In an optional implementation, the following steps are also included: First, receive the ordinary IP address corresponding to the cached data of the application sent by the relay network element; Secondly, determine the priority of relay IP addresses and regular IP addresses; Secondly, determine the designated IP address with the highest priority among relay IP addresses and ordinary IP addresses; Finally, a specified data acquisition request is generated based on the specified IP address and sent to the relay network element.

[0096] In the embodiments of this disclosure, the application can maintain a communication connection with the relay network element and receive various IP address information sent by the relay network element in real time, including ordinary IP addresses corresponding to the cached data required by the application.

[0097] Among them, ordinary IP addresses are used to point to the content delivery network or origin server, so that the application can obtain non-cached or cache-missed data. The application can parse and store the received ordinary IP addresses for subsequent priority determination.

[0098] Here, the application can call its own preset IP address priority determination rules to determine the priority of the received relay IP addresses (previously received and cached from the relay network element) and ordinary IP addresses, and obtain the priority determination result.

[0099] Here, based on the priority determination results mentioned above, the application compares and filters the relay IP address and the ordinary IP address, and selects the IP address with the highest priority as the designated IP address. This designated IP address is the target IP address for the application to subsequently initiate data acquisition requests.

[0100] Here, the application targets the selected IP address and generates a specified data acquisition request that conforms to the communication protocol requirements. The request carries the specified IP address and the identifier of the cached data to be acquired. After the request is generated, the application sends the specified data acquisition request to the relay network element.

[0101] Reference Figure 3 The diagram shown illustrates an interaction of a cached data distribution method according to an embodiment of this disclosure, including: a mobile terminal with an application installed, a relay network element, a DNS server, a CDN, and an origin server; wherein: The relay network element includes the Service Service Gateway (SSG) and the relay module.

[0102] 1. The application installed on the terminal obtains its configuration information from the source server.

[0103] 2. The application parses the configuration information to obtain the list of relay domain names, and generates a domain name request based on the list of relay domain names.

[0104] 3. The application sends a domain name request to the SSG of the relay element.

[0105] 4. If the SSG of the relay network element determines that the domain name in the domain name request is a relay domain name, it will fill the relay IP address into the DNS response message.

[0106] 5. The SSG of the relay element sends the DNS response message to the application.

[0107] 6. The application sends dynamic business requests to the origin server.

[0108] 7. The origin server parses dynamic business requests to determine the specified content data requested by the application.

[0109] 8. If the origin server determines that the specified content data is hot content, send the application a relay URL containing the relay domain name and a regular URL containing the regular domain name corresponding to the specified content data.

[0110] 9. If the application selects a relay URL to retrieve data, generate a data retrieval request based on the relay IP address.

[0111] 10. Send the data acquisition request to the relay element's relay.

[0112] 11. The relay element checks the local cache space corresponding to the relay IP address to see if there is cached data for the request.

[0113] 12. If the cached data corresponding to the data retrieval request is found in the local cache space, the relay element determines the cached data as the target cached data and sends the target cached data to the application.

[0114] 13. If the cached data corresponding to the data acquisition request is not found in the local cache space, the relay of the relay element generates an address query request based on the data acquisition request.

[0115] 14. The relay element sends the address query request to the DNS server.

[0116] 15. The DNS server sends a data retrieval request to the relay network element, requesting the destination IP address of the target cached data.

[0117] 16. The relay element initiates a link creation request to the CDN via the target IP address.

[0118] 17. Establish a communication connection with the relay element of the relay network.

[0119] 18. The relay element obtains the target cache data from the CDN and saves the target cache data to the local cache space.

[0120] 19. The relay element sends the target cached data to the application.

[0121] The above solution exhibits the following technical effects during actual implementation: (1) By labeling and identifying hot content, caching it in the local cache space of the relay network element, and completing the distribution in the local cache space, the solution effectively reduces the bandwidth resource load of upstream CDN, OTT (Over The Top, providing application services to users via the Internet).

[0122] (2) By identifying hot content, the network resources can be distributed in a refined manner, which expands the business scenarios and fills the solution gaps in related scenarios.

[0123] Based on the same inventive concept, this disclosure also provides a cache data distribution device corresponding to the cache data distribution method. Since the principle of the device in this disclosure for solving the problem is similar to the cache data distribution method described above in this disclosure, the implementation of the device can refer to the implementation of the method, and the repeated parts will not be described again.

[0124] Reference Figure 4 The diagram shown is a schematic of a cached data distribution device provided in an embodiment of this disclosure, including: a first sending module 41, a first receiving module 42, and a determining module 43; wherein: The first sending module is used to send a relay IP address carrying the application's cached data to the application when it receives a domain name request carrying a relay domain name from the application. The first receiving module is configured to receive a data acquisition request sent by the application when it is determined that the application supports relay functionality; wherein the data acquisition request carries the relay IP address, and the cache space corresponding to the relay IP address stores the application's hot content; The determination module is used to determine the target cached data corresponding to the data acquisition request based on the relay IP address, and send the target cached data to the application.

[0125] This embodiment responds to the application's relay domain name request in advance and returns the corresponding relay IP address, completing domain name resolution and caching entry preparation before the user triggers the service. This avoids the cumulative time consumption of temporarily resolving domain names and establishing links when the service is triggered, reducing the loading latency of hot content. Simultaneously, by storing hot content in the cache space corresponding to the relay IP address, combined with the application's priority selection of relay IP addresses and data retrieval requests, it achieves core network localized distribution of hot data, reducing repeated origin requests to CDN servers and improving cache resource utilization and network bandwidth efficiency.

[0126] Furthermore, by identifying and adapting the relay function in applications, cache distribution services are provided only to applications that support the relay function, ensuring the compatibility and specificity of the technical solution. Even when the cache misses, data can still be supplied by fetching from the origin server, balancing the optimization of hot content with the stability of regular business access, and improving the overall content access efficiency and user experience in mobile streaming media scenarios.

[0127] Reference Figure 5 The diagram shown is a schematic of another cached data distribution device provided in an embodiment of this disclosure, including: a second sending module 51, a second receiving module 52, a third sending module 53, and a third receiving module 54; wherein: The second sending module is used to send a domain name request carrying the relay domain name to the relay network element; The second receiving module is used to receive the relay IP address corresponding to the cached data of the application sent by the relay network element; The third sending module is used to send a data acquisition request to the relay network element when it is determined that the application supports the relay function; wherein the data acquisition request carries the relay IP address, and the cache space corresponding to the relay IP address stores the hot content of the application; The third receiving module is used to receive target cached data sent by the relay network element; wherein, the target cached data is cached data obtained by the relay network element based on the data acquisition request and according to the local cache space.

[0128] This embodiment responds to the application's relay domain name request in advance and returns the corresponding relay IP address, completing domain name resolution and caching entry preparation before the user triggers the service. This avoids the cumulative time consumption of temporarily resolving domain names and establishing links when the service is triggered, reducing the loading latency of hot content. Simultaneously, by storing hot content in the cache space corresponding to the relay IP address, combined with the application's priority selection of relay IP addresses and data retrieval requests, it achieves core network localized distribution of hot data, reducing repeated origin requests to CDN servers and improving cache resource utilization and network bandwidth efficiency.

[0129] Furthermore, by identifying and adapting the relay function in applications, cache distribution services are provided only to applications that support the relay function, ensuring the compatibility and specificity of the technical solution. Even when the cache misses, data can still be supplied by fetching from the origin server, balancing the optimization of hot content with the stability of regular business access, and improving the overall content access efficiency and user experience in mobile streaming media scenarios.

[0130] The processing flow of each module in the device and the interaction flow between each module can be referred to the relevant descriptions in the above method embodiments, and will not be detailed here.

[0131] Corresponding to Figure 1 In addition to the method for distributing cached data in the present disclosure, this embodiment also provides an electronic device 600, such as... Figure 6 The diagram shown is a structural schematic of an electronic device 600 provided in an embodiment of this disclosure, including: The system includes a processor 61, a memory 62, and a bus 63. The memory 62 stores execution instructions and includes main memory 621 and external memory 622. The main memory 621, also called internal memory, temporarily stores the computational data in the processor 61, as well as data exchanged with external memory such as a hard disk. The processor 61 exchanges data with the external memory 622 through the main memory 621. When the electronic device 600 is running, the processor 61 communicates with the memory 62 through the bus 63, causing the processor 61 to execute the following instructions: Upon receiving a domain name request carrying a relay domain name from an application, send the application a relay IP address carrying the application's cached data; If it is determined that the application supports relay functionality, a data acquisition request sent by the application is received; wherein, the data acquisition request carries the relay IP address, and the cache space corresponding to the relay IP address stores the application's hot content; Based on the data acquisition request, the target cached data corresponding to the data acquisition request is determined according to the relay IP address, and the target cached data is sent to the application.

[0132] The processor 61 also executes the following instructions: Send a domain name request carrying the relay domain name to the relay network element; Receive the relay IP address corresponding to the cached data of the application sent by the relay network element; If it is determined that the application supports relay functionality, a data acquisition request is sent to the relay network element; wherein, the data acquisition request carries the relay IP address, and the cache space corresponding to the relay IP address stores the hot content of the application; The relay network element receives target cached data sent by the relay network element; wherein the target cached data is cached data obtained by the relay network element based on the data acquisition request and according to the local cache space.

[0133] The basic principles of this disclosure have been described above with reference to specific embodiments. However, it should be noted that the advantages, benefits, and effects mentioned in this disclosure are merely examples and not limitations, and should not be considered as essential features of each embodiment of this disclosure. Furthermore, the specific details disclosed above are for illustrative and facilitative purposes only, and are not limitations. These details do not limit the scope of this disclosure to the necessity of employing the aforementioned specific details for implementation.

[0134] The block diagrams of devices, apparatuses, devices, and systems disclosed herein are merely illustrative examples and are not intended to require or imply that they must be connected, arranged, or configured in the manner shown in the block diagrams. As those skilled in the art will recognize, these devices, apparatuses, devices, and systems can be connected, arranged, and configured in any manner. Words such as “comprising,” “including,” “having,” etc., are open-ended terms meaning “including but not limited to,” and are used interchangeably with them. The terms “or” and “and” as used herein refer to the terms “and / or,” and are used interchangeably with them unless the context clearly indicates otherwise. The term “such as” as used herein refers to the phrase “such as but not limited to,” and is used interchangeably with it.

[0135] Additionally, as used herein, the "or" used in a list of items beginning with "at least one" indicates a separate list, such that a list of, for example, "at least one of A, B, or C" means A or B or C, or AB or AC or BC, or ABC (i.e., A and B and C). Furthermore, the word "exemplary" does not imply that the described example is preferred or better than other examples.

[0136] It should also be noted that in the systems and methods of this disclosure, the components or steps can be decomposed and / or recombined. These decompositions and / or recombinations should be considered as equivalent solutions to this disclosure.

[0137] Various changes, substitutions, and modifications can be made to the technology described herein without departing from the teachings defined by the appended claims. Furthermore, the scope of the claims of this disclosure is not limited to the specific aspects of the processes, machines, manufactures, events, means, methods, and actions described above. Currently existing or later-developed processes, machines, manufactures, events, means, methods, or actions that perform substantially the same function or achieve substantially the same result as the corresponding aspects described herein can be utilized. Therefore, the appended claims include such processes, machines, manufactures, events, means, methods, or actions within their scope.

[0138] The above description of the disclosed aspects is provided to enable any person skilled in the art to make or use this disclosure. Various modifications to these aspects will be readily apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects without departing from the scope of this disclosure. Therefore, this disclosure is not intended to be limited to the aspects shown herein, but rather to be carried out within the widest scope consistent with the principles and novel features disclosed herein.

[0139] The above description has been given for purposes of illustration and description. Furthermore, this description is not intended to limit the embodiments of this disclosure to the forms disclosed herein. Although numerous exemplary aspects and embodiments have been discussed above, those skilled in the art will recognize certain variations, modifications, alterations, additions, and sub-combinations therein.

Claims

1. A method for distributing cached data, characterized in that, Applied to relay network elements, including: Upon receiving a domain name request carrying a relay domain name from an application, send the application a relay IP address carrying the application's cached data; If it is determined that the application supports relay functionality, a data acquisition request sent by the application is received; wherein, the data acquisition request carries the relay IP address, and the cache space corresponding to the relay IP address stores the application's hot content; Based on the data acquisition request, the target cached data corresponding to the data acquisition request is determined according to the relay IP address, and the target cached data is sent to the application.

2. The method as described in claim 1, characterized in that, After sending the relay IP address carrying the application's cached data to the application, the method further includes: Receive a connection establishment request sent by the application; wherein the destination IP carried in the connection establishment request is the relay IP address; Upon receiving the connection request, a communication connection is established between the application and the relay IP address.

3. The method as described in claim 1, characterized in that, The step of determining the target cached data corresponding to the data acquisition request based on the relay IP address and sending the target cached data to the application includes: If the local cache space corresponding to the relay IP address is found to contain the target cache data corresponding to the data acquisition request, the target cache data is sent to the application. If the local cache space does not contain the target cache data corresponding to the data retrieval request, the target cache data is determined in the content delivery network based on the data retrieval request, and the target cache data is sent to the application.

4. The method as described in claim 3, characterized in that, When the local cache space does not store the target cache data corresponding to the data retrieval request, determining the target cache data in the content delivery network based on the data retrieval request includes: Based on the data acquisition request, an address query request is generated; wherein, the address query request is used to query the IP address of the target cached data requested by the data acquisition request; The address query request is sent to the domain name service server, and the target IP address of the storage location of the target cache data is sent by the domain name service server; A communication connection is established with the content delivery network based on the target IP address, and the target cached data is downloaded from the content delivery network.

5. The method as described in claim 1, characterized in that, The method further includes: When an application initiates a domain name request without carrying a relay domain name, the domain name request is sent to the domain name service server for processing.

6. A method for distributing cached data, characterized in that, Applied to applications, including: Send a domain name request carrying the relay domain name to the relay network element; Receive the relay IP address corresponding to the cached data of the application sent by the relay network element; If it is determined that the application supports relay functionality, a data acquisition request is sent to the relay network element; wherein, the data acquisition request carries the relay IP address, and the cache space corresponding to the relay IP address stores the hot content of the application; The relay network element receives target cached data sent by the relay network element; wherein the target cached data is cached data obtained by the relay network element based on the data acquisition request and according to the local cache space.

7. The method as described in claim 6, characterized in that, The method further includes: Receive the ordinary IP address corresponding to the cached data of the application sent by the relay network element; Determine the priority of the relay IP address and the regular IP address; Determine the designated IP address with the highest priority among the relay IP address and the ordinary IP address; A specified data acquisition request is generated based on the specified IP address, and the specified data acquisition request is sent to the relay network element.

8. An electronic device comprising a memory, a processor, and a computer program stored in the memory, characterized in that, The processor executes the computer program to implement the steps of the method as described in any one of claims 1 to 7.

9. A computer-readable storage medium having a computer program / instructions stored thereon, characterized in that, When the computer program / instructions are executed by the processor, they implement the steps of the method as described in any one of claims 1 to 7.

10. A computer program product comprising a computer program / instructions, characterized in that, When the computer program / instructions are executed by the processor, they implement the steps of the method as described in any one of claims 1 to 7.

Images