Downlink data processing method and device, equipment and storage medium

Abstract

The invention discloses a downlink data processing method and device, equipment and a storage medium. The method comprises the following steps: receiving downlink data sent by a base station, and obtaining a time slice field used for indicating a frame-level service attribute from frame header information of the downlink data; analyzing the time slice field into a mapping bitmap used for representing a terminal device set; under the condition that the bit corresponding to the terminal equipment in the mapping bitmap is determined to be set, performing forward error correction decoding on the downlink data to recover the baseband frame payload of the downlink data; performing protocol decapsulation on the baseband frame payload to obtain a protocol data unit; and in a case where it is determined that the protocol data unit corresponds to the terminal, performing upper-layer processing on the protocol data unit. According to the scheme, a frame-level service attribute sensing mechanism based on a time slice field, a terminal judgment mechanism driven by a mapping bitmap and a layered downlink data analysis and processing flow are introduced, so that efficient collaboration of downlink data in the stages of receiving, judgment, decoding and protocol processing is realized.

Description

Technical Field

[0001] This application relates to the field of wireless communication technology, and in particular to a downlink data processing method, apparatus, device and storage medium. Background Technology

[0002] With the rapid evolution of satellite communication technology, broadband multimedia broadcasting technology, and integrated air-space-ground communication systems for converged networks, downlink data processing mechanisms are widely used in scenarios such as satellite internet access, airborne / shipborne communication terminals, emergency communication equipment, and remote IoT terminals. These systems typically require data coordination and addressing control between broadcast satellite links and connection-oriented terrestrial mobile communication networks to ensure data accessibility and link resource utilization efficiency under simultaneous operation of multiple terminals and services.

[0003] However, in actual deployment scenarios, due to the inherent broadcast transmission attributes of the DVB-S2 (Digital Video Broadcasting-Satellite-Second Generation) system, the limitations of GSE (Generic Stream Encapsulation) encapsulation granularity, and the sensitivity of terminal-side power consumption, traditional data addressing and resolution mechanisms have significant limitations in terms of stability, efficiency, and scalability. For example, the DVB-S2 physical layer is mainly broadcast, and its PLFRAME (Physical Layer Frame) usually carries a continuous generic stream. It lacks a scrambling and assignment mechanism similar to the RNTI (Radio Network Temporary Identifier) ​​used in 5G for user-level addressing, making it difficult to accurately map data to specific terminals in broadcast links. Furthermore, although DVB-S2 carries upper-layer services through GSE, the Label field in the GSE header is mainly used to distinguish service systems or service channels, and cannot be refined to the terminal identification granularity corresponding to the PDU (Protocol Data Unit) level. Extending the GSE format also requires deep modifications to the firmware of commercial DVB modules, resulting in high implementation costs and significant compatibility risks. Simultaneously, if the terminal cannot complete fast filtering at the physical layer or frame header layer, and must perform a complete processing flow of receiving, demodulating, FEC (Forward Error Correction) decoding, and GSE decapsulation on all DVB-S2 physical frames to determine whether data belongs to it, this will lead to a large amount of invalid processing, significantly increasing terminal power consumption. This is particularly detrimental to battery-powered mobile terminals, lightweight IoT (Internet of Things) terminals, or long-term independently deployed satellite access equipment. Summary of the Invention

[0004] This application provides a downlink data processing method, apparatus, device, and storage medium. By introducing a frame-level service attribute indication mechanism based on a time-slice field and a terminal device set bitmap parsing mechanism, it achieves accurate identification, rapid discrimination, and efficient processing of downlink data. Through a collaborative design of bitmap addressing, conditional decoding, and layered decapsulation, this solution ensures efficient utilization of downlink resources while improving the timeliness of terminal-side processing and service isolation capabilities. It boasts advantages such as lightweight design, strong versatility, and low latency, making it suitable for efficient downlink data processing needs in cellular communication systems, vehicle-to-everything (V2X) communication systems, and multi-terminal concurrent scenarios.

[0005] In a first aspect, this application provides a downlink data processing method applied to a terminal device, comprising:

[0006] Receive downlink data sent by the base station, and obtain the time slice field used to indicate frame-level service attributes from the frame header information of the downlink data; The time slice field is parsed into a mapping bitmap that represents the set of terminal devices; If it is determined that the bit corresponding to the terminal device in the mapping bitmap is set, forward error correction decoding is performed on the downlink data to recover the baseband frame payload of the downlink data; The baseband frame payload is decapsulated to obtain protocol data units; If it is determined that the protocol data unit corresponds to the terminal device, upper-layer processing is performed on the protocol data unit.

[0007] Secondly, this application provides a downlink data processing method applied to a base station, comprising: Obtain the target data to be sent, and iterate through the target data to obtain the corresponding terminal device; A mapping bitmap is generated based on the terminal device, and the bits corresponding to the terminal device in the mapping bitmap are set. The terminal device performs protocol encapsulation on the target data to generate protocol data units; The baseband frame payload carrying the protocol data unit is forward-corrected and encoded to generate an encoded bit sequence; The frame header information carrying the mapped bitmap is framed with the encoded bit sequence to form downlink data, and the downlink data is sent to the terminal device.

[0008] Thirdly, this application provides a downlink data processing apparatus for use in a terminal device, comprising: The demodulation module is configured to receive downlink data sent by the base station and obtain the time slice field used to indicate frame-level service attributes from the frame header information of the downlink data. The mapping module is configured to parse the time slice field into a mapping bitmap for representing a set of terminal devices; The decoding module is configured to perform forward error correction decoding on the downlink data to recover the baseband frame payload of the downlink data when it is determined that the bit corresponding to the terminal device in the mapping bitmap is set. The decapsulation module is configured to perform protocol decapsulation on the baseband frame payload to obtain protocol data units; The processing module is configured to perform upper-layer processing on the protocol data unit when it is determined that the protocol data unit corresponds to the terminal device.

[0009] Fourthly, this application provides a downlink data processing apparatus applied to a base station, comprising: The traversal module is configured to acquire target data to be sent and traverse the target data to obtain the corresponding terminal device. The bit setting module is configured to generate a mapping bitmap based on the terminal device and set the bit bits in the mapping bitmap corresponding to the terminal device. The encapsulation module is configured to perform protocol encapsulation on the target data according to the terminal device to generate protocol data units; The encoding module is configured to perform forward error correction encoding on the baseband frame payload carrying the protocol data unit to generate an encoded bit sequence; The frame header module is configured to generate frame header information based on the mapping bitmap, wherein the mapping bitmap is located in the time slice field of the frame header information; The framing module is configured to frame the frame header information and the encoded bit sequence to form downlink data, and send the downlink data to the terminal device.

[0010] Fifthly, this application provides a downlink data processing device, comprising: One or more processors; A memory that stores one or more programs, which, when executed by one or more processors, cause the one or more processors to implement the downlink data processing method as described in the first aspect.

[0011] In a sixth aspect, this application provides a storage medium containing computer-executable instructions, which, when executed by a computer processor, are used to perform the downlink data processing method as described in the first aspect.

[0012] This application constructs a downlink data processing method based on frame-level service attribute indication and terminal device set mapping parsing, achieving accurate identification, effective filtering, and hierarchical processing of target downlink data. The method first receives downlink data sent by the base station and obtains the time slice field representing frame-level service attributes from the frame header information. Then, the time slice field is parsed into a mapping bitmap that characterizes the downlink scheduling range, enabling rapid determination of the terminal device set at a unified time scale. When the bit corresponding to the terminal in the mapping bitmap is set, the system triggers forward error correction decoding of the downlink data, recovering the baseband frame payload. After decoding, the payload is decapsulated to extract protocol data units. If the terminal determines that the protocol data unit belongs to its own service context, the upper-layer processing flow is further executed to complete the delivery of service data. This scheme, through the service indication capability of the time slice field and the fast addressing capability of the bitmap mapping, integrates scheduling determination, channel decoding, and protocol processing into a structured, low-latency processing link, thereby avoiding invalid decoding of non-target data by the terminal and improving the real-time performance, accuracy, and resource utilization efficiency of downlink data processing. Relying on the dual mechanisms of frame-level service attribute perception and terminal device set mapping, this method can operate stably in communication environments with multiple concurrent terminals and complex mixed service types. It is suitable for application scenarios with high requirements for downlink data processing accuracy and performance, such as cellular communication systems, satellite-terrestrial converged communication systems, and multi-terminal access systems. Attached Figure Description

[0013] Figure 1 This is a flowchart of a downlink data processing method for a terminal device provided in an embodiment of this application; Figure 2 This is a flowchart of a time slice field extraction method provided in an embodiment of this application; Figure 3 This is a flowchart of a bitmap determination method provided in an embodiment of this application; Figure 4 This is a flowchart of a protocol data unit determination method provided in an embodiment of this application; Figure 5 This is a flowchart of a downlink data processing method for a base station provided in an embodiment of this application; Figure 6 This is a flowchart illustrating the steps of a downlink data processing method for a terminal device provided in an embodiment of this application; Figure 7 This is a structural block diagram of a downlink data processing device for a terminal device provided in an embodiment of this application; Figure 8 This is a structural block diagram of a downlink data processing device for a base station provided in an embodiment of this application; Figure 9This is a schematic diagram of the structure of a downlink data processing device provided in an embodiment of this application. Detailed Implementation

