CN116980343A - Data stream transmission method, device, system, computer equipment and storage medium - Google Patents

Abstract

The application relates to a data stream transmission method, a device, a system, a computer device and a storage medium, which are used in a multicast gateway, wherein the method comprises the following steps: sending a first service request to a multicast server; adding a target multicast group according to the service response of the multicast server to the first service request, and receiving a multicast stream sent by the multicast server based on the target multicast group, wherein the multicast stream is a data stream based on a quick User Datagram Protocol (UDP) internet connection (QUIC) multicast protocol; and carrying out protocol conversion on the multicast stream to obtain a unicast stream based on a QUIC unicast protocol, and sending the unicast stream to a client. The application converts the multicast stream into the unicast stream and sends the unicast stream to the client through the multicast gateway, realizes the fusion bearing of the multicast and the unicast, and ensures that the unicast stream which is received by the client and is based on the QUIC unicast protocol does not need to be modified, thus the browser can be supported by adopting the method.

Description

Data streaming method, device, system, computer equipment and storage medium

Technical field

The present application relates to the field of network technology, and in particular to a data stream transmission method, device, system, computer equipment and storage medium.

Background technique

The QUIC (Quick User Datagram Protocol Internet Connection, Quick User Datagram Protocol UDP Internet Connection) protocol mainly carries live broadcast services in unicast mode, and the lowest cost solution is to carry large-scale live broadcast services in multicast mode.

However, the solution that IETF (The Internet Engineering Task Force) is developing to carry live broadcast services in multicast mode still has the problem of not supporting browsers.

Contents of the invention

Based on this, it is necessary to provide a data streaming transmission method, device, equipment, system and storage medium that can support the browser in view of the above technical problems.

In a first aspect, the present application provides a data stream transmission method for use in a multicast gateway. The method includes: sending a first service request to a multicast server; adding a data stream according to the multicast server's service response to the first service request. Target multicast group, and receive the multicast stream sent by the multicast server based on the target multicast group. The multicast stream is a data stream based on the Fast User Datagram Protocol UDP Internet Connection QUIC multicast protocol; perform protocol conversion on the multicast stream, Get the unicast stream based on QUIC unicast protocol and send the unicast stream to the client.

In one embodiment, sending the first service request to the multicast server includes: receiving a second service request sent by the client, and sending the first service request to the multicast server when triggered by the second service request.

In one embodiment, the second service request is a service request based on the QUIC unicast protocol. Triggered by the second service request, sending the first service request to the multicast server includes: performing protocol conversion processing on the second service request. , obtain the first service request based on the QUIC multicast protocol, and send the first service request to the multicast server.

In one embodiment, the first service request carries the authentication information in the second service request. The authentication information is used for the multicast server to feedback to the multicast gateway after passing the authentication of the multicast gateway based on the authentication information. Business response.

In one embodiment, the authentication information includes an encrypted correspondence between the address of the client and the address of the multicast gateway.

In one embodiment, the first service request carries token information in the second service request, and the token information is used by the multicast server to determine the address of the client based on the token information.

In one embodiment, the authentication information and token information are delivered to the client by the multicast scheduling server.

In one embodiment, the method further includes: receiving control information from the multicast server, and executing a multicast command process according to the control information.

In one embodiment, the method further includes: sending a third service request to the multicast server, and exiting the target multicast group according to the multicast server's service response to the third service request.

In one embodiment, sending the third service request to the multicast server includes: receiving the fourth service request sent by the client, and sending the third service request to the multicast server when triggered by the fourth service request.

In one embodiment, the fourth service request is a service request based on the QUIC unicast protocol. Triggered by the fourth service request, sending the third service request to the multicast server includes: performing protocol conversion processing on the fourth service request. , obtain the third service request based on the QUIC multicast protocol, and send the third service request to the multicast server.

In the second aspect, this application provides a data stream transmission method for use in a multicast scheduling server. The method includes: receiving a configuration request sent by a client based on the QUIC unicast protocol; and returning the address of the multicast gateway according to the configuration request. ; Wherein, the address of the multicast gateway is used by the client to send the second service request to the multicast gateway, so that the multicast gateway sends the first service request to the multicast server when triggered by the second service request.

In one embodiment, the configuration request includes a first configuration request, and the method further includes: generating token information according to the first configuration request and sending it to the client, where the token information is used by the multicast server to determine the client based on the token information. end address.

In one embodiment, the configuration request includes a second configuration request, and the method further includes: generating authentication information according to the second configuration request and sending it to the client, where the authentication information is used by the multicast server to configure the pair based on the authentication information. After the multicast gateway passes the authentication, the service response is fed back to the multicast gateway.

In one embodiment, the method further includes: configuring the address of the multicast gateway, configuring the correspondence between the client's address and the address of the multicast gateway, and generating a correspondence table between the client's address and the address of the multicast gateway.

In one embodiment, the method further includes: sending a monitoring request to the multicast gateway; receiving monitoring data sent by the multicast gateway based on the monitoring request; and determining the health status of the multicast gateway based on the monitoring data.

In a third aspect, this application provides a data stream transmission device, which is provided in a multicast gateway. The device includes: a first sending module for sending a first service request to the multicast server; a first receiving module for Join the target multicast group according to the service response of the multicast server to the first service request, and receive the multicast stream sent by the multicast server based on the target multicast group. The multicast stream is a data stream based on the QUIC multicast protocol; the second sending Module, used to convert the multicast stream into a protocol, obtain a unicast stream based on the QUIC unicast protocol, and send the unicast stream to the client.

In one embodiment, the first sending module is specifically configured to receive the second service request sent by the client, and send the first service request to the multicast server when triggered by the second service request.

In one embodiment, the second service request is a service request based on the QUIC unicast protocol. The first sending module is specifically configured to perform protocol conversion processing on the second service request to obtain the first service request based on the QUIC multicast protocol. , and sends the first service request to the multicast server.

In one embodiment, the first service request carries the authentication information in the second service request. The authentication information is used for the multicast server to feedback to the multicast gateway after passing the authentication of the multicast gateway based on the authentication information. Business response.

In one embodiment, the authentication information includes an encrypted correspondence between the address of the client and the address of the multicast gateway.

In one embodiment, the first service request carries token information in the second service request, and the token information is used by the multicast server to determine the address of the client based on the token information.

