Southbound routing downlink processing method and device of internet of things platform, equipment and medium

Abstract

Embodiments of the present application disclose a kind of Internet of Things platform's southbound route downlink processing method, device, equipment and medium.The method comprises: adding the device IP and device port of to-be-connected device;Receive the device data reported by to-be-connected device, if the IP attached to the device data is successfully matched with the device IP, then add temporary label to the downlink service message returned to the to-be-connected device, the temporary label includes the device IP and the device port;When the service message is returned to the to-be-connected device according to static route, replace the IP of the static route according to the device IP in the temporary label, so that the service message is returned to the to-be-connected device according to the device IP and the device port.The present application can improve the downlink interaction capability of multiple device IP addresses accessing to platform, ensure that multiple IP devices can return message to device side smoothly, and ensure the uplink and downlink of service.

Description

Technical Field

[0001] This invention relates to the field of Internet of Things (IoT) platform technology, and in particular to a southbound routing downlink processing method, apparatus, device, and medium for an IoT platform. Background Technology

[0002] Currently, there are numerous IoT platforms on the market, with tens of thousands of notebook devices connecting to various IoT platform brands. Each device's IP address is a point-to-point address, already stored in the device's address carrier Flash memory at the factory and deployed in the production environment. Adjusting the access address's IP requires unified adjustments to firmware updates, device module decoupling, production line adjustments, and ensuring the uniformity of the routing Dnat / Snat policy. Without adjusting the device carrier IP and port, after multiple devices connect to the platform and report data, the downlink service cannot correctly return to the source device address. Summary of the Invention

[0003] This invention provides a method, apparatus, device, and medium for southbound routing downlink processing on an IoT platform, aiming to solve the problem that downlink device services on existing IoT platforms cannot return to the source device address normally.

[0004] In a first aspect, embodiments of the present invention provide a southbound routing downlink processing method for an IoT platform, comprising: adding a device IP and a device port of a device to be connected; receiving device data reported by the device to be connected; if the IP attached to the device data matches the device IP, adding a temporary tag to the downlink service message returned to the device to be connected, the temporary tag including the device IP and the device port; when the service message is returned to the device to be connected according to a static route, replacing the IP of the static route with the device IP in the temporary tag, so that the service message is returned to the device to be connected according to the device IP and the device port.

[0005] Secondly, embodiments of the present invention also provide a southbound routing downlink processing apparatus for an IoT platform, comprising: an adding unit for adding a device IP and a device port of a device to be accessed; a tagging unit for receiving device data reported by the device to be accessed, wherein if the IP attached to the device data matches the device IP, a temporary tag is added to the downlink service message returned to the device to be accessed, the temporary tag including the device IP and the device port; and a replacement unit for replacing the IP of the static route according to the device IP in the temporary tag when the service message is returned to the device to be accessed according to the static route, so that the service message is returned to the device to be accessed according to the device IP and the device port.

[0006] Thirdly, embodiments of the present invention also provide a computer device, which includes a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the method described in the first aspect.

[0007] Fourthly, embodiments of the present invention also provide a computer-readable storage medium storing a computer program, the computer program including program instructions that, when executed by a processor, can implement the method described in the first aspect.

[0008] This invention provides a method, apparatus, device, and medium for southbound routing downlink processing on an IoT platform. The method includes: adding the device IP and device port of a device to be connected; receiving device data reported by the device to be connected; if the IP attached to the device data matches the device IP, adding a temporary tag to the downlink service message returned to the device to be connected, the temporary tag including the device IP and the device port; when the service message is returned to the device to be connected according to a static route, replacing the IP of the static route with the device IP in the temporary tag, so that the service message is returned to the device to be connected according to the device IP and device port. This invention's technical solution, by adding a temporary tag to the downlink service message returned to the device to be connected and replacing the IP of the static route with the device IP in the temporary tag, enables the service message to be returned normally to the device to be connected, improving the downlink interaction capability of multiple device IP addresses accessing the platform and ensuring smooth uplink and downlink services. Attached Figure Description

[0009] To more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings used in the following description of the embodiments will be briefly introduced. Obviously, the drawings described below are some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0010] Figure 1 A schematic diagram illustrating an application scenario of the southbound routing downlink processing method for an IoT platform provided in an embodiment of the present invention;

[0011] Figure 2 A flowchart illustrating the southbound routing downlink processing method of the Internet of Things platform provided in this embodiment of the invention;

