Transmission method of common channel block, communication node and storage medium

Abstract

This application provides a method for transmitting a common channel block, a communication node, and a storage medium. The method for transmitting the common channel block includes: determining the form and configuration information of the common channel block; and transmitting the common channel block according to the form and the configuration information.

Description

Technical Field

[0001] This application relates to the field of wireless communication technology, and for example to a method for transmitting a common channel block, a communication node, and a storage medium. Background Technology

[0002] To meet diverse application scenarios and higher performance requirements, future communication systems will support an expanded range of frequency resources, posing greater challenges to the management and allocation of these resources. Transmission over common channels is one of the main research directions. Existing common channel transmission mechanisms have some shortcomings. For example, in beam hopping scenarios, beam hopping technology can serve different areas by dynamically switching beams. In this case, the transmission resources of common channels in the existing New Radio (NR) are directly limited by beam availability. The discontinuity of common channel resources in time not only increases the computational complexity and power consumption for UEs accessing the network for the first time, but may also cause resources to become unavailable due to beam switching, thus prolonging access latency. For another example, the indication of common channel transmission resources relies on the downlink control information (DCI) carried by the Physical Downlink Control Channel (PDCCH) for dynamic scheduling. This increases the control signaling overhead of common channels. Especially in multi-beam or non-terrestrial network scenarios, frequent beam switching will further exacerbate the scheduling complexity and increase the computational overhead and energy consumption of user equipment. In particular, UEs accessing the network for the first time are sensitive to the latency of the entire access process. Existing mechanisms impose strong constraints on the design of beam hopping patterns, and UEs may miss critical common channel transmission windows due to rapid beam switching. Overall, the transmission efficiency of existing public channels is relatively low. Summary of the Invention

[0003] This application provides a method for transmitting a common channel block, a communication node, and a storage medium.

[0004] This application provides a method for transmitting a common channel block, including:

[0005] Determine the format and configuration information of the common channel block;

[0006] The common channel block is transmitted according to the aforementioned format and configuration information.

[0007] This application also provides a communication node, including: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the program to implement the above-described method for transmitting common channel blocks.

[0008] This application also provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the above-described method for transmitting common channel blocks. Attached Figure Description

[0009] Figure 1 A flowchart illustrating a method for transmitting a common channel block, as provided in one embodiment;

[0010] Figure 2 A schematic diagram of a common channel block provided in one embodiment;

[0011] Figure 3 A schematic diagram of another common channel block provided in one embodiment;

[0012] Figure 4 A schematic diagram of another common channel block provided in one embodiment;

[0013] Figure 5 A schematic diagram of yet another common channel block provided in one embodiment;

[0014] Figure 6 A schematic diagram of a transmission device for a common channel block is provided in one embodiment;

[0015] Figure 7 This is a schematic diagram of the hardware structure of a communication node provided in one embodiment. Detailed Implementation

[0016] The present application will now be described in conjunction with the accompanying drawings and embodiments. It is to be understood that the specific embodiments described herein are merely illustrative of the application and not intended to limit it. It should be noted that, unless otherwise specified, the embodiments and features described herein can be arbitrarily combined with each other. Furthermore, it should be noted that, for ease of description, the accompanying drawings show only the parts relevant to the present application, not the entire structure.

[0017] In high-frequency bands (such as millimeter wave or terahertz) or non-terrestrial networks (such as low-Earth orbit satellites), base stations (BSs) typically cannot generate a sufficient number of beams simultaneously to cover their entire service area. In such cases, beam hopping technology can be used, which dynamically switches beams to serve different areas. The transmission resources of common channels in 5G NR are directly limited by beam availability. For example, the 5G NR protocol relies on DCI to dynamically schedule common channel resources, resulting in temporal discontinuities in the transmission of Synchronization Signal and PBCH blocks (SSBs), System Information Blocks (SIBs) such as SIB1 and SIBx, and Random Access Channels (RACHs). This discontinuity poses significant problems for UEs making initial access, as these UEs need to complete the reception of multiple common channels and initiate initial access (such as transmitting a preamble via RACH) within a limited time window. In low-Earth orbit satellite scenarios, beam switching frequency may be as high as several times per second. The UE needs to quickly decode multiple DCIs to locate SSB, System Information (SI) and RACH resources. This not only increases the UE's computational complexity and power consumption, but may also cause resources to become unavailable due to beam switching, thus prolonging access latency.

[0018] Furthermore, in 5G NR, the transmission resource indication of common channels relies on the dynamic scheduling of DCI carried by the PDCCH, which increases the signaling overhead of common channel control. This is especially true in multi-beam or non-terrestrial network scenarios, where frequent beam switching further exacerbates the scheduling complexity. In beam hopping scenarios, the UE needs to decode multiple DCIs to determine the relevant common channel resources, thereby increasing the computational overhead and energy consumption of the user equipment. In particular, UEs initially accessing the network are sensitive to the latency of the entire access process, and existing mechanisms impose strong constraints on the design of the beam hopping pattern. For example, the period and switching mode of beam hopping must be aligned with the dynamic scheduling time of SSB, SI, and RACH; otherwise, the UE may not be able to obtain the necessary resources in time, affecting the access success rate. This is particularly prominent in high-mobility scenarios (such as drones or satellite terminals), where the UE may miss critical common channel transmission windows due to rapid beam switching.

[0019] In summary, existing common channel transmission mechanisms suffer from low resource allocation efficiency and high signaling overhead in beam hopping scenarios, making it difficult to meet the initial latency requirements of UEs and imposing strong constraints on beam hopping mode design. This application proposes a Common Channel Block (CCB) transmission method to address these issues. This method primarily enhances support for beam hopping scenarios and reduces signaling overhead by establishing fixed associations between different common channel resources. This facilitates improved resource efficiency and system compatibility within a unified design framework supporting multiple scenarios in future communication systems (such as 6G).

[0020] In communication systems, the transmission of common channels (such as SI) relies on the coordinated operation of synchronization signal blocks and PDCCH. SSBs are broadcast at fixed intervals (e.g., 5ms–160ms) and include the Primary Synchronization Signal (PSS), Secondary Synchronization Signal (SSS), and Master Information Block (MIB). The MIB is carried through the Physical Broadcast Channel (PBCH) and indicates the scheduling information for System Information Block 1 (SIB1). SIB1 and other System Information Blocks (SIBx, such as SIB2, SIB3, etc.) are transmitted through the Physical Downlink Shared Channel (PDSCH), with scheduling dynamically indicated by the DCI of the PDCCH. The transmission period of SIB1 can differ from that of the SSB, while SIBx is transmitted through the SI-Window mechanism, allowing each SIBx to be configured with an independent period, partially decoupling the SI and SSB periods. Furthermore, it supports an on-demand system information (SI) mechanism, allowing the UE to trigger SIBx transmission via random access messages (Msg1 or Msg3), thereby reducing unnecessary broadcast overhead. SI transmission adopts a hierarchical structure: MIB and SIB1 are mandatory core system information, while SIBx is on-demand or scenario-specific extended information (such as location, V2X, or non-terrestrial network parameters).

[0021] In some embodiments, the terminal can be a device with wireless transceiver capabilities, which can be deployed on land, including indoors or outdoors, handheld, wearable, or vehicle-mounted; it can also be deployed on water (such as on ships); and it can also be deployed in the air (e.g., on airplanes, balloons, and satellites). The terminal can be a mobile phone, tablet computer, computer with wireless transceiver capabilities, virtual reality (VR) terminal, augmented reality (AR) terminal, wireless terminal in industrial control, wireless terminal in self-driving, wireless terminal in remote medical care, wireless terminal in smart grid, wireless terminal in transportation safety, wireless terminal in smart city, wireless terminal in smart home, etc. The embodiments of this application do not limit the application scenarios. The term "terminal" can sometimes also refer to a user, user equipment (UE), access terminal, UE unit, UE station, mobile station, mobile station, remote station, remote terminal, mobile device, UE terminal, wireless communication device, UE agent, or UE device, etc., but the embodiments of this application do not limit this to these terms.

[0022] In some embodiments, the base station may be a base station in Long Term Evolution (LTE), Long Term Evolution Advanced (LTEA), or an evolved Node B (eNB or eNodeB), a base station device in a 5G network, or a base station in a future communication system. The base station may include various macro base stations, micro base stations, femtocell base stations, wireless remote extensions, reconfigurable intelligent surfaces (RISs), routers, wireless Fidelity (WIFI) devices, or various network-side devices such as primary cells and secondary cells.

[0023] Figure 1 This is a flowchart illustrating a common channel block transmission method according to one embodiment. This method can be applied to communication nodes, which can be nodes monitoring the common channel, such as a BS or UE. In a D2D scenario, it can also be applied to situations with a master UE and non-master UEs. Figure 1As shown, the method provided in this embodiment includes steps 110 and 120.

[0024] In step 110, the form and configuration information of the common channel block are determined.

[0025] In step 120, the common channel block is transmitted according to the form and the configuration information.

[0026] In this embodiment, a common channel block (also called a common information block) can be understood as a combination of at least two common channels, or as a continuous or discontinuous time-frequency resource block that can accommodate at least two common channels. Common channels can be synchronization signals (SS), synchronization signal blocks, system information, RACH resources, or PDSCH resources, etc.

[0027] The form of a common channel block can be determined based on network scenarios and beam availability requirements. As an example, a common channel block can be a combination of common channels on contiguous resources or a combination of common channels on discontinuous resources. Based on this, it can meet the resource allocation and transmission efficiency requirements of terrestrial networks (TN), non-terrestrial networks (NTN), and various terminal types (such as smartphones, low-power IoT devices, drones, and satellite terminals) in future communication systems.

[0028] As an example, in an NTN scenario, the total duration of the CCB is 5ms and the bandwidth is 20MHz; in a TN scenario, the total duration of the CCB is 10ms and the bandwidth is 100MHz. All common channels contained within the CCB and their occupied time-frequency resources can be configured simultaneously or predefined as specific parameters. For example, SSB occupies the first 1ms within the common channel block, SIB1 occupies the second 1ms within the common channel block, and SIBx occupies the third to fifth ms within the common channel block, etc. The frequency resources corresponding to these channels can be defined using independent parameters (such as the start, length, or end of the frequency domain PRB).

[0029] In one embodiment, the common channel block includes at least one of the following common channels:

[0030] Synchronization signal SS includes at least one of primary synchronization signal and secondary synchronization signal;

[0031] The synchronization signal block (SSB) includes the main synchronization signal, the auxiliary synchronization signal, and the PBCH. The SSB can be used to provide synchronization, identify beams, and provide basic system information.

[0032] First system information, including SIB1, can also be understood as key system information, which can be used to provide key system parameters (such as cell ID and frequency band configuration);

[0033] Second system information, including SIBx, may include non-critical system information, such as system information that can be used to provide on-demand or scenario-specific information (such as NTN track parameters, V2X configuration);

[0034] The transport channel RACH resources of the common channel block, i.e., the PRACH opportunities associated with the SSB, can be used for random access; physical downlink shared channel PDSCH resources, such as PDSCH resources used for broadcast or multicast.

[0035] In one embodiment, the common channel block may take the form of at least one of the following: a combination of common channels on contiguous resources; or a combination of common channels on discontinuous resources.

[0036] As an example, in scenarios like NTN, due to limited beam availability, UEs typically cannot receive multiple SSBs from a single SSB burst and select the optimal quality SSB as they would in TN scenarios. Especially when the satellite beam coverage area is large, the UE may only receive a single SSB. In traditional 5G NR designs, an SSB burst contains multiple SSBs, and the subsequent scheduling of system information (such as SIB1 and SIBx, e.g., SIB19) via PDCCH presents scheduling challenges. Because the satellite needs to transmit multiple common channels within its coverage area (footprint) in a short time through beam hopping to ensure access for all UEs within the service area, the time-discontinuous SSBs, PDCCH, and SIB1 require frequent beam hopping by the satellite. Therefore, a fixed-form common information block can be used, employing continuous time resources to contain multiple common channels.

[0037] In one example, the CCB contains one SSB and one SIB1, and their physical resources are allocated contiguously. For example... Figure 2 As shown, a single SSB and its corresponding SIB1 are placed within one time slot, and their time-frequency resources can be provided in a predefined manner. In this example, SSB+SIB1 occupy a total of 12 symbols * 28 PRBs. The SSB in the left diagram does not use repetition, so there are still some time-frequency resources available for other uses (such as placing other common channels). The SSB in the right diagram uses repetition (the same SSB has 3 transmissions), so its time end point is aligned with SIB1. In addition, the application of repetition can also be reflected in the entire CCB. For example... Figure 2Both single-slot structures can be repeatedly transmitted to obtain link-level receive gain. In this example, the first two symbols are occupied by the control channel (or the control channel can be omitted).

[0038] In one example, the CCB contains one SSB, one SIB1, and one SIB19, whose physical resources are allocated contiguously. For example... Figure 3 As shown, a single SSB and its corresponding SIB1 are placed in one slot, with SSB+SIB1 occupying a total of 14 symbols * 25 PRBs. The next slot contains a control channel and a SIB19. In this example, the first two symbols of the second slot are occupied by the control channel primarily to maintain compatibility with the current NR protocol's PDCCH and SSB resource allocation. The control channel can be used to carry scheduling information for other channels in non-common channel blocks. The control channel and SSB in a slot can be quasi-co-located (QCLed), meaning they are only used to schedule other channels in the corresponding beam's non-common channel block. Alternatively, the first two symbols of the second slot can be used entirely by common signals (such as SIB19) instead of a control channel. The time-frequency resources of each channel in the CCB can be given in a predefined manner.

[0039] In one example, such as Figure 4 As shown, a single SSB and its corresponding SIB1 are placed in one slot, with SSB + SIB1 occupying a total of 14 symbols * 25 PRBs. The subsequent slot contains a control channel and a SIB19. The difference between this example and the previous one is that the first slot presents a possible time-frequency resource allocation method for SSBs and PDSCHs (such as SIB1), meaning the time-frequency resources of the PDSCH are not completely contiguous, as an SSB is embedded within it. The advantage of this method is that the time-frequency resources of the SSB can utilize the SSB resource configuration under non-CCB conditions, thus better compatibility with various UEs receiving the common channel.

[0040] Without loss of generality, the combination of multiple common channels on contiguous resources can be extended to implementation examples that include more common channels, whose time-frequency resources can be given in a predefined manner, and these time-contiguous common channels can include uplink and downlink channels. For example, within a CCB, the SSB and its corresponding SIB1 are located in slot n, its corresponding SIB19 is located in slot n+1, and its corresponding PRACH occasion is located in slot n+4. The resources of common channels can be allocated contiguously and given in a fixed predefined manner. The UE can directly locate subsequent channel resources according to the SSB index without the need for dynamic scheduling through PDCCH.

[0041] Building upon the above, firstly, by arranging resources in continuous time, the BS can complete the transmission of all common channels within a single beam coverage time, avoiding resource interruptions caused by beam skipping and ensuring that the UE completes initial access in a short time. Secondly, the fixed association rule eliminates the need for dynamic scheduling of the PDCCH, reducing control channel overhead and minimizing the energy consumption of the base station due to frequent beam skipping. Taking the NTN scenario as an example, assuming the beam coverage time window is 5ms, and the CCB (including SSB+SIB1+SIB19+RO) occupies 5 consecutive time slots (1ms each), the UE can complete the transmission of downlink synchronization and uplink random preamble within this time window, which helps improve access efficiency.