In one embodiment, the authentication information and token information are delivered to the client by the multicast scheduling server.

In one embodiment, the device further includes an execution module configured to receive control information from the multicast server and execute the multicast command process according to the control information.

In one embodiment, the device further includes a fourth sending module and a third receiving module. The fourth sending module is used to send a third service request to the multicast server. The third receiving module is used to send a third service request to the multicast server according to the multicast server. The service response requested by the third service exits the target multicast group.

In one embodiment, the fourth sending module is specifically configured to receive the fourth service request sent by the client, and send the third service request to the multicast server when triggered by the fourth service request.

In one embodiment, the fourth service request is a service request based on the QUIC unicast protocol, and the fourth sending module is specifically configured to perform protocol conversion processing on the fourth service request to obtain a third service request based on the QUIC multicast protocol. , and sends the third service request to the multicast server.

In the fourth aspect, this application provides a data stream transmission device, which is provided in a multicast scheduling server. The device includes: a second receiving module for receiving a configuration request sent by a client based on the QUIC unicast protocol; a third sending module. A module configured to return the address of the multicast gateway according to the configuration request; wherein the address of the multicast gateway is used by the client to send a second service request to the multicast gateway, so that the multicast gateway can send the multicast gateway to the multicast gateway when triggered by the second service request. The broadcast server sends the first service request.

In one embodiment, the configuration request includes a first configuration request, and the device further includes a first generating module configured to generate token information according to the first configuration request and send it to the client, where the token information is used for multicast The server determines the client's address based on the token information.

In one embodiment, the configuration request includes a second configuration request, and the device further includes a second generation module for generating authentication information according to the second configuration request and sending it to the client, where the authentication information is used for multicast After the server passes the authentication of the multicast gateway based on the authentication information, the server feeds back a service response to the multicast gateway.

In one embodiment, the device further includes a configuration module for configuring the address of the multicast gateway, configuring the correspondence between the client's address and the multicast gateway's address, and generating a correspondence between the client's address and the multicast gateway's address. Relational tables.

In one embodiment, the device further includes a monitoring module, configured to send a monitoring request to the multicast gateway; receive monitoring data sent by the multicast gateway based on the monitoring request; and determine the health status of the multicast gateway based on the monitoring data.

In a fifth aspect, this application provides a data stream transmission system. The system includes a multicast gateway, a multicast scheduling server, a multicast server and a client; the multicast gateway is used to perform any of the above first or second aspects. The steps performed by the multicast gateway of one of the above items; the multicast scheduling server is used to perform the steps performed by the multicast scheduling server of any one of the above first aspect or the second aspect; the multicast server is used to perform the above mentioned third aspect. The steps performed by the multicast server in any one of the first aspect or the second aspect; the client is used to perform the steps performed by the client in any one of the first aspect or the second aspect.

In a sixth aspect, this application also provides a computer device. The computer device includes a memory and a processor. The memory stores a computer program. When the processor executes the computer program, the steps of the method described in any one of the above first or second aspects are implemented.

In a seventh aspect, this application also provides a computer-readable storage medium. The computer-readable storage medium has a computer program stored thereon, and when the computer program is executed by a processor, the steps of the method described in any one of the above-mentioned first or second aspects are implemented.

In an eighth aspect, this application also provides a computer program product. The computer program product includes a computer program that, when executed by a processor, implements the steps of the method described in any one of the first aspect or the second aspect.

In the above data stream transmission method, device, system, computer equipment and storage medium, the multicast gateway sends a first service request to the multicast server, and then joins the target multicast group according to the multicast server's service response to the first service request, and Based on the target multicast group, the multicast stream sent by the multicast server is received. The multicast stream is a data stream based on the Fast User Datagram Protocol UDP Internet Connection QUIC multicast protocol. Then the multicast gateway converts the multicast stream into a protocol based on QUIC unicast protocol unicast stream, and sends the unicast stream to the client. In this way, the multicast stream is converted into a unicast stream and sent to the client through the multicast gateway, realizing the integrated bearing of multicast and unicast, so that What the client receives is still the unicast stream based on the QUIC unicast protocol, and there is no need to modify the client, so this method can support the browser.

Description of the drawings

Figure 1 is an application environment diagram of a data stream transmission method in one embodiment;

Figure 2 is a schematic diagram of system deployment for implementing the QUIC multicast protocol in one embodiment;

Figure 3 is a schematic flowchart of a data stream transmission method in one embodiment;

Figure 4 is a schematic diagram of the interaction between a multicast gateway, a multicast server and a client in one embodiment;

Figure 5 is a schematic diagram of protocol conversion between a client, a multicast gateway and a multicast server in one embodiment;

Figure 6 is a schematic diagram of a multicast server authenticating a client and a multicast gateway in one embodiment;

Figure 7 shows another data stream transmission method in one embodiment;

Figure 8 is a schematic diagram of a multicast scheduling server scheduling a multicast gateway in an embodiment;

Figure 9 shows another data stream transmission method in an embodiment;

Figure 10 is a structural block diagram of a data stream transmission device in one embodiment;

Figure 11 is a structural block diagram of another data stream transmission device in one embodiment;

Figure 12 is a structural block diagram of a data stream transmission system in one embodiment;

Figure 13 is an internal structure diagram of a computer device in one embodiment.

Detailed ways

In order to make the purpose, technical solutions and advantages of the present application more clear, the present application will be further described in detail below with reference to the drawings and embodiments. It should be understood that the specific embodiments described here are only used to explain the present application and are not used to limit the present application.

Figure 1 is a schematic diagram of an application scenario of a data stream transmission method provided by an embodiment of the present application. As shown in Figure 1, this scenario includes all devices in the multicast gateway 101, multicast scheduling server 102, multicast server 103, client 104, and publishing client 105, and may also include only some devices. Among them, the publishing client 105 is used to upload the multicast stream to the multicast server, the multicast scheduling server 102 is used to configure a multicast gateway for the client 104 based on the client's configuration request, and the multicast gateway 101 is used to configure the multicast gateway based on the client 104. The service request obtains the multicast stream from the multicast server 103 and converts it into a unicast stream, and sends the unicast stream to the client 104. The client 104 is compatible with the existing QUIC protocol and is a client that can be applied on the browser.