[0014] To make the objectives, technical solutions, and advantages of this application clearer, specific embodiments of this application will be described in further detail below with reference to the accompanying drawings. It should be understood that the specific embodiments described herein are merely for explaining this application and not for limiting it. It should also be noted that, for ease of description, only the parts relevant to this application are shown in the drawings, not all of them. Before discussing exemplary embodiments in more detail, it should be mentioned that some exemplary embodiments are described as processes or methods depicted as flowcharts. Although the flowcharts describe operations (or steps) as being processed sequentially, many of these operations can be performed in parallel, concurrently, or simultaneously. Furthermore, the order of the operations can be rearranged. A process can be terminated when its operation is completed, but it may also have additional steps not included in the drawings. A process can correspond to a method, function, procedure, subroutine, subroutine, etc.

[0015] The terms "first," "second," etc., used in the specification and claims of this application are used to distinguish similar objects and not to describe a specific order or sequence. It should be understood that such use of data can be interchanged where appropriate so that embodiments of this application can be implemented in orders other than those illustrated or described herein, and the objects distinguished by "first," "second," etc., are generally of the same class and the number of objects is not limited; for example, a first object can be one or more. Furthermore, in the specification and claims, "and / or" indicates at least one of the connected objects, and the character " / " generally indicates that the preceding and following objects are in an "or" relationship.

[0016] Currently, with the accelerated evolution of space-ground converged networks, satellite internet, and 5G / 6G communication technologies, heterogeneous space-ground integrated communication systems are exhibiting characteristics of diversified link modes, differentiated protocol systems, and complex service requirements. In space-ground converged communication systems employing a "downlink DVB-S2 + uplink 5G NR (5G New Radio)" networking approach, the satellite and ground sides operate under different physical layer architectures and signaling systems, requiring fine-grained addressing, service mapping, and resource scheduling between the broadcast downlink and the connection-oriented uplink. However, DVB-S2 is essentially a broadcast system, and its physical layer structure and encapsulation methods differ fundamentally from the link addressing and terminal scheduling mechanisms of 5G NR, making it difficult to directly inherit key capabilities such as terminal identification, selective reception, and energy consumption control in a space-ground converged environment.

[0017] Existing downlink data processing solutions based on DVB-S2 still have significant technical limitations when used in satellite-ground converged service addressing scenarios. First, during the link access and user addressing phases, DVB-S2's physical frame structure primarily uses continuous general-purpose streams for transmission, lacking a user-level addressing mechanism similar to the PDCCH (Physical Downlink Control Channel) scrambling and RNTI binding in 5G NR. This results in a natural conflict between broadcast attributes and the connection-oriented addressing requirements of 5G, making it difficult for terminals to quickly determine their own services at the physical layer. Second, during the data encapsulation and service differentiation phases, although DVB-S2 uses GSE to carry upper-layer data, its Label field is mainly used for service type or business system differentiation, and cannot be refined to the user identifier of a single PDU. If RNTI-level addressing is achieved by extending or modifying the GSE identifier structure, it requires deep modifications to the commercial DVB module firmware, which is not only technically complex but also compromises the versatility and compatibility of existing equipment, making it difficult to implement in engineering. Secondly, regarding terminal power consumption and processing efficiency, the broadcast nature of DVB-S2 forces terminals to continuously receive, demodulate, and perform FEC decoding to determine whether data belongs to them, resulting in significant unnecessary processing overhead. This leads to severe energy waste and processing burden in resource-constrained scenarios, making it difficult to meet the low power consumption and high efficiency requirements of satellite-ground converged terminals. In summary, the traditional DVB-S2 downlink mechanism faces insurmountable technical bottlenecks in user addressing granularity, encapsulation expansion capabilities, and terminal energy efficiency management, limiting the efficient addressing and service scheduling capabilities of the "downlink DVB-S2 + uplink 5G NR" converged system.

[0018] Therefore, this invention aims to propose a downlink data processing method that can accurately identify, differentiate, and efficiently process target downlink data in a communication environment where base station downlink broadcast data and multi-terminal concurrent access coexist, thereby completing real-time reception and protocol parsing of terminal-side service data. This method utilizes the time slice field in the frame header to carry frame-level service attributes and parses it into a mapping bitmap of the terminal device set, achieving rapid location and addressing of terminal devices. This avoids the problems of invalid decoding, data mis-extraction, or resource waste commonly found in traditional broadcast processing methods. Based on the accurate confirmation of terminal device identity using the mapping bitmap, the system can trigger forward error correction decoding to recover the baseband frame payload when necessary, and extract protocol data units through a protocol decapsulation mechanism. If the protocol data unit is determined to belong to the current terminal service context, the upper-layer service processing flow is executed, achieving reliable data transmission between the physical layer, link layer, and upper-layer applications. This scheme complements the frame-level attribute expression capability of the time slice field with the fast addressing capability of bitmap mapping, significantly improving the accuracy and robustness of downlink data judgment and processing, reducing the overhead of terminal decoding irrelevant data, and enhancing the system's processing efficiency and resource utilization in multi-terminal, multi-service, and dynamic scheduling scenarios. Furthermore, this invention exhibits good adaptability in complex network service mixtures and environments with coexisting different service types, and can be widely applied to cellular communication systems, integrated satellite-terrestrial communication systems, and multi-terminal concurrent service carrying scenarios, providing solid technical support for the real-time performance, reliability, and scheduling flexibility of downlink data.

[0019] Figure 1 This is a flowchart illustrating a downlink data processing method for a terminal device according to an embodiment of this application. (Reference) Figure 1 The downlink data processing method of this terminal device specifically includes: S110. Receive downlink data sent by the base station, and obtain the time slice field used to indicate frame-level service attributes from the frame header information of the downlink data.

[0020] In some embodiments, downlink data may be physical layer or link layer data frames transmitted by the base station to the terminal device via the radio interface. The frame header information is used to carry control fields related to data scheduling, service attributes, and decoding configuration. The time slice field can serve as frame-level service attribute identification information, indicating the service type, terminal device set, or scheduling time resource allocation corresponding to the downlink data frame, providing a basis for subsequent data filtering and processing.

[0021] In one embodiment, the method of receiving downlink data may be as follows: the terminal device performs radio frequency reception, down-conversion and analog-to-digital conversion processing on the wireless signal sent by the base station through the wireless receiving module to obtain the corresponding baseband signal data, and performs preliminary synchronization and frame structure identification on the baseband signal to extract the complete downlink data.

[0022] In one embodiment, the time slice field can be obtained by parsing the physical layer frame header or baseband frame header of the downlink data frame and extracting the time slice field, which indicates frame-level service attributes. The time slice field can be a control field used to characterize time-domain resource allocation, service scheduling identifiers, or terminal grouping information, and is used to describe the service affiliation of the data frame in the time dimension.

[0023] In one embodiment, the time slice field can be represented by an encoding method, such as a combination of bits, an index number, or a mapping identifier, for subsequent parsing into a terminal device set identifier, a service type identifier, or a scheduling strategy parameter.

[0024] Through the above steps, the time slice field used to indicate frame-level service attributes can be accurately obtained from the downlink data sent by the base station, providing basic data support for subsequent terminal device set mapping, data filtering and processing, and service scheduling control, thereby constructing a unified entry point and parsing foundation for downlink data processing methods.

[0025] Optionally, Figure 2 This is a flowchart illustrating a method for extracting a time slice field provided in an embodiment of this application. (Reference) Figure 2 The specific methods for extracting the time slice field include: S1101. Demodulate the physical layer frame header of the downlink data to obtain demodulation parameters for physical layer demodulation configuration.

[0026] For example, the physical layer frame header can be used to carry control information required for downlink data transmission at the physical layer, while the demodulation parameters indicate the specific configuration method for the physical layer to demodulate and decode the downlink data. By demodulating the physical layer frame header, the demodulation parameters can be obtained in advance, providing a basic configuration basis for the correct demodulation and decoding of subsequent downlink data.

[0027] In one embodiment, the demodulation of the physical layer frame header can be achieved by the terminal performing synchronization, frequency offset correction, and channel estimation processing on the received wireless signal, and then demodulating the signal resources corresponding to the physical layer frame header to obtain the physical layer frame header bit information.

[0028] In one embodiment, the demodulation parameters can be obtained by parsing the physical layer frame header bit information obtained from the demodulation, and extracting demodulation parameters used to indicate the modulation scheme, coding rate, resource allocation, or decoding mode. For example, the demodulation parameters may include the modulation order, channel coding scheme, code rate indication information, or physical resource block allocation information.

[0029] Through the above steps, demodulation parameters for physical layer demodulation configuration can be obtained from the physical layer frame header of the demodulated downlink data. This enables the pre-acquisition and accurate matching of demodulation configuration in the downlink data reception process, providing a reliable physical layer processing foundation for subsequent time slice field parsing, forward error correction decoding, and protocol decapsulation.

[0030] S1102. Demodulate the frame header portion of the downlink data based on the demodulation parameters to obtain the baseband frame header.

[0031] For example, the baseband frame header can be the baseband domain representation obtained after demodulation of the downlink data physical layer frame header, used to carry the control information required for subsequent baseband processing and protocol parsing. By performing targeted demodulation on the frame header based on the demodulation parameters, it can be ensured that the frame header information is accurately recovered, providing reliable input for subsequent time slice field parsing and service determination.