[0012] Figure 3 A schematic diagram of a sub-process of the southbound routing downlink processing method of the Internet of Things platform provided in an embodiment of the present invention;

[0013] Figure 4A flowchart illustrating a southbound routing downlink processing method for an IoT platform provided in another embodiment of the present invention;

[0014] Figure 5 A schematic diagram of a sub-process of the southbound routing downlink processing method of the Internet of Things platform provided in an embodiment of the present invention;

[0015] Figure 6 A schematic diagram of a sub-process of the southbound routing downlink processing method of the Internet of Things platform provided in an embodiment of the present invention;

[0016] Figure 7 This is a flowchart illustrating the southbound routing downlink processing method of an IoT platform provided in another embodiment of the present invention;

[0017] Figure 8 A schematic block diagram of a southbound routing downlink processing device for an IoT platform provided in an embodiment of the present invention;

[0018] Figure 9 A schematic block diagram of a computer device provided for an embodiment of the present invention. Detailed Implementation

[0019] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of the present invention. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0020] It should be understood that, when used in this specification and the appended claims, the terms "comprising" and "including" indicate the presence of the described features, integrals, steps, operations, elements and / or components, but do not exclude the presence or addition of one or more other features, integrals, steps, operations, elements, components and / or collections thereof.

[0021] It should also be understood that the terminology used in this specification is for the purpose of describing particular embodiments only and is not intended to limit the invention. As used in this specification and the appended claims, the singular forms “a,” “an,” and “the” are intended to include the plural forms unless the context clearly indicates otherwise.

[0022] It should also be further understood that the term "and / or" as used in this specification and the appended claims refers to any combination of one or more of the associated listed items and all possible combinations, and includes such combinations.

[0023] Please see Figure 1 , Figure 1This is a schematic diagram illustrating an application scenario of the southbound routing downlink processing method for an IoT platform provided in this embodiment of the invention. The application scenario includes a southbound NB device 10, an IoT platform 20, and a northbound application platform 30. The southbound NB device is an IoT terminal hardware device, such as a water meter, electricity meter, or gas meter. The northbound application platform is an application server providing business processing, such as a SaaS platform. The IoT platform is a management platform for exchanging data and signaling between the southbound device and the northbound application, managing the device data of the southbound NB device, and simultaneously opening interfaces to third-party application systems, allowing various applications to quickly build their own IoT services. In this embodiment, the data interaction process between the southbound NB device, the IoT platform, and the northbound application platform is as follows: First, the southbound NB device provides the collected device data to the IoT platform via the uplink data link. After receiving the device data, the IoT platform parses it and then reports the device data to the northbound application platform. The northbound application platform performs corresponding business processing based on the device data and then returns the processed business message to the southbound NB device via the downlink data link of the IoT platform. The IoT platform in this embodiment is capable of deployment, device access, and application management for government agencies, equipment manufacturers, developers, large gas companies, water companies, etc. Developers do not need to consider issues such as underlying infrastructure expansion, routing NAT policies, data management and aggregation, communication protocols, and communication security. The IoT platform has the capability to manage the downlink IP service flow of southbound NB devices already connected to the platform, and supports downlink interaction capabilities for multiple vendors and existing legacy devices with IP addresses connected to the platform.

[0024] The following provides a detailed explanation of the southbound routing downlink processing method for the aforementioned IoT platform. For example... Figure 2 As shown, the method includes the following steps S110-S140.

[0025] S110, Add the device IP and device port of the device to be connected.

[0026] In this embodiment, the devices to be connected are existing, older southbound notebook (NB) devices, such as water meters, electricity meters, and gas meters. Different devices to be connected have different device IPs. Therefore, to unify the downlink service management of all NB devices, the IoT platform first needs to add the device IP and device port of each device to be connected to the platform. Each device to be connected is identified based on its device IP and device port, and only then can specific processing measures be implemented. Each device to be connected has its corresponding device information, including its device IP and device port. For example, the device IP might be IP10.xx.xx.xx1.1.2, and the port might be 80. Adding the device IP and device port also means storing the device IP and device port in the IoT platform's device management center.

[0027] In one embodiment, such as Figure 3 As shown, step S110 includes: S111-S112.

[0028] S111. Create a new IP sub-table in the preset database;

[0029] S112. Insert the device IP into the IP sub-table.

