A method for IoT data transmission based on a central station

Abstract

This invention discloses an IoT data transmission method based on a central station, relating to the field of data transmission technology. The method includes: using session placeholder information as input, issuing traffic guidance and bearer configuration strategies to the mobile communication core network to direct uplink data from IoT devices to the edge user plane path of the central station; generating bearer identification information; encapsulating the raw data sent by the IoT device according to a unified format and writing the bearer identification information into the encapsulated raw data to form a transmission packet; the central station receiving the transmission packet, performing consistency verification based on the bearer identification information, and forwarding it to the backend service node; simultaneously parsing the data type information in the transmission packet to generate a receipt judgment result. This invention ensures the stability and determinism of the uplink data forwarding path by generating session placeholder information corresponding to the IoT device before the uplink data arrives.

Description

Technical Field

[0001] This invention relates to the field of data transmission technology, and in particular to an Internet of Things (IoT) data transmission method based on a central station. Background Technology

[0002] With the evolution of next-generation mobile communication technologies and the continuous expansion of IoT applications, IoT services are gradually evolving from early applications focused on low-speed, non-real-time data collection to those requiring large-scale connectivity, highly reliable transmission, and low-latency response. Simultaneously, satellite IoT, as an important supplement to terrestrial cellular IoT, is increasingly being applied in scenarios such as marine monitoring, remote energy facilities, and environmental sensing in uninhabited areas, achieving wide-area coverage and cross-regional data transmission capabilities through satellite access. In the next-generation mobile communication network architecture, the core network and access network are increasingly adopting a network architecture that separates the control plane and user plane. This enables the network to have greater flexibility and programmability in session management, traffic scheduling, and bearer control, providing a technical foundation for the differentiated support of IoT services. Under the trend of integrated space-ground network architecture, the satellite access network can also collaborate with the mobile communication core network to achieve unified session management and traffic scheduling control for IoT services between satellite and terrestrial links. Meanwhile, with the development of edge computing and user plane function decentralization technologies, some IoT service traffic can be processed on the access network side or edge nodes, thereby reducing the backhaul pressure on the core network and lowering end-to-end transmission latency. In satellite IoT scenarios, by deploying user plane functions at satellite ground gateway stations or satellite access edge nodes, it is also possible to achieve local offloading and edge processing of service data. Against this technological backdrop, the industry has proposed various data transmission schemes based on the collaboration of wireless gateways and core network policy control, focusing on IoT device access management, data forwarding path control, and service reliability assurance, and these schemes have been applied in smart city, industrial internet, and other application scenarios.

[0003] However, existing transmission methods still have room for improvement. For example, existing transmission methods only establish sessions / bearers when business data arrives, which leads to lag in traffic guidance and bearer control, making it difficult to guide uplink data from IoT devices to designated edge user plane nodes in a timely and stable manner. Summary of the Invention

[0004] In view of the aforementioned existing problems, the present invention is proposed.

[0005] Therefore, the present invention provides an IoT data transmission method based on a central station to solve the problem of difficulty in timely and stable redirection of uplink data from IoT devices to designated edge user plane nodes.

[0006] To solve the above-mentioned technical problems, the present invention provides the following technical solution:

[0007] This invention provides an IoT data transmission method based on a central station, comprising:

[0008] Obtain the registration information of IoT devices and combine it with the real-time operating status of each wireless gateway to determine a unique target wireless gateway for the IoT devices and generate session placeholder information;

[0009] Using session placeholder information as input, traffic guidance and bearer configuration strategies are sent to the mobile communication core network to guide the uplink data of IoT devices to the edge user plane path of the central station and generate bearer identification information.

[0010] The raw data sent by IoT devices is encapsulated in a unified format, and the carrier identification information is written into the encapsulated raw data to form a transmission packet;

[0011] The central station receives the transmission packet, performs consistency verification based on the bearer identification information, and forwards it to the backend business node. At the same time, it parses the data type information in the transmission packet to generate a receipt judgment result.

[0012] When no confirmation information is received from the backend business node, the central station issues a retransmission control command to the target wireless gateway based on the receipt judgment result, updates the corresponding retransmission control status, and updates and reconfigures the binding relationship between IoT devices and the target wireless gateway, as well as the traffic guidance and bearing configuration strategy.

[0013] As a preferred embodiment of the IoT data transmission method based on a central station according to the present invention, the generation of session placeholder information specifically includes:

[0014] The central station issues unified access configuration and security parameters to each wireless gateway and creates a device-gateway binding table locally. When an IoT device joins the network for the first time, the central station receives the IoT device registration message and extracts the device identifier and service type. The device-gateway binding table is a binding table between IoT devices and gateways.

[0015] Based on the real-time available bandwidth and queuing depth reported by each wireless gateway, the central station selects the optimal target wireless gateway and records the binding relationship of IoT devices in the device-gateway binding table; the optimal target wireless gateway is the wireless gateway with the largest available bandwidth and the smallest queuing depth.

[0016] After the recording is completed, the target wireless gateway identification information is sent to the IoT device to complete the binding. After the binding is completed, the central station generates the corresponding session placeholder information according to the service type.

[0017] As a preferred embodiment of the IoT data transmission method based on a central station according to the present invention, the generation of bearer identification information specifically includes:

[0018] The central station uses session placeholder information as the sole business control input, and issues traffic guidance rules and bearer configuration policies for IoT devices through the policy interface of the mobile communication core network. In the traffic guidance rules, the corresponding edge user plane path is configured for the session placeholder information.

[0019] After receiving traffic guidance rules and bearer configuration policies, the mobile communication core network establishes a mapping relationship between session occupancy information and edge user plane paths, and stores it in the policy control center.

[0020] When the mobile communication core network subsequently receives uplink data from IoT devices that enter the mobile communication core network via the target radio gateway, it queries the mapping relationship based on the session placeholder information carried in the uplink data of the IoT devices to determine the corresponding edge user plane path.

[0021] According to the bearer configuration strategy, bearer processing is performed on the uplink data of IoT devices to forward the uplink data of IoT devices to the edge user plane path corresponding to the central station.

[0022] When the central station detects that the edge user plane path carries uplink data from the corresponding IoT device for the first time, it generates bearer identification information that corresponds one-to-one with the session placeholder information and establishes a binding relationship between the bearer identification information and the IoT device identification.

[0023] As a preferred embodiment of the IoT data transmission method based on a central station according to the present invention, the formation of the transmission packet specifically includes:

[0024] After receiving the bearer identification information, the target wireless gateway performs standardized conversion on the raw data from the IoT device;

[0025] The target wireless gateway encapsulates the standardized and converted raw data according to a unified format, and writes device identification information, serial number information, data type information, and bearer identification information into the encapsulated raw data to form a transmission packet;

[0026] The transmission packet is sent to the central station via the edge user plane path, and a cache entry corresponding to the sequence number is established locally. The cache entry includes the sequence number information, the complete content of the corresponding transmission packet, and the record of the number of retransmissions of the corresponding transmission packet.

[0027] As a preferred embodiment of the IoT data transmission method based on a central station according to the present invention, the generation of the receipt determination result specifically includes:

[0028] After receiving the transmission packet, the central station parses the bearer identification information field carried in the transmission packet, and queries the mapping relationship between IoT devices and bearers maintained locally by the central station based on the bearer identification information to determine whether the bearer identification information carried in the transmission packet is consistent with the current session bearer status of the IoT device.

[0029] If the bearer identification information is consistent, the central station will forward the service payload in the transmission packet to the back-end service node;

[0030] The central station parses the data type information carried in the transmission packet and generates a receipt judgment result based on the data type information.

[0031] As a preferred embodiment of the IoT data transmission method based on a central station described in this invention, the step of generating a receipt determination result based on data type information means that the central station parses the data type information carried in the transmission packet, determines the transmission packet whose data type information belongs to a preset receipt type set as requiring a receipt and generates a receipt determination result, and determines the transmission packet whose data type information does not belong to the preset receipt type set as not requiring a receipt and does not generate a receipt determination result.

[0032] As a preferred embodiment of the IoT data transmission method based on a central station according to the present invention, the update of the corresponding retransmission control state specifically includes:

[0033] If no confirmation information is received from the backend service node, the central station generates a retransmission control command based on the receipt judgment result and sends the retransmission control command to the target wireless gateway.

[0034] The target wireless gateway extracts the corresponding transmission packet from its local cache entry based on the sequence number information in the retransmission control command, re-uploads the transmission packet to the central station, and updates the cumulative number of retransmissions recorded locally by the target wireless gateway.

[0035] After completing the retransmission, the target wireless gateway sends a retransmission completion event to the central station. The central station updates the cumulative number of retransmissions for the IoT device based on the retransmission completion event.

[0036] When the cumulative number of retransmissions reaches the preset limit, the central station records the retransmission failure event and updates the corresponding receipt failure event record of the IoT device.

[0037] The central station uses the cumulative number of retransmissions and the record of failed receipt events as the retransmission control status.

[0038] As a preferred embodiment of the IoT data transmission method based on a central station according to the present invention, the updating and reconfiguration of the binding relationship between IoT devices and target wireless gateways, as well as the traffic guidance and bearer configuration strategy, specifically includes:

[0039] The central station determines whether the current IoT device meets the preset reliability switching conditions based on the acknowledgment failure event records and the cumulative number of retransmissions in the retransmission control status.

[0040] When the reliability switching conditions are met, the central station freezes the bearer identification information corresponding to the current IoT device and re-evaluates the operating status of each wireless gateway to determine the new target wireless gateway.

[0041] The central station updates the binding relationship between the IoT device and the new target wireless gateway in the device-gateway binding table, and sends the new target wireless gateway identification information to the IoT device;

[0042] The central station initiates a policy update request to the mobile communication core network to change the traffic routing and bearer configuration policy corresponding to the IoT device, and generates new bearer identification information and sends it to the new target wireless gateway, while notifying the original target wireless gateway to release the corresponding resources.

[0043] As a preferred embodiment of the IoT data transmission method based on a central station described in this invention, the re-evaluation of the operating status of each wireless gateway refers to the central station comparing and analyzing the available bandwidth and queuing depth of each wireless gateway based on the real-time operating status information reported by each wireless gateway, and selecting the wireless gateway with the largest available bandwidth and the smallest queuing depth as the new target wireless gateway.

[0044] As a preferred embodiment of the IoT data transmission method based on a central station as described in this invention, the mobile communication core network refers to a mobile communication core network platform that supports a control plane and user plane separation architecture, supports a policy control interface, and is capable of dynamically controlling the user plane data forwarding path.

[0045] The beneficial effects of this invention are as follows: By generating session placeholder information corresponding to the IoT device before the uplink data arrives, and using this session placeholder information as the sole control input to issue traffic guidance and bearer configuration strategies to the mobile communication core network, this invention enables the mobile communication core network to complete the pre-configuration of user plane paths and bearer processing before the IoT device generates service data. This avoids the lag problem in traffic guidance and bearer control caused by existing methods that only establish sessions or bearers when service data arrives as a trigger. Therefore, when the uplink data from the IoT device subsequently enters the mobile communication core network, it can be directly and fixedly guided to the edge user plane path associated with the central station, ensuring the stability and determinism of the uplink data forwarding path. Attached Figure Description

[0046] 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 only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0047] Figure 1This is a flowchart of an IoT data transmission method based on a central station.

[0048] Figure 2 This is a diagram of the communication process structure.

[0049] Figure 3 This is a schematic diagram of the transmission packet structure.