[0032] In one embodiment, demodulation of the downlink data frame header can be performed by the terminal performing demodulation processing on the frame header resource unit based on demodulation parameters obtained from the physical layer frame header to obtain the baseband frame header. The demodulation processing may include operations such as constellation demapping, soft bit generation, or symbol decision to convert the received physical layer signal into a baseband bit sequence.

[0033] Through the above steps, the frame header of the downlink data can be accurately demodulated based on the demodulation parameters to obtain a reliable baseband frame header. This enables effective conversion from physical layer signals to baseband control information, providing a key foundation for subsequent time slice field parsing, mapping bitmap generation, and downlink data filtering and processing.

[0034] S1103. Extract the time slice field from the baseband frame header.

[0035] For example, the time slice field can be used to identify the service affiliation of downlink data frames in the time domain resources, and is a key control information characterizing frame-level service attributes. By extracting the time slice field from the baseband frame header, reliable basic data can be provided for subsequent data frame filtering, bitmap generation, and upper-layer protocol processing by the terminal.

[0036] In one embodiment, the time slice field can be extracted as follows: the terminal performs bit-level parsing on the demodulated baseband frame header, and obtains the time slice field from a fixed bit position or a variable field position according to the predefined frame header structure in the communication protocol. The time slice field can be represented in the form of binary encoding, index number, or mapping identifier, and is used to describe the time slice or set of terminal devices corresponding to the data frame.

[0037] Through the above steps, the time slice field can be reliably extracted from the baseband frame header, enabling the acquisition of key data for determining the downlink data frame and terminal device set. This provides an accurate foundation for subsequent bitmap generation, forward error correction decoding, and protocol decapsulation, ensuring the integrity and stability of the downlink data processing flow.

[0038] S120. The time slice field is parsed into a mapping bitmap used to represent the set of terminal devices.

[0039] In some embodiments, the mapping bitmap can be used to represent the set of terminal devices corresponding to the current downlink data frame, describing at the bit level whether multiple terminals are scheduled or have the permission to receive the downlink data within the time slice. Each bit in the mapping bitmap can correspond to a terminal or a terminal identifier index, used to indicate the service association status of the corresponding terminal within the time slice.

[0040] In one embodiment, the mapping bitmap can be obtained by performing bit decomposition, index mapping, or table lookup transformation on the time slice field according to predefined time slice field encoding rules, converting the scheduling information carried in the time slice field into a mapping bitmap of fixed or variable length. For example, different bits or subfields in the time slice field can correspond to different terminal groups or terminal number ranges.

[0041] Through the above steps, the time slice field in the frame header can be converted into a mapping bitmap that represents the set of terminal devices, so that the terminal device information of the downlink data frame is presented in a structured and determinable form, providing a clear basis for subsequent terminal matching judgment, forward error correction decoding and upper-layer data processing, thereby improving the accuracy and efficiency of the downlink data processing process.

[0042] Optionally, after parsing the time slice field into a mapping bitmap for representing a set of terminal devices, the method further includes: If the bit corresponding to the terminal device in the mapping bitmap is not set, the terminal device is controlled to enter a low-power operation state.

[0043] For example, when the corresponding bit in the mapping bitmap is not set by the terminal device, it indicates that the current downlink data frame is not scheduled or transmitted for that terminal device, and therefore no subsequent error correction decoding and upper-layer processing are required. By introducing a low-power control mechanism, the energy consumption of the terminal during the reception of non-target data frames can be effectively reduced, thereby improving the overall energy efficiency of the terminal device and the utilization rate of system resources.

[0044] In one embodiment, the method for determining the state of a corresponding bit in a terminal device can be as follows: the terminal device locates the corresponding bit in the bitmap based on its own identifier or index, and reads the state of that bit. If the bit is in an unset state, it is determined that the current downlink data frame does not belong to the terminal's target data set.

[0045] In one embodiment, low-power operation can be achieved by: reducing the power consumption of the wireless receiver module, shutting down some baseband processing circuits, pausing demodulation and decoding operations, or adjusting the processor's operating frequency and scheduling strategy to reduce energy consumption without affecting the reception capability of subsequent frames.

[0046] Through the above steps, it is possible to determine whether the terminal is a downlink data frame target based on the mapped bitmap, and automatically enter a low-power operation state when not scheduled, thereby improving the energy efficiency management capability of the terminal device, reducing the burden of invalid data processing, and ensuring the efficiency and stability of the downlink data processing flow.

[0047] S130. If it is determined that the bit corresponding to the terminal device in the mapping bitmap is set, forward error correction decoding is performed on the downlink data to recover the baseband frame payload of the downlink data.

[0048] In some embodiments, forward error correction decoding can be used to correct errors in channel-coded downlink data to recover the original baseband frame payload. By introducing a mapping bitmap determination mechanism before performing forward error correction decoding, invalid decoding of data from non-terminal device sets by the terminal device can be avoided, thereby reducing computational overhead and improving downlink data processing efficiency.

[0049] In one embodiment, the determination method for the mapped bitmap may be as follows: the terminal device locates the corresponding bit in the mapped bitmap based on its own terminal identifier or terminal index, and determines the value state of the bit. When the bit is set, it is determined that the current downlink data frame is related to the terminal, thereby triggering further decoding processing of the downlink data frame.

[0050] In one embodiment, forward error correction decoding can be performed by executing error correction decoding on downlink data according to a pre-defined channel coding scheme in the communication protocol to correct bit errors caused by noise, interference, or channel fading during transmission and restore the corresponding baseband frame payload. Forward error correction decoding methods may include, but are not limited to, convolutional code decoding, Turbo code decoding, LDPC (Low-Density Parity-Check) decoding, or Polar code decoding.

[0051] Through the above steps, forward error correction decoding can be conditionally performed based on the mapping bitmap determination, and error correction decoding and payload recovery can be performed only on downlink data frames related to the terminal, thereby improving the efficiency, reliability and terminal resource utilization of the downlink data processing process, and laying the foundation for subsequent protocol data unit parsing and upper-layer processing.

[0052] Optionally, Figure 3 This is a flowchart of a bitmap determination method provided in an embodiment of this application. (Reference) Figure 3 The specific methods for determining the mapped bitmap include: S1301. Obtain the local identifier field of the terminal device.

[0053] For example, the local identification field can be used to uniquely identify the terminal itself, and is used to match and determine whether to receive and process the corresponding downlink data by matching the terminal device information carried in the downlink data frame. By obtaining the local identification field of the terminal device, accurate basis can be provided for mapping bitmap determination, protocol data unit attribution determination, and upper-layer processing.

[0054] In one embodiment, the local identification field can be obtained by reading a unique terminal identifier, such as an International Mobile Equipment Identity (IMEI), a temporary identifier, a terminal index number, or a logical terminal identifier, from an identifier register, memory, or system configuration file stored internally in the terminal device.

[0055] Through the above steps, the local identification field of the terminal device can be accurately obtained, providing a reliable basis for matching downlink data frames with the terminal. This ensures that forward error correction decoding, protocol decapsulation, and upper-layer processing are performed only on downlink data of this terminal, achieving high efficiency and accuracy in downlink data processing.

[0056] S1302. Determine the target bit position of the local identifier field in the mapping bitmap according to the set mapping relationship between the identifier field and the bit position.

[0057] For example, the mapping bitmap is used to represent the set of terminal devices targeted by the downlink data frame, with each bit corresponding to one or a group of terminal identifiers. By mapping the terminal's local identifier field to the target bit in the bitmap, the terminal can determine whether it is scheduled to receive downlink data, providing precise triggering conditions for downlink data processing.

[0058] In one embodiment, the target bit can be determined by mapping the terminal identifier to the corresponding bit index in the bitmap based on a pre-defined mapping relationship between the identifier field and the bitmap bits, thereby determining the target bit. The mapping relationship can be implemented using a simple hash function, an index mapping table, or an algorithmic calculation method. For example, the terminal identifier can be mapped to a bit position within the length range of the bitmap using modulo operations.

[0059] Through the above steps, the target bit position of the terminal in the mapping bitmap can be accurately determined based on the local identification field and the preset mapping relationship. This provides a reliable basis for the terminal to determine whether it belongs to the downlink data frame target set, trigger forward error correction decoding and upper layer processing, and improves the accuracy and efficiency of the downlink data processing flow.

[0060] S1303. If the state of the target bit is consistent with the set state, determine that the target bit is set.

[0061] For example, the state of each bit in the mapping bitmap can be used to indicate whether the corresponding terminal is the target receiver of the downlink data frame. When the state of the target bit is consistent with the preset set state, it can be determined that the terminal is scheduled to receive the current downlink data, thereby triggering subsequent data processing procedures, including forward error correction decoding and protocol decapsulation.

[0062] In one embodiment, the method to determine whether the target bit is set may be: the terminal reads the current state of the corresponding target bit in the mapping bitmap and compares it with the set state. If the bit state is consistent with the set state, it is determined that the target bit is set, indicating that the terminal belongs to the target set of the downlink data frame.

[0063] In one embodiment, the state and set state of the target bit can be represented by binary identifiers, Boolean values, or logic high and low levels, where the set state can correspond to logic "1" and the unset state can correspond to logic "0", so that the terminal can quickly determine the bit state.

[0064] By following the steps above, it is possible to accurately determine whether the target bit is set, thereby determining whether the terminal is the target receiving object of the current downlink data frame. This provides a reliable basis for the triggering conditions of the downlink data processing flow, ensuring the accuracy and efficiency of forward error correction decoding, protocol decapsulation, and upper-layer processing.

[0065] S140. Perform protocol decapsulation on the baseband frame payload to obtain protocol data units.

[0066] In some embodiments, the baseband frame payload may be data content carrying higher-layer protocol information, recovered after forward error correction decoding. Protocol decapsulation is used to parse the encapsulation fields in the baseband frame payload layer by layer according to the hierarchical structure of the communication protocol stack, extracting the protocol data units carried therein. The protocol data units may be data entities of the link layer, network layer, or service layer, used for subsequent upper-layer processing on the terminal side.

[0067] In one embodiment, the protocol decapsulation can be performed by parsing the protocol header field and valid data field in the baseband frame payload according to a preset communication protocol format, removing the encapsulation information at the corresponding level, and restoring the encapsulated data content layer by layer. For example, the physical layer or link layer encapsulation fields can be parsed first, followed by the logical channel or service bearer related fields, ultimately obtaining the complete protocol data unit.

[0068] Through the above steps, the baseband frame payload recovered by forward error correction decoding can be decapsulated according to the protocol layer, accurately obtain the protocol data unit, realize the smooth connection of downlink data from the physical layer to the upper layer protocol processing, and provide a reliable data foundation for subsequent terminal-side service judgment and upper layer processing.

[0069] S150. If it is determined that the protocol data unit corresponds to the terminal device, upper-layer processing is performed on the protocol data unit.

[0070] In some embodiments, upper-layer processing can be used to perform business parsing, protocol processing, or application layer operations on the decapsulated protocol data units to complete the final consumption of downlink data or business response. By introducing a protocol data unit attribution determination mechanism before executing upper-layer processing, invalid processing of data not belonging to the terminal device can be avoided, thereby improving system processing efficiency and terminal device resource utilization.

[0071] In one embodiment, determining the matching method between a protocol data unit and a terminal device can be achieved by matching the protocol data unit with the current terminal device based on the terminal identifier, address information, or service context identifier carried in the protocol data unit. For example, it can be compared whether the terminal identifier in the protocol data unit is consistent with the terminal device's own identifier, or it can be determined whether the logical channel or bearer identifier to which the protocol data unit belongs matches the current session state of the terminal.

[0072] In one embodiment, the upper-layer processing can be performed by submitting the protocol data unit to the corresponding protocol processing module or application processing module to perform operations such as data reassembly, business parsing, state updates, or application callbacks. For example, the protocol data unit can be handed over to the network layer for routing processing, or to the application layer for business data parsing and function execution.

[0073] Through the above steps, upper-layer processing can be conditionally executed based on the determination of the ownership of protocol data units, ensuring that terminal devices only perform business processing on downlink data related to themselves, realizing a complete closed loop of downlink data processing flow, and improving terminal processing efficiency, system reliability and business execution accuracy.

[0074] Optionally, Figure 4 This is a flowchart of a protocol data unit determination method provided in an embodiment of this application. (Reference) Figure 4 The specific methods for determining data units in this protocol include: S1501. Parse the header of the protocol data unit to obtain the terminal identifier field carried therein for indicating the terminal device.

[0075] For example, the protocol data unit header typically carries control information to identify the terminal device or set of terminal devices. By parsing the header, the terminal identification field can be obtained, providing a basis for the terminal device to determine whether it is the recipient of downlink data frames. This step is a crucial link in the transmission of downlink data from the protocol layer to the terminal service processing layer.

[0076] In one embodiment, parsing the protocol data unit header can be done by reading the terminal identification field from a fixed-byte position or a variable-length field according to the field definitions in the protocol data unit header. The terminal identification field may include a logical terminal identifier, a physical terminal address, a temporary session identifier, or a combined encoding form, used to accurately indicate the terminal device.

[0077] Through the above steps, the identification field of the terminal device can be accurately extracted from the header of the protocol data unit, providing a reliable foundation for the terminal device to determine its own receiving permissions, perform subsequent upper-layer processing, and realize the targeted distribution of downlink data, thus ensuring the accuracy and stability of the downlink data processing flow.

[0078] S1502, if the terminal identifier field is consistent with the local identifier field of the terminal device, determine that the protocol data unit corresponds to the terminal device.

[0079] For example, the terminal identifier field in the protocol data unit is used to indicate the terminal device of the data unit. When the terminal identifier field of the protocol data unit is consistent with the local identifier field of the terminal itself, it can be determined that the protocol data unit corresponds to the current terminal device, thereby triggering the terminal to perform upper-layer processing or service execution operations on the data unit.

[0080] In one embodiment, the method to determine that a protocol data unit corresponds to a terminal may be: comparing the terminal identification field parsed from the protocol data unit with the identification field stored locally on the terminal; if the two match completely, the protocol data unit is determined to belong to the terminal device; otherwise, the protocol data unit is determined not to correspond to the terminal device, and thus the device is either discarded or delayed.

[0081] Through the above steps, it is possible to accurately determine whether the protocol data unit corresponds to the current terminal device, providing a reliable basis for the terminal device to conditionally perform forward error correction decoding, protocol decapsulation and upper-layer processing, and realizing the directionality, accuracy and efficiency of the downlink data processing flow.

[0082] Optionally, Figure 5 This is a flowchart illustrating a downlink data processing method for a base station provided in an embodiment of this application. (Reference) Figure 5 The downlink data processing method of this base station specifically includes: S210. Obtain the target data to be sent, and traverse the target data to obtain the corresponding terminal device.

[0083] In some embodiments, the target data may include downlink service data, control information, or multimedia content. Before transmission, the corresponding set of terminal devices needs to be determined to ensure that the downlink data can be correctly routed to the appropriate terminal. Obtaining the corresponding terminal devices by traversing the target data provides basic information for subsequent bitmap generation, frame header padding, and scheduling control.

[0084] In one embodiment, the target data can be obtained by the base station or scheduling unit reading the target data to be sent from the upper-layer service module, buffer queue, or database.

[0085] In one embodiment, the terminal device can be determined by: extracting a corresponding list of terminal identifiers based on the terminal device identifier carried in the target data or upper-layer service scheduling information, and then determining the corresponding terminal device through the list of terminal identifiers. The terminal identifiers in the list can be unique identifiers, logical indexes, or temporary session identifiers, used to identify the receiving object of each data frame.

[0086] Through the above steps, the set of terminal devices corresponding to the data to be sent can be systematically obtained, providing a precise basis for generating the mapping bitmap, constructing the frame header, and subsequent downlink data scheduling and transmission, thereby ensuring that downlink data can reach the terminal devices accurately and efficiently, and realizing the directionality and reliability of downlink data transmission.

[0087] S220. Generate a mapping bitmap based on the terminal device, and set the bit bits in the mapping bitmap corresponding to the terminal device.

[0088] For example, the mapping bitmap is used to represent the set of terminal devices to which the current downlink data frame is targeted, with each bit corresponding to one or a group of terminal identifiers. By generating the mapping bitmap and setting the bits corresponding to the terminal devices, targeted scheduling of downlink data can be achieved, thereby ensuring that data is sent only to terminal devices, improving system transmission efficiency and reducing the processing load on non-terminal devices.

[0089] In one embodiment, the mapping bitmap can be generated by creating a bitmap structure according to a predefined terminal index mapping rule. The bitmap length of the mapping bitmap can correspond to the total number of terminal devices or the number of logical groups to ensure that each terminal can be mapped to a unique bit.

[0090] In one embodiment, setting the bitmap can be achieved by converting the terminal identifier into a bit index in the bitmap through the mapping rules, and then setting the bit to logic "1" or a set state, thereby setting the bitmap. The set bit corresponding to the terminal indicates that the terminal is the receiving object of the current downlink data frame.

[0091] Through the above steps, a mapping bitmap can be generated based on the set of terminal devices, and the corresponding bits can be accurately set, providing a reliable basis for downlink data frame scheduling and terminal reception determination, and realizing the directionality, accuracy and efficiency of downlink data transmission.

[0092] Optionally, setting the bit corresponding to the terminal device in the mapping bitmap includes: Obtain the terminal identifier field of the terminal device; Based on the established mapping relationship between the identifier field and the bit, determine the target bit of the terminal identifier field in the mapping bitmap; Set the target bit in the mapped bitmap.

[0093] For example, the terminal identifier field is used to uniquely identify each terminal in order to determine the set of terminal devices in the downlink data frame. The mapping bitmap can be a sequence of bits representing the set of terminal devices, where each bit corresponds to one or a group of terminal identifiers, and setting the bit indicates that the corresponding terminal device is the receiving target. The target bit can be the bit position in the mapping bitmap corresponding to a specific terminal identifier field, used to indicate that the terminal device is the data receiving target.

[0094] In one embodiment, the terminal identifier field can be obtained by extracting the terminal identifier field from the terminal device registration information, session context, or system configuration table to uniquely identify the terminal.