As a new generation transmission protocol, the QUIC protocol implements a reliable, secure, and low-latency transmission layer design based on UDP. It is very suitable for IPTV (Internet Protocol television, interactive network television), OTT (Over The Top), and provides applications to users through the Internet. Service) and other live broadcast services are carried; the QUIC protocol is designed as an application layer protocol of HTTP3 (Hypertext Transfer Protocol 3, the third version of Hypertext Transfer Protocol), and is mainly carried in unicast mode. However, the lowest cost is to use multicast to carry large-scale live broadcast services. plan.

The IETF is formulating the QUIC multicast protocol and solution. As shown in Figure 2, a system deployment diagram for implementing the QUIC multicast protocol is provided. The system includes a QUIC multicast client and a QUIC multicast server. Among them, the QUIC multicast client The client includes the QUIC multicast control client and the QUIC multicast receiving client, the QUIC multicast server includes the QUIC multicast control server and the QUIC multicast source server; the connection between the QUIC multicast control client and the QUIC multicast control server Extended QUIC multicast control information flow transmission is performed, and QUIC multicast media data flow (also called QUIC multicast data flow) is transmitted between the QUIC multicast receiving client and the QUIC multicast source server.

However, the above-mentioned QUIC multicast client does not support browsers, which leads to security issues in multicast. Therefore, the above-mentioned QUIC multicast protocol and solution have not yet entered the working group documentation stage. Based on this, it is necessary to propose effective technical means to solve this problem.

In one embodiment, as shown in Figure 3, a data stream transmission method is provided for use in a multicast gateway. The method includes the following steps:

Step 301: The multicast gateway sends a first service request to the multicast server.

The multicast gateway may be a device controlled by an operator. The multicast server may be a QUIC multicast server in the QUIC multicast protocol and solution developed by the IETF. The multicast server includes a QUIC multicast control server and a QUIC multicast source server.

The extended QUIC multicast control information stream is transmitted between the multicast gateway and the QUIC multicast control server, and the QUIC multicast data stream is transmitted between the multicast gateway and the QUIC multicast source server.

The first service request may be a live broadcast request sent by the multicast gateway to the multicast server, and the first service request is a service request based on the QUIC multicast protocol, that is, an extended QUIC request. The first service request carries at least one of the domain name sample.com, token information Token, and authentication information Authinfo.

Optionally, after receiving the live broadcast request sent by the client, the multicast gateway sends the first service request to the multicast server.

For example, the first business request HTTP://sample.com/live1/live1? Token=***&Authinfo.

Step 302: The multicast gateway joins the target multicast group according to the multicast server's service response to the first service request, and receives the multicast stream sent by the multicast server based on the target multicast group. The multicast stream is based on the QUIC multicast protocol. data flow.

The service response is control information based on the QUIC multicast protocol, that is, extended QUIC multicast control information, which includes a multicast group joining instruction carrying a multicast address.

Optionally, after receiving the first service request, the multicast server sends a multicast group join instruction carrying a multicast address to the multicast gateway based on the QUIC multicast protocol according to the first service request. The multicast group join instruction is used to Instructs the multicast gateway to join the target multicast group corresponding to the multicast address. After the multicast gateway receives the multicast group joining instruction, it will write the multicast address to the receiving port to join the target multicast group. Therefore, after the multicast server sends the multicast stream to the target multicast group, the group The multicast gateway can receive multicast streams through this receiving port.

The multicast gateway can also join the target multicast group by using the Internet Group Management Protocol (IGMP) method to join the target multicast group.

Step 303: The multicast gateway performs protocol conversion on the multicast stream, obtains a unicast stream based on the QUIC unicast protocol, and sends the unicast stream to the client.

Among them, the client is a QUIC universal client, which is compatible with the existing QUIC protocol and can be widely used on browsers.

Optionally, the multicast gateway unpacks the multicast stream based on the QUIC multicast protocol to obtain the original data stream, and then repackages the original data stream based on the QUIC unicast protocol to obtain the unicast stream based on the QUIC unicast protocol. The unicast stream is then sent to the client through the sending port.

In addition, the distance between the multicast gateway and the client can be set as needed. If the distance between the multicast gateway and the client is relatively close, such as one kilometer, then wireless transmission can be achieved between the multicast gateway and the client, so that the data flow of this application The transmission method supports wireless transmission.

In the above data stream transmission method, the multicast gateway sends a first service request to the multicast server, then joins the target multicast group based on the multicast server's service response to the first service request, and receives the multicast server based on the target multicast group. The multicast stream sent is a data stream based on the QUIC multicast protocol. The multicast gateway then converts the multicast stream into a protocol to obtain a unicast stream based on the QUIC unicast protocol, and sends the unicast stream to the client. end, in this way, the multicast stream is converted into a unicast stream and sent to the client through the multicast gateway, realizing the integrated bearer of multicast and unicast, so that the client still receives the unicast stream based on the QUIC unicast protocol, without the need for The client is modified so that the browser can be supported using this method, which can improve security.

In one embodiment, sending the first service request to the multicast server includes: receiving a second service request sent by the client, and sending the first service request to the multicast server when triggered by the second service request.

Optionally, the second service request is a service request based on the QUIC unicast protocol. The first service request is sent to the multicast server triggered by the second service request, including: performing protocol conversion processing on the second service request to obtain the service request based on the QUIC unicast protocol. A first service request of the QUIC multicast protocol, and sends the first service request to the multicast server.

The second service request is a service request based on the QUIC unicast protocol, that is, a non-extended QUIC request. The second service request may be a live broadcast request sent by the client to the multicast gateway. The second service request carries at least one of the multicast gateway address GWIP, domain name sample.com, token information Token, and authentication information Authinfo.

For example, the second service request HTTP://GWIP/sample.com/live1? Token=***&Authinfo.

In another optional embodiment, based on the above embodiment, a schematic diagram of interaction between a multicast gateway, a multicast server and a client is provided, as shown in Figure 4. The multicast gateway includes a QUIC multicast control client and QUIC multicast stream conversion client and QUIC multicast proxy client. The interaction principle is as follows:

The client sends a non-extended QUIC request (second service request) to the QUIC multicast proxy client. The QUIC multicast proxy client performs protocol conversion on the non-extended QUIC request, obtains the extended QUIC request (first service request), and sends the extended QUIC request to the QUIC multicast control client and the QUIC multicast stream conversion client respectively.