[0050] Figure 4 This is a flowchart for receipt determination and retransmission control. Detailed Implementation

[0051] To make the above-mentioned objects, features and advantages of the present invention more apparent and understandable, the specific embodiments of the present invention will be described in detail below with reference to the accompanying drawings.

[0052] Many specific details are set forth in the following description in order to provide a full understanding of the invention. However, the invention may also be practiced in other ways different from those described herein, and those skilled in the art can make similar extensions without departing from the spirit of the invention. Therefore, the invention is not limited to the specific embodiments disclosed below.

[0053] Secondly, the term "one embodiment" or "embodiment" as used herein refers to a specific feature, structure, or characteristic that may be included in at least one implementation of the present invention. The phrase "in one embodiment" appearing in different places in this specification does not necessarily refer to the same embodiment, nor is it a single or selective embodiment that is mutually exclusive with other embodiments.

[0054] Reference Figures 1-4 This is one embodiment of the present invention, which provides an Internet of Things (IoT) data transmission method based on a central station, comprising the following steps:

[0055] S1: Obtain the registration information of IoT devices and combine it with the real-time operating status of each wireless gateway to determine a unique target wireless gateway for the IoT devices and generate session placeholder information.

[0056] When the central station is deployed on the access network side and operates as an IoT service anchor point, it receives registration messages sent by IoT devices and parses the device identification information and service type information of the IoT devices from the registration messages. At the same time, the central station receives real-time operating status information reported by each wireless gateway at a fixed time period (1 second). The real-time operating status information includes at least the current available bandwidth value and queuing depth value of the wireless gateway.

[0057] The central station establishes a data table structure for the device-gateway binding table in its local storage space, and presets IoT device identifier fields and wireless gateway identifier fields in the device-gateway binding table. After the device-gateway binding table is established, the central station issues unified access configuration parameters and security parameters to each wireless gateway, enabling each wireless gateway to participate in the IoT device access process according to the unified access configuration and security parameters.

[0058] When an IoT device first joins the network, the central station sorts the wireless gateways based on their reported available bandwidth and queuing depth. The wireless gateway ranked first is selected as the target wireless gateway, following a sorting rule from largest to smallest available bandwidth and smallest to largest queuing depth. The central station uses available bandwidth as the primary sorting criterion and queuing depth as the secondary sorting criterion. When multiple wireless gateways have the same available bandwidth, the gateway with the smaller queuing depth is prioritized. This ensures the deterministic nature of the target wireless gateway selection process. After determining the target wireless gateway, the central station writes the IoT device's identifier and the target wireless gateway's identifier into the device-gateway binding table, creating a binding record between the IoT device and the target wireless gateway. The central station then sends the target wireless gateway's identifier to the IoT device to complete the binding process.

[0059] The central station receives registration messages from IoT devices and parses the service type field from the registration messages. The service type identifier carried in the service type field is used as the service type information of the IoT device. The central station assigns a unique session identifier to the IoT device locally and generates session placeholder information corresponding to the IoT device based on the session identifier. The session placeholder information includes at least the session identifier and the session state parameters associated with the session identifier. After the session placeholder information is generated, the central station establishes a correspondence record between the IoT device identifier and the session identifier in local storage and writes the correspondence record into the session management table maintained by the central station, thus completing the association storage of the session placeholder information with the IoT device.

[0060] It should also be noted that after receiving the registration message, the central station queries the device-gateway binding table and the session management table based on the device identification information obtained from parsing the registration message. If an existing record matching the device identification information exists in either the device-gateway binding table or the session management table, the central station determines that the device identification information conflicts and refuses to create a new binding record and new session placeholder information for the registration message corresponding to the device identification information. At the same time, it returns a registration rejection message to the IoT device. If no existing record matching the device identification information exists in either the device-gateway binding table or the session management table, the central station allows the registration message corresponding to the device identification information to pass through and performs operations such as target wireless gateway determination, binding record writing, session identifier allocation, and session placeholder information generation.

[0061] To further clarify, the uniqueness of session placeholder information is uniformly generated and maintained locally by the central station. When allocating session identifiers, the central station uses itself as the boundary for the generation and management of session identifiers, ensuring that each session identifier allocated within the coverage area of ​​the same central station is unique and cannot be repeated. The generated session placeholder information is only used within the scope of collaborative control between the corresponding central station and the mobile communication core network. In multi-central-station or multi-mobile communication core network deployment scenarios, different central stations independently maintain their own session management tables and only generate and manage session placeholder information for IoT devices accessing their respective central stations. Session placeholder information is not shared between different central stations, thereby avoiding conflicts in session placeholder information across the entire network through central station-level isolation, and ensuring that the mobile communication core network can perform deterministic identification and processing within the corresponding central station control domain when receiving session placeholder information.

[0062] It should also be noted that the update of the device-gateway binding table is triggered by changes in the real-time operating status of the wireless gateways by the central station. After receiving real-time operating status information reported by each wireless gateway at fixed time intervals, the central station continuously compares the operating status of the target wireless gateways corresponding to the IoT devices with established binding relationships. When a change in the real-time operating status of a target wireless gateway is detected, the central station re-executes the target wireless gateway determination process and updates the binding record of the corresponding IoT device in the device-gateway binding table based on the re-determination result. If the re-determined target wireless gateway is consistent with the original bound wireless gateway, the central station maintains the original binding record in the device-gateway binding table unchanged; if the re-determined target wireless gateway is inconsistent with the original bound wireless gateway, the central station updates the corresponding wireless gateway identifier field in the device-gateway binding table and sends the updated target wireless gateway identifier information to the IoT devices to complete the synchronous update of the device-gateway binding relationship.

[0063] To further explain, the IoT access and data transmission system jointly constructed by the central station, wireless gateway, and mobile communication core network in this embodiment is not only applicable to terrestrial cellular IoT scenarios, but can also be extended to satellite IoT scenarios. In the satellite IoT deployment mode, the wireless gateway can be carried by the satellite ground gateway station or the satellite access terminal, while the central station still serves as the IoT service anchor point to uniformly manage the generation of session occupancy information, path control, and the distribution of carrying strategies.

[0064] S2: Taking session placeholder information as input, it sends traffic guidance and bearer configuration strategies to the mobile communication core network, directs the uplink data of IoT devices to the edge user plane path of the central station, and generates bearer identification information.

[0065] The central station uses the policy interface provided by the mobile communication core network, taking session placeholder information as the sole service control input, to send traffic guidance rules and bearer configuration policies to the mobile communication core network. Traffic redirection rules use session placeholder information The session identifier parameter in the information is used as a unique matching key to explicitly match the session identifier parameter with the edge user plane path corresponding to the central station. By binding paths, the mobile communication core network can complete the reachability of the user plane path before the uplink data from the IoT device arrives. Sexual preparation; the bearer configuration strategy uses the session identifier parameter as the unique bearer control key, and configures the session identifier parameter accordingly. The bearer processing parameter set includes at least the forwarding execution priority, acknowledgment mechanism requirements, and user... Forwarding behavior constraint parameters enable uplink data from IoT devices subsequently entering the mobile communication core network to travel without relying on the bearer. With the identification information, the edge user plane path of the central station can be deterministically guided, realizing the front-end control and user... The surface-ready path anchoring effect avoids the traffic guidance lag and path delays caused by "data arrival triggering chain establishment" in existing technologies. drift.

[0066] To further explain, the reachability preparation includes a bearer configuration strategy and may also include path planning.

[0067] To further clarify, the session identifier parameter is a unique identifier assigned by the central station when generating session placeholder information. A session identifier is used to uniquely identify a service session corresponding to an IoT device in the mobile communication core network; the session identifier parameter can... To adopt Fixed-length numeric parameters or fixed-length encoded fields To achieve this, the session identifier parameter must be at least in the same central location. It remains unique within the station's control range and serves as the unique matching key for traffic routing rules and bearer configuration policies by the mobile communication core. MindNet Identification and Use.

[0068] Among them, the forwarding execution priority is used to indicate the order in which uplink data from IoT devices is forwarded and processed in the user plane. Sequence, for example, is used to distinguish between high-real-time business data and ordinary periodic reported data; confirmation mechanisms are required to indicate the order of events. Does the data from the session require confirmation from the backend business node? For example, is it necessary to require confirmation for alarm-type data? Receipts are accepted, while regular data collection does not require confirmation; user plane forwarding behavior constraint parameters are used to limit uplink data on IoT devices. Forwarding methods in the user plane, for example, can be used to specify that data is only allowed to be forwarded along the bound edge user plane path, avoiding... Cross-path forwarding or path drift occurs.

[0069] The mobile communication core network receives traffic routing rules and bearer configuration policies. Using the session identifier parameter in the session placeholder information as the index key, it creates a policy control entry in the policy control center. The policy control entry is then written with the edge user plane path identifier, traffic routing rule parameters, and bearer configuration policy parameters that correspond one-to-one with the session identifier parameter, forming a policy control record with the session identifier parameter as the unique index. This policy control record enables the mobile communication core network to complete the closed-loop control of "service identification - path determination - bearer processing" based on the session identifier parameter even without the allocation of bearer identifier information. This replaces the traditional bearer identifier information with session placeholder information as the pre-control anchor point, improving the certainty and consistency of path determination.

[0070] When an IoT device sends uplink data through a target wireless gateway and enters the mobile communication core network, the mobile communication core network parses session placeholder information from the uplink data and queries the policy control record in the policy control center using the parsed session identifier parameter. After finding the policy control record, it directly determines the edge user plane path corresponding to the uplink data. The mobile communication core network performs bearer processing on the uplink data according to the bearer configuration policy. Bearer processing includes: setting forwarding execution priority for the uplink data according to the bearer processing parameter set, setting confirmation mechanism requirements and binding edge user plane path forwarding constraint parameters, associating the uplink data to the determined edge user plane path according to the traffic guidance rules, and forwarding the uplink data to the central station via the edge user plane path. This ensures that the path control and bearer processing of the uplink data are completed under the same session identifier parameter index, reducing latency jitter caused by multiple determinations and improving the stability of IoT service uplink data reaching the central station.

[0071] After the mobile communication core network begins to actually forward uplink data from IoT devices according to traffic guidance rules and bearer configuration strategies, the central station triggers the bearer identifier information generation operation by monitoring the data forwarding event of the first bearer of the corresponding session identifier parameter on the edge user plane path. The central station generates bearer identifier information that corresponds one-to-one with the session placeholder information, and establishes a binding relationship between the bearer identifier information, the IoT device identifier information, and the session placeholder information and stores it locally at the central station. This ensures that the allocation of bearer identifier information strictly falls after the edge user plane path has actually carried uplink data from IoT devices, thereby avoiding the occupation of bearer identifier resources when IoT devices have not yet generated valid service data. At the same time, the bearer identifier information is used as a consistency verification anchor point in the subsequent data encapsulation, transmission verification, and retransmission control processes, enabling the central station to perform deterministic verification of the bearer continuity of IoT device data transmission, and enhancing the traceability and reliability of data paths in cross-wireless gateway handover or abnormal retransmission scenarios.

