Methods and devices for configuring a DNS module and for address resolution in order to manage the streaming of media content in a telecommunications network

Abstract

The invention relates to a configuration method that allows the configuration of a DNS module (DNS_OTT, DNS_HGW) implemented by an entity (OTT, LB) formed by a gateway (LB) that is configured to interconnect a local area network with an operator network (NET) or by a device (OTT) of this local area network, the configuration comprising at least: (i) registering a domain name (MC_GW.fr) which directs to a multicast gateway (MC_GW) that is included in the entity (OTT, LB) and is configured to respond to a content access request received over the local area network by unicasting this content, the content being received (4E82) by the multicast gateway (MC_GW) via multicasting from a multicast server for this content (MC_SRV) via the operator network (NET); (ii) a rule for resolving a domain name (CP.COM) of at least one content server with the IP address (@IP_RDV) of a switching module (RDV) located in the operator network (NET); (iii) registering a secondary domain name (CPBIS.COM) which directs to the content server (CP.COM); the switching module (RDV) being configured so as, upon receiving (E40) a request to access content: - to respond (E60) with a redirect request to the domain name (MC_GW.fr) which directs to the multicast gateway if the content is to be accessed via multicasting; and - to respond (E110) with a redirect request to the secondary domain name (CPBIS.COM) which directs to the server for the content (CP.COM) if the content is to be accessed via unicasting.

Description

[0001] Description

[0002] Title: Methods and devices for configuring a DNS module and for resolving addresses for broadcasting multimedia content streams in a telecommunications network

[0003] Background of the invention

[0004] The present invention relates to the management of the distribution of multimedia content streams in a telecommunications network. It applies in particular to the distribution of audiovisual content from an OTT (Over the Top) service. This content is offered using a simple Internet connection and delivered in unicast streaming to a receiver (OTT decoder) via the Web.

[0005] In a unicast broadcast mode, a transmitting device (streaming server) generally belonging to a CDN (Content Delivery Network)) transmits a stream per client / receiving device (OTT decoder) having requested the content (client / server mode). Consequently, if several clients access the same content simultaneously, for example the Live (direct) of a TV channel, several identical streams circulate in the network. This method has the disadvantage of occupying a significant bandwidth of the network in the event of significant simultaneous requests for a linear (direct) service.

[0006] This unicast transmission is usually carried out with contents prepared in ABR (Adaptive Bit Rate) or adaptive bit rate in which the source content is encoded according to several bit rates, each segmented into small parts of several seconds, typically between two and ten seconds, the segments of the available streams and their respective bit rates being filled in a file downloadable by the clients (OTT decoders). When a client starts to receive a stream, it generally requests the segments of the stream with the lowest bit rate and if it determines that the network bit rate is higher than the bit rate of the downloaded segment, it requests a higher bit rate segment. On the contrary, if a client notices that the network bit rate has deteriorated, it can request a lower bit rate segment. Each client implements an adaptive bit rate algorithm to decide which bit rate segments to download, depending on the current network status.

[0007] Historically, Linear streaming used point-to-multipoint transmission methods such as Broadcast (cable, satellite, etc.) or Multicast (IPTV, etc.), these methods consisting of transmitting a single stream to a plurality of receivers. These methods save bandwidth since in the network, a single stream circulates for all receivers. On the other hand, these methods required the use of receivers dedicated to the transmission mode (Satellite Receiver, IPTV decoder, etc.) and to the characteristics of the transmission network (association of TV channel and broadcast frequency or multicast address, etc.), which is not compatible with OTT decoders. Since 2020, new standards have appeared such as M-ABR (example: DVB ETSI TS 103 769 VI.1.1, a standard inspired by earlier 3GGP and ATSC work) combining existing media encoding and packaging formats (ABR) with the efficiency of point-to-multipoint distribution to the edge of IP-based access networks. It becomes possible to design a linear media distribution system that is both efficient and scalable to very large audiences, while remaining technically compatible with the largest possible set of already deployed end-user equipment (OTT set-top boxes). Point-to-multipoint topologies also offer opportunities for efficient pre-positioning of assets on devices at the network edge. This supports additional non-linear use cases and can help mitigate peak demand on the access network at synchronization points in the linear schedule.

