Map-t autonomous migration to 1:1 sharing ratio

Abstract

Method for managing addresses in a communication network, the communication network comprising first network devices (20), each first network device (20) configured to interface one or more user devices (10) with the communication network. The method comprises the step of sharing (S1), between said first network devices (20), a network address, accessible from the communication network via address-port mapping information configured in said first network devices (20) and indicating a mapping between said network address and a respective number of ports corresponding to each of said first network devices (20). In accordance with a configuration change of connection (S2) to the communication network of a first user device (10) comprised in said one or more user devices (10), in which said first user device (10) interfaces with a respective first network device (20) of said first network devices (20), the method envisages the step of providing (S3), in response to at least one of the first notification (N1) and a second notification (N2), a third notification (N3) to the first network device (20) allocating an individual network address to said respective first network device (20). The first notification (N1) and the second notification (N2) include information related to the configuration change, wherein said first notification (N1) and said second notification (N2) are different.

Description

[0001] MAP-T autonomous migration to 1 : 1 sharing ratio

[0002] ★ ★ ★ ★ ★ ★ ★

[0003] FIELD OF THE INVENTION

[0004] The present invention concerns a method for managing addresses in a communication network .

[0005] BACKGROUND OF THE INVENTION

[0006] The IPv4 and IPv6 protocols are known in the communication via the Internet . The IPv4 protocol allows to create a limited number of IP addresses . The number of IPv4-type IP addresses available may not meet the demand . Although the IPv6 technology allows to have a much greater number of IP addresses , many applications and many users still need to use IPv4 technology, for example for compatibility reasons . For this reason it is not possible to completely abandon the IPv4 technology and it is necessary to be able to translate IPv4 messages into IPv6 and vice versa . This translation function is available , for example , through MAP-T (Mapping Address and Port using Translation) technology, which allows to translate and interpret messages from IPv4 to IPv6 and vice versa .

[0007] MAP-T also allows sharing IPv4 addresses between multiple routers . For example , a MAP border relay may communicate with a number of routers ( e . g . 16 routers ) the same IPv4 address with the ef fect that , from the outside , each of these routers appears as the same device . The MAP border relay can however identi fy the recipient router of a packet from the ports it has allocated to that router for communication, thus enabling proper communication . Each individual router ( for example , a router associated with a user, or customer premise equipment ) , internally to its local network, serves one or more user devices . The user devices are not individually identi fiable from outside the local network, which sometimes makes it impossible to deliver a dedicated service to a single user device or to a speci fic application of a single user device .

[0008] SUMMARY OF THE INVENTION

[0009] The obj ect of the present invention is to overcome the problem of guaranteeing the operation of a service dedicated to a single user device or to a specific application of a single user device in a safe and reliable manner in the context of technologies such as MAP-T technology .

[0010] Some aspects of the invention may be described as follows :

[0011] Al . Method for managing addresses in a communication network, the communication network comprising first network devices ( 20 ) , each first network device (20 ) configured to interface one or more user devices (10) with the communication network, the method comprising the steps of: sharing (SI) , between said first network devices (20) , a network address, accessible from the communication network via address-port mapping information configured in said first network devices (20) and indicating a mapping between said network address and a respective number of ports corresponding to each of said first network devices (20) ; in accordance with a configuration change of connection (S2) to the communication network of a first user device (10) comprised in said one or more user devices (10) , in which said first user device (10) interfaces with a respective first network device (20) of said first network devices (20) :

[0012] - providing (S3) , in response to at least one of the first notification (Nl) and a second notification (N2) , a third notification (N3) to the first network device (20) allocating an individual network address to said respective first network device (20) , wherein the first notification (Nl) and the second notification (N2) include information related to the configuration change, wherein said first notification (Nl) and said second notification (N2) are different.

[0013] A2. Method according to aspect Al, wherein the second notification (N2) is received even if the first notification (Nl) has not been received.

[0014] A3. Method for managing addresses in a communication network, the communication network comprising first network devices, each first network device (20) configured to interface one or more user devices (10) with the communication network, the method comprising the steps of: sharing, between said first network devices, a network address, accessible from the communication network via address-port mapping information configured in said first network devices and indicating a mapping between said network address and a respective number of ports corresponding to each of said first network devices; in accordance with a configuration change of connection to the communication network of a first user device comprised in said one or more user devices, in which said first user device interfaces with a respective first network device of said first network devices (20) :

[0015] - providing a first notification (Nl) , to a second network device, the first notification (Nl) including information related to the configuration change;