[0042] In the example of multiple common channel combinations occupying contiguous resources mentioned above, the SSB location may be incompatible with existing NR designs. Therefore, in this embodiment, the CCB can also be defined as a combination of multiple common channels on discontinuous resources. Based on this, by using pre-configured resource allocation rules, dynamic scheduling of the PDCCH is eliminated, avoiding frequent beam hopping due to PDCCH transmission, thereby improving resource utilization efficiency.

[0043] As an example, the CCB comprises an SSB, an SIB1, and an SIB19, whose physical resources are not contiguously allocated. Figure 5 As shown, a single SSB is placed in slot n, its corresponding SIB1 is placed in slot n+1, and its corresponding SIB19 is placed in slot n+2. Each of the latter two slots contains a control channel, and the first two symbols of each slot are occupied by the control channel (or the control channel may not be placed there). The control channel can be used to carry scheduling information for other channels in the non-common channel block. The control channel and SSB in a slot can be quasi-co-located (QCLed), meaning they are only used to schedule other channels in the corresponding beam's non-common channel block. The time-frequency resources of all channels in the CCB can be given in a predefined manner. Idle resources in slot n can be allocated to other service areas by the BS on demand via beam hopping.

[0044] Without loss of generality, the combination of multiple common channels on discontinuous resources can be extended to implementation examples that include more common channels. Their time-frequency resources can be provided in a predefined manner, and these time-discontinuously arranged common channels can include uplink and downlink channels. For example, within a CCB, the SSB is located in slot n, its corresponding SIB1 is located in slot n+1, its corresponding SIB19 is located in slot n+2, and its corresponding PRACH occasion is located in slot n+5. The main technical feature is that the resources of the aforementioned common channels are allocated discontinuously and are provided through fixed predefined methods. The UE can directly locate subsequent channel resources based on the SSB index without dynamic scheduling via PDCCH.

[0045] Furthermore, multiple common channels combined on discontinuous resources can be transmitted in a periodic manner, meaning all common channels have the same period (e.g., all follow the SSB period). The time-domain location of each common channel can then be determined by adding a different offset to the start point of the first common channel period. The offset can be: (a) the offset between the start and end points of the first channel, or (b) the offset between the start and end points of the preceding channel. In summary, common channel resources can be allocated discontinuously, and can be configured via offsets. The UE can directly locate subsequent channel resources based on the SSB index without dynamic scheduling via PDCCH.

[0046] Based on this, the pre-configured time-frequency resource allocation eliminates the need for dynamic scheduling of PDCCH, reducing control channel overhead and avoiding the overhead of frequent beam hopping due to PDCCH transmission. Furthermore, the distribution of discontinuous time resources is compatible with the existing 5G NR SI-Window mechanism. In addition, this approach is suitable for scenarios with high resource allocation flexibility requirements, such as TN high-frequency, high-density UE scenarios. Retaining a certain discontinuous interval helps the BS to dynamically hop beams to provide services in a timely manner according to the UE's service requirements.

[0047] In one embodiment, the common channel block includes at least one SSB; the number of repetitions of the SSB is indicated by the master information block (MIB).

[0048] As an example, a single slot structure can be repeatedly transmitted to obtain link-level receive gain. When repetition is applied, the number of repetitions can be indicated in the MIB.

[0049] In one embodiment, some symbols in the common channel block are occupied by the control channel; the control channel is used to carry scheduling information for channels in the non-common channel block.

[0050] The control channel includes at least one of the following: control resource set (CORESET), search space timing (occasion), physical downlink control channel (PDCCH), and PDCCH candidates. Based on this, compatibility with the PDCCH and SSB resource allocation in the current NR protocol can be maintained.

[0051] In one embodiment, the SSB in the common channel block serves as the quasi-co-address reference signal for the channel in the non-common channel block.

[0052] As an example, the control channel and SSB in a slot can be quasi-co-located (QCLed), meaning they are used only to schedule other channels in the non-common channel block of the corresponding beam.

[0053] In one embodiment, determining the form of the common channel block includes at least one of the following:

[0054] The form of the common channel block is determined based on the type of network access scenario;

[0055] The form of the common channel block is determined based on the frequency resources of the received common channel.

[0056] The form of the common channel block is determined based on the indication information carried in the synchronization signal or the synchronization signal block.

[0057] In this embodiment, the UE can clearly determine whether the current network is transmitting common channels in the form of common channel blocks or using the traditional non-blocked common channel transmission method. This can be correctly identified using at least one of the following methods:

[0058] Method 1: The UE can determine the structure of the common channel based on the scenario type of the access network. For example, in an NTN scenario (via NTN access), due to limited beam availability, a common channel block structure is preferred. In a TN scenario, the UE can receive multiple SSBs to select the optimal beam, thus it is more likely to use a non-blocked common channel transmission method. Specifically, the UE determines the type of the current access network through network identification information (such as cell ID or network type indication) received during the initial access process.

