CN114666841A - Flow-free method and flow-free system for directional flow - Google Patents

Abstract

The application provides a flow-free method for realizing directional flow by using a CDN technology. In the method provided by the application, a CDN scheduling center receives a play scheduling request message sent by a user client, then sends a scheduling request response message carrying a target streaming-free IP address to the user client according to the play scheduling request message, the user client sends a play request message carrying the target streaming-free IP address, a target CDN node receiving the play request message obtains free directional flow from a server corresponding to the target streaming-free IP address, and finally, the target CDN node sends the free directional flow to the user client. In the method, because the play request message carries the stream-free IP address, the stream-free CDN node and the non-stream-free CDN node are not required to be additionally distinguished in the CDN network, and the stream-free service end and the non-stream-free service end are not required to be distinguished, and the stream-free directional flow can be provided for the user client, so that network resources can be saved.

Description

Flow-free method and flow-free system for directional flow

technical field

The present application relates to the field of communication technologies, and in particular, to a flow-free method and flow-free system for directional traffic.

Background technique

With the development of the mobile Internet and the popularization of 4G (4 generation, 4G) networks, more and more people can access high-speed wireless broadband networks anytime, anywhere, and enjoy the convenience brought by mobile digital technology.

Currently, traffic-free services for directional traffic are relatively common. Traffic-free services for directional traffic refer to services that do not charge for the specified directional traffic when the service usage regulations and limits are met. In the prior art, the CDN technology can be used to implement directional traffic operations.

However, in the network, for the same traffic to users, some are free-flow traffic and some are non-flow-free traffic. The server needs to deploy free-flow CDN nodes and non-flow-free CDN nodes, which requires more node resources to achieve free-flow. Streaming service or non-streaming service.

SUMMARY OF THE INVENTION

The embodiments of the present application provide a flow-free method and flow-free system for directional traffic, so that the CDN network does not need to additionally distinguish between flow-free CDN nodes and non-flow-free CDN nodes, and does not need to additionally provide flow-free servers and non-flow-free servers. It can provide flow-free directional traffic for user clients, thereby saving network resources.

In a first aspect, the present application provides a flow-free method for directional traffic. The method includes: a CDN scheduling center receives a playback scheduling request message sent by a user client, wherein the playback scheduling request message carries first indication information, and the first An indication message is used to instruct the user client to request free directional traffic of the target; the CDN scheduling center sends a scheduling request response message to the user client according to the playback scheduling request message, and the scheduling request response message carries the target Stream-free IP address; the user client sends a playback request message, and the playback request message carries the target stream-free IP address; the target CDN node that receives the playback request message corresponds to the target stream-free IP address The server obtains the free directional traffic; the target CDN node sends the free directional traffic to the user client.

In this method, because the flow-free IP address is configured for the server that provides directional traffic, and the dispatch center returns the flow-free IP address of the server that can provide the directional traffic requested by the user to the user client, the user client sends the CDN When a node requests flow-free directional traffic, it can inform the CDN node of the flow-free IP address, so that the CDN node can obtain flow-free directional traffic from the flow-free IP address of the server. The method of the present embodiment can make it possible to provide flow-free directional traffic for user clients without additionally distinguishing flow-free CDN nodes and non-flow-free CDN nodes and without additionally providing flow-free servers and non-flow-free servers in the CDN network. Thereby, network resources can be saved.

With reference to the first aspect, in a first possible implementation manner, before the CDN scheduling center sends a scheduling request response message to the user client according to the playback scheduling request message, the method further includes: the CDN scheduling The center performs subscription relationship authentication between the user client and the free directional traffic; the CDN dispatch center performs traffic limit authentication on the user client and the free directional traffic.

In combination with the first possible implementation manner, in the second possible implementation manner, the playback scheduling request message also carries the mobile phone number of the user client; correspondingly, the CDN scheduling center according to the playback scheduling request The message sends a scheduling request response message to the user client, including: the CDN scheduling center determines the attribution of the user client according to the mobile phone number; The flow-free IP address of the target server of the flow-directed service is determined as the target flow-free IP address.

With reference to the second possible implementation manner, in a third possible implementation manner, the playback scheduling request message is generated based on a hypertext transfer protocol (hyper text transfer protocol, HTTP) application layer scheduling interface, and the HTTP application The parameters of the layer scheduling interface include: the mobile phone number of the user client, the IP address of the user client, the service profile (SP) identifier, the identifier of the product requested by the user client, and the uniform resource location system of the product requested by the user client. (uniform resource locator, URL), timestamp, key of the product requested by the user client, and encryption check code of the product requested by the user client.