[0030] In this embodiment, a pre-defined database is provided in the IoT platform to store device information for all devices to be connected. This device information includes multiple items, such as device IP and device port. Each item of device information is stored in a corresponding sub-table. For example, in this embodiment, the device IP of a newly added device to be connected is stored in an IP sub-table. Specifically, when storing the device IP, the device IP is inserted as a key in the IP sub-table. This allows the IP to be used to associate with other sub-tables, enabling one-to-many search queries by querying the IP.

[0031] In another embodiment, such as Figure 4 As shown, the southbound routing downlink processing method of the IoT platform further includes steps S113-S114.

[0032] S113. Record the device information of the device to be accessed and store the device information in the corresponding sub-table. The device information includes IMEI information, user ID, resident ID information, and billing information.

[0033] S114. Establish a one-to-many sub-table relationship between the IP sub-table and multiple sub-tables corresponding to the device information.

[0034] In this embodiment, in addition to processing the device IP and device port of the device to be connected, the device information processing also includes IMEI information, user ID, resident ID information, and billing information. IMEI information refers to the International Mobile Equipment Identity (IMEI), used to identify the device. The user ID is used to identify the customer. The resident ID information indicates which resident's home the device is installed in; for example, it can be represented by an ID card or a house number. The billing information is used to track the usage of the device. In addition to processing the device IP and device port of the device to be connected in the device management center, IMEI information, user ID, resident ID information, and billing information are also added. Specifically, this information is recorded, and corresponding sub-tables are created in a preset database. These sub-tables store the information one-to-one. For example, an IMEI information sub-table, a user ID sub-table, a resident ID information sub-table, and a billing information sub-table are created. IMEI information is stored in the IMEI information sub-table, user ID information is stored in the user ID sub-table, resident ID information is stored in the resident ID sub-table, and billing information is stored in the billing information sub-table. Then, a one-to-many sub-table relationship is established between the IP sub-table and the IMEI information sub-table, user ID sub-table, resident ID information sub-table, and billing information sub-table. Through this one-to-many sub-table relationship, it is possible to query the corresponding IMEI information, user ID, resident ID information, and billing information using an IP address. Of course, it is understood that in other embodiments, this device information can all be stored in a single data table, with key-value pairs linked using the IP address as the primary key, thereby enabling queries. The specific storage method chosen is not limited here; it is merely presented as a preferred and optional embodiment.

[0035] S120. Receive device data reported by the device to be accessed. If the IP address attached to the device data matches the device IP address, add a temporary tag to the downlink service message returned to the device to be accessed. The temporary tag includes the device IP address and the device port.

[0036] In this embodiment, the southbound NB device reports the collected device data to the IoT platform. Device data includes, for example, gas usage data from gas meters, domestic water usage data from water meters, and electricity usage data from electricity meters. The device data includes an IP address, which is matched against previously added device IPs. If a match is found, the device is identified as a device to be connected, i.e., an existing, older device. After identifying these devices, they are tagged. Specifically, a temporary tag is added before the business message, i.e., the temporary tag is appended to the payload. This temporary tag includes the device IP and port of the device to be connected. The business message refers to the message returned by the northbound application platform to the device to be connected after processing through the IoT platform.

[0037] In another embodiment, the southbound routing downlink processing method of the IoT platform further includes the step of: if device data reported by multiple devices to be accessed is received, the temporary tag is added in a distributed queue manner.

[0038] In this embodiment, when a large number of older southbound NB devices are connected to the physical platform, after these devices report their data, the IoT platform needs to tag multiple downlink service messages. If the number of tagging tasks is too large, it can cause congestion and lead to untimely data transmission. Therefore, to avoid data delays and improve message transmission rates, this embodiment uses a distributed queue approach for tagging tasks. The distributed queue executes the task of adding temporary tags in parallel through multi-threaded asynchronous processing, thereby improving the immediacy of message transmission.

[0039] In one embodiment, such as Figure 5 As shown, step S120 includes: S121-S123.

[0040] S121. Resolve the protocol layer address reported by the device data to obtain the IP address attached to the device data;

[0041] S122. Match the IP address attached to the device data with the IP sub-table;

[0042] S123. If the same matching result exists, a temporary tag is added to the downlink service message returned to the device to be accessed.

[0043] In this embodiment, after the device data of these devices to be connected is reported and processed by policy routing, the IoT platform parses the protocol layer address reported by the devices to be connected, thereby resolving the IP address and port attached to the device data. Then, the IP address is matched with the IP sub-table storing device IPs and the port sub-table storing ports in the preset database. If the same IP and port exist in the IP sub-table and the port sub-table, it means that the match is successful and there is a matching result. In this case, the processing operation of adding a temporary tag to the business message is triggered.

