A method and system for fast multi-hop message transmission in a communication network

Abstract

The application discloses a kind of communication network fast multi-hop message transmission method and system, the method obtains destination address index before data is uploaded on user node, and at least one control message in SR, BSR is multiplexed transmission to base station by preset control channel;Base station demodulates index and inquires complete destination address, synchronizes to core network, and core network starts multi-hop protocol negotiation in parallel;Base station uses multi-node shared SR opportunity mechanism, and collision is solved by modulation state distinction node, SR-BSR signaling multiplexing and dynamic backoff;User node generates temporary QoS request code containing transmission speed, reliability, scene adaptation and reserved bit, and base station creates single message temporary QoS context after demodulation and synchronizes to core network, to realize end-to-end multi-hop QoS cooperation;User node uploads data according to temporary QoS parameter and resource authorization increment.The application solves the defects of multi-hop message transmission technology in delay control, resource utilization, QoS flexibility and address transmission efficiency etc.

Description

Technical Field

[0001] This invention relates to the field of communication network technology, and specifically to a method and system for fast multi-hop message transmission in communication networks. Background Technology

[0002] As 5G networks evolve towards wide-area coverage and edge computing integration, and 6G technology develops towards "integrated sensing and terrestrial-space integration," multi-hop message transmission, as a key technology connecting the core network, edge base stations, and terminal nodes, plays an irreplaceable role in scenarios such as emergency communication, autonomous driving vehicle-to-everything (V2X) communication, and mobile IoT. These scenarios place stringent demands on transmission latency, resource utilization, and Quality of Service (QoS) flexibility, while traditional multi-hop message transmission technologies are gradually revealing numerous bottlenecks, making it difficult to adapt to the development needs of next-generation wireless communication networks.

[0003] Regarding multi-hop address acquisition and transmission, according to the 5G core network user plane transmission process defined in the 3GPP TS 23.501 V16.0.0 standard, the traditional solution uses a serial link where data messages carry the destination address, the base station receives and decodes the complete data, and the core network resolves the address and establishes a multi-hop protocol. Since address decoding depends on the reception and demodulation of the complete data message, multi-hop preparation latency accounts for 35% to 45% of the total transmission latency. For scenarios requiring millisecond-level response, such as emergency communications and autonomous vehicle-to-everything (V2X) communication, this latency has become a core obstacle to technology implementation. Even though some improved solutions shorten the transmission path through relay enhancement and edge computing path optimization, they still fail to overcome the core defect of strong address-data coupling. Relay nodes still need to decode data to extract the address and forward it, and the multi-hop preparation latency bottleneck persists.

[0004] Scheduling Request (SR), as the core mechanism of 5G uplink control, faces the dual problems of resource waste and high collision rate. Traditional 5G NR SRs typically use a single-node exclusive allocation method, with approximately 60% of SR resources remaining idle due to a lack of node requests. Even with a random backoff collision solution, the collision rate remains as high as 20% when multiple users make concurrent requests, further extending uplink access latency. Furthermore, the traditional SR mechanism suffers from insufficient signaling multiplexing; SRs are used solely for resource allocation and transmitted independently from other control signaling such as Buffer Status Report (BSR), consuming additional channel resources and time, exacerbating uplink access latency, and severely contradicting the goals of low latency and high resource utilization.

[0005] Regarding dynamic QoS adjustment, traditional solutions require modifying user default parameters through Radio Resource Control (RRC) reconfiguration, resulting in a latency exceeding 100ms for the entire process. This makes them unsuitable for dynamic scenarios where a single urgent message needs high-priority transmission while regular messages maintain their default QoS. Furthermore, the adjusted QoS parameters apply to all subsequent data messages, exhibiting strong adaptability. If only a single urgent message needs priority enhancement, RRC reconfiguration must be initiated again after transmission to restore the default parameters, making the process cumbersome and adding further latency. More importantly, traditional QoS adjustment only focuses on resource allocation for single-hop links, failing to cover end-to-end QoS guarantees for multi-hop transmissions. The core network and relay nodes cannot synchronously acquire temporary QoS requirements, potentially causing delays in high-priority messages during multi-hop transmissions due to resource preemption.

[0006] In terms of address transmission efficiency, traditional 5G uses 48-bit MAC addresses or 32-bit IP addresses to identify terminals. Under 256QAM modulation, transmitting a complete address requires 6 symbols, accounting for 15% to 20% of the total short message bandwidth, resulting in a serious waste of bandwidth resources. Although some studies have proposed static address indexing schemes to reduce bandwidth consumption by replacing complete addresses with short indexes, the index-address mapping relationship of this scheme needs to be pre-configured and fixed, which cannot adapt to the dynamic changes in communication objects in scenarios such as vehicle-to-everything (V2X) and mobile IoT. Furthermore, it does not solve the latency problem of waiting for data message decoding to obtain the address in multi-hop scenarios, and still cannot support fast multi-hop transmission. In addition, although the application of AI in 5G resource allocation has been widely carried out, existing AI models mostly focus on single-hop resource scheduling, and it is difficult to achieve optimal global performance in multi-hop scenarios for specific optimization of multi-hop message transmission. Summary of the Invention

[0007] Therefore, this invention provides a fast multi-hop message transmission method and system for communication networks, which solves the defects of existing multi-hop message transmission technologies in terms of latency control, resource utilization, QoS flexibility and address transmission efficiency.

[0008] To achieve the above objectives, the present invention provides the following technical solution: a method for fast multi-hop message transmission in a communication network, comprising the following steps:

[0009] (1) Construct a two-level distributed dynamic address index database consisting of a local base station database and a global core network database, and establish and maintain an index-address mapping relationship through the dynamic address index database;

[0010] (2) Before the user node uploads the complete data message, the index corresponding to the destination address is obtained based on the dynamic address index database, and at least one of the control messages, namely the index corresponding to the destination address, the scheduling request, and the cache status report, is multiplexed and transmitted to the base station through a preset control channel;

[0011] (3) After receiving the multiplexing message, the base station demodulates and extracts the index and obtains the complete destination address through the dynamic address index database. It then transmits the destination address and data size information to the core network in parallel. The core network then initiates multi-hop protocol negotiation with the receiving base station and relay node in parallel.

[0012] (4) The base station adopts a multi-node shared SR opportunity mechanism, assigns a unique modulation state to user nodes that share the same SR opportunity, carries dual information through SR-BSR signaling multiplexing technology, and implements a dynamic backoff collision resolution mechanism based on the unique identifier of the user node and the system clock.

[0013] (5) The user node generates a temporary QoS request code in a preset format. The request code is divided into transmission speed adjustment bits, transmission reliability adjustment bits, scenario adaptation bits and reserved bits according to function. It is transmitted to the base station through the control channel. The base station demodulates the code and creates a temporary QoS context for a single data message.

[0014] (6) The base station synchronizes the temporary QoS context parameters to the core network. The core network embeds the temporary QoS context parameters in the multi-hop protocol negotiation and synchronizes them to the relay node and the receiving base station to achieve end-to-end multi-hop QoS coordination.

[0015] (7) User nodes upload data incrementally through preset data channels according to temporary QoS context parameters and resource authorization issued by the base station. After receiving the data block, the base station forwards it to the core network. The core network completes the data transmission through the established multi-hop link. After the transmission is completed, the temporary QoS context is cleared and the default configuration is restored.

[0016] As a preferred scheme for fast multi-hop message transmission in communication networks, in step (1), the dynamic address index database supports an automatic index allocation mechanism, an invalid cleanup mechanism, and a multi-level synchronization mechanism;

[0017] The multi-level synchronization mechanism divides the synchronization range and period according to the level. User nodes and base stations perform periodic synchronization of high-frequency address mapping, base stations and core network perform periodic synchronization of low-frequency and cross-base station address mapping, and core network and all base stations in the network perform periodic synchronization of cross-cell high-frequency address mapping. The invalid cleanup mechanism performs automatic cleanup of indexes that have not been used for a set period of time, and sets protection strategies for emergency address indexes and important address indexes manually marked by users.

[0018] As a preferred scheme for the fast multi-hop message transmission method in communication networks, in step (2), the preset control channel includes the PUCCH channel, the PUSCH channel and the RACH channel;

[0019] The PUCCH channel is adapted for low-latency scenarios, multiplexing the index and SR request into a single modulation symbol for transmission; the PUSCH channel is adapted for large message transmission scenarios, seamlessly concatenating the index and BSR message before transmission; the RACH channel is adapted for emergency communication scenarios, combining the index, BSR message, and SR request for asynchronous transmission.

[0020] As a preferred scheme for fast multi-hop message transmission in communication networks, in step (3), after the base station receives the multiplexed message, it demodulates and extracts the index and obtains the complete destination address by querying the dynamic address index database:

[0021] After receiving the index, the base station first queries the high-frequency address mapping stored in the local database to obtain the complete address;

[0022] If no matching mapping is found in the local database, a query is initiated to the core network global database through the interface. The core network global database covers low-frequency and cross-base station address mappings across the entire network. After the query result is fed back to the base station, the base station caches the query result in the local database.

[0023] If the index is invalid or the query returns no results, switch to full address transfer mode.

[0024] As a preferred scheme for the fast multi-hop message transmission method in communication networks, in step (4), the unique modulation state is realized based on the amplitude-phase combination difference of the modulation method. The amplitude-phase combination allocated to different user nodes is uniquely distinguishable in the modulation constellation diagram. The base station identifies the corresponding request node by the amplitude and phase characteristics of the demodulated symbol.

[0025] The SR-BSR signaling multiplexing technology carries both data size quantization information and resource request related identifiers through a single modulation symbol;

[0026] The dynamic backoff collision resolution mechanism calculates differentiated backoff delays using a portion of the user node's unique identifier and a portion of the system clock's timing information, ensuring that the retransmission times of colliding nodes do not overlap. After detecting a collision, the base station sends a collision notification to the relevant user node through a designated channel. Upon receiving the notification, the node initiates the backoff and retransmission process, using reserved resource blocks during retransmission.

