## 3 Simple Resource Algorithm
### Advertising Cloud Formulation
It includes a EUI-64 identification field to identify the object and an 8-bit netadmin field to manage the object on a network. * **Random Bit Field (16 bits):** This field provides unforgeability and helps uniquely identify the object. This field is generated after the type field, SYS field, property field, and Object ID field are created. When proxy certificates are created, a new random field is generated. This field also allows for easy revocation of capabilities by simply changing the random field and recomputing the hash field, hence revoking previous versions. * **Hash Field (16 bits):** This field detects the tampering of capabilities. When a capability is created, the type field, SYS field, property field, and Object ID field are first generated, followed by the random bit field. These fields are then used to generate a SHA-1 hash, which is placed in the Hash Field of the capability. As shown in Figure 6, the SYS field consists of the following bits:

* **Private or P bit:** Restricts the list of people holding the capability. With a public capability, only the capability for the object must be presented, allowing anyone to hold it without needing the identification of the subject, the person holding the capability. With a private capability, both the object's capability and the subject's capability must be presented to ensure the subject has the right to invoke the object. * **System or S bit:** Indicates whether the object involved was created by the system or by an application or user. A system capability cannot be modified or deleted by users or applications. * **Master or M bit:** Indicates that the capability was created by a Certificate Authority (CA). The master capability is usually created when the object is created. If this bit is not set, it means this is a proxy capability. Proxy capabilities are derived from master capabilities and cannot be derived from other proxy capabilities. * **Change or C bit:** Indicates whether this capability can be changed. If this bit is set, proxy capabilities can be derived from the master capability. If this bit is not set, the capability cannot be modified, and proxy capabilities cannot be generated. By adhering to these principles, Intelligent Edge Environments can maintain a high level of security and efficiency, ensuring that resources are managed effectively and that unauthorized access is prevented. ## 6 The Secure Service Protocol (SSP)

The advancement of highly mobile technologies such as Vehicular Adhoc Networks (VANETs), MEC, AI, ML, and IoT systems requires multiple interfaces to seamlessly connect and provide optimal performance for mobile users. As discussed in the Introduction, MEC facilitates moving services closer, minimizing the need for data processing on remote servers, reducing delays, and increasing network bandwidth. However, in order to allow

Figure 6: Capability structure—SYS FIELD. services to run from the edge of the network, it is essential to enable service migration to support these networks, allowing services to migrate as mobile users move around. Figure 7 is a visual representation of the change needed. In the old environment, the service provider had to manage the scaling and migration of services. In the new environment, these functions are now managed by the Service Management Framework (SMF). A new SMF for mobile services has been developed, as shown in Figure 8 and detailed in [16]. ### SMP Layers in Detail

* The Application Layer (AL) is the first layer of the SMF. It runs on the mobile node and calls the service through the Service Management Layer (SManL). AL provides the service name, Service ID, and the required QoS of the service it requires such as delay time, latency, bandwidth, reliability, and security. When a service first registers with the SMF, it is given a unique ID for identification and a service name which indicates the type of service being provided, and the resources such as CPU, Memory, or Storage needed to run the service.