[0008] The invention relates in particular to a mechanism for directing requests for access to content sent by the client (OTT decoder). In the DVB standard (DVB ETSI TS 103 769 VI.1.1), the device in charge of such a switching device is called a rendezvous service. It allows a request for access to content to be redirected either to a unicast CDN server (the classic mode), or to a "multicast gateway". The multicast gateway receives the content via a multicast transport (see broadcast) and delivers it to the client in unicast.

[0009] Figure 1 represents a first method for managing the broadcasting of multimedia streams in unicast to an OTT receiver, this method being in accordance with the state of the art.

[0010] An OTT receiver device (OTT end device) includes a CP_APP application from a content provider (Content Provider Application), a multimedia stream decoder and a DNS module (Domain Name Server) referenced DNSJDTT.

[0011] This OTT receiver device is connected via a LAN to a Home Gateway (HGW). This Home Gateway (HGW) includes a DNS module, referenced DNS_HGW.

[0012] The HGW home gateway is connected to a NET telecommunications network with a DNS_NET DNS server.

[0013] A Content Provider server (CP server) CP_SRV of a Content Delivery Network (CDN) is connected to the NET network. We note "CP.net" as the domain name (FQDN, in English Fully Qualified Domain Name) and "@IP_CDN" as the IP address of the content server CP_SRV.

[0014] In this document, domain names are actually fully qualified domain names; the term domain name is used for simplicity.

[0015] When the user of the OTT receiving device wants to access the content delivered by the content server CP_SRV, the OTT device sends (step 1E10) a “RESOLVE CP.net” request to resolve the FQDN domain name of this server.

[0016] This query is received by the DNSJDTT DNS module of the OTT receiving device and if this module cannot resolve the query (i.e. if it has never processed a similar query or if the response it holds has become obsolete), it forwards the query to the next DNS module for resolution, i.e. to the DNS_HGW of the HGW home gateway. On this same principle, if this DNS_HGW module cannot resolve the query, it forwards it to the next DNS server, i.e. in this example to the DNS_NET DNS server of the network.

[0017] The DNS_NET DNS server of the network returns (step 1E20) the IP address @IP_CDN of the CP content delivery to the DNS module that queried it, i.e. to the DNS module DNS_HGW, and this is repeated up to the OTT receiver device.

[0018] The OTT receiver device sends (step 1E30) a “GET CP.net / content” request to the IP address @IP_CDN to obtain (step 1E40) the content from the content server CP_SRV in unicast mode.

[0019] Figure 2 represents a second method for managing the broadcasting of multimedia streams in accordance with the state of the art and illustrates in particular three additional functional modules making it possible to deliver to the OTT receiver device an ABR M-ABR multicast content (for example in accordance with the DVB reference architecture ETSI TS 103 769 VI.1.1).

[0020] A "Multicast server" module (MC_SRV), or "multicast server", retrieves the content to be transmitted from the content distribution server CP_SRV (step 2E70) and broadcasts it in point-to-multipoint mode (step 2E80). In accordance with the M-ABR protocol, the broadcast mode is carried out in multicast.

[0021] A "Rendez Vous Service" (RDV) module has knowledge of the content broadcast in M-ABR. The CP_APP application of the PTT receiving device addresses the RDV module to obtain content from the CP_SRV content server (step 2E90).

[0022] In a particular “REDIRECT” embodiment described here, the RDV service appointment module responds to the CP_APP application (steps 2E101 and 2E102) to directly fetch the desired content in unicast on the Multicast Gateway (steps 2E112 and 2E122) or on the CP_SRV server (steps 2E111 and 2E121).