[0027] As a preferred scheme for fast multi-hop message transmission in communication networks, in step (5), the temporary QoS request code of the preset format is a fixed-length binary code, the transmission speed adjustment bit supports multi-level speed adjustment options, corresponding to the delay optimization requirements of multi-hop transmission; the transmission reliability adjustment bit supports multi-level reliability adjustment options, corresponding to the retransmission strategy configuration of multi-hop links; the scenario adaptation bit covers predefined scenarios and user-defined scenarios, and each predefined scenario corresponds to a default QoS parameter combination;

[0028] In step (5), the transmission format of the temporary QoS request code is adapted to the control message type and scenario requirements. When quickly requesting resources, it is multiplexed with the SR request and transmitted to the PUCCH channel; when reporting the cache status, it is concatenated with the BSR message and transmitted to the PUSCH channel; in emergency scenarios where there is no need to wait for resource request opportunities, it is combined with the address index, BSR message and SR request and transmitted asynchronously to the RACH channel.

[0029] As a preferred method for fast multi-hop message transmission in communication networks, in step (6), the end-to-end multi-hop QoS coordination is achieved through hierarchical signaling synchronization:

[0030] The base station synchronizes temporary QoS parameters to the core network through the control plane interface, and the synchronization signaling is transmitted with high priority to shorten the synchronization delay.

[0031] During the multi-hop protocol negotiation process between the core network and relay nodes and receiving base stations, QoS parameters are embedded in the multi-hop control signaling; relay nodes adjust the forwarding queue priority based on QoS parameters, giving priority to forwarding high QoS data messages; receiving base stations reserve downlink channel resources; the core network monitors the QoS execution status of nodes in real time and triggers resynchronization when an anomaly is detected.

[0032] As a preferred solution for fast multi-hop message transmission in communication networks, the dynamic address index database ensures the security of index transmission through encryption technology. A check code is generated during the index allocation process. When the user node transmits the index, it carries the check code. After receiving and verifying the check code, the base station performs an address demapping operation.

[0033] The index length, transmission format, and synchronization signaling of the dynamic address index database are all compatible with the set network protocol specifications.

[0034] As a preferred method for fast multi-hop message transmission in communication networks, the base station monitors the transmission quality indicators of SR opportunities in real time, including collision rate and resource idle rate: if the collision rate continues to be higher than the set value, the number of shared user nodes is increased by adjusting the modulation method to distribute the transmission pressure;

[0035] If the resource idle rate is higher than the set value, adjacent resource sharing groups are merged to reduce the number of idle resource blocks. When a user node joins or leaves the sharing group, the base station updates the modulation state allocation list in real time and synchronizes it to all user nodes in the group to ensure the uniqueness of the modulation state.

[0036] This invention also provides a fast multi-hop message transmission system for communication networks, employing the aforementioned fast multi-hop message transmission method for communication networks, comprising:

[0037] The dynamic address index database module is used to construct a two-level distributed dynamic address index database consisting of a base station local database and a core network global database, and to establish and maintain an index-address mapping relationship through the dynamic address index database.

[0038] The multiplexing message generation and transmission module is used to obtain the index corresponding to the destination address based on the dynamic address index database before the user node uploads the complete data message, and to multiplex and transmit at least one of the control messages, including the index corresponding to the destination address, the scheduling request, and the cache status report, to the base station through a preset control channel.

[0039] The base station receiving and multi-hop negotiation triggering module is used to demodulate and extract the index after the base station receives the multiplexing message, and obtain the complete destination address by querying the dynamic address index database. The destination address and data size information are transmitted to the core network in parallel. The core network initiates multi-hop protocol negotiation with the receiving base station and relay node in parallel.

[0040] The SR mechanism optimization module is used by the base station to adopt a multi-node shared SR opportunity mechanism, assign a unique modulation state to user nodes sharing the same SR opportunity, carry dual information through SR-BSR signaling multiplexing technology, and implement a dynamic backoff collision resolution mechanism based on the unique identifier of the user node and the system clock.

[0041] The temporary QoS request processing module is used by user nodes to generate temporary QoS request codes in a preset format. The request codes are divided into transmission speed adjustment bits, transmission reliability adjustment bits, scenario adaptation bits and reserved bits according to their functions. They are transmitted to the base station through the control channel. After demodulation, the base station creates a temporary QoS context for a single data message.

[0042] An end-to-end multi-hop QoS coordination module is used by the base station to synchronize temporary QoS context parameters to the core network. The core network embeds the temporary QoS context parameters in the multi-hop protocol negotiation and synchronizes them to the relay node and the receiving base station to achieve end-to-end multi-hop QoS coordination.

[0043] The data transmission and resource reclamation module is used by user nodes to incrementally upload data through a preset data channel according to temporary QoS context parameters and resource authorization issued by the base station. After receiving the data block, the base station forwards it to the core network. The core network completes the data transmission through the established multi-hop link. After the transmission is completed, the temporary QoS context is cleared and the default configuration is restored.

[0044] The present invention has the following advantages:

[0045] First, through an innovative design that decouples destination address and data in parallel, the bottleneck of traditional serial transmission is broken, allowing multi-hop protocol negotiation and data uploading to occur simultaneously. This significantly reduces multi-hop preparation latency, fully meeting the rigid requirements for low latency in scenarios such as emergency communication and vehicle-to-everything (V2X) communication, and enabling rapid response in multi-hop transmission. Simultaneously, uplink access latency and QoS adjustment latency are also effectively controlled, and the address demapping process is highly efficient and fast, completely eliminating the latency constraints of traditional processes.

[0046] Secondly, the shared SR opportunity mechanism among multiple nodes significantly reduces channel resource idleness. Combined with signaling multiplexing technology, it reduces unnecessary transmissions and lowers network transmission overhead. The design of replacing long addresses with short indices effectively reduces bandwidth consumption for address transmission, optimizes overall resource allocation efficiency, and allows for more efficient utilization of limited network resources.

[0047] Third, by leveraging temporary QoS retransmission strategy adjustments, anti-interference modulation techniques, and dynamic backoff collision resolution mechanisms, the risk of data packet loss and transmission failure is significantly reduced, improving the reliability of message transmission. The automatic allocation, cleanup, and synchronization mechanism of dynamic address indexes enhances the technical solution's ability to withstand dynamic scene fluctuations, effectively adapting to complex scenarios in vehicle-to-everything (V2X) networks such as the movement of communication objects and frequent access by IoT nodes, ensuring the stability of the transmission process.

[0048] Fourth, the system designs multiple address pre-transmission paths, various QoS scenario templates, and multiple channel transmission options to comprehensively cover core 5G / 6G application scenarios such as regular low latency, large message transmission, emergency communication, and cross-cell communication. It enables dynamic QoS adjustment at the message level without modifying default configurations and automatically recovers after transmission, perfectly adapting to mixed service requirements of sudden high-priority messages and regular messages, thus enhancing the flexibility and adaptability of the technical solution.

[0049] Fifth, all technical designs strictly adhere to the 5G NR protocol specifications, requiring no modification to the existing network architecture. They can seamlessly switch with traditional address transmission and QoS scheduling methods, significantly reducing the cost of technology deployment. The two-tiered distributed storage design of the base station local library and the core network global library, coupled with a robust synchronization fault-tolerance mechanism, ensures stable operation of the technology in real-world networks. Its disaster recovery and scalability fully meet the needs of large-scale deployment. Attached Figure Description

[0050] To more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings in the following description are merely exemplary, and those skilled in the art can derive other embodiments based on the provided drawings without creative effort.

[0051] The structures, proportions, sizes, etc. illustrated in this specification are only for the purpose of assisting those skilled in the art in understanding and reading the content disclosed herein, and are not intended to limit the conditions under which the present invention can be implemented. Therefore, they have no substantial technical significance. Any modifications to the structure, changes in the proportions, or adjustments to the size, without affecting the effects and objectives that the present invention can produce, should still fall within the scope of the technical content disclosed in the present invention.

[0052] Figure 1 This is a schematic diagram of the fast multi-hop message transmission method for communication networks provided in an embodiment of the present invention;

[0053] Figure 2 This is a flowchart of the address index dynamic update process in the fast multi-hop message transmission method for communication networks provided in this embodiment of the invention.

[0054] Figure 3 This is a schematic diagram of SR-BSR multiplexing and dynamic backoff in the fast multi-hop message transmission method for communication networks provided in this embodiment of the invention;

[0055] Figure 4 This is a schematic diagram of a fast multi-hop message transmission system architecture for a communication network provided in an embodiment of the present invention. Detailed Implementation

[0056] The following specific embodiments illustrate the implementation of the present invention. Those skilled in the art can easily understand other advantages and effects of the present invention from the content disclosed in this specification. Obviously, the described embodiments are only some, not all, of the embodiments of the present invention. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0057] The meanings of the English abbreviations used in this invention are as follows:

[0058] 5G: Fifth-Generation Mobile Communication Technology

[0059] 6G: Sixth-Generation Mobile Communication Technology

[0060] 3GPP: 3rd Generation Partnership Project

[0061] TS: Technical Specification

[0062] SR: Scheduling Request

[0063] BSR: Buffer Status Report

[0064] QoS: Quality of Service

[0065] RRC: Radio Resource Control

[0066] MAC: Media Access Control

[0067] IP: Internet Protocol

[0068] PUCCH: Physical Uplink Control Channel

[0069] PUSCH: Physical Uplink Shared Channel

[0070] RACH: Random Access Channel

[0071] PDCCH: Physical Downlink Control Channel

[0072] PDSCH: Physical Downlink Shared Channel

[0073] DCI: Downlink Control Information

[0074] HARQ: Hybrid Automatic Repeat Request

[0075] uRLLC: Ultra-Reliable and Low-Latency Communication

[0076] mMTC: Massive Machine-Type Communication

[0077] D2D: Device-to-Device communication

[0078] ZFR / ZFT: Zero-Forcing Receive / Transmit Precoding

[0079] C-RNTI: Cell Radio Network Temporary Identifier

[0080] S1-MME: S1 Interface Mobility Management Entity

[0081] N2: Core Network-Base Station Control Plane Interface

[0082] X2: Inter-Base Station Interface

