7 Specification level requirements
28.3113GPPManagement and orchestrationNetwork policy management for mobile networks based on Network Function Virtualization (NFV) scenariosRelease 17TS
7.1 Requirements
REQ-POM-FUN-01
The IRPAgent shall provide the capability to allow the IRPManager to create the network policy.
REQ-POM-FUN-02
The IRPAgent shall provide the capability to allow the IRPManager to delete the network policy.
REQ-POM-FUN-03
The IRPAgent shall provide the capability to allow the IRPManager to update the network policy.
REQ-POM-FUN-04
The IRPAgent shall provide the capability to allow the IRPManager to query the network policy.
REQ-POM-FUN-05
The IRPAgent shall provide the capability to allow the IRPManager to activate the network policy.
REQ-POM-FUN-06
The IRPAgent shall provide the capability to allow the IRPManager to deactivate the network policy.
REQ-POM-FUN-07
The IRPAgent should notify the IRPManager when there is a network policy conflict.
7.2 Actor roles
See detailed actors and roles for each use case in clause 7.4.
7.3 Telecommunications resources
See detailed telecommunication resources for each use case in clause 7.4.
7.4 Use cases
7.4.1 Create a policy in the context of NFV
|
Use Case Stage |
Evolution / Specification |
<<Uses>> Related use |
|---|---|---|
|
Goal |
To create a policy such as deploying the SBC from IMS and P-GW from EPC in the same Data Centre. |
|
|
Actors and Roles |
IRPManager as user |
|
|
Telecom resources |
3GPP management system (NM, EM). |
|
|
Assumptions |
3GPP management systems are running normally, scenarios and policy requirements are clearly defined. |
|
|
Pre conditions |
The systems is correctly configured and normally running. |
|
|
Begins when |
The IRPManager decides to create a policy. |
|
|
Step 1 (M) |
The IPRManager makes a decision to create a network policy according to the network requirements, such as deploying the SBC. |
|
|
Step 2 (M) |
After the completion of the policy creation process, the IRPAgent informs the IRPManager on the result of the process. |
|
|
Ends when |
Ends when all mandatory steps identified above are successfully completed or when an exception occurs. |
|
|
Exceptions |
One of the steps identified above fails. |
|
|
Post Conditions |
The policy is created and stored in the IRPAgent. |
|
|
Traceability |
REQ-POM-FUN -01 |
7.4.2 Delete a policy in the context of NFV
|
Use Case Stage |
Evolution / Specification |
<<Uses>> Related use |
|---|---|---|
|
Goal |
To delete a policy such as deploying the SBC from IMS and P-GW from EPC in the same Data Center. |
|
|
Actors and Roles |
IRPManager as user |
|
|
Telecom resources |
3GPP management system (NM, EM). |
|
|
Assumptions |
3GPP management systems are running normally, scenarios and policy requirements are clearly defined. |
|
|
Pre conditions |
The systems is correctly configured and normally running. There is a network policy stored in the IRPAgent. |
|
|
Begins when |
The IRPManager decides to delete a policy. |
|
|
Step 1 (M) |
The IPRManager makes a decision to delete the existing policy. |
|
|
Step 2 (M) |
After the completion of the policy deletion process, the IRPAgent informs the IRPManager on the result of the process. |
|
|
Ends when |
Ends when all mandatory steps identified above are successfully completed or when an exception occurs. |
|
|
Exceptions |
One of the steps identified above fails. |
|
|
Post Conditions |
The policy is deleted in the IRPAgent. |
|
|
Traceability |
REQ-POM-FUN -02 |
7.4.3 Update a policy in the context of NFV
|
Use Case Stage |
Evolution / Specification |
<<Uses>> Related use |
|---|---|---|
|
Goal |
To update an existing network policy. |
|
|
Actors and Roles |
IRPManager as user |
|
|
Telecom resources |
3GPP management system (NM, EM). |
|
|
Assumptions |
3GPP management systems are running normally, scenarios and policy requirements are clearly defined. |
|
|
Pre conditions |
The systems is correctly configured and normally running. There is a network policy stored in the IRPAgent. |
|
|
Begins when |
The IRPManager decides to update a policy. |
|
|
Step 1 (M) |
The IPRManager makes a decision to update the existing policy. |
|
|
Step 2 (M) |
After the completion of the policy update process, the IRPAgent informs the IRPManager on the result of the process. |
|
|
Ends when |
Ends when all mandatory steps identified above are successfully completed or when an exception occurs. |
|
|
Exceptions |
One of the steps identified above fails. |
|
|
Post Conditions |
The policy is updated and stored in the IRPAgent. |
|
|
Traceability |
REQ-POM-FUN -03 |
7.4.4 Query a policy in the context of NFV
|
Use Case Stage |
Evolution / Specification |
<<Uses>> Related use |
|---|---|---|
|
Goal |
To query an existing network policy. |
|
|
Actors and Roles |
IRPManager as user |
|
|
Telecom resources |
3GPP management system (NM, EM). |
|
|
Assumptions |
3GPP management systems are running normally, scenarios and policy requirements are clearly defined. |
|
|
Pre conditions |
The systems is correctly configured and normally running. There is a network policy stored in the IRPAgent. |
|
|
Begins when |
The IRPManager decides to query a policy. |
|
|
Step 1 (M) |
The IPRManager makes a decision to query the existing policy. |
|
|
Step 2 (M) |
After the completion of the policy query process, the IRPAgent informs the IRPManager on the result of the process. |
|
|
Ends when |
Ends when all mandatory steps identified above are successfully completed or when an exception occurs. |
|
|
Exceptions |
One of the steps identified above fails. |
|
|
Post Conditions |
The policy information is returned to the IPRManager. |
|
|
Traceability |
REQ-POM-FUN -04 |
7.4.5 Activate a policy in the context of NFV
|
Use Case Stage |
Evolution / Specification |
<<Uses>> Related use |
|---|---|---|
|
Goal |
To activate an existing network policy. |
|
|
Actors and Roles |
IRPManager as user |
|
|
Telecom resources |
3GPP management system (NM, EM). |
|
|
Assumptions |
3GPP management systems are running normally, scenarios and policy requirements are clearly defined. |
|
|
Pre conditions |
The systems is correctly configured and normally running. There is a network policy stored in the IRPAgent. |
|
|
Begins when |
The IRPManager decides to active a policy. |
|
|
Step 1 (M) |
The IPRManager makes a decision to active the existing policy. |
|
|
Step 2 (M) |
After the completion of the policy activation process, the IRPAgent informs the IRPManager on the result of the process. |
|
|
Ends when |
Ends when all mandatory steps identified above are successfully completed or when an exception occurs. |
|
|
Exceptions |
One of the steps identified above fails. |
|
|
Post Conditions |
The policy is activated in the IRPAgent. |
|
|
Traceability |
REQ-POM-FUN -05 |
7.4.6 Deactivate a policy in the context of NFV
|
Use Case Stage |
Evolution / Specification |
<<Uses>> Related use |
|---|---|---|
|
Goal |
To query an existing network policy. |
|
|
Actors and Roles |
IRPManager as user |
|
|
Telecom resources |
3GPP management system (NM, EM). |
|
|
Assumptions |
3GPP management systems are running normally, scenarios and policy requirements are clearly defined. |
|
|
Pre conditions |
The systems is correctly configured and normally running. There is an active network policy stored in the IRPAgent. |
|
|
Begins when |
The IRPManager decides to deactive a policy. |
|
|
Step 1 (M) |
The IPRManager makes a decision to deactive the existing policy. |
|
|
Step 2 (M) |
After the completion of the policy deactivation process, the IRPAgent informs the IRPManager on the result of the process. |
|
|
Ends when |
Ends when all mandatory steps identified above are successfully completed or when an exception occurs. |
|
|
Exceptions |
One of the steps identified above fails. |
|
|
Post Conditions |
The policy is deactivated in the IRPAgent. |
|
|
Traceability |
REQ-POM-FUN -06 |
7.4.7 Reporting policy conflicts in the context of NFV
|
Use Case Stage |
Evolution / Specification |
<<Uses>> Related use |
|---|---|---|
|
Goal |
To query an existing network policy. |
|
|
Actors and Roles |
IRPManager as user |
|
|
Telecom resources |
3GPP management system (NM, EM). |
|
|
Assumptions |
3GPP management systems are running normally, scenarios and policy requirements are clearly defined. |
|
|
Pre conditions |
The systems is correctly configured and normally running. There is a network policy stored in the IRPAgent. |
|
|
Begins when |
The IRPManager decides to update a policy. |
|
|
Step 1 (M) |
The IPRManager makes a decision to query the existing policy. |
|
|
Step 2 (M) |
After the completion of the policy conflicts notification process, the IRPAgent informs the IRPManager on the result of the process. |
|
|
Ends when |
Ends when all mandatory steps identified above are successfully completed or when an exception occurs. |
|
|
Exceptions |
One of the steps identified above fails. |
|
|
Post Conditions |
The policy conflicts notification is returned to the IRPManager. |
|
|
Traceability |
REQ-POM-FUN -07 |