In a second aspect, the present application provides a flow-free system for directional traffic, the system includes: a CDN scheduling center, configured to receive a playback scheduling request message sent by a user client, where the playback scheduling request message carries first indication information, The first indication information is used to instruct the user client to request target free directional traffic; the CDN scheduling center is further configured to send a scheduling request response message to the user client according to the playback scheduling request message, and the scheduling The request response message carries the target streaming-free IP address; the user client is used to send a playback request message, and the playback request message carries the target streaming-free IP address; the target CDN node that receives the playback request message uses the obtaining the free directional traffic from the server corresponding to the target traffic-free IP address; the target CDN node is further configured to send the free directional traffic to the user client.

With reference to the second aspect, in a first possible implementation manner, before the CDN scheduling center sends a scheduling request response message to the user client according to the playback scheduling request message, the system is further configured to: the CDN The dispatch center is further configured to authenticate the subscription relationship between the user client and the free directed traffic; the CDN dispatch center is further configured to perform traffic limit authentication on the user client and the free directed traffic.

In combination with the first possible implementation manner, in the second possible implementation manner, the play scheduling request message also carries the mobile phone number of the user client; accordingly, the CDN scheduling center is specifically used to: The mobile phone number is used to determine the home location of the user client;

In combination with the second possible implementation manner, in the third possible implementation manner, the playback scheduling request message is generated based on the HTTP application layer scheduling interface, and the parameters of the HTTP application layer scheduling interface include: the mobile phone of the user client Number, IP address of the user client, SP identification, identification of the product requested by the user client, URL of the product requested by the user client, timestamp, key of the product requested by the user client, and encryption of the product requested by the user client Check code.

In a third aspect, the present application provides a flow-free system for directional traffic, comprising: a plurality of memories and a plurality of processors; the memories are used for storing program instructions; the processors are used for calling the program instructions in the memory to execute The method according to the first aspect or any one of the possible implementations.

When the system is a computing device, in some implementations, the system may also include a transceiver or communication interface for communicating with other devices.

When the system is a chip for a computing device, in some implementations, the system may further include a communication interface for communicating with other devices in the computing device, for example, for communicating with a transceiver of the computing device.

In a fourth aspect, the present application provides a computer-readable medium, where the computer-readable medium stores a program code for computer execution, the program code comprising a computer-readable medium for executing the method described in the first aspect or any one of the possible implementations. instructions for the method described.

In a fifth aspect, the present application provides a computer program product comprising instructions, which, when the computer program product runs on a processor, causes the processor to implement the method of the first aspect or any one of the implementation manners.

Description of drawings

1 is a flowchart of a flow-free method for directional traffic according to an embodiment of the present application;

FIG. 2 is a flowchart of service authentication according to an embodiment of the application;

3 is a flowchart of a number segment scheduling strategy according to an embodiment of the application;

4 is an overall flow chart of user traffic collection and storage according to an embodiment of the application;

FIG. 5 is a schematic structural diagram of a flow-free device for directional flow according to an embodiment of the present application.

Detailed ways

For the sake of understanding, the related terms involved in this application will be explained first.

1. Directed traffic

Directed traffic refers to the mobile communication traffic generated only in the use of designated mobile applications and content. Operators can distinguish the directed traffic by identifying the server IP and adopt different billing strategies. Directed traffic can be an operator's own business or a third-party cooperative business. The corresponding server has a large number of IPs, and it is impossible to configure all the server IPs in the operator's mobile communication network.

2. CDN

CDN is a new network architecture added to the existing Internet, which is composed of high-performance acceleration nodes all over the country. These high-performance service nodes will store service content according to a certain caching strategy. When a user initiates a request for a certain service content, the request will be dispatched to the service node closest to the user, and the service node will respond directly and quickly, effectively reducing user costs. Access delay and improve availability.