[0083] UE ID: User Equipment Identifier

[0084] SUPI: Subscription Permanent Identifier

[0085] SUCI: Subscription Concealed Identifier

[0086] III. Modulation and Coding

[0087] QPSK: Quadrature Phase Shift Keying

[0088] 16QAM: 16-Quadrature Amplitude Modulation

[0089] 256QAM: 256-Quadrature Amplitude Modulation

[0090] AES-128: Advanced Encryption Standard-128

[0091] LZ77: LZ77 Data Compression Algorithm

[0092] Gr-BSR: Buffer Status Report Grant

[0093] Gr-DAT: Data Transmission Grant

[0094] 6LoWPAN: IPv6 over Low-Power Wireless Personal Area Networks

[0095] HFSC: Hierarchical Fair Service Curve

[0096] SD-WAN: Software-Defined Wide Area Network

[0097] Example 1

[0098] See Figure 1 This invention provides a method for fast multi-hop message transmission in a communication network, comprising the following steps:

[0099] S1. Construct a two-level distributed dynamic address index database consisting of a base station local database and a core network global database. Establish and maintain the index-address mapping relationship through this dynamic address index database. The base station local database is deployed on an edge storage module, focusing on high-frequency address storage to ensure low-latency queries. The core network global database adopts a distributed cluster deployment, covering low-frequency addresses across the entire network and cross-base station addresses to ensure wide-area communication needs. The establishment of the index-address mapping relationship is based on the logic of replacing long addresses with short indexes. The index length adapts to different modulation methods, reducing bandwidth consumption for address transmission and adapting to dynamic communication scenarios through an automated management mechanism.

[0100] S2. Before the user node uploads the complete data message, the index corresponding to the destination address is obtained based on the dynamic address index database. At least one control message, including the index corresponding to the destination address, a scheduling request, and a cache status report, is multiplexed and transmitted to the base station via a preset control channel. By multiplexing the control channel, address-related information is transmitted in advance before data upload, enabling the core network to synchronously initiate multi-hop protocol negotiation, significantly reducing multi-hop preparation delay. The design adapts to different control channels based on their transmission characteristics: the PUCCH channel has low transmission latency, adapting to conventional low-latency requirements; the PUSCH channel has sufficient bandwidth, adapting to large message transmission; and the RACH channel supports asynchronous transmission, eliminating the need to wait for resource opportunities, adapting to the rapid triggering requirements of emergency scenarios.

[0101] S3. After receiving the multiplexing message, the base station demodulates and extracts the index, then queries the dynamic address index database to obtain the complete destination address. Simultaneously, it transmits the destination address and data size information to the core network. The core network then initiates multi-hop protocol negotiation with the receiving base station and relay nodes in parallel. The base station prioritizes querying its local high-frequency address database to quickly obtain the address and trigger multi-hop negotiation, avoiding delays caused by cross-network queries. A global database query serves as a fallback to ensure normal resolution of low-frequency and cross-base station addresses, while a query result caching design optimizes the efficiency of subsequent queries for similar addresses. After receiving the address information, the core network initiates multi-hop protocol negotiation in parallel, including key steps such as routing planning and bandwidth reservation, ensuring that multi-hop preparation and data upload are synchronized, fundamentally shortening end-to-end transmission latency.

[0102] S4. The base station adopts a multi-node shared SR opportunity mechanism, assigning a unique modulation state to user nodes sharing the same SR opportunity. SR-BSR signaling multiplexing technology carries dual information, and a dynamic backoff collision resolution mechanism is implemented based on the unique identifier of the user node and the system clock. Multi-node shared SR opportunities are achieved through modulation state differentiation. Utilizing the uniqueness of the amplitude-phase combination of the modulation scheme, multiple nodes can transmit in parallel within the same time-frequency resource block, significantly improving PUCCH channel resource utilization. SR-BSR signaling multiplexing carries dual information through a single modulation symbol, reducing the number of signaling transmissions and latency. The dynamic backoff mechanism calculates differentiated delays based on the unique identifier of the node and the system clock, avoiding repeated collisions between colliding nodes. Combined with collision notification and reserved resource retransmission design, it further improves collision resolution efficiency.

[0103] S5. The user node generates a temporary QoS request code in a preset format. This request code is functionally divided into transmission speed adjustment bits, transmission reliability adjustment bits, scenario adaptation bits, and reserved bits. It is transmitted to the base station via the control channel. After demodulation, the base station creates a temporary QoS context for a single data message. Fixed-length binary encoding ensures efficient and unified QoS request parsing. Each functional bit corresponds to transmission speed, reliability, and scenario requirements, covering multi-dimensional adjustment needs. Reserved bits ensure the scalability of the technology. The temporary QoS context design ensures that adjustments only apply to a single data message, without requiring modification of the default configuration. It automatically recovers after transmission, adapting to mixed service scenarios of sudden high-priority messages and regular messages. Multi-channel transmission adapts to different triggering times, ensuring that QoS requests are delivered to the base station quickly and reliably.

[0104] S6. The base station synchronizes the temporary QoS context parameters to the core network. The core network embeds the temporary QoS context parameters in the multi-hop protocol negotiation and synchronizes them to the relay nodes and receiving base stations to achieve end-to-end multi-hop QoS coordination. The base station synchronizes the QoS parameters to the core network through high-priority signaling, shortening the synchronization delay. The core network embeds the QoS parameters in the multi-hop protocol negotiation, ensuring that all multi-hop nodes, including relay nodes and receiving base stations, clearly understand the processing requirements. Relay nodes adjust the forwarding queue priority, and receiving base stations reserve dedicated resources to form a full-link priority guarantee. The core network monitors the execution status in real time and handles anomalies to ensure that the QoS parameters are effectively implemented during the multi-hop process.

[0105] S7. User nodes incrementally upload data through a preset data channel according to temporary QoS context parameters and resource authorization issued by the base station. After receiving the data blocks, the base station forwards them to the core network. The core network completes data transmission through established multi-hop links. After transmission is complete, the temporary QoS context is cleared and the default configuration is restored. Incremental upload splits data into multiple data blocks for batch transmission. The base station forwards the data immediately after receiving it, and the core network transmits it synchronously through established multi-hop links. The receiver does not need to wait for complete data to start receiving, significantly reducing the total end-to-end latency. After transmission is complete, the temporary QoS context is cleared, temporarily occupied resources are released, and the default configuration is restored to avoid affecting subsequent message transmission and ensure the stability and balance of network services.

[0106] In this embodiment, in step S1, the dynamic address index database supports an automatic index allocation mechanism, an invalid cleanup mechanism, and a multi-level synchronization mechanism. The multi-level synchronization mechanism divides the synchronization range and period according to the level. User nodes and base stations perform periodic synchronization of high-frequency address mappings, base stations and the core network perform periodic synchronization of low-frequency and cross-base station address mappings, and the core network and all base stations in the network perform periodic synchronization of cross-cell high-frequency address mappings. The invalid cleanup mechanism performs automatic cleanup of indexes that have not been used for a set period of time and sets protection strategies for emergency address indexes and important address indexes manually marked by users.

[0107] Specifically, the automatic index allocation mechanism works by dynamically adapting to changes in communication objects. When a user node receives or sends a new address, the base station automatically assigns a unique index to that address and synchronizes it to the user node and related databases, eliminating the need for manual configuration and adapting to dynamic communication scenarios such as vehicle-to-everything (V2X) and mobile IoT. The multi-level synchronization mechanism is designed based on layered synchronization and precise adaptation. High-frequency address mapping is synchronized between user nodes and base stations to ensure local communication efficiency. Low-frequency and cross-base station address mapping is synchronized between base stations and the core network, balancing coverage and synchronization overhead. Network-wide synchronization of high-frequency address mapping across cells improves the address demapping efficiency for cross-regional communication. The core of the invalid cleanup mechanism is resource optimization. By cleaning up long-term unused indexes, storage resources are released, while protection strategies are set for urgent and important addresses to prevent critical communications from being affected by accidental cleanup.

[0108] See Figure 2 When a user node receives / sends a new address (such as "00:1B:44:11:3A:B7"), the process is as follows:

[0109] The base station detects that the address is not in its local database ("Is the address in the base station's local database?" → "No"), and automatically assigns a unique index (such as index 6).

[0110] The base station stores the mapping of "index 6 → new address" in its local database and synchronizes it with the user node through the PUCCH channel;

[0111] User nodes update their local index list and store the mapping. Subsequent communication can directly use index 6 to replace the full address, significantly reducing bandwidth consumption (from 30% of the traditional address to 5%).

[0112] The invalid address cleanup process targets existing addresses; the base station periodically checks their usage status.

[0113] Base station query address recent usage time ("Has it not been used for 30 days?");

[0114] If an address is not used for more than 30 days, mark it as "invalid" and remove its index mapping from the local library.

[0115] At the same time, the "index invalidation" information is synchronized to user nodes to release index resources (e.g., there are only 256 8-bit indexes) and avoid invalid addresses occupying limited index space.

[0116] The periodic synchronization process triggers an index mapping verification between the base station and user nodes every 24 hours.

[0117] The base station sends an "index-address" verification packet to the user node. The user node compares its local list with the verification packet. If there is an inconsistency ("Is there a difference?"), it completes the missing mapping (such as the base station adding "index 7 → 00:1C:55:22:4B:C8"); it deletes invalid mappings locally. If the mappings are completely consistent, the synchronization is completed, ensuring the consistency of the index-address mapping between the two parties and avoiding multi-hop transmission failures due to mismatch.

[0118] In this embodiment, in step S2, the preset control channel includes a PUCCH channel, a PUSCH channel, and a RACH channel; the PUCCH channel is adapted to low-latency scenarios, multiplexing the index and SR request into a single modulation symbol for transmission; the PUSCH channel is adapted to large message transmission scenarios, seamlessly splicing the index and BSR message before transmission; the RACH channel is adapted to emergency communication scenarios, combining the index with the BSR message and SR request for asynchronous transmission.

