Method and system for multicast broadcasting towards a roaming terminal according to the location thereof

0001The invention relates to a method and a system of multicast broadcasting to a roaming terminal according to the location of the IP network connection of the latter, and the corresponding software product or products.

0002Currently, businesses or industrial or commercial companies use, as a quasi-necessity, the interchange of data and information supported by this data, via the IP network.

0003More widely, these businesses or companies are multi-establishment organizations, with one or more establishments normally being associated with at least one computer site, or web site, these sites being interlinked via an IP network. These businesses or companies are therefore also multisite entities, forming one and the same original organization.

0004As a general rule, the IP multicast information broadcasting method is used for broadcasting information to each of the abovementioned sites.

0005There are in fact three types of multicast broadcast defined in the RFC 2365 standard (administratively scoped IP multicast): <ul id="ul0001" list-style="none"><li id="ul0001-0001" num="0000"><ul id="ul0002" list-style="none"><li id="ul0002-0001" num="0006"> broadcasts private to the site, also designated broadcasts local to the site, performed only to terminals affiliated to and managed by the original site, via an original home network, these local broadcasts never being transmitted from one site to another even though the latter are affiliated to the same original organization; </li><li id="ul0002-0002" num="0007"> broadcasts private to the original organization, typically the business, also called broadcasts local to the organization, performed only to terminals affiliated to the original organization, these broadcasts local to the organization never being transmitted to an organization external to the original organization; </li><li id="ul0002-0003" num="0008"> global broadcasts, these broadcasts being able to be broadcast to all the INTERNET and therefore accessible from any local IP network or access point connected to the latter. </li></ul></li></ul>

0009A review of the multicast broadcasting technique will first of all be given in conjunction with <figref idref="DRAWINGS">FIGS. 1</figref><i>a </i>and <b>1</b><i>b. </i>

0010In the case of the multicast broadcasting technique, with reference to <figref idref="DRAWINGS">FIGS. 1</figref><i>a </i>and <b>1</b><i>b</i>, a receiver, R₆, wishing to have access or subscribe to a multicast broadcast sends an access request to its access router RO₆, according to the IGMP method (RFC 2236). The access router RO₆uses a multicast routing protocol, the PIM-SM method (RFC 2117) for example, to relay this request to the point of the network (switching point or router) that is already receiving this broadcast, where appropriate, directly to the access router RO₀of the broadcasting source, as represented in <figref idref="DRAWINGS">FIG. 1</figref><i>a</i>. The routing of the abovementioned request is represented by solid line arrows in <figref idref="DRAWINGS">FIG. 1</figref><i>a. </i>

0011Each router belonging on the route keeps in memory the software interface, routing data and addresses, via which it has received a request to subscribe to a predetermined broadcast. When the router concerned receives the IP data packets relating to this broadcast, it transmits them to its neighboring router by reverse path, using the stored software interface.

0012Thus, the IP data packets corresponding to this broadcast reach the requesting receiver R₆by reverse path. The reverse path is represented by broken line arrows in <figref idref="DRAWINGS">FIG. 1</figref><i>a. </i>

0013When a new receiver, the receiver R₁for example, as represented in <figref idref="DRAWINGS">FIG. 1</figref><i>a</i>, wants to access this same broadcast, it sends its access request to its access router RO₄. The latter transmits this request until it reaches a router executing the requested broadcast, in this case the router RO₂in <figref idref="DRAWINGS">FIG. 1</figref><i>a</i>. The path of this request is represented by mixed line arrows in <figref idref="DRAWINGS">FIG. 1</figref><i>a. </i>

0014The most forward router, in the direction of the broadcast, reached by this request, which is already receiving the data and information of the broadcast requested by the receiver R₁, stops returning this request to the broadcasting source, server SD, duplicates the IP data packets to transmit the latter also to the receiver R₁using the stored software interface, by reverse path. The path of the full broadcast is represented by broken line arrows in <figref idref="DRAWINGS">FIG. 1</figref><i>a</i>, the reverse path RO₂-RO₃-RO₄-R₁being represented by a double broken line arrow in <figref idref="DRAWINGS">FIG. 1</figref><i>a</i>, although belonging to the same multicast broadcast as that requested by the receiver R₆. The same applies for any receiver R₂to R₅likely to request this same broadcast.

0015Consequently, with the IP multicast broadcast technique, it will be understood that the server SD sends the data supporting the information that makes up the broadcast only once. This data is duplicated by the routers of the network dynamically, to reach the authorized receivers that have made the request. The set of paths or routes followed by the IP data packets of the broadcast, from the server SD to these authorized receivers, forms a multicast information broadcasting tree, the root of which is the broadcasting source, server SD or root router RO₀, the various routes forming the branches and the end receivers forming the leaves. It should be understood, in particular, that, following the access request from the receivers R₆and R₁, in the case of an access request from the receiver R₄, the branch RO₂-RO₉and the receiving leaf R₄are added whereas in the case of an access request from the receiver R₂, only the receiving leaf R₂is added.

0016As for the IP multicast addressing, the multicast broadcasting technique introduces the concept of multicast broadcast. An IP data packet that is part of a multicast broadcast has a destination IP address, called multicast address. All the data packets supporting information belonging to the same broadcast have the same destination multicast address. Whereas a unicast IP address can be used to identify just one receiving machine or workstation, a multicast IP address is used to identify a set or group of machines, the set of machines authorized to access this broadcast. A multicast address is therefore always a destination address and would be meaningless as a source address. To this end, a part of the IP address codes is reserved for assigning multicast addresses.

0017Specifically, the standard RFC 2365 (Administratively Scoped IP Multicast) defines a way of assigning certain multicast addresses an administrative limit to the broadcast that these addresses represent.

0018Depending on the value of the multicast address assigned to a broadcast, this broadcast is consequently intended, as mentioned previously, to be limited: <ul id="ul0003" list-style="none"><li id="ul0003-0001" num="0000"><ul id="ul0004" list-style="none"><li id="ul0004-0001" num="0019"> to a site (site-local scope); </li><li id="ul0004-0002" num="0020"> to an organization (organization-local scope); </li><li id="ul0004-0003" num="0021"> to all the Internet (global scope). </li></ul></li></ul>

0022The possibilities offered by the abovementioned multicast broadcast concept for broadcasting data to the different sites of a business or multisite entity appear currently to be significantly limited.

0023If, with reference to <figref idref="DRAWINGS">FIG. 1</figref><i>b</i>, we consider a multisite entity located on four separate sites, site <b>1</b>, site <b>2</b>, site <b>3</b> and site <b>4</b>, site <b>1</b> including, for example, a multicast broadcast server SD, such a broadcast, according to a “site-local scope” mode, is local to site <b>1</b>. Consequently, the IP data packets supporting the information of this broadcast are not sent outside of the site. These data packets therefore do not cross the interconnecting network and cannot be received by the users of other sites, site <b>2</b>, site <b>3</b> and site <b>4</b>.

0024The abovementioned different broadcast types have a very significant impact on the access restrictions affecting any roaming terminal affiliated to an original organization, according to the location of the network, local IP network and/or INTERNET, to which the latter is connected.

0025Discriminating the location of the connection of any roaming terminal affiliated to an original organization, such as a multisite business, is therefore crucial, in order to implement a specific selective broadcasting method towards a roaming terminal, such a broadcast needing, in particular, to be totally selective, of the point-to-point broadcast type, when this roaming terminal is connected to a network outside its original organization, and, more often than not, when this same roaming terminal, although connected to a site affiliated to its original organization, is not connected to its original site.

0026These situations are represented in <figref idref="DRAWINGS">FIG. 1</figref><i>c</i>, for a roaming terminal T network-connected to its original site S₁, to sites S₂and S₃separate from the original site S₁but affiliated to the original organization O₀and to any site S_paffiliated to an organization O_pseparate from the original organization O₀, the terminal being denoted T₁, T₂, T₃and T_psuccessively.

0027In the abovementioned situations, this roaming terminal can be reached only by the global broadcasts, or the global broadcasts and broadcasts local to the original site.

0028In practice, some IP network services use the concept of hierarchy of the IP network architecture. These services can limit their network scope to a link, a site, an organization, or even extend this scope to all of the INTERNET.

0029In these conditions, it is essential for a terminal that is on the move to be able to determine if it is connected to its original home network, to another site affiliated to its original organization or to another site external to the latter.

0030The location of this connection is in fact likely to modify the recognized capabilities of this terminal that is on the move to access the services of the IP network for which the access is restricted by the original organization of the latter, such as its business.

0031At the present time, the techniques for locating the connection of a roaming terminal that is on the move do not allow for this terminal to be informed of its location, in particular the location of its network connection either on its original site, or on another site separate from its original site but affiliated to its original organization, or even to a site affiliated to an organization separate from its original organization, or directly to the INTERNET.

0032Among the solutions currently available for locating terminals connected to the IP network, only partial solutions have been proposed.