The basic principle of CDN is to widely use various cache servers, and distribute these cache servers to regions or networks where user access is relatively concentrated. When users visit a website, the global load technology is used to direct the user's access to the nearest working normal cache. On the server, the cache server directly responds to user requests. CDN has the following main functions: (1) Save backbone network bandwidth and reduce bandwidth requirements; (2) Provide server-side acceleration to solve the problem of server overload caused by large user visits; (3) Service providers can use Web Cache technology to The Web pages and objects visited by users are cached locally, so that the access to the same objects does not need to occupy the egress bandwidth of the backbone, and increases the demand for the corresponding time for users to access Internet pages; (4) It can overcome the problem of uneven distribution of websites, and can reduce Website construction and maintenance costs; (5) Reduce the impact of "communication storms" and improve the stability of network access.

3. Domain Name System (DNS)

DNS is a service of the Internet. It acts as a distributed database that maps domain names and IP addresses to each other, making it easier for people to access the Internet. DNS is a system on the Internet that resolves the naming of machines on the Internet. Just like visiting a friend, you must first know how to get there. When a host wants to visit another host on the Internet, it must first know its address. The IP address in TCP/IP is a number separated by four segments with "." The composition (here, the IPv4 address is used as an example, and the IPv6 address is the same), it is always not as convenient as the name to remember. Therefore, the domain name system is used to manage the corresponding relationship between the name and the IP.

4. HTTP

HTTP is a simple request-response protocol that usually runs on top of Transmission Control Protocol (TCP). It specifies what kind of messages the client might send to the server and what kind of response it gets. The headers of the request and response messages are given in ASCII; the message content has a MIME-like format. This simple model was instrumental in the early success of the Web because it made development and deployment very straightforward.

HTTP is a stateless protocol, i.e. the server does not keep any state of the transaction with the client. This greatly reduces the memory burden of the server, thereby maintaining a faster response speed. HTTP is an object-oriented protocol that allows the transmission of any type of data object. It identifies the content and size of the transmitted data by data type and length, and allows data to be compressed and transmitted. After a user defines a hypertext link in an HTML document, the browser will establish a connection with the designated server through the transmission control protocol/internet protocol (TCP/IP) protocol.

At present, the existing CDN technology mainly adopts the DNS scheduling mechanism. Under the DNS scheduling mechanism, the client sends the request to the CDN edge node through domain name resolution. The scheduling process is completed in the domain name resolution part of the TCP/IP protocol stack under the application layer, and the business authentication logic of the application layer cannot be implemented. In addition, the granularity of the existing CDN scheduling is nodes, and a service node is allocated to the user, and the servers in the node are automatically allocated by load balancing. However, in the flow-free scenario, since the flow-free depends on the specified IP, according to the existing scheduling granularity, it is necessary to deploy the flow-free node and the non-flow-free node in the same area, which is not conducive to the reuse of equipment, and also brings about the impact on the server, machine waste of resources such as racks.

In view of the above shortcomings, the present application provides a flow-free method for directional traffic. On the basis of HTTP scheduling, service-related parameters such as user ID and service ID are sent in the interface for the server to perform corresponding service authentication, and ensure that the parameters cannot be used. Tampering and counterfeiting; the granularity of scheduling needs to be implemented to the IP level, so that the same server can be configured with multiple IPs, including flow-free IP and non-flow-free IP, which can serve both common non-flow-free scenarios and flow-free scenarios. , to achieve effective use of server and IP resources.

The implementation of the embodiments of the present application will be described in detail below with reference to the accompanying drawings.

FIG. 1 is a flowchart of a flow-free method for directional traffic according to an embodiment of the present application. As shown in FIG. 1, the method may include S101, S102, S103, S104 and S105.

S101. The CDN scheduling center of the content distribution network receives a playback scheduling request message sent by a user client, where the playback scheduling request message carries first indication information, where the first indication information is used to instruct the user client to request free targeting of a target flow.

For example, when an APP is ordering a streaming-free service and playing a video in a mobile network environment, it can initiate a playback scheduling request to the CDN scheduling center. The playback scheduling request can carry the ordering mobile phone number, product ID, back-to-source information, and anti-leech. information and the type of free quantitative traffic requested.

The mapping relationship between IP addresses and free directed traffic can be pre-stored in the CDN dispatch center.

In some implementations, the playback scheduling request message may be implemented by using an HTTP application layer scheduling interface.

An example of a dispatch interface is as follows:

http://host:port/gslb? userid=xxxx&userip=xxxxspid=xxxx&pid=xxxx&srcURL=x&tm=xxx&spkey=xxx

in,