[0072] It should also be noted that when generating bearer identification information, the central station uses the session identifier parameter in the session placeholder information as the unique generation basis, establishing a one-to-one correspondence between the session identifier parameter and the bearer identification information in the bearer management table maintained locally by the central station. Before executing the bearer identification information generation operation, the central station first checks the bearer management table to see if bearer identification information corresponding to the session identifier parameter already exists. If a correspondence already exists, the bearer identification information is not generated again; only if no correspondence exists is the generation and allocation operation of the bearer identification information performed, thus ensuring that each session identifier parameter corresponds to only one bearer identification information. In this way, the bearer identification information remains unique within the central station, avoiding duplicate or conflicting bearer identification information between different IoT devices or different sessions. The bearer management table is a data table structure established by the central station in local storage, and it includes at least a session identifier parameter field, an IoT device identifier field, and a bearer identification information field.

[0073] The edge user plane path is a user plane data forwarding path established between user plane functional entities in the mobile communication core network, or between a user plane functional entity and the central station. The edge user plane path is implemented based on the standardized user plane forwarding mechanism supported by the mobile communication core network and is used to carry the forwarding process of uplink data from IoT devices in the user plane. In specific implementations, the edge user plane path can be established through user plane interfaces between user plane functional entities in the mobile communication core network, or through a user plane forwarding channel established between a user plane functional entity and the central station. The user plane forwarding channel can use tunnel encapsulation to carry uplink data from IoT devices, enabling the uplink data from IoT devices to be forwarded to the central station in the mobile communication core network along a pre-determined user plane path. The establishment and maintenance of the edge user plane path are completed by the mobile communication core network according to traffic guidance rules and bearer configuration strategies. The central station does not participate in the link establishment process of the edge user plane path, but only acts as the receiving end of the user plane path to receive uplink data from IoT devices forwarded via the user plane path, thus ensuring that the implementation method of the edge user plane path is consistent with the existing user plane forwarding architecture of the mobile communication core network.

[0074] Preferably, through the S2 technical step of the present invention, the central station uses the session identifier parameter in the session placeholder information as the unique service control anchor point. Before the uplink data from the IoT device enters the mobile communication core network, it completes the distribution of traffic guidance rules and bearer configuration strategies. This allows the mobile communication core network to determine the edge user plane path in advance without allocating bearer identifier information, ensuring that the uplink data from the IoT device is directly guided to the edge user plane path corresponding to the central station upon its first arrival, avoiding forwarding delays and path uncertainties caused by post-establishment links. Simultaneously, the present invention limits the generation of bearer identifier information to after the user plane path has actually carried the uplink data from the IoT device, ensuring that the bearer identifier information is only allocated after the service path is confirmed. This decouples session control from bearer identifier allocation, reduces unnecessary resource consumption, and improves path stability and bearer consistency during IoT data transmission.

[0075] S3: Encapsulate the raw data sent by IoT devices in a unified format, and write the bearer identification information into the encapsulated raw data to form a transmission packet.

[0076] The target wireless gateway receives the bearer identification information from the central station and stores it locally for subsequent data encapsulation processing by IoT devices. When an IoT device sends raw data through the target wireless gateway, the gateway performs a standardization conversion process on the received raw data. This standardization conversion process follows a pre-agreed unified transmission format when the central station sends unified access configuration parameters to the target wireless gateway. The standardization conversion process includes: byte order standardization of the raw data sent by the IoT device, converting it to a predefined byte encoding format; statistical analysis of the raw data length and generation of corresponding data length description information; and maintaining the complete byte order mapping of the raw data content to the service payload field without semantic parsing, ensuring the transparency and integrity of the data content during transmission.

[0077] The unified transmission format consists of a header field and a payload field, both of which have fixed definitions regarding field order, field length, and encoding method. The header field includes at least: a device identification information field, a serial number information field, a data type information field, and a bearer identification information field. The payload field carries the raw service data content sent by the IoT device. The unified transmission format defines the field composition and order of the transmission packet, ensuring that data sent by different IoT devices can be recognized by the central station according to consistent parsing rules.

[0078] During the encapsulation operation, the target wireless gateway constructs a transmission packet structure according to a unified transmission format, writing the raw data sent by the IoT device into the service payload field of the transmission packet. At the same time, the device identification information corresponding to the IoT device, the sequence number information used to identify the current data transmission order, the data type information used to indicate the service category, and the bearer identification information used to identify the bearer relationship are sequentially written into the packet header field of the transmission packet, thereby forming a transmission packet with fixed field positions and clear field meanings.

[0079] The target wireless gateway sends the transmission packet to the central station via the edge user plane path. At the same time, the target wireless gateway establishes a cache entry indexed by the sequence number information locally, and stores the complete content of the transmission packet with the corresponding sequence number information. This enables the target wireless gateway to accurately locate the corresponding transmission packet and perform the retransmission operation based on the sequence number information when it receives a retransmission control command later.

[0080] S4: The central station receives the transmission packet, performs consistency verification based on the bearer identification information, and forwards it to the backend business node. At the same time, it parses the data type information in the transmission packet to generate a receipt judgment result.

[0081] S4.1: The central station receives the transmission packets uploaded by the target radio gateway through the edge user plane path associated with the mobile communication core network, and performs parsing processing on the transmission packets. The parsing processing includes separating the packet header field and the service payload field according to the unified transmission format pre-agreed between the central station and the target radio gateway, and reading each field in the packet header field one by one.

[0082] During the parsing process, the central station reads the bearer identification information field used to identify the bearer relationship from the packet header. Using the read bearer identification information as a query condition, the central station performs a mapping query operation in the IoT device and bearer mapping table maintained locally by the central station, and reads the IoT device identification information corresponding to the bearer identification information and the session bearer status record associated with the IoT device identification information.

[0083] The central station performs a consistency comparison between the parsed bearer identifier information and the session bearer status record obtained from the mapping query. When the bearer identifier information is consistent with the currently valid bearer identifier information recorded in the session bearer status record, the central station determines that the transmission packet meets the session bearer status requirements of the current IoT device, thereby completing the session consistency verification based on the bearer identifier information.