[0119] Specifically, the PUCCH channel, as an uplink control channel, inherently features low transmission latency and low resource overhead. Multiplexing the index and SR request into a single modulation symbol allows for rapid transmission of critical information without increasing additional channel resources, making it suitable for low-latency scenarios such as ordinary data transmission. The PUSCH channel, as an uplink shared channel, has ample bandwidth resources and can carry large-size data. Seamlessly splicing the index and BSR messages for transmission reduces the number of signaling transmissions, avoiding delays caused by multiple signaling interactions in large message transmissions, making it suitable for high-volume transmission scenarios such as high-definition video and industrial big data. The RACH channel supports asynchronous transmission, eliminating the need to wait for SR opportunities allocated by the base station. It combines the index, BSR message, and SR request and transmits them immediately. Furthermore, the time correlation of each message field ensures accurate identification of the corresponding relationship by the base station, making it suitable for emergency communication scenarios requiring millisecond-level response, such as fire warnings and medical emergencies.

[0120] Specifically, the implementation process of the PUCCH+SR path (in typical low-latency scenarios) is as follows:

[0121] After a user node detects that ordinary service data is waiting to be transmitted, it first queries its local "index-address" list, converting the destination address into a short index adapted to the corresponding modulation scheme. The index length is flexibly selected according to the modulation scheme to cover the needs of commonly used communication objects. Then, it waits for the SR opportunity window pre-allocated by the base station and transmits a multiplexed symbol containing an SR request identifier and an address index via the PUCCH channel. The SR request identifier informs the base station of its resource requirements. Upon receiving the signal, the base station demodulates it based on the corresponding modulation scheme, quickly extracts the SR request and address index, retrieves the complete MAC address through its local "user-specific address index database," and then issues a Gr-BSR authorization via the PDCCH channel. After receiving the authorization, the user node transmits a BSR message on the PUSCH channel, informing the base station of the data buffer size. After parsing the BSR message, the base station synchronizes the complete MAC address and data size to the core network via the S1-MME interface. The core network immediately initiates multi-hop protocol negotiation, including route planning and bandwidth reservation. Once the core network reports that the multi-hop link is ready, the base station issues Gr-DAT authorization, and the user node uploads data in incremental mode on the PUSCH channel. The base station simultaneously forwards the received data blocks to the core network, enabling multi-hop transmission and data upload to proceed in parallel.

[0122] The implementation process of the PUSCH+BSR path (large message transmission scenario) is as follows:

[0123] When a user node has high-volume data to transmit, such as high-definition video or industrial big data, it first triggers a Service Request (SR) request. Within the SR opportunity window pre-allocated by the base station, a pure SR request is sent via the PUCCH channel (address information is not carried due to limited PUCCH channel bandwidth). Upon receiving the request, the base station issues a Gr-BSR authorization via the PDCCH channel, specifying the PUSCH transmission resources and modulation scheme for the BSR message. Based on this authorization, the user node seamlessly concatenates the address index or complete MAC address (if the new address has no corresponding index) with the BSR message and transmits it via the PUSCH channel. This concatenation design reduces the number of signaling transmissions. After demodulating the PUSCH symbols, the base station separates the BSR message from the address information. If it is an index, it queries the local database to obtain the complete MAC address; if it is a complete address, it stores it directly and synchronizes it to the core network. The core network, considering the large message size resolved by the BSR, plans multi-hop paths and reserves sufficient bandwidth to complete multi-hop protocol negotiation. The base station then issues Gr-DAT authorization to the user node. The user node splits the large message into transport blocks and uploads them incrementally through the PUSCH channel. The base station forwards each data block it receives to the core network. The core network transmits the data synchronously through multi-hop links to ensure that the transmission of large messages is unblocked.

[0124] The implementation process of RACH asynchronous path (emergency communication scenario) is as follows:

[0125] Upon detecting emergency data such as fire warnings or medical emergency commands, user nodes can initiate asynchronous transmission directly without waiting for SR (Request for Response) opportunities. The address index, BSR message, and SR request identifier are combined into a unified message, using a modulation scheme with stronger anti-interference capabilities, and asynchronously transmitted via the RACH channel. The different parts of the message maintain reasonable time intervals to ensure the base station can accurately identify the correlation. The base station monitors the RACH channel in real time, prioritizes parsing the received combined message, quickly extracts the address index, queries the database to obtain the complete MAC address, and simultaneously parses the BSR to obtain the emergency data size. The base station immediately synchronizes "emergency identifier + MAC address + data size" to the core network via the S1-MME interface. The core network triggers a multi-hop negotiation expedited process, prioritizing the planning of low-latency multi-hop paths, skipping unnecessary verification steps, and notifying relay nodes and the receiving base station to initiate emergency priority processing. The base station does not need to wait for multi-hop negotiation to be fully ready and quickly issues Gr-DAT authorization. User nodes prioritize uploading emergency data on the PUSCH channel. After receiving the data, the relay node skips the low-priority message queue and forwards it immediately. The receiving base station allocates dedicated PDSCH resources for data download, ensuring end-to-end low-latency transmission of emergency data throughout the process and avoiding the waiting delays in the traditional process.

[0126] By employing three differentiated paths—PUCCH+SR, PUSCH+BSR, and RACH asynchronous—a dynamic balance between latency, bandwidth, reliability, and resource utilization is achieved. The PUCCH+SR path, designed for typical low-latency scenarios, uses short indexes to multiplex modulation symbols, significantly saving channel resources while meeting the low-latency requirements of ordinary data transmission, thus balancing practicality and efficiency. The PUSCH+BSR path, geared towards large message transmission scenarios, leverages high-bandwidth modulation to support flexible switching between indexes and full addresses, adapting to the reliability requirements of high-volume transmissions while reducing the number of signaling transmissions. The RACH asynchronous path, focused on emergency communication scenarios, uses highly interference-resistant modulation, possessing extremely short multi-hop preparation delays, fully meeting millisecond-level response requirements, and eliminating the need to wait for SR opportunities, further compressing trigger latency. All three paths strictly adhere to the modulation scheme and channel characteristics of the 5G NR standard, without occupying additional frequency resources. Through the address carrier design of "index priority and complete address fallback", the modulation adaptation logic of "low-order modulation to ensure reliability and high-order modulation to improve efficiency", and the channel selection strategy of "control channel to adapt to low latency, shared channel to adapt to high traffic, and asynchronous channel to adapt to emergency scenarios", they fully cover the core application scenarios of 5G / 6G multi-hop transmission. The overall performance far exceeds that of traditional single address transmission methods, fully demonstrating the scenario-based, flexible and efficient nature of the technology design.

[0127] In this embodiment, in step S3, after the base station receives the multiplexing message, it demodulates and extracts the index and obtains the complete destination address by querying the dynamic address index database: After receiving the index, the base station first queries the high-frequency address mapping stored in the local database to obtain the complete address; if no matching mapping is found in the local database, it initiates a query to the core network global database through the interface. The core network global database covers low-frequency and cross-base station address mappings across the entire network. After the query result is fed back to the base station, the base station caches the query result in the local database; if the index is invalid or the query yields no results, it switches to the complete address transmission mode.

[0128] Specifically, the principle of prioritizing local database queries is "nearest range first, reduced latency." The base station's local database stores frequently accessed address mappings, resulting in extremely low query latency. This allows for rapid retrieval of complete addresses and triggers multi-hop negotiation. When the local database fails to find the address, the core network's global database is queried. Based on the design logic of "global coverage, ensuring connectivity," the core network's global database integrates low-frequency and cross-base station address mappings across the entire network, ensuring that addresses for cross-regional, low-frequency communication can be resolved normally. Caches the query results in the local database to optimize the efficiency of subsequent queries for similar addresses and avoid repeated cross-network queries. Switching to full address transmission mode when the index is invalid or the query returns no results is a design that ensures compatibility and business continuity. When the index becomes invalid due to cleanup, errors, or other reasons, transmitting the complete address avoids communication interruption, ensuring the compatibility and reliability of the technical solution.

[0129] After receiving the index, the base station first queries the local database (prioritizing high-frequency addresses), quickly matching the "UE ID and index" to obtain the complete address within 0.1-0.2ms. If the local database does not find the address (low-frequency address), the base station initiates a query to the core network's global database via the S1 interface. The core network returns the complete address within 1ms, and the base station caches it in the local database (marked as "temporary high-frequency"). If the index is invalid (e.g., it has been cleared) or the query yields no results, the base station reports "index invalid" via the PDCCH channel and requests the user node to transmit the complete address. The user node switches to "complete address transmission mode" to ensure communication continuity. After the base station demaps and obtains the complete address, it synchronizes it to the core network via the S1-MME interface. The core network plans multi-hop paths based on address type: for high-frequency addresses (local communication), a short path of "base station, receiver base station" is planned; for low-frequency addresses (inter-cell communication), a long path of "base station, relay node, receiver base station" is planned. The index is transmitted in advance to ensure that path planning and data uploading are carried out in parallel.

[0130] In this embodiment, in step S4, the unique modulation state is achieved based on the amplitude-phase combination difference of the modulation scheme. The amplitude-phase combination allocated to different user nodes is uniquely distinguishable in the modulation constellation diagram. The base station identifies the corresponding requesting node through the amplitude and phase characteristics of the demodulated symbol. The SR-BSR signaling multiplexing technology carries data size quantization information and resource request related identifiers simultaneously through a single modulation symbol. The dynamic backoff collision resolution mechanism calculates differentiated backoff delays through a portion of the unique identifier of the user node and a portion of the timing information of the system clock, so that the retransmission times of colliding nodes do not overlap. After the base station detects a collision, it sends a collision notification to the relevant user node through a designated channel. After receiving the notification, the node initiates the backoff and retransmission process, and the reserved resource block is used during retransmission.

