IP Library Granted Patent US 10,693,817
Granted Patent B1
US 10,693,817 · App. 16/200,611 · Granted Jun 23, 2020

VNFM resolution of split-brain virtual network function components

View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 10,693,817
App. No.
16/200,611
Granted
Jun 23, 2020
Kind
B1
Abstract

An example operation may include a system, comprising one or more of receiving a VNFCI status notification resumption with an active state, retrieving a timestamp of the VNFCI state change to active, retrieving a timestamp of a peer VNFCI state change to active, checking with a VIM to determine if the VNFCI network isolated while active, checking with the VIM to determine if the peer VNFCI network isolated while active, sending a first state change request message with standby to the peer VNFCI when one or more of: the peer VNFCI was network isolated, and the VNFCI was not network isolated, sending a second state change request message with standby to the peer VNFCI when one or more of: the VNFCI is not the preferred standby instance, and the peer VNFCI was not network isolated, and the VNFCI was not network isolated, starting a first retry timer for the peer VNFCI when one or more of: the first state change request message is sent, and the second state change request message is sent, sending a third state change request message with standby to the VNFCI when one or more of: the VNFCI is the preferred standby instance, and the peer VNFCI was network isolated, and the VNFCI was network isolated, sending a fourth state change request message with standby to the VNFCI when one or more of: the peer VNFCI was not network isolated, and the VNFCI was network isolated, and starting a second retry timer for the VNFCI when one or more of: the third state change request message is sent, and the fourth state change request message is sent.

Claims (53)

1. A system, comprising:

receive a virtual network function component instance (VNFCI) status notification resumption with an active state;

retrieve a timestamp of the VNFCI state change to active;

retrieve a timestamp of a peer VNFCI state change to active;

check with a virtualized infrastructure manager (VIM) to determine if the VNFCI network isolated while active;

check with the VIM to determine if the peer VNFCI network isolated while active;

send a first state change request message with standby to the peer VNFCI when one or more of: the peer VNFCI was network isolated, and the VNFCI was not network isolated;

send a second state change request message with standby to the peer VNFCI when one or more of: the VNFCI is not the preferred standby instance, and the peer VNFCI was not network isolated, and the VNFCI was not network isolated;

start a first retry timer for the peer VNFCI when one or more of: the first state change request message is sent, and the second state change request message is sent;

send a third state change request message with standby to the VNFCI when one or more of: the VNFCI is the preferred standby instance, and the peer VNFCI was network isolated, and the VNFCI was network isolated;

send a fourth state change request message with standby to the VNFCI when one or more of: the peer VNFCI was not network isolated, and the VNFCI was network isolated; and

start a second retry timer for the VNFCI when one or more of: the third state change request message is sent, and the fourth state change request message is sent.

2. The system of claim 1 , wherein the status notification resumption is received when the peer VNFCI operational state is active.

3. The system of claim 1 , wherein a sixth state change request with standby message is sent to the VNFCI when the first retry timer for the VNFCI expires.

4. The system of claim 1 , the first retry timer is stopped when a receive state change acknowledgement is received from the VNFCI.

5. The system of claim 1 , wherein a fifth state change request with standby message is sent to the VNFCI when the second retry timer for the VNFCI expires.

6. The system of claim 1 , the second retry timer is stopped when a receive state change acknowledgement is received from the VNFCI.

7. The system of claim 1 , where the first state change request message and the second state change request message and the third state change request message and the fourth state change request message and the fifth state change request message and the sixth state change request message may be one or more of: the same message, and a different message.

8. A method, comprising:

receiving a VNFCI status notification resumption with an active state;

retrieving a timestamp of the VNFCI state change to active;

retrieving a timestamp of a peer VNFCI state change to active;

checking with a VIM to determine if the VNFCI network isolated while active;

checking with the VIM to determine if the peer VNFCI network isolated while active;

sending a first state change request message with standby to the peer VNFCI when one or more of: the peer VNFCI was network isolated, and the VNFCI was not network isolated;