spkey=MD5(http://host:port/gslb?userid=xxxx&userip=xxxxspid=xxxx&pid=xxxx&srcURL=x&tm=xxx&key)

host:port is the address of the scheduling interface. The interface parameters are as follows:

Table 1

Response: It is returned in json format, and the normal message contains the following parameters:

Table 2

S102. The CDN scheduling center sends a scheduling request response message to the user client according to the playback scheduling request message, where the scheduling request response message carries the target stream-free IP address.

S103. The user client sends a play request message, where the play request message carries the target streaming-free IP address.

S104. The target CDN node that receives the play request message obtains the free directional traffic from the server corresponding to the target free streaming IP address.

S105. The target CDN node sends the free directed traffic to the user client.

In this embodiment, the server corresponding to the target flow-free IP address may also be configured with a non-flow-free IP address at the same time, so as to provide a non-flow-free directional traffic service.

The CDN uses the streaming-free IP address to return the content requested by the user. The whole process of using directional traffic to play videos is over. Since the streaming-free IP address has been configured on the provincial GGSN (gateway GPRS support node, GGSN), the user successfully uses the free directional traffic to play videos.

In the method of this embodiment, since a flow-free IP address is configured for the server that provides directional traffic, and the dispatch center returns the flow-free IP address of the server that can provide the directional traffic requested by the user to the user client, the user client When the client requests flow-free directional traffic from the CDN node, it can inform the CDN node of the flow-free IP address, so that the CDN node can obtain the flow-free directional traffic from the flow-free IP address of the server. The method of the present embodiment can make it possible to provide flow-free directional traffic for user clients without additionally distinguishing flow-free CDN nodes and non-flow-free CDN nodes and without additionally providing flow-free servers and non-flow-free servers in the CDN network. Thereby, network resources can be saved.

In some implementations of this embodiment, the dispatch center may perform subscription relationship authentication and service authentication on the user client.

FIG. 2 is a flowchart of service authentication according to an embodiment of the present application. As shown in Figure 2, the overall process of service authentication includes user subscription, synchronization of subscription relationship between billing system and CDN system after unsubscription occurs, collection of user traffic details and deduction of available quota for directional traffic, and Authentication when requesting directed traffic. A REDIS database is set up on the CDN side to update the management of the subscription relationship in real time and maintain the available quota of directional traffic.

S201, order relationship synchronization.

The billing side receives user subscription and cancellation messages from various channels, and synchronizes subscription and cancellation to the subscription relationship synchronization interface of the CDN.

S202, the subscription relationship is updated to the Redis database.

The synchronization interface updates the Redis database in real time and maintains legal ordering relationships.

S203, after collecting the detailed list of user traffic, the deduction of the available traffic of the user is completed.

The traffic collection and deduction module collects user traffic details in real time, and deducts the available quota of directional traffic for corresponding products.

S204 , the CDN scheduling center inquires whether the corresponding subscription relationship and traffic are excessive when receiving the playback scheduling request from the user client.

When the CDN scheduling center receives the directional traffic playback scheduling request from the user client, it queries the Redis database to authenticate the subscription relationship and the available traffic quota. If there is no legal subscription relationship or the traffic usage is excessive, the dispatch center returns the corresponding error code to the client APP.

In some implementations of this embodiment, optionally, when the mobile phone number of the user is carried in the playback scheduling request message, the scheduling center may determine a streaming-free IP address for the user client based on the mobile phone number. An example in which the dispatch center determines the flow-free IP address for the user client based on the mobile phone number is shown in FIG. 3 .

FIG. 3 is a flowchart of a number segment scheduling strategy according to an embodiment of the present application. In the scheduling process, the dispatch center can extract the user's mobile phone number, and based on the operator's management of the mobile phone number database, the mobile phone number segment-based scheduling can be implemented as a supplement to IP address scheduling, or combined with IP address scheduling. More precise scheduling.

S301. Configure a CDN node corresponding to an area in the management background.

The CDN management background allocates CDN service nodes for different geographical areas.

S302, after receiving the playback scheduling request, query the area according to the mobile phone number segment.

After receiving the playback scheduling request, the CDN scheduling center extracts the mobile phone number in the request and matches it with the number segment library to locate the user area.

S303: Query the CDN service node according to the area from the area schedule table.

After locating the area from the mobile phone number, the service node matching is performed according to the area schedule, and the service node in the corresponding area is allocated for the request.

In the directional traffic scenario, the flow-free identification parameter configured on the GGSN is the IP address. However, the current CDN scheduling is generally only refined to the node level, and the nodes are redistributed to a certain physical server using a load balancing strategy, and the same server is generally configured with multiple IPs (there are some IP free flow, some Some IPs cannot avoid flow), which will lead to scheduling to non-flow-free IPs, resulting in wrong traffic billing. Therefore, in this scenario, CDN scheduling must be refined to the IP level to ensure that requests for directional traffic are scheduled to flow-free IPs. The specific implementation mechanism is as follows:

1) For resource management in the CDN background, the data structure from node to server to network card to IP is used, that is, a node can contain multiple servers, a server can contain multiple network cards, and a network card can contain multiple IPs.