[0084] After completing the session consistency verification, the central station extracts the service payload field from the transmission packet and sends the service payload field to the backend service node according to the access interface specification predefined by the backend service node, so that the backend service node can process the service data of the IoT device.

[0085] To further explain, the predefined access interface specifications include the interface address for receiving business payload fields, the interface calling method, the data encapsulation format, the field encoding rules, and the interface confirmation return rules.

[0086] S4.2: After the business payload field is forwarded, the central station continues to parse the data type information field in the transmission packet header, and compares the parsed data type information field value with the preset receipt type set pre-configured locally by the central station. The preset receipt type set is used to identify the data type information value that requires the backend business node to return confirmation information.

[0087] To further explain, the preset receipt type set is a fixed set of data type information values ​​configured by the central station during initialization based on the IoT application requirements and the business characteristics of the backend business nodes. These include, but are not limited to, the following data type information values: IoT device status update type, alarm notification type, data synchronization confirmation type, and configuration modification feedback type. Each data type information value in the preset receipt type set, along with its corresponding business confirmation requirements and processing methods, has been defined by the backend business nodes to ensure that when these data type information fields appear in the transmission packet, the backend business nodes can promptly return confirmation information.

[0088] When the data type information field value belongs to the preset receipt type set, the central station determines that the corresponding transmission packet needs to generate a receipt determination result and marks the transmission packet as a transmission packet that needs a receipt; when the data type information field value does not belong to the preset receipt type set, the central station determines that the corresponding transmission packet does not need to generate a receipt determination result and marks the transmission packet as a transmission packet that does not need a receipt.

[0089] The central station will establish an association record between the receipt judgment result generated based on the data type information and the corresponding transmission packet, and store the receipt judgment result locally in the central station for the judgment and processing of the data transmission status of IoT devices in the subsequent transmission reliability control process.

[0090] To further explain, the central station maintains a matching table locally between data type information and a preset set of receipt types. This table uses the data type information field values ​​as index keys and pre-configures a corresponding receipt determination attribute for each field value. The receipt determination attribute indicates whether the corresponding data type information field belongs to the preset receipt type set. In the matching table, data type information field values ​​belonging to the preset receipt type set are configured with the "receive receipt required" attribute, while those not belonging are configured with the "no receipt required" attribute. After parsing the data type information fields in the transmission packet, the central station directly determines whether a receipt determination result needs to be generated based on the matching table, without introducing additional business determination logic during data forwarding. The matching table is configured by the central station during the initialization phase based on the business types supported by the backend business nodes and remains stable during operation to ensure consistency and determinism in the receipt determination process for different IoT devices and different business data.

[0091] S5: When no confirmation information is received from the backend business node, the central station issues a retransmission control command to the target wireless gateway based on the receipt judgment result, updates the corresponding retransmission control status, and updates and reconfigures the binding relationship between IoT devices and the target wireless gateway, as well as the traffic guidance and bearer configuration strategy.

[0092] S5.1: After the central station generates the receipt judgment result based on the data type information, if the central station does not receive the confirmation information returned by the backend business node within the fixed configuration confirmation waiting period (200 milliseconds), the central station determines that the corresponding transmission packet has a receipt missing situation, and generates a retransmission control instruction based on the receipt judgment result. The retransmission control instruction includes at least the sequence number information used to uniquely identify the transmission packet, and establishes an association with the IoT device identification information that triggered the receipt missing.

[0093] The central station sends the generated retransmission control command to the target wireless gateway, instructing the target wireless gateway to perform a retransmission operation on the transmission packet corresponding to the sequence number information. After receiving the retransmission control command, the target wireless gateway reads the cache entry that matches the sequence number information in the retransmission control command from the cache entries maintained locally by the target wireless gateway, and extracts the transmission packet corresponding to the sequence number information from the cache entry.

[0094] Without making any modifications to the content of the transmission packet, the target wireless gateway re-uploads the extracted transmission packet to the central station along the same edge user plane path as the initial uploaded transmission packet. After completing one retransmission upload operation, the target wireless gateway increments the retransmission cumulative count record corresponding to the sequence number information by one on its local machine and stores the updated retransmission cumulative count record on its local machine.

[0095] After completing the retransmission upload operation, the target wireless gateway sends a retransmission completion event to the central station. The retransmission completion event carries at least the IoT device identification information and serial number information to identify the transmission packet that has completed the retransmission operation.

[0096] The central station receives the retransmission completion event and, based on the IoT device identification information carried in the retransmission completion event, updates the cumulative number of retransmissions corresponding to the IoT device identification information locally at the central station to the latest value consistent with the retransmission completion event.

[0097] When the central station detects that the cumulative number of retransmissions corresponding to the IoT device identification information has reached the preset limit (3 times), the central station records a retransmission failure event and updates the corresponding receipt failure event record to a failure status locally. The retransmission failure event record and the receipt failure event record indicate the abnormal reliability status of the IoT device during data transmission.

[0098] To further clarify, the preset upper limit is set after evaluating the transmission stability and fault tolerance requirements of IoT devices. Choosing three times as the upper limit takes into account the requirement for timely feedback during data transmission and to avoid wasting network resources due to excessive retransmissions. This is considered a reasonable value that balances transmission stability and resource utilization. Exceeding three times indicates a reliability issue with the device, requiring further processing.

[0099] The central station stores the cumulative number of retransmissions and the record of failed receipt events corresponding to the IoT device identification information as the retransmission control status.

[0100] S5.2: Read the receipt failure event record and retransmission cumulative count record corresponding to the IoT device identifier from the central station, and determine whether the current IoT device meets the preset reliability switching conditions based on the receipt failure event record and retransmission cumulative count record.