[0023] A multicast gateway (MC_GW module) is responsible for retrieving the requested content (step 2E112) broadcast in multicast (in the case of M-ABR). To this end, the MC_GW multicast gateway subscribes to the corresponding multicast stream (step 2E80) and transmits it to the CP_APP application in step 2E122.

[0024] Figure 3 represents a method for managing the broadcasting of multimedia streams in M-ABR mode in accordance with the state of the art in which:

[0025] - the MC_SRV multicast server and the RDV service appointment module are located in the operator's NET network; and

[0026] - the MC_GW multicast gateway is integrated into the HGW home gateway.

[0027] As is known, the multicast server MC_SRV uses point-to-multipoint broadcast resources (step 3E02) made available by the network operator (in the context of M-ABR, these resources are multicast IP addresses) and retrieves the content to be broadcast in M-ABR (step 3E01) at the content server CP_SRV. The RDV service appointment module must also have knowledge of the content broadcast in M-ABR and the multicast broadcast gateway MC_GW knows the association between the content(s) broadcast in M-ABR and the point-to-multipoint broadcast resource(s) used, made at the multicast server MC_SRV.

[0028] In this example, when activating the RDV module in the network, the network operator declares two new rules (step 3E03) in the network DNS (DNS_NET):

[0029] - the first rule (CP.net=>@IP_RDV) redefines the resolution of the main FQDN “CP.net” either by the IP address @IP_RDV of the RDV module (replacing the IP address of the content delivery server CP_SRV). As a variant not shown here, the main FQDN “CP.net” can be resolved by a new FQDN “RDV.net” which is resolved by the IP address of the RDV module;

[0030] - the second rule (CPBIS.net=>@IP_CDN) defines a secondary FQDN “CPBIS.net” resolved by the IP address @IP_CDN of the content server CP_SRV.

[0031] Furthermore, at the HGW home gateway, when activating the MC_GW multicast gateway, a new DNS rule (MC_GW.Ian => @IP_MC_GW) is inserted (step 3E05) ​​in the DNS_HGW DNS of the HGW home gateway resolving the URL “MC_GW.Ian” by the IP address @IP_MC_GW of the multicast gateway.

[0032] During a step 3E04, the multicast broadcast gateway MC_GW registers in a database at the service appointment module RDV. Thus, when a device requests the service appointment module RDV via this home gateway HGW, the service appointment module RDV knows whether a multicast broadcast gateway MC_GW is present for this device.

[0033] In the example of Figure 3, when the CP_APP application of the OTT receiving device resolves the domain name “CP.net”, it obtains the IP address @IP_RDV of the RDV service appointment module (steps 3E10, 3E20), so its content request (step 3E30) is redirected to the RDV module.

[0034] The RDV service appointment module performs a routing function. Indeed, the response to the content request is a request to redirect the query to the FQDN "MC_GW.Ian" (step 3E42) if, on the one hand, the MC_GW multicast gateway has been registered on the RDV service appointment module and if, on the other hand, the content is broadcast in M-ABR mode. This response, once resolved (steps 3E52 and 3E62), allows the OTT receiver device to obtain the content from the MC_GW multicast gateway (steps 3E72, 3E82 and 3E92).

[0035] On the contrary, if the multicast gateway MC_GW has not been registered in the database, or if the requested content is not broadcast in M-ABR mode; the response to the content request (3E30) is a redirection request to the secondary FQDN "CPBIS.net" which once resolved (steps 3E51 and 3E61) will allow obtaining the content from the content server CP_SRV (steps 3E71 and 3E81).

[0036] It is important to note that this broadcasting method has a major drawback in that it requires declaring (in step 3E04) the multicast broadcast gateway MC_GW to the rendezvous service module RDV. Indeed, assuming that this registration is not carried out, and therefore that the rendezvous service module systematically returns, in step 3E42, as soon as the requested content is accessible in multicast, a redirection instruction to a domain name associated with a multicast broadcast gateway, even in the absence of such a gateway MC-GW, then step 3E52 of resolving this domain name would result in a service interruption, typically an HTTP code 404 error. To avoid such an inconvenience, a known solution consists of managing such a response at the level of the CP_APP application of the OTT decoder to redirect the request to the server of this content CP_SRV for unicast reception.