2) Whether each IP address is identified as a flow-free IP;

3) For the flow-free service, the user is allocated a flow-free IP for service, and for the non-flow-free service, the user is allocated a non-flow-free IP for service.

In this way, each server is configured with multiple IPs, which can be used for directional traffic services or ordinary CDN services, which improves the multiplexing efficiency of the server and saves server resources.

An example of traffic limit authentication in this embodiment is shown in FIG. 4 . FIG. 4 is an overall flowchart of user traffic collection and storage according to an embodiment of the present application. For different products, CDN will set the traffic limit for the product based on the product definition. For example, the traffic limit of product A is 10G, and the part exceeding 10G will return a corresponding error message in the access scheduling process, and the client can prompt the user according to the returned parameters. "The current data limit has been exceeded, and will use general data to play".

The CDN edge server serves the user's directed traffic requests and generates a log message for each relevant HTTP request. The log information includes: log generation time, user request time, service duration, downloaded bytes, service profile identifier (SPID), product identity document (ID) and other information. The log is cut every minute and entered into the log backup directory.

S401 , summarizing the regular traffic, and generating a detailed list of user traffic.

The traffic collection module scans the log backup directory, processes the newly generated log files, and summarizes the logs according to the user ID (mobile phone number), SPID, and product ID as the aggregation basis to form a detailed user traffic list, which includes the following Fields: time, user phone number, SPID, product ID, traffic, server IP. After the detailed list is generated, it will be uniformly uploaded to the central server detailed list directory.

S402, the traffic bill is stored, and the directional traffic can be deducted.

The traffic bill storage module is deployed in the center, scans the newly uploaded detailed bill files in the detailed bill directory in real time, and forms the user traffic details for each record in the detailed bill, and deducts the available traffic of the corresponding products.

S403. After receiving the playback scheduling request, the CDN scheduling center queries the available traffic quota in real time.

After receiving the user client's playback scheduling request, the CDN scheduling center queries the available traffic of the corresponding product in real time, and determines whether the user is over-excited. If the available traffic is insufficient, the corresponding error message can be returned.

The present application also provides a flow-free system for directional traffic, and the flow-free system may include a CDN scheduling center, a CDN node, and a directional traffic server. Further, the flow-free system may further include a user client. The user client provided in this application can be used to execute S101 and S103, the CDN scheduling center can be used to execute S102, the server can be used to execute S104, and the CDN node can be used to execute S105.

FIG. 5 is a schematic structural diagram of a flow-free device for directional flow according to an embodiment of the present application. The apparatus shown in FIG. 5 can be used to implement the functions implemented by the user client, the CDN scheduling center, the CDN node or the server in any of the foregoing embodiments.

As shown in FIG. 5 , the apparatus 500 in this embodiment includes: a memory 501 , a processor 502 , a communication interface 503 , and a bus 504 . The memory 501 , the processor 502 , and the communication interface 503 are connected to each other through the bus 504 for communication.

The memory 501 may be a read only memory (ROM), a static storage device, a dynamic storage device, or a random access memory (RAM). The memory 501 can store programs, and when the program stored in the memory 501 is executed by the processor 502, the processor 502 is configured to execute each of the methods performed by the user client, the CDN scheduling center, the CDN node or the server in the method shown in FIG. 1 . step.

The processor 502 can be a general-purpose central processing unit (CPU), a microprocessor, an application specific integrated circuit (ASIC), or one or more integrated circuits for executing related programs to The methods in the various embodiments of the present application are implemented.

The processor 502 may also be an integrated circuit chip with signal processing capability. In the implementation process, each step of the method in the various embodiments of the present application may be completed by an integrated logic circuit of hardware in the processor 602 or an instruction in the form of software.