sending a second state change request message with standby to the peer VNFCI when one or more of: the VNFCI is not the preferred standby instance, and the peer VNFCI was not network isolated, and the VNFCI was not network isolated;

starting a first retry timer for the peer VNFCI when one or more of: the first state change request message is sent, and the second state change request message is sent;

sending a third state change request message with standby to the VNFCI when one or more of: the VNFCI is the preferred standby instance, and the peer VNFCI was network isolated, and the VNFCI was network isolated;

sending a fourth state change request message with standby to the VNFCI when one or more of: the peer VNFCI was not network isolated, and the VNFCI was network isolated; and

starting a second retry timer for the VNFCI when one or more of: the third state change request message is sent, and the fourth state change request message is sent.

9. The method of claim 8 , wherein the status notification resumption is received when the peer VNFCI operational state is active.

10. The method of claim 8 , wherein a sixth state change request with standby message is sent to the VNFCI when the first retry timer for the VNFCI expires.

11. The method of claim 8 , the first retry timer is stopped when a receive state change acknowledgement is received from the VNFCI.

12. The method of claim 8 , wherein a fifth state change request with standby message is sent to the VNFCI when the second retry timer for the VNFCI expires.

13. The method of claim 8 , the second retry timer is stopped when a receive state change acknowledgement is received from the VNFCI.

14. The method of claim 8 , where the first state change request message and the second state change request message and the third state change request message and the fourth state change request message and the fifth state change request message and the sixth state change request message may be one or more of: the same message, and a different message.

15. A non-transitory computer readable medium comprising instructions, that when read by a processor, cause the processor to perform:

receiving a VNFCI status notification resumption with an active state;

retrieving a timestamp of the VNFCI state change to active;

retrieving a timestamp of a peer VNFCI state change to active;

checking with a VIM to determine if the VNFCI network isolated while active;

checking with the VIM to determine if the peer VNFCI network isolated while active;

sending a first state change request message with standby to the peer VNFCI when one or more of: the peer VNFCI was network isolated, and the VNFCI was not network isolated;

sending a second state change request message with standby to the peer VNFCI when one or more of: the VNFCI is not the preferred standby instance, and the peer VNFCI was not network isolated, and the VNFCI was not network isolated;

starting a first retry timer for the peer VNFCI when one or more of: the first state change request message is sent, and the second state change request message is sent;

sending a third state change request message with standby to the VNFCI when one or more of: the VNFCI is the preferred standby instance, and the peer VNFCI was network isolated, and the VNFCI was network isolated;

sending a fourth state change request message with standby to the VNFCI when one or more of: the peer VNFCI was not network isolated, and the VNFCI was network isolated; and

starting a second retry timer for the VNFCI when one or more of: the third state change request message is sent, and the fourth state change request message is sent.

16. The non-transitory computer readable medium of claim 15 , wherein the status notification resumption is received when the peer VNFCI operational state is active.

17. The non-transitory computer readable medium of claim 15 , wherein a sixth state change request with standby message is sent to the VNFCI when the first retry timer for the VNFCI expires.

18. The non-transitory computer readable medium of claim 15 , the first retry timer is stopped when a receive state change acknowledgement is received from the VNFCI.

19. The non-transitory computer readable medium of claim 15 , wherein a fifth state change request with standby message is sent to the VNFCI when the second retry timer for the VNFCI expires.

20. The non-transitory computer readable medium of claim 15 , wherein the first state change request message and the second state change request message and the third state change request message and the fourth state change request message and the fifth state change request message and the sixth state change request message may be one or more of: the same message, and a different message.

Assignments (2)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 25, 2022
From: OPEN INVENTION NETWORK LLC
To: GOOGLE LLC
Reel/Frame 061766/0545 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Nov 26, 2018
From: MELKILD, KEITH WILLIAM
To: OPEN INVENTION NETWORK LLC
Reel/Frame 047637/0365 →