[0037] This solution is not satisfactory because it requires a modification of the software of OTT receivers.

[0038] The invention aims at a diffusion method which does not have these drawbacks.

[0039] Subject matter and summary of the invention

[0040] Thus, and according to a first aspect, the invention relates to a method for configuring a DNS module implemented by a home gateway configured to interconnect a local network with an operator network, said configuration comprising at least:

[0041] (i) a registration of a domain name pointing to a multicast gateway included in said home gateway and configured to respond to a request for access to content received on the local network, by sending this content in unicast, said content being received in multicast by the multicast gateway from a multicast server of this content via the operator's network;

[0042] (ii) a rule for resolving a domain name of at least one content server with the address of a routing module located in the operator's network, said routing module being configured to, upon receipt of a request for access to content:

[0043] - respond with a redirection request to said domain name pointing to said multicast gateway if the content is to be accessed in multicast; and

[0044] - respond with a redirection request to a secondary domain name that can be resolved to the address of the server of said content if the content is to be accessed in unicast.

[0045] Correlatively, the invention relates to a device for configuring a DNS module included in a home gateway configured to interconnect a local network with an operator network, said configuration comprising at least:

[0046] (i) a registration of a domain name pointing to a multicast gateway included in said home gateway and configured to respond to a request for access to content received on the local network, by sending this content in unicast, said content being received in multicast by the multicast gateway from a multicast server of this content via the operator's network;

[0047] (ii) a rule for resolving a domain name of at least one content server with the IP address of a routing module located in the operator's network, said routing module being configured to, upon receipt of a request for access to content:

[0048] - respond with a redirection request to the domain name pointing to said multicast gateway if the content is to be accessed in multicast; and

[0049] - respond with a redirection request to a secondary domain name that can be resolved to the address of said content server if the content is to be accessed in unicast.

[0050] The method of configuring a DNS module according to the invention is remarkable in that it makes it possible to intelligently direct the unicast or multicast stream to the OTT receiver according to the broadcast mode of this stream, without requiring prior registration or declaration of the multicast broadcast gateway to the service rendezvous module, nor modification of the OTT receiver software.

[0051] The invention also relates to an address resolution device configured by the configuration method mentioned above and an address resolution method implemented by such a device.

[0052] Thus, according to a second aspect, the invention relates to an address resolution method implemented by an entity constituted by a home gateway configured to interconnect a local network with an operator network, this method comprising:

[0053] - a step of receiving a domain name resolution request from a content server

[0054] - a step of responding to said resolution request by sending the IP address of a switching module located in the operator's network, said switching module being configured to, upon receipt of a request for access to content:

[0055] - respond with a redirection request to a domain name of a multicast gateway included in said home gateway if the content is to be accessed in multicast; and

[0056] - respond with a redirection request to a secondary domain name that can be resolved to the address of a server of said content if the content is to be accessed in unicast.

[0057] Correlatively, the invention relates to an address resolution device intended to be integrated into a home gateway configured to interconnect a local network with an operator network, this device comprising:

[0058] - a module for receiving a request to resolve a domain name from a content server; and

[0059] - a module for sending a response to said resolution request, said response comprising the IP address of a switching module located in the operator's network, said switching module being configured to, upon receipt of a request for access to content:

[0060] - respond with a redirection request to the domain name of a multicast gateway included in said home gateway if the content is to be accessed in multicast; and

[0061] - respond with a redirection request to a secondary domain name that can be resolved into the address of a server of said content if the content is to be accessed in unicast. The invention also relates to a home gateway configured to interconnect a local network with an operator network, this gateway being characterized in that it comprises a configuration device as mentioned above.