[0101] It should also be noted that the reliability switching conditions are pre-configured by the central station, specifically set as follows: within the valid time window corresponding to the same session placeholder information, the cumulative number of retransmissions corresponding to the IoT device reaches 3 times, and the central station has a local record of the current IoT device's corresponding acknowledgment failure event in a failed state.

[0102] When the central station determines that an IoT device meets the reliability switching conditions, it sets the bearer identifier information corresponding to the IoT device identifier to a frozen state locally. The frozen bearer identifier information will no longer participate in the subsequent encapsulation, transmission verification, and retransmission control processing of IoT device data, and is used to block abnormal bearer paths from continuing to carry IoT device service data.

[0103] After freezing the bearer identification information, the central station reassesses the operational status of each wireless gateway to determine the new target wireless gateway. The central station reads the available bandwidth and queuing depth values ​​for each wireless gateway from the real-time operational status information reported by each gateway, and compares the available bandwidth and queuing depth values. The wireless gateway with the largest available bandwidth and the smallest queuing depth is selected as the new target wireless gateway.

[0104] The central station updates the binding relationship between the IoT device and the new target wireless gateway in the Device-Gateway Binding Table. Simultaneously, it deletes the binding record between the IoT device identifier and the original target wireless gateway identifier in the Device-Gateway Binding Table, and writes a binding record between the IoT device identifier and the new target wireless gateway identifier into the Device-Gateway Binding Table.

[0105] The central station sends new target wireless gateway identification information to IoT devices, enabling the IoT devices to access data through the new target wireless gateway.

[0106] After the binding relationship between the IoT device and the new target wireless gateway is updated, the central station initiates a policy update request to the mobile communication core network. The policy update request is used to trigger the mobile communication core network to change the traffic routing rules and bearer configuration policies corresponding to the IoT device, so that the updated traffic routing rules and bearer configuration policies are consistent with the new target wireless gateway and the new edge user plane path.

[0107] After initiating a policy update request, the central station generates new bearer identifier information corresponding to the IoT device identifier and sends the new bearer identifier information to the new target wireless gateway for subsequent IoT device data encapsulation, transmission verification, and retransmission control processing. Simultaneously, the central station sends a resource release notification to the original target wireless gateway to release the cached resources and bearer resources in the original target wireless gateway corresponding to the frozen bearer identifier information.

[0108] This embodiment also provides a computer device applicable to the IoT data transmission method based on a central station, comprising: a memory and a processor; the memory is used to store computer-executable instructions, and the processor is used to execute the computer-executable instructions to implement the IoT data transmission method based on a central station as proposed in the above embodiment.

[0109] The computer device can be a terminal, comprising a processor, memory, communication interface, display screen, and input devices connected via a system bus. The processor provides computing and control capabilities. The memory includes non-volatile storage media and internal memory. The non-volatile storage media stores the operating system and computer programs. The internal memory provides an environment for the operation of the operating system and computer programs stored in the non-volatile storage media. The communication interface is used for wired or wireless communication with external terminals; wireless communication can be achieved through Wi-Fi, carrier networks, NFC (Near Field Communication), or other technologies. The display screen can be an LCD screen or an e-ink screen. The input devices can be a touch layer covering the display screen, buttons, a trackball, or a touchpad on the computer device's casing, or an external keyboard, touchpad, or mouse.

[0110] This embodiment also provides a storage medium storing a computer program, which, when executed by a processor, implements the IoT data transmission method based on a central station as proposed in the above embodiments. The storage medium can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as Static Random Access Memory (SRAM), Electrically Erasable Programmable Read-Only Memory (EEPROM), Erasable Programmable Read Only Memory (EPROM), Programmable Red-Only Memory (PROM), Read-Only Memory (ROM), magnetic storage, flash memory, magnetic disk, or optical disk.

[0111] In summary, this invention generates session placeholder information corresponding to an IoT device before the uplink data arrives, and uses this session placeholder information as the sole control input to issue traffic guidance and bearer configuration strategies to the mobile communication core network. This allows the mobile communication core network to pre-configure user plane paths and bearer processing before the IoT device generates service data, avoiding the lag in traffic guidance and bearer control caused by existing methods that only establish sessions or bearers when service data arrives. Therefore, when uplink data from the IoT device subsequently enters the mobile communication core network, it can be directly and consistently guided to the edge user plane path associated with the central station, ensuring the stability and determinism of the uplink data forwarding path.

[0112] It should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention and are not intended to limit it. Although the present invention has been described in detail with reference to preferred embodiments, those skilled in the art should understand that modifications or equivalent substitutions can be made to the technical solutions of the present invention without departing from the spirit and scope of the technical solutions of the present invention, and all such modifications or substitutions should be covered within the scope of the claims of the present invention.

Claims

1. A method for transmitting data in the Internet of Things (IoT) based on a central station, characterized in that: include, Obtain the registration information of IoT devices and combine it with the real-time operating status of each wireless gateway to determine a unique target wireless gateway for the IoT devices and generate session placeholder information; Using session placeholder information as input, traffic guidance and bearer configuration policies are issued to the mobile communication core network to direct uplink data from IoT devices to the edge user plane path of the central station, generating bearer identification information, specifically: The central station uses session placeholder information as the sole business control input, and issues traffic guidance rules and bearer configuration policies for IoT devices through the policy interface of the mobile communication core network. In the traffic guidance rules, the corresponding edge user plane path is configured for the session placeholder information. After receiving traffic guidance rules and bearer configuration policies, the mobile communication core network establishes a mapping relationship between session occupancy information and edge user plane paths, and stores it in the policy control center. When the mobile communication core network subsequently receives uplink data from IoT devices that enter the mobile communication core network via the target radio gateway, it queries the mapping relationship based on the session placeholder information carried in the uplink data of the IoT devices to determine the corresponding edge user plane path. According to the bearer configuration strategy, bearer processing is performed on the uplink data of IoT devices to forward the uplink data of IoT devices to the edge user plane path corresponding to the central station. The bearer processing refers to setting forwarding execution priority, confirmation mechanism requirements, and user plane forwarding behavior constraint parameters for uplink data on IoT devices according to the bearer configuration strategy. When the central station detects that the edge user plane path carries uplink data from the corresponding IoT device for the first time, it generates bearer identification information that corresponds one-to-one with the session placeholder information, and establishes a binding relationship between the bearer identification information and the IoT device identification. The raw data sent by IoT devices is encapsulated in a unified format, and the carrier identification information is written into the encapsulated raw data to form a transmission packet; The central station receives the transmission packet, performs consistency verification based on the bearer identification information, and forwards it to the backend business node. At the same time, it parses the data type information in the transmission packet to generate a receipt judgment result. When no confirmation information is received from the backend business node, the central station issues a retransmission control command to the target wireless gateway based on the receipt judgment result, updates the corresponding retransmission control status, and updates and reconfigures the binding relationship between IoT devices and the target wireless gateway, as well as the traffic guidance and bearing configuration strategy.