The above-mentioned processor 502 may also be a general-purpose processor, a digital signal processor (digital signal processing, DSP), an application-specific integrated circuit (ASIC), an off-the-shelf programmable gate array (field programmable gate array, FPGA) or other programmable logic devices, discrete gates. Or transistor logic devices, discrete hardware components. The methods, steps, and logic block diagrams disclosed in the embodiments of this application can be implemented or executed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.

The steps of the method disclosed in conjunction with the embodiments of the present application may be directly embodied as executed by a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor. The software modules may be located in random access memory, flash memory, read-only memory, programmable read-only memory or electrically erasable programmable memory, registers and other storage media mature in the art. The storage medium is located in the memory 501, and the processor 502 reads the information in the memory 501, and combines its hardware to complete the functions required to be performed by the units included in the device of the present application. For example, the embodiment shown in FIG. 1 can be implemented by the CDN scheduling center. the individual steps/functions.

The communication interface 503 may use, but is not limited to, a transceiver such as a transceiver to implement communication between the apparatus 500 and other devices or a communication network.

Bus 504 may include a pathway for communicating information between various components of apparatus 500 (eg, memory 501, processor 502, communication interface 503).

It should be understood that the apparatus 500 shown in this embodiment of the present application may be a computing device, or may also be a chip configured in the computing device.