[0059] Method 2: The UE can determine the structure of the common channel based on the frequency resources available for receiving it. Different scenarios typically allocate specific frequency resources. For example, band 256, allocated for NTN scenarios, is used for satellite communication, which is clearly different from bands like band 78 used for millimeter-wave terrestrial communication in terrestrial networks. Therefore, the UE can determine the default assumption for the common channel transmission format during its reception based on different frequency resources. For instance, in NTN bands (such as band 256), the common channel is presented in CCB form; while in TN bands (such as band 78), the common channel uses a non-blocked form, i.e., dynamically scheduling SIB1 and SIBx through PDCCH. A specific implementation example is: during initial access, the UE determines the current operating frequency band through spectrum scanning and determines the common channel format based on pre-configured and / or pre-defined frequency band and structure mapping relationships. For example, if the UE detects that the operating frequency band is band 256, it queries pre-configured and / or predefined rules to determine that the common channel is presented in CCB form, and then determines the SSB, SIB1, and / or PRACH resources according to the pre-configured and / or predefined rules. If the UE detects that the operating frequency band is band 78, it assumes that it is in non-blocked form, and the UE decodes the common channels SSB, PDCCH, SIB1, SIBx, etc., sequentially. Similarly, specific time-frequency resource starting positions can also be used to implicitly indicate the structure of the common channel. For example, some synchronization grid points in band 256 are pre-set to use common channels in CCB form, while other synchronization grid points are pre-set to use common channels in non-CCB form.

[0060] Method 2: The UE can directly determine the common channel structure through the indication information carried in the synchronization signal or the synchronization signal block. Taking the SSB as an example, it includes the PSS, SSS, and PBCH, and the indication information of the common channel structure can be carried in different forms or fields.

[0061] In one embodiment, the indication information includes at least one of the following:

[0062] Indicative information based on SSB sequences;

[0063] Indication information based on the DMRS sequence of the PBCH demodulated reference signal;

[0064] Indicative information based on PBCH scrambled sequences;

[0065] Indication information based on the PBCH indication information field;

[0066] Indication information based on SSB indexes or index groups.

[0067] As an example, for SSB-based indications, the PSS or SSS sequence of the SSB can be designed in different forms to indicate the structure of the common channel. For example, two sets of PSS sequences can be defined: sequence group A indicates that the common channel is presented in CCB form, and sequence group B indicates a non-blocked form. The UE can determine the subsequent channel structure by detecting the PSS sequence group. Assuming the UE detects that the PSS belongs to sequence group A, it resolves the subsequent SIB1, SIBx, and / or PRACH resources according to fixed association rules. As another example, three sets of PSS sequences can be defined: sequence group A indicates that the common channel is presented in CCB1 form, sequence group B indicates that the common channel is presented in CCB2 form, and sequence group C indicates a non-blocked form. The UE can determine the subsequent channel structure by detecting the PSS sequence group. Assuming the UE detects that the PSS belongs to sequence group A, it resolves the subsequent SIB1, SIBx, and / or PRACH resources according to the fixed association rules of CCB1. Assuming the UE detects that the PSS belongs to sequence group B, it resolves the subsequent SIB1 and SIBx resources according to the fixed association rules.

[0068] As an example, for indications based on PBCH DMRS sequences: the DMRS column of the PBCH can be used to carry structure indication information. For example, two sets of PBCH DMRS sequences can be defined, with sequence 1 representing CCB form and sequence 2 representing non-blocked form. Alternatively, three sets of PBCH DMRS sequences can be defined, with sequence 1 representing CCB1 form, sequence 2 representing CCB2 form, and sequence 3 representing non-blocked form. The UE determines the common channel structure by decoding the PBCH DMRS sequences and uses the corresponding parsing method in subsequent steps.

[0069] As an example, regarding indications based on PBCH scrambling sequences: PBCH scrambling can be applied to either the PBCH data portion or the PBCH CRC portion. The scrambling sequence can carry structural indication information. For example, different scrambling sequences can be used to scramble the PBCH data; scrambling sequence A represents CCB format, and scrambling sequence B represents non-blocking format. Alternatively, scrambling sequence A might represent CCB1 format, scrambling sequence B CCB2 format, and scrambling sequence C C C non-blocking format. The UE determines the structural form by attempting to descramble the PBCH (based on a predefined set of scrambling sequences) and determines the subsequent channel resolution method accordingly.

[0070] As an example, for indications based on the PBCH indication information field: A new indication information field is added to the PBCH to directly indicate the common channel structure. For example, an indication bit "1" indicates CCB format, and "0" indicates non-blocked format. The UE obtains this indication bit by decoding the PBCH to determine whether subsequent channels are presented in CCB format. For example, if the UE finds the indication bit "1" after decoding the PBCH, it assumes that a CCB has been received and looks up the mapping table according to the SSB index to locate SIB1, SIB19, and PRACH resources. Furthermore, the indication information field can contain multiple bits; all zeros indicate non-blocked format, and non-zero bits indicate various different CCBs.

[0071] As an example, regarding indications based on SSB indices or index groups: some SSB indices or index groups are predefined to use a common channel in CCB form, while other SSB indices or index groups use a non-CCB common channel form. Based on this, within the same cell, different SSBs can correspond to different common channel structures, making the corresponding SSB suitable for different scenarios (e.g., different area coverage).

[0072] In one embodiment, the configuration information includes at least one of the following: a combination of common channels in a common channel block; and configuration parameters of the time-frequency resources of the common channels in the common channel block.