After receiving the extended QUIC request, the QUIC multicast control client establishes a QUIC connection with the multicast server and sends an extended QUIC request to the QUIC multicast control server in the multicast server. The QUIC multicast control server sends an extended QUIC request to the QUIC server based on the extended QUIC request. The multicast control client sends a multicast group join instruction carrying a multicast address, and the QUIC multicast control client writes the multicast address into the QUIC multicast stream conversion client to enable the multicast gateway to join the target multicast group, thereby After the QUIC multicast source server in the multicast server sends the multicast stream to the target multicast group, the QUIC multicast stream conversion client can receive the multicast stream.

The QUIC multicast stream conversion client forwards the multicast stream to the QUIC multicast proxy client based on the extended QUIC request. The QUIC multicast proxy client performs protocol conversion on the multicast stream to obtain a unicast stream, and sends the unicast stream to the client to complete the transmission of the data stream.

In addition, as shown in Figure 5, a schematic diagram of protocol conversion between the client, the multicast gateway and the multicast server is provided, in which QUIC unicast is supported between the client, the multicast server and the multicast server. protocol, that is, the non-extended QUIC protocol. What is supported between the multicast server and the multicast server is the QUIC multicast protocol, which is the extended QUIC protocol. Therefore, when the multicast gateway receives the client's service request, it needs to perform protocol conversion on the service request, that is, to implement conversion between the HTTP application layer and the QUIC transport layer.

The client sends a non-extended QUIC request to the multicast gateway, and the multicast gateway performs protocol conversion on the non-extended QUIC request and obtains the extended QUIC request.

The client can also directly send a non-extended QUIC request to the multicast server, and the multicast server sends a unicast stream to the client based on the non-extended QUIC request.

The client can send non-extended QUIC requests to both the multicast server and the multicast gateway,

In one embodiment, the first service request carries the authentication information in the second service request. The authentication information is used for the multicast server to feedback to the multicast gateway after passing the authentication of the multicast gateway based on the authentication information. Business response.

Among them, the authentication information includes the encrypted correspondence between the client's address and the address of the multicast gateway. The authentication information is delivered to the client by the multicast scheduling server. For its specific implementation, see the following implementation on the multicast scheduling server side. For example, I won’t go into details here.

Optionally, after receiving the first service request, the multicast server parses the first service request. If the authentication information is obtained through the parsing, it means that the multicast gateway is legal, and the multicast gateway has passed the authentication. Otherwise, it means that the multicast gateway has passed the authentication. If it is illegal, the multicast gateway authentication fails.

In one embodiment, the first service request carries token information in the second service request, and the token information is used by the multicast server to determine the address of the client based on the token information.

The token information is delivered to the client by the multicast scheduling server. The specific implementation method can be found in the following embodiments on the multicast scheduling server side, which will not be described again here. This token information is used by the client to simplify re-authentication within the validity period.

As shown in Figure 6, a schematic diagram of the multicast server authenticating the client and the multicast gateway is provided. In it, both the client and the multicast gateway can send service requests to the multicast server, and the multicast server can pass the service request. Whether it carries authentication information is used to determine whether the service request comes from the client or the multicast gateway.

For example, the client sends a service request carrying the domain name Domain1 and token information Token to the multicast server. After the multicast gateway receives the service request from the client that carries the multicast gateway address, domain name Domain1, token information Token, and authentication information Authinfo, the multicast gateway sends the multicast server the service request carrying the domain name Domain1, token information Token, and Business request for authentication information Authinfo. After the multicast server receives the service requests sent by the client and the multicast gateway respectively, it can determine whether the service request comes from the client or the multicast gateway based on whether the service request carries authentication information.

In one embodiment, the method further includes: receiving control information from the multicast server, and executing a multicast command process according to the control information.

Among them, the control information includes multicast group joining instructions, multicast group exit instructions, etc. The process of executing multicast commands according to the control information includes: executing corresponding network layer multicast commands on the corresponding ports according to the control information, such as IGMP Join (Internet Group Management Protocol Join, join the Internet Group Management Protocol).

The process of the multicast gateway executing the multicast command according to the multicast group joining instruction has been described in detail in the above embodiments. The following will elaborate on the process of the multicast gateway executing the multicast command according to the multicast group exit instruction.

In one embodiment, the method further includes: sending a third service request to the multicast server, and exiting the target multicast group according to the multicast server's service response to the third service request.

Optionally, sending the third service request to the multicast server includes: receiving the fourth service request sent by the client, and sending the third service request to the multicast server when triggered by the fourth service request.

Sending a third service request to the multicast server triggered by the fourth service request includes: performing protocol conversion processing on the fourth service request, obtaining a third service request based on the QUIC multicast protocol, and sending the third service request to Multicast server.

Exiting the target multicast group according to the service response of the multicast server to the fourth service request includes: after the multicast server receives the third service request, according to the third service request, the multicast packet is sent to the multicast gateway based on the QUIC multicast protocol. The multicast group exit command of the address is used to instruct the multicast gateway to exit the target multicast group corresponding to the multicast address. After receiving the multicast group exit command, the multicast gateway will delete the multicast address from the receiving port to exit the target multicast group.

The third service request may be a live broadcast exit request sent by the multicast gateway to the multicast server, and the third service request is a service request based on the QUIC multicast protocol, that is, an extended QUIC request. The third service request carries at least one of the domain name sample.com, token information Token, and authentication information Authinfo.

The fourth service request may be a live broadcast exit request sent by the client to the multicast gateway, and the fourth service request is a service request based on the QUIC unicast protocol, that is, a non-extended QUIC request. The fourth service request carries at least one of the multicast gateway address GWIP, domain name sample.com, token information Token, and authentication information Authinfo.

In addition, the multicast gateway can also receive the fifth service request sent by the client. When triggered by the fifth service request, the multicast gateway stops receiving the multicast stream from the multicast server and sending the unicast stream to the client.

The fifth service request may be a live broadcast pause request sent by the client to the multicast gateway, and the fifth service request is a service request based on the QUIC unicast protocol, that is, a non-extended QUIC request. The fifth service request carries at least one of the multicast gateway address GWIP, domain name sample.com, token information Token, and authentication information Authinfo.

In one embodiment, as shown in Figure 7, another data stream transmission method is provided for use in a multicast scheduling server. The method includes the following steps:

Step 701: The multicast scheduling server receives the configuration request sent by the client based on the QUIC unicast protocol.

