Bu sayfa henüz yerel dilinizde mevcut değildir. Daha fazla dil seçeneği eklemek için yoğun bir şekilde çalışıyoruz. Desteğiniz için teşekkür ederiz.
IoT Device Access
IoT Device Access
- What's New
- Product Bulletin
- Service Overview
- Billing
-
Getting Started
-
Quick Device Access - Property Reporting and Command Receiving
- Subscribing to IoTDA
- Connecting a Smart Smoke Detector to the Platform (Quick Usage)
- Registering a Simulated Smart Street Light Device
- Using MQTT.fx to Simulate Communication Between the Smart Street Light and the Platform
- Using a Virtual Smart Street Light to Communicate with the Platform (Java SDK)
- Using a Virtual Smart Street Light to Communicate with the Platform (C SDK)
- Quick Device Access - Message Sending and Receiving
- Quick Application Access
-
Quick Device Access - Property Reporting and Command Receiving
-
User Guide
- Overview
- IoTDA Instances
- Resource Spaces
- Device Access
- Message Communications
- Device Management
-
Rules
- Overview
- Data Forwarding Process
- SQL Statements
- Connectivity Tests
- Data Forwarding to Huawei Cloud Services
- Data Forwarding to Third-Party Applications
- Data Forwarding Channel Details
- Data Forwarding Stack Policies
- Data Forwarding Flow Control Policies
- Abnormal Data Target
- Device Linkage
- Monitoring and O&M
- Granting Permissions Using IAM
-
Best Practices
- Introduction
-
Device Access
- Developing an MQTT-based Simulated Smart Street Light Online
- Developing a Smart Street Light Using NB-IoT BearPi
- Developing a Smart Smoke Detector Using NB-IoT BearPi
- Connecting and Debugging an NB-IoT Smart Street Light Using a Simulator
- Developing a Protocol Conversion Gateway for Access of Generic-Protocol Devices
- Connecting a Device That Uses the X.509 Certificate Based on MQTT.fx
- Connecting to IoTDA Based on the BearPi-HM_Nano Development Board and OpenHarmony 3.0
- Testing MQTT Performance Using JMeter
- Device Management
- Data Forwarding
- Device Linkage
-
Developer Guide
- Before You Start
- Obtaining Resources
- Product Development
- Development on the Device Side
- Development on the Application Side
-
API Reference
-
API Reference on the Application Side
- Before You Start
- Calling APIs
- API Overview
-
API
- Product Management
- Device Management
- Device Message
- Device Command APIs
- Device Property
- AMQP Queue Management
- Access Credential Management
- Data Forwarding Rule Management
-
Transition Data
- Push a Device Status Change Notification
- Push a Device Property Reporting Notification
- Push a Device Message Status Change Notification
- Push a Batch Task Status Change Notification
- Push a Device Message Reporting Notification
- Push a Device Addition Notification
- Push a Device Update Notification
- Push a Device Deletion Notification
- Push a Product Addition Notification
- Push a Product Update Notification
- Push a Product Deletion Notification
- Push an Asynchronous Device Command Status Change Notification
- Rule Management
- Device Shadow
- Group Management
- Tag Management
- Instance Management
- Resource Space Management
- Batch Task
- Device CA Certificate Management
- OTA Upgrade Package Management
- Message Broadcasting
- Device Tunnel Management
- Stack policy management
- Flow control policy management
- Device Proxy
- Device Policy Management
- Bridge Management
- Pre-provisioning Template Management
- Custom Authentication
- Codec Function Management
- Permissions and Supported Actions
- Examples
- Appendix
-
MQTT or MQTTS API Reference on the Device Side
- Before You Start
- Communication Modes
- Topics
- Device Connection Authentication
- Device Commands
- Device Messages
- Device Properties
-
Gateway and Child Device Management
- Platform Notifying a Gateway of New Child Device Connection
- Platform Notifying a Gateway of Child Device Deletion
- Gateway Synchronizing Child Device Information
- Gateway Updating Child Device Status
- Responding to a Request for Updating Child Device Statuses
- Gateway Requesting for Adding Child Devices
- Platform Responding to a Request for Adding Child Devices
- Gateway Requesting for Deleting Child Devices
- Platform Responding to a Request for Deleting Child Devices
- Software and Firmware Upgrade
- File Upload and Download
- Device Time Synchronization
- Device Reporting Information
- Device Log Collection
- Remote Configuration
- Device Tunnel Management
- HTTPS API Reference on the Device Side
- LwM2M API Reference on the Device Side
- Security Tunnel WebSocket API Reference
- Module AT Command Reference
- Change History
-
API Reference on the Application Side
- SDK Reference
-
FAQs
- Top FAQs
-
Solution Consulting
- In What Scenarios Can the IoT Platform Be Applied?
- What Are the Changes Brought by the Integration of IoT Device Management and IoTDA?
- Can I Enable IoTDA for IAM Users or Sub-Projects?
- Which Regions of Huawei Cloud Are Supported by the IoT Platform?
- Does Huawei Provide Modules, Hardware Devices, and Application Software?
- What Should I Do If I Want to Call an API But Have No Permissions to Do So as an IAM User? (Is It Edition-specific?)
- Why Was I Prompted to Grant Security Administrator Permissions When I Create a Rule or Set Resource File Storage?
- Which Resource Space Will Be Set As Default on the IoT Platform?
- How Does IoTDA Obtain Device Data?
- Is There Any Limitation on the Number of Resource Spaces and Devices I Can Add on the IoT Platform?
- Does the IoTDA Support Device Registration in Batches?
- Are There Any Limitations on the Use of the IoT Platform?
- What DTLS Encryption Algorithms Are Supported by the IoT Platform?
- Does the IoT Platform Support Conversion Between Big-Endian and Little-Endian for Binary Data?
- What Is NB-IoT?
- What Are the Components of the IoT Platform and What Hardware Architectures Does It Support?
- How Do I Obtain the Platform Access Address?
- Device Integration
- IoT Device SDKs
- LwM2M/CoAP Device Access
- MQTT-based Device Access
- Products Models
- Message Communications
- Subscription and Push
- Codecs
- OTA Upgrades
- Application Integration
- General Reference
On this page
Help Center/
IoT Device Access/
User Guide/
Rules/
Data Forwarding to Third-Party Applications/
AMQP Data Forwarding/
C# SDK Access Example
Copied.
C# SDK Access Example
This topic describes how to connect an AMQP.Net Lite client to the IoT platform and receive subscribed messages from the platform.
Requirements for the Development Environment
.NET Framework 4.6 or later has been installed.
Obtaining the Java SDK
1. Right-click the project directory and choose Manage NuGet Packages.
2. In the NuGet manager, search for AmqpNetLite and install the required version.
Sample Code
For details about the parameters in the demo, see AMQP Client Access.
using Amqp; using Amqp.Framing; using Amqp.Sasl; using System; using System.Threading; namespace AmqpDemo { class Program { /// <summary> /// Access domain name. For details, see "AMQP Client Access". /// See Connection Configuration Parameters. /// </summary> static string Host = "${Host}"; /// <summary> /// Port /// </summary> static int Port = 5671; /// <summary> /// Access key /// </summary> static string AccessKey = "${YourAccessKey}"; /// <summary> /// Access code /// </summary> static string AccessCode = "${yourAccessCode}"; /// <summary> /// Instance ID. This parameter is required when multiple instances of the Standard Edition are purchased in the same region. /// </summary> static string InstanceId = "${instanceId}"; /// <summary> /// Queue name /// </summary> static string QueueName = "${yourQueue}"; static Connection connection; static Session session; static ReceiverLink receiverLink; static DateTime lastConnectTime = DateTime.Now; static void Main(string[] args) { try { connection = CreateConnection(); // Add a connection exception callback. connection.AddClosedCallback(ConnectionClosed); // Create a session. var session = new Session(connection); // Create a receiver link. receiverLink = new ReceiverLink(session, "receiverName", QueueName); // Receive a message. ReceiveMessage(receiverLink); } catch (Exception e) { Console.WriteLine(e); } // Press Enter to exit the program. Console.ReadLine(); ShutDown(); } /// <summary> /// Create a connection. /// </summary> /// <returns>Connection</returns> static Connection CreateConnection() { lastConnectTime = DateTime.Now; long timestamp = new DateTimeOffset(DateTime.UtcNow).ToUnixTimeMilliseconds(); string userName = "accessKey=" + AccessKey + "|timestamp=" + timestamp + "|instanceId=" + InstanceId; Address address = new Address(Host, Port, userName, AccessCode); ConnectionFactory factory = new ConnectionFactory(); factory.SASL.Profile = SaslProfile.External; // Trust the server and skip certificate verification. factory.SSL.RemoteCertificateValidationCallback = (sender, certificate, chain, sslPolicyError) => { return true; }; factory.AMQP.IdleTimeout = 8000; factory.AMQP.MaxFrameSize = 8 * 1024; factory.AMQP.HostName = "default"; var connection = factory.CreateAsync(address).Result; return connection; } static void ReceiveMessage(ReceiverLink receiver) { receiver.Start(20, (link, message) => { // Process the message in the thread pool to prevent the thread that pulls the message from being blocked. ThreadPool.QueueUserWorkItem((obj) => ProcessMessage(obj), message); // Return an ACK message. link.Accept(message); }); } static void ProcessMessage(Object obj) { if (obj is Message message) { string body = message.Body.ToString(); Console.WriteLine("receive message, body=" + body); } } static void ConnectionClosed(IAmqpObject amqpObject, Error e) { // Reconnection upon disconnection ThreadPool.QueueUserWorkItem((obj) => { ShutDown(); int times = 0; while (times++ < 5) { try { Thread.Sleep(1000); connection = CreateConnection(); // Add a connection exception callback. connection.AddClosedCallback(ConnectionClosed); // Create a session. session = new Session(connection); // Create a receiver link. receiverLink = new ReceiverLink(session, "receiverName", QueueName); // Receive a message. ReceiveMessage(receiverLink); break; } catch (Exception exception) { Console.WriteLine("reconnect error, exception =" + exception); } } }); } static void ShutDown() { if (receiverLink != null) { try { receiverLink.Close(); } catch (Exception e) { Console.WriteLine("close receiverLink error, exception =" + e); } } if (session != null) { try { session.Close(); } catch (Exception e) { Console.WriteLine("close session error, exception =" + e); } } if (connection != null) { try { connection.Close(); } catch (Exception e) { Console.WriteLine("close connection error, exception =" + e); } } } } }
Parent topic: AMQP Data Forwarding
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.
The system is busy. Please try again later.
For any further questions, feel free to contact us through the chatbot.
Chatbot