[0073] As an example, after the UE identifies common channels as presented in the form of Common Channel Blocks (CCBs), it can further determine the specific configuration information of the CCBs to correctly resolve at least one common channel within the CCB. The configuration information may include CCB channel combination configurations. As mentioned earlier, a common information block may include at least one of SS, SSB, first system information, second system information, RACH resources, and other common channels. The configuration information of the CCBs clearly specifies which of the aforementioned channels are included in the CCB. Multiple channel combinations can be used as predefined tables. For example, in an NTN scenario, a CCB may include SSB, MIB, SIB1, SIB19, and PRACH. In a terrestrial high-frequency network scenario, a CCB may only include SSB, MIB, and SIB1.

[0074] CCB channel combination configuration may include channel combination indexes in a predefined table, which may be indicated by the signaling. The signaling may be included in the PBCH information field.

[0075] The configuration information may also include configuration parameters for the time-frequency resources of multiple channels within the CCB. The time-frequency resources of the multiple channels contained in the CCB need to be explicitly configured, or can be achieved through predefined resource allocation. After the UE determines the channel combination configuration contained in the common channel block, it determines the time-frequency resources for each channel based on the channel combination configuration.

[0076] In one embodiment, the configuration parameters of the time-frequency resources include at least one of the following: time resource parameters; frequency resource parameters; channel association rules; wherein,

[0077] The time resource parameters include at least one of the following: the time interval between the reference channel; the time interval between adjacent channels; the rules for setting the time interval; the start symbol and duration of the channel;

[0078] The frequency resource parameters include at least one of the following: frequency resource units per common channel; initial subcarrier spacing (SCS) and frequency domain length; SCS size;

[0079] The channel association rules include: each channel resource is bound to a corresponding SSB index, and each SSB supports independent time resource parameters and frequency resource parameters.

[0080] As an example, time resource parameters include at least one of the following:

[0081] The time interval between relative reference channels, that is, the time interval between each common channel in the common channel block and the reference channel, defines the time position of each common channel. For example, the slot offset relative to the associated SSB (the first channel) is used. SSB is located in slot n, SIB1 is located in slot n+1 (slot offset = 1), and SIBx is located in slot n+3 (slot offset = 3).

[0082] The time interval between adjacent channels is defined by the time interval between each adjacent common channel in the common channel block. For example, the time interval between SSB and SIB1 is fixed at 1ms, and the time interval between SIB1 and SIBx is fixed at 2ms.

[0083] The time interval setting rules define the relative time position of each channel by using the time intervals specified in the setting rules. For example, the time slot position of SIB1 is the SSB time slot plus a fixed offset of 1 slot, and the time slot position of SIBx is the SIB1 time slot plus a fixed offset of 2 slots.

[0084] Each channel starts with a symbol and a duration, for example, SSB starts with symbol 2 and occupies 4 symbols, SIB1 starts with symbol 0 and occupies 14 symbols, and SIBx starts with symbol 0 and occupies 14 symbols.

[0085] As an example, frequency resource parameters include at least one of the following:

[0086] For each common channel, the frequency resource unit, taking PRB as an example, can include the PRB offset of each common channel relative to the associated SSB. SSB starts at PRBk, SIB1 starts at PRBk (PRB offset = 0), and starts at PRBk (PRB offset = 0).

[0087] The starting SCS and frequency domain length of each common channel, for example, SSB starts at SCS 0 and occupies 20 PRBs, SIB1 starts at SCS 0 and occupies 25 PRBs, and SIBx starts at SCS 0 and occupies 25 PRBs.

[0088] The SCS size for each common channel, for example, SSB and SIB1 use a 15kHz subcarrier spacing, while SIBx uses a 30kHz subcarrier spacing.

[0089] As an example, the channel association rule includes: all channel resources in each CCB are bound to its SSB index. Each SSB can be configured independently with the aforementioned time and frequency resources to provide time and frequency resources for all channels in the CCB bound to it.

[0090] This application also provides a common channel block transmission device. Figure 6 This is a schematic diagram of a transmission apparatus for a common channel block, provided as an embodiment. Figure 6 As shown, the transmission device for the common channel block includes:

[0091] Module 210 is configured to determine the form and configuration information of the common channel block.

[0092] The transmission module 220 is configured to transmit the common channel block according to the form and the configuration information.

[0093] In one embodiment, the common channel block includes at least one of the following common channels:

[0094] Synchronization signal SS includes at least one of primary synchronization signal and secondary synchronization signal;

[0095] The synchronization signal block (SSB) includes the primary synchronization signal, the secondary synchronization signal, and the physical broadcast channel (PBCH).

[0096] First system information, including SIB1;

[0097] Second system information, including SIBx;

[0098] RACH resources for the common channel block;

[0099] Physical downlink shared channel (PDSCH) resources.

[0100] In one embodiment, the form includes at least one of the following:

[0101] Combination of common channels on contiguous resources; combination of common channels on discontinuous resources.

[0102] In one embodiment, the common channel block includes at least one SSB;

[0103] The number of times an SSB is repeated is indicated by the main information block (MIB).

[0104] In one embodiment, some symbols in the common channel block are occupied by the control channel; the control channel is used to carry scheduling information for channels in the non-common channel block.