The multicast scheduling server may be a device controlled by an operator. The configuration request is used by the client to request the multicast scheduling server to configure a multicast gateway for it. The configuration request is a request sent by the client based on the QUIC unicast protocol.

Optionally, before sending the second service request to the multicast gateway, the client needs to send a configuration request to the multicast scheduling server.

Step 702: The multicast scheduling server returns the address of the multicast gateway according to the configuration request; where the address of the multicast gateway is used by the client to send the second service request to the multicast gateway, so that the multicast gateway can trigger the second service request. Next, the first service request is sent to the multicast server.

Among them, the multicast scheduling server can query the address of the multicast gateway serving the client from the configuration database according to the client's address. The configuration database stores multiple sets of correspondences between the addresses of different clients and the multicast gateway. The multicast gateway and the client can have a one-to-many relationship, that is, one multicast gateway can serve multiple clients. In addition, the multicast scheduling server may return the address of the multicast gateway according to the configuration request, and the multicast scheduling server may return the address of the multicast gateway based on the QUIC unicast protocol.

Optionally, after the client obtains the address of the multicast gateway, it sends a second service request to the multicast gateway. The multicast gateway sends a first service request to the multicast server under the trigger of the second service request. The first service request uses The multicast gateway joins the target multicast group according to the multicast server's service response to the first service request, receives the multicast stream sent by the multicast server based on the target multicast group, and performs protocol conversion on the multicast stream to obtain a QUIC-based single unicast stream of the QUIC multicast protocol and sends the unicast stream to the client, where the multicast stream is a data stream based on the QUIC multicast protocol. In addition, the specific implementation method for the multicast gateway to implement this step can be found in the above-mentioned embodiment on the multicast gateway side, and will not be described again here.

In the above data stream transmission method, the multicast scheduling server receives the configuration request sent by the client based on the QUIC unicast protocol, and then returns the address of the multicast gateway according to the configuration request. The address of the multicast gateway is used by the client to send data to the multicast gateway. The second service request is for the multicast gateway to send the first service request to the multicast server when triggered by the second service request. The first service request is used for the multicast gateway to send the first service request to the multicast server, and then Join the target multicast group according to the service response of the multicast server to the first service request, and receive the multicast stream sent by the multicast server based on the target multicast group. The multicast stream is a data stream based on the QUIC multicast protocol, and then multicast The gateway performs protocol conversion on the multicast stream to obtain a unicast stream based on the QUIC unicast protocol, and sends the unicast stream to the client. In this way, the multicast stream is converted into a unicast stream through the multicast gateway and sent to the client. Implementing the integrated bearer of multicast and unicast allows the client to receive unicast streams based on the QUIC unicast protocol without the need to modify the client. Therefore, this method can support browsers, thereby improving security.

In one embodiment, the configuration request includes a first configuration request, and the method further includes: generating token information according to the first configuration request and sending it to the client, where the token information is used by the multicast server to determine the client based on the token information. end address.

The first configuration request may be a live broadcast request sent by the client to the multicast scheduling server, and the first configuration request carries the domain name sample.com, for example, HTTP://sample.com/live1.

Optionally, the multicast scheduling server is installed with a HASH (hash) client, which can generate token information Token based on the client's address, which can be used by the client to simplify re-authentication within the validity period. The multicast scheduling server sends the token information Token to the client in the format of the first response information to implement redirection to QUIC scheduling. The format of the first response information is such as HTTP://sample.QuicRR.com/live1? Token=***.

In one embodiment, the configuration request includes a second configuration request, and the method further includes: generating authentication information according to the second configuration request and sending it to the client, where the authentication information is used by the multicast server to configure the pair based on the authentication information. After the multicast gateway passes the authentication, the service response is fed back to the multicast gateway.

The second configuration request may be a live broadcast request sent by the client to the multicast scheduling server. The second configuration request carries the token information Token and the domain name sample.QuicRR.com, for example, HTTP://sample.QuicRR.com/ live1? Token=***, which can be directed to the multicast scheduling server through domain name change.

The authentication information includes the encrypted correspondence between the client's address and the address of the multicast gateway.

Optionally, after the multicast scheduling server receives the second configuration request sent by the client, the multicast scheduling server checks whether there is a multicast gateway suitable for serving the client. If it exists, the client's information is encrypted using a shared symmetric encryption algorithm. address and the address of the multicast gateway to generate authentication information Authinfo. The multicast scheduling server sends the authentication information Authinfo to the client in the format of the second response information to implement redirection to the multicast gateway. The format of the second response information is, for example, HTTP://GWIP/sample.com/live1? Token=***&Authinfo.

If it does not exist, the multicast scheduling server sends the response message to the client in the format of the third response information to implement redirection to the multicast server. The format of the third response information is, for example, HTTP://sample.com/live1/ live1? Token=***. At this time, the client sends the sixth service request to the multicast server based on the QUIC unicast protocol, and the multicast server responds to the client according to the sixth service request, that is, sends the unicast stream to the client. This process is an ordinary live broadcast service. The sixth business request is HTTP://sample.com/live1? Token=***.

In this embodiment, the authentication information is generated by the multicast scheduling server, which can prevent the multicast gateway and the client from decrypting and forging the authentication information. In addition, the client sends two live broadcast requests (the first configuration request and the second configuration request) to the multicast scheduling server based on the QUIC unicast protocol, and the multicast scheduling server returns the address of the multicast gateway based on the QUIC unicast protocol, realizing The multicast scheduling server uses the non-extended QUIC protocol to guide live application layer requests to the multicast gateway.

In one embodiment, the method further includes: configuring the address of the multicast gateway, configuring the correspondence between the client's address and the address of the multicast gateway, and generating a correspondence table between the client's address and the address of the multicast gateway.

In one embodiment, the method further includes: sending a monitoring request to the multicast gateway; receiving monitoring data sent by the multicast gateway based on the monitoring request; and determining the multicast gateway based on the monitoring data. health status.

Wherein, both the address of the multicast gateway and the address of the client may be IP (Internet Protocol) addresses.

Optionally, as shown in Figure 8, a schematic diagram of a multicast scheduling server scheduling a multicast gateway is provided. There are multiple multicast gateways, and the multicast scheduling server includes a multicast gateway management client and a multicast scheduling client. .

The multicast gateway management client has the function of managing and configuring the parameters of the multicast gateway, including managing and configuring the IP address and port of the multicast gateway, the version of the multicast gateway, authentication information, etc. The multicast gateway management client also has the function of monitoring the health status of the multicast gateway and reporting it to the multicast scheduling client. There are two implementation methods, as follows:

First, the multicast gateway management client sends a monitoring request to the multicast gateway, receives the monitoring data sent by the multicast gateway based on the monitoring request, and determines the health status of the multicast gateway based on the monitoring data.

Second, the multicast gateway management client periodically receives status data sent by the multicast gateway and determines the health status of the multicast gateway based on the status data.

The multicast scheduling client has the function of establishing and maintaining a correspondence table between the client's address and the address of the multicast gateway. The multicast scheduling client also has the function of generating authentication information Authinfo during scheduling.

In another embodiment, before the client sends the first configuration request to the multicast scheduling server, the publishing client, that is, the live broadcast source, will upload the live broadcast to the multicast server, and the multicast server will convert the live broadcast into multicast stream and send it to the network, and then the multicast server sends the unicast URL (Uniform Resource Locator, Uniform Resource Locator) and multicast address of the live broadcast to the multicast scheduling server. The multicast scheduling server generates token information Token based on the unicast URL and multicast address.

In summary, as shown in Figure 9, another data stream transmission method is provided for the data stream transmission system. The data stream transmission system includes a client, a multicast gateway, a multicast scheduling server, a multicast server and a publishing system. client. The method is divided into two parts. The first part is live broadcast release, and the second part is live broadcast service. The second part can be divided into QUIC multicast service and ordinary live broadcast service. The contents of each part are as follows:

1. Live broadcast, which includes the following steps:

Step 901: The publishing client uploads the live broadcast to the multicast server.

Step 902: The multicast server converts the live broadcast into a multicast stream based on the QUIC multicast protocol and sends it to the network.

Step 903: The multicast server sends the live unicast URL and multicast address to the multicast scheduling server.

2. Live broadcast services include QUIC multicast services and ordinary live broadcast services. The differences between QUIC multicast services and ordinary live broadcast services are as follows:

2.1. QUIC multicast service, which includes the following steps:

Step 904: The client sends a first configuration request (live broadcast request) to the multicast scheduling server, such as HTTP://sample.com/live1.

Step 905: The multicast scheduling server authenticates the client and generates token information Token according to the client's address.

Step 906: The multicast scheduling server sends the token information Token to the client. For example, the multicast scheduling server sends the token information Token to the client in the format of the first response information to implement redirection to QUIC scheduling. The format of the first response information is such as HTTP://sample.QuicRR.com/live1? Token=***.

Step 907: The client sends a second configuration request (live broadcast request) to the multicast scheduling server, such as HTTP://sample.QuicRR.com/live1? Token=***.

Step 908a: The multicast scheduling server checks whether a suitable multicast network gateway exists. If the result is that it exists, step 909a is executed;

Step 909a: The multicast scheduling server generates authentication information Authinfo and sends it to the client. For example, the multicast scheduling server sends the authentication information Authinfo to the client in the format of the second response information to implement redirection to the multicast gateway. The format of the second response information is, for example, HTTP://GWIP/sample.com/live1 ? Token=***&Authinfo.

Step 910a: The client sends a second service request (live broadcast request) to the multicast gateway, such as HTTP://GWIP/sample.com/live1? Token=***&Authinfo.

Step 911: The multicast gateway sends a first service request (extended QUIC request) to the multicast server, such as HTTP://sample.com/live1/live1? Token=***&Authinfo.

Step 912: The multicast server checks the authentication information Authinfo. If the result is that the authentication is passed, step 913 is executed.

Step 913: The multicast server sends response information to the multicast gateway.

Step 914: The multicast gateway uses the IGMP protocol to join the target multicast group.

Step 915: The multicast gateway converts the multicast stream into a unicast stream and sends it to the client.

2.2. Ordinary live broadcast service, which includes the following steps:

Step 908b: The multicast scheduling server checks whether a suitable multicast network gateway exists. If the result is that it does not exist, step 909b is executed.

Step 909b: The scheduling server sends the response message to the client in the format of the third response information to implement redirection to the multicast server. The format of the third response information is, for example, HTTP://sample.com/live1/live1? Token=***.

Step 910b: The client sends a sixth service request to the multicast server based on the QUIC unicast protocol. The multicast server responds to the client according to the sixth service request, that is, sends the unicast stream to the client. This process is an ordinary live broadcast service. The sixth business request is HTTP://sample.com/live1? Token=***.

It should be understood that although the steps in the flowcharts involved in the above-mentioned embodiments are shown in sequence as indicated by the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated in this article, there is no strict order restriction on the execution of these steps, and these steps can be executed in other orders. Moreover, at least some of the steps in the flowcharts involved in the above embodiments may include multiple steps or stages. These steps or stages are not necessarily executed at the same time, but may be completed at different times. The execution order of these steps or stages is not necessarily sequential, but may be performed in turn or alternately with other steps or at least part of the steps or stages in other steps.

Based on the same inventive concept, embodiments of the present application also provide a data stream transmission device for implementing the above-mentioned data stream transmission method. The implementation solution provided by this device to solve the problem is similar to the implementation solution recorded in the above method. Therefore, the specific limitations in the one or more data stream transmission device embodiments provided below can be found in the above description of the data stream transmission method. Limitations will not be repeated here.

In one embodiment, as shown in Figure 10, a data stream transmission device is provided, which is provided in a multicast gateway. The data stream transmission device 1000 includes: a first sending module 1001, a first receiving module 1002 and a second Send module 1003, where:

The first sending module 1001 is used to send a first service request to the multicast server.

The first receiving module 1002 is configured to join the target multicast group according to the multicast server's service response to the first service request, and receive the multicast stream sent by the multicast server based on the target multicast group. The multicast stream is QUIC-based multicast. Protocol data flow.

The second sending module 1003 is used to perform protocol conversion on the multicast stream, obtain a unicast stream based on the QUIC unicast protocol, and send the unicast stream to the client.

In one embodiment, the first sending module 1001 is specifically configured to receive a second service request sent by the client, and send the first service request to the multicast server when triggered by the second service request.