[0095] In one embodiment, the target bit can be determined by mapping the terminal identifier field to the corresponding bit position in the mapping bitmap according to a preset mapping rule, and then determining the mapped bit position as the target bit. The mapping rule can be a hash mapping, an index table mapping, or a logical number mapping to ensure that different terminals have unique and identifiable positions in the mapping bitmap.

[0096] In one embodiment, the target bit can be set by setting the value of the target bit to "1" to indicate that the terminal device is the recipient of downlink data, while keeping the other bits unchanged, thereby completing the terminal device selection identifier for downlink data.

[0097] Through the above steps, the target bit can be determined and set in the mapping bitmap based on the terminal identification field, realizing the basic control of downlink data directional transmission and providing accurate terminal selection information for subsequent protocol encapsulation, encoding and transmission.

[0098] S230. The terminal device performs protocol encapsulation on the target data to generate a protocol data unit.

[0099] For example, protocol encapsulation is used to convert the target data to be sent into protocol data units suitable for physical layer transmission, while attaching control information to the header of the data unit to indicate the terminal device, thereby realizing the directional transmission of downlink data and terminal identification. The protocol data unit is an important carrier for the transmission of downlink data from the upper-layer service module to the physical layer.

[0100] In one embodiment, the protocol encapsulation can be performed by combining the target data with the protocol header information based on the set of terminal devices corresponding to each piece of target data. The protocol header information may include a terminal device identifier field, a data length field, a service type field, a serial number or checksum, etc., which are used by the terminal to determine data ownership and ensure data transmission integrity.

[0101] Through the above steps, the terminal device can perform protocol encapsulation on the target data to generate a protocol data unit containing complete control information and terminal device identification. This provides a reliable foundation for the targeted transmission of downlink data, terminal determination, and subsequent physical layer transmission, ensuring the accuracy and efficiency of the downlink data processing flow.

[0102] Optionally, the step of performing protocol encapsulation on the target data according to the terminal device to generate protocol data units includes: Obtain the terminal identifier field of the terminal device; The target data is encapsulated according to the terminal identifier field to generate a protocol data unit.

[0103] For example, a protocol data unit is used to encapsulate upper-layer data to be transmitted in a communication system for transmission and decoding in downlink data frames. The terminal identification field can be a bit sequence or identifier that uniquely identifies each terminal, used to determine the target receiving terminal of the protocol data unit.

[0104] In one embodiment, the terminal identifier field can be obtained by extracting the terminal identifier field from the terminal registration information, session context, or system configuration table to uniquely identify the terminal device.

[0105] In one embodiment, the protocol encapsulation method can be: combining the target data with the terminal identification field and necessary control information, serial number, check code, etc., to form a protocol data unit, ensuring that the receiving end can identify whether the data belongs to itself based on the terminal identification field during decoding, and can correctly parse the protocol data.

[0106] Through the above steps, the target data and the corresponding terminal identification field can be encapsulated into a protocol data unit, enabling the directional transmission and correct reception of downlink data between terminals, and providing a basic data structure for subsequent encoding, framing and transmission.

[0107] S240. Perform forward error correction coding on the baseband frame payload carrying the protocol data unit to generate a coded bit sequence.

[0108] For example, the baseband frame payload can be a bit sequence carrying protocol data units, and the encoded bit sequence can be a sequence containing original data bits and redundancy check bits. Forward error correction coding is used to enhance the reliability of downlink data during transmission. By redundantly coding the baseband frame payload, even in the presence of noise, interference or packet loss in the channel, the receiver can be guaranteed to correctly recover the protocol data units, thereby improving the robustness and stability of the system transmission.

[0109] In one embodiment, the method for performing forward error correction coding on the baseband frame payload can be as follows: taking the protocol data unit generated by protocol encapsulation of the target data as input, applying a preset coding algorithm, such as convolutional code, LDPC code, Turbo code or polar code, to combine the original data bits with the redundancy check bits to generate a coded bit sequence with error correction capability.

[0110] Through the above steps, the baseband frame payload carrying the protocol data unit can be converted into an error-correcting coded bit sequence, providing a reliable foundation for subsequent physical layer modulation, mapping, and downlink transmission, and ensuring accurate reception and decoding of downlink data under complex channel conditions.

[0111] S250. Generate frame header information based on the mapping bitmap, wherein the mapping bitmap is located in the time slice field of the frame header information.

[0112] For example, the frame header information can be control information and terminal device indication information used to carry downlink data, so that the terminal can determine whether to receive the corresponding downlink data. The mapping bitmap can be used to represent a set of terminal devices, where each bit corresponds to one or a group of terminal identifiers, and setting the bit indicates that the corresponding terminal is the recipient of downlink data. In this step, the mapping bitmap is placed in the time slice field of the frame header information to indicate the frame-level service attributes and the reception eligibility of the set of terminal devices.

[0113] In one embodiment, the frame header information can be generated by converting the mapped bitmap into a bit sequence that conforms to the frame header structure specification and filling it into the time slice field. At the same time, a frame sequence number, checksum, or other control fields can be attached to form complete frame header information.

[0114] Through the above steps, frame header information can be generated based on the set of terminal devices, and the mapping bitmap can be embedded in the time slice field, providing a reliable basis for the targeted transmission of downlink data and terminal determination, ensuring that downlink data can be efficiently and accurately transmitted to the corresponding terminal devices.

[0115] S260. The frame header information and the encoded bit sequence are framed to form downlink data, and the downlink data is sent to the terminal device.

[0116] For example, downlink data is used to transmit baseband frame payload and control information to terminal devices, enabling directional downlink transmission. The frame header information can be structured data containing a mapping bitmap, sequence number, timestamp, and other control fields, used to indicate frame-level service attributes and the set of terminal devices corresponding to the downlink data. The mapping bitmap can be a bit sequence representing the set of terminal devices, where each bit corresponds to one or a group of terminal identifiers, and setting a bit indicates that the terminal is the receiving target. The encoded bit sequence can be a bit sequence generated by forward error correction coding of the baseband frame payload carrying protocol data units, containing original data bits and redundancy check bits, used to improve the transmission reliability of downlink data.

[0117] In one embodiment, the framing method may be: concatenating the frame header information as a preamble field with the encoded bit sequence to form complete downlink data, ensuring that the terminal can first parse the frame header to obtain terminal device information and mapping bitmap when receiving data, and then perform error correction decoding on the subsequent encoded bit sequence to recover the protocol data unit.

[0118] In one embodiment, the downlink data can be transmitted by means of communication methods such as physical layer modulation, time division multiplexing, or frequency division multiplexing, to transmit the framed downlink data to the corresponding terminal device, ensuring that only the terminal with the corresponding bit set receives and decodes the data, thereby achieving targeted transmission and downlink resource optimization.

[0119] Through the above steps, the frame header information and the encoded bit sequence can be framed to form complete downlink data, which can be reliably sent to the terminal device, realizing the overall process of downlink data directional transmission, terminal judgment and error correction decoding.

[0120] Optionally, the step of framing the frame header information and the coded bit sequence to form downlink data includes: Demodulation parameters are generated based on the modulation scheme, channel bandwidth, and coding format of the target data; Generate a physical layer frame header based on the demodulation parameters; The physical layer frame header, the frame header information, and the coded bit sequence are framed to form downlink data.

[0121] For example, downlink data is used to reliably transmit protocol data units and control information to terminal devices. The frame header information can be structured data carrying a mapping bitmap, sequence number, timestamp, and other control fields, used to indicate frame-level service attributes and the set of terminal devices. The coded bit sequence can be a bit sequence generated by forward error correction coding of the baseband frame payload carrying protocol data units, containing original data bits and redundancy check bits, used to improve the reliability of downlink data transmission. Demodulation parameters can be information such as modulation scheme, channel bandwidth, and coding format, used by the receiver's physical layer to correctly demodulate and recover the baseband frame payload. The physical layer frame header can be a preamble field containing demodulation parameters, sequence number, and checksum, used to guide the terminal in demodulating data at the physical layer.

[0122] In one embodiment, the demodulation parameters can be generated by extracting the modulation scheme, channel bandwidth, and coding format corresponding to the target data, and generating demodulation parameters for the physical layer of the receiver accordingly.

[0123] In one embodiment, the physical layer frame header can be generated by encoding the demodulation parameters into a bit sequence according to the frame header structure specification to form a physical layer frame header that can be directly appended to the front end of the downlink data, ensuring that the terminal can correctly demodulate the downlink data when receiving it.

[0124] In one embodiment, the framing method may be as follows: placing the physical layer frame header at the beginning of the frame header, followed by the frame header information and the encoded bit sequence to form complete downlink data, so that the terminal can first parse the physical layer frame header to obtain demodulation parameters, then parse the frame header information to determine the terminal device set, and finally perform error correction decoding on the encoded bit sequence to recover the protocol data unit.

[0125] Through the above steps, a complete downlink data frame can be generated based on the target data characteristics and physical layer parameters, realizing the overall process of physical layer demodulation, terminal determination and error correction decoding, and providing reliable support for the targeted transmission of downlink data.

[0126] Optionally, Figure 6 This is a flowchart illustrating the steps of a downlink data processing method for a terminal device provided in an embodiment of this application. (Reference) Figure 6 The downlink data processing method of this terminal device specifically includes: S301, Receives DVB-S2 radio frequency signals.