[0062] The invention also relates to a multicast gateway integrated into a home gateway as mentioned above and configured to respond to a request for access to content by sending this content in unicast, this content being received by said multicast gateway in multicast from a multicast broadcast server of this content, said multicast gateway comprising a configuration device as mentioned above.

[0063] In one embodiment of the invention, the configuration method is implemented upon detection of the presence of the multicast gateway. In this embodiment, as soon as the home gateway detects the presence of the broadcast gateway, it configures its DNS with the two rules (i) and (ii) mentioned above.

[0064] In one embodiment, the configuration method is implemented by the multicast gateway, preferably upon its startup. In this embodiment, it is the multicast gateway which itself configures the DNS of the home gateway with the two rules (i) and (ii) mentioned above.

[0065] In a particular embodiment, the different steps of the configuration method and / or the address resolution method are determined by computer program instructions or are implemented by a silicon chip which comprises transistors adapted to constitute logic gates of non-programmable hard-wired logic.

[0066] Consequently, the invention also relates to a computer program on an information medium, this program being capable of being implemented in a controller computer, this program comprising instructions adapted to the implementation of the steps of a configuration and / or address resolution method as described above.

[0067] This program may use any programming language, and may be in the form of source code, object code, or code intermediate between source code and object code, such as in a partially compiled form, or in any other desirable form.

[0068] The invention also relates to a computer-readable information medium, and comprising instructions of a computer program as mentioned above. The information medium may be any entity or device capable of storing the program. For example, the medium may comprise a storage means, such as a ROM, a non-volatile memory of the flash type or even a magnetic recording means, for example a hard disk. Furthermore, the information medium may be a transmissible medium such as an electrical or optical signal, which may be conveyed via an electrical or optical cable, by radio or by other means. The program according to the invention may in particular be downloaded from a network such as the Internet. Alternatively, the information medium may be an integrated circuit in which the program is incorporated, the circuit being adapted to execute or to be used in the execution of the method in question.Brief description of the drawings:.

[0069] Other characteristics and advantages of the present invention will emerge from the description given below, with reference to the appended drawings which illustrate exemplary embodiments thereof which are not in any limiting nature. In the figures:

[0070] - figure 1, already described, represents a method for managing the broadcasting of multimedia streams in unicast conforming to the state of the art;

[0071] - figure 2, already described, represents another method for managing the broadcasting of multimedia streams in accordance with the state of the art;

[0072] - figure 3, already described, represents another method for managing the broadcasting of multimedia streams in accordance with the state of the art;

[0073] - Figure 4 represents a configuration method and an address resolution method according to a particular embodiment of the invention;

[0074] - figure 5 represents a configuration device in accordance with a particular embodiment of the invention;

[0075] - Figure 6 represents an address resolution device according to a particular embodiment of the invention; and

[0076] - Figure 7 represents a home gateway, and a multicast gateway according to a particular embodiment of the invention.

[0077] Detailed description

[0078] Figure 4 represents a method of configuring a DNS module and a method of resolving an address in accordance with a particular embodiment of the invention.

[0079] In this embodiment, the configuration method and the address resolution method are implemented by a home gateway HGW realizing the interconnection between a local area network LAN and an operator network NET.

[0080] In this embodiment, the home gateway HGW comprises a DNS module DNS_HGW and a multicast gateway MC_GW.

[0081] Figure 4 shows a content server CP_SRV of a content delivery network CDN connected to the NET network. We denote respectively "CP.net", the FQDN domain name and "@IP_CDN", the IP address of the content server CP_SRV.

[0082] Figure 4 shows an OTT receiver device comprising a CP_APP application from a content provider, a decoder (not shown) and a DNSJDTT DNS module.

[0083] A multicast server MC_SRV of the operator's network NET uses point-to-multipoint broadcast resources (step 4E02) and retrieves the contents to be broadcast in M-ABR mode (step 4E01) at the content server CP_SRV.

