Methods, Function Manager and Orchestration Node of Managing a Port Type

Abstract

Embodiments relate to e.g. a method performed by an orchestration node for managing network interfaces. The orchestration node sends to a function manager, trunk-port specific information of a trunk port to enable the function manager to unambiguously orchestrate trunk ports.

1 - 26 . (canceled) 
     
     
         27 . A method performed by an orchestration node for managing network interfaces, the method comprising:
 sending to a function manager, trunk-port specific information of a trunk port to enable the function manager to unambiguously orchestrate trunk ports.   
     
     
         28 . The method according to  claim 27 , wherein the trunk-port specific information comprises an identifier used between an application and networking infrastructure to identify a network sub-interface of the trunk port in question. 
     
     
         29 . The method according to  claim 27 , further comprising establishing that the trunk port is a trunk port type comprising a plurality of network sub-interfaces; and
 associating with each network sub-interface of said trunk port a respective trunk-port specific information.   
     
     
         30 . The method according to  claim 29 , wherein associating with each network sub-interface of said trunk port the respective trunk-port specific information comprises adding a segmentation identity to a configuration. 
     
     
         31 . The method according to  claim 27 , wherein the trunk-port specific information comprises an identifier for each network sub-interface of said trunk port. 
     
     
         32 . The method of  claim 27 , wherein the orchestration node is a Network Functions Virtualization Orchestrator and/or the function manager is a Virtualized Network Function Manager. 
     
     
         33 . The method according to  claim 27 , wherein said trunk-port specific information comprises a sub-interface network identifier or a sub-interface network tag, identifying which network the sub-interface connects to. 
     
     
         34 . A method performed by a function manager for managing network interfaces, the method comprising:
 receiving from an orchestration node, trunk-port specific information of a trunk port; and   orchestrating the trunk port based on the received trunk-port specific information.   
     
     
         35 . The method according to  claim 34 , wherein the trunk-port specific information comprises an identifier used between an application and networking infrastructure to identify a network sub-interface of the trunk port in question. 
     
     
         36 . The method according to  claim 34 , wherein the trunk-port specific information comprises an identifier for each network sub-interface of said trunk port. 
     
     
         37 . The method of  claim 34 , wherein the orchestration node is a Network Functions Virtualization Orchestrator and/or the function manager is a Virtualized Network Function Manager. 
     
     
         38 . The method according to  claim 34 , wherein said trunk-port specific information comprises a sub-interface network identifier or a sub-interface network tag, identifying which network the network sub-interface connects to. 
     
     
         39 . The method according to  claim 34 , wherein orchestrating the trunk port comprises adding and/or removing network sub-interfaces to/from a trunk port based on the received trunk-port specific information. 
     
     
         40 . An orchestration node for managing network interfaces, wherein the orchestration node is adapted to:
 send to a function manager, trunk-port specific information of a trunk port in such a way that the function manager can unambiguously orchestrate trunk ports.   
     
     
         41 . The orchestration node according to  claim 40 , wherein the trunk-port specific information comprises an identifier used between an application and networking infrastructure to identify a network sub-interface of the trunk port in question. 
     
     
         42 . The orchestration node according to  claim 40 , wherein the orchestration node is further adapted to
 establish that the trunk port is a trunk port type comprising a plurality of network sub- interfaces; and   associate with each network sub-interface of said trunk port a respective trunk-port specific information.   
     
     
         43 . The orchestration node according to  claim 40 , wherein the trunk-port specific information comprises an identifier for each network sub-interface of said trunk port. 
     
     
         44 . The orchestration node of  claim 40 , wherein the orchestration node is a Network Functions Virtualization Orchestrator and/or the function manager is a Virtualized Network Function Manager. 
     
     
         45 . The orchestration node according to  claim 40 , wherein the orchestration node is configured to associate with each network sub-interface of said trunk port the respective trunk-port specific information by adding a segmentation identity to a configuration. 
     
     
         46 . The orchestration node according to  claim 40 , wherein said trunk-port specific information comprises a sub-interface network identifier or a sub-interface network tag, identifying which network the network sub-interface connects to. 
     
     
         47 . A function manager for managing network interfaces, wherein the function manager is adapted to:
 receive from an orchestration node, trunk-port specific information of a trunk port; and   orchestrate the trunk port based on the received trunk-port specific information.   
     
     
         48 . The function manager according to  claim 47 , wherein the trunk-port specific information comprises an identifier used between an application and networking infrastructure to identify a network sub-interface of the trunk port in question. 
     
     
         49 . The function manager according to  claim 47 , wherein the trunk-port specific information comprises an identifier for each network sub-interface of said trunk port. 
     
     
         50 . The function manager of  claim 47 , wherein the orchestration node is a Network Functions Virtualization Orchestrator and/or the function manager is a Virtualized Network Function Manager. 
     
     
         51 . The function manager according to  claim 47 , wherein said trunk-port specific information comprises a sub-interface network identifier or a sub-interface network tag, identifying which network the network sub-interface connects to. 
     
     
         52 . The function manager according to  claim 47 , wherein the function manager is adapted to orchestrate the trunk port by adding and/or removing network sub-interfaces to/from a trunk port based on the received trunk-port specific information.