Downlink transmission methods, communication node and storage medium
By introducing a retransmission indication mechanism in the PBCH or MIB, the problem of user equipment being unable to receive the common downlink channel in deep coverage scenarios is solved, thereby improving the signal reception success rate and coverage enhancement during the initial access process.
Patent Information
- Application Number
- PCT/CN2026/083827
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2025-05-08
- Filing Date
- 2026-03-17
- Publication Date
- 2026-11-12
AI Technical Summary
In scenarios with deep coverage of 5G and 6G wireless communication systems, user equipment cannot correctly receive the common downlink channel, especially in non-terrestrial networks and marine communications. Due to high path loss, existing technologies cannot provide repeated transmission configurations for the common PDCCH and PDSCH before the user enters the connected state, resulting in signal reception failure during the initial access process.
By introducing a new indication mechanism in the PBCH or MIB, the repeated transmission of common downlink channels is configured, including the repeated transmission of Type0-PDCCH CSS and SIB1 PDSCH. The idle bit fields in the PBCH or MIB indicate the repeated transmission, enabling connected users to be aware of configuration updates and correctly receive downlink channels in case of mismatch.
It improves the downlink channel reception success rate during the initial access process of user equipment, ensures that connected users can correctly receive the common PDCCH and PDSCH, and enhances communication coverage capabilities in deep coverage scenarios.
Smart Images