[0127] For example, the DVB-S2 radio frequency signal can be a digital video broadcast signal relayed by a satellite and downlinked in the target frequency band. This signal follows the DVB-S2 or DVB-S2X (Digital Video Broadcasting-Satellite-SecondGeneration eXtended) standard protocol, and adopts modulation methods such as QPSK (Quadrature Phase Shift Keying), 8PSK (8-Phase Shift Keying), 16APSK (16-Amplitude and Phase Shift Keying), or 32APSK (32-Amplitude and Phase Shift Keying). It also combines LDPC and BCH (Bose–Chaudhuri–Hocquenghem) concatenated error correction coding mechanism for channel protection. Receiving DVB-S2 radio frequency signals can be accomplished through the terminal's radio frequency receiving unit. The radio frequency receiving unit may include a low-noise amplifier, a down-conversion module, and an analog-to-digital conversion module, which are used to convert the high-frequency radio frequency signals received over the air interface into intermediate frequency or baseband digital signals.

[0128] In one embodiment, the DVB-S2 radio frequency signal may carry physical layer frame structure information, pilot sequence, and physical layer frame header field. The physical layer frame header is used to indicate the modulation and coding scheme, frame length, and channel parameters, providing a configuration basis for subsequent synchronization, demodulation, and decoding processes.

[0129] S302, Demodulate PLLHEADER / BBHEADER and extract TSN.

[0130] Exemplarily, the PLHEADER (Physical Layer Header) can be a DVB - S2 physical layer header, which is used to characterize physical layer parameters such as the modulation method, coding format, frame type, and pilot configuration corresponding to the current physical layer frame; the BBHEADER (BaseBand Header) can be used to indicate the data type, payload length, synchronization information, and upper - layer service - related identifier of the baseband frame. Demodulating the PLHEADER / BBHEADER can be based on the received baseband digital signal, performing symbol decision and field parsing on the physical layer header and the baseband header according to predefined synchronization sequences and modulation rules to recover the control field information carried therein. The TSN (Time Slot Number) can be a time - slot field, which is used to characterize the scheduling position of the current baseband frame or service data in the time dimension. Exemplarily, the TSN can be located in a preset field of the BBHEADER, and is used to indicate the time - slot index, service scheduling period, or terminal device set mapping relationship corresponding to the baseband frame.

[0131] In one embodiment, by demodulating and parsing the PLHEADER / BBHEADER to extract the TSN, it can provide an index basis in the time dimension for subsequent terminal identification, mapping bitmap matching, or service selection processing based on time slots.

[0132] In one embodiment, the terminal device performs physical layer header demodulation on the received DVB - S2 radio frequency signal, obtains the PLHEADER and the BBHEADER, and extracts the TSN field for service indication from the BBHEADER, where the TSN field characterizes the set of terminal devices associated with the current physical frame in the form of a bitmap.

[0133] S303 - S304. When TSN & (1 << My_Bit_Index) is not true, go to sleep.

[0134] Exemplarily, the TSN may be a time slice field, which may be in the form of a bitmap or a bit mask, and is used to represent the set of terminal devices scheduled or woken up within the current time slice. My_Bit_Index may be the target bit corresponding to the current terminal, and is used to uniquely indicate the position of the terminal in the TSN mapping bitmap. Exemplarily, My_Bit_Index may be determined by looking up a table or a mapping rule according to the terminal identification field, physical address or pre-allocated terminal number of the terminal. (1<<My_Bit_Index) may be a bit mask generated by a left shift operation, and is used to indicate the target bit corresponding to the current terminal in the TSN. TSN&(1<<My_Bit_Index) may be a bitwise AND operation performed on the TSN and the bit mask, and is used to determine whether the target bit is set. Among them, the operation result being true indicates that the current terminal is included in the set of terminal devices corresponding to the current time slice, and the operation result not being true indicates that the current terminal is not scheduled.

[0135] In one embodiment, in the case where it is determined that TSN&(1<<My_Bit_Index) is not true, it can be determined that there is no service data or control information for the terminal within the current time slice, and the terminal does not need to continue to execute subsequent demodulation, decoding or protocol processing procedures. In this case, the control terminal enters the sleep state, and the sleep state may be a low-power operating state in which part of the radio frequency receiving link is turned off, the clock frequency of the baseband processing unit is reduced or the protocol stack processing is paused, so as to reduce the energy consumption of the terminal in the non-scheduled time slice.

[0136] In one embodiment, based on the RNTI mapping rule of the terminal itself, the corresponding bitmap bit index My_Bit_Index is determined, and a bitwise AND operation is performed on the TSN and (1<<My_Bit_Index); in the case where the determination result is not true, it is determined that the current physical frame does not contain downlink data related to the terminal, the subsequent processing of the physical frame is terminated, and the sleep state is entered to skip the FEC decoding and data extraction processes.

[0137] S303 - S305, when TSN&(1<<My_Bit_Index) is true, perform LDPC decoding on the entire FECFRAME.

[0138] Exemplarily, when it is determined that TSN & (1 << My_Bit_Index) is true, it can be determined that the current FECFRAME contains valid service data or control information for this terminal, and the terminal needs to continue to perform subsequent channel decoding processing. FECFRAME (Forward Error Correction Frame) can be a channel coding frame formed by forward error correction coding, used to carry the baseband frame payload, which can include system information, service data, or protocol data units.

[0139] In one embodiment, performing LDPC decoding on the entire FECFRAME can be based on the LDPC (Low Density Parity Check) decoding algorithm defined by the DVB-S2 specification, and performing iterative decoding processing on the received soft decision or hard decision bit sequence to correct the bit errors introduced during channel transmission and restore the corresponding baseband frame bit sequence. By performing LDPC decoding only after confirming that the terminal is scheduled, it is possible to avoid performing invalid decoding processing on the data frames of non-terminal devices, thereby reducing the computing load and energy consumption of the terminal.

[0140] S306. Extract the IP / MAC data packet.

[0141] Exemplarily, after completing LDPC decoding of the FECFRAME and obtaining the corresponding baseband frame bit sequence, subsequent protocol layer parsing processing can be performed on the decoded baseband data to extract the carried IP (Internet Protocol) / MAC (Media Access Control) data packet. The baseband frame bit sequence can be the valid payload data after BBFRAME (BaseBand Frame) decoding, and it can carry network layer or link layer data according to a preset protocol encapsulation format inside.

[0142] In one embodiment, extracting the IP / MAC data packet can include: distinguishing whether the baseband data carries an IP data packet or a MAC frame according to the protocol type identifier or encapsulation header field, and parsing the corresponding protocol header to obtain a complete IP data message or MAC layer data frame. Among them, the IP data packet can be a data unit conforming to the IPv4 or IPv6 protocol format, including a source IP address, a destination IP address, a protocol type, and payload data; the MAC data packet can be a data frame conforming to the Ethernet or other link layer protocol format, including a source MAC address, a destination MAC address, and a frame check field.

[0143] In one embodiment, by performing IP / MAC packet extraction processing after LDPC decoding, the baseband bit sequence recovered from the physical layer and channel layer can be further restored into data units that can be processed by upper-layer network protocols or service applications, providing a foundation for subsequent data forwarding, service parsing, or terminal application processing.

[0144] S307. Parse the MAC PDU header and extract the RNTI CE (Control Element).

[0145] For example, after extracting the MAC data packet, the header fields of the MAC PDU can be parsed to identify and extract the carried RNTI control unit. A MAC PDU can be a data unit consisting of one or more MAC sub-headers and corresponding MACSDUs (Service Data Units) or control units. The MAC PDU header may contain an identifier field indicating the type, length, and control information of each sub-header. The RNTI CE can be a type of MAC layer control unit used to carry the RNTI (Radio Network Temporary Identifier) ​​of a terminal in the wireless network or control information related to the RNTI. By identifying the type identifier in the sub-header indicating the RNTI CE, the corresponding RNTI CE content can be extracted from the MAC PDU.

[0146] In one embodiment, parsing the MAC PDU header may include: parsing each MAC sub-header sequentially according to a preset MAC layer protocol format, and determining whether there is a sub-header of the control unit type.

[0147] In one embodiment, by parsing the MAC PDU header and extracting the RNTI CE, information related to terminal identification or scheduling control can be obtained directly at the MAC layer without relying on higher-level protocol parsing, providing a basis for subsequent terminal identity verification, data matching, or scheduling status determination.

[0148] S308~S309: If RNTI_CE==My_RNTI is not true, discard the radio frequency signal.

[0149] For example, RNTI_CE can be the RNTI control unit identifier extracted from the MAC PDU header, which is used to indicate the terminal device identifier corresponding to the current MAC data unit; My_RNTI can be a local wireless network temporary identifier that is pre-configured or assigned to the current terminal during the access process, which is used to uniquely identify the terminal's scheduling object identity in the wireless system.

[0150] In one embodiment, determining whether RNTI_CE == My_RNTI can be achieved by comparing the consistency of RNTI_CE parsed from the MAC layer with My_RNTI stored locally on the terminal. If the comparison result is false, it indicates that the data currently decoded and parsed is not intended for this terminal, but rather for service data or control information intended for other terminals.