[0016] - providing a second notification (N2) to the second network device, the second notification (N2) including information related to the configuration change, wherein said first notification (Nl) and said second notification (N2) are different; providing, in response to at least one of the first notification (Nl) and second notification (N2) , a third notification to the first network device (20) , the third notification allocating an individual network address to said respective first network device (20) .

[0017] A4. Method according to one of the preceding aspects, wherein the first notification (Nl) is a notification generated in response to the configuration change, preferably a real-time notification . A5. Method according to one of the preceding aspects, wherein the second notification (N2) is an aperiodic or asynchronous notification relative to the configuration change, preferably a notification including telemetry information.

[0018] A6. Method according to one of the preceding aspects, wherein the configuration change of connection of said first user device (10) is not a change in the address-port mapping configuration configured in said first network devices (20) towards respective user devices (10) .

[0019] A7. Method according to one of the preceding aspects, wherein the third notification (N3) includes information for changing the address-port mapping configuration in said first network devices (20) .

[0020] A8. Method according to one of the preceding aspects, further comprising the steps of: determining that the individual network address should no longer be allocated to the respective first network device (20) ; in accordance with a fourth notification (N4) provided to said respective first network device (20) , sharing the network address between said first network devices (20) .

[0021] A9. Method according to aspect A8, wherein the determination is based on at least one of: a determination of whether said respective first network device

[0022] (20) requires an individual network address, based on information relating to the configuration of connection of said one or more user devices (10) to said respective first network device (20) that is provided recurringly; and a determination that a predetermined period of time has elapsed since the provision of said third notification (N3) to said respective first network device (20) .

[0023] A10. Method according to one of the preceding aspects, wherein the first notification (Nl) and / or the second notification (N2) indicates at least one of:

[0024] - a port activation for the first user device (10) ;

[0025] - a port transfer for the first user device (10) ; and

[0026] - an indication that the first user device (10) and / or a port of the first user device (10) is made accessible to the network .

[0027] All. Method according to one of the preceding aspects, further comprising the step of: in accordance with an instruction from a network controller, providing to said respective first network device (20) , a fourth notification (N4) allocating the individual network address to said respective first network device (20) .

[0028] A12. Method according to aspect All, wherein the instruction overrides any determination that the individual network address should no longer be allocated to the respective first network device (20) .

[0029] A13. Method according to one of the preceding aspects, further comprising the step of: entering, in an address allocation engine (40) running on a node from the network, information from the first notification (Nl) and from the second notification (N2) , wherein the engine (40) uses a number of predetermined rules to determine whether an individual network address should be allocated to the respective first network device (20) .

[0030] A14. Method according to aspect A13, further comprising the steps of: generating a new rule for the address allocation engine (40) , based on information by looking at the address and port mapping in said first network devices (20) ; and updating the address allocation engine (40) to use the new rule .

