diff --git a/05-osm-usage.md b/05-osm-usage.md
index 4bdba9078a2ead0c78d3e510fd203181bc8242f6..282f3bb521413f8fcf16b2773d8e2562138426e8 100644
--- a/05-osm-usage.md
+++ b/05-osm-usage.md
@@ -522,6 +522,20 @@ These charms can run with three scopes:
 - VNF: running globally for the VNF, for the management VDU that represents it.
 - NS: running for the whole NS, after VNFs have been configured, to handle interactions between them.
 
+Depending on the scope of charms, the charm application naming differs:
+
+- **The VNF level** charm application name is prepared by combining the relevant execution environment name and vnf-profile-id.
+- **The VDU level** charm application name includes vdu-profile-id as an identifier together with the relevant execution environment name and vnf-profile-id that it belongs.
+- **The NS level** charm application name is identified with the charm name. 
+
+The structure of charm application name makes the charm more apparent. Besides, it makes the VDU/KDU more visible by looking through the related charm. The structure of charm application names which are limited with 50 characters, are described below according to scope of charms:
+
+```bash
+NS level: <charm-name>-ns
+VNF level: <ee-name>-z<vnf-ordinal-scale-number>-<vnf-profile-id>-vnf
+VDU level: <ee-name>-z<vnf-ordinal-scale-number>-<vnf-profile-id>-<vdu-profile-id>-z<vdu-ordinal-scale-number>-vdu
+```
+            
 For detailed instructions on how to add cloud-init or charms to your VNF, visit the following references:
 
 - [VNF Onboarding Guidelines, Day-0](https://osm.etsi.org/docs/vnf-onboarding-guidelines/02-day0.html)