It should also be understood that the memory in the embodiments of the present application may be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. The non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically programmable Erase programmable read-only memory (electrically EPROM, EEPROM) or flash memory. Volatile memory may be random access memory (RAM), which acts as an external cache. By way of example and not limitation, many forms of random access memory (RAM) are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory Access memory (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous connection dynamic random access Memory (synchlink DRAM, SLDRAM) and direct memory bus random access memory (direct rambus RAM, DR RAM).

The above embodiments may be implemented in whole or in part by software, hardware, firmware or any other combination. When implemented in software, the above-described embodiments 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 or computer programs. When the computer instructions or computer programs are loaded or executed on a computer, all or part of the processes or functions described in the embodiments of the present application are generated. The computer may be a general purpose computer, special purpose computer, computer network, or other programmable device. The computer instructions may be stored in or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be downloaded from a website site, computer, server, or data center Transmission to another website site, computer, server or data center by wire (eg, infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server, a data center, or the like that contains one or more sets of available media. The usable media may be magnetic media (eg, floppy disks, hard disks, magnetic tapes), optical media (eg, DVDs), or semiconductor media. The semiconductor medium may be a solid state drive.

It should be understood that the term "and/or" in this document is only an association relationship to describe associated objects, indicating that there can be three kinds of relationships, for example, A and/or B, which can mean that A exists alone, and A and B exist at the same time , there are three cases of B alone, where A and B can be singular or plural. In addition, the character "/" in this document generally indicates that the related objects before and after are an "or" relationship, but may also indicate an "and/or" relationship, which can be understood with reference to the context.

In this application, "at least one" means one or more, and "plurality" means two or more. "At least one item(s) below" or similar expressions thereof refer to any combination of these items, including any combination of single item(s) or plural items(s). For example, at least one item (a) of a, b, or c can represent: a, b, c, a-b, a-c, b-c, or a-b-c, where a, b, c may be single or multiple .

It should be understood that, in various embodiments of the present application, the size of the sequence numbers of the above-mentioned processes does not mean the sequence of execution, and the execution sequence of each process should be determined by its functions and internal logic, and should not be dealt with in the embodiments of the present application. implementation constitutes any limitation.

Those of ordinary skill in the art can realize that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Skilled artisans may implement the described functionality using different methods for each particular application, but such implementations should not be considered beyond the scope of this application.

Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working process of the above-described systems, devices and units may refer to the corresponding processes in the foregoing method embodiments, which will not be repeated here.

In the several embodiments provided in this application, it should be understood that the disclosed system, apparatus and method may be implemented in other manners. For example, the apparatus embodiments described above are only illustrative. For example, the division of the units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored, or not implemented. On the other hand, the shown or discussed mutual coupling or direct coupling or communication connection may be through some interfaces, indirect coupling or communication connection of devices or units, and may be in electrical, mechanical or other forms.

The units described as separate components may or may not be physically separated, and components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution in this embodiment.

In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically alone, or two or more units may be integrated into one unit.

The functions, if implemented in the form of software functional units and sold or used as independent products, may be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application can be embodied in the form of a software product in essence, or the part that contributes to the prior art or the part of the technical solution, and the computer software product is stored in a storage medium, including Several instructions are used to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present application. The aforementioned storage medium includes: a U disk, a removable hard disk, a read-only memory, a random access memory, a magnetic disk or an optical disk and other media that can store program codes.

The above are only specific embodiments of the present application, but the protection scope of the present application is not limited to this. should be covered within the scope of protection of this application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.

Claims (10)

1. a flow-free method of directional flow, is characterized in that, comprises: The CDN scheduling center of the content distribution network receives a playback scheduling request message sent by the user client, where the playback scheduling request message carries first indication information, where the first indication information is used to instruct the user client to request target free directional traffic; The CDN scheduling center sends a scheduling request response message to the user client according to the playback scheduling request message, where the scheduling request response message carries the target stream-free Internet Protocol IP address; The user client sends a play request message, where the play request message carries the target stream-free IP address; The target CDN node that receives the playback request message obtains the free directional traffic from the server corresponding to the target stream-free IP address; The target CDN node sends the free directed traffic to the user client. 2. The method according to claim 1, wherein before the CDN scheduling center sends a scheduling request response message to the user client according to the playback scheduling request message, the method further comprises: The CDN scheduling center performs subscription relationship authentication between the user client and the free directional traffic; The CDN scheduling center performs traffic limit authentication on the user client and the free directional traffic. 3. The method according to claim 2, wherein the play scheduling request message also carries the mobile phone number of the user client; Correspondingly, the CDN scheduling center sends a scheduling request response message to the user client according to the playback scheduling request message, including: The CDN dispatch center determines the attribution of the user client according to the mobile phone number; The CDN scheduling center determines the free flow IP address of the target server that can provide the flow-free directional service in the home location as the target flow-free IP address. 4. The method according to claim 3, wherein the playback scheduling request message is generated based on a hypertext transfer protocol HTTP application layer scheduling interface, and the parameters of the HTTP application layer scheduling interface include: the mobile phone of the user client Number, IP address of the user client, service profile SP identification, identification of the product requested by the user client, Uniform Resource Location System URL of the product requested by the user client, timestamp, key of the product requested by the user client, and user The encryption check code of the product requested by the client. 5. A flow-free system of directional flow, characterized in that, comprising: A CDN scheduling center of a content distribution network, configured to receive a playback scheduling request message sent by a user client, where the playback scheduling request message carries first indication information, and the first indication information is used to instruct the user client to request the target free of charge directed traffic; The CDN scheduling center is further configured to send a scheduling request response message to the user client according to the playback scheduling request message, where the scheduling request response message carries the target stream-free Internet Protocol IP address; The user client is configured to send a play request message, where the play request message carries the target stream-free IP address; The target CDN node that receives the playback request message is used to obtain the free directional traffic from the server corresponding to the target stream-free IP address; The target CDN node is further configured to send the free directed traffic to the user client. 6. The system according to claim 5, wherein before the CDN scheduling center sends a scheduling request response message to the user client according to the playback scheduling request message, the system is further configured to: The CDN dispatch center is also used to authenticate the subscription relationship between the user client and the free directional traffic; The CDN dispatch center is further configured to perform traffic limit authentication on the user client and the free directional traffic. 7. The method according to claim 6, wherein the play scheduling request message also carries the mobile phone number of the user client; Correspondingly, the CDN scheduling center is specifically used for: Determine the attribution of the user client according to the mobile phone number; The free flow IP address of the target server capable of providing the flow-free directional service in the home location is determined as the target flow-free IP address. 8. The system according to claim 7, wherein the playback scheduling request message is generated based on a hypertext transfer protocol HTTP application layer scheduling interface, and the parameters of the HTTP application layer scheduling interface include: the mobile phone of the user client Number, IP address of the user client, SP identification, identification of the product requested by the user client, URL of the product requested by the user client, timestamp, key of the product requested by the user client, and encryption of the product requested by the user client Check code. 9. A flow-free system for directional traffic, comprising: a plurality of memories and a plurality of processors; the memory is used to store program instructions; The processor is configured to invoke program instructions in the memory to perform the method of any one of claims 1 to 4. 10. A computer-readable medium, characterized in that the computer-readable medium stores a program code for computer execution, the program code comprising a program code for performing the method according to any one of claims 1 to 4 instruction.

Images