[0105] The control channel includes at least one of the following: control resource set CORESET, search space timing, physical downlink control channel PDCCH, and PDCCH candidate.

[0106] In one embodiment, the SSB in the common channel block serves as the quasi-co-address reference signal for the channel in the non-common channel block.

[0107] In one embodiment, the determining module 210 is configured to be at least one of the following:

[0108] The form of the common channel block is determined based on the type of network access scenario;

[0109] The form of the common channel block is determined based on the frequency resources of the received common channel.

[0110] The form of the common channel block is determined based on the indication information carried in the synchronization signal or the synchronization signal block.

[0111] In one embodiment, the indication information includes at least one of the following:

[0112] Indicative information based on SSB sequences;

[0113] Indication information based on the DMRS sequence of the PBCH demodulated reference signal;

[0114] Indicative information based on PBCH scrambled sequences;

[0115] Indication information based on the PBCH indication information field;

[0116] Indication information based on SSB indexes or index groups.

[0117] In one embodiment, the configuration information includes at least one of the following:

[0118] The combination of common channels in the common channel block; the configuration parameters of the time-frequency resources of the common channels in the common channel block.

[0119] In one embodiment, the configuration parameters of the time-frequency resources include at least one of the following: time resource parameters; frequency resource parameters; channel association rules;

[0120] The time resource parameters include at least one of the following: the time interval between the reference channel; the time interval between adjacent channels; the rules for setting the time interval; the start symbol and duration of the channel;

[0121] The frequency resource parameters include at least one of the following: frequency resource units per common channel; initial subcarrier spacing (SCS) and frequency domain length; SCS size;

[0122] The channel association rules include: each channel resource is bound to a corresponding SSB index, and each SSB supports independent time resource parameters and frequency resource parameters.

[0123] The common channel block transmission device proposed in this embodiment belongs to the same inventive concept as the common channel block transmission method proposed in the above embodiments. Technical details not described in detail in this embodiment can be found in any of the above embodiments. Furthermore, this embodiment has the same beneficial effects as the common channel block transmission method.

[0124] This application also provides a communication node. Figure 7 This is a schematic diagram of the hardware structure of a communication node provided in one embodiment, such as... Figure 7 As shown, the communication node provided in this application includes a processor 310 and a memory 320; the processor 310 in the communication node can be one or more. Figure 7 Taking a processor 310 as an example; the memory 320 is configured to store one or more programs; the one or more programs are executed by the one or more processors 310, causing the one or more processors 310 to implement the common channel block transmission method as described in the embodiments of this application.

[0125] The communication node also includes: a communication device 330, an input device 340, and an output device 350.

[0126] The processor 310, memory 320, communication device 330, input device 340, and output device 350 in the communication node can be connected via a bus or other means. Figure 7 Taking the example of a connection between China and Israel via a bus.

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

[0128] The communication device 330 may include a receiver and a transmitter. The communication device 330 is configured to perform information transmission and reception communication under the control of the processor 310.

[0129] The memory 320, as a computer-readable storage medium, can be configured to store software programs, computer-executable programs, and modules, such as program instructions / modules corresponding to the common channel block transmission method described in the embodiments of this application. The memory 320 may include a program storage area and a data storage area, wherein the program storage area may store the operating system and at least one application program required for a function; the data storage area may store data created based on the use of the communication node, etc. Furthermore, the memory 320 may include high-speed random access memory and may also include non-volatile memory, such as at least one disk storage device, flash memory device, or other non-volatile solid-state storage device. In some instances, the memory 320 may further include memory remotely located relative to the processor 310, and these remote memories can be connected to the communication node via a network. Examples of such networks include, but are not limited to, the Internet, enterprise intranets, local area networks, mobile communication networks, and combinations thereof.

[0130] This application also provides a storage medium storing a computer program, which, when executed by a processor, implements the transmission method of any of the common channel blocks described in this application.

[0131] This application also provides a computer program product, including a computer program / instruction, which, when executed by a processor, implements the transmission method of any of the common channel blocks described in this application.

[0132] The computer storage medium in this application embodiment can be any combination of one or more computer-readable media. The computer-readable medium can be a computer-readable signal medium or a computer-readable storage medium. For example, a computer-readable storage medium can be, but is not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of computer-readable storage media (a non-exhaustive list) include: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), flash memory, optical fiber, portable CD-ROM, optical storage device, magnetic storage device, or any suitable combination thereof. The computer-readable storage medium can be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, apparatus, or device.

[0133] Computer-readable signal media may include data signals propagated in baseband or as part of a carrier wave, carrying computer-readable program code. Such propagated data signals may take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. Computer-readable signal media may also be any computer-readable medium other than computer-readable storage media, which can send, propagate, or transmit programs for use by or in connection with an instruction execution system, apparatus, or device.

[0134] Program code contained on a computer-readable medium may be transmitted using any suitable medium, including but not limited to: wireless, wire, optical fiber, radio frequency (RF), etc., or any suitable combination thereof.

[0135] Computer program code for performing the operations of this application can be written in one or more programming languages ​​or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, and C++, as well as conventional procedural programming languages ​​such as "C" or similar programming languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer can be connected to the user's computer via any type of network, including a local area network (LAN) or a wide area network (WAN), or it can be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0136] This application also provides a computer program product, including a computer program / instructions, which, when executed by a processor, implement the common channel block transmission method as described in any of the above embodiments.