[0131] Specifically, based on the unique modulation state design of amplitude-phase combination, the diversity of amplitude and phase combinations of modulation methods such as 16QAM and 256QAM is used to assign a unique combination to each node sharing SR opportunity. The base station can accurately identify the requesting node by the amplitude and phase characteristics of the demodulated symbol, thereby reducing the probability of collision from the root. The SR-BSR signaling multiplexing technology carries two types of key information simultaneously through a single modulation symbol, avoiding channel resource occupation and delay accumulation caused by independent transmission of SR requests and BSR messages, thus improving uplink access efficiency. The core of the dynamic backoff collision resolution mechanism is "differentiated delay and avoidance of repeated collisions". Some fields of the unique identifier of the user node are random, and some timing information of the system clock changes dynamically with time. The combination of the two can generate significantly different backoff delays, ensuring that the retransmission time of the colliding nodes does not overlap. The collision notification and reserved resource block retransmission design can quickly trigger the backoff process, and the retransmission does not occupy normal transmission resources, further reducing the impact on overall transmission performance.

[0132] See Figure 3The core of multi-node shared SR opportunities is to enable multiple user nodes to transmit SR requests containing SR-BSR multiplexing information in parallel within the same time-frequency resource block through "centralized base station configuration + modulation state differentiation + resource block reuse". This improves PUCCH resource utilization and avoids collisions by leveraging modulation differences, and the entire implementation process conforms to the 5G NR protocol specifications. The base station, as the control core, pre-divides fixed SR opportunity resource blocks in the PUCCH channel. The resource block structure complies with relevant protocol requirements, and the SR opportunity period is dynamically adjusted according to the service type. Simultaneously, a portion of the sub-channels is reserved for each resource block as backup resources for collision retransmission, avoiding retransmission interference with normal transmission. Then, the base station uses RRC messages to group user nodes within its coverage area according to geographical location and service activity. Each group shares one SR opportunity resource block. The number of sharing nodes is determined by the modulation scheme; different modulation schemes can provide different numbers of amplitude-phase combinations, corresponding to support different scales of node sharing. The grouping results and the number of shared nodes are synchronized to each node via RRC reconfiguration messages. Meanwhile, the base station assigns a unique "amplitude-phase" modulation state combination to each node in each group. This combination is designed based on the constellation diagram of the corresponding modulation method. Each combination can be uniquely distinguished in the constellation diagram. The modulation state parameters are accurately sent to the nodes through RRC messages for subsequent use.

[0133] After receiving the pre-configured parameters from the base station, the user node first stores its shared group ID, the time and frequency resource location of the SR opportunity, its own dedicated modulation state, and the SR-BSR multiplexing rules. The SR-BSR multiplexing rules define an 8-bit symbol structure: the high 4 bits carry BSR information, and the low 4 bits contain the SR request and node index. It then receives confirmation via PUCCH channel feedback parameters to ensure consistency with the base station configuration. When a node has data to transmit, it first generates a 4-bit BSR message quantization of the data size, then generates a 4-bit information containing the SR request identifier and node index, combining them into 8-bit binary data. Based on its own dedicated modulation state, it maps this data to the modulation symbols of the corresponding modulation scheme, strictly following the 5G NR modulation mapping rules. Simultaneously, the node receives a synchronization signal from the base station to calibrate its local clock, ensuring transmission starts within the specified SR opportunity window and avoiding demodulation failure due to time offset.

[0134] Within the predefined SR opportunity window of the base station, nodes with data requirements within the same shared group will synchronously transmit their generated modulation symbols within the same time-frequency resource block. Different nodes occupy different sub-channels within the resource block, while reserved spare sub-channels remain idle. The symbol signals from multiple nodes are superimposed and transmitted in the PUCCH channel. Because the modulation state of each symbol is unique and isolation is achieved through sub-channel partitioning, the superimposed signals can still be effectively distinguished by the base station, preventing complete signal aliasing due to parallel transmission. After the base station captures the superimposed signals through the PUCCH receiving antenna, it first performs channel equalization to compensate for the effects of channel fading and interference. Then, it splits the signals by sub-channel, separating them into independent data streams and focusing on the signals of the effectively transmitted sub-channels. Subsequently, for the signals of each sub-channel, the base station matches the constellation diagram coordinates one by one based on the pre-configured modulation state list of the shared group, achieving multi-node signal separation through the uniqueness of the modulation state. After separating the modulation symbols of a single node, the base station demodulates them into 8-bit binary data. The high 4 bits are parsed into BSR information to determine the data size, and the low 4 bits are parsed into SR request and node index to clarify the node's resource requirements and identity. The entire demodulation process ensures low-latency response.

[0135] For nodes that successfully demodulate without collision, the base station allocates corresponding PUSCH resources based on the parsed BSR data size, including time-frequency blocks and modulation schemes, and issues Gr-DAT authorizations via the PDCCH channel. After receiving the authorization, the node starts uploading data. If the symbol modulation state of a sub-channel cannot be matched due to signal interference or other factors, it is determined to be a collision. The base station will send a "collision notification" to the shared group via the PDCCH channel and activate the reserved backup sub-channel. After receiving the notification, the colliding node calculates the dynamic backoff delay based on its own C-RNTI and the system clock. After backoff, it retransmits the modulation symbols on the backup sub-channel to avoid occupying the main shared sub-channel again and reduce the probability of repeated collisions.

[0136] The base station monitors the transmission quality of shared SR opportunities in real time and dynamically optimizes the configuration. If the collision rate of a certain shared group is consistently high, it indicates that the current node density exceeds the carrying capacity of the existing modulation method. The base station will adjust the modulation method through RRC messages, increase the upper limit of the number of shared nodes, and distribute the transmission pressure. If the idle rate of a certain shared group is consistently high, it indicates that the current resource configuration does not match the node demand. The base station will merge adjacent shared groups, reduce the number of SR opportunity resource blocks, and avoid wasting PUCCH resources. When a node joins or leaves a shared group, the base station will update the modulation state allocation list in real time and synchronize it to all nodes in the group through RRC messages to ensure that the uniqueness of the modulation state is not affected.

[0137] In this embodiment, in step S5, the temporary QoS request code in the preset format is a fixed-length binary code. The transmission speed adjustment bit supports multi-level speed adjustment options, corresponding to the latency optimization requirements of multi-hop transmission; the transmission reliability adjustment bit supports multi-level reliability adjustment options, corresponding to the retransmission strategy configuration of multi-hop links; the scenario adaptation bit covers predefined scenarios and user-defined scenarios, and each predefined scenario corresponds to a default combination of QoS parameters; in step S5, the transmission form of the temporary QoS request code is adapted to the control message type and scenario requirements. When quickly requesting resources, it is multiplexed with the SR request and transmitted to the PUCCH channel; when reporting the buffer status, it is concatenated with the BSR message and transmitted to the PUSCH channel; in emergency scenarios where there is no need to wait for resource request opportunities, it is combined with the address index, BSR message, and SR request and asynchronously transmitted to the RACH channel.

[0138] Specifically, the unified encoding format simplifies and simplifies the base station demodulation and parsing process, eliminating the need for complex adaptation logic. The multi-level option design of the transmission speed adjustment bit optimizes latency based on the varying latency requirements of different services, meeting diverse latency needs from ordinary data to emergency messages. The multi-level option of the transmission reliability adjustment bit corresponds to the dynamic configuration of the retransmission count, improving data transmission reliability by increasing the number of retransmissions, thus adapting to the high reliability requirements of critical services such as medical data and emergency commands. The predefined scenario design of the scenario adaptation bit reduces user configuration complexity; each scenario corresponds to an optimized combination of QoS parameters, while user-defined scenarios ensure the technology's adaptability to specific services. The design principle of multiple transmission modes is "scenario matching and flexible triggering," selecting the corresponding transmission channel and combination method based on the triggering timing and service scenario of the QoS request, ensuring that the QoS request is delivered to the base station quickly and reliably, while avoiding additional channel resource occupation.

[0139] In this embodiment, in step S6, the end-to-end multi-hop QoS coordination is achieved through hierarchical signaling synchronization: the base station synchronizes temporary QoS parameters to the core network through the control plane interface, and the synchronization signaling uses high-priority transmission to shorten the synchronization delay; during the multi-hop protocol negotiation process with relay nodes and receiving base stations, the core network embeds QoS parameters into the multi-hop control signaling; the relay node adjusts the forwarding queue priority based on the QoS parameters, prioritizing the forwarding of high QoS data messages; the receiving base station reserves downlink channel resources; the core network monitors the QoS execution status of nodes in real time, and triggers resynchronization when an anomaly is detected.

[0140] Specifically, the principle of hierarchical signaling synchronization is step-by-step transmission and full-link coverage. High-priority signaling synchronization from the base station to the core network ensures that QoS parameters are quickly transmitted to the core network, avoiding synchronization delays that could affect multi-hop negotiation. The core network embeds QoS parameters into multi-hop control signaling, enabling all nodes participating in multi-hop transmission, such as relay nodes and receiving base stations, to obtain QoS requirements and achieve full-link parameter synchronization. Relay nodes adjust forwarding queue priorities to ensure that high-QoS messages are not blocked by low-priority messages during multi-hop forwarding, ensuring delay optimization. Reserving downlink channel resources at the receiving base station avoids high-QoS messages competing for resources with other messages during download, ensuring transmission reliability. The core network's real-time monitoring and abnormal resynchronization design are designed to handle parameter synchronization anomalies in multi-hop transmission, ensuring that QoS parameters are effectively executed throughout the link and guaranteeing the stability of end-to-end multi-hop QoS coordination.

[0141] In this embodiment, the base station synchronizes the complete rules of the 8-bit temporary QoS code to the user node via RRC reconfiguration messages. This includes the first 6 bits defining the function and the last 2 bits specifying the reservation. The node stores this information in its local QoS configuration module to ensure coding consistency during request generation. Simultaneously, it synchronizes the "scenario-default parameter" mapping template, clearly defining the default QoS parameter combinations for different scenarios, reducing node configuration complexity. The base station also allocates temporary QoS transmission resources for three types of channels—PUCCH, PUSCH, and RACH—to the user node. The PUCCH channel reserves a dedicated symbol position for "SR+QoS" multiplexing; the PUSCH channel defines the seamless, aligned splicing rules between the QoS code and BSR; and the RACH channel specifies the time interval threshold for asynchronous transmission. All parameters are compatible with the 5G NR channel frame structure. Furthermore, the base station reserves a temporary QoS context storage unit locally for each user node, containing key information such as speed level, reliability level, scenario type, activation identifier, and data block count. The core network reserves a QoS parameter buffer for multi-hop nodes such as relay nodes and receiving base stations to ensure rapid subsequent retrieval.