[0031] A15. Network device (40) comprising: management means (401) for network addresses configured to manage a network address shared between one or more other network devices (20, 20' ) each configured to interface one or more respective user devices (10-1 ... 10-N; , 10-1'... 10-N ' ) , wherein said network address is accessible from the communication network via address-port mapping information configured in said one or more other network devices (20, 20' ) and indicating a mapping between said network address and a respective number of ports corresponding to each of said one or more other network devices (20, 20' ) ; transmission means (402) configured to transmit, in accordance with a configuration change of connection to the communication network of a first user device (10) interfacing with a respective first other network device (20) comprised in said one or more other user devices (10-1 ... 10-N) and in response to at least one of a first notification (Nl) and a second notification (N2) , a third notification (N3) to said first other network device (20) , the third notification allocating an individual network address to said respective first other network device (20) , wherein the first notification (Nl) includes information related to the configuration change and the second notification (N2) includes information related to the configuration change, wherein said first notification (Nl) and said second notification (N2) are different.

[0032] A16. Network device (40) according to aspect A15, wherein said network device (40) further comprises reception means configured to receive the first notification (Nl) and the second notification (N2) , wherein the configuration means is configured to receive the second notification (N2) even if the first notification (Nl) has not been received.

[0033] A17. Network device (40) according to one of aspects A15 or A16, wherein the first notification (Nl) is a notification generated in response to the configuration change, preferably a real-time notification.

[0034] A18. Network device (40) according to one of the aspects from AA17, wherein the second notification (N2) is an aperiodic or asynchronous notification relative to the configuration change, preferably a notification including telemetry information .

[0035] A19. Network device (40) according to one of aspects A15 to A18, wherein the configuration change of connection of said first user device (10) is not a change in the address-port mapping configuration configured in said first network devices

[0036] (20) towards respective user devices (10) .

[0037] A20. Network device (40) according to one of aspects A15 to A19, wherein the third notification (N3) includes information for changing the address-port mapping configuration in said first network devices (20) .

[0038] A21. Network device (40) according to one of aspects A15 to A20, further comprising: determination means configured to determine that the individual network address should no longer be allocated to the respective first network device (20) ; wherein the network device (20) is configured to, in accordance with a fourth notification (N4) provided to said respective first network device (20) , share the network address between said first network devices (20) .

[0039] A22. Network device (40) according to one of aspects A15 to A21, wherein the determination is based on at least one of: a determination of whether said respective first network device (20) requires an individual network address, based on information relating to the configuration of connection of said one or more user devices (10) to said respective first network device (20) that is provided recurringly; and a determination that a predetermined period of time has elapsed since the provision of said third notification (N3) to said respective first network device (20) . A23. Network device (40) according to one of aspects A15-A22, wherein the first notification (Nl) and / or the second notification (N2) indicates at least one of:

[0040] - a port activation for the first user device (10) ;

[0041] - a port transfer for the first user device (10) ; and

[0042] - an indication that the first user device (10) and / or a port of the first user device (10) is made accessible to the network .

[0043] A24. Network device (40) according to one of aspects A15-A23, wherein, in accordance with an instruction from a network controller (100) , a fourth notification (N4) is provided to said respective first network device (20) allocating the individual network address to said respective first network device (20) .

[0044] A25. Network device (40) according to aspect A24, wherein the instruction overrides any determination that the individual network address should no longer be allocated to the respective first network device (20) .

[0045] A26. Device configured to function as a node of a network executing the method according to aspect Al or A2, or any of aspects A4-A14 when dependent on aspect Al or A2, wherein, the device is configured to run the address allocation engine (40) , and the address allocation engine (40) determines whether an individual network address should be allocated to a user device (10) . A27 . Device configured to function as a node of a communication network executing the method according to aspect A3 or any aspect from A4-A14 when dependent on aspect A3 .

[0046] A28 . Computer program comprising instructions configured to implement , when said program is executed on one or more processors , all steps according to any one of aspects Al to Al 4 .

[0047] LIST OF FIGURES

[0048] Fig . 1 depicts a router 20 to which some user devices 10 are connected .

[0049] Fig . 2 depicts a 16 router 20 connected to a MAP border relay 30 .

[0050] Fig . 3A depicts a connection where the router 20 receives and transmits according to the IPv6 protocol .

[0051] Fig . 3B depicts a connection where the router 20 converts from the IPv6 protocol to the IPv4 protocol .

[0052] Fig . 4 depicts a MAP border relay 30 that communicates with two routers 20 using the IPv6 protocol , although it receives from the network via the IPv4 protocol .

[0053] Fig . 5 depicts an exchange of noti fications .

[0054] Fig . 6 depicts a flow diagram of a method according to an embodiment of the present invention .

[0055] Fig . 7A depicts a block diagram of a network device according to an embodiment of the present invention .

[0056] Fig . 7B depicts a block diagram of a system according to an embodiment of the present invention . Fig . 8 illustrates a block diagram of a computer adapted to run a program according to an embodiment of the present invention;

[0057] DETAILED DESCRIPTION

[0058] Configuration of the local network

[0059] As can be seen in Fig . 1 , a router 20 , representing an example of and hereinafter also called first network device or CPE ( customer premise equipment ) , is a device that is interposed between a network operator ( internet provider, cloud) and one or more user devices 10 functioning within a local ( e . g . home ) network created by the router 20 . The home network is for example a Wi-Fi network . The user devices 10 can be for example smartphones , computers , tablets , appliances connected to the wireless network such as a dishwasher, an oven, a heating unit , a gaming station, or any other device capable of being connected to a communication network such as the internet .

[0060] In managing IP addresses (network address ) of a router 20 , a network operator allocates to the router 20 an IP address representing it when it is reached from outside the home network . In other words , each user device 10 of the home network is reachable using the IP address allocated to the router 20 . The router 20 , however, creates a series of IP addresses internal to the local network in order to reach the individual user devices 10 . This series of IP addresses is for internal use , in the sense that the addresses are not identi fiable from outside the network . Diversi fication within the home network takes place via an address-port mapping configured in the router 20 , which indicates a mapping between the IP address and a respective number of ports corresponding to each router 20 .

[0061] Sharing IPv4 addresses

[0062] However, in order to reduce the total number of IPv4 addresses used by an internet provider 50 , it is also possible that the IPv4 address allocated to a router 20 is not unique , but shared with other routers 20 . In this case , as can be seen in Fig . 2 , for example , N routers 20 ( 20_l , 20_2 , ..., 20_16 ) may share the same IPv4 address . The figure depicts the case where N=16 . N could also take on other values , for example N=32 routers per mobile devices . This sharing is administered by a device called MAP border relay that stands between the internet provider 50 ( for example the cloud) and the routers 20 . The MAP border relay 30 receives services and data (packets ) from the internet provider 50 and trans fers them to the routers 20 . Although the example of an IPv4 address as a network address has been made whose availability is limited or could be subj ect to technical restrictions to the available number, the same applies to any type of allocatable address that is subj ect to limitations , and not necessarily only to the IPv4 addresses .

[0063] Exchanges between IPv4 and IPv6 Protocols

[0064] As can be seen in Fig . 3A, i f the internet service is provided via the IPv6 protocol and a user device 10 requests an IPv6 protocol from the router 20 , the transmission of the service (packet transmission) takes place directly using the IPv6 protocol .

[0065] As can be seen in Fig . 3B, i f instead the internet service is provided via the IPv6 protocol and a user device 10 requests an IPv4 protocol from the router 20 , the router 20 translates the IPv6 protocol into IPv4 .

[0066] As can be seen in Fig . 4 , i f the internet service is provided via the IPv4 protocol , the MAP border relay 30 translates the service from IPv4 to IPv6 and trans fers it to the router 20 in the IPv6 format ( in case the router 20 supports IPv6 towards the MAP border relay) . The router 20 is then able to provide the same service to a user device 10 in the IPv6 format , or to reconvert it into IPv4 depending on the needs of one or more user devices 10 . This ensures uni formity in the communications between the MAP border relay 30 to the routers 20 .

[0067] Unique IPv4 Address

[0068] Although, as discussed above , it is possible for one router 20 to share the same IPv4 address with 15 other routers 20 , there are applications of a user device 10 that require the router 20 to be uniquely identi fied . In other words , there are cases in which sharing a same IPv4 address ( allocated to a determined router 20 ) between user devices 10 ( connected to the determined router 20 ) is acceptable for a part of the user devices 10 , but disadvantageous for one or more of the user devices 10 . For example , one or more user devices 10 need to be uniquely identi fied by a service of the internet provider 50 ( or generally by a device or service provided by a device accessible via the provider 50 ) . Although in the following reference will be made for simplicity of exposition to a user device 10 alone having this need, the same must be considered applicable to more than one user device 10 connected to a router 20 . Switching to a unique address

[0069] In this case , a unique IPv4 address can be allocated to a router 20 . This can be achieved by stopping sharing the shared IPv4 address . This procedure of switching to a unique address is a configuration change of connection to the communication network of the router 20 interfacing with the user device 10 that needs to be uniquely identi fied from the outside ( or another configuration change incompatible with the sharing of the address between the router 20 and other routers , for example i f the user device 10 requires the use of speci fic ports ) . In other words , given a user device 10 connected to a determined router 20 , in which the user device 10 needs to be uniquely addressed from the outside , the sharing of the IP address of the determined router 20 with other routers 20 is stopped; an address ( e . g . IPv4 ) that is not shared with other routers 20 is allocated to said determined router 20 . The configuration change of connection to the router 20 is not a change in the mapping configuration between the IP address and the number of ports corresponding to the router 20 to which the user device 10 is connected . In other words , it is not a conversion of addresses made by the CPE using e . g . a NAT conversion table . In other words , it is not a configuration change internal to the local network of the router 20 with the terminals 10 connected thereto , but rather a configuration change of the address allocated to the router 20 so that it can communicate with devices external to the local network .

[0070] Switching to a unique address may occur as a result of a need from a user device . Speci fically, for example , the internet provider 50 may receive information about a configuration change of connection of a user device 10 . This time , this is a configuration change internal to the local network of the router 20.

[0071] In one example, the configuration change of connection of the user device 10 may be transmitted to the internet provider 50 via an app on the user device 10. In another example, the information about the configuration change may be generated by the router 20, for example via a user interface (GUI, graphical user interface) , and transmitted to the internet provider 50. In another example, the information about the configuration change may be generated by a network operator (controller) 100. The examples can be combined.

[0072] The information about the configuration change of connection of the user device 10 that results when switching to a unique address is sent (by the router 20 or via the app) in two notifications N1 and N2, as illustrated in Fig. 5.

[0073] Address allocation engine

[0074] The decision whether to grant to a user device 10 (i.e., to the router 20 to which the user device is connected) to switch to a unique address is made by a device called address allocation engine (hereinafter, also rule engine) . The address allocation engine 40 may be located on a node of the network.

[0075] The first notification N1 is sent in response to the request for configuration change of connection to the communication network of the user device 10. In other words, the request for configuration change is the trigger that generates and / or causes the transmission of the first notification N1. The first notification N1 is preferably sent in real time, but it is also possible to predetermine a delay for sending it. The first notification N1 includes information related to the configuration change. The first notification N1 may be sent from the router 20 to the address allocation engine 40. Alternatively, the first notification N1 may be sent by an app used by the user directly to the address allocation engine 40.

[0076] The second notification N2 (including information related to the configuration change) , unlike the first notification Nl, is not triggered by the request for configuration change, i.e. it is generated and / or transmitted regardless of the time instant in which the request for configuration change is detected or occurs. The second notification N2 may be sent by the router 20 to the address allocation engine 40 for the first time after a predetermined time since the configuration change or at the first chance of connection of the router 20 to the address allocation engine 40. The predetermined time may for example be of 10, 15 or 20 minutes. Alternatively, the second notification N2 is asynchronous relative to the configuration change. Preferably, the second notification N2 is repeated periodically at predetermined intervals. Alternatively, the second notification N2 is aperiodic. The second notification N2 can be a notification message including other information, or originally conceived to transmit other information (such as "telemetry" information) and to which message information related to the configuration change is added. The second notification N2 may then be a notification including telemetry information. The second notification N2 preferably includes the same information related to the configuration change as included in the first notification. The second notification N2 is however different from the first notification Nl : for example, the second notification N2 may preferably exploit the transmission of an already existing message and does not require the creation of a specific message, so as not to significantly affect the traffic of data exchanged in the network. However, although it is preferable to add the information related to the configuration change to an already existing message, it is possible to conceive the second notification N2 as a new message including the information related to the configuration change and sent with a timing independent of the time instant in which the configuration change occurs. For example, the first notification N1 may be in real-time (or near real-time) while the second notification N2 is sent at a time instant independent of the time instant in which the first notification is sent. The second notification N2 acts as a back-up in case the first notification N1 does not reach its destination.

[0077] A technical advantage of the dual notification system is to have a standby notification system so that, even if the first notification N1 should not arrive at its destination (for example due to a malfunction on the device transmitting it, and / or an error on the transmission channel, and / or an error on the side of the device receiving it) , the request for the allocation of a unique IP address can still reach the address allocation engine 40. This ensures safety and reliability.

[0078] In other words, in the example where the configuration change is applied via the router 20 (e.g., via a GUI of the router 20) , the router 20 is configured to transmit both the first notification N1 and the second notification N2. In fact, errors may occur in the transmission and / or generation of the message Nl, due to which the respective notification (for example the first notification Nl) is not received by the devices configured for configuration change. In this case, the configuration change information may be received via the second notification. In another example, a user makes a configuration change (or a request for configuration change) via an app; in that case, the notification messages may be generated and transmitted by the app or by a network device connected to that app (e.g. a server in communication with said app and / or running said app) .

[0079] The first notification Nl and / or the second notification N2 indicates at least one of the following events: port activation for the first user device 10; port transfer for the first user device 10; an indication that the first user device 10 and / or a port of the first user device 10 is made network accessible .

[0080] The decision on switching to a unique address can be made automatically or manually.

[0081] The decision on switching to a unique address of a user device 10 made automatically by the address allocation engine 40 depends on the occurrence of one or more predetermined triggers (rules, conditions) . The triggers that may cause the user device 10 to switch to a unique address may comprise one or more of the following conditions (which are illustrative, as other conditions may also apply) : a ) activation of a DMZ ( demilitari zed zone ) . The DMZ is a sub-network visible from the outside via an application upon request from a user of the router 20 ; b ) a port forwarding rule ; c ) Port Triggering - activatable from a GUI of the router 20 ; d) UPnP - activatable from a graphic user interface of the router 20 , for example in the case of streaming video games .