[0084] An RDV routing module providing a service appointment function is installed in the operator's NET network. In the embodiment described here, during a step 4E03, when activating the RDV routing module in the network, the network operator declares a new rule in the network DNS DNS_NET (CPBIS.net=>@IP_CDN) which defines a secondary FQDN "CPBIS.net" resolved by the IP address @IP_CDN of the content server CP_SRV.

[0085] During a step 4E04, a CTR controller of the home gateway HGW detects the presence of the multicast gateway MC_GW.

[0086] During this same step 4E04, the CTR controller configures the DNS_HGW DNS module of the home gateway. More precisely: it registers a domain name MC_GW.Ian pointing to the multicast gateway MC_GW. Since the multicast gateway MC_GW is included in the home gateway HGW, the multicast gateway MC_GW and the home gateway HGW have the same IP address, which is the IP address @IP_MC_GW; it registers a rule (CP.net=>@IP_RDV) that redefines the resolution of the primary FQDN

[0087] “CP.net” of the content server CP_SRV by the IP address @IP_RDV of an RDV routing module located in the operator's network.

[0088] In a step 4E10, the OTT receiving device sends a RESOLVE CP.net request to resolve the primary domain name of the content server CP_SRV.

[0089] This query is received by the DNSJDTT DNS module of the OTT receiver device and forwarded to the DNSJHGW DNS module of the home gateway.

[0090] The DNS module DNS_HGW of the home gateway responds (step 4E20) to the OTT receiver device that the IP address of the content server CP_SRV is the IP address @IP_RDV of the RDV switching module.

[0091] The OTT receiving device sends (step 4E30) a request to access a GET CP.net / content content to the IP address @IP_RDV of the RDV switching module.

[0092] During a step 4E50, the RDV routing module determines whether the URL associated with the content is, in a configuration file, associated with an ABR multicast broadcast mode.

[0093] If this is the case, the RDV switching module sends (step 4E42) to the OTT receiving device a REDIRECT MC_GW.Ian / content redirection request so that it sends its content access request to the MC_GW multicast gateway.

[0094] During a step 4E52, the OTT receiver device sends a “RESOLVE MC_GW.Ian” request to resolve the FQDN domain name of the MC_GW multicast gateway.

[0095] This query is received by the DNSJDTT DNS module of the OTT receiver device and forwarded to the DNS_HGW DNS module of the HGW home gateway.

[0096] The HGW home gateway returns (step 4E62) to the OTT receiver device the IP address @IP_MC_GW of the MC_GW multicast gateway. This is also the IP address of the HGW home gateway. The OTT receiver device sends (step 4E72) the "GET MC_GW.Ian / content" request to access the content to the IP address of the MC_GW multicast gateway.

[0097] This MC_GW multicast gateway ensures the conversion, into unicast for playback by the OTT receiver device, of the stream received in multicast from the MC_SRV multicast broadcast server.

[0098] The multicast gateway MC_GW sends (step 4E92) in unicast to the decoder DEC, the content received (4E82) in multicast from the multicast broadcast server MC_SRV.

[0099] If, during step 4E50, the RDV routing module determines that the URL associated with the content is not associated with an ABR multicast broadcast mode, the RDV routing module sends (step 4E41) to the OTT receiver device a redirection request REDIRECT CPBIS.net / content to the secondary FQDN of the content server CP_SRV.

[0100] During a step 4E51, the OTT receiver device sends a “RESOLVE CPBIS.net” request to resolve the secondary FQDN domain name of the unicast content server CP_SRV.

[0101] This query is received by the DNSJDTT DNS module of the OTT receiver device and forwarded to the DNSJHGW DNS module of the HGW home gateway, which forwards it to the operator's DNS_NET DNS module.

[0102] The operator's DNS_NET module returns (step 4E61) to the OTT receiver device the IP address @IP_CDN of the unicast content server CP_SRV.

[0103] The OTT receiver device sends (step 4E71) the “GET CPBIS.net / content” request to access the content to the IP address IP_CDN of the unicast content server CP_SRV.

