Legal claims defining the scope of protection. Each claim is shown in both the original legal language and a plain English translation.
1. A method for obtaining information about a service chain in a cloud computing system, the method comprising: receiving, by a service control proxy apparatus, a path forwarding identifier of a path used to transmit service data that is received from a service chain decision device; obtaining, by the service control proxy apparatus from a network functions virtualization orchestrator (NFVO), information about a path instance that corresponds to the path forwarding identifier, wherein the information about the path instance comprises an identifier of the path instance, an address of each node in the path, and a rank of each node in the path; obtaining, by the service control proxy apparatus from the NFVO, an address of a virtual controller that corresponds to the identifier of the path instance; obtaining, by the service control proxy apparatus, an identifier of a physical service chain from the virtual controller according to the address of the virtual controller, the address of each node in the path, and the rank of each node in the path; and sending, by the service control proxy apparatus, information about the physical service chain to the service chain decision device for instructing the service chain decision device to route and forward the service data, wherein the information about the physical service chain comprises the identifier of the physical service chain, the address of each node in the path, and the rank of each node in the path.
A service control proxy apparatus obtains information about a service chain. It first receives a path forwarding identifier, which identifies a path for transmitting service data, from a service chain decision device. Next, it requests and receives path instance information from a Network Functions Virtualization Orchestrator (NFVO), detailing the specific deployment of that path, including its unique identifier, the address of each node in the path, and their processing order (rank). The apparatus then requests and receives the address of a virtual controller from the NFVO, corresponding to the path instance identifier. Using this virtual controller's address, along with the node addresses and ranks, it obtains the identifier of the actual physical service chain. Finally, it sends this complete physical service chain information (identifier, node addresses, and ranks) back to the service chain decision device to instruct it on how to route and forward the service data.
2. The method according to claim 1 , wherein obtaining information about the path instance that corresponds to the path forwarding identifier comprises: sending, by the service control proxy apparatus, a path instance allocation request message to the NFVO, wherein the path instance allocation request message carries the path forwarding identifier; and receiving, by the service control proxy apparatus, the information about the path instance that is returned by the NFVO.
A service control proxy apparatus obtains information about a service chain. It first receives a path forwarding identifier, which identifies a path for transmitting service data, from a service chain decision device. To obtain the path instance information, which includes its unique identifier, the address of each node in the path, and their processing order (rank), the apparatus sends a path instance allocation request message containing the path forwarding identifier to a Network Functions Virtualization Orchestrator (NFVO), and then receives the requested path instance information back from the NFVO. Next, it requests and receives the address of a virtual controller from the NFVO, corresponding to the path instance identifier. Using this virtual controller's address, along with the node addresses and ranks, it obtains the identifier of the actual physical service chain. Finally, it sends this complete physical service chain information (identifier, node addresses, and ranks) back to the service chain decision device to instruct it on how to route and forward the service data.
3. The method according to claim 2 , wherein the method further comprises: receiving, by the service control proxy apparatus, information about a virtualized infrastructure manager (VIM) managing the path instance that is received from the NFVO; and wherein obtaining, by the service control proxy apparatus, the address of the virtual controller that corresponds to the identifier of the path instance comprises: sending, by the service control proxy apparatus, a request for obtaining an address of a virtual controller to the NFVO, wherein the request for obtaining the address of the virtual controller carries the identifier of the path instance and the information about the VIM, the information about the VIM for indicating the VIM that provides the address of the virtual controller that corresponds to the identifier of the path instance, and receiving the address of the virtual controller received from the NFVO; or sending, by the service control proxy apparatus, a request for obtaining an address of a virtual controller to the NFVO, wherein the request for obtaining the address of the virtual controller carries the address of each node in the path, the rank of each node in the path, the information about the VIM, the information about the VIM for indicating the VIM that provides the address of the virtual controller that corresponds to the identifier of the path instance, and the identifier of the path instance corresponds to the address of each node in the path and the rank of each node in the path, and receiving the address of the virtual controller received from the NFVO.
A service control proxy apparatus obtains information about a service chain. It first receives a path forwarding identifier, which identifies a path for transmitting service data, from a service chain decision device. To obtain the path instance information, which includes its unique identifier, the address of each node in the path, and their processing order (rank), the apparatus sends a path instance allocation request message containing the path forwarding identifier to a Network Functions Virtualization Orchestrator (NFVO), and then receives the requested path instance information back from the NFVO. Additionally, the apparatus receives information about the Virtualized Infrastructure Manager (VIM) that manages the path instance from the NFVO. To obtain the address of a virtual controller corresponding to the path instance identifier, the apparatus either sends a request to the NFVO carrying the path instance identifier and the VIM information (indicating which VIM provides the virtual controller address), or sends a request to the NFVO carrying the node addresses, node ranks, and VIM information (where the path instance identifier corresponds to the node addresses and ranks), and then receives the virtual controller's address from the NFVO. Using this address, node addresses, and ranks, it obtains the physical service chain identifier and sends the physical service chain information to the service chain decision device for routing.
4. The method according to claim 2 , wherein obtaining the address of the virtual controller that corresponds to the identifier of the path instance comprises: sending, by the service control proxy apparatus, a request for obtaining an address of a virtual controller to the NFVO, wherein the request for obtaining the address of the virtual controller carries the identifier of the path instance, the request for obtaining an address of a virtual controller for instructing the NFVO to obtain, according to the identifier of the path instance, information about a VIM managing the path instance, and to obtain, from the VIM indicated by the information about the VIM, the address of the virtual controller that corresponds to the identifier of the path instance, and receiving the address of the virtual controller received from the NFVO; or sending, by the service control proxy apparatus, a request for obtaining an address of a virtual controller to the NFVO, wherein the request for obtaining the address of the virtual controller carries the address of each node in the path and the rank of each node in the path, the request for obtaining an address of a virtual controller for instructing the NFVO to obtain information about a VIM managing the path instance that comprises the address of each node in the path and the rank of each node in the path, and to obtain, from the VIM indicated by the information about the VIM, the address of the virtual controller that corresponds to the identifier of the path instance, and the identifier of the path instance corresponds to the address of each node in the path and the rank of each node in the path, and receiving the address of the virtual controller received from the NFVO.
A service control proxy apparatus obtains information about a service chain. It first receives a path forwarding identifier, which identifies a path for transmitting service data, from a service chain decision device. To obtain the path instance information, which includes its unique identifier, the address of each node in the path, and their processing order (rank), the apparatus sends a path instance allocation request message containing the path forwarding identifier to a Network Functions Virtualization Orchestrator (NFVO), and then receives the requested path instance information back from the NFVO. To obtain the address of a virtual controller corresponding to the path instance identifier, the apparatus either sends a request to the NFVO carrying the path instance identifier, instructing the NFVO to obtain VIM information managing the path instance and then get the virtual controller address from that VIM, or sends a request to the NFVO carrying the node addresses and ranks, instructing the NFVO to obtain VIM information managing the path instance (which comprises the node addresses and ranks) and then get the virtual controller address from that VIM. In either case, the apparatus receives the virtual controller's address from the NFVO. Using this address, node addresses, and ranks, it obtains the physical service chain identifier and sends the physical service chain information to the service chain decision device for routing.
5. The method according to claim 1 , wherein obtaining the identifier of the physical service chain from the virtual controller according to the address of the virtual controller, the address of each node in the path, and the rank of each node in the path comprises: sending, by the service control proxy apparatus, a physical service chain identifier obtaining request to the virtual controller according to the address of the virtual controller, wherein the physical service chain identifier obtaining request carries the address of each node in the path and the rank of each node in the path; and receiving, by the service control proxy apparatus, the identifier of the physical service chain that is received from the virtual controller.
A service control proxy apparatus obtains information about a service chain. It first receives a path forwarding identifier, which identifies a path for transmitting service data, from a service chain decision device. Next, it requests and receives path instance information from a Network Functions Virtualization Orchestrator (NFVO), detailing the specific deployment of that path, including its unique identifier, the address of each node in the path, and their processing order (rank). The apparatus then requests and receives the address of a virtual controller from the NFVO, corresponding to the path instance identifier. To obtain the identifier of the physical service chain, the apparatus sends a physical service chain identifier obtaining request to the virtual controller (using its address), carrying the address of each node in the path and their rank. It then receives the physical service chain identifier from the virtual controller. Finally, it sends this complete physical service chain information (identifier, node addresses, and ranks) back to the service chain decision device to instruct it on how to route and forward the service data.
6. A method for obtaining information about a service chain in a cloud computing system, the method comprising: receiving, by a network functions virtualization orchestrator (NFVO), a path instance allocation request message from a service control proxy apparatus, wherein the path instance allocation request message carries a path forwarding identifier; returning, by the NFVO, information about a path instance to the service control proxy apparatus, wherein the information about the path instance comprises an identifier of the path instance that corresponds to the path forwarding identifier, an address of each node in a path, and a rank of each node in the path; receiving, by the NFVO, a request for obtaining an address of a virtual controller that is received from the service control proxy apparatus, wherein the request for obtaining an address of a virtual controller carries (i) the identifier of the path instance or (ii) the address of each node in the path and the rank of each node in the path; sending, by the NFVO, the request for obtaining an address of a virtual controller to a virtualized infrastructure manager (VIM) managing the path instance indicated by the identifier of the path instance; receiving, by the NFVO, an address of a virtual controller returned by the VIM; and sending, by the NFVO, the address of the virtual controller to the service control proxy apparatus for indicating the virtual controller that provides an identifier of a physical service chain according to the address of each node in the path and the rank of each node in the path.
A Network Functions Virtualization Orchestrator (NFVO) helps obtain service chain information. It receives a path instance allocation request message, carrying a path forwarding identifier, from a service control proxy apparatus. The NFVO then returns path instance information to the service control proxy apparatus, which includes a path instance identifier (corresponding to the path forwarding identifier), the address of each node in the path, and their rank. The NFVO then receives a request for a virtual controller's address from the service control proxy apparatus, which contains either the path instance identifier or both the node addresses and ranks. It forwards this request to the Virtualized Infrastructure Manager (VIM) that manages the path instance indicated by the path instance identifier. After receiving the virtual controller's address from the VIM, the NFVO sends this address to the service control proxy apparatus, indicating the virtual controller that can provide the physical service chain identifier based on the node addresses and ranks.
7. The method according to claim 6 , wherein before receiving the request for obtaining the address of the virtual controller from the service control proxy apparatus, the method comprises: returning, by the NFVO, information about the VIM managing the path instance to the service control proxy apparatus, wherein the request for obtaining an address of a virtual controller further carries the information about the VIM managing the path instance; and wherein sending the request for obtaining the address of the virtual controller to the VIM managing the path instance comprises: sending, by the NFVO according to the information about the VIM managing the path instance, the request for obtaining an address of a virtual controller to the VIM managing the path instance.
A Network Functions Virtualization Orchestrator (NFVO) helps obtain service chain information. It receives a path instance allocation request message, carrying a path forwarding identifier, from a service control proxy apparatus. The NFVO then returns path instance information to the service control proxy apparatus, which includes a path instance identifier (corresponding to the path forwarding identifier), the address of each node in the path, and their rank. Before receiving the virtual controller address request, the NFVO returns information about the Virtualized Infrastructure Manager (VIM) managing the path instance to the service control proxy apparatus. The NFVO then receives a request for a virtual controller's address from the service control proxy apparatus, which contains either the path instance identifier or both the node addresses and ranks, and also carries the VIM information. The NFVO sends this request to the VIM, using the VIM information to identify the correct VIM managing the path instance. After receiving the virtual controller's address from the VIM, the NFVO sends this address to the service control proxy apparatus, indicating the virtual controller that can provide the physical service chain identifier based on the node addresses and ranks.
8. The method according to claim 6 , wherein the method further comprises: obtaining, by the NFVO according to the identifier of the path instance, information about the VIM managing the selected path instance; and wherein sending the request for obtaining the address of the virtual controller to the VIM managing the path instance comprises: sending, by the NFVO according to the information about the VIM managing the path instance, the request for obtaining an address of a virtual controller to the VIM managing the path instance.
A Network Functions Virtualization Orchestrator (NFVO) helps obtain service chain information. It receives a path instance allocation request message, carrying a path forwarding identifier, from a service control proxy apparatus. The NFVO then returns path instance information to the service control proxy apparatus, which includes a path instance identifier (corresponding to the path forwarding identifier), the address of each node in the path, and their rank. The NFVO then receives a request for a virtual controller's address from the service control proxy apparatus, which contains either the path instance identifier or both the node addresses and ranks. The NFVO obtains information about the Virtualized Infrastructure Manager (VIM) managing the path instance based on the path instance identifier. It then sends the virtual controller address request to that identified VIM. After receiving the virtual controller's address from the VIM, the NFVO sends this address to the service control proxy apparatus, indicating the virtual controller that can provide the physical service chain identifier based on the node addresses and ranks.
9. The method according to claim 6 , further comprising: receiving, by the NFVO, a service chain decision device instantiation request that carries an identifier of a virtualized network function descriptor (VNFD) of a service chain decision device; obtaining, by the NFVO, the VNFD according to the identifier of the VNFD; determining, by the NFVO according to the VNFD, the VNFD comprises a requirement for a service control proxy apparatus; selecting, by the NFVO, for the service chain decision device, a virtualized network function manager (VNFM) that comprises a service control proxy apparatus; and sending, by the NFVO, the service chain decision device instantiation request to the selected VNFM that comprises a service control proxy apparatus.
A Network Functions Virtualization Orchestrator (NFVO) helps obtain service chain information. It receives a path instance allocation request message, carrying a path forwarding identifier, from a service control proxy apparatus. The NFVO then returns path instance information to the service control proxy apparatus, which includes a path instance identifier (corresponding to the path forwarding identifier), the address of each node in the path, and their rank. The NFVO then receives a request for a virtual controller's address from the service control proxy apparatus, which contains either the path instance identifier or both the node addresses and ranks. It forwards this request to the Virtualized Infrastructure Manager (VIM) that manages the path instance indicated by the path instance identifier. After receiving the virtual controller's address from the VIM, the NFVO sends this address to the service control proxy apparatus. Additionally, the NFVO receives a service chain decision device instantiation request with a Virtualized Network Function Descriptor (VNFD) identifier, obtains the VNFD, determines it requires a service control proxy apparatus, selects a Virtualized Network Function Manager (VNFM) that includes a service control proxy apparatus, and sends the instantiation request to that selected VNFM.
10. The method according to claim 6 , further comprising: receiving, by the NFVO, a service chain decision device instantiation request, wherein the service chain decision device instantiation request carries an identifier of a virtualized network function descriptor (VNFD) of a service chain decision device; obtaining, by the NFVO, the VNFD according to the identifier of the VNFD; determining, by the NFVO, according to the VNFD, the VNFD comprises a requirement for a service control proxy apparatus; selecting, by the NFVO, for the service chain decision device, a service control proxy apparatus and a virtualized network function manager (VNFM) that does not comprise a service control proxy apparatus; and sending, by the NFVO, the service chain decision device instantiation request to the selected VNFM that does not comprise a service control proxy apparatus, wherein the service chain decision device instantiation request sent to the VNFM further comprises an identifier of the selected service control proxy apparatus for instructing the VNFM to configure, after the service chain decision device is instantiated, an address of the service control proxy apparatus for an instance of the service chain decision device according to the identifier of the service control proxy apparatus.
A Network Functions Virtualization Orchestrator (NFVO) helps obtain service chain information. It receives a path instance allocation request message, carrying a path forwarding identifier, from a service control proxy apparatus. The NFVO then returns path instance information to the service control proxy apparatus, which includes a path instance identifier (corresponding to the path forwarding identifier), the address of each node in the path, and their rank. The NFVO then receives a request for a virtual controller's address from the service control proxy apparatus, which contains either the path instance identifier or both the node addresses and ranks. It forwards this request to the Virtualized Infrastructure Manager (VIM) that manages the path instance indicated by the path instance identifier. After receiving the virtual controller's address from the VIM, the NFVO sends this address to the service control proxy apparatus. Additionally, the NFVO receives a service chain decision device instantiation request with a Virtualized Network Function Descriptor (VNFD) identifier, obtains the VNFD, determines it requires a service control proxy apparatus, selects a service control proxy apparatus and a Virtualized Network Function Manager (VNFM) that does not include one, and sends the instantiation request to that VNFM with the service control proxy apparatus identifier, instructing the VNFM to configure its address for the instantiated device.
11. A network element, comprising: a transceiver; a processor coupled to the transceiver; and a memory coupled to the processor and configured to store computer executable program code comprising instructions which, when executed by the processor, cause the network element to: receive a path forwarding identifier of a path used to transmit service data that is received from a service chain decision device, obtain from a network functions virtualization orchestrator (NFVO), information about a path instance that corresponds to the path forwarding identifier, wherein the information about the path instance comprises an identifier of the path instance, an address of each node in the path, and a rank of each node in the path, obtain from the NFVO, an address of a virtual controller that corresponds to the identifier of the path instance, obtain an identifier of a physical service chain from the virtual controller according to the address of the virtual controller, the address of each node in the path, and the rank of each node in the path, and send information about the physical service chain to the service chain decision device for instructing the service chain decision device to route and forward the service data, wherein the information about the physical service chain comprises the identifier of the physical service chain, the address of each node in the path, and the rank of each node in the path.
A network element, likely a service control proxy apparatus, includes a transceiver, processor, and memory storing instructions. When executed, these instructions cause the network element to perform the following steps to obtain service chain information: It receives a path forwarding identifier for service data from a service chain decision device. It obtains path instance information from a Network Functions Virtualization Orchestrator (NFVO), which includes the path instance's identifier, node addresses, and node ranks. It then obtains a virtual controller's address from the NFVO, corresponding to the path instance identifier. Using this virtual controller's address, the node addresses, and node ranks, it obtains the identifier of the physical service chain from the virtual controller. Finally, it sends this physical service chain information (identifier, node addresses, and ranks) to the service chain decision device to instruct it on routing the service data.
12. A network element, comprising: a transceiver; a processor coupled to the transceiver; a memory coupled to the processor and configured to store computer executable program code comprising instructions which, when executed by the processor, cause the network element to: receive a path instance allocation request message received from a service control proxy apparatus, wherein the path instance allocation request message carries the path forwarding identifier, return information about a path instance to the service control proxy apparatus, wherein the information about the path instance comprises an identifier of the path instance that corresponds to the path forwarding identifier, an address of each node in the path, and a rank of each node in the path, receive a request for obtaining an address of a virtual controller that is received from the service control proxy apparatus, wherein the request for obtaining an address of a virtual controller carries the identifier of the path instance, send the request for obtaining an address of a virtual controller to a virtualized infrastructure manager (VIM) managing the path instance indicated by the identifier of the path instance, receive an address of a virtual controller returned by the VIM, and send the address of the virtual controller to the service control proxy apparatus for indicating the virtual controller that provides an identifier of a physical service chain according to the address of each node in the path and the rank of each node in the path.
A network element, likely a Network Functions Virtualization Orchestrator (NFVO), includes a transceiver, processor, and memory storing instructions. When executed, these instructions cause the network element to perform the following steps to facilitate obtaining service chain information: It receives a path instance allocation request message, carrying a path forwarding identifier, from a service control proxy apparatus. It returns path instance information to the service control proxy apparatus, including a path instance identifier (corresponding to the path forwarding identifier), node addresses, and node ranks. It then receives a request for a virtual controller's address from the service control proxy apparatus, specifically carrying the path instance identifier. The NFVO sends this request to the Virtualized Infrastructure Manager (VIM) managing the path instance identified. After receiving the virtual controller's address from the VIM, the NFVO sends this address to the service control proxy apparatus, indicating the virtual controller that can provide the physical service chain identifier based on the node addresses and ranks.
Unknown
August 4, 2020
Browse 5M+ US patents with plain-English claim translations and AI-generated analysis.