[0082] However, a new trigger may be generated by an automation engine based on information regarding the address and port mapping in the routers 20 . For example , an Al (Arti ficial Intelligence ) that receives the first noti fications N1 and the second noti fications N2 as input and returns a binary response about the need to switch to a unique address can be trained to create a new trigger .

[0083] After the new trigger is generated, the address allocation engine 40 is updated to use the new trigger ( rule ) .

[0084] In this example , the address allocation engine 40 communicates the decision about the switch to a unique address to the internet provider 50 , which informs the router 20 and the MAP border relay 30 . The router 20 is informed about the decision to switch to a unique address via a third noti fication N3 in response to at least one of the first and second noti fication . With the third noti fication N3 , an individual IP address is allocated to the user device 10 that has obtained to switch to a unique address . The third noti fication N3 may include information for changing the address-port mapping configuration in the corresponding router 20 . The decision on switching to a unique address made manually may be a setting that is entered by a network operator ( controller ) 100 by manually setting a management parameter o f the router 20 for which a unique IP address is desired via a fourth noti fication N4 . In case of switching to a manual unique address , the address allocation engine 40 merely registers the new setting of the concerned router 20 .

[0085] Abandoning the unique address

[0086] After switching to a unique address of a user device 10 , the internet provider 50 may determine that the individual network address allocated to the user device 10 that obtained to switch to a unique address should no longer be allocated to the respective router 20 . Further, following this determination, the internet provider 50 may again share the individual network address allocated to the user device 10 between the routers 20 . This allows the exclusive IP address to be reused when the need to use it exclusively no longer exists , and consists in abandoning the unique address . The determination by the internet provider 50 may be based on at least one of the following findings :