[0142] The core of user nodes triggering temporary QoS adjustments is generating an 8-bit code that conforms to rules and adapts to different service requirements. After detecting data to be transmitted, the node automatically triggers a temporary QoS request based on the service type, or it can be manually triggered by the user. After triggering, it first checks if it matches a predefined scenario template. If it matches, the template code is directly invoked; otherwise, the first 6 functional bits are manually configured. The generation of the 8-bit code follows specific logic: the speed adjustment bit selects the corresponding level based on service latency requirements; the reliability adjustment bit matches the retransmission policy configuration based on data importance; the scenario adaptation bit corresponds to a predefined scenario or a custom scenario; and the reserved bit is filled with a fixed identifier by default for use in 6G scenarios. The node then combines the 8-bit QoS code with the corresponding control message. When resources need to be requested, it combines "SR request and QoS code"; when reporting to the cache, it combines "BSR message + QoS code"; and in emergency scenarios, it combines "address index + BSR + SR + QoS code". The combined code is aligned according to the base station's pre-configured format to adapt to the modulation requirements of the corresponding channel.

[0143] User nodes select transmission channels based on service scenarios to ensure QoS requests are delivered to the base station quickly and reliably. In normal high-priority scenarios, nodes wait for the pre-allocated SR opportunity window from the base station, multiplexing the SR request identifier and 8-bit QoS code into a single modulation symbol for transmission. Transmission strictly adheres to the modulation state allocated by the base station to avoid collisions with other sharing nodes, and the symbol transmission time is precisely aligned with the SR opportunity window. In large message high-priority scenarios, nodes first send a pure SR request. After receiving Gr-BSR authorization from the base station, they seamlessly concatenate the 8-bit QoS code with the BSR message, aligning it according to the symbol format adapted to the modulation scheme, and transmit it through a designated sub-channel of the PUSCH channel. The minimum transmission block size ensures rapid demodulation by the base station. In emergency scenarios, nodes do not need to wait for SR opportunities. They directly combine the QoS code, address index, BSR, and SR request into a unified message, using a strong anti-interference modulation scheme for transmission through the RACH channel. The time intervals of each field conform to the 5G sensing time slot standard, ensuring base station identification and relevance. An "emergency identifier" is added to the message header to trigger priority processing by the base station.

[0144] After receiving a QoS request, the base station initiates single-use QoS control through efficient parsing and context creation. The base station extracts the QoS code based on the transmission channel type, separates the SR request and QoS code from the demodulation symbols on the PUCCH channel, obtains the QoS code by splitting and splicing messages on the PUSCH channel, and prioritizes parsing the emergency flag and QoS code on the RACH channel. The base station verifies the code's validity; if invalid, it discards the code and sends a "QoS request invalid" message via the PDCCH channel; otherwise, it proceeds to the next step. The base station fills the parsed speed level, reliability level, and scenario type into the user node's temporary QoS context unit, sets the activation flag to enabled, and initializes the data block count. Based on the QoS parameters, it configures resource allocation strategies, such as prioritizing channel time slot allocation, adjusting retransmission counts, and marking expedited processing. Subsequently, the base station, based on the data size parsed from the BSR, allocates corresponding PUSCH resources, specifies the time-frequency block and modulation scheme, generates a Gr-DAT grant, and embeds a "temporary QoS activation flag" in the grant message, informing the user node to transmit data according to the temporary QoS parameters.

[0145] The base station synchronizes QoS parameters through the core network to ensure that each node in the multi-hop link executes the temporary QoS, avoiding priority loss. The base station synchronizes the user identifier, temporary QoS parameters, data size, and single-use validity flag to the core network via the S1 control plane interface. The synchronization message uses expedited signaling to ensure low-latency transmission. Upon receiving the data, the core network immediately embeds the QoS parameters into the multi-hop control signaling and sends it to the relay node and the receiving base station, clarifying that the parameters only apply to the current user's data transmission. Simultaneously, it adjusts the multi-hop link scheduling strategy, reserving a high-priority forwarding queue for this data transmission. After receiving the QoS parameters, the relay node creates a temporary high-priority forwarding queue, skipping low-priority data and forwarding it immediately upon receiving the corresponding data block. The receiving base station reserves dedicated PDSCH channel resources to avoid competition with other data and sets the same retransmission count as the base station to ensure reliable data download. The core network receives QoS execution feedback from the multi-hop nodes in real time and triggers resynchronization in case of anomalies.

[0146] User nodes transmit data according to temporary QoS parameters. The base station and multi-hop nodes strictly control the scope of QoS to ensure it only applies to a single message. After receiving Gr-DAT authorization, a node breaks down the data to be transmitted into transmission blocks and transmits them according to the modulation scheme and retransmission strategy of the temporary QoS. A HARQ acknowledgment is sent back after each block is transmitted to ensure accurate base station counting. Each time the base station receives a data block, it increments the "data block count" in the temporary QoS context and synchronizes it to the core network according to the "receive one block, forward one block" strategy. When the data block count reaches the total number of blocks resolved by the BSR, it marks "single transmission complete." Relay nodes and the receiving base station only process the current data block from that user node using temporary QoS. After transmission is complete, they immediately clear the QoS parameter cache and restore the default scheduling strategy to avoid affecting other messages.

[0147] After a single data transmission is completed, temporary resources are quickly cleared and the default configuration is restored. When the base station detects that the data block count has reached the total number of blocks and has received all data blocks, it immediately triggers temporary QoS context cleanup; if data transmission fails, cleanup is also triggered after a timeout. The base station clears the parameters of the temporary QoS context unit, sets the effective flag to the off state, and sends a "temporary QoS end" notification to the user node via the PDCCH channel; after receiving the notification, the user node stops using temporary QoS parameters, restores the default QoS configuration, and clears its local QoS request cache; after receiving the "transmission complete" feedback from the base station, the core network and multi-hop nodes clear the QoS parameter cache, close the temporary high-priority queue, and restore the default scheduling policy.

[0148] In one possible embodiment, the dynamic address index database ensures the security of index transmission through encryption technology. A checksum is generated during the index allocation process, and the user node carries the checksum when transmitting the index. After receiving and verifying the checksum, the base station performs an address demapping operation. The index length, transmission format, and synchronization signaling of the dynamic address index database are all compatible with the set network protocol specifications.

[0149] Specifically, encryption prevents the index from being maliciously tampered with or stolen during transmission, ensuring the accuracy of address demapping and communication security. The core of the verification code mechanism is "identity verification and prevention of malicious attacks." The verification code generated when the base station allocates the index is bound to the user node's identity. The user node carries the verification code when transmitting the index. The base station performs the demapping operation only after the verification is successful, which can effectively resist malicious index attacks. The design principle of compatibility with network protocol specifications is "seamless integration and reduced implementation costs." The technical solution does not require modification of the existing network architecture and is seamlessly compatible with existing 5G NR and other protocol specifications. It supports flexible switching with traditional address transmission methods, ensuring that existing services are not affected and improving the feasibility of the technical solution.

[0150] In one possible embodiment, the base station monitors the transmission quality indicators of SR opportunities in real time, including collision rate and resource idle rate: if the collision rate continues to be higher than a set value, the number of shared user nodes is increased by adjusting the modulation method to distribute the transmission pressure; if the resource idle rate is higher than a set value, adjacent resource sharing groups are merged to reduce the number of idle resource blocks; when a user node joins or leaves the sharing group, the base station updates the modulation state allocation list in real time and synchronizes it to all user nodes in the group to ensure the uniqueness of the modulation state.

[0151] Specifically, when the collision rate remains high, it indicates that the current number of shared nodes has exceeded the carrying capacity of the modulation scheme. Upgrading the modulation scheme (e.g., from 16QAM to 256QAM) increases the number of shareable nodes, distributes transmission pressure, and reduces the collision rate. When the resource idle rate remains high, it indicates that the current number of SR opportunity resource blocks does not match the needs of user nodes. Merging adjacent shared groups can reduce idle resource blocks and improve the utilization rate of PUCCH channel resources. Real-time updates of the modulation state allocation list when user nodes join or leave are to "maintain the uniqueness of modulation state," ensuring that newly joined nodes obtain a unique amplitude-phase combination, and that the modulation state of leaving nodes can be reallocated. This avoids modulation state conflicts caused by dynamic changes in nodes and ensures the stable operation of the multi-node shared SR opportunity mechanism.

[0152] The application scenarios of this invention are as follows:

[0153] Scenario 1: Emergency Communication Scenario

[0154] It is suitable for scenarios requiring millisecond-level response, such as earthquake emergency response, fire early warning, and medical emergency. User nodes do not need to wait for SR opportunities. They transmit the address index, BSR, SR request and temporary QoS code together via the RACH asynchronous path. The core network triggers a multi-hop negotiation expedited process, skipping unnecessary verification steps. Relay nodes prioritize forwarding emergency data, and the receiving base station reserves dedicated downlink resources. The multi-hop preparation latency is as low as 3~5ms, ensuring the rapid transmission of emergency instructions and emergency data and avoiding rescue failure due to delays.

[0155] Scenario 2: Intelligent Transportation (Internet of Vehicles) Scenario:

[0156] It is adapted to scenarios such as autonomous driving collision warning, vehicle cooperative communication, and interaction between roadside equipment and vehicles. As a user node, the vehicle transmits the address indexes of commonly used roadside equipment and surrounding vehicles through the PUCCH+SR path. Combined with temporary QoS dynamic adjustment (speed upgrade level 1 + reliability upgrade level 2), it ensures low-latency transmission of cooperative data. The dynamic address index database supports fast index allocation for temporarily encountered vehicles and short-cycle cleanup of 14 days, adapting to the high mobility of vehicles. At the same time, the SR mechanism is optimized to reduce the collision rate of concurrent requests from multiple vehicles, ensuring the real-time performance and reliability of vehicle-road cooperation and vehicle-to-vehicle cooperation.

