3GPP Alignment
- Reviewed proposal from Damian to make the primary and fallback IPs requirements conditionally mandatory
- Some concerns raised that this makes the decider of whether primary and fallback IPs are supported the sole decision of the NF provider which has implications to reliable delivery of events for the Operator
- As it exists today, there is a disconnect between ONAP, O-RAN, and 3GPP on this item.
- We agreed to jointly review the proposal offline and come back to discuss again
| View file |
|---|
| name | 3GPP_Harmonization_Pri_Sec_IP_address_20200414.pptx |
|---|
| height | 250 |
|---|
|
VES Fall Back to Primary (note: this is dependent on the outcome of the fallback
- Damian - Can we send duplicate Heart Beats to primary and secondary simultaneious?
- Vijay - that should be fine with DCAE, but the NF would need to know not to buffer the failure on the non-active endpoint.
- The de-duplication may need to be handled (it may already be cared for Vijay will confirm)
Do we need need to probe the primary listener endpoint when on the secondary to trigger a fallback?
- DCAE expects the NF to use the primary endpoint when available.
- The proposal is to use the Heart Beat to check the primary (when in failover mode) and if the Heart Beat