[0044] S130 When the service message is returned to the device to be accessed according to the static route, the IP of the static route is replaced according to the device IP in the temporary tag, so that the service message is returned to the device to be accessed according to the device IP and the device port.

[0045] In this embodiment, the IoT platform returns the business message to the device to be connected via static routing. During the process of returning the business message, the device IP in the temporary tag will be forcibly replaced by the IP in the static route, so that the business message can point to the source address, that is, the device to be connected, thereby ensuring that the message can be successfully returned to the device side.

[0046] In one embodiment, such as Figure 6 As shown, step S130 includes: S131-S133.

[0047] S131. During a short connection session with the device to be accessed, replace the IP address of the static route with the device IP address in the temporary label;

[0048] S132. If the short connection session fails, match the user ID and IMEI information stored in the sub-table with the device information of the device to be accessed.

[0049] S133. If the match is successful, return to the step of replacing the IP of the static route with the device IP in the temporary label.

[0050] In this embodiment, the temporary tag device IP replacement process specifically involves the IoT platform establishing a short connection session with the device to be accessed. During this short connection session, the route-assigned IP is resolved and replaced, thus successfully returning the message to the device. If the short connection fails, the IoT platform will re-establish a connection with the device and perform an acknowledgment to ensure that the device is the one corresponding to the service message. This acknowledgment involves matching the device information of the device with user IDs, IMEIs, and other information in various sub-tables of a preset database. If a user ID and IMEI matching the one of the devices exists in any of the sub-tables of the preset database, the match is successful, indicating that the device is the one corresponding to the service message to be returned. After confirmation, the IP replacement process is initiated again, thus returning the service message to the device. This re-initiation process takes less than 10 milliseconds.

[0051] In another embodiment, such as Figure 7 As shown, the southbound routing downlink processing method of the IoT platform further includes steps S141-S143.

[0052] S141. Parse the protocol layer address reported by the device data to obtain the address ID and port ID fields;

[0053] S142. Based on the address ID and port ID fields, the URL address to be pushed is matched from the preset database;

[0054] S143. Push the device data to the northbound application platform for business processing according to the URL address.

[0055] In this embodiment, the northbound application platform, which provides various software services (essentially an app), needs to receive device data from NB devices for corresponding business processing. This includes, for example, billing water meter usage, processing gas meter top-ups, and handling electricity meter account openings. Therefore, the IoT platform needs to send device data to the corresponding northbound application platform. Specifically, the protocol layer address of the reported device data is parsed to obtain address ID and port ID fields (or other queryable fields). Then, the address ID and port ID fields are matched against a pre-defined database. This database stores a URL sub-table containing the URLs of the northbound application platforms being pushed to it. This URL sub-table is associated with the IP and port sub-tables. Therefore, the URLs of the corresponding northbound application platforms in the URL sub-table can be matched using the address ID and port ID fields. The matched URLs are then pushed to the northbound application platform for further business processing.

[0056] In addition, it should be noted that after the device data is pushed to the northbound SaaS by the IoT platform, and then the command is sent to the physical network platform, it will be processed according to the command queue. At the same time, the user ID, IMEI, and the replaced tag IP and port are confirmed again. After the information is matched, the downlink service is sent back to the designated IP device side.

[0057] The technical solution of this invention mainly includes key steps such as address addition, message reporting tagging, and overriding static routing addresses. Adding an address involves adding the IP address and port of the southbound NB device. Message reporting tagging involves matching the IP address of the device's reported message with the address database, calculating the address and port to be pushed to the downlink message, and attaching a tag to the message according to a policy. Overriding static routing addresses involves replacing the policy-assigned address with the IP address and port from the tag, and then returning the device message downlink to the specified IP address. Multi-IP queue processing involves asynchronously and multi-threadedly returning the IP address to the device side after multiple IP devices are tagged. For ease of understanding, this invention will further provide a specific example to illustrate the processing flow of this embodiment, as follows:

[0058] For example:

[0059] 1) Prepare 3 identical southbound NB devices with different IP addresses and ports, including 1 China Telecom IoT SIM card, 1 China Mobile IoT SIM card, and 1 China Unicom IoT SIM card.

[0060] 2) The device information for these three devices has been deleted from the original device addition platform.