[0157] Scenario 3: Industrial Internet of Things (IIoT) Scenarios

[0158] It covers scenarios such as industrial control, remote equipment operation and maintenance, and industrial big data transmission. Industrial equipment transmits large-size production data and operation and maintenance instructions through the PUSCH+BSR path. The address index and BSR are seamlessly spliced ​​to reduce signaling overhead, and 256QAM modulation adapts to high bandwidth requirements. Temporary QoS dynamic adjustment supports "single message level" priority configuration, and production control instructions can temporarily improve transmission reliability and avoid process interruption caused by retransmission. The lightweight storage mode of the dynamic address index database reduces the resource occupation of edge base stations and adapts to the communication needs of massive low-interaction devices.

[0159] Scenario 4: Large-scale IoT scenario:

[0160] Suitable for scenarios with massive node access, such as smart homes, environmental monitoring, and smart security. Terminal nodes (such as sensors and cameras) transmit short indexes of high-frequency interactive objects through the PUCCH+SR path. The 4-6 bit index is adapted to 16QAM / 64QAM modulation, which greatly reduces bandwidth consumption. The SR multi-node sharing mechanism improves the utilization of PUCCH resources and avoids resource idleness caused by massive concurrent requests from nodes. Predefined scenario templates for temporary QoS (such as the default parameter combination for "large-scale IoT") reduce the complexity of terminal configuration and adapt to the low-power and low-interaction characteristics of IoT.

[0161] Scenario 5: 6G Preliminary Scenarios

[0162] Supporting the evolution requirements of 6G "integrated sensing and terrestrial networks". In integrated sensing scenarios, the reserved bits of temporary QoS coding can be expanded into "sensing accuracy adaptation bits", which, combined with end-to-end multi-hop collaboration, balance communication latency and sensing data reliability. In terrestrial network integrated scenarios (integration of satellite and terrestrial networks), the dynamic address index database supports rapid synchronization and cross-base station query of satellite terminal addresses, and the anti-interference modulation of the RACH asynchronous path adapts to the characteristics of satellite link, ensuring the continuity and low latency of multi-hop transmission in integrated space-ground-terrestrial networks.

[0163] Example 2

[0164] See Figure 4 Embodiment 2 of the present invention also provides a fast multi-hop message transmission system for communication networks, which employs the above-described fast multi-hop message transmission method for communication networks, including:

[0165] The dynamic address index database module 100 is used to construct a two-level distributed dynamic address index database consisting of a base station local database and a core network global database, and to establish and maintain an index-address mapping relationship through the dynamic address index database.

[0166] The multiplexing message generation and transmission module 200 is used to obtain the index corresponding to the destination address based on the dynamic address index database before the user node uploads the complete data message, and to multiplex and transmit at least one of the control messages, namely the index corresponding to the destination address, scheduling request, and cache status report, to the base station through a preset control channel.

[0167] The base station receiving and multi-hop negotiation triggering module 300 is used to demodulate and extract the index after the base station receives the multiplexing message and obtain the complete destination address by querying the dynamic address index database. The destination address and data size information are transmitted to the core network in parallel. The core network initiates multi-hop protocol negotiation with the receiving base station and relay node in parallel.

[0168] The SR mechanism optimization module 400 is used by the base station to adopt a multi-node shared SR opportunity mechanism, assign a unique modulation state to user nodes sharing the same SR opportunity, carry dual information through SR-BSR signaling multiplexing technology, and implement a dynamic backoff collision resolution mechanism based on the unique identifier of the user node and the system clock.

[0169] The temporary QoS request processing module 500 is used by user nodes to generate temporary QoS request codes in a preset format. The request codes are divided into transmission speed adjustment bits, transmission reliability adjustment bits, scenario adaptation bits and reserved bits according to their functions. The code is transmitted to the base station through the control channel. After demodulation, the base station creates a temporary QoS context for a single data message.

[0170] The end-to-end multi-hop QoS coordination module 600 is used by the base station to synchronize temporary QoS context parameters to the core network. The core network embeds the temporary QoS context parameters in the multi-hop protocol negotiation and synchronizes them to the relay node and the receiving base station to realize end-to-end multi-hop QoS coordination.

[0171] The data transmission and resource reclamation module 700 is used by user nodes to incrementally upload data through a preset data channel according to temporary QoS context parameters and resource authorization issued by the base station. After receiving the data block, the base station forwards it to the core network. The core network completes the data transmission through the established multi-hop link. After the transmission is completed, the temporary QoS context is cleared and the default configuration is restored.

[0172] In this embodiment, the dynamic address index database module 100 supports an automatic index allocation mechanism, an invalid cleanup mechanism, and a multi-level synchronization mechanism.

[0173] The multi-level synchronization mechanism divides the synchronization range and period according to the level. User nodes and base stations perform periodic synchronization of high-frequency address mapping, base stations and core network perform periodic synchronization of low-frequency and cross-base station address mapping, and core network and all base stations in the network perform periodic synchronization of cross-cell high-frequency address mapping. The invalid cleanup mechanism performs automatic cleanup of indexes that have not been used for a set period of time, and sets protection strategies for emergency address indexes and important address indexes manually marked by users.

[0174] In this embodiment, the preset control channel in the multiplexed message generation and transmission module 200 includes a PUCCH channel, a PUSCH channel, and a RACH channel;

[0175] The PUCCH channel is adapted for low-latency scenarios, multiplexing the index and SR request into a single modulation symbol for transmission; the PUSCH channel is adapted for large message transmission scenarios, seamlessly concatenating the index and BSR message before transmission; the RACH channel is adapted for emergency communication scenarios, combining the index, BSR message, and SR request for asynchronous transmission.

[0176] In this embodiment, in the base station receiving and multi-hop negotiation triggering module 300, after the base station receives the multiplexing message, it demodulates and extracts the index and obtains the complete destination address by querying the dynamic address index database:

[0177] After receiving the index, the base station first queries the high-frequency address mapping stored in the local database to obtain the complete address;

[0178] If no matching mapping is found in the local database, a query is initiated to the core network global database through the interface. The core network global database covers low-frequency and cross-base station address mappings across the entire network. After the query result is fed back to the base station, the base station caches the query result in the local database.

[0179] If the index is invalid or the query returns no results, switch to full address transfer mode.

[0180] In this embodiment, in the SR mechanism optimization module 400, the unique modulation state is realized based on the amplitude-phase combination difference of the modulation method. The amplitude-phase combination allocated to different user nodes is uniquely distinguishable in the modulation constellation diagram. The base station identifies the corresponding request node through the amplitude and phase characteristics of the demodulated symbol.

[0181] The SR-BSR signaling multiplexing technology carries both data size quantization information and resource request related identifiers through a single modulation symbol;

[0182] The dynamic backoff collision resolution mechanism calculates differentiated backoff delays using a portion of the user node's unique identifier and a portion of the system clock's timing information, ensuring that the retransmission times of colliding nodes do not overlap. After detecting a collision, the base station sends a collision notification to the relevant user node through a designated channel. Upon receiving the notification, the node initiates the backoff and retransmission process, using reserved resource blocks during retransmission.

[0183] In this embodiment, in the temporary QoS request processing module 500, the temporary QoS request encoding of the preset format is a fixed-length binary encoding, the transmission speed adjustment bit supports multi-level speed adjustment options, corresponding to the latency optimization requirements of multi-hop transmission; the transmission reliability adjustment bit supports multi-level reliability adjustment options, corresponding to the retransmission strategy configuration of multi-hop links; the scenario adaptation bit covers predefined scenarios and user-defined scenarios, and each predefined scenario corresponds to a default QoS parameter combination.

[0184] In the temporary QoS request processing module 500, the transmission format of the temporary QoS request encoding is adapted to the control message type and scenario requirements. When quickly requesting resources, it is multiplexed with the SR request and transmitted to the PUCCH channel; when reporting the cache status, it is concatenated with the BSR message and transmitted to the PUSCH channel; in emergency scenarios where there is no need to wait for resource request opportunities, it is combined with the address index, BSR message, and SR request and transmitted asynchronously to the RACH channel.

[0185] In this embodiment, in the end-to-end multi-hop QoS coordination module 600, the end-to-end multi-hop QoS coordination is achieved through hierarchical signaling synchronization:

[0186] The base station synchronizes temporary QoS parameters to the core network through the control plane interface, and the synchronization signaling is transmitted with high priority to shorten the synchronization delay.

[0187] During the multi-hop protocol negotiation process between the core network and relay nodes and receiving base stations, QoS parameters are embedded in the multi-hop control signaling; relay nodes adjust the forwarding queue priority based on QoS parameters, giving priority to forwarding high QoS data messages; receiving base stations reserve downlink channel resources; the core network monitors the QoS execution status of nodes in real time and triggers resynchronization when an anomaly is detected.

[0188] It should be noted that the information interaction and execution process between the modules of the above system are based on the same concept as the method embodiment in Embodiment 1 of this application, and the resulting technical effects are the same as those in the method embodiment of this application. For details, please refer to the description in the method embodiment shown above in this application, and it will not be repeated here.

[0189] Example 3

[0190] Embodiment 3 of the present invention provides a non-transitory computer-readable storage medium storing program code for a fast multi-hop message transmission method for a communication network. The program code includes instructions for executing the fast multi-hop message transmission method for a communication network according to Embodiment 1 or any possible implementation thereof.

[0191] Computer-readable storage media can be any available medium that a computer can access, or a data storage device such as a server or data center that integrates one or more available media. The available medium can be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., DVDs), or semiconductor media (e.g., solid-state drives (SSDs)).

[0192] Example 4

[0193] Embodiment 4 of the present invention provides an electronic device, including: a memory and a processor;

[0194] The processor and the memory communicate with each other via a bus; the memory stores program instructions that can be executed by the processor, and the processor can execute the fast multi-hop message transmission method for communication networks in Embodiment 1 or any possible implementation thereof by calling the program instructions.