[0151] In one embodiment, if RNTI_CE == My_RNTI is not true, the control terminal discards the corresponding radio frequency signal or its subsequent processing result. Discarding the radio frequency signal may include: terminating further protocol parsing and upper-layer processing of the current data unit; releasing the buffer resources associated with the data unit; and not reporting the data unit to the network layer or application layer.

[0152] In one embodiment, by performing radio frequency signal discarding processing based on RNTI consistency judgment at the MAC layer, non-terminal device data can be prevented from entering the upper-layer protocol stack, reducing the computational overhead caused by invalid processing, while improving the data processing efficiency and system security of the terminal in multi-user broadcast or shared channel environments.

[0153] S308~S310, when RNTI_CE==My_RNTI is true, submit the data corresponding to the radio frequency signal.

[0154] For example, the submitted data can be IP packets, service load data, or control signaling data, which can be sent to the network protocol stack, service processing unit, or application layer module for further processing according to the system architecture.

[0155] In one embodiment, the data corresponding to the submitted radio frequency signal can be: submitting valid data units obtained through physical layer reception, channel decoding, and MAC layer parsing to the upper-layer protocol processing module. For example, the submission process may include submitting the MAC SDU to the network layer or link layer processing module, or submitting the parsed IP data packet to the IP layer protocol stack for further data reassembly, forwarding, or service processing.

[0156] In one embodiment, by submitting the data corresponding to the radio frequency signal only after confirming RNTI consistency, it can be ensured that the terminal only performs upper-layer processing on the valid data facing itself, avoiding misprocessing of data of other terminals, thereby improving the data processing accuracy and overall operating efficiency of the system.

[0157] Through the above steps, the physical layer achieves pre-filtering of irrelevant downlink frames based on the TSN bitmap, and the MAC layer achieves accurate confirmation of target data based on the RNTI control unit, thereby constructing a two-level data filtering and receiving mechanism that utilizes physical layer coarse screening and MAC layer fine selection.

[0158] Based on the above embodiments, Figure 7 This is a structural block diagram of a downlink data processing device for a terminal device provided in an embodiment of this application. (Reference) Figure 7 The downlink data processing device for the terminal device provided in this embodiment specifically includes: a demodulation module 11, a mapping module 12, a decoding module 13, a deblocking module 14, and a processing module 15.

[0159] The demodulation module 11 is configured to receive downlink data sent by the base station and obtain a time slice field indicating frame-level service attributes from the frame header information of the downlink data; the mapping module 12 is configured to parse the time slice field into a mapping bitmap representing a set of terminal devices; the decoding module 13 is configured to perform forward error correction decoding on the downlink data to recover the baseband frame payload of the downlink data when it is determined that the bit corresponding to the terminal device in the mapping bitmap is set; the decapsulation module 14 is configured to perform protocol decapsulation on the baseband frame payload to obtain a protocol data unit; and the processing module 15 is configured to perform upper-layer processing on the protocol data unit when it is determined that the protocol data unit corresponds to the terminal device.

[0160] Based on the above embodiments, the demodulation module 11 includes: a demodulation parameter unit configured to demodulate the physical layer frame header of the downlink data to obtain demodulation parameters for physical layer demodulation configuration; a frame header demodulation unit configured to demodulate the frame header portion of the downlink data based on the demodulation parameters to obtain a baseband frame header; and a time slice extraction unit configured to extract a time slice field from the baseband frame header.

[0161] Based on the above embodiments, the decoding module 13 includes: a local identifier unit configured to acquire a local identifier field of the terminal device; a bit mapping unit configured to determine the target bit of the local identifier field in the mapping bitmap according to a set mapping relationship between the identifier field and the bit; and a bit setting unit configured to determine that the target bit is set when the state of the target bit is consistent with the set state.

[0162] Based on the above embodiments, the processing module 15 includes: a parsing unit configured to parse the header of the protocol data unit to obtain a terminal identifier field carried therein for indicating a terminal device; and a correspondence determination unit configured to determine that the protocol data unit corresponds to the terminal device when the terminal identifier field is consistent with the local identifier field of the terminal device.

[0163] Based on the above embodiments, the downlink data processing device for the terminal device further includes: a low-power module configured to control the terminal device to enter a low-power operating state when the bit corresponding to the terminal device in the mapping bitmap is not set.

[0164] The downlink data processing apparatus provided in this application embodiment, by constructing a hierarchical collaborative processing system consisting of a demodulation module 11, a mapping module 12, a decoding module 13, a decapsulation module 14, and a processing module 15, achieves multi-stage parsing of downlink data, terminal mapping determination, and upper-layer protocol processing, thereby improving the reliability, integrity, and processing accuracy of data recovery in complex communication environments. Specifically, the demodulation module 11 has downlink data reception and frame header parsing capabilities, used to receive downlink data sent by the base station and obtain the time slice field indicating frame-level service attributes from the frame header information of the downlink data, providing basic information for terminal mapping. The mapping module 12 undertakes the task of representing the set of terminal devices, determining the bit state of each terminal at the current moment by parsing the time slice field into a mapping bitmap, providing accurate positioning basis for subsequent decoding. The decoding module 13 is responsible for performing forward error correction decoding on the downlink data when the corresponding bit of the terminal in the mapping bitmap is set, to recover the effective payload of the baseband frame, ensuring that signal interference or bit errors that may exist during data transmission will not affect the acquisition of effective information. The decapsulation module 14 is responsible for protocol decapsulation, performing protocol decapsulation on the decoded baseband frame payload to obtain upper-layer protocol data units, thus achieving standardized processing of data in different protocol formats. The processing module 15, upon confirming the terminal corresponding to the protocol data unit, performs upper-layer processing operations on the protocol data unit, including data parsing, business logic execution, and response generation, achieving closed-loop control of downlink data from physical reception to business processing. Through the coordinated efforts of data acquisition and frame header parsing in the demodulation module, terminal mapping in the mapping module, error correction and recovery in the decoding module, protocol parsing in the decapsulation module, and upper-layer processing in the processing module, this device can maintain high-reliability downlink data processing capabilities under conditions of wireless channel fluctuations, frame loss, or protocol interference, improving the stability and processing accuracy of terminal data reception, and is suitable for multi-terminal communication and complex network scenarios.

[0165] The downlink data processing apparatus for the terminal device provided in this application embodiment can be used to execute the downlink data processing method for the terminal device provided in the above embodiment, and has corresponding functions and beneficial effects.

[0166] Based on the above embodiments, Figure 8 This is a structural block diagram of a downlink data processing device for a base station provided in an embodiment of this application. (Reference) Figure 8The downlink data processing device for the base station provided in this embodiment specifically includes: a traversal module 21, a setting module 22, an encapsulation module 23, an encoding module 24, a frame header module 25, and a framing module 26.

[0167] The system comprises the following modules: a traversal module 21, configured to acquire target data to be sent and traverse the target data to obtain the corresponding terminal device; a setting module 22, configured to generate a mapping bitmap based on the terminal device and set the bits in the mapping bitmap corresponding to the terminal device; an encapsulation module 23, configured to perform protocol encapsulation on the target data according to the terminal device to generate protocol data units; an encoding module 24, configured to perform forward error correction encoding on the baseband frame payload carrying the protocol data units to generate an encoded bit sequence; a frame header module 25, configured to generate frame header information based on the mapping bitmap, wherein the mapping bitmap is located in the time slice field of the frame header information; and a framing module 26, configured to frame the frame header information and the encoded bit sequence to form downlink data and send the downlink data to the terminal device.

[0168] The downlink data generation apparatus provided in this application embodiment constructs a hierarchical collaborative processing system consisting of a traversal module 21, a setting module 22, an encapsulation module 23, an encoding module 24, a frame header module 25, and a framing module 26. This system enables terminal mapping, protocol encapsulation, encoding and framing, and downlink transmission control of target data, improving the accuracy, completeness, and reliability of downlink data generation in complex communication environments. Specifically, the traversal module 21 possesses target data acquisition and terminal identification capabilities. It acquires the target data to be transmitted and traverses the target data to determine the corresponding terminal device, providing basic information for subsequent mapping. The setting module 22 undertakes the terminal mapping task. By generating a mapping bitmap based on the terminal device and setting the corresponding bit bits of the terminal device in the mapping bitmap, it establishes the correspondence between the target data and the set of terminal devices, providing a positioning basis for encoding and frame header generation. The encapsulation module 23 is responsible for the protocol encapsulation task. It performs protocol encapsulation on the target data according to the terminal device, generating protocol data units that can be used for downlink transmission, achieving standardized processing of upper-layer data into downlink frames. Encoding module 24 performs forward error correction coding, encoding the baseband frame payload carrying protocol data units to generate a coded bit sequence, thereby improving anti-interference capability during downlink transmission. Frame header module 25 is responsible for frame header generation, generating frame header information based on a mapping bitmap, where the mapping bitmap is located in the time slice field of the frame header information, thus binding terminal mapping information with the frame structure. Framing module 26 performs frame assembly and transmission, framing the frame header information and coded bit sequence to form complete downlink data, and sending it to the terminal device, achieving closed-loop control from data generation to transmission. Through data acquisition and terminal identification in the traversal module, mapping generation in the setting module, protocol processing in the encapsulation module, error correction coding in the encoding module, frame header generation in the frame header module, and transmission coordination in the framing module, this device can maintain high-reliability downlink data generation and transmission capabilities under conditions of multiple terminals, multiple services, and fluctuating wireless channels, improving the overall stability and downlink service accuracy of the communication system, and is suitable for multi-terminal scenarios and complex network environments.