[0087] - a predetermined period of time has elapsed since the transmission of the third noti fication N3 to the router 20 ;

[0088] - the configuration of connection of the user devices 10 to the respective router 20 has changed;

[0089] - the configuration of connection of the user devices 10 to the respective router 20 is provided recurringly;

[0090] - it is necessary to start a maintenance procedure . I f the internet provider 50 has established to abandon the unique address for a determined user device 10 connected to a respective router 20 , the internet provider 50 informs the router 20 and the MAP border relay 30 about the new configuration .

[0091] In case of manual setting of the router 20 to allocate a unique IP address , the instruction of the operator ( controller ) 100 may override any determination that the individual network address should no longer be allocated to the respective first network device 20 . In other words , this allocation can take ( or be set to take ) precedence over a possible abandonment of the unique address .

[0092] Fig . 6 shows a block diagram illustrating a method according to an embodiment of the present invention as described above . A method for managing addresses in a communication network, wherein the communication network comprises first network devices 20 and each first network device 20 is configured to interface one or more user devices 10 with the communication network . The method comprises a step of sharing ( step S I ) , between first network devices 20 , a network address , accessible from the communication network via address-port mapping information configured in said first network devices 20 and indicating a mapping between said network address and a respective number of ports corresponding to each of said first network devices 20 In accordance with a configuration change of connection ( step S2 ) to the communication network of a first user device 10 comprised in said one or more user devices 10 , in which said first user device 10 interfaces with a respective first network device 20 of said first network devices 20, the method comprises a step of providing (step S3) , in response to receiving at least one of the first notification N1 and the second notification N2 (see dashed arrows in Fig. 6) , a third notification N3 to the first network device 20 allocating an individual network address to said respective first network device 20; the first notification N1 and the second notification N2 include information related to the configuration change. However, the first notification N1 and the second notification N2 are different as explained above. Optionally, the method may comprise a step of receiving the first notification N1 and a step of receiving the second notification N2. However, in view of what has said above, the case may happen, in which, despite of the device being configured to receive the first notification Nl, the first notification Nl is not received. In this case, receiving the second notification N2 will ensure that the information related to the configuration change is received. In other words, in case of malfunctions and / or transmission errors that prevent the notification Nl from being received, the device can still receive the information about the configuration change via the second notification N2.