[0137] The above description is merely an exemplary embodiment of this application and is not intended to limit the scope of protection of this application.

[0138] Those skilled in the art will understand that the term user terminal encompasses any suitable type of wireless user equipment, such as mobile phones, portable data processing portable web browsers, or vehicle-mounted mobile stations.

[0139] Generally, the various embodiments of this application can be implemented in hardware or dedicated circuitry, software, logic, or any combination thereof. For example, some aspects can be implemented in hardware, while others can be implemented in firmware or software that can be executed by a controller, microprocessor, or other computing device, although this application is not limited thereto.

[0140] Embodiments of this application can be implemented by executing computer program instructions through the data processor of a mobile device, for example, in a processor entity, or through hardware, or through a combination of software and hardware. The computer program instructions can be assembly instructions, Instruction Set Architecture (ISA) instructions, machine instructions, machine-dependent instructions, microcode, firmware instructions, status setting data, or source code or object code written in any combination of one or more programming languages.

[0141] Any block diagram of logical flow in the accompanying drawings of this application may represent program steps, or may represent interconnected logic circuits, modules, and functions, or may represent a combination of program steps and logic circuits, modules, and functions. The computer program may be stored in memory. The memory may be of any type suitable to the local technical environment and may be implemented using any suitable data storage technology, such as, but not limited to, read-only memory (ROM), random access memory (RAM), optical storage devices and systems (Digital Video Disc (DVD) or Compact Disk (CD), etc.). Computer-readable media may include non-transitory storage media. The data processor may be of any type suitable to the local technical environment, such as, but not limited to, general-purpose computers, special-purpose computers, microprocessors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), and processors based on multi-core processor architectures.

[0142] A detailed description of exemplary embodiments of this application has been provided above through exemplary and non-limiting examples. However, various modifications and adjustments to the above embodiments will be apparent to those skilled in the art when considered in conjunction with the accompanying drawings and claims, without departing from the scope of this application. Therefore, the proper scope of this application will be determined by the claims.

Claims

1. A method for transmitting a common channel block, characterized in that, include: Determine the format and configuration information of the common channel block; The common channel block is transmitted according to the aforementioned format and configuration information.

2. The method according to claim 1, characterized in that, The common channel block includes at least one of the following common channels: Synchronization signal SS includes at least one of primary synchronization signal and secondary synchronization signal; The synchronization signal block (SSB) includes the primary synchronization signal, the secondary synchronization signal, and the physical broadcast channel (PBCH). First system information, including SIB1; Second system information, including SIBx; Random Access Channel (RACH) resources for common channel blocks; Physical downlink shared channel (PDSCH) resources.

3. The method according to claim 1, characterized in that, The form includes at least one of the following: Combination of common channels on contiguous resources; combination of common channels on discontinuous resources.

4. The method according to claim 3, characterized in that, The common channel block includes at least one SSB; The number of times an SSB is repeated is indicated by the main information block (MIB).

5. The method according to claim 3, characterized in that, Some symbols in the common channel block are occupied by the control channel; the control channel is used to carry scheduling information for channels in the non-common channel block. The control channel includes at least one of the following: control resource set CORESET, search space timing, physical downlink control channel PDCCH, and PDCCH candidate.

6. The method according to claim 3, characterized in that, The SSB in the common channel block serves as the quasi-co-address reference signal for the channels in the non-common channel block.

7. The method according to claim 1, characterized in that, The form of the common channel block is determined, including at least one of the following: The form of the common channel block is determined based on the type of network access scenario; The form of the common channel block is determined based on the frequency resources of the received common channel. The form of the common channel block is determined based on the indication information carried in the synchronization signal or the synchronization signal block.

8. The method according to claim 7, characterized in that, The indication information includes at least one of the following: Indicative information based on SSB sequences; Indication information based on the DMRS sequence of the PBCH demodulated reference signal; Indicative information based on PBCH scrambled sequences; Indication information based on the PBCH indication information field; Indication information based on SSB indexes or index groups.

9. The method according to claim 1, characterized in that, The configuration information includes at least one of the following: The combination of common channels in the common channel block; the configuration parameters of the time-frequency resources of the common channels in the common channel block.

10. The method according to claim 9, characterized in that, The configuration parameters of the time-frequency resources include at least one of the following: time resource parameters; frequency resource parameters; channel association rules; The time resource parameters include at least one of the following: the time interval between the reference channel; the time interval between adjacent channels; the rules for setting the time interval; the start symbol and duration of the channel; The frequency resource parameters include at least one of the following: frequency resource units; initial subcarrier spacing (SCS) and frequency domain length; SCS size; The channel association rules include: each channel resource is bound to a corresponding SSB index, and each SSB supports independent time resource parameters and frequency resource parameters.

11. A communication node, characterized in that, include: Memory, and one or more processors; The memory is configured to store one or more programs; When the one or more programs are executed by the one or more processors, the one or more processors implement the method for transmitting common channel blocks as described in any one of claims 1-10.

12. A computer-readable storage medium having a computer program stored thereon, characterized in that, When executed by the processor, this program implements the method for transmitting common channel blocks as described in any one of claims 1-10.

Images