[0061] 3) Add 3 IPs and ports to the components on the platform side, and add 3 device information in the device management section.

[0062] 4) Establish a core network virtual tunnel address. On side A, the core network external interconnection address of the base stations of the three operators is established. On the customer side, the core network B-end address is established through a many-to-one relationship to establish a core network virtual tunnel.

[0063] 5) Start device data reporting. The first interaction establishes a session. The sub-database establishes the corresponding device IP and information, and records the PGW information of the three different core networks of the operator, the device protocol layer address IP port, resident ID, IMEI, IMSI, etc.

[0064] 6) Begin assigning message tags to different IPs. Using information from sub-tables, start labeling with virtual tags and perform static policy IP replacement. After acquisition, push the data to the SaaS or data southbound cloud platform according to the IoT platform's push mechanism, and connect to a third party.

[0065] 7) During the downlink return of 3 IP messages, obtain the previous virtual tag IP, using the algorithm formula (\d{1,3}\.\d{1,3}\.\d{1,3}\.\d{1,3}):(\d{1,5}) or perform temporary IP update processing on the corresponding device through the IMEI of the sub-table.

[0066] 8) Finally, the virtual IP and payload are sent back to the platform.

[0067] The southbound routing downlink processing method of the IoT platform provided in this embodiment of the invention adds the IP address and port of the device to be connected. After the device completes data reporting through the routing policy, the IP address attached to the message will be matched one-to-one by the IoT platform. The matching database is based on the IP addresses of the devices added in the early stage. Upon successful matching, a temporary tag is assigned to the device, containing the device address and port number. When the device begins processing downlink business messages, the IP and port of the temporary tag are appended to the message packet, replacing the IP address processed by the static routing policy. After the router identifies the downlink push address and port, the message is sent back to the device normally. This addresses the issue of downlink business failing to return to the source device address after multiple devices access the platform for data reporting without adjusting the device carrier IP and port. It enables unified downlink business management for massive amounts of existing and newly added device IPs for large state-owned enterprises, equipment manufacturers, and government agencies. It allows for multi-IP existing device access processing on a private cloud platform with static routing and firewalls, resolving the impact of Dnat and Snat on unified processing of a single IP. This ensures that multiple IP devices can successfully send messages back to the device side, guaranteeing smooth uplink and downlink business operations. It also solves the problem of adjusting IP addresses when replacing device firmware modules and production business lines, allowing for flexible unified downlink management of multiple IPs on IoT platforms with southbound routing downlink policy components.

[0068] Figure 8 This is a schematic block diagram of a southbound routing downlink processing device 200 for an Internet of Things (IoT) platform provided in an embodiment of the present invention. Figure 8 As shown, corresponding to the southbound routing downlink processing method for the above-described IoT platform, the present invention also provides a southbound routing downlink processing apparatus 200 for an IoT platform. This southbound routing downlink processing apparatus 200 includes a unit for executing the aforementioned southbound routing downlink processing method for the IoT platform, and the apparatus can be configured within the IoT platform. Specifically, please refer to... Figure 8 The southbound routing downlink processing device 200 of the IoT platform includes: an adding unit 201, a tag unit 202, and a replacement unit 203.

[0069] The system includes an adding unit 201 for adding the device IP and device port of the device to be accessed; a tagging unit 202 for receiving device data reported by the device to be accessed, and if the IP attached to the device data matches the device IP, adding a temporary tag to the downlink service message returned to the device to be accessed, the temporary tag including the device IP and the device port; and a replacement unit 203 for replacing the IP of the static route with the device IP in the temporary tag when the service message is returned to the device to be accessed according to the static route, so that the service message is returned to the device to be accessed according to the device IP and the device port.

[0070] In one embodiment, the adding unit 201 includes a first creating unit and an inserting unit.

[0071] The first creation unit is used to create a new IP sub-table in a preset database; the insertion unit is used to insert the device IP into the IP sub-table.

[0072] In one embodiment, the southbound routing downlink processing device 200 of the IoT platform further includes a second creation unit and an establishment unit.

[0073] The second creation unit is used to record the device information of the device to be accessed and store the device information in the corresponding sub-table. The device information includes IMEI information, user ID, resident ID information, and billing information. The establishment unit is used to establish a one-to-many sub-table relationship between the IP sub-table and the multiple sub-tables corresponding to the device information.

[0074] In one embodiment, the tag unit 202 includes a first parsing unit, a first matching unit, and a tag subunit.