In one embodiment, the second service request is a service request based on the QUIC unicast protocol. The first sending module is specifically configured to perform protocol conversion processing on the second service request to obtain the first service request based on the QUIC multicast protocol. , and sends the first service request to the multicast server.

In one embodiment, the first service request carries the authentication information in the second service request. The authentication information is used for the multicast server to feedback to the multicast gateway after passing the authentication of the multicast gateway based on the authentication information. Business response.

In one embodiment, the authentication information includes an encrypted correspondence between the address of the client and the address of the multicast gateway.

In one embodiment, the first service request carries token information in the second service request, and the token information is used by the multicast server to determine the address of the client based on the token information.

In one embodiment, the authentication information and token information are delivered to the client by the multicast scheduling server.

In one embodiment, the device further includes an execution module configured to receive control information from the multicast server and execute the multicast command process according to the control information.

In one embodiment, the device further includes a fourth sending module and a third receiving module. The fourth sending module is used to send a third service request to the multicast server. The third receiving module is used to send a third service request to the multicast server according to the multicast server. The service response requested by the third service exits the target multicast group.

In one embodiment, the fourth sending module is specifically configured to receive the fourth service request sent by the client, and send the third service request to the multicast server when triggered by the fourth service request.

In one embodiment, the fourth service request is a service request based on the QUIC unicast protocol, and the fourth sending module is specifically configured to perform protocol conversion processing on the fourth service request to obtain a third service request based on the QUIC multicast protocol. , and sends the third service request to the multicast server.

In one embodiment, as shown in Figure 11, another data stream transmission device is provided, which is provided in the multicast scheduling server. The data stream transmission device 1100 includes: a second receiving module 1101 and a third sending module 1102, in:

The second receiving module 1101 is used to receive the configuration request sent by the client based on the QUIC unicast protocol.

The third sending module 1102 is configured to return the address of the multicast gateway according to the configuration request; wherein the address of the multicast gateway is used by the client to send the second service request to the multicast gateway, so that the multicast gateway can respond to the second service request. The first service request is sent to the multicast server when triggered.

In one embodiment, the configuration request includes a first configuration request, and the device further includes a first generating module configured to generate token information according to the first configuration request and send it to the client, where the token information is used for multicast The server determines the client's address based on the token information.

In one embodiment, the configuration request includes a second configuration request, and the device further includes a second generation module for generating authentication information according to the second configuration request and sending it to the client, where the authentication information is used for multicast After the server passes the authentication of the multicast gateway based on the authentication information, the server feeds back a service response to the multicast gateway.

In one embodiment, the device further includes a configuration module for configuring the address of the multicast gateway, configuring the correspondence between the client's address and the address of the multicast gateway, and generating a correspondence between the client's address and the address of the multicast gateway. Relational tables.

In one embodiment, the device further includes a monitoring module, configured to send a monitoring request to the multicast gateway; receive monitoring data sent by the multicast gateway based on the monitoring request; and determine the health status of the multicast gateway based on the monitoring data.

Each module in the above-mentioned data stream transmission device can be implemented in whole or in part by software, hardware and combinations thereof. Each of the above modules may be embedded in or independent of the processor of the computer device in the form of hardware, or may be stored in the memory of the computer device in the form of software, so that the processor can call and execute the operations corresponding to the above modules.

In one embodiment, as shown in Figure 12, a structural block diagram of a data stream transmission system is provided. The system includes a multicast gateway, a multicast scheduling server, a multicast server and a client.

The multicast scheduling server includes: multicast gateway management client and multicast scheduling client; the multicast scheduling server includes QUIC multicast control server and QUIC multicast source server; the multicast gateway includes QUIC multicast control client and QUIC Multicast stream conversion client and QUIC multicast proxy client.

The multicast gateway is used to perform the steps performed by the multicast gateway in any of the above method embodiments; the multicast scheduling server is used to perform the steps performed by the multicast scheduling server in any of the above method embodiments; The multicast server is used to perform the steps performed by the multicast server in any of the above method embodiments; the client is used to perform the steps performed by the client in any of the above method embodiments, which will not be repeated here. Describe the detailed implementation method.

In one embodiment, a computer device is provided. The computer device may be a server, and its internal structure diagram may be as shown in Figure 13. The computer device includes a processor, a memory, an input/output interface (Input/Output, referred to as I/O), and a communication interface. Among them, the processor, memory and input/output interface are connected through the system bus, and the communication interface is connected to the system bus through the input/output interface. Wherein, the processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes non-volatile storage media and internal memory. The non-volatile storage medium stores operating systems, computer programs and databases. This internal memory provides an environment for the execution of operating systems and computer programs in non-volatile storage media. The computer device's database is used for data such as multicast streams and unicast streams. The input/output interface of the computer device is used to exchange information between the processor and external devices. The communication interface of the computer device is used to communicate with an external terminal through a network connection. The computer program implements a data streaming method when executed by a processor.

Those skilled in the art can understand that the structure shown in Figure 13 is only a block diagram of a partial structure related to the solution of the present application, and does not constitute a limitation on the computer equipment to which the solution of the present application is applied. Specific computer equipment can May include more or fewer parts than shown, or combine certain parts, or have a different arrangement of parts.

In one embodiment, a computer device is provided, including a memory and a processor. A computer program is stored in the memory. When the processor executes the computer program, it implements the steps described in any of the above method embodiments.

In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the steps described in any of the above method embodiments are implemented.

In one embodiment, a computer program product is provided, including a computer program that, when executed by a processor, implements the steps described in any of the above method embodiments.

Those of ordinary skill in the art can understand that all or part of the processes in the methods of the above embodiments can be completed by instructing relevant hardware through a computer program. The computer program can be stored in a non-volatile computer-readable storage. In the media, when executed, the computer program may include the processes of the above method embodiments. Any reference to memory, database or other media used in the embodiments provided in this application may include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive memory (ReRAM), magnetic variable memory (Magnetoresistive Random) Access Memory (MRAM), Ferroelectric Random Access Memory (FRAM), Phase Change Memory (PCM), graphene memory, etc. Volatile memory may include random access memory (Random Access Memory, RAM) or external cache memory. By way of illustration but not limitation, RAM can be in various forms, such as static random access memory (Static Random Access Memory, SRAM) or dynamic random access memory (Dynamic Random Access Memory, DRAM). The databases involved in the various embodiments provided in this application may include at least one of a relational database and a non-relational database. Non-relational databases may include blockchain-based distributed databases, etc., but are not limited thereto. The processors involved in the various embodiments provided in this application may be general-purpose processors, central processing units, graphics processors, digital signal processors, programmable logic devices, quantum computing-based data processing logic devices, etc., and are not limited to this.