[0104] The unicast content server CP_SRV sends the content to the OTT receiver device during a step 4E81.

[0105] Figure 5 represents a DC device for configuring a module according to the invention. This device is intended to be integrated into a home gateway HGW between a local network and a NET operator network, the home gateway HGW comprising a multicast gateway MC_GW.

[0106] In the embodiment described here, the DC configuration device has the hardware architecture of a computer II comprising a processor 10, a ROM type read-only memory 11, a random access memory 12, a rewritable non-volatile memory 14 and communication means 15.

[0107] The ROM type read-only memory 11 constitutes a recording medium within the meaning of the invention. It comprises a computer program PGC comprising instructions for executing the steps of a configuration method according to the invention when this program is executed by the processor 10.

[0108] In particular, the communication means 15 are configured to configure a DNS module DNS_HGW with configuration rules comprising at least:

[0109] (i) a record of a domain name MC_GW.fr pointing to the multicast gateway MC_GW; (ii) a resolution rule of a domain name CP.net of at least one content server CP_SRV with the IP address @IP_RDV of an RDV routing module located in the network of the operator NET,

[0110] Figure 6 shows an address resolution device DR according to the invention. This device is intended to be integrated into a domestic gateway HGW between a local network and a NET operator network.

[0111] In the embodiment described here, the address resolution device DR has the hardware architecture of a computer II comprising a processor 20, a ROM type read-only memory 21, a random access memory 22, a rewritable non-volatile memory 24 and communication means 25.

[0112] The ROM type read-only memory 21 constitutes a recording medium within the meaning of the invention. It comprises a computer program PGR comprising instructions for executing the steps of an address resolution method according to the invention when this program is executed by the processor 20.

[0113] The communication means 25 are in particular configured to receive a request for resolution of a domain name from a content server and to send, in response to this resolution request, a response comprising the IP address of an RDV routing module located in the operator's network, this RDV routing module being configured to, upon receipt of a request for access to content:

[0114] - respond with a redirection request to a domain name of a multicast gateway included in the home gateway if the content is to be accessed in multicast; and

[0115] - respond with a redirect request to a secondary domain name that can be resolved to the address of a content server if the content is to be accessed in unicast.

[0116] Figure 7 shows a home gateway HGW and a multicast gateway MC_GW according to the invention.

[0117] The HGW home gateway comprises a DNS module DNS-HGW, a configuration DC device and an address resolution DR device according to the invention.

[0118] In one embodiment, the DC configuration device is integrated into the multicast gateway MC_GW. The multicast gateway is then in accordance with the invention.

[0119] In another embodiment, the DC device for configuring the home gateway HGW is not integrated into the multicast gateway MC_GW.

[0120] In one embodiment, the address resolution device DR is integrated with the DNS module DNSJHGW.

Claims

CLAIMS

1. Method for configuring a DNS module (DNSJHGW) implemented by a home gateway (HGW) configured to interconnect a local area network (LAN) with an operator network (NET), said configuration comprising at least: (i) a record of a domain name (MC_GW.Ian) pointing to a multicast gateway (MC_GW) included in said home gateway (HGW) and configured to respond to a request for access to content received on the local network, by sending this content in unicast, said content being received (4E82) in multicast by the multicast gateway (MC_GW) from a multicast server of this content (MC_SRV) via the operator network (NET); (ii) a rule for resolving a domain name (CP.net) of at least one content server (CP_SRV) with the IP address (@IP_RDV) of a routing module (RDV) located in the operator's network (NET), said routing module (RDV) being configured to, upon receipt (4E30) of a request for access to content: - respond (4E42) with a redirection request to said domain name (MC_GW.Ian) pointing to said multicast gateway (MC_GW) if the content is to be accessed in multicast; and - respond (4E41) with a redirection request to a secondary domain name (CPBIS.net) that can be resolved to the address (@IP_CDN) of said content server (CP_SRV) if the content is to be accessed in unicast.