[0075] The first parsing unit is used to parse the protocol layer address reported by the device data to obtain the IP address attached to the device data; the first matching unit is used to match the IP address attached to the device data with the IP sub-table; and the tagging sub-unit is used to add a temporary tag to the downlink service message returned to the device to be accessed if there is a matching result.

[0076] In one embodiment, the replacement unit 203 includes a replacement subunit, a second matching unit, and a return execution unit.

[0077] The system includes a replacement subunit, used to replace the IP address of the static route with the device IP address in the temporary tag during a short connection session with the device to be accessed; a second matching unit, used to match the user ID and IMEI information stored in the sub-table with the device information of the device to be accessed if the short connection session fails; and a return execution unit, used to return to the step of replacing the IP address of the static route with the device IP address in the temporary tag if the matching is successful.

[0078] In one embodiment, the southbound routing downlink processing device 200 of the IoT platform further includes a second parsing unit, a third matching unit, and a push unit.

[0079] The second parsing unit is used to parse the protocol layer address reported by the device data to obtain the address ID and port ID fields; the third matching unit is used to match the URL address to be pushed from a preset database based on the address ID and port ID fields; and the push unit is used to push the device data to the northbound application platform for business processing based on the URL address.

[0080] In one embodiment, the southbound routing downlink processing device 200 of the IoT platform further includes a distributed unit.

[0081] The distributed unit is used to add the temporary tag in a distributed queue if it receives device data reported by multiple devices to be connected.

[0082] It should be noted that those skilled in the art can clearly understand that the specific implementation process of the southbound routing downlink processing device 200 and each unit of the above-mentioned IoT platform can be referred to the corresponding description in the aforementioned method embodiments. For the sake of convenience and brevity, it will not be repeated here.

[0083] The southbound routing downlink processing device of the aforementioned IoT platform can be implemented as a computer program, which can, for example... Figure 9 It runs on the computer device shown.

[0084] Please see Figure 9 , Figure 9 This is a schematic block diagram of a computer device provided in an embodiment of this application.

[0085] See Figure 9 The computer device 500 includes a processor 502, a memory, and a network interface 505 connected via a system bus 501. The memory may include a non-volatile storage medium 503 and internal memory 504.

[0086] The non-volatile storage medium 503 may store an operating system 5031 and a computer program 5032. The computer program 5032 includes program instructions that, when executed, cause the processor 502 to perform a southbound routing downlink processing method for an Internet of Things (IoT) platform.

[0087] The processor 502 provides computing and control capabilities to support the operation of the entire computer device 500.

[0088] The internal memory 504 provides an environment for the operation of the computer program 5032 in the non-volatile storage medium 503. When the computer program 5032 is executed by the processor 502, the processor 502 can execute a southbound routing downlink processing method for an Internet of Things platform.

[0089] This network interface 505 is used for network communication with other devices. Those skilled in the art will understand that... Figure 9 The structure shown is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the computer device 500 to which the present application is applied. The specific computer device 500 may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.

[0090] The processor 502 is used to run a computer program 5032 stored in a memory to implement any embodiment of the southbound routing downlink processing method of the IoT platform described above.

[0091] It should be understood that in the embodiments of this application, the processor 502 may be a central processing unit (CPU), or it may be other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or any conventional processor.

[0092] It will be understood by those skilled in the art that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The computer program includes program instructions and can be stored in a storage medium, which is a computer-readable storage medium. The program instructions are executed by at least one processor in the computer system to implement the process steps of the embodiments of the above methods.

[0093] Therefore, the present invention also provides a storage medium. This storage medium can be a computer-readable storage medium. The storage medium stores a computer program, wherein the computer program includes program instructions. When executed by a processor, the program instructions cause the processor to perform any embodiment of the southbound routing downlink processing method of the IoT platform described above.

[0094] The storage medium can be any computer-readable storage medium capable of storing program code, such as a USB flash drive, portable hard drive, read-only memory (ROM), magnetic disk, or optical disk.

[0095] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of both. To clearly illustrate the interchangeability of hardware and software, the components and steps of the various examples have been generally described in terms of functionality in the foregoing description. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementations should not be considered beyond the scope of this invention.

[0096] In the several embodiments provided by this invention, it should be understood that the disclosed apparatus and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative. For example, the division of each unit is merely a logical functional division, and there may be other division methods in actual implementation. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed.