[0169] The downlink data processing apparatus for a base station provided in this application embodiment can be used to execute the downlink data processing method for a base station provided in the above embodiment, and has corresponding functions and beneficial effects.

[0170] The downlink data processing apparatus provided in this application embodiment can be used to execute the downlink data processing method provided in the above embodiment, and has corresponding functions and beneficial effects.

[0171] Figure 9 This is a schematic diagram of the structure of a downlink data processing device provided in an embodiment of this application, with reference to... Figure 9The downlink data processing device includes a processor 31, a memory 32, a communication device 33, an input device 34, and an output device 35. The downlink data processing device may have one or more processors 31 and one or more memory units 32. The processor 31, memory 32, communication device 33, input device 34, and output device 35 of the downlink data processing device can be connected via a bus or other means.

[0172] The memory 32, as a computer-readable storage medium, can be used to store software programs, computer-executable programs, and modules, such as program instructions / modules corresponding to the downlink data processing method in any embodiment of this application (e.g., demodulation module 11, mapping module 12, decoding module 13, depackaging module 14, and processing module 15 in the downlink data processing device). The memory 32 may primarily include a program storage area and a data storage area. The program storage area may store the operating system and at least one application program required for a function; the data storage area may store data created based on the use of the device, etc. Furthermore, the memory 32 may include high-speed random access memory and may also include non-volatile memory, such as at least one disk storage device, flash memory device, or other non-volatile solid-state storage device. In some instances, the memory may further include memory remotely located relative to the processor, and these remote memories can be connected to the device via a network. Examples of such networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.

[0173] The communication device 33 is used for data transmission.

[0174] The processor 31 executes various functional applications and data processing of the device by running software programs, instructions and modules stored in the memory 32, thereby realizing the downlink data processing method described above.

[0175] Input device 34 can be used to receive input digital or character information, and to generate key signal inputs related to user settings and function control of the device. Output device 35 may include display devices such as a display screen.

[0176] The downlink data processing device provided above can be used to execute the downlink data processing method provided in the above embodiments, and has corresponding functions and beneficial effects.

[0177] This application embodiment also provides a storage medium containing computer-executable instructions. When executed by a computer processor, the computer-executable instructions are used to perform a downlink data processing method. The downlink data processing method includes: receiving downlink data transmitted by a base station; obtaining a time slice field indicating frame-level service attributes from the frame header information of the downlink data; parsing the time slice field into a mapping bitmap representing a set of terminal devices; performing forward error correction decoding on the downlink data to recover the baseband frame payload of the downlink data when it is determined that the bit corresponding to the terminal device in the mapping bitmap is set; performing protocol decapsulation on the baseband frame payload to obtain a protocol data unit; and performing upper-layer processing on the protocol data unit when it is determined that the protocol data unit corresponds to the terminal device.

[0178] Storage medium—any type of memory device or storage device. The term "storage medium" is intended to include: mounting media, such as CD-ROM, floppy disk, or magnetic tape devices; computer system memory or random access memory, such as DRAM, DDR RAM, SRAM, EDO RAM, etc.; non-volatile memory, such as flash memory, magnetic media (e.g., hard disk or optical storage); registers or other similar types of memory elements, etc. Storage medium may also include other types of memory or combinations thereof. Furthermore, storage medium may reside in a first computer system in which a program is executed, or it may reside in a different second computer system connected to the first computer system via a network (such as the Internet). The second computer system can provide program instructions to the first computer for execution. The term "storage medium" may include two or more storage media residing in different locations (e.g., in different computer systems connected via a network). Storage medium may store program instructions (e.g., specifically implemented as a computer program) executable by one or more processors.

[0179] Of course, the computer-executable instructions provided in the embodiments of this application are not limited to the downlink data processing method described above, but can also perform related operations in the downlink data processing method provided in any embodiment of this application.

[0180] The downlink data processing apparatus, storage medium, and downlink data processing device provided in the above embodiments can execute the downlink data processing method provided in any embodiment of this application. For technical details not described in detail in the above embodiments, please refer to the downlink data processing method provided in any embodiment of this application.

[0181] The above description is merely a preferred embodiment and the technical principles employed in this application. This application is not limited to the specific embodiments described herein, and various obvious changes, readjustments, and substitutions that can be made by those skilled in the art will not depart from the scope of protection of this application. Therefore, although this application has been described in detail through the above embodiments, this application is not limited to the above embodiments, and may include many other equivalent embodiments without departing from the concept of this application. The scope of this application is determined by the scope of the claims.

Claims

1. A downlink data processing method, applied to a terminal device, characterized in that, include: Receive downlink data sent by the base station, and obtain the time slice field used to indicate frame-level service attributes from the frame header information of the downlink data; The time slice field is parsed into a mapping bitmap that represents the set of terminal devices; If it is determined that the bit corresponding to the terminal device in the mapping bitmap is set, forward error correction decoding is performed on the downlink data to recover the baseband frame payload of the downlink data; The baseband frame payload is decapsulated to obtain protocol data units; If it is determined that the protocol data unit corresponds to the terminal device, upper-layer processing is performed on the protocol data unit.

2. The downlink data processing method according to claim 1, characterized in that, The step of obtaining the time slice field indicating frame-level service attributes from the frame header information of the downlink data includes: Demodulate the physical layer frame header of the downlink data to obtain demodulation parameters for physical layer demodulation configuration; The baseband frame header is obtained by demodulating the frame header portion of the downlink data based on the demodulation parameters. Extract the time slice field from the baseband frame header.

3. The downlink data processing method according to claim 1, characterized in that, The step of determining that the bit corresponding to the terminal device in the mapping bitmap is set includes: Obtain the local identifier field of the terminal device; Based on the established mapping relationship between the identifier field and the bit, determine the target bit of the local identifier field in the mapping bitmap; If the state of the target bit is consistent with the set state, it is determined that the target bit is set.

4. The downlink data processing method according to claim 1, characterized in that, The step of determining that the protocol data unit corresponds to the terminal device includes: Parse the header of the protocol data unit to obtain the terminal identification field carried therein, which is used to indicate the receiving terminal; If the terminal identifier field matches the local identifier field of the terminal device, the protocol data unit is determined to correspond to the terminal device.

5. The downlink data processing method according to claim 1, characterized in that, After parsing the time slice field into a mapping bitmap representing a set of terminal devices, the method further includes: If the bit corresponding to the terminal device in the mapping bitmap is not set, the terminal device is controlled to enter a low-power operation state.

6. A downlink data processing method, applied to a base station, characterized in that, include: Obtain the target data to be sent, and iterate through the target data to obtain the corresponding terminal device; A mapping bitmap is generated based on the terminal device, and the bits corresponding to the terminal device in the mapping bitmap are set. The terminal device performs protocol encapsulation on the target data to generate protocol data units; The baseband frame payload carrying the protocol data unit is forward-corrected and encoded to generate an encoded bit sequence; Frame header information is generated based on the mapping bitmap, wherein the mapping bitmap is located in the time slice field of the frame header information; The frame header information and the encoded bit sequence are framed to form downlink data, which is then sent to the terminal device.

7. A downlink data processing device, applied to a terminal device, characterized in that, include: The demodulation module is configured to receive downlink data sent by the base station and obtain the time slice field used to indicate frame-level service attributes from the frame header information of the downlink data. The mapping module is configured to parse the time slice field into a mapping bitmap for representing a set of terminal devices; The decoding module is configured to perform forward error correction decoding on the downlink data to recover the baseband frame payload of the downlink data when it is determined that the bit corresponding to the terminal device in the mapping bitmap is set. The decapsulation module is configured to perform protocol decapsulation on the baseband frame payload to obtain protocol data units; The processing module is configured to perform upper-layer processing on the protocol data unit when it is determined that the protocol data unit corresponds to the terminal device.

8. A downlink data processing apparatus, applied to a base station, characterized in that, include: The traversal module is configured to acquire target data to be sent and traverse the target data to obtain the corresponding terminal device. The bit setting module is configured to generate a mapping bitmap based on the terminal device and set the bit bits in the mapping bitmap corresponding to the terminal device. The encapsulation module is configured to perform protocol encapsulation on the target data according to the terminal device to generate protocol data units; The encoding module is configured to perform forward error correction encoding on the baseband frame payload carrying the protocol data unit to generate an encoded bit sequence; The frame header module is configured to generate frame header information based on the mapping bitmap, wherein the mapping bitmap is located in the time slice field of the frame header information; The framing module is configured to frame the frame header information and the encoded bit sequence to form downlink data, and send the downlink data to the terminal device.

9. A downlink data processing device, characterized in that, include: One or more processors; A memory that stores one or more programs, which, when executed by one or more processors, cause the one or more processors to implement the downlink data processing method as described in any one of claims 1-5.

10. A storage medium containing computer-executable instructions, characterized in that, The computer-executable instructions, when executed by a computer processor, are used to perform the downlink data processing method as described in any one of claims 1-5.

Images