Figure CN2026083827_12112026_PF_FP_ABST
Abstract
Description
Downlink transmission method, communication node and storage medium Technical Field
[0001] This application relates to the field of wireless communication technology, such as downlink transmission methods, communication nodes, and storage media. Background Technology
[0002] Future communication systems need to be able to be applied to more scenarios, including deep coverage scenarios. For example, 5G and 6G wireless communication systems need to support scenarios such as non-terrestrial networks (NTN) and maritime communications. In these scenarios, due to the large distance between users and network nodes, the path loss during signal transmission will be much greater than in traditional terrestrial communication networks. Therefore, it is necessary to consider enhancing the coverage capability of downlink physical channels (e.g., Physical Downlink Control Channel (PDCCH) and Physical Downlink Shared Channel (PDSCH)) to ensure that users can successfully receive downlink signals.
[0003] For example, a network node configures a search space (SS) for a user to indicate when the user should detect the PDCCH. The network node can configure two search spaces (SSs) for the user, and configure the same search space linking identifier (SearchSpaceLinkingId) in both SSs, thus considering the two SSs as associated. Then, the network node can transmit duplicate PDCCHs in the two associated SSs. The user can improve PDCCH detection performance by detecting the duplicate PDCCHs. However, the above configuration of associated SSs can only be performed after the user enters the connected state. PDCCH duplication based on associated SSs is not applicable to the common PDCCH CSS, nor can it be used for SIB scheduling, initial access scheduling, paging scheduling, and SDT scheduling. In these scenarios, the UE cannot correctly receive the common downlink channel.
[0004] For example, PDSCH repetition (or PDSCH aggregation) is already supported to improve PDSCH coverage performance. However, PDSCH repetition configuration can only be performed after the UE enters connected state. Therefore, PDSCH repetition is not applicable to common PDSCH or PDSCH before receiving UE-specific PDSCH configuration, causing the UE to be unable to correctly receive common downlink channels. Summary of the Invention
[0005] This application provides a downlink transmission method, a communication node, and a storage medium.
[0006] This application provides a downlink transmission method applied to a first communication node, comprising: receiving repetitive transmission configuration information of a common downlink channel; and receiving the common downlink channel according to the repetitive transmission configuration information.
[0007] This application also provides a downlink transmission method applied to a second communication node, comprising: sending repetitive transmission configuration information for a common downlink channel; and sending the common downlink channel according to the repetitive transmission configuration information.
[0008] 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 downlink transmission method described above.
[0009] This application also provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the downlink transmission method described above. Attached Figure Description
[0010] Figure 1 is a schematic diagram of an NTN architecture provided in one embodiment;
[0011] Figure 2 is a flowchart of a downlink transmission method provided in an embodiment;
[0012] Figure 3 is a schematic diagram of a TDD cycle pattern provided in one embodiment;
[0013] Figure 4 is a schematic diagram of unnecessary discarding in a TDD mode provided by an embodiment;
[0014] Figure 5 is a flowchart of a downlink transmission method provided in an embodiment;
[0015] Figure 6 is a schematic diagram of a downlink transmission device provided in one embodiment;
[0016] Figure 7 is a schematic diagram of a downlink transmission device according to an embodiment;
[0017] Figure 8 is a schematic diagram of the hardware structure of a communication node according to an embodiment. Detailed Implementation
[0018] Unless otherwise specified, the embodiments and features described in this application may be combined arbitrarily with each other.
[0019] Traditional terrestrial networks have already enhanced the downlink physical channel to some extent, but this is mainly applicable to users in the connected state and not to common channels in idle state or initial access scenarios. To configure coverage enhancements for common channels before user access, a Physical Broadcast Channel (PBCH) may be used. In a communication system, users in the connected state are unaware of PBCH updates. This application's embodiments consider how to enable connected users to perceive configuration updates, or how to ensure correct downlink channel reception even in the event of mismatch. Furthermore, for the repeated transmission of Message 4 (Msg4 PDSCH) during the initial access process, users have the opportunity to report corresponding capabilities or requests. This application's embodiments consider the triggering conditions for users to report capabilities or requests, as well as the conditions for deciding whether to perform repeated transmissions, to save signaling and resource consumption.
[0020] Furthermore, when downlink coverage is enhanced, time-domain repetitive transmissions are typically used. In Time Division Duplex (TDD) mode, when downlink transmissions overlap with non-downlink times, the corresponding transmissions may be delayed. Therefore, periodic downlink channels or search spaces may overlap due to delays. This application's embodiments consider how to handle the aforementioned overlap problem.
[0021] Figure 1 is a schematic diagram of an NTN architecture provided in one embodiment. As shown in Figure 1, in the NTN communication system, the link between the UE and the satellite is a service link, and the link between the access network equipment (such as a base station or gateway station) and the satellite is a feeder link, which is common to all UEs in the same cell (UE1 and UEx shown in Figure 1).
[0022] Network nodes can configure Service Controllers (SSs) for users to instruct them on when to detect the PDCCH. Depending on the purpose of the PDCCH, there are various types of SSs; Table 1 shows information on different types of SSs.
[0023] Table 1 Different types of SS
[0024] For SS0 (SearchSpace Zero), the network node will indicate an index (4 bits). The UE determines the corresponding table (which is predefined in the protocol) based on parameters such as the control resource set (CORESET) multiplexing mode, carrier frequency, and / or subcarrier space, and then determines the time domain resource corresponding to SS0 through the index indicated by the network node.
[0025] For SSs other than SS0, configuration can be performed via Radio Resource Control (RRC) signaling. The configuration information includes at least one of the following: SSID (Search Space ID), CORESET ID (control Resource Set ID), Monitoring Slot Periodicity and Offset, Duration of each monitoring event, Monitoring Symbols Within Slot, Number of PDCCH Candidates / Number of Monitorings (nrofCandidates) per aggregation level, SS type (searchSpaceType, e.g., public SS or UE-specific SS), SS group (searchSpaceGroupIdList), and associated SS (SearchSpaceLinkingId).
[0026] The protocol supports PDCCH repetition to improve PDCCH coverage performance. For example, if a network node configures two search spaces (SSs) for a user, and both SSs are configured with the same searchSpaceLinkingId, then the two SSs can be considered associated. The network node can then transmit duplicate PDCCHs between the associated SSs. Users can improve PDCCH detection performance by detecting duplicate PDCCH transmissions.
[0027] However, the above configuration of associated SSs can only be performed after the user enters connected state. Furthermore, the following SSs do not support association with other SSs: SS set 0, searchSpaceSIB1, searchSpaceOtherSystemInformation, pagingSearchSpace, ra-SearchSpace, searchSpaceMCCH, searchSpaceMTCH, peiSearchSpace, and sdt-SearchSpace. Therefore, PDCCH duplication based on associated SSs is not applicable to common PDCCH CSSs such as Type0-PDCCH Common Search Space (CSS), Type0A-PDCCH CSS, Type0B-PDCCH CSS, Type1-PDCCH CSS, Type1A-PDCCH CSS, Type2-PDCCH CSS, and Type2A-PDCCH CSS. In other words, it cannot be used for System Information Block (SIB) scheduling, scheduling during initial access, paging scheduling, and Small Data Transmission (SDT) scheduling.
[0028] Furthermore, PDCCH repetition only supports repetitive transmission within a time slot. For the two associated SSs, the detection timing and PDCCH candidates must have a one-to-one mapping relationship. The two associated PDCCH candidates must have the same aggregation level, coded bits, and Downlink Control Information (DCI) payload. For the two associated PDCCH candidates, the UE can report whether to perform two or three blind detections, or count them as two or three PDCCH candidates.
[0029] The protocol supports PDSCH repetition (or PDSCH aggregation) to improve PDSCH coverage performance. However, PDSCH repetition configuration can only be performed after the UE enters connected state. Therefore, PDSCH repetition is not applicable to public PDSCH or PDSCH configured before receiving UE-specific PDSCH, such as the PDSCH corresponding to SIB, Msg2, MsgB, Msg4, and paging PDSCH.
[0030] A user typically goes through the following process when accessing a network:
[0031] The system searches for the SSB and demodulates the PBCH to obtain the Master Information Block (MIB) information. The MIB contains the relevant configuration for the PDCCH of SIB1, namely PDCCH-Config SIB1, which configures SearchSpaceZero and ControlResourceSetZero. Based on the information indicated by the MIB, it detects the Type 0-PDCCH and the scheduled SIB1. SIB1 contains basic system messages, as well as configurations for other common channels, such as Type 0A-PDCCH CSS and Type 1-PDCCH CSS.
[0032] After obtaining the necessary system information (such as SIB1 and SIB19), a random access procedure is initiated. This procedure may include the user sending Msg1 (random access preamble), receiving Msg2 (random access response RAR message), sending Msg3 (containing user identification code, etc.), and receiving Msg4 (contention resolution message). Alternatively, the procedure may include the user sending MsgA (Msg A Physical Random Access Channel (PRACH) and MsgA Physical Uplink Shared Channel (PUSCH), corresponding to the random access preamble and a message containing the user identification code), and receiving MsgB (MsgB PDCCH and MsgB PDSCH, corresponding to control information and the random access response message; MsgB may contain contention resolution or backoff information). Type 1-PDCCH CSS is used to detect the PDCCH during this process.
[0033] After the random access procedure is completed, the network node can configure dedicated resources for the user, such as a Universal Serial Interface (USS) and a dedicated PDSCH configuration. The USS can then be used to schedule user-specific data and transmit it according to the configuration of the dedicated PDSCH.
[0034] As mentioned earlier, before the UE enters the connected state or receives UE-specific configuration, PDCCH and PDSCH (mainly common PDCCH and common PDSCH) do not support repeated transmission. Furthermore, during initial access, especially when detecting the PDSCH corresponding to Type 0-PDCCH CSS and SIB1, the signaling that the UE can receive is very limited. Therefore, repeated transmission of the common downlink channel cannot be simply configured through dedicated RRC signaling, requiring the introduction of new indication or configuration mechanisms.
[0035] The methods described in this application embodiment may be applied to various networks, including but not limited to NR, NB-IoT, eMTC, or 6G networks. The various channels or signals described in this application embodiment may also refer to channels in other networks that have the same function but different names or formats. For example, PDSCH may also refer to the Narrowband Physical Broadcast Channel (NPDSCH), etc. PDCCH may also refer to the Narrowband Physical Downlink Control Channel (NPDCCH), MPDCCH, etc. PUSCH may also refer to NPUSCH, etc. PRACH may also refer to NPRACH, etc. PBCH may also refer to NPBCH, etc. MIB may also refer to MIB-NB, etc. SIBx may also refer to SIBx-NB, etc.
[0036] In the embodiments of this application, the configuration, signaling, or indication may include at least one of the following: MIB, PBCH, SIB1, SIBx (x>=1), RRC signaling, MAC CE, MAC header or MAC subheader, DCI signaling, etc. Specific indication methods may include: defining new or dedicated bit fields for indication; reinterpreting or reusing existing bit fields for indication; reinterpreting or reusing one or more states or code points of existing bit fields for indication; introducing new information elements (IEs) for indication (such as indicating a specific value, or enumerating multiple candidate values and indicating a value from multiple candidate values); reinterpreting or reusing one or more states or candidate values of existing information elements for indication; introducing new MAC CEs and indicating them through MAC CEs; introducing new MAC subheaders and indicating them through code points of the Logical Channel Identifier (LCID); using scrambling code-related information for indication (such as Radio Network Temporary Identity (RNTI), code sequence, root of the generation code, seed of the generation code, etc.); modifying tables in standard protocols, etc. Modifying tables in the standard protocol may refer to adding extra rows or columns to existing tables to indicate additional information (e.g., adding an extra column to the Time Domain Resource Assignment (TDRA) table or Demodulation Reference Signal (DMRS) table to indicate retransmission or code division multiplexing configuration), reinterpreting or reusing some information in existing tables (e.g., modifying the contents of certain rows in the TDRA or DMRS table to indicate retransmission or code division multiplexing configuration), or introducing new tables (e.g., introducing a new TDRA or DMRS table containing retransmission or code division multiplexing configuration).The existing bit fields may include, but are not limited to, the following bit fields: resource allocation, frequency domain resource allocation, time domain resource allocation, frequency hopping flag, modulation and coding scheme, new data indication, redundancy version, number of Hybrid Automatic Repeat reQuest (HARQ) processes, transmit power control command, channel access type, cyclic prefix extension, uplink / supplementary uplink indication, virtual resource block-physical resource block mapping, downlink allocation index, PUCCH resource indication, PDSCH to HARQ feedback timing indication, short message indication, short message, transport block scaling, tracking reference signal valid indication, system information indication, least significant bit of system frame, repetition count, number of transport blocks (TB) scheduled for unicast, subcarrier indication, resource reservation, scheduling delay, DCI subframe repetition count, reserved or idle bit fields. Reinterpreting or reusing existing bit fields may include reinterpreting the indication content of existing bit fields to indicate target information; or it may include reducing existing bit fields and using empty bits to indicate target information.
[0037] When indicating via DCI, such as introducing a new / dedicated bit field or reinterpreting / reusing an existing bit field, corresponding enable or activate signaling may be introduced, for example, via MIB, PBCH, SIB, RRC, and / or MAC CE. Alternatively, when the network side configures multiple parameters via higher-layer signaling (e.g., SIB1, SIBx, and / or RRC), DCI may be used to further indicate one of the parameters. A new / dedicated bit field or a reinterpretation / reuse of an existing bit field will only be included in the DCI when enabling or activating / configuring multiple parameters on the network side. The existing bit fields may include, but are not limited to:
[0038] When indications are made via MAC CE, MAC header, or subheader, such as introducing new or dedicated bit fields or reinterpreting / multiplexing existing bit fields, corresponding enable or activate signaling may be introduced, for example, via MIB, PBCH, SIB, and / or RRC. Alternatively, when the network side configures multiple parameters via higher-layer signaling (e.g., SIB1, SIBx, and / or RRC), MAC CE, MAC header, or subheader may be used to further indicate one of the parameters. New / dedicated bit fields or reinterpretations / multiplexing of existing bit fields are only included in the MAC CE, MAC header, or subheader when enabling or activating / configuring multiple parameters on the network side.
[0039] For enable or activation indications, a corresponding information element (IE) may be introduced. When the network side configures / indicates this information element, it indicates enable or activation; when the information element is not configured or indicated, it indicates disable, de-enable, or deactivated. Alternatively, for enable or activation indications, new bit fields or multiplexing or reinterpreting idle or reserved bits in existing signaling may be introduced, such as MIB, PBCH, SIB1, and / or SIBx. When the bit indicates "1", it indicates enable or activation; "0" indicates disable, de-enable, or deactivated; and vice versa.
[0040] 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.
[0041] 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.
[0042] Figure 2 is a flowchart of a downlink transmission method provided in one embodiment. This method can be applied to a first communication node, which can be a UE or a receiver of a receiver that repeatedly transmits configuration information and a common downlink channel. As shown in Figure 2, the method provided in this embodiment includes steps 110 and 120.
[0043] In 110, the retransmission configuration information of the common downlink channel is received.
[0044] In step 120, the common downlink channel is received according to the repeated transmission configuration information.
[0045] In one example, prior to detecting SIB1, the user can only receive configurations from the PBCH or MIB. Therefore, duplicate transmissions of the Type0-PDCCH CSS can only be indicated or configured via the PBCH or MIB. Similarly, duplicate transmissions of the SIB1 PDSCH may also be indicated or configured via the PBCH or MIB. To conserve signaling, duplicate transmissions of other common PDCCHs or common PDSCHs may also be indicated or configured via the PBCH or MIB. For example, the network side may indicate at least one of the following via idle or reserved bits in the PBCH or MIB: whether Type0-PDCCH CSS uses, enables, or activates repeat transmission, and / or the number of repeat transmissions; whether SIB1 PDSCH uses, enables, or activates repeat transmission, and / or the number of repeat transmissions; whether Type0-PDCCH CSS and SIB1 PDSCH use, enable, or activate repeat transmission, and / or the number of repeat transmissions; whether Type0-PDCCH CSS configured in the MIB (via PDCCH-ConfigSIB1) uses, enables, or activates repeat transmission, and / or the number of repeat transmissions; whether Type0-PDCCH CSS and SIB1 PDSCH configured in the MIB (via PDCCH-ConfigSIB1) use, enable, or activate repeat transmission, and / or the number of repeat transmissions; whether Type0-PDCCH CSS on SS0 uses, enables, or activates repeat transmission, and / or the number of repeat transmissions; and whether Type0-PDCCH CSS and SIB1 PDSCH on SS0 use, enable, or activate repeat transmission, and / or the number of repeat transmissions. Whether PDSCH uses, enables, or activates repeat transmission, and / or the number of repeat transmissions; whether public PDCCH uses, enables, or activates repeat transmission, and / or the number of repeat transmissions; whether PDCCH on SS0 uses, enables, or activates repeat transmission, and / or the number of repeat transmissions.
[0046] However, when a user is in connected state, the PBCH or MIB is typically not detected. For example, in the NR protocol, the PBCH or MIB is only detected when a connected user obtains system information during a specified timer (such as T311) (usually during RRC reconstruction). In other cases, a connected user will detect SIB1 or SIBx (x>1) when obtaining system information, but will not detect the PBCH or MIB. Since RRC reconstruction is triggered by the UE, the network cannot actively trigger the connected UE to obtain the PBCH or MIB; that is, the connected UE cannot know about changes in the configuration of the PBCH or MIB. Considering that users, network nodes, or satellites may be mobile, and coverage performance may change over time, meaning the retransmission configuration of the public PDCCH or public PDSCH may also change over time, how connected users can cope with changes in the retransmission configuration of the public PDCCH or public PDSCH needs to be addressed. When the configuration in the PBCH or MIB is updated, in order to enable connected users to correctly receive the Type0-PDCCH CSS, the update of the PBCH or MIB can be flexibly indicated by repeatedly transmitting the configuration information. This allows connected users to be aware of the configuration update and can also instruct the UE to adopt an appropriate method to correctly receive the downlink channel in the event of mismatch.
[0047] In one embodiment, the common downlink channel includes at least one of a common PDCCH and a common PDSCH; the common PDCCH includes at least one of the following: PDCCH CSS, a PDCCH using cell-level PDCCH parameters; the common PDSCH includes at least one of the following: a PDSCH before the second communication node acquires the proprietary PDSCH configuration, a PDSCH using cell-level PDSCH parameters.
[0048] In one example, the common PDCCH may refer to at least one of the PDCCH CSS, or a PDCCH using cell-level PDCCH parameters (PDCCH-ConfigCommon). The common PDCCH may include at least one of the following: the PDCCH corresponding to the Type0-PDCCH CSS or Type0-PDCCH CSS, the PDCCH corresponding to the Type0A-PDCCH CSS or Type0A-PDCCH CSS, the PDCCH corresponding to the Type0B-PDCCH CSS or Type0B-PDCCH CSS, the PDCCH corresponding to the Type1-PDCCH CSS or Type1-PDCCH CSS, the PDCCH corresponding to the Type1A-PDCCH CSS or Type1A-PDCCH CSS, the PDCCH corresponding to the Type2-PDCCH CSS or Type2-PDCCH CSS, the PDCCH corresponding to the Type2A-PDCCH CSS or Type2A-PDCCH CSS, or the Type3-PDCCH CSS or Type3-PDCCH. The PDCCH corresponding to the CSS, SS0 or the PDCCH corresponding to SS0, the PDCCH corresponding to the SS configured in searchSpaceSIB1, the PDCCH corresponding to the SS configured in searchSpaceOtherSystemInformation, the PDCCH corresponding to the SS configured in pagingSearchSpace, the PDCCH corresponding to the SS configured in ra-SearchSpace, the PDCCH corresponding to the SS configured in searchSpaceMCCH, the PDCCH corresponding to the SS configured in searchSpaceMTCH, the PDCCH corresponding to the SS configured in searchSpaceMulticastMCCH, the PDCCH corresponding to the SS configured in searchSpaceMulticastMTCH, the PDCCH corresponding to the SS configured in peiSearchSpace, and the PDCCH corresponding to the SS configured in sdt-SearchSpace. Here, SS0 refers to search space 0, which may include searchSpaceZero configured in MIB (e.g., via PDCCH-ConfigSIB1), and may include searchSpaceZero configured in SIB1, SIBx, or RRC (e.g., via PDCCH-ConfigCommon). For simplicity, the PDCCH CSS mentioned in this application embodiment may refer to the PDCCH corresponding to that CSS.
[0049] Public PDSCH may refer to the PDSCH before the UE obtains a proprietary PDSCH configuration (such as PDSCH-Config), or the PDSCH using cell-level PDSCH parameters (PDSCH-ConfigCommon). The public PDSCH may include at least one of the following: SIB1 PDSCH, SIBx PDSCH (x>1), Msg2 PDSCH, Msg4 PDSCH, MsgB PDSCH, paging PDSCH, PDSCH scheduled by the public PDCCH (public PDCCH as described above), PDSCH corresponding to the System Information RNTI (SI-RNTI) or PDSCH scheduled by the DCI of SI-RNTI scrambled Cyclic Redundancy Check, PDSCH corresponding to the Random Access (RA) RNTI (RA-RNTI) or PDSCH scheduled by the DCI of RA-RNTI scrambled CRC, PDSCH corresponding to the Temporary RNTI (Temporary C-RNTI, TC-RNTI) or PDSCH scheduled by the DCI of TC-RNTI scrambled CRC, PDSCH corresponding to MsgB-RNTI or PDSCH scheduled by the DCI of MsgB-RNTI scrambled CRC, and paging PDSCH. The PDSCH corresponding to RNTI (P-RNTI) or the PDSCH of DCI scheduling for P-RNTI scrambled CRC, the PDSCH corresponding to PEI-RNTI or the PDSCH of DCI scheduling for PEI-RNTI scrambled CRC, the PDSCH corresponding to MCCH-RNTI or the PDSCH of DCI scheduling for MCCH-RNTI scrambled CRC, the PDSCH corresponding to G-RNTI or the PDSCH of DCI scheduling for G-RNTI scrambled CRC, the PDSCH corresponding to C-RNTI / CS-RNTI before the proprietary configuration, or the PDSCH of DCI scheduling for C-RNTI / CS-RNTI scrambled CRC before the proprietary configuration.
[0050] In one embodiment, the retransmission configuration information includes at least one of the following: enabling retransmission, activating retransmission, the number of retransmissions, resource allocation for retransmission (e.g., the offset or interval of time-domain and / or frequency-domain resources occupied by retransmissions relative to the time-domain and / or frequency-domain resources of the initial transmission), associated search space, and associated identifier of the search space.
[0051] In one embodiment, the retransmission configuration information is received via a first signaling, which includes at least one of the following: PBCH, MIB, SIB, and dedicated RRC signaling.
[0052] In one embodiment, when the first signaling is at least one of PBCH and MIB, the retransmission configuration information is also received via a second signaling, the second signaling including at least one of SIB and dedicated RRC signaling.
[0053] In this embodiment, the common channel retransmission indication configured in the PBCH and / or MIB can be additionally configured in the SIB (such as SIB1 and / or SIBx) and / or dedicated RRC signaling to ensure that the connected UE can know whether the configuration has been updated.
[0054] In this embodiment, the retransmission configuration information received via the second signaling is consistent with at least one of the following in the retransmission configuration information received via the first signaling: bit field; signaling; information element; indication method for retransmission configuration information; and interpretation method for bit field or information element.
[0055] As an example, when the indications or configurations in the PBCH or MIB are updated, the network side may also update the indications or configurations in SIB1, SIBx, or the dedicated RRC. Users in connected mode can determine whether the information indicated or configured via the PBCH or MIB has been updated by receiving the indications or configurations in SIB1, SIBx, or the dedicated RRC (i.e., retransmitted configuration information). The network side may implement measures to ensure that the indications or configurations in the PBCH or MIB are consistent with those in SIB1, SIBx, or the dedicated RRC. These indications or configurations may include retransmitted indications or configurations for the public PDCCH or public PDSCH as described above.
[0056] For example, the network side indicates or configures whether to use, enable, or activate repeated transmission in Type0-PDCCH CSS via idle or reserved bits in PBCH or MIB. Additionally, the network side also indicates or configures whether to use, enable, or activate repeated transmission in Type0-PDCCH CSS via SIB1, SIBx, or a dedicated RRC. Users in connected state determine whether to use, enable, or activate repeated transmission in Type0-PDCCH CSS based on the indication or configuration of SIB1, SIBx, or the dedicated RRC. More specifically, for example, 1 bit in PBCH may be used to indicate whether repeated transmission is enabled (e.g., this signaling, indication, field, or information could be named Type0PDCCHRepetition), where a value of "1" indicates that repeated transmission is enabled in Type0-PDCCH CSS, and a value of "0" indicates that it is disabled; or vice versa. Alternatively, an information element in PDCCH-ConfigCommon in SIB1, SIBx, or the dedicated RRC may be used to indicate whether repeated transmission is enabled. The information element may also be 1 bit, consistent with the indication or interpretation method of the 1 bit in PBCH (e.g., also indicating Type0PDCCHRepetition). The Type0-PDCCH CSS may refer to at least one of the following: Type0-PDCCH CSS on searchSpaceZero, Type0-PDCCH CSS on searchSpaceZero configured in PDCCH-ConfigSIB1, Type0-PDCCH CSS on searchSpaceZero configured in SIB1, Type0-PDCCH CSS on searchSpaceZero configured in SIBx, Type0-PDCCH CSS on searchSpaceZero configured in dedicated RRC, Type0-PDCCH CSS on searchSpaceZero configured in PDCCH-ConfigCommon, and Type0-PDCCH CSS on searchSpaceSIB1.
[0057] For example, the network side indicates or configures whether to use, enable, or activate repeated transmissions in the Type0-PDCCH CSS via idle / reserved bits in the PBCH or MIB. This indication or configuration may apply to the searchSpaceZero configured in the MIB (in PDCCH-ConfigSIB1). Simultaneously, the network side also indicates or configures whether to use, enable, or activate repeated transmissions in the Type0-PDCCH CSS via SIB1, SIBx, or a dedicated RRC. This indication or configuration may apply to the searchSpaceZero configured in SIB1, SIBx, or a dedicated RRC (in PDCCH-ConfigCommon). The signaling or information elements indicated or configured in the SIB1, SIBx, or dedicated RRC may be consistent with the indication or interpretation method in the PBCH or MIB (e.g., the 1-bit indication mentioned above). Alternatively, the signaling or information elements indicated or configured in the SIB1, SIBx, or dedicated RRC may be inconsistent with the indication or interpretation method in the PBCH or MIB. For example, a dedicated enable information element is defined. When this element is configured, it indicates that Type0-PDCCH CSS retransmission is enabled; otherwise, retransmission is disabled. Since a UE in connected mode may receive Type0-PDCCH CSS via searchSpaceZero configured in PDCCH-ConfigCommon, the user in connected mode determines whether Type0-PDCCH CSS (use, enable, or activate retransmission) based on the indication or configuration of SIB1, SIBx, or a dedicated RRC.
[0058] In one embodiment, receiving the common downlink channel according to the repetitive transmission configuration information includes: detecting the common downlink channel using a blind detection method according to the repetitive transmission configuration information, wherein the blind detection method includes at least one of the following: detecting a first common downlink channel candidate; detecting a second common downlink channel candidate; detecting a merged common downlink channel candidate, wherein the merged common downlink channel candidate is obtained by merging common downlink channel candidates from different time slots of the repetitive transmission.
[0059] In this embodiment, the indication or configuration for repeated transmission of the common downlink channel can be performed solely through the PBCH and / or MIB. Connected-state users cannot be aware of updates to the indication or configuration, but user behavior can be defined to ensure that connected-state users can correctly detect the target channel, guaranteeing that the UE can correctly detect the PDCCH both when repeated transmission is enabled and disabled. For example, when Type 0-PDCCH CSS repeated transmission is enabled, the user can be instructed to perform multiple blind detections, including but not limited to at least one of the following: detecting the first PDCCH candidate, detecting the second PDCCH candidate, merging multiple repeatedly transmitted PDCCH candidates, and performing detection. The indication or configuration may include the repeated transmission indication or configuration for the common PDCCH or common PDSCH as described above (i.e., [the indication or configuration]).
[0060] In one embodiment, the blind detection method includes: detecting common downlink channel candidates according to the latest received retransmission configuration information.
[0061] As an example, the network side can indicate or configure whether Type0-PDCCH CSS (repeated transmissions) are used, enabled, or activated via idle or reserved bits in the PBCH and / or MIB. If the user receives a PBCH or MIB configuration, Type0-PDCCH CSS detection will always be performed according to the most recently received configuration until the next PBCH and / or MIB is received, regardless of whether the indication or configuration in the PBCH or MIB is updated. Because the resources used when Type0-PDCCH CSS is repeated include the resources used when it is not repeated, if the PBCH or MIB configuration is updated from disabling Type0-PDCCH CSS repeated transmissions to enabling Type0-PDCCH CSS repeated transmissions, the user will still receive Type0-PDCCH CSS according to the disabling method. In this case, even if the network side performs repeated transmissions while the user only performs non-repeated receptions, the user can still correctly detect one transmission in the repeated transmissions. Users still have a chance to correctly detect Type0-PDCCH CSS, and there will be no performance degradation compared to users who do not support repeated transmission. If the PBCH or MIB configuration is updated from enabling Type0-PDCCH CSS repeated transmission to disabling it, users will still receive Type0-PDCCH CSS as if it were enabled. In this case, if the user's blind detection behavior includes detecting the first PDCCH candidate alone or the second PDCCH candidate alone, it is equivalent to including the Type0-PDCCH CSS detection behavior when "Type0-PDCCH CSS repeated transmission is disabled". Users still have a chance to correctly detect Type0-PDCCH CSS, and there will be no performance degradation compared to users who do not support repeated transmission.
[0062] In one embodiment, the first communication node does not anticipate any changes to the retransmission configuration information of the common downlink channel.
[0063] In this embodiment, instructions or configurations can be made solely through the PBCH or MIB, and the configurations in the PBCH or MIB will not be updated.
[0064] In one embodiment, the method further includes: receiving first indication information, the first indication information being used to instruct a first communication node in a connected state to acquire at least one of MIB and PBCH during the process of acquiring system information.
[0065] In this embodiment, a new mechanism is introduced that allows connected-state users to receive, detect, or acquire the PBCH and / or MIB. For example, the process of a connected-state user acquiring system information includes acquiring the MIB or PBCH. This function may be enabled or activated through network-side configuration. For example, the network side may indicate whether to enable or activate it through SIB or RRC signaling. When this function is enabled or activated, the connected-state user will acquire the MIB or PBCH when acquiring system information; otherwise, the connected-state user will not acquire the MIB or PBCH when acquiring system information, or the process of acquiring system information is the same as the protocol in related technologies.
[0066] In one embodiment, the method further includes: receiving second indication information, the second indication information being used to indicate to the first communication node in the connected state at least one of the following: whether the repeat transmission configuration has been updated, whether the repeat transmission configuration needs to be reacquired; and if the repeat transmission configuration has been updated or needs to be reacquired, acquiring the repeat transmission configuration starting from the start time of the next modification period.
[0067] As an example, the network side notifies connected users via short message whether the configuration of the MIB and / or PBCH (in which it is located) has changed or needs to be reacquired. The short message may refer to a PDCCH transmitted using P-RNTI scrambling. Idle or reserved bits in the short message are used to indicate whether the configuration of the MIB and / or PBCH (in which it is located) has changed or needs to be reacquired. For example, a bit indicating 1 indicates that the configuration of the MIB and / or PBCH (in which it is located) has changed or needs to be reacquired; otherwise, it indicates that the configuration of the MIB and / or PBCH (in which it is located) has not changed or does not need to be reacquired. When a user receives a short message indicating that the configuration of the MIB and / or PBCH (in which it is located) has changed or needs to be reacquired, the user begins receiving, detecting, or acquiring the PBCH or MIB from the start time of the next Modification Period. Alternatively, when a user receives a short message indicating that the configuration of the MIB and / or PBCH (in which it is located) has changed or needs to be reacquired, the user immediately receives, detects, or acquires the PBCH or MIB. This function may be enabled or activated through network-side configuration. For example, the network side may indicate whether to enable or activate via SIB or RRC signaling. When the function is activated, bits in the short message will be used to indicate whether the configuration in the MIB and / or PBCH has changed or needs to be reacquired.
[0068] The above scheme may also be applied to SIB1 PDSCH, by changing the Type0-PDCCH CSS to SIB1 PDSCH, and by changing PDCCH candidates to PDSCH repetition. Additionally, the above scheme may only apply to Type0-PDCCH CSS configured in the MIB (via PDCCH-ConfigSIB1) or Type0-PDCCH CSS on SS0. In this case, the above scheme can still be used, and restrictions can be added to the Type0-PDCCH CSS, such as Type0-PDCCH CSS configured in the MIB (via PDCCH-ConfigSIB1) or Type0-PDCCH CSS on SS0. Furthermore, the above scheme may apply to all common PDCCHs configured on SS0. In this case, the Type0-PDCCH CSS can be changed to a common PDCCH on SS0. Additionally, the repetition of Type0-PDCCH CSS and SIB1 PDSCH may be performed together. In this case, the above scheme may apply to both Type0-PDCCH CSS and SIB1 PDSCH simultaneously. The Type0-PDCCH CSS may also be changed to the Type0-PDCCH CSS configured in the MIB (via PDCCH-ConfigSIB1) or the Type0-PDCCH CSS on SS0 or the public PDCCH on SS0.
[0069] In one embodiment, the repeated transmission of the common PDCCH can be determined based on the configuration of SIB1.
[0070] As an example, after receiving SIB1, a user can determine the repeated transmission of the public PDCCH based on the configuration of SIB1. In this case, the search space association method described above can be considered. For example, the configuration of the associated SS can be extended to the search space corresponding to the public PDCCH. That is, the search space configuration in PDCCH-ConfigCommon also includes the search space association ID. Furthermore, the following search spaces can also be associated with other search spaces: SS set 0,searchSpaceSIB1,searchSpaceOtherSystemInformation,pagingSearchSpace,ra-SearchSpace,searchSpaceMCCH,searchSpaceMTCH,peiSearchSpace,sdt-SearchSpace. To ensure backward compatibility, i.e., compatibility with users who do not support repeated transmission of the public PDCCH, new signaling may be introduced to configure the association of the public search space. For example, the public search space configuration including the association ID will be configured through new SIB or RRC signaling (e.g., SearchSpaceExt-r17).
[0071] The configuration method for SS0 differs from that of other search spaces. SS0 can be configured via a bit field (e.g., searchSpaceZero) in either PDCCH-ConfigSIB1 or PDCCH-ConfigCommon. This bit field may be 4 bits long. The user retrieves the search space configuration from a predefined table in the standard protocol based on the value indicated by the bit field. Therefore, it is difficult to directly include the aforementioned association identifier (e.g., searchSpaceLinkingID) in the SS0 configuration. To address this, at least one of the following methods can be considered:
[0072] Method 1: Predefine an association identifier for SS0. When configuring other search spaces, if this association identifier is included, it is considered associated with SS0. For example, the predefined association identifier for SS0 can be 0, 1, N, or N+1, etc., where N is the maximum number of search space associations.
[0073] When the predefined association identifier x falls within the original configuration range of association identifiers (e.g., within the range of 0 to N-1), it may affect the traditional configuration. In this case, additional enable or disable configuration may be required to control whether the association identifier x is the association identifier of SS0. When the network side enables search space association or retransmission of SS0, the association identifier x is the association identifier of SS0; otherwise, the association identifier x is not the association identifier of SS0, or SS0 is not associated with other search spaces. The enable or disable configuration may be configured through the above configuration methods, such as through PBCH, MIB, SIB, or dedicated RRC. Alternatively, when retransmission is enabled for Type0-PDCCH CSS, search space association or retransmission of SS0 is enabled, or the predefined association identifier x is the association identifier of SS0.
[0074] When the predefined association identifier x is not within the configuration range of the original association identifier (e.g., N), it will not affect the traditional configuration. In this case, no additional enabling or disabling configuration may be required. When other search spaces contain the association identifier x, it is considered that the search space association or duplicate transmission of SS0 is enabled.
[0075] Method 2: Introduce a dedicated, new, or additional signaling, information element, or indication to indicate the association identifier of SS0. For example, introduce a new information element (e.g., searchSpaceZeroLinkingID) in SIB or dedicated RRC signaling (e.g., PDCCH-ConfigCommon) to indicate the association identifier. Other search space configurations are considered to be associated with SS0 if they contain this association identifier.
[0076] In traditional search space association, associated search spaces typically need to have the same period, offset, and duration. That is, associated search spaces need to occupy the same time slot. However, SS0 may correspond to different time slots for different SSB indices. Other search space configurations may not differentiate based on the SSB index. Therefore, when SS0 is associated with other search spaces, appropriate enhancements may be necessary.
[0077] In one example, for SS0, the duration of the search space might refer to: the set of detection slots corresponding to all SSB indices (of an SSB burst), or the time length from the first slot to the last slot among all detection slots corresponding to all SSB indices (of an SSB burst). The period of the search space might refer to: the period corresponding to the first slot among all detection slots corresponding to all SSB indices (of an SSB burst). The offset of the search space might refer to: the offset corresponding to the first slot among all detection slots corresponding to all SSB indices (of an SSB burst). The period, offset, and duration of the search space associated with SS0 may be determined according to the above definitions during configuration.
[0078] In one example, when detecting PDCCH candidates, a user may only detect them at the detection timing or time slot associated with the corresponding SSB. The corresponding SSB may refer to the SSB associated with the active TCI state, or the SSB quasi-co-located with a reference signal (such as CSI-RS) contained in the active TCI state. The associated detection timing or time slot may refer to the detection timing or time slot of SS0 determined according to the corresponding SSB index.
[0079] In one example, the search space associated with SS0 is determined based on the SS0 detection slot associated with the first SSB index. For example, the duration of the search space might refer to the duration of the detection slot corresponding to the first SSB index, or the time length from the first slot to the last slot. The period of the search space might refer to the period of the detection slot corresponding to the first SSB index. The offset of the search space might refer to the offset of the detection slot corresponding to the first SSB index. Additionally, an extra offset associated with the SSB index is introduced. For example, for SSB index x, an extra search space offset k is introduced. x Among them, k x This could be equal to the offset of the SS0 detection slot corresponding to SSB index x relative to the SS0 detection slot corresponding to the first SSB index. More specifically, for FR1 and multiplexing mode 1, for example, k x =x*M rounded down.
[0080] In one example, the search space associated with SS0 may need its detection slots to include all the detection slots of SS0. However, it may not be required to have the same duration or offset as SS0.
[0081] In one embodiment, the common downlink channel includes Msg4 PDSCH; the method further includes: determining whether to retransmit the Msg4 PDSCH based on at least one of the following: retransmission configuration information; retransmission capability reported by a first communication node; retransmission request reported by a first communication node.
[0082] In this embodiment, whether to repeat the Msg4 PDSCH may be determined based on the network-side configuration and the capabilities and / or requests reported by the UE. The UE may report the capability and / or request for repeated Msg4 PDSCH transmission via Msg3. For example, the LCID code point in the MAC subheader may indicate that the UE has the capability to repeat Msg4 PDSCH or requests repeated Msg4 PDSCH transmission. The network side may configure the number of repetitions of the Msg4 PDSCH or whether repeated Msg4 PDSCH transmission is enabled. The Msg4 PDSCH may include the PDSCH before the UE obtains the dedicated PDSCH configuration.
[0083] In one example, the network side configures the number of repetitions for Msg4 PDSCH via SIB. When the number of repetitions for Msg4 PDSCH is configured, it is considered that repetitive transmission of Msg4 PDSCH is enabled; otherwise, it is considered that Msg4 PDSCH is not enabled.
[0084] In one example, the network side configures the repetition count of Msg4 PDSCH via SIB. When SIB1 PDSCH is retransmitted, repetition of Msg4 PDSCH is considered enabled; otherwise, Msg4 PDSCH is considered disabled.
[0085] In one example, the network side configures the number of repetitions for Msg4 PDSCH via SIB. When the PDCCH that schedules Msg4 PDSCH is retransmitted, it is considered that repetition of Msg4 PDSCH is enabled; otherwise, it is considered that Msg4 PDSCH is not enabled.
[0086] In one example, the network side configures the number of repetitions of Msg4 PDSCH via SIB, as well as a reference signal received power threshold (e.g., RSRP threshold). When the reference signal received power is less than the threshold, Msg4 PDSCH repetition is considered enabled. Otherwise, Msg4 PDSCH is considered disabled.
[0087] In one example, the network side configures the number of repetitions of Msg4 PDSCH via SIB, and configures whether to enable repetition transmission of Msg4 PDSCH.
[0088] In one embodiment, the method further includes: reporting at least one of the repetitive transmission capability and the repetitive transmission request when reporting conditions are met; wherein the reporting conditions include at least one of the following: the repetition count of Msg4 PDSCH is configured; SIB1 PDSCH is repetitively transmitted; the PDCCH that schedules Msg4 PDSCH is repetitively transmitted; the reference signal received power is less than a configured threshold; and repetitive transmission of Msg4 PDSCH is enabled.
[0089] In this embodiment, to save signaling, the UE can report capabilities and / or requests when Msg4 PDSCH retransmission is possible. For example, a UE that supports Msg4 PDSCH retransmission can report capabilities and / or requests when at least one of the following conditions is met: when the number of Msg4 PDSCH retransmissions is configured; when SIB1 PDSCH retransmission is performed; when the PDCCH scheduling Msg4 PDSCH retransmission is performed; when the reference signal received power is less than a configured threshold; and when Msg4 PDSCH retransmission is enabled.
[0090] Reporting capability and / or request may refer to the use of the corresponding LCID code point. The code point may be an idle / reserved code point, or a reinterpretation of an existing code point (e.g., PUCCH repetition of Msg4 HARQ-ACK). The use of an idle / reserved code point or the reinterpretation of an existing code point may only be effective if the above conditions are met.
[0091] In one embodiment, the method further includes: determining the repeated transmission of the Msg4 PDSCH based on the number of repetitions of the Msg4 PDSCH indicated in the repeated transmission configuration information, provided that an activation condition is met; wherein the activation condition includes at least one of the following: the first communication node reports at least one of repeated transmission capability and repeated transmission request: repeated transmission of the SIB1 PDSCH; repeated transmission of the PDCCH that schedules the Msg4 PDSCH; the reference signal received power is less than a configured threshold; and repeated transmission of the Msg4 PDSCH is configured to be enabled or activated.
[0092] In this embodiment, the UE's reporting capability and / or request may be effective for a long time, while the configuration for Msg4 PDSCH retransmission may change. In response, the UE may determine Msg4 PDSCH retransmission based on at least one of the following criteria: If the UE reports Msg4 PDSCH retransmission capability and / or request, then Msg4 PDSCH retransmission is determined based on the configured / indicated number of Msg4 PDSCH retransmissions; If the UE reports Msg4 PDSCH retransmission capability and / or request, and at least one of the following conditions is met, then Msg4 PDSCH retransmission is determined based on the configured / indicated number of Msg4 PDSCH retransmissions: SIB1 PDSCH is retransmitted; the PDCCH scheduling Msg4 PDSCH is retransmitted; the reference signal received power is less than the configured threshold; Msg4 PDSCH retransmission is enabled or activated.
[0093] The protocol already supports PDCCH retransmission within a time slot. The mechanism is as described previously: the network node configures two SSs with the same association ID (searchSpaceLinkingId) for the user. Then, the network node can transmit repeated PDCCHs between the two associated SSs. The detection timing or PDCCH candidates for PDCCH retransmission between the two associated SSs are mapped one-to-one and must be within the same time slot; therefore, it is also called intra-time slot PDCCH retransmission. For the above intra-time slot PDCCH retransmission, depending on the UE's reporting capabilities, the two associated PDCCH candidates may be counted as two PDCCH candidates or three PDCCH candidates (i.e., two blind detections or three blind detections). This is mainly because intra-time slot PDCCH retransmission is primarily for multi-TRP transmission scenarios, where two TRPs may each correspond to one SS and transmit one PDCCH transmission respectively. In response, the UE may exhibit the following detection behaviors: two blind detections: detecting the first PDCCH candidate and the second PDCCH candidate; three blind detections: detecting the first PDCCH candidate, detecting the second PDCCH candidate, merging the two PDCCH candidates and performing detection.
[0094] Separate detection of the two PDCCH candidates allows the UE to receive the PDCCH candidate from the other TRP even when one TRP is blocked. This avoids performance degradation caused by detecting the signal of the blocked TRP. However, in coverage enhancement scenarios, such as satellite communications, the main purpose of PDCCH repetition is to compensate for path loss, primarily for single-TRP scenarios. In this case, it is usually not the case that the UE can only receive one PDCCH candidate, and it may be necessary to further reduce the number of blind detections, such as by performing only combined detection.
[0095] In addition to intra-slot PDCCH repetition, inter-slot PDCCH repetition can also be considered. For example, the network side configures an SS. Starting from the detection timing corresponding to the SS (e.g., the first time slot in the SS detection timing, or time slot n0 corresponding to SS0), PDCCH repetition occurs in multiple consecutive or non-consecutive time slots (e.g., time slots n0 and n0+1 corresponding to SS0). The repetitive PDCCH candidates may have the same aggregation level, coded bits, DCI payload, and CCE index. In the protocol, there may be a maximum number of blind detections (e.g., the number of detected PDCCH candidates, or the number of non-overlapping CCEs) limit for each time slot / extension / time slot group. If the maximum number of blind detections or the maximum number of detected PDCCH candidates is per time slot, how to calculate the number of blind detections or the number of PDCCH candidates during inter-slot PDCCH repetition detection needs to be considered separately. The following examples describe the UE's detection behavior when detecting inter-slot PDCCH repetition.
[0096] In one embodiment, the blind detection method includes: detecting merged common downlink channel candidates, wherein the merged common downlink channel candidates are obtained by merging common downlink channel candidates from different time slots of repeated transmissions; the merged common downlink channel candidates belong to the first time slot occupied by repeated transmissions, or the last time slot occupied by repeated transmissions, or each time slot used for merge detection.
[0097] In this embodiment, the UE performs a blind detection: merging PDCCH candidates from multiple repeatedly transmitted time slots and detecting them. Alternatively, the PDCCH candidates from multiple repeatedly transmitted time slots are treated as a single PDCCH candidate. This detection or PDCCH candidate may be counted in the first or last time slot. Alternatively, it may be counted in each time slot used for merging detection (e.g., each time slot is counted as one detection or one PDCCH candidate). This detection method can minimize the number of detections.
[0098] In one embodiment, the blind detection method includes: detecting a first common downlink channel candidate, the common downlink channel candidate belonging to a first time slot; detecting merged common downlink channel candidates, the merged common downlink channel candidates being obtained by merging common downlink channel candidates from different time slots of repeated transmission; the merged common downlink channel candidates belonging to the first time slot occupied by repeated transmission, or the last time slot occupied by repeated transmission, or each time slot used for merge detection.
[0099] In this embodiment, the UE performs two blind detections: detecting the first PDCCH candidate, which may be included in the first time slot; and merging PDCCH candidates from multiple time slots of repeated transmission and detecting them, which may be included in the first or last time slot (of the time slots occupied by the repeated PDCCH transmission). Alternatively, the PDCCH candidates from multiple time slots of repeated transmission can be regarded as two PDCCH candidates. The two detections or two PDCCH candidates may belong to different time slots. For example, each time slot corresponds to one detection or one PDCCH candidate, or both detections or two PDCCH candidates belong to the first time slot, or the merged detections or merged PDCCH candidates are included in each time slot used for merged detection (e.g., each time slot is counted as one detection or one PDCCH candidate). When repeated transmission is disabled, this detection method allows the UE to have the opportunity to correctly detect the PDCCH, even if the UE does not know whether the repeated transmission enable has been updated (as described in Embodiment 1), but the network side needs to transmit the PDCCH in the first time slot when repeated transmission is disabled.
[0100] In one embodiment, the blind detection method includes: detecting a first common downlink channel candidate, the common downlink channel candidate belonging to a first time slot; detecting the i-th common downlink channel candidate, or detecting a merged common downlink channel candidate, the merged common downlink channel candidate being obtained by merging the first common downlink channel candidate to the i-th common downlink channel candidate in different time slots of repeated transmission, the detection of the i-th common downlink channel candidate or the merged common downlink channel candidate belonging to the i-th time slot, i = 2, 3, ... N, where N is the number of repetitions of the repeated transmission of the common downlink channel.
[0101] In this embodiment, the UE performs N blind detections: for example, detecting the first PDCCH candidate, this detection or PDCCH candidate may be included in the first time slot; detecting the i-th PDCCH candidate, or merging the first PDCCH candidate into the i-th PDCCH candidate and performing detection, this detection or (merged) PDCCH candidate may be included in the i-th time slot. The specific detection method used may be determined by the UE implementation, configured by the network side, or predefined by the protocol; and so on, detecting the N-th PDCCH candidate, or merging the first PDCCH candidate into the N-th PDCCH candidate and performing detection, this detection or (merged) PDCCH candidate may be included in the N-th time slot. The specific detection method used may be determined by the UE implementation, configured by the network side, or predefined by the protocol.
[0102] Alternatively, the PDCCH candidates in multiple time slots of repeated transmission can be considered as N PDCCH candidates. N is the number of PDCCH repetitions, which may be a positive integer greater than 1. The N detections or N PDCCH candidates may belong to different time slots. For example, each time slot corresponds to one detection / one PDCCH candidate. This detection method allows the UE to correctly detect the PDCCH, even if the UE does not know whether the repeated transmission enable has been updated. However, it may place higher demands on the UE implementation, such as requiring the UE to determine which detection method to use.
[0103] In one embodiment, the blind detection method includes: detecting the i-th common downlink channel candidate, the common downlink channel candidate belonging to the i-th time slot, i = 2, 3, ... N, where N is the number of repetitions of the repeated transmission of the common downlink channel; detecting merged common downlink channel candidates, the merged common downlink channel candidates being obtained by merging the first common downlink channel candidate to the Nth common downlink channel candidate in different time slots of repeated transmission, the merged common downlink channel candidates belonging to the first time slot occupied by repeated transmission, or the last time slot occupied by repeated transmission, or each time slot used for merge detection.
[0104] In this embodiment, N+1 blind detections are performed: the first PDCCH candidate is detected, and this detection or PDCCH candidate may be included in the first time slot; the i-th PDCCH candidate is detected, and this detection or PDCCH candidate may be included in the i-th time slot; and so on, the N-th PDCCH candidate is detected, and this detection or PDCCH candidate may be included in the N-th time slot (of the time slots occupied by PDCCH repetition transmission); the first to N-th PDCCH candidates are merged and detected, and this detection or (merged) PDCCH candidate may be included in the first or N-th time slot. Alternatively, they may be included in the first to N-th time slots.
[0105] Alternatively, the PDCCH candidates in multiple repeatedly transmitted time slots may be regarded as N+1 PDCCH candidates. N is the number of PDCCH repetitions, which may be a positive integer greater than 1. The N+1 detections or the N+1 PDCCH candidates may belong to different time slots. For example, each time slot corresponds to a separate PDCCH candidate, and the combined PDCCH candidate belongs to the first or the Nth time slot. Alternatively, the first time slot corresponds to two PDCCH candidates (for example, the separate first PDCCH candidate and the combined PDCCH candidate), and the other time slots each correspond to one PDCCH candidate. Alternatively, the Nth time slot corresponds to two PDCCH candidates (for example, the separate Nth PDCCH candidate and the combined PDCCH candidate), and the other time slots each correspond to one PDCCH candidate. Alternatively, the combined detection or the combined PDCCH candidate is counted in each time slot used for combined detection (for example, each time slot is counted as one detection or one PDCCH candidate). When repeated transmission is disabled, this detection method enables the UE to have an opportunity to correctly detect the PDCCH, even if the UE does not know whether the enabling of repeated transmission is updated.
[0106] The i-th time slot may refer to the i-th time slot among the time slots occupied by PDCCH repeated transmission. The i-th PDCCH candidate may refer to the PDCCH candidate of the i-th time slot among the time slots occupied by PDCCH repeated transmission, or refer to the i-th PDCCH candidate in chronological order among the repeatedly transmitted PDCCH candidates. i may be an integer greater than or equal to 1 and less than or equal to N.
[0107] In some embodiments, a beam hopping mechanism is adopted to expand the coverage of the network side. For example, in a period T, the service time of a certain cell is T active <T. Alternatively, in a period T, the dwell time of an active beam in a certain cell is T active In this way, a single active beam can serve multiple cells in the period T, so as to improve the coverage area of the network. T active may be referred to as activation time or dwell time. The activation time for uplink transmission and the activation time for downlink reception may be the same or different. The reference point for the activation time may be a satellite or an uplink synchronization reference point. In specific implementation, to reduce implementation complexity, the uplink and downlink active beams may overlap on the satellite side. That is, the satellite transmits and receives signals to and from the same cell or beam position at the same time. Alternatively, the uplink activation time and the downlink activation time (for the same cell or beam position) are aligned on the satellite side. However, the uplink frame and the downlink frame are aligned at the uplink synchronization reference point, and the uplink synchronization reference point may not be on the satellite. At this time, the frame numbers or subframe numbers or time slot numbers or symbol numbers of the uplink activation time and the downlink activation time may be different. Therefore, the following solutions may be considered to determine the uplink activation time and the downlink activation time:
[0108] In one embodiment, the network side configures or indicates uplink activation time and downlink activation time respectively. For each activation time, the network side may configure at least one of period, offset, and duration. The reference point for the period or offset may be radio frame 0, or the reception time of the SSB (the radio frame, subframe, time slot, or symbol in which it is located). The granularity of the period, offset, and duration may be symbol, time slot, subframe, radio frame, millisecond, etc. The configuration of uplink and downlink activation times may be independent of each other.
[0109] In one embodiment, the network side configures or indicates the downlink activation time and indicates the offset of the uplink activation time relative to the downlink activation time. The user determines the uplink activation time based on the downlink activation time and the offset of the uplink activation time relative to the downlink activation time. The offset of the uplink activation time relative to the downlink activation time may refer to an offset of the start time or an offset of the end time. The granularity of the offset of the uplink activation time relative to the downlink activation time may be a symbol, time slot, subframe, radio frame, millisecond, etc. The offset may be positive, negative, or zero. The offset may be a logical time offset. For example, if the start time of the uplink activation time is in uplink subframe i and the start time of the downlink activation time is in downlink subframe j, the offset may be an index offset between uplink subframe i and uplink subframe j, and the index offset may be represented by the number of subframes. For another example, the offset may refer to an offset of the radio frame, an offset of the time slot, or an offset of the symbol. If an index number wrapback occurs, the wrapback should be included in the offset calculation. For example, if the uplink activation time starts in subframe i of uplink radio frame x, and the downlink activation time starts in subframe j of downlink radio frame x+2, then the aforementioned offset could be i-(j+2*N). subframe,num ), where N subframe,num The number of subframes within a single radio frame.
[0110] In one embodiment, the network side configures or indicates the downlink activation time. The user determines the uplink activation time based on the downlink activation time and the common TA. The common TA may refer to the round-trip time between the uplink synchronization reference point and the satellite.
[0111] In one embodiment, the network-side configuration only configures the uplink activation time.
[0112] Figure 3 is a schematic diagram of a periodic mode of TDD provided in one embodiment. Time Division Duplex (TDD) is a duplexing technology commonly used in traditional terrestrial networks. As shown in Figure 3, in TDD, a periodic transmission mode is usually defined, allocating a portion of the periodic time domain resources as downlink transmission resources, a portion as uplink transmission resources, and a portion as guard intervals or flexible resources.
[0113] In this application embodiment, the following concepts can be introduced for the transmission mode in TDD:
[0114] Periodic mode: This may also refer to transmission configuration, transmission mode, and / or periodic configuration, etc. For example, the length or period of a transmission mode is T. Each transmission mode may contain one or more uplink times, downlink times, and / or guard intervals.
[0115] Uplink time: This may also refer to uplink service time, uplink activation time, uplink configuration time, uplink duration, and / or uplink mode, etc. In TDD mode, uplink and downlink are time-divided resources, meaning that uplink transmission is performed for a portion of the time, downlink transmission for a portion of the time, and additional time is used as guard intervals / protection time, flexible time, or special time. Uplink time refers to the time used for uplink transmission as defined by the standard protocol or configured by the network (in periodic mode). Here, time may also refer to time-domain resources. For example, uplink time may refer to uplink subframes, available uplink subframes, or NB-IoT uplink subframes, etc.
[0116] Downlink time: This may also refer to downlink service time, downlink activation time, downlink configuration time, downlink duration, and / or downlink mode, etc. Downlink time refers to the time used for downlink transmission as defined by the standard protocol or configured by the network (in periodic mode). Time here may also refer to time-domain resources. For example, downlink time may refer to a downlink subframe, an available downlink subframe, or an NB-IoT downlink subframe, etc.
[0117] Guard interval: This may also refer to guard time, non-service time, inactive time, flexible time, special time, offset time (between uplink and downlink times), non-uplink / downlink time, time other than uplink and / or downlink times, etc. It may be defined by standard protocols or network configuration. Here, time or interval may also refer to time-domain resources. For example, a guard interval may refer to a subframe not configured as a downlink or uplink subframe, or consecutive subframes between downlink and uplink subframes, etc.
[0118] Non-uplink time: refers to time other than uplink time, which may include downlink time and protection interval.
[0119] Non-downlink time: refers to time other than downlink time, which may include uplink time and protection interval.
[0120] Overlap: This may also refer to overlap, conflict, collision, and / or coincidence. It refers to two resources partially or completely overlapping. The overlap described in this application embodiment also includes coincidence with offset. For example, when the interval or offset between two transmissions / transmission timings is less than (or less than or equal to) X time units, it is also considered an overlap. The interval or offset may refer to the interval between the first transmission end time and the second transmission start time (the first transmission start time may be earlier than the second transmission), or the offset between the first transmission start time and the second transmission start time, or the offset between the first transmission end time and the second transmission end time. Here, X may be configured on the network side or predefined by the protocol. X may reflect the minimum interval required between two transmissions / transmission timings.
[0121] The units or units of time mentioned above may be superframes, frames, subframes, time slots, symbols, samples, resource units, symbol groups, repetition units, etc., or absolute time such as milliseconds. When time resources used for transmission or mapping overlap with non-transmission time, it may be necessary to specify the UE's behavior. For example, if a subframe originally used for PDSCH transmission or mapping overlaps with non-downlink time, the PDSCH transmission overlapping with the non-downlink time may be delayed.
[0122] In the protocol, the search space, PDCCH candidates, or PDCCH period in NB-IoT is T = R. max *G. Where R... max G represents the maximum number of PDCCH repetitions / duration / aggregation level, a parameter configured on the network side. The start subframe parameter G characterizes the ratio of the period of the PDCCH candidate or the period of the search space to the maximum number of repetitions. The search space, PDCCH candidate, or the start subframe of the PDCCH may satisfy the following conditions:
[0123] n f n is the system frame number. s For the time slot number, α offset This is the start time offset coefficient. k0 is the start subframe, i.e., the time when resource mapping begins in the search space, PDCCH candidate, or PDCCH, but it is not necessarily the start time of actual transmission / detection. For example, if k0 is not an NB-IoT downlink subframe, i.e., the search space, PDCCH candidate, or PDCCH cannot be mapped, then the actual start time of transmission / detection of the search space, PDCCH candidate, or PDCCH may be the first NB-IoT downlink subframe after k0. In the protocol, R maxThe possible values for can be 1, 2, 4, 8, 16, 32, 64, 128, 256, 512, 1024, 2048. The possible values for G can be 1.5, 2, 4, 8, 16, 32, 48, 64, 96, 128. G=96 and G=128 may only be used in ground-based TDD mode. The period in the periodic mode may not be consistent with the period of the search space, PDCCH candidates, or PDCCH itself. For example, if the period in the periodic mode is 90ms, then regardless of the configuration, the period of the search space, PDCCH candidates, or PDCCH will be different from the period in the periodic mode.
[0124] As mentioned above, in TDD mode, downlink time may occur periodically, and may only account for a small portion in periodic mode. When the period of the periodic mode differs from the period of downlink transmission, downlink transmission may overlap with non-downlink time. This situation is more likely to occur when coverage enhancement is performed, such as during repeated transmissions. To avoid downlink transmission during non-downlink time, the PDCCH may only be mapped to valid downlink subframes, such as downlink subframes within downlink time or NB-IoT downlink subframes. In this case, it can be assumed that if the PDCCH overlaps with non-downlink time, it will be delayed to the next valid subframe, a downlink subframe within downlink time, or an NB-IoT downlink subframe.
[0125] The aforementioned delay behavior may cause different downlink transmissions to overlap or have intervals shorter than the minimum interval requirement. For example, after a delay, the first search space or PDCCH candidate or PDCCH may overlap with the second search space or PDCCH candidate or PDCCH or have an interval shorter than the minimum interval requirement. In conventional implementations (e.g., NB-IoT), if search spaces or PDCCH candidates or PDCCHs overlap or have intervals shorter than the minimum interval, the UE may prioritize detecting the later / new search space or PDCCH candidate or PDCCH (e.g., the second search space or PDCCH candidate or PDCCH), or the UE may not require detection of the preceding or older search space or PDCCH candidate or PDCCH (e.g., the first search space or PDCCH candidate or PDCCH), or may discard the preceding / older search space or PDCCH candidate or PDCCH (e.g., the first search space or PDCCH candidate or PDCCH). However, in TDD mode, if the period of the search space or PDCCH candidate or PDCCH does not match the TDD period, a situation as shown in Figure 4 may occur. That is, the start time of the second search space or PDCCH candidate or PDCCH is outside the downlink time, and the interval between it and the first search space or PDCCH candidate or PDCCH is less than the minimum interval (e.g., 4ms). However, after a delay, the actual start time of the second search space or PDCCH candidate or PDCCH transmission is greater than the minimum interval between it and the first search space. In this case, the first search space or PDCCH candidate or PDCCH may be discarded, but this discarding is unnecessary. To address the above problem, some enhanced methods are described in the following embodiments.
[0126] In one embodiment, the method further includes: determining the period of the search space or common downlink channel based on the period of the periodic pattern; wherein the period of the search space or common downlink channel is consistent with or an integer multiple of the period of the periodic pattern.
[0127] In this embodiment, a new search space, PDCCH candidate, or PDCCH period configuration or calculation method is introduced. For example, after determining the search space, PDCCH candidate, or PDCCH period according to conventional methods, scaling can be performed to maintain consistency with or be an integer multiple of the period of the periodic pattern.
[0128] In one example, T actual =K1*T TDD T actual T represents the search space, PDCCH candidates, or the (actual) period of the PDCCH. TDD This represents the period of the periodic pattern. The value of K1 may be T / T. TDD =R max *G / T TDDRound up or round down.
[0129] In one example, T actual =K1*T, where T actual For the search space, or the PDCCH candidate, or the (actual) period of the PDCCH, T = R max *G represents the period of the periodic pattern, and K1 is the scaling factor. The value of K1 can be T. TDD / T rounds up or down.
[0130] In one embodiment, determining the period of the search space or common downlink channel based on the period of the periodic pattern includes at least one of the following:
[0131] The period of the search space or common downlink channel is scaled; the period of the search space or common downlink channel is determined according to the parameters configured on the network side, wherein the parameters configured on the network side are integer multiples of the period value of the period mode, or the period value of the period mode is an integer multiple of the parameters configured on the network side.
[0132] In this embodiment, new parameters are introduced so that the search space, PDCCH candidates, or PDCCH period can be configured to be consistent with or an integer multiple of the periodic pattern. For example, in TDD mode, new candidate values for the parameter G are introduced. G may be T TDD The value of G (in milliseconds, subframes, or frames) is an integer multiple of the value (e.g., G = T). TDD *K2, where K2 is a positive integer such as 1, 2, 4, 5, 8, 10, etc. Or, T TDD The value of (in milliseconds, subframes, or frames) may be an integer multiple of G (e.g., G = T). TDD / K2, where K2 is a positive integer such as 1, 2, 4, 5, 8, 10, etc. For example, T TDD When the signaling time is 90ms, the candidate value of G may take at least one of the following values: 90, 45, 22.5, 18, 11.25, 9, 1. When introducing these candidate values, in order to maintain the same number of signaling bits, they may replace the current candidate value of G or delete some of the current candidate values of G. For example, introducing candidate value 90 may replace the original candidate value 1.5, or candidate value 90 may be introduced and candidate value 1.5 may be deleted.
[0133] In one embodiment, determining the period of the search space or common downlink channel based on parameters configured on the network side includes at least one of the following: T = G * T TDD T = R max *T TDD T = G * R max / D*T TDD T = R max / D*TTDD T = G * K3 * T TDD T = K3 * T TDD Where T is the period of the search space or common downlink channel, T TDD The period is the period of the periodic mode, where G is a parameter configured on the network side, D is the downlink time in the periodic mode or the time available for PDCCH transmission, and R is the period of the periodic mode. max K3 represents the maximum number of repetitions, duration, or aggregation level of PDCCH. max / D rounds up or down.
[0134] In this embodiment, a new formula for calculating the search space, PDCCH candidates, or PDCCH period is introduced, allowing the search space, PDCCH candidates, or PDCCH to maintain consistency with or be integer multiples of the periodic pattern. For example, the period of the search space, PDCCH candidates, or PDCCH is T = G * T. TDD Or, T = R max *T TDD Or, T = G * R max / D*T TDD Where D is the downlink time in periodic mode or the time available for PDCCH transmission. Alternatively, T = R. max / D*T TDD Alternatively, T = G * K3 * T TDD Where K3 is R max / D rounds up or down, where D is the downlink time in periodic mode or the time available for PDCCH transmission. Alternatively, T = K3 * T TDD .
[0135] In one embodiment, the method further includes: determining the start subframe of the search space or common downlink channel based on the superframe number; the start subframe satisfies: Where T is the period of the search space or common downlink channel, and n Hf n is the superframe number. f n is the frame number. s For the time slot number, α offset This is the start time offset coefficient.
[0136] In this embodiment, considering that the period of the periodic pattern may not be consistent with or an integer multiple of the system frame wrapback period or the superframe length (e.g., every 1024 system frames constitute a superframe, and the system frame index wraps back to 0 every 1024 system frames), a superframe may not contain an integer number of periodic patterns. To ensure the integrity of the periodic pattern, the periodic pattern may be transmitted across superframes, meaning that the start time of the periodic pattern mapping differs between different superframes. If the search space, PDCCH candidate, or PDCCH period is consistent with or an integer multiple of the periodic pattern period, a superframe may not contain an integer number of search spaces, PDCCH candidates, or PDCCH periods. In this case, if the method for determining k0 in the protocol (based on the system frame number and time slot number) is followed, the period mapping of the search space, PDCCH candidate, or PDCCH within each superframe will be reset to be calculated starting from system frame 0. Therefore, the interval between the last search space or PDCCH candidate or PDCCH of the previous superframe and the first search space or PDCCH candidate or PDCCH of the next superframe may not satisfy the search space or PDCCH candidate or PDCCH period. To avoid this problem, it may be necessary to incorporate the superframe number into the calculation of the start subframe k0. For example, the start subframe of the search space or PDCCH candidate or PDCCH may satisfy the following condition:
[0137] In one embodiment, the repeated transmission of the common downlink channel satisfies at least one of the following: overlap between the first search space and the second search space; the interval between the first search space and the second search space is less than a minimum interval; overlap between the first common downlink channel and the second common downlink channel; the interval between the first common downlink channel and the second common downlink channel is less than a minimum interval; wherein the start time of the second search space is after the start time of the first search space, and the start time of the second common downlink channel is after the start time of the first common downlink channel; the overlap or the interval is determined according to at least one of the following: the actual transmission time of the search space or the common downlink channel; the actual detection time of the search space or the common downlink channel.
[0138] In this embodiment, new rules are defined to handle overlaps in the search space, PDCCH candidates, or PDCCHs. For example, overlaps or intervals between the first search space, PDCCH candidate, or PDCCH and the second search space, PDCCH candidate, or PDCCH are less than the minimum interval, wherein the start time of the second search space, PDCCH candidate, or PDCCH is after the start time of the first search space, PDCCH candidate, or PDCCH. The UE does not require / expect to detect the first search space, PDCCH candidate, or PDCCH. The overlap or interval is determined based on the actual transmission / detection time of the search space, PDCCH candidate, or PDCCH. For example, the interval is determined by the end time of the first search space, PDCCH candidate, or PDCCH and the actual start time of the second search space, PDCCH candidate, or PDCCH (e.g., the first mapped subframe / slot). Specifically, this might be expressed as: the UE does not require detection of a PDCCH candidate in the first search space if that PDCCH candidate ends in subframe n, and the UE is configured to detect a PDCCH candidate in the second search space whose starting subframe is earlier than subframe n+5. The starting subframe is the actual starting subframe of the second search space or a PDCCH candidate in the second search space, such as the first mapped subframe. The second search space may be another search space (with a start time k0 later than the start time k0 of the first search space).
[0139] The UE is not required to detect PDCCH candidates in the first search space if a PDCCH candidate in the first search space ends in subframe n, and the UE is configured to detect PDCCH candidates in the second search space with a start subframe earlier than subframe n+5. The start subframe is the actual start subframe of the second search space or a PDCCH candidate in the second search space, such as the first mapped subframe. The second search space may be another search space (with a start time k0 later than the start time k0 of the first search space). The start time may be a start time determined according to the protocol rather than the actual start subframe.
[0140] The first search space or PDCCH candidate or PDCCH overlaps with the second search space or PDCCH candidate or PDCCH, or the interval between them is less than the minimum interval, wherein the start time of the second search space or PDCCH candidate or PDCCH is after the start time of the first search space or PDCCH candidate or PDCCH. The UE does not require / expect the detection of the second search space or PDCCH candidate or PDCCH. In specific implementations, this may be expressed as:
[0141] If a PDCCH candidate in the first search space ends in subframe n, the UE does not require detection of a PDCCH candidate in the second search space if the starting subframe of that PDCCH candidate is earlier than subframe n+5. The starting subframe may be the actual starting subframe of the second search space or a PDCCH candidate in the second search space, such as the first mapped subframe. The second search space may be another search space (with a start time k0 later than the start time k0 of the first search space).
[0142] If a PDCCH candidate exists in the first search space ending at subframe n, the UE does not require detection of PDCCH candidates in the second search space if a PDCCH candidate exists in the second search space and the starting subframe of that PDCCH candidate is earlier than subframe n+5. The starting subframe may be the actual starting subframe of the second search space or a PDCCH candidate in the second search space, such as the first mapped subframe. The second search space may be another search space (with a start time k0 later than the start time k0 of the first search space).
[0143] The enhancements mentioned above regarding the search space or PDCCH detection timing can also be applied to PRACH. For example, for PRACH, a new configurable period is introduced. This period may be consistent with or an integer multiple of the periodic pattern period. Considering that the periodic pattern period may not be consistent with or an integer multiple of the system frame wraparound period or superframe length (e.g., every 1024 system frames constitutes a superframe, and the system frame index wraps back to 0 every 1024 system frames), a superframe may not contain an integer number of periodic patterns. To ensure the integrity of the periodic patterns, periodic patterns may be transmitted across superframes, meaning that the start times of the periodic pattern mappings differ between superframes. If the PRACH period is consistent with or an integer multiple of the periodic pattern period, a superframe may not contain an integer number of PRACH periods. In the standard protocol, NPRACH transmission occurs in radio frame n. f The start time is delayed again. It begins at the time unit. Among them, wireless frame n f satisfy The start time parameter is configured for the network side. If the PRACH start time is determined according to the method in the protocol (based on the radio frame number and the start time parameter), the PRACH period mapping within each superframe will be reset to start from system frame 0. In this case, the interval between the last search space or PDCCH candidate or PDCCH of the previous superframe and the first search space or PDCCH candidate or PDCCH of the next superframe may not satisfy the search space or PDCCH candidate or PDCCH period. To avoid this problem, it may be necessary to incorporate the superframe number into the calculation of the PRACH start time. For example, in the above radio frame n... f The following conditions may be met: Where, n Hf This is the superframe number.
[0144] Figure 5 is a flowchart of a downlink transmission method provided in one embodiment. This method can be applied to a second communication node, which can be a network side, such as a base station. As shown in Figure 5, the method provided in this embodiment includes steps 210 and 220.
[0145] In 210, repeat transmission configuration information for the common downlink channel is sent.
[0146] In step 220, the common downlink channel is transmitted according to the repeated transmission configuration information.
[0147] In one embodiment, the retransmission configuration information is received via a first signaling, which includes at least one of the following: PBCH, MIB, SIB, and dedicated RRC signaling; if the first signaling is at least one of PBCH and MIB, the configuration information is also received via a second signaling, which includes at least one of SIB and dedicated RRC signaling; the retransmission configuration information received via the second signaling is consistent with at least one of the following of the retransmission configuration information received via the first signaling: bit field; signaling; information element; indication method for retransmission configuration information; and interpretation method for bit field or information element.
[0148] In one embodiment, the retransmission configuration information of the common downlink channel is not changed.
[0149] In one embodiment, the method further includes at least one of the following: sending first indication information, the first indication information being used to instruct a first communication node in the connected state to acquire at least one of MIB and PBCH during the process of acquiring system information; sending second indication information, the second indication information being used to instruct the first communication node in the connected state to at least one of the following: whether the retransmission configuration has been updated, and whether the retransmission configuration needs to be acquired again.
[0150] In one embodiment, the common downlink channel includes Msg4 PDSCH; the method further includes: determining whether to retransmit the Msg4 PDSCH based on at least one of the following: retransmission configuration information; retransmission capability reported by a first communication node; retransmission request reported by a first communication node.
[0151] In one embodiment, the method further includes: enabling or activating repeated transmission of the Msg4 PDSCH according to the number of repetitions of the Msg4 PDSCH indicated in the repeated transmission configuration information, when an activation condition is met; wherein the activation condition includes at least one of the following: the second communication node reports at least one of repeated transmission capability and repeated transmission request: repeated transmission of the SIB1 PDSCH; repeated transmission of the PDCCH that schedules the Msg4 PDSCH; the reference signal received power is less than a configured threshold; and repeated transmission of the Msg4 PDSCH is configured to be enabled or activated.
[0152] In one embodiment, the method further includes at least one of the following: determining the period of a search space or a common downlink channel based on the period of a periodic pattern, wherein the period of the search space or the common downlink channel is consistent with or an integer multiple of the period of the periodic pattern; determining the start subframe of the search space or the common downlink channel based on a superframe number, wherein the start subframe satisfies: Where T is the period of the search space or common downlink channel, and n Hf n is the superframe number. f n is the frame number. s For the time slot number, α offset This is the start time offset coefficient.
[0153] In one embodiment, the repeated transmission of the common downlink channel satisfies at least one of the following: the overlap between the first search space and the second search space is less than the minimum interval; the interval between the first search space and the second search space is less than the minimum interval; the overlap between the first common downlink channel and the second common downlink channel is less than the minimum interval; the interval between the first common downlink channel and the second common downlink channel is less than the minimum interval; wherein the start time of the second search space is after the start time of the first search space, and the start time of the second common downlink channel is after the start time of the first common downlink channel; the overlap or interval is determined according to at least one of the following: the actual transmission time of the search space or the common downlink channel; the actual detection time of the search space or the common downlink channel.
[0154] This application also provides a downlink transmission device. Figure 6 is a schematic diagram of the structure of a downlink transmission device according to an embodiment. As shown in Figure 6, the downlink transmission device includes: a first receiving module 310, configured to receive repetition configuration information of a common downlink channel; and a second receiving module 320, configured to receive the common downlink channel according to the repetition configuration information.
[0155] In one embodiment, the common downlink channel includes at least one of a common PDCCH and a common PDSCH; the common PDCCH includes at least one of the following: PDCCH CSS, a PDCCH using cell-level PDCCH parameters; the common PDSCH includes at least one of the following: a PDSCH before the second communication node obtains its proprietary PDSCH configuration, a PDSCH using cell-level PDSCH parameters.
[0156] In one embodiment, the retransmission configuration information includes at least one of the following: enabling retransmission, activating retransmission, the number of retransmissions, resource allocation for retransmission, associated search space, and associated identifier of search space.
[0157] In one embodiment, the retransmission configuration information is received via a first signaling, which includes at least one of the following: PBCH, MIB, SIB, and dedicated RRC signaling.
[0158] In one embodiment, when the first signaling is at least one of PBCH and MIB, the configuration information is also received via a second signaling, the second signaling including at least one of SIB and dedicated RRC signaling; the retransmission configuration information received via the second signaling is consistent with at least one of the following of the retransmission configuration information received via the first signaling: bit field; signaling; information element; indication method of retransmission configuration information; interpretation method of bit field or information element.
[0159] In one embodiment, the device further includes a second receiving module 320, specifically configured to detect the common downlink channel using a blind detection method based on the repeated transmission configuration information. The blind detection method includes at least one of the following: detecting a first common downlink channel candidate; detecting a second common downlink channel candidate; detecting a merged common downlink channel candidate, wherein the merged common downlink channel candidate is obtained by merging common downlink channel candidates from different time slots of repeated transmission.
[0160] In one embodiment, the blind detection method includes: detecting common downlink channel candidates according to the latest received retransmission configuration information.
[0161] In one embodiment, the first communication node does not anticipate any changes to the retransmission configuration information of the common downlink channel.
[0162] In one embodiment, the device further includes a third receiving module configured to receive first indication information, the first indication information being used to instruct a first communication node in a connected state to acquire at least one of MIB and PBCH during the process of acquiring system information.
[0163] In one embodiment, the device further includes: a fourth receiving module, configured to receive second indication information, the second indication information being used to indicate to the first communication node in the connected state at least one of the following: whether the repeat transmission configuration has been updated, or whether the repeat transmission configuration needs to be reacquired; and a reacquisition module, configured to acquire the repeat transmission configuration starting from the start time of the next modification cycle if the repeat transmission configuration has been updated or needs to be reacquired.
[0164] In one embodiment, the common downlink channel includes Msg4 PDSCH; the apparatus further includes: a determining module configured to determine whether to retransmit the Msg4 PDSCH based on at least one of the following: retransmission configuration information; retransmission capability reported by a first communication node; and retransmission request reported by a first communication node.
[0165] In one embodiment, the device further includes: a reporting module configured to report at least one of the repeat transmission capability and the repeat transmission request when reporting conditions are met; wherein the reporting conditions include at least one of the following: the number of repetitions of Msg4 PDSCH is configured; SIB1 PDSCH is retransmitted; the PDCCH that schedules Msg4 PDSCH is retransmitted; the reference signal received power is less than a configured threshold; and Msg4 PDSCH is configured to enable repeat transmission.
[0166] In one embodiment, the device further includes: an activation module configured to determine the repeated transmission of the Msg4 PDSCH based on the number of repetitions of the Msg4 PDSCH indicated in the repeated transmission configuration information, provided that an activation condition is met; wherein the activation condition includes at least one of the following: a first communication node reports at least one of repeated transmission capability and repeated transmission request: repeated transmission of the SIB1 PDSCH; repeated transmission of the PDCCH that schedules the Msg4 PDSCH; the reference signal received power is less than a configured threshold; and repeated transmission of the Msg4 PDSCH is configured to be enabled or activated.
[0167] In one embodiment, the blind detection method includes: detecting merged common downlink channel candidates, wherein the merged common downlink channel candidates are obtained by merging common downlink channel candidates from different time slots of repeated transmissions; the merged common downlink channel candidates belong to the first time slot occupied by repeated transmissions, or the last time slot occupied by repeated transmissions, or each time slot used for merge detection.
[0168] In one embodiment, the blind detection method includes: detecting a first common downlink channel candidate, the common downlink channel candidate belonging to a first time slot; detecting merged common downlink channel candidates, the merged common downlink channel candidates being obtained by merging common downlink channel candidates from different time slots of repeated transmission; the merged common downlink channel candidates belonging to the first time slot occupied by repeated transmission, or the last time slot occupied by repeated transmission, or each time slot used for merge detection.
[0169] In one embodiment, the blind detection method includes: detecting a first common downlink channel candidate, the common downlink channel candidate belonging to a first time slot; detecting an i-th common downlink channel candidate, or detecting a merged common downlink channel candidate, the merged common downlink channel candidate being obtained by merging the first common downlink channel candidate to the i-th common downlink channel candidate in different time slots of repeated transmission, the i-th common downlink channel candidate or the merged common downlink channel candidate belonging to the i-th time slot, i = 2, 3, ... N, where N is the number of repetitions of the repeated transmission of the common downlink channel.
[0170] In one embodiment, the blind detection method includes: detecting the i-th common downlink channel candidate, the common downlink channel candidate belonging to the i-th time slot, i = 2, 3, ... N, where N is the number of repetitions of the repeated transmission of the common downlink channel; detecting merged common downlink channel candidates, the merged common downlink channel candidates being obtained by merging the first common downlink channel candidate to the Nth common downlink channel candidate in different time slots of repeated transmission, the merged common downlink channel candidates belonging to the first time slot occupied by repeated transmission, or the last time slot occupied by repeated transmission, or each time slot used for merge detection.
[0171] In one embodiment, the device further includes a period processing module configured to determine the period of the search space or common downlink channel based on the period of the periodic pattern; wherein the period of the search space or common downlink channel is consistent with or an integer multiple of the period of the periodic pattern.
[0172] In one embodiment, the period processing module is specifically configured to: scale the period of the search space or the common downlink channel; determine the period of the search space or the common downlink channel according to parameters configured on the network side, wherein the parameters configured on the network side are integer multiples of the period value of the period mode, or the period value of the period mode is an integer multiple of the parameters configured on the network side.
[0173] The period processing module is configured to determine the period of the search space or common downlink channel based on parameters configured on the network side, including at least one of the following: T = G * T TDD T = R max *T TDD T = G * R max / D*T TDD T = R max / D*T TDD T = G * K3 * T TDD T = K3 * T TDD Where T is the period of the search space or common downlink channel, T TDD The period is the period of the periodic mode, where G is a parameter configured on the network side, D is the downlink time in the periodic mode or the time available for PDCCH transmission, and R is the period of the periodic mode. max K3 represents the maximum number of repetitions, duration, or aggregation level of PDCCH. max / D rounds up or down.
[0174] In one embodiment, the apparatus further includes: a subframe determination module, configured to determine the start subframe of the search space or common downlink channel based on a superframe number; the start subframe satisfies: Where T is the period of the search space or common downlink channel, and n Hf n is the superframe number. f n is the frame number. s For the time slot number, α offset This is the start time offset coefficient.
[0175] In one embodiment, the repeated transmission of the common downlink channel satisfies at least one of the following: overlap between the first search space and the second search space; the interval between the first search space and the second search space is less than a minimum interval; overlap between the first common downlink channel and the second common downlink channel; the interval between the first common downlink channel and the second common downlink channel is less than a minimum interval; wherein the start time of the second search space is after the start time of the first search space, and the start time of the second common downlink channel is after the start time of the first common downlink channel; the overlap or the interval is determined according to at least one of the following: the actual transmission time of the search space or the common downlink channel; the actual detection time of the search space or the common downlink channel.
[0176] The downlink transmission device proposed in this embodiment and the downlink transmission method proposed in the above embodiments belong to the same concept. 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 performing the downlink transmission method.
[0177] This application also provides a downlink transmission device. Figure 7 is a schematic diagram of the structure of a downlink transmission device according to an embodiment. As shown in Figure 7, the downlink transmission device includes: a first transmitting module 410, configured to transmit repetitive transmission configuration information of a common downlink channel; and a second transmitting module 420, configured to transmit the common downlink channel according to the repetitive transmission configuration information.
[0178] In one embodiment, the retransmission configuration information is received via a first signaling, which includes at least one of the following: PBCH, MIB, SIB, and dedicated RRC signaling; if the first signaling is at least one of PBCH and MIB, the configuration information is also received via a second signaling, which includes at least one of SIB and dedicated RRC signaling; the retransmission configuration information received via the second signaling is consistent with at least one of the following of the retransmission configuration information received via the first signaling: bit field; signaling; information element; indication method for retransmission configuration information; and interpretation method for bit field or information element.
[0179] In one embodiment, the retransmission configuration information of the common downlink channel is not changed.
[0180] In one embodiment, the device further includes at least one of the following: a third sending module configured to send first indication information, the first indication information being used to instruct a first communication node in the connected state to acquire at least one of MIB and PBCH during the process of acquiring system information; and a fourth sending module configured to send second indication information, the second indication information being used to instruct the first communication node in the connected state to at least one of the following: whether the retransmission configuration has been updated, and whether the retransmission configuration needs to be reacquired.
[0181] In one embodiment, the common downlink channel includes Msg4 PDSCH; the apparatus further includes: a determining module configured to determine whether to retransmit the Msg4 PDSCH based on at least one of the following: retransmission configuration information; retransmission capability reported by a first communication node; and retransmission request reported by a first communication node.
[0182] In one embodiment, the device further includes: an activation module configured to enable or activate repeated transmission of the Msg4 PDSCH according to the number of repetitions of the Msg4 PDSCH indicated in the repeated transmission configuration information, provided that an activation condition is met; wherein the activation condition includes at least one of the following: the second communication node reports at least one of repeated transmission capability and repeated transmission request: repeated transmission of the SIB1 PDSCH; repeated transmission of the PDCCH that schedules the Msg4 PDSCH; the reference signal received power is less than a configured threshold; and repeated transmission of the Msg4 PDSCH is configured to be enabled or activated.
[0183] In one embodiment, the device further includes a period processing module configured to determine the period of the search space or common downlink channel based on the period of the periodic pattern, wherein the period of the search space or common downlink channel is consistent with or an integer multiple of the period of the periodic pattern.
[0184] In one embodiment, the apparatus further includes a subframe determination module, configured to determine the start subframe of the search space or common downlink channel based on a superframe number, wherein the start subframe satisfies: Where T is the period of the search space or common downlink channel, and n Hf n is the superframe number. f n is the frame number. s For the time slot number, α offset This is the start time offset coefficient.
[0185] In one embodiment, the overlap between the first search space and the second search space is less than a minimum interval; the interval between the first search space and the second search space is less than a minimum interval; the overlap between the first common downlink channel and the second common downlink channel is less than a minimum interval; the interval between the first common downlink channel and the second common downlink channel is less than a minimum interval; wherein the start time of the second search space is after the start time of the first search space, and the start time of the second common downlink channel is after the start time of the first common downlink channel; the overlap or interval is determined based on at least one of the following: the actual transmission time of the search space or the common downlink channel; the actual detection time of the search space or the common downlink channel.
[0186] This application also provides a communication node. Figure 8 is a schematic diagram of the hardware structure of a communication node provided in an embodiment. As shown in Figure 8, the communication node provided in this application includes a processor 510 and a memory 520. The processor 510 in the communication node can be one or more, and Figure 8 takes one processor 510 as an example. The memory 520 is configured to store one or more programs. The one or more programs are executed by the one or more processors 510, so that the one or more processors 510 implement the downlink transmission method as described in the embodiment of this application.
[0187] The communication node also includes: a communication device 530, an input device 540, and an output device 550.
[0188] The processor 510, memory 520, communication device 530, input device 540 and output device 550 in the communication node can be connected by a bus or other means. Figure 8 shows an example of connection by bus.
[0189] Input device 540 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 550 may include display devices such as a display screen.
[0190] The communication device 530 may include a receiver and a transmitter. The communication device 530 is configured to perform information transmission and reception communication under the control of the processor 510.
[0191] The memory 520, 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 downlink transmission method described in the embodiments of this application. The memory 520 may include a program storage area and a data storage area, wherein the program storage area may store an operating system and an application program required for at least one function; the data storage area may store data created based on the use of the communication node, etc. Furthermore, the memory 520 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 520 may further include memory remotely located relative to the processor 510, 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, corporate intranets, local area networks, mobile communication networks, and combinations thereof.
[0192] This application also provides a storage medium storing a computer program, which, when executed by a processor, implements any of the downlink transmission methods or downlink transmission methods described in this application.
[0193] This application also provides a computer program product, including a computer program / instruction, which, when executed by a processor, implements any of the downlink transmission methods or downlink transmission methods described in this application.
[0194] 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.
[0195] 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.
[0196] 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.
[0197] 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).
[0198] This application also provides a computer program product, including a computer program / instructions, which, when executed by a processor, implement the downlink transmission method as described in any of the above embodiments.
[0199] The above description is merely an exemplary embodiment of this application and is not intended to limit the scope of protection of this application.
[0200] 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.
[0201] 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.
[0202] 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.
[0203] Any block diagram of logical flow in the accompanying drawings of this application may represent program operations, or may represent interconnected logic circuits, modules, and functions, or may represent a combination of program operations and logic circuits, modules, and functions. Computer programs may be stored in memory. 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. Data processors 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.
Claims
1. A downlink transmission method, applied to a first communication node, comprising: Receive retransmission configuration information for the common downlink channel; The common downlink channel is received according to the repeat transmission configuration information.
2. The method according to claim 1, wherein, The common downlink channel includes at least one of the common physical downlink control channel (PDCCH) and the common physical downlink shared channel (PDSCH); The public PDCCH includes at least one of the following: PDCCH Public Search Space (CSS), or PDCCH using cell-level PDCCH parameters; The public PDSCH includes at least one of the following: the PDSCH obtained by the second communication node before the proprietary PDSCH configuration, and the PDSCH using cell-level PDSCH parameters.
3. The method according to claim 1, wherein, The repetitive transmission configuration information includes at least one of the following: enabling repetitive transmission, activating repetitive transmission, the number of repetitive transmissions, resource allocation for repetitive transmission, associated search space, and associated identifier of the search space.
4. The method according to claim 1, wherein, The retransmission configuration information is received via a first signaling, which includes at least one of the following: Physical Broadcast Channel (PBCH), Master Information Block (MIB), System Information Block (SIB), and Dedicated Radio Resource Control (RRC) signaling.
5. The method according to claim 4, wherein, If the first signaling is at least one of the PBCH and the MIB, the retransmission configuration information is also received via a second signaling, the second signaling including at least one of the SIB and the dedicated RRC signaling; The repeat transmission configuration information received via the second signaling is consistent with at least one of the following in the repeat transmission configuration information received via the first signaling: bit field; signaling; information element; indication method of the repeat transmission configuration information; Methods for interpreting bit fields or information elements.
6. The method according to claim 1, wherein, Receiving the common downlink channel according to the repetitive transmission configuration information includes: Based on the retransmission configuration information, the common downlink channel is detected using a blind detection method, which includes at least one of the following: Detect the first common downlink channel candidate; Detect candidates for the second common downlink channel; The merged common downlink channel candidate is obtained by merging common downlink channel candidates from different time slots of repeated transmission.
7. The method according to claim 6, wherein, The blind detection method includes: detecting common downlink channel candidates according to the latest received repetitive transmission configuration information.
8. The method according to claim 1, wherein, The first communication node does not expect the retransmission configuration information of the common downlink channel to change.
9. The method according to claim 1, further comprising: Receive first indication information, which is used to instruct the first communication node in the connected state to acquire at least one of MIB and PBCH during the process of acquiring system information.
10. The method according to claim 1, further comprising: Receive second indication information, the second indication information being used to indicate to the first communication node in the connected state at least one of the following: whether the retransmission configuration has been updated, and whether the retransmission configuration needs to be reacquired; If the retransmission configuration is updated or needs to be retrieved again, the retransmission configuration will be retrieved starting from the start time of the next modification cycle.
11. The method according to claim 1, wherein, The common downlink channel includes message 4Msg4 PDSCH; the method further includes determining whether to retransmit the Msg4 PDSCH based on at least one of the following: The repeated transmission configuration information; The retransmission capability reported by the first communication node; The first communication node reports a retransmission request.
12. The method of claim 11, further comprising: If the reporting conditions are met, report at least one of the repeated transmission capability and the repeated transmission request; The reporting conditions include at least one of the following: The number of repetitions of the Msg4 PDSCH is configured; SIB1 PDSCH is used for repeated transmission; Schedule the PDCCH of the Msg4 PDSCH to be transmitted repeatedly; The reference signal received power is less than the configured threshold; When the Msg4 PDSCH is configured with retransmission enabled.
13. The method of claim 11, further comprising: If the activation conditions are met, the repeated transmission of Msg4 PDSCH is determined according to the number of repetitions of Msg4 PDSCH indicated in the repeated transmission configuration information; The activation conditions include at least one of the following: The first communication node reported at least one of the repeat transmission capability and the repeat transmission request: SIB1 PDSCH is used for repeated transmission; Schedule the PDCCH of the Msg4 PDSCH to be transmitted repeatedly; The reference signal received power is less than the configured threshold; The Msg4 PDSCH has been configured to enable or activate repetitive transmission.
14. The method according to claim 6, wherein, The blind detection method includes: The merged common downlink channel candidate is detected, which is obtained by merging the common downlink channel candidates in different time slots of the repeated transmission; The merged common downlink channel candidates belong to the first time slot occupied by the repeated transmission, or the last time slot occupied by the repeated transmission, or each time slot used for merge detection.
15. The method according to claim 6, wherein, The blind detection method includes: The first common downlink channel candidate is detected, and the common downlink channel candidate belongs to the first time slot; The merged common downlink channel candidate is detected, which is obtained by merging the common downlink channel candidates in different time slots of the repeated transmission; The merged common downlink channel candidates belong to the first time slot occupied by the repeated transmission, or the last time slot occupied by the repeated transmission, or each time slot used for merge detection.
16. The method according to claim 6, wherein, The blind detection method includes: The first common downlink channel candidate is detected, and the common downlink channel candidate belongs to the first time slot; Detect the i-th common downlink channel candidate, or detect the merged common downlink channel candidate, wherein the merged common downlink channel candidate is obtained by merging the first common downlink channel candidate to the i-th common downlink channel candidate in different time slots of the repeated transmission, and the i-th common downlink channel candidate or the merged common downlink channel candidate belongs to the i-th time slot, i = 2, 3, ... N, where N is the number of repetitions of the repeated transmission of the common downlink channel.
17. The method according to claim 6, wherein, The blind detection method includes: Detect the i-th common downlink channel candidate, which belongs to the i-th time slot, i = 2, 3, ... N, where N is the number of repetitions of the common downlink channel being transmitted repeatedly; The merged common downlink channel candidate is detected. The merged common downlink channel candidate is obtained by merging the first common downlink channel candidate to the Nth common downlink channel candidate in different time slots of the repeated transmission. The merged common downlink channel candidate belongs to the first time slot occupied by the repeated transmission, or the last time slot occupied by the repeated transmission, or each time slot used for merge detection.
18. The method according to claim 1, further comprising: The search space or the period of the common downlink channel is determined based on the period of the periodic pattern; The period of the search space or the common downlink channel is the same as or an integer multiple of the periodic pattern.
19. The method according to claim 18, wherein, Determining the search space or the period of the common downlink channel based on the period of the periodic pattern includes at least one of the following: Scaling the period of the search space or the common downlink channel; The period of the search space or the common downlink channel is determined according to the parameters configured on the network side, wherein the parameters configured on the network side are integer multiples of the period value of the periodic mode, or the period value of the periodic mode is an integer multiple of the parameters configured on the network side.
20. The method according to claim 19, wherein, The determination of the period of the search space or the common downlink channel based on parameters configured on the network side includes at least one of the following: T = G * T TDD T=R max *T TDD T = G * R max / D*T TDD T=R max / D*T TDD T = G * K3 * T TDD T = K3 * T TDD ; Where T is the period of the search space or the common downlink channel, T TDD Where G is the period of the periodic mode, D is the downlink time or the time available for PDCCH transmission in the periodic mode, and R is the period of the periodic mode. max K3 represents the maximum number of repetitions, duration, or aggregation level of PDCCH. max / D rounds up or down.
21. The method according to claim 1, further comprising: The search space or the start subframe of the common downlink channel is determined based on the superframe number; The starting subframe satisfies: Where T is the period of the search space or the common downlink channel, and n Hf n is the superframe number. f n is the frame number. s For the time slot number, α offset This is the start time offset coefficient.
22. The method according to claim 1, wherein, The repeated transmission of the common downlink channel satisfies at least one of the following: The first search space overlaps with the second search space; The interval between the first search space and the second search space is less than the minimum interval; The first common downlink channel and the second common downlink channel overlap; The interval between the first common downlink channel and the second common downlink channel is less than the minimum interval; Wherein, the start time of the second search space is after the start time of the first search space, and the start time of the second common downlink channel is after the start time of the first common downlink channel; The overlap or the interval is determined according to at least one of the following: The search space or the actual transmission time of the common downlink channel; The search space or the actual detection time of the public downlink channel.
23. A downlink transmission method, applied to a second communication node, comprising: Send retransmission configuration information for the common downlink channel; The common downlink channel is transmitted according to the repeat transmission configuration information.
24. The method according to claim 23, wherein, The retransmission configuration information is received via a first signaling, which includes at least one of the following: Physical Broadcast Channel (PBCH), Master Information Block (MIB), System Information Block (SIB), and Dedicated Radio Resource Control (RRC) signaling. If the first signaling is at least one of the PBCH and the MIB, the retransmission configuration information is also received via a second signaling, the second signaling including at least one of the SIB and the dedicated RRC signaling; The repeat transmission configuration information received via the second signaling is consistent with at least one of the following in the repeat transmission configuration information received via the first signaling: bit field; signaling; information element; indication method of the repeat transmission configuration information; Methods for interpreting bit fields or information elements.
25. The method according to claim 23, wherein, The retransmission configuration information for the common downlink channel will not be changed.
26. The method of claim 23, further comprising at least one of the following: Send a first indication message, which is used to instruct the first communication node in the connected state to acquire at least one of MIB and PBCH during the process of acquiring system information; Send a second indication message, which is used to indicate to the first communication node in the connected state at least one of the following: whether the retransmission configuration has been updated, and whether the retransmission configuration needs to be reacquired.
27. The method according to claim 23, wherein, The common downlink channel includes message 4Msg4 PDSCH; the method further includes determining whether to retransmit the Msg4 PDSCH based on at least one of the following: The repeated transmission configuration information; The ability to repeatedly transmit data reported by the first communication node; The first communication node reports a retransmission request.
28. The method of claim 23, further comprising: If the activation conditions are met, the repeated transmission of Msg4 PDSCH is enabled or activated according to the number of repetitions of Msg4 PDSCH indicated in the repeated transmission configuration information. The activation conditions include at least one of the following: The second communication node reported at least one of the following: repeat transmission capability and repeat transmission request: SIB1 PDSCH is used for repeated transmission; Schedule Msg4 PDSCH for repeated transmission of its PDCCH; The reference signal received power is less than the configured threshold; The Msg4 PDSCH retransmission is enabled or activated.
29. The method of claim 23, further comprising at least one of the following: The search space or the period of the common downlink channel is determined based on the period of the periodic pattern, and the period of the search space or the common downlink channel is consistent with or an integer multiple of the period of the periodic pattern. The start subframe of the search space or the common downlink channel is determined based on the superframe number, and the start subframe satisfies: in, T is the period of the search space or the common downlink channel, n Hf n is the superframe number. f n is the frame number. s For the time slot number, α offset This is the start time offset coefficient.
30. The method according to claim 23, wherein, The repeated transmission of the common downlink channel satisfies at least one of the following: The overlap between the first search space and the second search space is less than the minimum interval; The interval between the first search space and the second search space is less than the minimum interval; The overlap between the first common downlink channel and the second common downlink channel is less than the minimum interval; The interval between the first common downlink channel and the second common downlink channel is less than the minimum interval; Wherein, the start time of the second search space is after the start time of the first search space, and the start time of the second common downlink channel is after the start time of the first common downlink channel; The overlap or spacing is determined according to at least one of the following: The search space or the actual transmission time of the common downlink channel; The search space or the actual detection time of the public downlink channel.
31. A communication node, comprising: Memory, and at least one processor; The memory is configured to store at least one program; When the at least one program is executed by the at least one processor, the at least one processor implements the downlink transmission method as described in any one of claims 1-30.
32. A computer-readable storage medium storing a computer program that, when executed by a processor, implements the downlink transmission method as described in any one of claims 1-30.