0033The abovementioned partial solutions mainly consist of neighbor terminal discovery and error management protocols, such as are defined by the IETF (The Internet Engineering Task Force), by the documents: <ul id="ul0005" list-style="none"><li id="ul0005-0001" num="0000"><ul id="ul0006" list-style="none"><li id="ul0006-0001" num="0034"> RFC 2461 (Neighbour Discovery for IP Version 6) for the IP protocol, version 6, IPv6; </li><li id="ul0006-0002" num="0035"> RFC 1256 (ICMP Router Discovery Messages) for the IP protocol, version 4, IPv4; <ul id="ul0007" list-style="none"><li id="ul0007-0001" num="0036"> by the dynamic IP address allocation protocols: </li></ul></li><li id="ul0006-0003" num="0037"> RFC 2131 (Dynamic Host Configuration Protocol) for the IPv4 protocol; </li><li id="ul0006-0004" num="0038"> RFC 3315 (Dynamic Host Configuration Protocol for IPv6, (DHCPv6)); <ul id="ul0008" list-style="none"><li id="ul0008-0001" num="0039"> by the documents specifying the IP addressing architectures used by the abovementioned protocols: </li></ul></li><li id="ul0006-0005" num="0040"> RFC 3513 (IPv6 Addressing Architecture) IPv6; </li><li id="ul0006-0006" num="0041"> RFC 2365 (Administratively Scoped IP Multicast, RFC 1918 (Address Allocation for Private Internets), RFC 3232 (Assigned Numbers: RFC 1700 is replaced by an Online Database) for IPv4; <ul id="ul0009" list-style="none"><li id="ul0009-0001" num="0042"> by a document submitted to the IETF, which proposes a solution enabling a terminal of the IP network to distinguish the IPv6 prefix of its organization: </li></ul></li><li id="ul0006-0007" num="0043"> draft-zill-ipv6wg-zone-prefixlen-oo.txt (Organization Zone Prefix Length Discovery). </li></ul></li></ul>

0044The solutions for terminal mobility management within IP networks are defined by the following IETF documents (www.ietf.org): <ul id="ul0010" list-style="none"><li id="ul0010-0001" num="0000"><ul id="ul0011" list-style="none"><li id="ul0011-0001" num="0045"> RFC 3344 (IP Mobility support for IPv4) for IPv4; </li><li id="ul0011-0002" num="0046"> draft-ietf-mobileip-ipv6-20.txt for IPv6. </li></ul></li></ul>

0047The solutions for terminal mobility management within IP networks using an AAA “Authentication, Authorization, Accounting” infrastructure are defined by the following IETF documents (www.ietf.org): <ul id="ul0012" list-style="none"><li id="ul0012-0001" num="0000"><ul id="ul0013" list-style="none"><li id="ul0013-0001" num="0048"> Protocol Diameter: draft-ietf-aaa-diameter-17.txt </li><li id="ul0013-0002" num="0049"> Application Mobile IPv4: draft-ietf-aaa-diameter-mobileip-13.txt; </li><li id="ul0013-0003" num="0050"> Application Mobile IPv6: draft-le-aaa-diameter-mobileipv6-0.3.txt. </li></ul></li></ul>

0051The prior arts implementing the abovementioned solutions to support the movement of a roaming terminal present many drawbacks, due to unresolved operational problems.

0052All the fixed or roaming terminals connected to the same link, affiliated to the same original home network, forming a local area network for example, have an IP address with the same prefix, but different suffixes.

0053According to the IPv4 protocol, an IP address is encoded on 32 bits. The length of the prefix used to describe a network address is variable, from 1 to 30 bits. A part of the IPv4 addressing space, a set of addresses, is reserved for the “unicast” addresses, in accordance with the IETF document: RFC 3232. The term “unicast” denotes all of the “Unicast” and “Global Unicast” addresses.

0054According to the IPv6 protocol, an IP address is encoded on 128 bits. The length of the suffix of a “unicast” address is set at 64 bits, except for specific IPv6 addresses which begin with the word “000”, the use of which is highly regulated. A part of the IPv6 addressing space, a set of addresses, is reserved for the “unicast” addresses, in accordance with the IETF document: RFC 3513.

0055When a roaming terminal that is on the move connects to a receiving IP network that is separate from its original home network, there are currently three protocols that allow such a terminal to acquire an IP address enabling it to be integrated into the receiving IP network.

0056A first protocol, designated DHCP, for “Dynamic Host Configuration Protocol”, can be implemented within the framework of the abovementioned IPv4 and IPv6 protocols. It allows an IP terminal to ask an address server to allocate it an IP address from a pool, or set of addresses, that is specific to it for a period of time negotiated between the roaming terminal, the client, and the address server. On such an allocation, the requesting IP terminal also detects the prefix of the link to which it is connected. The series of IPv4 and IPv6 protocols defines a protocol called DHCPv4, or respectively DHCPv6, based on a dynamic allocation mechanism. The latter provides good flexibility in terms of configuration and makes it possible to allocate a client terminal an IP address and other configuration parameters in the network such as DNS (Domain Name System) address, as per documents RFC 1034 and 1035 published by the IETF, for routers, servers, gateways and the like.

0057A second protocol is an integral part of the “Mobile IP” protocols. In the context of the abovementioned IPv4 and IPv6 protocols, the corresponding versions of this second protocol are compatible with the use of the DHCP protocol, but use a different mode, better suited to the mobility of the roaming terminals within different IP networks. In both the abovementioned versions, this second protocol relies on the fact that the routers of the IP networks periodically transmit announcement messages, in particular in the IPv6 version, describing the prefix of the original home or receiving IP networks to which the fixed or roaming terminals are connected.

0058A roaming terminal on the move then uses these announcement messages to detect the prefix of the IP network to which it is connected, and uses it to self-generate and be assigned a unique, coherent “unicast” address. In the IPv4 version, however, the abovementioned periodic announcement messages can directly announce the complete “unicast” address which can be used by the roaming terminal on the move. This address is an address assigned to a router, managed by the latter, and can be used by a roaming terminal on the move when the procedures described in the Mobile IP protocol (for IPv4) are followed.

0059In the context of this second protocol, a fixed or roaming terminal has a fixed IP address, configured specifically in the terminal. This fixed IP address is part of the original home network of the terminal and constitutes a coherent address with the prefix of the original home link of the terminal, original home link and therefore network to which the roaming terminal is connected, when the latter is not on the move.

0060In the context of the “Mobile IP” protocols, a roaming terminal on the move always remains in contact with its original home network. To this end, there is provided, installed on the latter, a software agent called “Home Agent”, HA. When the roaming terminal on the move has acquired a new IP address that is different, and therefore unknown, to those that are part of its original home network, it then registers with its software agent HA by communicating to it the IP address that is newly acquired and that it will use from now on to communicate. Thus, the software agent HA still knows the IP address that it must use to enter into contact with the roaming terminal on the move.

0061A third protocol is also implemented mainly by the IP network access control protocols.

0062The access control protocols are used between the roaming terminal on the move and the first IP router of the receiving IP network, also called access router.

0063The access control protocol used between the access router and an access control server is normally the RADIUS protocol or a more recent development of the latter, the DIAMETER protocol.

0064Among the parameters conveyed by the DIAMETER and RADIUS protocols, there is one that specifies the IP address to be assigned to the roaming terminal on the move requesting access. This IP address is then transmitted to the terminal by the access control protocol.

0065In this type of architecture, an access control server affiliated to the original home network of the roaming terminal and implementing the DIAMETER protocol, this server also being designated AAAH, for “Authentication, Authorization, Accounting Home” server, is configured to handle the authentication and access authorization of the roaming terminal on the move.

0066Thus, the AAAH server is always notified when one of the terminals that it manages tries to connect to the IP network and can even, depending on the case, propose the IP address to be assigned to it.

0067The advantage of the DIAMETER protocol is that this protocol proposes a distributed architecture of access control servers, which makes it possible to control access to terminals via local area networks managed by separate organizations. When being allocated its new IP address, the roaming terminal on the move also detects the prefix of the link to which it is connected.

0068The drawbacks, due to inadequacies, of the abovementioned three current protocols can be summarized as follows.

0069The DHCP protocol, in addition to the address that it allows to be allocated to a terminal, is capable of providing other network configuration parameters to the latter. The main parameters are the network mask, the validity time granted to the new address, the default network gateway address, address of an access provider or an ISP (for “International Standard Profile”) via which the terminal will access the IP network, and the identifier of the client and the name of the server to be used.

0070However, it cannot compensate for the addressing-related problems inherent to the IPv4 protocol and its breakdown into sites and organizations.

0071In particular, the structure of the addresses and the terminal/router dialogs do not in any way allow the terminals to determine: <ul id="ul0014" list-style="none"><li id="ul0014-0001" num="0000"><ul id="ul0015" list-style="none"><li id="ul0015-0001" num="0072"> when an address is allocated to the IP terminal on the move; </li><li id="ul0015-0002" num="0073"> whether it is connected to another link affiliated to its original site; </li><li id="ul0015-0003" num="0074"> whether it is connected to a link from another site affiliated to its original organization; </li><li id="ul0015-0004" num="0075"> whether it is connected to a link not affiliated to its organization; </li><li id="ul0015-0005" num="0076"> whether the addresses cover a number of sites of one and the same business or a number of different businesses that can use the same network address prefixes. </li></ul></li></ul>

0077With the second protocol being an integral part of the “Mobile IP” protocols, when a terminal acquires a new IP address, this terminal can only determine the prefix of the subnetwork, such as a local area network, to which the new IP address that has been acquired belongs, and compare it to the prefix of its fixed address.

0078While it can make it possible to detect whether the roaming terminal is connected to its original link, on the negative side, it cannot in any way make it possible to determine whether the roaming terminal is connected: <ul id="ul0016" list-style="none"><li id="ul0016-0001" num="0000"><ul id="ul0017" list-style="none"><li id="ul0017-0001" num="0079"> to another link affiliated to its original site; </li><li id="ul0017-0002" num="0080"> to a link affiliated to a site of its original organization; </li><li id="ul0017-0003" num="0081"> to a link not affiliated to its organization. </li></ul></li></ul>

0082Furthermore, the second abovementioned protocol does not necessarily allow the roaming terminal to detect whether it is connected to its original home network. Such is in particular the case when there are overlapping addressing plans, that is, when a number of sites of one and the same business or several different businesses use the same network prefixes.

0083In these conditions, if the roaming terminal connects to an IP network using the same prefix as its original home network, in the absence of possible discrimination, this roaming terminal will, wrongly, believe it is connected to the latter.

0084Finally, when a roaming terminal on the move transmits IP data packets outside the site to which it is connected, a translation of the source address of the packets may be performed, for example in the case of overlapping addressing plans or if the sites of the organization are linked via the INTERNET. In these conditions, the roaming terminal on the move is therefore no longer accessible from the outside by its address acquired dynamically, but by its translated address. It will be remembered that, for any site to which a roaming terminal is connected, the interior denotes, in fact, all the networks and IP nodes that are interconnected and that are identifiable by all the private and public IP addresses of the organization to which the abovementioned any site belongs. The exterior denotes all the IP networks and nodes that cannot be identified from the abovementioned addresses.

0085In the case of the third protocol, the use of an access control protocol based on a DIAMETER type architecture results in the roaming terminal on the move having only a fixed identifier called NAI (Network Access Identifier), which makes it possible, among other things, to determine the AAAH server to be interrogated to request access. Furthermore, the roaming terminal does not know the IP address of the AAAH server affiliated to its original home network. Thus, when an address is assigned to the roaming terminal on the move, the latter cannot in any case determine if it is connected: <ul id="ul0018" list-style="none"><li id="ul0018-0001" num="0000"><ul id="ul0019" list-style="none"><li id="ul0019-0001" num="0086"> to another link affiliated to its original site; </li><li id="ul0019-0002" num="0087"> to a link affiliated to another site of its original organization; </li><li id="ul0019-0003" num="0088"> to a link not affiliated to its original organization. </li></ul></li></ul>

0089Besides the lapses relating to the inadequacies inherent in the location of the abovementioned protocols, the transmission of a multicast broadcast that is local to a site to another site, even if this site and this other site belong to one and the same original organization, is not possible.

0090Thus, when a roaming terminal on the move requests access to a broadcast identified by the multicast group address, it simply transmits an access request using the IGMP protocol, specifying the address for which it wants to receive the stream.

0091Such a method does not therefore make it possible, in any case, to take into account the location of the connection of the roaming terminal in order to transmit broadcasts local to the original site and/or organization, for which access is therefore restricted by this location.

0092The object of the present invention is to remedy all of the drawbacks of the techniques and processes of the prior art, in order to make it possible to ensure the transmission of any type of broadcast local to the original site and/or organization to which the roaming terminal is affiliated in the absence of any limitation given the location of the network connection of the latter with respect to that original site and/or organization.

0093One object of the present invention is in particular to implement a method of multicast broadcasting to a roaming terminal, making it possible to combine a location process of this roaming terminal and an extended multicast broadcast process that are specific, an extended multicast broadcast process whereby a broadcast local to an original site and/or an organization is made accessible via a global multicast broadcast.

0094In particular, an object of the abovementioned combination is to jointly implement a unique location process for any roaming terminal, making it possible to create and transmit to the latter a location discriminating information item, with respect to the original site and/or organization to which this roaming terminal is affiliated, and a unique extended multicast broadcast process which, depending on this location discriminating information item, makes it possible to replace any multicast broadcast local to the original site and/or organization to which this roaming terminal is affiliated with a global multicast broadcast allowing access to the latter by this roaming terminal, when the latter is connected outside its original site and/or organization, in the absence of access to this local multicast broadcast.

0095The method of multicast broadcasting to a roaming terminal according to the IP network connection of the latter, the subject of the present invention, is noteworthy in that, following a routine connection of this roaming terminal to a site affiliated or not affiliated to the original site and/or organization to which this roaming terminal is attached and the transmission of a message requesting registration of this roaming terminal to the original site, this method consists in at least, on this original site, discriminating the location of this roaming terminal with respect to its original site, or its original organization, from this registration message, and transmitting to the roaming terminal a location discriminating information item and, on this roaming terminal, for any request to access a group multicast broadcast intended for the original site and relating to a multicast broadcast local to the original site, or to the original organization, of this roaming terminal, replacing this access request, when this location information designates a connection of this roaming terminal outside its original site, or its original organization, with a request to access an extended multicast broadcast allowing access to said local multicast broadcast and transmitting, to the original site, the request to access this extended multicast broadcast.

0096The system of multicast broadcasting to a roaming terminal according to the IP network connection of the latter, the subject of the present invention, is noteworthy in that, following a routine connection of this roaming terminal to a site affiliated or not affiliated to the original site and/or organization to which this roaming terminal is attached and the transmission of a signaling message from this roaming terminal to this original site, this system comprises at least, on the original site, a module for discriminating the location of this roaming terminal with respect to its original site, or its original organization, from this signaling message, and a module for transmitting to this roaming terminal a location discriminating information item, and, on this roaming terminal, for any request from this roaming terminal to access a group multicast broadcast intended for the original site and relating to a multicast broadcast local to the original site, or to the original organization, of this roaming terminal, a module for replacing this access request, when this location discriminating information item designates a connection of this roaming terminal outside its original site, or its original organization, with a request to access an extended multicast broadcast allowing access to this local multicast broadcast and a module for transmitting to the original site this request to access this extended multicast broadcast.

0097The method and the system of multicast broadcasting that are the subjects of the present invention find application in any type of IP network, in particular local area networks, wide area networks, the INTERNET, and so on.

0098They will be better understood from reading the description and studying the drawings below, in which, in addition to <figref idref="DRAWINGS">FIGS. 1</figref><i>a</i>, <b>1</b><i>b </i>and <b>1</b><i>c </i>relating to the prior art,

0099<figref idref="DRAWINGS">FIG. 2</figref><i>a </i>represents, by way of illustration, a flow diagram of the essential steps for implementing the multicast broadcasting method that is the subject of the present invention;

0100<figref idref="DRAWINGS">FIG. 2</figref><i>b </i>represents, by way of illustration, an implementation detail of the multicast broadcasting method that is the subject of the invention as represented in <figref idref="DRAWINGS">FIG. 2</figref><i>a; </i>

0101<figref idref="DRAWINGS">FIG. 3</figref><i>a </i>represents, by way of illustration, a preferential nonlimiting flow diagram of a unique process for locating a roaming terminal with respect to its original site or its original organization, enabling the method that is the subject of the present invention to be implemented;

0102<figref idref="DRAWINGS">FIG. 3</figref><i>b </i>represents, by way of illustration, a specific method of implementing the comparison process used by the unique location process, according to <figref idref="DRAWINGS">FIG. 3</figref><i>a; </i>

0103<figref idref="DRAWINGS">FIG. 4</figref><i>a </i>represents, by way of illustration, a preferential flow diagram of a unique extended multicast transmission process enabling the method that is the subject of the present invention to be implemented;

0104<figref idref="DRAWINGS">FIG. 4</figref><i>b </i>represents, by way of illustration, an implementation detail of a process for transferring a multicast broadcast local to a site to a global broadcast or a broadcast local to the original organization;

0105<figref idref="DRAWINGS">FIG. 5</figref> represents, by way of illustration, a diagram of a system of multicast broadcasting to a roaming terminal according to its location, in accordance with the subject of the present invention.

0106A more detailed description of the method of multicast broadcasting to a roaming terminal, according to the location of the IP network connection of the latter, in accordance with the subject of the invention, will now be given in conjunction with <figref idref="DRAWINGS">FIG. 2</figref><i>a. </i>

0107With reference to the abovementioned figure, consideration is given to a roaming terminal T affiliated to an original site S₁and, of course, an original organization O₀, this roaming terminal being brought, by the movement of the user U of the latter, to any site S_xand to connect to the abovementioned any site S_x.

0108It should be indicated generally, that the any site S_xis or is not affiliated to the original site and/or organization to which the roaming terminal T is attached.

0109With reference to <figref idref="DRAWINGS">FIG. 2</figref><i>a</i>, the step A for connecting the roaming terminal to the site S_xis shown due to the initiative of the user U, the terminal T then taking the reference T_xpurely because of the connection of this terminal to the abovementioned any site S_x.

0110Purely because of this connection, and conventionally, the duly connected roaming terminal T_xis able to transmit, if necessary, a signaling request message from this roaming terminal to the original site S₁, this signaling message being denoted RM(LR). Such a message is not necessary when the roaming terminal is connected to its original link or subnetwork.

0111As a nonlimiting example, it is indicated that, in the abovementioned signaling message, the parameter LR designates a location reference formed, for example, by an IP address allocated by the site receiving the roaming terminal T_x, that is, the any site S_x, in particular by the administrator of the abovementioned any site S_x.

0112Following the transmission of the signaling message RM(LR), the method that is the subject of the invention consists, on the original site S₁, and following the receipt of this signaling message, in a step B, in discriminating the location of the roaming terminal T_x, with respect to its original site S₁, or its original organization O₀, from the abovementioned signaling message, the discrimination extending to the creation of a location discriminating information item LI, as will be described later in the description.

0113The step consisting in discriminating is then followed by a step consisting in transmitting to the roaming terminal T_xthe abovementioned location discriminating information item LI, in order for the latter to be able to use the discriminated location information.

0114The abovementioned step B is then followed, on the roaming terminal T_x, for any request from the roaming terminal to access a group multicast broadcast intended for the original site S₁and relating to a multicast broadcast local to the original site, or to the original organization, of the roaming terminal, the access request being denoted AD(GR), GR in fact designating the group multicast broadcast address in the original site, in replacing, in the steps D, F, G, H as represented in <figref idref="DRAWINGS">FIG. 2</figref><i>a</i>, the access request AD(GR) with a request to access an extended multicast broadcast, when, on the one hand, the access request AD(GR) relates to a multicast broadcast local to the original site S₁, or the original organization O₀, of the roaming terminal and, on the other hand, the location discriminating information item LI designates a connection of the roaming terminal outside its original site S₁, or its original organization O₀.

0115It will be understood in particular that, with the abovementioned replacement, any access request relating to a multicast broadcast local to the original site, or to the original organization, of the roaming terminal, cannot be accessed from any site S_xconnecting the roaming terminal outside its original site, or outside its original organization, but that, however, the request to access an extended multicast broadcast allows access to the multicast broadcast local to the original site, or to the original organization, from the roaming terminal concerned.

0116The abovementioned replacement step is then followed by a step F consisting in transmitting to the original site the request to access the extended multicast broadcast as will be described later in the description.

0117In particular, it is indicated that the request to access the extended multicast broadcast is denoted AR(GR₂), the abovementioned replacement operation consisting, as will be described in more detail later in the description, in replacing the address GR requesting access to a group multicast broadcast with an extended multicast broadcast address GR₂making it possible to provide a similar data broadcast.

0118In a first embodiment of the method that is the subject of the present invention, it is indicated that the abovementioned replacement operation can be managed as represented in <figref idref="DRAWINGS">FIG. 2</figref><i>a. </i>

0119Following the step C of the access request generated by the roaming terminal Tx solely on the initiative of the user U, the replacement operation can consist in performing a test D to discriminate the address GR of the request to access a group multicast broadcast, the test of the step D consisting in discriminating whether the abovementioned address GR is a global address GA, a group address local to the organization GI₀or even a group address local to the site GI_s.

0120To implement the test of the step D, it is indicated that the value of the address G of the request to access a group multicast broadcast is simply discriminated as a value relative to a law for creating values for global access addresses GA, group addresses local to the organization GI₀, or group addresses local to the site GI_s.

0121It is indicated, by way of nonlimiting example, that the global addresses GA, local to the organization GI₀, or to the site GI_scan, by way of nonlimiting example, correspond to values of addresses assigned by the administrator of the original site S₁from unconnected ranges of values in order to perform a simple discrimination by comparison.

0122On a positive response that the address GR of the access request belongs to the set of global addresses GA, this positive address being denoted “yes” in <figref idref="DRAWINGS">FIG. 2</figref><i>a</i>, the request to access a group multicast broadcast is then transmitted in a step E directly in the form of an access request denoted AR(GR), the group multicast broadcast request being accessible by the roaming terminal Tx independently of the location of its connection site because of the global nature of the multicast broadcast.

0123When the address GR of the group multicast broadcast request is not a global address, it corresponds either to a group multicast broadcast address local to the organization GI₀or local to the site GI_s.

0124This situation is represented symbolically in the test D of <figref idref="DRAWINGS">FIG. 2</figref><i>a </i>by the response “yes but” when the address GR is an address global to the organization GI₀and by the response “no” when the address GR is, on the other hand, an address global to the site GI_s. In the two abovementioned situations represented by the “yes but” and “no” situations in response to the test D, the knowledge of the location of the connection or, more precisely, of the site of the roaming terminal T_xon the any site S_x, is then necessary.

0125Consequently, the responses “yes but” and “no” to the test D are then followed by a call to the step F for the location information LI, which has been transmitted to the roaming terminal in the step B by the original site S₁.

0126The step F is then followed by a step G, the object of which is to discriminate whether the group multicast broadcast request address GR belongs to the set of global addresses local to the original organization when the roaming terminal is connected to a site separate from the original site but affiliated to the original organization O₀, or whether the group broadcast request address GR belongs to the set of group addresses local to the original site and the connection of the roaming terminal T_xto the latter.

0127Consequently, the test of the step G is used to create the following logical relations: <br />LI∈O₀AND GR∈GI₀; <br />LI∈S₁AND GR∈GI_s.

0128On positive response to one or other of the abovementioned logical relations, the group multicast broadcast access request AD(GR) is then created in the form of a request to access this same address G in the form of request AR(GR) in the step E of <figref idref="DRAWINGS">FIG. 2</figref><i>a. </i>

0129On the other hand, on a negative response to one or other of the logical relations of the test of the step G, a step H is invoked in order to enable the group multicast broadcast access request GR, which cannot be received on the any site S_xto which the terminal T_xis connected, to be replaced with an address GR₂making it possible, on the other hand, to receive on the abovementioned site S_xthe abovementioned group multicast broadcast.

0130The step H is then followed by a step I consisting in transmitting the access request AR(GR₂) in which the group multicast broadcast address has been replaced by a so-called extended multicast broadcast address GR₂enabling, of course, access to the local multicast broadcast that cannot be accessed from the roaming terminal connected to the any site S_x.

0131The replacement procedure carried out in the step H will be described later in the description.

0132As a general rule, it will be observed in <figref idref="DRAWINGS">FIG. 2</figref><i>a </i>that the location reference LR, on the one hand, and the group multicast broadcast request address GR, on the other hand, are, of course, independent variables left substantially to the judgment of the user U.

0133For this reason, it is, of course, possible to envisage reversing, where appropriate, the succession of the steps D, F and G, without departing from the framework of the object of the present invention, the discrimination of the affiliation of the location reference LI to the original organization, or to the original site, possibly being carried out prior to the discrimination of the value of the group multicast broadcast request address GR, for example.

0134Such a reversal will not be described, because it falls within the scope of those skilled in the art.

0135Regarding the implementation of the logical steps represented in steps D and G of <figref idref="DRAWINGS">FIG. 2</figref><i>a</i>, these can be implemented as represented in <figref idref="DRAWINGS">FIG. 2</figref><i>b</i>, the step D possibly being subdivided in fact into two successive tests D₁and D₂, in which the group multicast broadcast address GR is successively compared to the set of group global addresses GA in the substep D₁, the negative response to the abovementioned substep making it possible to invoke the substep D₂to test whether the group address GR belongs to the set of group addresses local to the organization GI₀. A positive response to the substep D₂restores the situation of the response “yes but” of the step D in <figref idref="DRAWINGS">FIG. 2</figref><i>a </i>and a negative response to the substep D₂restores the situation of the negative response “no” to the test of the step D in <figref idref="DRAWINGS">FIG. 2</figref><i>a. </i>

0136The step G of <figref idref="DRAWINGS">FIG. 2</figref><i>a </i>can also be subdivided into two substeps G₁, or G₂, on affiliation of the location reference LI to the original organization O₀, or to the original site S₁.

0137The steps E, F, H and I are then invoked in the same way as in the case of <figref idref="DRAWINGS">FIG. 2</figref><i>a. </i>

0138A more detailed description of a unique process for discriminating the connection site with respect to the original site and/or original multisite organization of a roaming terminal in accordance with the object of the present invention will now be given in conjunction with <figref idref="DRAWINGS">FIG. 1</figref><i>c</i>, relating to the prior art, and <figref idref="DRAWINGS">FIGS. 3</figref><i>a </i>and <b>3</b><i>b. </i>

0139<figref idref="DRAWINGS">FIG. 1</figref><i>c </i>represents an original multisite organization O₀comprising, for example, three sites S₁, S₂, S₃, the site S₁making up the original site corresponding to a local area network, for example of IP type, comprising a plurality of routers R₁₁, R₁₂and R₁₃, and a server S for managing the abovementioned original multisite organization O₀.

0140The site S₂is, for example, made up of an IP type local subnetwork linked to the local area network forming the original home network of the site S₁.

0141Finally, the site S₃is a site affiliated to the original multisite organization O₀, the site S₃being, however, linked to the original home network and to the site S₁via the Internet for example.

0142A roaming terminal T₁is thus liable to operate in its original home network, this terminal connected to the original site S₁to which it is attached being referenced T₁and connected to the router R₁₂for example, and/or outside its original home network, this terminal then being denoted T₂when it is connected to the local subnetwork forming the site S₂via the router R₂.

0143The abovementioned roaming terminal can also be connected outside its original home network to the site S₃affiliated to the original multisite organization O₀, but via the INTERNET, the abovementioned roaming terminal being denoted T₃in this situation, and connected to the router R₃.

0144Finally, the abovementioned roaming terminal can be connected to any site denoted S_pnot affiliated to the original multisite organization O₀but, on the other hand, to any multisite organization, denoted O_p, the abovementioned roaming terminal bearing the reference T_pin this situation.

0145It will, of course, be understood, by way of nonlimiting example, that the abovementioned roaming terminal bearing the references T₁, T₂, T₃and T_pcan be one and the same terminal on the move or even any separate roaming terminal likely to implement the method that is the object of the present invention.

0146As is represented in <figref idref="DRAWINGS">FIG. 1</figref><i>c</i>, the roaming terminal T₁is allocated, by the original home site and ultimately by the original home network, an internal permanent address denoted P@_1ifor any network connection of the roaming terminal T₁to a site affiliated to this original home network.

0147Similarly, an internal temporary address is allocated to the roaming terminal referenced T₂or T₃for any network connection of the abovementioned roaming terminal to another site affiliated to the original multisite organization O₀. It will be understood, in particular, that the administrator of the IP network that forms the original multisite organization O₀and ultimately, the administrator of the sites S₁, S₂and S₃is then able to allocate, when the roaming terminal in position T₂is connected to the site S₂, an internal temporary address denoted P@_2jor, on the other hand, an internal temporary address denoted P@_3kor P@_4lwhen the roaming terminal in position T₃is connected to the site S₃. It is indicated in particular that the distinction between the internal temporary addresses P@_3kor P@_4lcorresponds respectively to a substantially arbitrary, so-called mobility temporary address allocated by the server center S, or to a translation address for example.

0148It will be remembered, in particular, that, in the case of a business, the administrator has a set of so-called private IP addresses, which can be used freely; any administrator of an IP network can also freely re-use these same IP addresses (IETF document RFC 1918). Furthermore, when this business wishes to communicate over the INTERNET, it must then use its globally unique IP addresses, unique in the world and therefore regardless of the network connected to the INTERNET. The globally unique addresses are called public and assigned either by the INTERNET service provider, or by a Regional Internet Registry (RIR) organization. More often than not, the businesses use a device between their network and the INTERNET which translates the private addresses into public addresses. In the method that is the object of the invention, the IP address assigned to the roaming terminal T_xcan be private and the datagrams used to reach the server S can, nevertheless, pass through an address translator via the INTERNET and therefore appear to come from a public address. Such a public address can, for example, be owned by the site S₃of <figref idref="DRAWINGS">FIG. 1</figref>, or any other site.

0149Finally, when the roaming terminal is connected to any site, such as the site S_pnot affiliated to the original multisite organization but to another multisite organization O_p, then the address allocated to the terminal in position T_pin <figref idref="DRAWINGS">FIG. 1</figref> is designated P@_pmand constitutes an external temporary address. P@_pmdesignates a private address and P@_6ndesignates a public address used in address translation of the abovementioned private address P@_pm.

0150It will be understood, in these conditions, that the concept of internal permanent and temporary address corresponds to the internal nature of the addresses allocated to the original multisite organization O₀, whereas the external nature of the temporary address, when the roaming terminal is connected to a site not affiliated to the original multisite organization, corresponds to the external nature of this address with respect to the abovementioned original multisite organization.

0151It will, of course, be understood that, a priori, only the internal addresses are known to the original multisite organization O₀, the external addresses not being known to the latter.

0152Consequently, and in accordance with one aspect of the method that is the object of the present invention, it is considered that the abovementioned internal and/or external addresses form, for the roaming terminal, a location reference relative to the original multisite organization O₀.

0153Thus, by way of nonlimiting example: <maths id="MATH-US-00001" num="1"><math overflow="scroll"><mrow><mrow><mo>{</mo><mrow><mi>P</mi><mo>⁢</mo><msub><mo>@</mo><mrow><mn>1</mn><mo>⁢</mo><mi>si</mi></mrow></msub></mrow><mo>}</mo></mrow><mo>⁢</mo><mtable><mtr><mtd><mrow><mi>i</mi><mo>=</mo><mi>I</mi></mrow></mtd></mtr><mtr><mtd><mrow><mrow><mi>i</mi><mo>=</mo><mn>1</mn></mrow><mo>,</mo><mrow><mi>s</mi><mo>=</mo><mrow><mn>1</mn><mo>⁢</mo><mstyle><mtext> </mtext></mstyle><mo>⁢</mo><mi>to</mi><mo>⁢</mo><mstyle><mtext> </mtext></mstyle><mo>⁢</mo><mi>H</mi></mrow></mrow><mo>,</mo></mrow></mtd></mtr></mtable></mrow></math></maths><br /> denotes the set of internal permanent addresses of one of the subnetworks allocated to the set of roaming terminals attached to the original home network supporting the original site S₁. This set is the set of the internal permanent addresses of the original link or original subnetwork, the set {P@_1i} therefore refers to the set of addresses of the original site S<b>1</b>, all the subnetworks being combined; <maths id="MATH-US-00002" num="2"><math overflow="scroll"><mrow><mrow><mo>-</mo><mrow><mo>{</mo><mrow><mi>P</mi><mo>⁢</mo><msub><mo>@</mo><mrow><mn>2</mn><mo>⁢</mo><mi>j</mi></mrow></msub></mrow><mo>}</mo></mrow></mrow><mo>⁢</mo><mtable><mtr><mtd><mrow><mi>j</mi><mo>=</mo><mi>J</mi></mrow></mtd></mtr><mtr><mtd><mrow><mrow><mi>j</mi><mo>=</mo><mn>1</mn></mrow><mo>,</mo></mrow></mtd></mtr></mtable><mo>⁢</mo><mrow><mo>{</mo><mrow><mi>P</mi><mo>⁢</mo><msub><mo>@</mo><mrow><mn>3</mn><mo>⁢</mo><mi>k</mi></mrow></msub></mrow><mo>}</mo></mrow><mo>⁢</mo><mtable><mtr><mtd><mrow><mi>k</mi><mo>=</mo><mi>K</mi></mrow></mtd></mtr><mtr><mtd><mrow><mrow><mi>k</mi><mo>=</mo><mn>1</mn></mrow><mo>,</mo></mrow></mtd></mtr></mtable><mo>⁢</mo><mrow><mo>{</mo><mrow><mi>P</mi><mo>⁢</mo><msub><mo>@</mo><mrow><mn>4</mn><mo>⁢</mo><mi>l</mi></mrow></msub></mrow><mo>}</mo></mrow><mo>⁢</mo><mtable><mtr><mtd><mrow><mi>l</mi><mo>=</mo><mi>L</mi></mrow></mtd></mtr><mtr><mtd><mrow><mi>l</mi><mo>=</mo><mn>1</mn></mrow></mtd></mtr></mtable></mrow></math></maths><br /> the set of internal temporary addresses allocated to the set of the abovementioned roaming terminals for any connection of one of these roaming terminals to another site affiliated to the original multisite organization O₀; <maths id="MATH-US-00003" num="3"><math overflow="scroll"><mrow><mrow><mo>-</mo><mrow><mo>{</mo><mrow><mi>P</mi><mo>⁢</mo><msub><mo>@</mo><mi>pm</mi></msub></mrow><mo>}</mo></mrow></mrow><mo>⁢</mo><mtable><mtr><mtd><mrow><mi>m</mi><mo>=</mo><mi>M</mi></mrow></mtd></mtr><mtr><mtd><mrow><mi>m</mi><mo>=</mo><mn>1</mn></mrow></mtd></mtr></mtable></mrow></math></maths><br /> the set of the external temporary addresses allocated by a multisite organization O_pseparate from the original multisite organization and for any site S_paffiliated to this separate multisite organization; <maths id="MATH-US-00004" num="4"><math overflow="scroll"><mrow><mrow><mo>-</mo><mrow><mo>{</mo><mrow><mi>P</mi><mo>⁢</mo><msub><mo>@</mo><mrow><mn>6</mn><mo>⁢</mo><mi>n</mi></mrow></msub></mrow><mo>}</mo></mrow></mrow><mo>⁢</mo><mtable><mtr><mtd><mrow><mi>n</mi><mo>=</mo><mi>N</mi></mrow></mtd></mtr><mtr><mtd><mrow><mi>n</mi><mo>=</mo><mn>1</mn></mrow></mtd></mtr></mtable></mrow></math></maths><br /> the set of the public addresses used by translation of the private addresses P@_pm.

0154With reference to <figref idref="DRAWINGS">FIG. 3</figref><i>a</i>, for any network connection of the abovementioned roaming terminal on a predetermined site, the unique location process that is the object of the invention consists in a step A in transmitting from the roaming terminal T₁, T₂, T₃or T_p, to the original home network and ultimately to the site S₁affiliated to the original multisite organization O₀, a registration message comprising at least the abovementioned location reference.

0155In <figref idref="DRAWINGS">FIG. 3</figref><i>a</i>, the registration message is denoted:

0156RM (LR), in which LR designates the abovementioned location reference. It will be remembered that the location reference is formed by one of the addresses allocated to the roaming terminal on the move mentioned previously according to the situations represented in <figref idref="DRAWINGS">FIG. 1</figref><i>c. </i>

0157The signaling message can be used to perform a registration of the connection of the roaming terminal.

0158In particular, in a nonlimiting but advantageous manner, it is indicated that the location reference LR can consist of a coded value, dependent on the address allocated. Given this assumption, this coded value can be obtained on the roaming computer, based on a specific bit-by-bit or other XOR coding function of the permanent address with a parameter-setting key, the reciprocal coding function and the parameter-setting key with which to restore the permanent address being known only to the server S of the original site S₁. The identity coding and reciprocal decoding functions are used, for example, to transmit only the original permanent address. To this end, the roaming terminal can perform a test, being able to compare the result of the coding of the location reference LR, by means of the coding function f, designated f(LR), and the result of this same coding function applied to the original permanent address {P@_1si}. The roaming terminal knowing only f{P@_1si} proceeds to calculate f(LR) to be able to perform this comparison. The latter enables the roaming terminal to detect or not whether it is or is not connected to its original link on its original site S₁. The server S must proceed to decode the value resulting from the coding RP@_1si=f{P@_1si} to retrieve the true fixed set {P@_1si}_i=1^i=I, s. Only the server S knows the inverse function f⁻¹, which, when applied to the coded value of the permanent address f⁻¹(f {P@_1si})={P@_1si} restores the latter. The server S can then compare the value of the location reference LR with <maths id="MATH-US-00005" num="5"><math overflow="scroll"><mrow><mrow><mo>{</mo><mrow><mi>P</mi><mo>⁢</mo><msub><mo>@</mo><mrow><mn>1</mn><mo>⁢</mo><mi>si</mi></mrow></msub></mrow><mo>}</mo></mrow><mo>⁢</mo><mtable><mtr><mtd><mrow><mi>i</mi><mo>=</mo><mi>I</mi></mrow></mtd></mtr><mtr><mtd><mrow><mrow><mi>i</mi><mo>=</mo><mn>1</mn></mrow><mo>,</mo></mrow></mtd></mtr></mtable></mrow></math></maths><br /> s=1 to H, to check that the terminal is on its original site.

0159The step A is then followed by a step B₁consisting in comparing, for identification purposes, the location reference LR with the address values of at least one of the aforementioned sets formed by the set of internal permanent addresses allocated to the set of roaming terminals attached to the original home network and by the set of internal temporary addresses allocated to this set of roaming terminals for any connection to another site affiliated to the original multisite organization O₀.

0160In <figref idref="DRAWINGS">FIG. 3</figref><i>a</i>, the comparison operation is symbolized by the relation: <maths id="MATH-US-00006" num="6"><math overflow="scroll"><mrow><mi>LR</mi><mo>∈</mo><mrow><mo>[</mo><mstyle><mtext> </mtext></mstyle><mo>⁢</mo><mtable><mtr><mtd><mrow><mrow><mtable><mtr><mtd><mrow><mo>{</mo><mrow><mi>P</mi><mo>⁢</mo><msub><mo>@</mo><mrow><mn>1</mn><mo>⁢</mo><mi>i</mi></mrow></msub></mrow><mo>}</mo></mrow></mtd></mtr></mtable><mo>⁢</mo><mtable><mtr><mtd><mrow><mi>i</mi><mo>=</mo><mi>I</mi></mrow></mtd></mtr><mtr><mtd><mrow><mi>i</mi><mo>=</mo><mn>1</mn></mrow></mtd></mtr></mtable></mrow><mo>;</mo></mrow></mtd><mtd><mrow><mrow><mrow><mo>{</mo><mrow><mi>P</mi><mo>⁢</mo><msub><mo>@</mo><mrow><mn>2</mn><mo>⁢</mo><mi>j</mi></mrow></msub></mrow><mo>}</mo></mrow><mo>⁢</mo><mtable><mtr><mtd><mrow><mi>k</mi><mo>=</mo><mi>K</mi></mrow></mtd></mtr><mtr><mtd><mrow><mrow><mi>k</mi><mo>=</mo><mn>1</mn></mrow><mo>,</mo></mrow></mtd></mtr></mtable></mrow><mo>;</mo></mrow></mtd><mtd><mrow><mrow><mo>{</mo><mrow><mi>P</mi><mo>⁢</mo><msub><mo>@</mo><mrow><mn>3</mn><mo>⁢</mo><mi>k</mi></mrow></msub></mrow><mo>}</mo></mrow><mo>⁢</mo><mtable><mtr><mtd><mrow><mi>k</mi><mo>=</mo><mi>K</mi></mrow></mtd></mtr><mtr><mtd><mrow><mrow><mi>k</mi><mo>=</mo><mn>1</mn></mrow><mo>,</mo></mrow></mtd></mtr></mtable></mrow></mtd><mtd><mrow><mrow><mo>{</mo><mrow><mi>P</mi><mo>⁢</mo><msub><mo>@</mo><mrow><mn>4</mn><mo>⁢</mo><mi>l</mi></mrow></msub></mrow><mo>}</mo></mrow><mo>⁢</mo><mtable><mtr><mtd><mrow><mi>l</mi><mo>=</mo><mi>L</mi></mrow></mtd></mtr><mtr><mtd><mrow><mi>l</mi><mo>=</mo><mn>1</mn></mrow></mtd></mtr></mtable></mrow></mtd></mtr></mtable><mo>⁢</mo><mstyle><mtext> </mtext></mstyle><mo>]</mo></mrow></mrow></math></maths>

0161The comparison step B₁is then followed by a step B₂consisting in transmitting from the original home site S₁to the roaming terminal, according to the position of the latter, a signaling response or acknowledgement message containing at least one location discriminating information item for the abovementioned roaming terminal.

0162In the step B₂, the registration acknowledgement message is denoted:

0000AR (LI).

0163For the abovementioned message, LI designates the location discriminating information item transmitted to the roaming terminal.

0164According to a noteworthy aspect of the method that is the subject of the invention, the location discriminating information item LI designates: <ul id="ul0020" list-style="none"><li id="ul0020-0001" num="0000"><ul id="ul0021" list-style="none"><li id="ul0021-0001" num="0165"> either the connection of the roaming terminal to its original home network, that is, to its site S₁, on identification of the location reference LR in the set of internal permanent addresses; </li><li id="ul0021-0002" num="0166"> or the network connection of the roaming terminal to another site affiliated to the original multisite organization on identification of the location reference LR in the set of internal temporary addresses mentioned previously; </li><li id="ul0021-0003" num="0167"> or even the network connection of the roaming terminal to any site not affiliated to the original multisite organization, in the absence of identification of the location reference LR in one or other of the set of internal permanent addresses and the set of internal temporary addresses. </li></ul></li></ul>

0168In <figref idref="DRAWINGS">FIG. 3</figref><i>a</i>, in the abovementioned step B₂, the content of the location discriminating information item is represented by the relations: <br />LI=0 if LR∈S₁; <br />LI=1 if LR∈(S₂;S₃) <br />LI=2 if LR∉(S₁,S₂,S₃).

0169In the preceding relation, it is indicated that the relations concerning affiliation to the sites S₁, S₂and S₃are represented symbolically but executed by checking whether the location reference belongs to the set of addresses associated with each of the abovementioned sites as mentioned previously in the description.

0170It is also understood that the fact that the location reference LR does not belong is also obtained by checking the absence of identification of the location reference LR in all the sets of addresses associated with each of the sites S₁, S₂, S₃affiliated to the original multisite organization.

0171Of course, in the symbolic relation given for the step B₂in <figref idref="DRAWINGS">FIG. 3</figref><i>a</i>, the values 0, 1 and 2 for the location information item LI are totally arbitrary.

0172Finally, in the step B₂in <figref idref="DRAWINGS">FIG. 3</figref><i>a</i>, T_xin fact designates the roaming terminal in the position T₁, T₂, T₃or T_p.

0173More specifically, it is indicated that the set of internal permanent addresses <maths id="MATH-US-00007" num="7"><math overflow="scroll"><mrow><mrow><mrow><mo>{</mo><mrow><mi>P</mi><mo>⁢</mo><msub><mo>@</mo><mrow><mn>1</mn><mo>⁢</mo><mi>i</mi></mrow></msub></mrow><mo>}</mo></mrow><mo>⁢</mo><mtable><mtr><mtd><mrow><mi>i</mi><mo>=</mo><mi>I</mi></mrow></mtd></mtr><mtr><mtd><mrow><mi>i</mi><mo>=</mo><mn>1</mn></mrow></mtd></mtr></mtable></mrow><mo>⁢</mo><mstyle><mtext> </mtext></mstyle></mrow></math></maths><br /> the set of internal temporary addresses <maths id="MATH-US-00008" num="8"><math overflow="scroll"><mrow><mrow><mo>{</mo><mrow><mi>P</mi><mo>⁢</mo><msub><mo>@</mo><mrow><mn>2</mn><mo>⁢</mo><mi>j</mi></mrow></msub></mrow><mo>}</mo></mrow><mo>⁢</mo><mtable><mtr><mtd><mrow><mi>j</mi><mo>=</mo><mi>J</mi></mrow></mtd></mtr><mtr><mtd><mrow><mrow><mi>j</mi><mo>=</mo><mn>1</mn></mrow><mo>,</mo></mrow></mtd></mtr></mtable><mo>⁢</mo><mrow><mo>{</mo><mrow><mi>P</mi><mo>⁢</mo><msub><mo>@</mo><mrow><mn>3</mn><mo>⁢</mo><mi>k</mi></mrow></msub></mrow><mo>}</mo></mrow><mo>⁢</mo><mtable><mtr><mtd><mrow><mi>k</mi><mo>=</mo><mi>K</mi></mrow></mtd></mtr><mtr><mtd><mrow><mi>k</mi><mo>=</mo><mn>1</mn></mrow></mtd></mtr></mtable><mo>⁢</mo><mstyle><mtext> </mtext></mstyle><mo>⁢</mo><mi>and</mi><mo>⁢</mo><mstyle><mtext> </mtext></mstyle><mo>⁢</mo><mrow><mo>{</mo><mrow><mi>P</mi><mo>⁢</mo><msub><mo>@</mo><mrow><mn>4</mn><mo>⁢</mo><mi>l</mi></mrow></msub></mrow><mo>}</mo></mrow><mo>⁢</mo><mtable><mtr><mtd><mrow><mi>l</mi><mo>=</mo><mi>L</mi></mrow></mtd></mtr><mtr><mtd><mrow><mi>l</mi><mo>=</mo><mn>1</mn></mrow></mtd></mtr></mtable></mrow></math></maths><br /> are advantageously formed by separate sets of address values allocated by the original home network to the roaming terminal which in fact requests it on its network connection to one of the sites affiliated to the original multisite organization. This operation is, of course, performed under the control of the server S and of the network administrator responsible for the latter.

0174However, since the sets <maths id="MATH-US-00009" num="9"><math overflow="scroll"><mrow><mrow><mo>{</mo><mrow><mi>P</mi><mo>⁢</mo><msub><mo>@</mo><mrow><mn>1</mn><mo>⁢</mo><mi>i</mi></mrow></msub></mrow><mo>}</mo></mrow><mo>⁢</mo><mtable><mtr><mtd><mrow><mi>i</mi><mo>=</mo><mi>I</mi></mrow></mtd></mtr><mtr><mtd><mrow><mrow><mi>i</mi><mo>=</mo><mn>1</mn></mrow><mo>,</mo></mrow></mtd></mtr></mtable><mo>⁢</mo><mrow><mo>{</mo><mrow><mi>P</mi><mo>⁢</mo><msub><mo>@</mo><mrow><mn>2</mn><mo>⁢</mo><mi>j</mi></mrow></msub></mrow><mo>}</mo></mrow><mo>⁢</mo><mtable><mtr><mtd><mrow><mi>j</mi><mo>=</mo><mi>J</mi></mrow></mtd></mtr><mtr><mtd><mrow><mi>j</mi><mo>=</mo><mn>1</mn></mrow></mtd></mtr></mtable><mo>⁢</mo><mstyle><mtext> </mtext></mstyle><mo>⁢</mo><mi>and</mi><mo>⁢</mo><mstyle><mtext> </mtext></mstyle><mo>⁢</mo><mrow><mo>{</mo><mrow><mi>P</mi><mo>⁢</mo><msub><mo>@</mo><mrow><mn>4</mn><mo>⁢</mo><mi>l</mi></mrow></msub></mrow><mo>}</mo></mrow><mo>⁢</mo><mtable><mtr><mtd><mrow><mi>l</mi><mo>=</mo><mi>L</mi></mrow></mtd></mtr><mtr><mtd><mrow><mi>l</mi><mo>=</mo><mn>1</mn></mrow></mtd></mtr></mtable></mrow></math></maths><br /> are formed by separate sets of address values, the set <maths id="MATH-US-00010" num="10"><math overflow="scroll"><mrow><mrow><mo>{</mo><mrow><mi>P</mi><mo>⁢</mo><msub><mo>@</mo><mrow><mn>3</mn><mo>⁢</mo><mi>k</mi></mrow></msub></mrow><mo>}</mo></mrow><mo>⁢</mo><mtable><mtr><mtd><mrow><mi>k</mi><mo>=</mo><mi>K</mi></mrow></mtd></mtr><mtr><mtd><mrow><mi>k</mi><mo>=</mo><mn>1</mn></mrow></mtd></mtr></mtable></mrow></math></maths><br /> can be a non-separate set, overlapping the sets <maths id="MATH-US-00011" num="11"><math overflow="scroll"><mrow><mrow><msubsup><mrow><mo>{</mo><mrow><mi>p</mi><mo>⁢</mo><msub><mo>@</mo><mrow><mn>1</mn><mo>⁢</mo><mi>i</mi></mrow></msub></mrow><mo>}</mo></mrow><mrow><mi>i</mi><mo>=</mo><mn>1</mn></mrow><mrow><mi>i</mi><mo>=</mo><mi>I</mi></mrow></msubsup><mo>⁢</mo><mstyle><mtext> </mtext></mstyle><mo>⁢</mo><mi>and</mi><mo>⁢</mo><mstyle><mtext> </mtext></mstyle><mo>⁢</mo><msubsup><mrow><mo>{</mo><mrow><mi>p</mi><mo>⁢</mo><msub><mo>@</mo><mrow><mn>2</mn><mo>⁢</mo><mi>j</mi></mrow></msub></mrow><mo>}</mo></mrow><mrow><mi>j</mi><mo>=</mo><mn>1</mn></mrow><mrow><mi>j</mi><mo>=</mo><mi>J</mi></mrow></msubsup></mrow><mo>,</mo></mrow></math></maths><br /> because the addresses of the set <maths id="MATH-US-00012" num="12"><math overflow="scroll"><msubsup><mrow><mo>{</mo><mrow><mi>p</mi><mo>⁢</mo><msub><mo>@</mo><mrow><mn>3</mn><mo>⁢</mo><mi>k</mi></mrow></msub></mrow><mo>}</mo></mrow><mrow><mi>k</mi><mo>=</mo><mn>1</mn></mrow><mrow><mi>k</mi><mo>=</mo><mi>K</mi></mrow></msubsup></math></maths><br /> can be translated into addresses <maths id="MATH-US-00013" num="13"><math overflow="scroll"><mrow><msubsup><mrow><mo>{</mo><mrow><mi>p</mi><mo>⁢</mo><msub><mo>@</mo><mrow><mn>4</mn><mo>⁢</mo><mi>l</mi></mrow></msub></mrow><mo>}</mo></mrow><mrow><mi>l</mi><mo>=</mo><mn>1</mn></mrow><mrow><mi>l</mi><mo>=</mo><mi>L</mi></mrow></msubsup><mo>.</mo></mrow></math></maths>

0175It is furthermore indicated that the set of internal temporary addresses is formed either by predetermined address values, that is, by the subset <maths id="MATH-US-00014" num="14"><math overflow="scroll"><mrow><mstyle><mtext> </mtext></mstyle><mo>⁢</mo><mrow><mrow><msubsup><mrow><mo>{</mo><mrow><mi>p</mi><mo>⁢</mo><msub><mo>@</mo><mrow><mn>2</mn><mo>⁢</mo><mi>j</mi></mrow></msub></mrow><mo>}</mo></mrow><mrow><mi>j</mi><mo>=</mo><mn>1</mn></mrow><mrow><mi>j</mi><mo>=</mo><mi>J</mi></mrow></msubsup><mo>⁢</mo><mstyle><mtext> </mtext></mstyle><mo>⁢</mo><mi>and</mi><mo>⁢</mo><mstyle><mtext> </mtext></mstyle><mo>⁢</mo><msubsup><mrow><mo>{</mo><mrow><mi>p</mi><mo>⁢</mo><msub><mo>@</mo><mrow><mn>3</mn><mo>⁢</mo><mi>k</mi></mrow></msub></mrow><mo>}</mo></mrow><mrow><mi>k</mi><mo>=</mo><mn>1</mn></mrow><mrow><mi>k</mi><mo>=</mo><mi>K</mi></mrow></msubsup></mrow><mo>,</mo></mrow></mrow></math></maths><br /> these predetermined address values possibly of course being arbitrary but contained within a specific address range determined by the network administrator or by address values calculated by translation. For example, the values of the subset <maths id="MATH-US-00015" num="15"><math overflow="scroll"><msubsup><mrow><mo>{</mo><mrow><mi>p</mi><mo>⁢</mo><msub><mo>@</mo><mrow><mn>4</mn><mo>⁢</mo><mi>l</mi></mrow></msub></mrow><mo>}</mo></mrow><mrow><mi>l</mi><mo>=</mo><mn>1</mn></mrow><mrow><mi>l</mi><mo>=</mo><mi>L</mi></mrow></msubsup></math></maths><br /> are calculated from the address values forming the abovementioned internal permanent addresses by and under the authority of the original home network and of the network administrator.

0176Regarding the external temporary address allocated to the roaming terminal in position T_pin <figref idref="DRAWINGS">FIG. 1</figref><i>c</i>, for any network connection on any site S_pnot affiliated to the original multisite organization, it is indicated that such a temporary address can, for example, be formed by an address value calculated by translation from the permanent address allocated to the roaming terminal by the separate multisite organization O_punder the authority of the administrator of the latter, but translated into a unique IP address on the INTERNET, before reaching the server S within the original multisite organization O₀, between the multisite organization O_pand the INTERNET.

0177Regarding a specific implementation of the comparison step B₁of <figref idref="DRAWINGS">FIG. 3</figref><i>a</i>, it is indicated, by way of nonlimiting example, that such an implementation can consist of a succession of steps as represented in <figref idref="DRAWINGS">FIG. 3</figref><i>b. </i>

0178In <figref idref="DRAWINGS">FIGS. 3</figref><i>a </i>and <b>3</b><i>b</i>, the location reference LR is denoted LR=P@_xywhere x designates the situation reference of the roaming terminal and y an address allocated in this situation.

0179By way of nonlimiting example, the abovementioned steps can then include, in the context of the implementation of the step B₁, a step B₁₁for testing whether the location reference belongs to the set of internal permanent addresses, a positive response to this test B₁₁making it possible to conclude, in a step B₁₂, that the value is 0 for the location discriminating information item LI, the terminal T_xbeing then connected to the original site S₁affiliated to the multisite organization O₀.

0180On the other hand, on a negative response to the test B₁₁, a new test B₁₃is invoked to compare the location reference LR to the set of internal temporary addresses as mentioned previously in the description.

0181On a positive response to the test B₁₃, the location information LI is allocated the value LI=1, the terminal T_xthus being connected to a site S_xseparate from the original site S₁but affiliated to the original multisite organization O₀.

0182On the other hand, on a negative response to the test B₁₃, then the location information LI is assigned the value 2, the roaming terminal T_xbeing connected to any site S_qnot affiliated to the original multisite organization O₀.

0183The unique extended multicast information broadcast process, from a multicast information broadcast local to an original site to a roaming workstation user affiliated to this original site, to at least one separate site hosting this roaming workstation and linked to this original site by the IP network, in accordance with the subject of the present invention, will now be described in conjunction with <figref idref="DRAWINGS">FIGS. 4</figref><i>a </i>and <b>4</b><i>b. </i>

0184Generally, it will be remembered that the local multicast information broadcast denoted LMD_1iis generated from an information broadcasting source SD dedicated to a first local multicast information broadcast address in this original site S₁.

0185With reference to <figref idref="DRAWINGS">FIG. 4</figref><i>a</i>, the local multicast information broadcast is designated LMD_1iin which the address references 1 and i represent the first local multicast information broadcast address in this original site, the reference 1 designating the address of the original site S₁and the reference i designating the address of the local multicast information broadcast concerned in the abovementioned original site. The local multicast information broadcast can be compared to the first broadcast address.

0186Also considered is a set of separate sites {S_k}, k=2 to k=N, the original site S₁and each of the sites S_kforming the multisite entity or business mentioned previously in the description.

0187Finally, consideration is given to a roaming workstation denoted T_1jk, the index 1 indicating an affiliation reference of this roaming station to the original site S₁, the reference j denoting a reference or code identifying the roaming workstation concerned, the reference k denoting the connection of the roaming workstation concerned to the separate site S_khosting the latter and the link from the roaming workstation concerned to the original site via the IP network.

0188With reference to <figref idref="DRAWINGS">FIG. 4</figref><i>a</i>, the unique extended multicast information broadcast process that is the object of the invention consists, via the interconnection of the roaming workstation to the IP network, in transmitting, in a step H₁, from the roaming workstation T_1jkto the original site S₁, an extended multicast information broadcast request message, this request message being denoted EMR (LMD_1i).

0189As indicated in the step H₁of <figref idref="DRAWINGS">FIG. 4</figref><i>a</i>, the abovementioned request message contains at least the first local multicast information broadcast address LMD_1i, forming the group multicast broadcast address GR, and a code identifying the roaming workstation from, in particular, the indices 1 and references j and k of the roaming workstation concerned T_1jk.

0190Following the identification of the roaming workstation by the original site from the information contained in the request message, the extended multicast information broadcast process consists, in a step H₂, in transmitting from the original site S₁to the roaming workstation T_1jk, a message offering access to a global multicast information broadcast, this access-offering message GMO(GMD_1g) being denoted GMO (GMD_1g) in <figref idref="DRAWINGS">FIG. 4</figref><i>a</i>. The abovementioned access-offering message includes at least one second global multicast information broadcast address GMD_1g, that is, the replacement address GR₂, the broadcasting source of which is identified in the original site.

0191With reference to <figref idref="DRAWINGS">FIG. 4</figref><i>a </i>and the step H₂in the latter, it will be understood that the second global multicast information broadcast address GMD_1gincludes the reference with the index 1 relating to the original site and the reference g to a global multicast broadcast address as defined specifically according to the RFC2365 standard mentioned previously in the description.

0192Following the receipt of the access-offering message GMO (GMD_1g) by the roaming workstation T_1jk, the extended multicast information broadcast process then consists, in a step H₃, in transmitting from the abovementioned roaming workstation to the original site S₁via the IP network, a message accepting the offer of access to the information being broadcast at the second global multicast information broadcast address.

0193In the step H₃of <figref idref="DRAWINGS">FIG. 4</figref><i>a</i>, the message accepting the offer of access is denoted AAO (GMD_1g).

0194After receipt of the message accepting the offer of access AAO (GMD_1g) on the original site S₁, the extended multicast information broadcast process includes a step H₄consisting in transferring information to be broadcast, stored at the first broadcast address and denoted for this reason ID_1i, to the second broadcast address. The information stored at the second broadcast address being denoted ID_1g.

0195By this simple operation, the information broadcast according to a local multicast information broadcast on the original site S₁can then be broadcast according to an extended multicast information broadcast via the following step H₅represented in <figref idref="DRAWINGS">FIG. 4</figref><i>a. </i>

0196The abovementioned step H₅then consists in transmitting, by global multicast broadcast, the information to be broadcast under the second address ID_1g. This enables the roaming workstation T_1jkinterconnected on the separate site to receive on the abovementioned separate site S_kinformation being broadcast under the first local broadcast address then broadcast under the second global broadcast address.

0197With reference to the same <figref idref="DRAWINGS">FIG. 4</figref><i>a</i>, it is indicated that the steps H₁, H₂and H₃represented in the latter, relating to the transmission between the roaming workstation T_1jkand the original site S₁of the extended IP multicast broadcast request message EMR (LMD_1i), of the message offering access to a global multicast broadcast GMO (GMD_1g) and of the message accepting the offer of access AAO (GMD_1g) are executed in point-to-point mode.

0198The use of this mode of transmission for the abovementioned steps is made possible by the communication of the respective addresses 1 of the original site, and k of the separate site concerned, the index j or address reference of the roaming workstation possibly then consisting of a code identifying the latter.

0199Conversely, and according to a noteworthy aspect of the method that is the object of the present invention, the step H₅for global multicast transmission is performed in point-to-multipoint mode.

0200It will be understood, in these conditions, that the process of transmitting broadcast information under the second address, the global multicast transmission in the step H₅, is then comparable to that described in conjunction with <figref idref="DRAWINGS">FIG. 1</figref><i>a </i>described previously in the description but that, however, the transmission of the information broadcast under the second global multicast broadcast address ID_1gis no longer performed locally on only the original site but also on the separate site or sites of the multisite entity.

0201A particular embodiment of the step H₄consisting in transferring the information to be broadcast from the first to the second broadcast address will now be described in conjunction with <figref idref="DRAWINGS">FIG. 4</figref><i>b. </i>

0202The abovementioned embodiment concerns the particular and nonlimiting case in which the original site S₁includes a broadcast server SD connected to the IP network via a router denoted R₁₁for example. This particular case advantageously corresponds to the situation of a multisite business for which one of the original sites S₁is provided with a broadcast server SD having a large number of clients, the use of a router in this situation being preferable.

0203With reference to <figref idref="DRAWINGS">FIG. 4</figref><i>b</i>, it is indicated that the abovementioned step H₄can then include a step H₄₁for the local multicast broadcast, of information to be broadcast stored at the first address LMD_1iof the broadcast server, to the router R₁₁.

0204The abovementioned step H₄₁is followed by a step H₄₂consisting of a step for redirecting the information to be broadcast ID_1iby substituting the second global multicast broadcast address GMD_1gor GR₂for the first local broadcast address LMD_1iforming the group multicast broadcast address GR. It will be understood, in particular, that this redirection step H₄₂can simply consist in allocating the locally broadcast information ID_1ithe second global multicast broadcast address to in fact generate the data stored at the second broadcast address, denoting ID_1g.

0205It will be understood, in particular, that the abovementioned redirection step can simply consist in associating with the stored data supporting the information to be broadcast, stored on the router R₁₁, a simple data structure comprising the first and second addresses, the data structure possibly simply consisting of a list with at least the first and the second abovementioned addresses or any equivalent data structure.

0206Given the method of the extended multicast broadcast process as described in <figref idref="DRAWINGS">FIGS. 4</figref><i>a </i>and <b>4</b><i>b</i>, it is indicated that, for a plurality of extended multicast broadcast request messages, relating to one and the same first local multicast broadcast address, emanating from a plurality of roaming workstations affiliated to the original site and each interconnected to the IP network on a different separate site, the step H₅consisting in transmitting by global multicast broadcast the information to be broadcast under the second address then allows for the creation of a global multicast broadcast tree, the root element of which is formed by one of the routers common to the broadcast branches that make up the abovementioned global multicast broadcast tree.

0207However, a specific embodiment of the extended multicast broadcast process can be envisaged, this embodiment appearing particularly advantageous for a coherent management of the local, or global, multicast information broadcasting types, and of the memory space ultimately occupied to this end, both on the broadcast server SD and on the router R₁₁.

0208According to the abovementioned particularly advantageous embodiment, the second global multicast broadcast address GMD_1gcan be maintained and validated for a permanent local multicast information broadcast LMD_1iat the first address. The concept of permanent information broadcast is extended to maintaining the global address as long as there are external subscribers.

0209In these conditions, it will be understood that, to permanently maintain and validate the second global multicast information broadcast address GMD_1g, the data structure, such as a list [LMD_1i, GM_1g], is stored and secured permanently on the router, the first and second addresses thus being mapped on a one-to-one basis permanently.

0210In these conditions, the step H₄consisting in transferring information to be broadcast from the first to the second broadcast address can then be eliminated for any extended multicast broadcast request message to this second address, subsequent to the first extended IP multicast broadcast request message to the abovementioned second address.

0211It will be understood, in particular, that the idea of eliminating the step H₄simply concerns eliminating the physical transfer of the data stored at the first address to the second address, in which case this physical transfer can possibly then simply be replaced by calling the second global multicast information broadcast address from the permanent data structure mentioned previously.

0212For a more detailed description of the unique process for discriminating the connection site in relation to the original site and/or original multisite organization, or of the unique extended global multicast broadcast process, it may be useful to refer to the French patent applications FR 03 09873 and FR 03 12688 filed previously, respectively on Aug. 12, 2003 and Oct. 29, 2003, in the name of the applicant.

0213A more detailed description of a system of multicast broadcasting to a roaming terminal according to the location of the IP network connection of this terminal, in accordance with the subject of the present invention, will now be given in conjunction with <figref idref="DRAWINGS">FIG. 5</figref>.

0214In <figref idref="DRAWINGS">FIG. 5</figref>, the same notations designate the same elements as in the preceding figures.

0215As is shown in the abovementioned <figref idref="DRAWINGS">FIG. 5</figref>, the system that is the subject of the invention comprises, at least on the original site S₁, a module for discriminating the location of the roaming terminal T_xwith x=1, 2, 3, p in <figref idref="DRAWINGS">FIG. 5</figref> with respect to its original site S₁and/or its original organization O₀, from the signaling message as described previously in the description in conjunction with <figref idref="DRAWINGS">FIG. 2</figref><i>a. </i>

0216In <figref idref="DRAWINGS">FIG. 5</figref>, the discrimination module bears the reference HA and can be installed on the server S associated with the original home network of the roaming terminal concerned.

0217Of course, the system that is the object of the invention also includes a transmission module installed on the original site S₁, this transmission module being used to handle the transmission to the roaming terminal T_xof an information location discriminating information item LI described previously in the description.

0218The transmission module is not represented explicitly in <figref idref="DRAWINGS">FIG. 5</figref> because the server S is, of course, conventionally provided with any module for transmitting messages to the terminals, in particular the roaming terminals, under its responsibility.

0219Finally, the system that is the subject of the invention includes, on the roaming terminal referenced T_xand regardless of the position of the latter x=1, 2, 3, p, and for any request to access a group multicast broadcast intended for the original site S₁and relating to a multicast broadcast local to the original site, or to the original organization S₁, O₀of this roaming terminal, a module for replacing this access request with a request to access an extended multicast broadcast, allowing access to the abovementioned local multicast broadcast, when the location discriminating information item LI of the roaming terminal concerned designates a connection of the latter outside its original site S₁or its original organization O₀.

0220In <figref idref="DRAWINGS">FIG. 5</figref>, the replacement module is denoted TA, this module, of course, being installed on the roaming terminal regardless of the connection position of the latter.

0221With regard to the discrimination module HA installed on the server S of the original site S₁, it is indicated that this discrimination module advantageously includes a database module including a first set of internal permanent addresses allocated by the original home network or the original site S₁to the set of roaming terminals attached to this original home network, and a second set of internal temporary addresses likely to be allocated to the set of roaming terminals for any connection to another site affiliated to this original organization. The abovementioned sets are, of course, represented in <figref idref="DRAWINGS">FIG. 3</figref><i>a. </i>

0222The discrimination module further includes a comparison module for identifying the location reference LR with the address values of at least one of the first and second abovementioned sets, that is, with the internal permanent, or internal temporary, addresses mentioned previously.

0223The transmission module can then be used to transmit from the original home network to the roaming terminal, a signaling acknowledgement message containing the location discriminating information item LI. This information item designates either the connection of the roaming terminal concerned T_xon its original home network or its original home site S₁on identification of the location reference LR in the first set of internal permanent addresses, or the network connection of the roaming terminal T_xon another site affiliated to the original multisite organization, the sites S₂or S₃in <figref idref="DRAWINGS">FIG. 5</figref>, on identification of the location reference in the second set of internal temporary addresses, or even the network connection of the roaming terminal on any site with the terminal in position T_pwhen this site S_pis not affiliated to the original multisite organization in the absence of identification of the location reference in one or other of the first and second sets of internal permanent, or internal temporary, addresses, mentioned previously.

0224<figref idref="DRAWINGS">FIG. 5</figref> thus shows the roaming terminal T_xin the position of connection on its original site S₁, the location information LI being equal to 0 in the example mentioned previously in the description, the roaming terminal connected to the site S₂or the site S₃separate from the original site S₁, but affiliated to the original organization O₀, the location information LI having the value 1 in this situation and, finally, the roaming terminal connected to any site S_paffiliated to any organization O_pseparate from the original organization O₀, the location information LI in this situation having the value 2 as mentioned previously in the description.

0225Of course, and in a particularly advantageous and nonlimiting manner, the module for discriminating the location of the roaming terminal concerned, the module denoted HA in <figref idref="DRAWINGS">FIG. 5</figref>, is formed by a software agent installed on the original site S₁of the roaming terminal. It can in particular be installed on the server S mentioned previously.

0226Similarly, with regard to the module for replacing the access request formulated by the roaming terminal T_x, it is indicated that this replacement module denoted TA advantageously includes a module for discriminating the class of the multicast broadcast address requested with respect to the multicast broadcast classes that are global, or local, to the original site and/or organization S₁and O₀of the roaming terminal concerned.

0227It also includes a module for discriminating the value of the location discriminating information item LI that the roaming terminal has after connection and transmission by the server S installed on the original site S₁to which the roaming terminal concerned is attached.

0228The module for discriminating the class of the multicast broadcast address requested with respect to the global and/or local multicast broadcast classes and the module for discriminating the value of the location discriminating information item of this roaming terminal are advantageously formed by a software agent denoted TA and associated with the roaming terminal concerned, this software agent being installed on the abovementioned roaming terminal and, of course, executable by the latter.

0229The process of execution by the software agent TA concerned corresponds to that described in conjunction with <figref idref="DRAWINGS">FIGS. 3</figref><i>a </i>and <b>3</b><i>b. </i>

0230Finally, it is indicated that the method and system of multicast broadcasting to a roaming terminal according to the location and IP network connection of the latter according to the object of the present invention are advantageously implemented from a software product stored on a storage medium, this software product being, of course, executed by a computer.

0231The software product is used to install and run the software agent HA on the server S of the original site S₁and, in particular, the set of operations and steps represented in <figref idref="DRAWINGS">FIGS. 2</figref><i>a</i>, <b>3</b><i>a </i>and <b>3</b><i>b </i>previously described in the description.

0232The method and system that are the object of the present invention are also advantageously implemented from a software product for installing and executing the software agent TA installed on each roaming terminal in accordance with the execution process as represented in <figref idref="DRAWINGS">FIGS. 2</figref><i>a</i>, <b>2</b><i>b </i>and <b>4</b><i>a</i>, <b>4</b><i>b</i>, described previously in the description.