[0195] Specifically, a processor can be implemented in hardware or software. When implemented in hardware, the processor can be a logic circuit, an integrated circuit, etc. When implemented in software, the processor can be a general-purpose processor that reads software code stored in memory. This memory can be integrated into the processor or located outside the processor and exist independently.

[0196] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented in software, it can be implemented, in whole or in part, as a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of the present invention are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means.

[0197] It is obvious to those skilled in the art that the modules or steps of the present invention described above can be implemented using general-purpose computing devices. They can be centralized on a single computing device or distributed across a network of multiple computing devices. Optionally, they can be implemented using computer-executable program code, thereby storing them in a storage device for execution by a computing device. In some cases, the steps shown or described can be performed in a different order than those presented herein, or they can be fabricated as separate integrated circuit modules, or multiple modules or steps can be fabricated as a single integrated circuit module. Thus, the present invention is not limited to any particular combination of hardware and software.

[0198] Although the present invention has been described in detail above with general descriptions and specific embodiments, modifications or improvements can be made to it, which will be obvious to those skilled in the art. Therefore, all such modifications or improvements made without departing from the spirit of the present invention fall within the scope of protection claimed by the present invention.

Claims

1. A method for multi-hop message transmission in a communication network, characterized in that, Includes the following steps: (1) Construct a two-level distributed dynamic address index database consisting of a local base station database and a global core network database, and establish and maintain an index-address mapping relationship through the dynamic address index database; In step (1), the dynamic address index database supports an automatic index allocation mechanism, an invalid cleanup mechanism, and a multi-level synchronization mechanism; The multi-level synchronization mechanism divides the synchronization range and period according to the level. User nodes and base stations perform periodic synchronization of high-frequency address mapping, base stations and core network perform periodic synchronization of low-frequency and cross-base station address mapping, and core network and all base stations in the network perform periodic synchronization of cross-cell high-frequency address mapping. The invalid cleanup mechanism performs automatic cleanup of indexes that have not been used for a set period of time, and sets protection strategies for emergency address indexes and important address indexes manually marked by users. (2) Before the user node uploads the complete data message, the index corresponding to the destination address is obtained based on the dynamic address index database, and at least one of the control messages, namely the index corresponding to the destination address, the scheduling request, and the cache status report, is multiplexed and transmitted to the base station through a preset control channel; (3) After receiving the multiplexing message, the base station demodulates and extracts the index and obtains the complete destination address through the dynamic address index database. It then transmits the destination address and data size information to the core network in parallel. The core network then initiates multi-hop protocol negotiation with the receiving base station and relay node in parallel. (4) The base station adopts a multi-node shared SR opportunity mechanism, assigns a unique modulation state to user nodes that share the same SR opportunity, carries dual information through SR-BSR signaling multiplexing technology, and implements a dynamic backoff collision resolution mechanism based on the unique identifier of the user node and the system clock. In step (4), the unique modulation state is realized based on the amplitude-phase combination difference of the modulation method. The amplitude-phase combination assigned to different user nodes is uniquely distinguishable in the modulation constellation diagram. The base station identifies the corresponding request node by the amplitude and phase characteristics of the demodulated symbol. The SR-BSR signaling multiplexing technology carries both data size quantization information and resource request related identifiers through a single modulation symbol; The dynamic backoff collision resolution mechanism calculates differentiated backoff delays by combining a portion of the user node's unique identifier with a portion of the system clock's timing information, ensuring that the retransmission times of colliding nodes do not overlap. After a collision is detected by the base station, a collision notification is sent to the relevant user nodes through a designated channel. After receiving the notification, the nodes initiate a backoff and retransmission process, and the reserved resource blocks are used during retransmission. (5) The user node generates a temporary QoS request code in a preset format. The request code is divided into transmission speed adjustment bits, transmission reliability adjustment bits, scenario adaptation bits and reserved bits according to function. It is transmitted to the base station through the control channel. The base station demodulates the code and creates a temporary QoS context for a single data message. (6) The base station synchronizes the temporary QoS context parameters to the core network. The core network embeds the temporary QoS context parameters in the multi-hop protocol negotiation and synchronizes them to the relay node and the receiving base station to achieve end-to-end multi-hop QoS coordination. In step (6), the end-to-end multi-hop QoS coordination is achieved through hierarchical signaling synchronization: The base station synchronizes temporary QoS parameters to the core network through the control plane interface, and the synchronization signaling is transmitted with high priority to shorten the synchronization delay. During the multi-hop protocol negotiation process between the core network and relay nodes and receiving base stations, QoS parameters are embedded in the multi-hop control signaling. Relay nodes adjust the priority of forwarding queues based on QoS parameters, prioritizing the forwarding of high QoS data messages; The receiving base station reserves downlink channel resources; the core network monitors the QoS execution status of nodes in real time and triggers resynchronization when an anomaly is detected; (7) User nodes upload data incrementally through preset data channels according to temporary QoS context parameters and resource authorization issued by the base station. After receiving the data block, the base station forwards it to the core network. The core network completes the data transmission through the established multi-hop link. After the transmission is completed, the temporary QoS context is cleared and the default configuration is restored.

2. The multi-hop message transmission method for communication networks according to claim 1, characterized in that, In step (2), the preset control channels include the PUCCH channel, the PUSCH channel, and the RACH channel; The PUCCH channel is adapted for low-latency scenarios, multiplexing the index and SR request into a single modulation symbol for transmission; the PUSCH channel is adapted for large message transmission scenarios, seamlessly concatenating the index and BSR message before transmission; the RACH channel is adapted for emergency communication scenarios, combining the index, BSR message, and SR request for asynchronous transmission.

3. The multi-hop message transmission method for communication networks according to claim 1, characterized in that, In step (3), after the base station receives the multiplexing message, it demodulates and extracts the index and obtains the complete destination address by querying the dynamic address index database: After receiving the index, the base station first queries the high-frequency address mapping stored in the local database to obtain the complete address; If no matching mapping is found in the local database, a query is initiated to the core network global database through the interface. The core network global database covers low-frequency and cross-base station address mappings across the entire network. After the query result is fed back to the base station, the base station caches the query result in the local database. If the index is invalid or the query returns no results, switch to full address transfer mode.

4. The multi-hop message transmission method for communication networks according to claim 1, characterized in that, In step (5), the preset format temporary QoS request code is a fixed-length binary code. The transmission speed adjustment bit supports multi-level speed adjustment options, corresponding to the delay optimization requirements of multi-hop transmission. The transmission reliability adjustment bit supports multi-level reliability adjustment options, corresponding to the retransmission strategy configuration of multi-hop links. The scenario adaptation bit covers predefined scenarios and user-defined scenarios. Each predefined scenario corresponds to a default combination of QoS parameters. In step (5), the transmission format of the temporary QoS request code is adapted to the control message type and scenario requirements. When applying for resources, it is multiplexed with the SR request and transmitted to the PUCCH channel; when reporting the cache status, it is concatenated with the BSR message and transmitted to the PUSCH channel; in emergency scenarios where there is no need to wait for resource application opportunities, it is combined with the address index, BSR message and SR request and transmitted asynchronously to the RACH channel.

5. The multi-hop message transmission method for communication networks according to claim 1, characterized in that, The dynamic address index database ensures the security of index transmission through encryption technology. A check code is generated during the index allocation process. When the user node transmits the index, it carries the check code. After receiving and verifying the code, the base station performs an address demapping operation. The index length, transmission format, and synchronization signaling of the dynamic address index database are all compatible with the set network protocol specifications.

6. The multi-hop message transmission method for communication networks according to claim 1, characterized in that, The base station monitors the transmission quality indicators of SR opportunities in real time, including collision rate and resource idle rate: if the collision rate continues to be higher than the set value, the number of shared user nodes is increased by adjusting the modulation method to distribute the transmission pressure; If the resource idle rate is higher than the set value, merge adjacent resource sharing groups to reduce the number of idle resource blocks; When a user node joins or leaves the sharing group, the base station updates the modulation state allocation list in real time and synchronizes it to all user nodes in the group to ensure the uniqueness of the modulation state.

7. A multi-hop message transmission system for a communication network, employing the multi-hop message transmission method for a communication network as described in any one of claims 1 to 6, characterized in that, include: The dynamic address index database module is used to construct a two-level distributed dynamic address index database consisting of a base station local database and a core network global database, and to establish and maintain an index-address mapping relationship through the dynamic address index database. The multiplexing message generation and transmission module is used to obtain the index corresponding to the destination address based on the dynamic address index database before the user node uploads the complete data message, and to multiplex and transmit at least one of the control messages, including the index corresponding to the destination address, the scheduling request, and the cache status report, to the base station through a preset control channel. The base station receiving and multi-hop negotiation triggering module is used to demodulate and extract the index after the base station receives the multiplexing message, and obtain the complete destination address by querying the dynamic address index database. The destination address and data size information are transmitted to the core network in parallel. The core network initiates multi-hop protocol negotiation with the receiving base station and relay node in parallel. The SR mechanism optimization module is used by the base station to adopt a multi-node shared SR opportunity mechanism, assign a unique modulation state to user nodes sharing the same SR opportunity, carry dual information through SR-BSR signaling multiplexing technology, and implement a dynamic backoff collision resolution mechanism based on the unique identifier of the user node and the system clock. The temporary QoS request processing module is used by user nodes to generate temporary QoS request codes in a preset format. The request codes are divided into transmission speed adjustment bits, transmission reliability adjustment bits, scenario adaptation bits and reserved bits according to their functions. They are transmitted to the base station through the control channel. After demodulation, the base station creates a temporary QoS context for a single data message. An end-to-end multi-hop QoS coordination module is used by the base station to synchronize temporary QoS context parameters to the core network. The core network embeds the temporary QoS context parameters in the multi-hop protocol negotiation and synchronizes them to the relay node and the receiving base station to achieve end-to-end multi-hop QoS coordination. The data transmission and resource reclamation module is used by user nodes to incrementally upload data through a preset data channel according to temporary QoS context parameters and resource authorization issued by the base station. After receiving the data block, the base station forwards it to the core network. The core network completes the data transmission through the established multi-hop link. After the transmission is completed, the temporary QoS context is cleared and the default configuration is restored.

Images