2. The IoT data transmission method based on a central station as described in claim 1, characterized in that: The generated session placeholder information is specifically as follows: The central station sends unified access configuration and security parameters to each wireless gateway and creates a device-gateway binding table locally. When an IoT device joins the network for the first time, the central station receives the IoT device registration message and extracts the device identifier and service type. Based on the real-time available bandwidth and queuing depth reported by each wireless gateway, the central station selects the optimal target wireless gateway and records the binding relationship of IoT devices in the device-gateway binding table. After the recording is completed, the target wireless gateway identification information is sent to the IoT device to complete the binding. After the binding is completed, the central station generates the corresponding session placeholder information according to the service type.

3. The IoT data transmission method based on a central station as described in claim 1, characterized in that: The formation of the transmission packet specifically includes: After receiving the bearer identification information, the target wireless gateway performs standardized conversion on the raw data from the IoT device; The target wireless gateway encapsulates the standardized and converted raw data in a unified format, and writes IoT device identification information, serial number information, data type information, and bearer identification information into the encapsulated raw data to form a transmission packet; The transmission packet is sent to the central station via the edge user plane path, and a cache entry corresponding to the sequence number is established locally. The cache entry includes the sequence number information, the complete content of the corresponding transmission packet, and the record of the number of retransmissions of the corresponding transmission packet.

4. The IoT data transmission method based on a central station as described in claim 1, characterized in that: The specific result of generating the receipt determination is as follows: After receiving the transmission packet, the central station parses the bearer identification information field carried in the transmission packet, and queries the mapping relationship between IoT devices and bearers maintained locally by the central station based on the bearer identification information to determine whether the bearer identification information carried in the transmission packet is consistent with the current session bearer status of the IoT device. If the bearer identification information is consistent, the central station will forward the service payload in the transmission packet to the back-end service node; The central station parses the data type information carried in the transmission packet and generates a receipt judgment result based on the data type information.

5. The IoT data transmission method based on a central station as described in claim 4, characterized in that: The process of generating a receipt determination result based on data type information refers to the central station parsing the data type information carried in the transmission packet, determining that transmission packets whose data type information belongs to the preset receipt type set require a receipt and generating a receipt determination result, and determining that transmission packets whose data type information fields do not belong to the preset receipt type set do not require a receipt and do not generate a receipt determination result.

6. The IoT data transmission method based on a central station as described in claim 1, characterized in that: The update of the corresponding retransmission control state is specifically as follows: If no confirmation information is received from the backend service node, the central station generates a retransmission control command based on the receipt judgment result and sends the retransmission control command to the target wireless gateway. The target wireless gateway extracts the corresponding transmission packet from its local cache entry based on the sequence number information in the retransmission control command, re-uploads the transmission packet to the central station, and updates the cumulative number of retransmissions recorded locally by the target wireless gateway. After completing the retransmission, the target wireless gateway sends a retransmission completion event to the central station. The central station updates the cumulative number of retransmissions for the IoT device based on the retransmission completion event. When the cumulative number of retransmissions reaches the preset limit, the central station records the retransmission failure event and updates the corresponding receipt failure event record of the IoT device. The central station uses the cumulative number of retransmissions and the record of failed receipt events as the retransmission control status.

7. The IoT data transmission method based on a central station as described in claim 1, characterized in that: The update and reconfiguration of the binding relationship between IoT devices and target wireless gateways, as well as the traffic routing and bearer configuration strategies, specifically involves: The central station determines whether the current IoT device meets the preset reliability switching conditions based on the acknowledgment failure event records and the cumulative number of retransmissions in the retransmission control status. When the reliability switching conditions are met, the central station freezes the bearer identification information corresponding to the current IoT device and re-evaluates the operating status of each wireless gateway to determine the new target wireless gateway. The central station updates the binding relationship between IoT devices and the new target wireless gateway in the device-gateway binding table, and sends the new target wireless gateway identification information to the IoT devices; The central station initiates a policy update request to the mobile communication core network to change the traffic routing and bearer configuration policy corresponding to the IoT device, and generates new bearer identification information and sends it to the new target wireless gateway, while notifying the original target wireless gateway to release the corresponding resources.

8. The IoT data transmission method based on a central station as described in claim 7, characterized in that: The reassessment of the operating status of each wireless gateway refers to the central station comparing and analyzing the available bandwidth and queuing depth of each wireless gateway based on the real-time operating status information reported by each wireless gateway, and selecting the wireless gateway with the largest available bandwidth and the smallest queuing depth as the new target wireless gateway.

9. The IoT data transmission method based on a central station as described in claim 1, characterized in that: The mobile communication core network refers to a mobile communication core network platform that supports a control plane and user plane separation architecture, supports policy control interfaces, and can dynamically control user plane data forwarding paths.

Images