[0093] Fig. 7A shows a device 40 according to another embodiment, in particular a device 40 configured to function as a node of a network configured to perform the respective steps of the method described above. The device 40 may be configured to operate in a system as depicted for example in Fig. 7B. In particular, the device 40 is capable of interfacing one or more user devices 20, 20' with a communication network such as the Internet. Devices 20 and 20' (also referred to as other network device 20, 20' ) , each configured to interface respective one or more user devices (10-1 ... 10-N, 10-1' ...10-N' ) with a communication network such as the Internet, are depicted in the system of Fig. 7B. The device 40 depicted in Fig. 7B is an example of an address allocation engine as set forth further above. For example, the device 40 may determine whether an individual network address (see dashed line) should be allocated to a specific device 20 that interfaces with a respective user 10. Returning to Fig. 7A, the network device (40) is configured to interface one or more devices (10) with a communication network, wherein said network device comprises management means 401 and transmission means 402. The device 40 may be referred to as an address management device for simplicity's sake; each of the other network devices 20, 20' may be referred to as a user network device (representing the fact that it interfaces with one or more user devices) . The management means (401) may be management means for network addresses configured to manage a network address shared between one or more other network devices (20, 20' ) , wherein each of said devices 20, 20' is configured to interface one or more respective user devices (10-1 ... 10-N; 10-1' ...10-N' ) . This network address is accessible from the communication network via address-port mapping information configured in said one or more other network devices (20, 20' ) and indicating a mapping between said network address and a respective number of ports corresponding to each of said one or more other network devices (20, 20' ) . The transmission means (402) are configured to transmit, in accordance with a configuration change of connection to the communication network of a first user device (10) interfacing with a respective first other network device (20) comprised in said one or more other user devices (10-1 . . . 10-N) and in response to at least one of a first notification (Nl) and a second notification (N2) , a third notification (N3) to said first other network device (20) . The third notification allocates an individual network address to said respective first other network device (20) . The first notification (Nl) includes information related to the configuration change and the second notification (N2) includes information related to the configuration change, wherein said first notification (Nl) and said second notification (N2) are different as explained above. In other words, in accordance with a request for configuration change for a certain user device 10 (10-1 ... 10-N, 10-1' ... 10-N' ) , the device 40 sends a third notification to the network device 20, 20' which interfaces with the device 10 for which the configuration change is applied. The third notification N3 is sent in response to the second notification Nl and / or to the second notification N2. In particular, the third notification is sent in response to the second notification N2 even if the first notification is not received.

[0094] Preferably, the device 40 can be configured to receive both the first notification and the second notification, which is to be understood as meaning that the device 40 can only receive the second notification in the event that the first notification is not received due to, for example, errors in the transmission or generation of the first notification.

[0095] It should be noted that, in one example, the device 40 may be implemented in a single network device (via a hardware and / or software implementation) . In another example, the device 40 may be implemented in a distributed manner, i.e., wherein the hardware and / or software implementation is distributed; for example, the described functionalities may be implemented via a hardware and / or software combination on several distinct network equipment and interacting to implement such functionalities .

[0096] Figure 8 illustrates a block diagram exempli fying a computer ( 500 ) capable of executing the aforesaid program . In particular, the computer ( 500 ) comprises a memory ( 530 ) for storing the instructions of the program and / or the data necessary for the execution thereof , a processor ( 520 ) for executing the instructions themselves and an input / output interface ( 510 ) . In particular, figure 8 is illustrative and non-limiting, since the computer can in fact be constructed either in such a manner as to be concentrated in one device , or in manner such as to be distributed over a number of interconnected devices . Therefore, the program can be executed locally on a concentrated ( localised) or distributed device . According to a further embodiment, there is provided a medium for supporting a computer program configured to implement , when the program is executed on a computer, one or a combination of the steps according to the method described in the first embodiment . Examples of a medium are a static and / or dynamic memory, a fixed disk or any other medium such as a CD, DVD or Blu-Ray . The medium also comprises a means capable of supporting a signal representing the instructions , including a means for wired transmission (ethernet , optical , etc . ) or wireless transmission ( cellular, satellite , digital terrestrial transmission, etc . ) .

[0097] Many of the embodiments and examples have been discussed with reference to method or process steps . Nevertheless , what has been described can also be implemented in a program to be run on a processing entity ( also distributed) or on an entity the means of which are configured to perform the corresponding method steps . The entities described above , as well as the components thereof ( for example the units thereof ) can be implemented in a single device , via hardware , software , or a combination of these , or on multiple interconnected units or devices ( also hardware , software , or a combination thereof ) . In other words , each or some of the entities described above , as well as each or some of the components thereof ( for example the units thereof ) can be implemented locally or in a distributed manner . Naturally, the above description of embodiments and examples applying the principles recognised by the inventors has been provided solely as an example of such principles and must therefore not be understood as a limitation of the scope of the invention claimed herein . Furthermore , the means sets forth above can be represented by respective units ; for example , the management means can be represented by a management unit or a processor suitable for managing addresses or in any case by any hardware and / or software unit capable o f performing such functions . Similarly, the transmission means can be represented by a transmitter and the reception means by a receiver ; the transmitter and the receiver can be represented together by a transceiver .

[0098] Therefore , the technology discussed above allows a router 20 to request and obtain the requested changes for a determined user device 10 , so that the determined user device 10 can access a speci fic service without limitations . This procedure is also made safe and reliable by the double noti fication system .

Claims

CLAIMS1. Method for managing addresses in a communication network, the communication network comprising first network devices (20) , each first network device (20) being configured to interface one or more user devices (10) with the communication network, the method comprising the step of: sharing (SI) , between said first network devices (20) , a network address, accessible from the communication network via address-port mapping information configured in said first network devices (20) and indicating a mapping between said network address and a respective number of ports corresponding to each of said first network devices (20) ; in accordance with a configuration change of connection (S2) to the communication network, of a first user device (10) comprised in said one or more user devices (10) , in which said first user device (10) interfaces with a respective first network device (20) of said first network devices (20) : providing (S3) , in response to at least one of the first notification (Nl) and a second notification (N2) , a third notification (N3) to the first network device (20) allocating an individual network address to said respective first network device (20) , wherein the first notification (Nl) and the second notification (N2) include information related to the configuration change, wherein said first notification (Nl) and said second notification (N2) are different.

2. Network device (40) comprising: management means (401) for network addresses configured to manage a network address shared between one or more other network devices (20, 20' )each configured to interface one or more respective user devices ( 10-1...10-N; 10-1' ...10-N' ) , wherein said network address is accessible from the communication network via address-port mapping information configured in said one or more other network devices (20, 20' ) and indicating a mapping between said network address and a respective number of ports corresponding to each of said one or more other network devices (20, 20' ) ; transmission means (402) configured to transmit, in accordance with a configuration change of connection to the communication network of a first user device (10) interfacing with a respective first other network device (20) comprised in said one or more user devices ( 10-1...10-N; 10-1' ...10-N' ) and in response to at least one of a first notification (Nl) and a second notification (N2) , a third notification (N3) to said first other network device (20) , the third notification allocating an individual network address to said respective first other network device (20) , wherein the first notification (Nl) includes information related to the configuration change and the second notification (N2) includes information related to the configuration change, wherein said first notification (Nl) and said second notification (N2) are different.

3. Network device (40) according to claim 2, wherein said network device (40) further comprises reception means configured to receive the first notification (Nl) and the second notification (N2) , wherein the configuration means are configured to receive the second notification (N2) even if the first notification (Nl) has not been received.

4. Network device (40) according to one of claims 2 or 3, wherein the first notification (Nl) is a notification generated in response to the configuration change, preferably a realtime notification.

5. Network device (40) according to one of claims 2 to 4, wherein the second notification (N2) is aperiodic or asynchronous relative to the configuration change, preferably a notification including telemetry information.

6. Network device (40) according to one of claims 2 to 5, wherein the third notification (N3) includes information for changing the address-port mapping configuration in said first network devices (20) .

7. Network device (40) according to one of claims 2 to 6, further comprising: determination means configured to determine that the individual network address should no longer be allocated to the respective first network device (20) ; wherein the network device (20) is configured to, in accordance with a fourth notification (N4) provided to said respective first network device (20) , share the network address between said first network devices (20) .

8. Network device (40) according to one of claims 2 to 7, wherein the determination is based on at least one of: a determination of whether said respective first network device(20) requires an individual network address, based on information relating to the configuration of connection ofsaid one or more user devices (10) to said respective first network device (20) that is provided recurringly; and a determination that a predetermined time period has elapsed since the provision of said third notification (N3) to said respective first network device (20) .

9. Network device (40) according to one of claims 2 to 8, wherein the first notification (Nl) and / or the second notification (N2) indicates at least one of:- a port activation for the first user device (10) ;- a port transfer for the first user device (10) ; and- an indication that the first user device (10) and / or a port of the first user device (19) is made accessible to the network .

10. Network device (40) according to one of claims 2 to 9, wherein, in accordance with an instruction from a network controller (100) , a fourth notification (N4) is provided to said respective first network device (20) allocating the individual network address to said respective first network device (20, wherein preferably the instruction overrides any determination that the individual network address should no longer be allocated to the respective first network device (20) .

11. Computer program comprising instructions configured for executing, when said program is executed on one or more processor, all steps according to claim 1.

Images