[0097] The steps in the method of this invention can be adjusted, merged, or reduced in order according to actual needs. The units in the device of this invention can be merged, divided, or reduced according to actual needs. Furthermore, the functional units in the various embodiments of this invention can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0098] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a storage medium. Based on this understanding, the technical solution of the present invention, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device to execute all or part of the steps of the methods described in the various embodiments of the present invention.

[0099] In the above embodiments, the descriptions of each embodiment have different focuses. For parts that are not described in detail in a certain embodiment, please refer to the relevant descriptions in other embodiments.

[0100] Obviously, those skilled in the art can make various modifications and variations to this invention without departing from its spirit and scope. Since these modifications and variations fall within the scope of the claims and their equivalents, this invention also intends to include these modifications and variations.

[0101] The above description is merely a specific embodiment of the present invention, but the scope of protection of the present invention is not limited thereto. Any person skilled in the art can easily conceive of various equivalent modifications or substitutions within the technical scope disclosed in the present invention, and these modifications or substitutions should all be covered within the scope of protection of the present invention. Therefore, the scope of protection of the present invention should be determined by the scope of the claims.

Claims

1. A southbound routing downlink processing method for an Internet of Things (IoT) platform, characterized in that, include: Create a new IP sub-table in the preset database, insert the device IP of the device to be connected into the IP sub-table, and add the device port of the device to be connected; Record the device information of the device to be accessed and store the device information in the corresponding sub-table. The device information includes IMEI information, user ID, resident ID information, and billing information. Establish a one-to-many sub-table relationship between the IP sub-table and the multiple sub-tables corresponding to the device information. Receive device data reported by the device to be connected. If the IP address attached to the device data matches the device IP address, add a temporary tag to the downlink service message returned to the device to be connected. The temporary tag includes the device IP address and the device port. During a short connection session with the device to be accessed, when the service message is returned to the device to be accessed according to the static route, the IP of the static route is replaced with the device IP in the temporary tag, so that the service message is returned to the device to be accessed according to the device IP and the device port; If the short connection session fails, the user ID and IMEI information stored in the sub-table are matched with the device information of the device to be accessed; if the match is successful, the process returns to the step of replacing the IP of the static route with the device IP in the temporary tag.

2. The method according to claim 1, characterized in that, If the IP address attached to the device data matches the device IP address, the step of adding a temporary tag to the downlink service message returned to the device to be accessed includes: The IP address associated with the device data is obtained by parsing the protocol layer address reported by the device. Match the IP address associated with the device data with the IP sub-table; If the same matching result exists, a temporary tag is added to the downlink service message returned to the device to be accessed.

3. The method according to claim 1, characterized in that, The method further includes: The address ID and port ID fields are obtained by parsing the protocol layer address reported by the device data; The URL address to be pushed is matched from the preset database based on the address ID and port ID fields; The device data is pushed to the northbound application platform for business processing based on the URL address.

4. The method according to any one of claims 1-3, characterized in that, The method further includes: If device data is received from multiple devices waiting to be connected, the temporary tag is added using a distributed queue.

5. A southbound routing downlink processing device for an Internet of Things (IoT) platform, characterized in that, include: The addition unit is used to create a new IP sub-table in a preset database, insert the device IP of the device to be connected into the IP sub-table, and add the device port of the device to be connected; record the device information of the device to be connected and store the device information in the corresponding sub-table, the device information including IMEI information, user ID, resident ID information, and billing information; and establish a one-to-many sub-table relationship between the IP sub-table and multiple sub-tables corresponding to the device information. The tag unit is used to receive device data reported by the device to be accessed. If the IP attached to the device data matches the device IP, a temporary tag is added to the downlink service message returned to the device to be accessed. The temporary tag includes the device IP and the device port. The replacement unit is used to replace the IP address of the static route with the device IP address in the temporary tag when the service message is returned to the device according to the static route during a short connection session with the device to be accessed, so that the service message is returned to the device to be accessed according to the device IP address and the device port. If the short connection session fails, the user ID and IMEI information stored in the sub-table are matched with the device information of the device to be accessed; if the match is successful, the process returns to the step of replacing the IP of the static route with the device IP in the temporary tag.

6. A computer device, characterized in that, The computer device includes a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the method as described in any one of claims 1-4.

7. A storage medium, characterized in that, The storage medium stores a computer program, which includes program instructions that, when executed by a processor, can implement the method as described in any one of claims 1-4.

Images