The technical features of the above embodiments can be combined in any way. To simplify the description, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, all possible combinations should be used. It is considered to be within the scope of this manual.

The above-described embodiments only express several implementation modes of the present application, and their descriptions are relatively specific and detailed, but should not be construed as limiting the patent scope of the present application. It should be noted that, for those of ordinary skill in the art, several modifications and improvements can be made without departing from the concept of the present application, and these all fall within the protection scope of the present application. Therefore, the scope of protection of this application should be determined by the appended claims.

Claims (22)

1. A method of data streaming for use in a multicast gateway, the method comprising:

sending a first service request to a multicast server;

adding a target multicast group according to the service response of the multicast server to the first service request, and receiving a multicast stream sent by the multicast server based on the target multicast group, wherein the multicast stream is a data stream based on a quick User Datagram Protocol (UDP) internet connection (QUIC) multicast protocol;

And carrying out protocol conversion on the multicast stream to obtain a unicast stream based on a QUIC unicast protocol, and sending the unicast stream to a client.

2. The method of claim 1, wherein the sending the first service request to the multicast server comprises:

and receiving a second service request sent by the client, and sending the first service request to the multicast server under the triggering of the second service request.

3. Method according to claim 2, wherein said second service request is a service request based on the QUIC unicast protocol, said sending said first service request to said multicast server under the triggering of said second service request comprising:

and carrying out protocol conversion processing on the second service request to obtain the first service request based on a QUIC multicast protocol, and sending the first service request to the multicast server.

4. The method of claim 2, wherein the first service request carries authentication information in the second service request, the authentication information being used by the multicast server to feed back the service response to the multicast gateway after authenticating the multicast gateway based on the authentication information.

5. The method of claim 4, wherein the authentication information comprises a correspondence between the address of the client and the address of the multicast gateway after encryption.

6. The method of claim 4, wherein the first service request carries token information in the second service request, the token information being used by the multicast server to determine the address of the client based on the token information.

7. The method of claim 6, wherein the authentication information and the token information are issued to the client by a multicast dispatch server.

8. The method according to claim 1, wherein the method further comprises:

and receiving control information from the multicast server, and executing a multicast command flow according to the control information.

9. The method according to claim 1, wherein the method further comprises:

and sending a third service request to the multicast server, and exiting the target multicast group according to the service response of the multicast server to the third service request.

10. The method of claim 9, wherein the sending the third service request to the multicast server comprises:

And receiving a fourth service request sent by the client, and sending the third service request to the multicast server under the triggering of the fourth service request.

11. Method according to claim 10, wherein said fourth service request is a service request based on the QUIC unicast protocol, said sending said third service request to said multicast server under the triggering of said fourth service request comprising:

and carrying out protocol conversion processing on the fourth service request to obtain the third service request based on a QUIC multicast protocol, and sending the third service request to the multicast server.

12. A data stream transmission method, for use in a multicast scheduling server, the method comprising:

receiving a configuration request sent by a client based on a QUIC unicast protocol;

returning an address of the multicast gateway according to the configuration request;

the address of the multicast gateway is used for the client to send a second service request to the multicast gateway, so that the multicast gateway sends a first service request to a multicast server under the triggering of the second service request.

13. The method of claim 12, wherein the configuration request comprises a first configuration request, the method further comprising:

And generating token information according to the first configuration request and sending the token information to the client, wherein the token information is used for the multicast server to determine the address of the client based on the token information.

14. The method of claim 12, wherein the configuration request comprises a second configuration request, the method further comprising:

and generating authentication information according to the second configuration request and sending the authentication information to the client, wherein the authentication information is used for enabling the multicast server to feed back service response to the multicast gateway after the multicast gateway is authenticated based on the authentication information.

15. The method according to claim 12, wherein the method further comprises:

and configuring the address of the multicast gateway, configuring the corresponding relation between the address of the client and the address of the multicast gateway, and generating a corresponding relation table of the address of the client and the address of the multicast gateway.

16. The method according to claim 12, wherein the method further comprises:

sending a monitoring request to the multicast gateway;

receiving monitoring data sent by the multicast gateway based on the monitoring request;

And determining the health state of the multicast gateway according to the monitoring data.

17. A data streaming apparatus, disposed in a multicast gateway, the apparatus comprising:

the first sending module is used for sending a first service request to the multicast server;

the first receiving module is used for joining a target multicast group according to the service response of the multicast server to the first service request, and receiving a multicast stream sent by the multicast server based on the target multicast group, wherein the multicast stream is a data stream based on a QUIC multicast protocol;

and the second sending module is used for carrying out protocol conversion on the multicast stream to obtain a unicast stream based on a QUIC unicast protocol, and sending the unicast stream to the client.

18. A data streaming apparatus, disposed in a multicast scheduling server, the apparatus comprising:

the second receiving module is used for receiving a configuration request sent by the client based on the QUIC unicast protocol;

a third sending module, configured to return an address of the multicast gateway according to the configuration request;

the address of the multicast gateway is used for the client to send a second service request to the multicast gateway, so that the multicast gateway sends a first service request to a multicast server under the triggering of the second service request.

19. A data stream transmission system, characterized in that the system comprises a multicast gateway, a multicast scheduling server, a multicast server and a client;

the multicast gateway for performing the steps performed by the multicast gateway of any of claims 1 to 16;

the multicast scheduling server for performing the steps performed by the multicast scheduling server of any one of claims 1 to 16;

the multicast server for performing the steps performed by the multicast server of any of claims 1 to 16;

the client being adapted to perform the steps performed by the client of any of claims 1 to 16.

20. A computer device comprising a memory and a processor, the memory storing a computer program, characterized in that the processor implements the steps of the method of any one of claims 1 to 11 or 12 to 16 when the computer program is executed.

21. A computer readable storage medium, on which a computer program is stored, characterized in that the computer program, when being executed by a processor, implements the steps of the method of any of claims 1 to 11 or 12 to 16.

22. A computer program product comprising a computer program, characterized in that the computer program, when executed by a processor, implements the steps of the method of any one of claims 1 to 11 or 12 to 16.