このページは、お客様の言語ではご利用いただけません。Huawei Cloudは、より多くの言語バージョンを追加するために懸命に取り組んでいます。ご協力ありがとうございました。
- What's New
- Product Bulletin
- Service Overview
- Getting Started
-
User Guide
- Edge Computing with IEF
- Service Instances
-
User Guide (Professional)
- Node Management
-
End Device Management
- End Devices and Device Twins
- Device Templates
- End Devices
- Binding an End Device to an Edge Node
- Device Twin Working Principles
- Migrating Device Data to the Cloud
- Performing Security Authentication Using Certificate
-
MQTT Topics
- Device Twin Update
- Device Twin Delta
- Device Member Update
- Device Property Update
- Device Member Acquisition
- Device Member Acquisition Result
- Device Twin Acquisition
- Device Twin Acquisition Result
- Device Twin Modification
- Device Twin Modification Result
- Encryption Data Request
- Encryption Data Acquisition
- Alarm Reporting
- Alarm Clearance
- Custom Topics
- Containerized Application Management
- Edge-Cloud Messages
- Batch Management
- Auditing
- Permissions Management
-
User Guide (Platinum)
- Node Management
-
End Device Management
- End Devices and Device Twins
- Device Templates
- End Devices
- Binding an End Device to an Edge Node
- Device Twin Working Principles
- Migrating Device Data to the Cloud
- Performing Security Authentication Using Certificate
-
MQTT Topics
- Device Twin Update
- Device Twin Delta
- Device Member Update
- Device Property Update
- Device Member Acquisition
- Device Member Acquisition Result
- Device Twin Acquisition
- Device Twin Acquisition Result
- Device Twin Modification
- Device Twin Modification Result
- Encryption Data Request
- Encryption Data Acquisition
- Alarm Reporting
- Alarm Clearance
- Custom Topics
- Containerized Application Management
- Application Mesh
- Edge-Cloud Messages
- Batch Management
- Auditing
- Permissions Management
- Best Practices
-
API Reference
- Before You Start
- API Overview
- Calling APIs
-
API
-
Edge Node Management
- Registering an Edge Node
- Updating an Edge Node
- Querying Details About an Edge Node
- Querying a List of Edge Nodes
- Deleting an Edge Node
- Starting or Stopping an Edge Node
- Updating End Devices for an Edge Node
- Querying Node Certificates
- Creating a Node Certificate
- Deleting a Node Certificate
- Performing an Edge Node Upgrade Check
- Upgrading Edge Nodes
- End Device Management
- End Device Template Management
-
Application Template Management
- Creating an Application Template
- Updating an Application Template
- Querying Details About an Application Template
- Querying a List of Application Templates
- Deleting an Application Template
- Creating an Application Template Version
- Updating an Application Template Version
- Querying Details About an Application Template Version
- Querying a List of Application Template Versions
- Deleting an Application Version
- Deployment Management
- Tag Management
- ConfigMap Management
- Secret Management
- Endpoint Management
- Rule Management
- System Subscription Event Management
- Batch Node Management
- Batch Job Management
- Quota Management
- Service Management
-
Edge Node Management
- Data Structure
- Permissions Policies and Supported Actions
- Appendix
- Change History
- SDK Reference
-
FAQs
-
Edge Node FAQs
- What Do I Do If an Edge Node Is Faulty?
- What Are the Fault Scenarios of Edge Nodes?
- What Do I Do If Edge Node Management Fails?
- How Do I Obtain the Latest Device Properties After Device Properties Are Updated?
- What Operations Can I Perform After a Device Is Associated with a Node?
- Does an Edge Node Support Multiple GPUs?
- Can I Change the GPU on a Running Edge Node?
- How Is Edge Environment Security Protected?
- Why Cannot I View Monitoring Data on an Edge Node?
- How Can I Restore a Deleted Edge Node?
- What Is the Impact of IP Address Changing on an Edge Node?
- What Do I Do If the NTP Configuration Cannot Be Modified?
- How Do I Synchronize Time with the NTP Server?
- How Do I Obtain the IP Addresses of IEF Cloud Services?
- What Do I Do If the Edge Node Space Is Insufficient?
- How Do I Set Docker Cgroup Driver After Installing Docker on an Edge Node?
-
Edge Application FAQs
- What Do I Do If an Application Fails to Be Delivered to an Edge Node?
- What Do I Do If a Containerized Application Fails to Be Started on an Edge Node?
- What Do I Do If a Containerized Application Fails to Be Upgraded?
- What Do I Do If a Container Image Fails to Be Pulled?
- Why Cannot I View Application Logs and System Logs?
- How Do Applications Schedule GPU Resources?
- How Do I Control the Disk Space Occupied by a Container Engine?
- What Do I Do If a Containerized Application Cannot Access External IP Addresses
- What Do I Do If the Ascend AI Accelerator Card (NPU) Is Abnormal?
-
Edge-Cloud Message FAQs
- What Is Route Management?
- What Is a Message Endpoint in Route Management?
- What Is a Route?
- Why Does a Route Fail to Be Created?
- What Can I Do If a Message Fails to Be Forwarded over a Route?
- What Is the Impact of Disabling a Route?
- What Can I Do If SystemEventBus (MQTT Broker) of an Edge Node Fails to Be Connected?
- Network Management FAQs
- Basic Concept FAQs
-
Others
- Region and AZ
- What Are the Specifications of Edge Nodes Supported by IEF?
- What Are the Differences Between Device Properties and Device Twins?
- What Programming Language Is Required for IEF Development?
- Do I Need to Prepare Edge Nodes by Myself?
- Can I Still Use the Previously Delivered Applications After My Account Is in Arrears?
- What Are the Differences Between IEF and IoT Edge?
- What Do I Do If an Agency Fails to Be Automatically Created?
- How Can I Deal With Insufficient Permissions?
- How Will the Multi-AZ Reconstruction of SWR Application Container Image Data Affect IEF?
-
Edge Node FAQs
-
Edgectl User Guide
- Overview
- Installing edgectl
- Example: Using edgectl to Run Commands
-
edgectl Commands
- Querying the edgectl Version
- Managing the Product Lifecycle
-
Checking an Item
- Checking the Hardware Architecture
- Checking the CPU
- Checking the Memory
- Checking Hard Disks
- Checking the Domain Name Resolution Function
- Checking Docker
- Checking Network Connectivity
- Checking the Installation Status of the IEF Software
- Checking the Running Status of the IEF Software
- Checking GPUs
- Checking NPUs
- Checking Processes
-
Error Codes
- Error Code Overview
- Common Errors
- Permission Errors
-
OS Errors
- ERROR3001 Failed to obtain the hardware architecture
- ERROR3002 Unsupported hardware architecture
- ERROR3101 Failed to obtain the CPU information of the node
- ERROR3102 Failed to obtain the real-time CPU status of the node
- ERROR3103 Insufficient node CPU
- ERROR3201 Failed to obtain the memory information of the node
- ERROR3202 Insufficient node memory
- ERROR3301 Failed to obtain the disk information of the node
- ERROR3302 Insufficient disk space on the node
- ERROR3401 Failed to resolve the domain name
- ERROR3501 Failed to check the network
- ERROR3601 Failed to obtain the process information of the node
- ERROR3602 Failed to obtain the total number of processes on the node
- ERROR3603 Number of remaining processes on the node is insufficient
-
IEF Software Errors
- ERROR5001 Incomplete IEF software installation
- ERROR5002 IEF software is not completely running
- ERROR5003 Failed to read the IEF software configuration file
- ERROR5004 Docker is not enabled for the IEF software
- ERROR5005 Failed to start the IEF software
- ERROR5006 Failed to stop the IEF software
- ERROR5101 No application data found
- ERROR5102 No status data of the application found
- ERROR5103 Container is not started
- ERROR5104 Container exits abnormally
- ERROR5105 Failed to pull the container image
- ERROR5106 Container exits
- Third-Party Dependency Errors
- Data Collection Errors
- Internal Errors
- Videos
- General Reference
Copied.
Edge-Cloud Message Overview
IEF provides the function of routing messages exchanged between the edge and cloud. Based on configured routes, IEF forwards messages to the corresponding endpoint. In this way, messages can be forwarded based on specified paths, enhancing flexibility in data routing control and improves data security.
- Message endpoint: a party that sends or receives a message. It can be an end device or a cloud service.
- Message route: a message forwarding path.
Message Endpoints
IEF provides the following default message endpoints:
- SystemEventBus: MQTT broker on an edge node, which can communicate with other endpoints on behalf of the edge node. It can function as a source endpoint to send data to the cloud, or as a destination endpoint to receive messages from the cloud. MQTT topics on the edge node are used as endpoint resources of the MQTT broker.
- SystemREST: a REST gateway interface in the cloud. It can function as a source endpoint to send REST requests to the edge. REST request paths are used as endpoint resources of SystemREST.
You can also create the following message endpoints:
- Service Bus: an endpoint deployed on an edge node to process transaction requests. It can function as a destination endpoint to process file upload requests. REST request paths are used as endpoint resources of Service Bus.
- DIS: data injection service. It can function as a destination endpoint to receive data forwarded by IEF. DIS streams created in DIS are used as endpoint resources.
- API Gateway: API gateway service. It can function as a destination endpoint to receive data forwarded by IEF. API URLs created in API Gateway are used as endpoint resources.
Routes
Currently, IEF supports the following message forwarding paths:
- SystemREST -> Service Bus: The REST gateway interface in the cloud is called to obtain file services on edge nodes.
- SystemREST -> SystemEventBus: The REST gateway interface in the cloud is called to send messages to SystemEventBus (MQTT broker) on edge nodes.
- SystemEventBus -> DIS/API Gateway: You can publish end device data to a custom topic in the MQTT broker of an edge node. IEF forwards the device data to a DIS stream or an API Gateway address. Then, you can extract the data for processing and analysis. You must customize an MQTT topic when creating the route. For details about custom topics, see Custom Topics.
To use the message routing function, create endpoints and then create routes.
Creating an Endpoint
- Log in to the IEF console, and click Switch Instance on the Dashboard page to select a platinum service instance.
- In the navigation pane, choose Edge-Cloud Messages > Endpoints.
- Click Create Endpoint in the upper right corner, and set the endpoint parameters.
Figure 1 Creating an endpoint
- Type: Select an endpoint type. DIS, API Gateway, and Service Bus are supported.
- Name: Enter an endpoint name.
- Service Port: Available only for endpoints of the Service Bus type. Ranges from 1 to 65535.
- Click OK. The endpoint is successfully created and the endpoint list page is displayed.
Creating a Route
- Log in to the IEF console, and click Switch Instance on the Dashboard page to select a platinum service instance.
- In the navigation pane, choose Edge-Cloud Messages > Routes.
- Click Create Route in the upper right corner.
- Set the route parameters.
- Name: Enter a route name.
CAUTION:
Message routes and system subscriptions are of the same resource type. Their names cannot conflict with each other.
- Source Endpoint: Select a source endpoint, for example, SystemREST or SystemEventBus.
- Source Endpoint Resource: Select a source endpoint resource.
- When SystemREST is selected:
Enter the REST path, for example, /abc/ab.
- When SystemEventBus is selected:
Custom topic: Select a node and enter a topic.
Device data upload channel: Select a node and select the MQTT devices bound to the node.
NOTE:You can only select MQTT devices.
- When SystemREST is selected:
- Destination Endpoint: Select a destination endpoint, for example, SystemEventBus.
- Destination Endpoint Resource: Select a destination endpoint resource.
- Name: Enter a route name.
- Click Create. The route is successfully created and the route list page is displayed.
IEF forwards messages sent to the specified resource of the source endpoint to the specified resource of the destination endpoint based on the route.
Disabling or Enabling a Route
- To disable a route, click Disable in the row where the route resides.
After the route is disabled, IEF will not forward messages destined for the specified resource of the source endpoint.
- To enable a route, click Enable in the row where the route resides.
After the route is enabled, IEF will forward messages destined for the specified resource of the source endpoint.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot