Page Comparison

...

	Issue	Notes	Decision
1	Review the use case returning all 50k cmHandle	Validity of the use case where ALL 50k CMhanlde are expected to be returned everytime ? AP Csaba Kocsis & kieran mccarthy

Requirements

Interface

Requirement

Additional Information

Signoff

1

N/A

Registration & De-registration (Discovery)

AID

alternateID	28 Aug 2024 Parallel/Sequential ? tbc Batch size of 100 The whole cmhandle should be in ready state @the moment - TBC (should change to rate)
2	N/A	CM-handle search	28 Aug 2024 Frequency will increase by 2.5 of current capacity - CPS-391Spike: Define and Agree NCMP REST Interface - Developer Wiki - Confluence (onap.org) Search shall return all 50k searches ? @NCMP to confirm Searches shall return all 50k searches within 1 minute max
3	N/A	CM-handle ID Search	28 Aug 2024 Frequency will increase by 2.5 of current capacity Search shall return all 50k searches ? @NCMP to confirm Searches shall return all 50k searches within 1 minute max
4	N/A	Synchronous single CM-handle pass-through write (CUD)	28 Aug 2024 Frequencies will increase (2.5) atm TBC Response time should stay the same as current

(delay, size

- NCMP Characteristics
5	N/A	Synchronous single CM-handle pass-through Read

Frequencies

28 Aug 2024

Frequencies will increase (2.5) atm TBC
Response time should stay the same as current NCMP Characteristics (delay, size)

6

N/A

Batch Operation/Legacy

TBC next call

7

N/A

CM change notification

NCMP shall support a CM notification load of 150 million CM change notifications per day with an average of 870 notification
NCMP shall support a peak CM change notification load of 7k/s for a duration 5 minutes

TBC next call

	Scenario	Expected Behavior	Notes	Signoff
1

...