2. Configuration method according to claim 1, said method being implemented upon detection (4E04) of the presence of the multicast gateway (MC_GW).

3. A configuration method according to claim 1, said method being implemented by the multicast gateway (MC_GW).

4. Address resolution method implemented by a home gateway (HGW) configured to interconnect a local network with an operator network (NET), this method comprising: - a step (4E20) of receiving a request for resolution of a domain name (CP.net) from a content server (CP_SRV); - a step (4E20) of responding to said resolution request by sending the IP address (@IP_RDV) of a switching module (RDV) located in the operator's network (NET), said switching module (RDV) being configured to, upon receipt (4E30) of a request for access to content: - respond (4E42) with a redirection request to a domain name (MC_GW.Ian) of a multicast gateway (MC_GW) included in said home gateway (HGW) if the content is to be accessed in multicast; and - respond (4E41) with a redirection request to a secondary domain name (CPBIS.net) that can be resolved to the address (@IP_CDN) of a server (CP_SRV) of said content if the content is to be accessed in unicast.

5. Device (DC) for configuring a DNS module (DNS_HGW) included in a home gateway (HGW) configured to interconnect a local area network (LAN) with an operator network (NET), said configuration comprising at least: (i) a registration of a domain name (MC_GW.fr) pointing to a multicast gateway (MC_GW) included in said home gateway (HGW) and configured to respond to a request for access to content received on the local network, by sending (4E92) this content in unicast, said content being received (4E82) in multicast by the multicast gateway (MC_GW) from a broadcast server (MC_SRV) of this content via the operator network (NET); (ii) a rule for resolving a domain name (CP.net) of at least one content server (CP_SRV) with the IP address (@IP_RDV) of a routing module (RDV) located in the operator's network (NET), said routing module (RDV) being configured to, upon receipt (4E30) of a request for access to content,: - respond (4E42) with a redirection request to the domain name (MC_GW.Ian) pointing to said multicast gateway (MC_GW) if the content is to be accessed in multicast; and - respond (E110) with a redirection request to a secondary domain name (CPBIS.net) that can be resolved to the address (@IP_CDN) of said content server (CP_SRV) if the content must be accessed in unicast.

6. Home gateway (HGW) configured to interconnect a local area network (LAN) with an operator network (NET), said home gateway (HGW) being characterized in that it comprises a configuration device (DC) according to claim 5.

7. Multicast gateway (MC_GW) integrated into a home gateway according to claim 6 and configured to respond to a request for access to content by sending (4E92) in unicast of this content, this content being received (4E82) by said multicast gateway (MC_GW) in multicast from a multicast broadcast server (MC_SRV) of this content, said multicast gateway (MC_GW) being characterized in that it comprises a configuration device (DC) according to claim 5.

8. Address resolution device (DR) intended to be integrated into a home gateway (HGW) configured to interconnect a local network with an operator network (NET), this device comprising: - a module (25) for receiving a request for resolving a domain name (CP.net) from a content server (CP_SRV); and - a module (25) for sending a response to said resolution request, said response comprising the IP address (@IP_RDV) of a switching module (RDV) located in the operator's network (NET), said switching module (RDV) being configured to, upon receipt (4E30) of a request for access to content: - respond (4E42) with a redirection request to a domain name (MC_GW.Ian) of a multicast gateway (MC_GW) included in said home gateway (HGW) if the content is to be accessed in multicast; and - respond (4E41) with a redirection request to a secondary domain name (CPBIS.net) that can be resolved to the address (@IP_CDN) of a server (CP_SRV) of said content if the content is to be accessed in unicast.

9. Computer program (CPG) comprising instructions for executing the steps of the configuration method according to any one of claims 1 to 3 when said program is executed by a computer.

10. A computer program (PGR) comprising instructions for performing the steps of the address resolution method according to claim 4 when said program is executed by a computer.

Images