Message sending method and device, message receiving method and device, terminal and network side equipment

Abstract

The invention discloses a message sending method and device, a message receiving method and device, a terminal and network side equipment, and belongs to the technical field of communication, and the message sending method comprises the steps that the terminal sends a target message, and the target message is used for at least one of the following items: indicating a repeated related function of a downlink channel supported by the terminal; requesting to send downlink transmission corresponding to the repeated related function of the downlink channel to the terminal; wherein the downlink channel comprises at least one of the following items: a public physical downlink control channel (PDCCH) and a public physical downlink shared channel (PDSCH).

Description

Technical Field

[0001] The present application belongs to the field of communication technology, and specifically relates to a message sending method, a message receiving method, an apparatus, a terminal and a network side device. Background Art

[0002] In some scenarios or states, the terminal needs to receive some common downlink channels, such as receiving the common physical downlink control channel (PDCCH) and the common physical downlink shared channel (PDSCH). In some related technologies, the common downlink channel often only supports a single transmission, which results in a low success rate for the terminal to receive the downlink channel, resulting in poor service performance of the terminal. Summary of the invention

[0003] The embodiments of the present application provide a message sending method, a message receiving method, an apparatus, a terminal and a network side device, which can solve the problem of poor service performance of the terminal.

[0004] In a first aspect, a message sending method is provided, comprising:

[0005] The terminal sends a target message, where the target message is used for at least one of the following:

[0006] Indicating a repetition-related function of a downlink channel supported by the terminal;

[0007] Requesting to send a downlink transmission corresponding to a repeat-related function of a downlink channel to the terminal;

[0008] The downlink channel includes at least one of the following:

[0009] Public PDCCH, public PDSCH.

[0010] In a second aspect, a message receiving method is provided, comprising:

[0011] The network side device receives a target message sent by the terminal, where the target message is used for at least one of the following:

[0012] Indicating a repetition-related function of a downlink channel supported by the terminal;

[0013] Requesting to send a downlink transmission corresponding to a repeat-related function of a downlink channel to the terminal;

[0014] The downlink channel includes at least one of the following:

[0015] Public PDCCH, public PDSCH.

[0016] In a third aspect, a message sending device is provided, including:

[0017] The sending module is used to send a target message, where the target message is used for at least one of the following:

[0018] Indicating a repetition-related function of a downlink channel supported by the terminal;

[0019] Requesting to send a downlink transmission corresponding to a repeat-related function of a downlink channel to the terminal;

[0020] The downlink channel includes at least one of the following:

[0021] Public PDCCH, public PDSCH.

[0022] In a fourth aspect, a message receiving device is provided, comprising:

[0023] The receiving module is used to receive a target message sent by the terminal, where the target message is used for at least one of the following:

[0024] Indicating a repetition-related function of a downlink channel supported by the terminal;

[0025] Requesting to send a downlink transmission corresponding to a repeat-related function of a downlink channel to the terminal;

[0026] The downlink channel includes at least one of the following:

[0027] Public PDCCH, public PDSCH.

[0028] In a fifth aspect, a terminal is provided, which includes a processor and a memory, wherein the memory stores programs or instructions that can be run on the processor, and when the program or instructions are executed by the processor, the steps of the message sending method provided in the embodiment of the present application are implemented.

[0029] In a sixth aspect, a terminal is provided, comprising a processor and a communication interface, wherein the communication interface is used to send a target message, and the target message is used for at least one of the following: indicating a repetition-related function of a downlink channel supported by the terminal; requesting to send a downlink transmission corresponding to the repetition-related function of the downlink channel to the terminal; wherein the downlink channel comprises at least one of the following: a common PDCCH and a common PDSCH.

[0030] In the seventh aspect, a network side device is provided, which includes a processor and a memory, wherein the memory stores programs or instructions that can be run on the processor, and when the program or instructions are executed by the processor, the steps of the message receiving method provided in the embodiment of the present application are implemented.

[0031] In the eighth aspect, a network side device is provided, including a processor and a communication interface, wherein the communication interface is used to receive a target message sent by a terminal, and the target message is used for at least one of the following: indicating the repetition-related functions of the downlink channel supported by the terminal; requesting to send a downlink transmission corresponding to the repetition-related functions of the downlink channel to the terminal; wherein the downlink channel includes at least one of the following: a common PDCCH and a common PDSCH.

[0032] In the ninth aspect, a readable storage medium is provided, on which a program or instruction is stored. When the program or instruction is executed by a processor, the steps of the message sending method provided in the embodiment of the present application are implemented, or the steps of the message receiving method provided in the embodiment of the present application are implemented.

[0033] In the tenth aspect, a wireless communication system is provided, including: a terminal and a network side device, wherein the terminal can be used to execute the steps of the message sending method provided in the embodiment of the present application, and the network side device can be used to execute the steps of the message receiving method provided in the embodiment of the present application.

[0034] In the eleventh aspect, a chip is provided, which includes a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run a program or instruction to implement a message sending method as provided in an embodiment of the present application, or to implement a message receiving method as provided in an embodiment of the present application.

[0035] In the twelfth aspect, a computer program / program product is provided, which is stored in a storage medium, and the program / program product is executed by at least one processor to implement the steps of the message sending method provided in the embodiment of the present application, and the program / program product is executed by at least one processor to implement the steps of the message receiving method provided in the embodiment of the present application.

[0036] In the embodiment of the present application, the terminal sends a target message, and the target message is used for at least one of the following: indicating the repetition-related function of the downlink channel supported by the terminal; requesting to send the downlink transmission corresponding to the repetition-related function of the downlink channel to the terminal; wherein the downlink channel includes at least one of the following: public PDCCH and public PDSCH. In this way, at least one repetition transmission of the public PDCCH and the public PDSCH can be supported, thereby improving the success rate of the terminal receiving the downlink channel, so as to improve the service performance of the terminal. BRIEF DESCRIPTION OF THE DRAWINGS

[0037] Figure 1 is a block diagram of a wireless communication system to which the embodiments of the present application can be applied;

[0038] Figure 2is a flow chart of a message sending method provided in an embodiment of the present application;

[0039] Figure 3 is a flow chart of a message receiving method provided by an embodiment of the present application;

[0040] Figure 4 is a structural diagram of a message sending device provided in an embodiment of the present application;

[0041] Figure 5 is a structural diagram of a message receiving device provided in an embodiment of the present application;

[0042] Figure 6 is a structural diagram of a communication device provided in an embodiment of the present application;

[0043] Figure 7 is a structural diagram of a terminal provided in an embodiment of the present application;

[0044] Figure 8 It is a structural diagram of a network side device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0045] The following will be combined with the drawings in the embodiments of the present application to clearly describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, rather than all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field belong to the scope of protection of this application.

[0046] The terms "first", "second", etc. of the present application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It should be understood that the terms used in this way are interchangeable where appropriate, so that the embodiments of the present application can be implemented in an order other than those illustrated or described herein, and the objects distinguished by "first" and "second" are generally of one type, and the number of objects is not limited, for example, the first object can be one or more. In addition, "or" in the present application represents at least one of the connected objects. For example, "A or B" covers three schemes, namely, Scheme 1: including A but not including B; Scheme 2: including B but not including A; Scheme 3: including both A and B. The character " / " generally indicates that the objects associated with each other are in an "or" relationship.

[0047] The term "indication" in this application can be a direct indication (or explicit indication) or an indirect indication (or implicit indication). A direct indication can be understood as the sender explicitly informing the receiver of specific information, operations to be performed, or request results in the sent indication; an indirect indication can be understood as the receiver determining the corresponding information according to the indication sent by the sender, or making a judgment and determining the operation to be performed or the request result according to the judgment result.

[0048] It is worth noting that the technology described in the embodiments of the present application is not limited to the Long Term Evolution (LTE) / LTE-Advanced (LTE-A) system, but can also be used in other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency-Division Multiple Access (SC-FDMA) or other systems. The terms "system" and "network" in the embodiments of the present application are often used interchangeably, and the described technology can be used for the systems and radio technologies mentioned above as well as for other systems and radio technologies. The following description describes a New Radio (NR) system for illustrative purposes, and NR terminology is used in most of the following descriptions, but these technologies can also be applied to systems other than NR systems, such as the 6th generation (6 th Generation, 6G) communication system.

[0049] Figure 1A block diagram of a wireless communication system applicable to an embodiment of the present application is shown. The wireless communication system includes a terminal 11 and a network side device 12. Among them, the terminal 11 can be a mobile phone, a tablet computer (Tablet Personal Computer), a laptop computer (Laptop Computer), a notebook computer, a personal digital assistant (Personal Digital Assistant, PDA), a handheld computer, a netbook, an ultra-mobile personal computer (Ultra-mobile Personal Computer, UMPC), a mobile Internet device (Mobile Internet Device, MID), an augmented reality (Augmented Reality, AR), a virtual reality (Virtual Reality, VR) device, a robot, a wearable device (Wearable Device), an aircraft (flight vehicle), a vehicle-mounted device (Vehicle User Equipment, VUE), a ship-mounted device, a pedestrian terminal (Pedestrian User Equipment, PUE), a smart home (home appliances with wireless communication functions, such as refrigerators, televisions, washing machines or furniture, etc.), a game console, a personal computer (Personal Computer, PC), a teller machine or a self-service machine and other terminal side devices. Wearable devices include: smart watches, smart bracelets, smart headphones, smart glasses, smart jewelry (smart bracelets, smart bracelets, smart rings, smart necklaces, smart anklets, smart anklets, etc.), smart wristbands, smart clothing, etc. Among them, the vehicle-mounted device can also be called a vehicle-mounted terminal, a vehicle-mounted controller, a vehicle-mounted module, a vehicle-mounted component, a vehicle-mounted chip or a vehicle-mounted unit, etc. It should be noted that the specific type of the terminal 11 is not limited in the embodiment of the present application. The network side device 12 may include an access network device or a core network device, wherein the access network device may also be referred to as a radio access network (Radio Access Network, RAN) device, a radio access network function or a radio access network unit. The access network device may include a base station, a wireless local area network (Wireless Local Area Network, WLAN) access point (Access Point, AP) or a wireless fidelity (Wireless Fidelity, WiFi) node, etc.Among them, the base station may be referred to as a Node B (NB), an evolved Node B (eNB), a next generation Node B (gNB), a New Radio Node B (NR Node B), an access point, a Relay Base Station (RBS), a Serving Base Station (SBS), a Base Transceiver Station (BTS), a radio base station, a radio transceiver, a Basic Service Set (BSS), an Extended Service Set (ESS), a Home Node B (HNB), a Home Evolved Node B, a Transmission Reception Point (TRP) or other appropriate terms in the field. As long as the same technical effect is achieved, the base station is not limited to specific technical terms. It should be noted that in the embodiments of the present application, only the base station in the NR system is used as an example for introduction, and the specific type of the base station is not limited.

[0050] The core network equipment may include but is not limited to at least one of the following: core network node, core network function, mobility management entity (Mobility Management Entity, MME), access mobility management function (Access and Mobility Management Function, AMF), session management function (Session Management Function, SMF), user plane function (User Plane Function, UPF), policy control function (Policy Control Function, PCF), policy and charging rules function unit (Policy and Charging Rules Function, PCRF), edge application service discovery function (Edge Application Server Discovery Function, EASDF), unified data management (Unified Data Management, UDM), unified data storage (Unified Data Repository, UDR), home user server (Home Subscriber Server, HSS), centralized network configuration (CNC), network storage function (Network Repository Function, NRF), network exposure function (Network Exposure Function, NEF), local NEF (Local NEF, or L-NEF), binding support function (Binding Support Function, BSF), application function (Application Function, AF), etc. It should be noted that in the embodiments of the present application, only the core network device in the NR system is introduced as an example, and the specific type of the core network device is not limited.

[0051] In some embodiments, the random access process may be a contention-based random access process or a non-contention-based random access process. The random access process may be a four-step random access process (also called a Type-1 random access process) or a two-step random access process (also called a Type-2 random access process).

[0052] In the competitive 4-step random access process (Random Access Channel, RACH), the terminal first sends message 1 (Msg1) to the network, including a preamble; after the network detects the preamble, it will send message 2 (Msg2) / Random Access Response (RAR) message, including the number of the preamble detected by the network and the uplink wireless resources allocated to the terminal to send message 3 (Msg3); after receiving Msg2, the terminal confirms that at least one of the preamble numbers carried in Msg2 is consistent with the number of the preamble sent by itself, and then sends Msg3 containing contention resolution information according to the resources indicated by RAR; after receiving Msg3, the network will send message 4 (Msg4) containing contention resolution information; after receiving Msg4, the terminal confirms that the resolution information is consistent with that sent by itself in Msg3, that is, the 4-step random access is completed.

[0053] The network includes uplink grant (UL grant) information in the RAR to indicate the scheduling information of the Msg3 physical uplink shared channel (PUSCH), and includes information such as the random access preamble ID (RAPID), temporary cell-radio networktemporary identifier (TC-RNTI), and timing advance (TA). If the network does not receive the Msg3 PUSCH, it can schedule the retransmission of the Msg3 PUSCH in the TC-RNTI-scrambled physical downlink control channel (PDCCH).

[0054] For the competitive random access process, different terminals randomly select preambles for transmission, so different terminals may select the same preamble to send on the same time-frequency wireless resources (such as random access opportunity (RACH Occasion, RO) resources), which can be understood as a preamble conflict of the terminal. In this case, different terminals will receive the same RAR, and at this time, different terminals will transmit Msg3PUSCH according to the scheduling information in the RAR UL grant. In some related technologies, since repeated transmission of Msg3 PUSCH is not supported, the network can only decode the PUSCH (including contention resolution information) sent by one terminal on one Msg3 PUSCH scheduling resource, so the network will include the contention resolution information received in Msg3 in Msg4. If the contention resolution information in Msg4 received by the terminal matches the contention resolution information sent by the terminal in Msg3 PUSCH, the terminal considers that the contention resolution is successful. If they do not match, the contention resolution is considered unsuccessful.

[0055] If the contention resolution is unsuccessful, the terminal reselects RACH transmission resources, performs physical random access channel (PRACH) transmission, and makes the next random access attempt.

[0056] In some embodiments, the first step in the two-step random access process (2-step RACH) is that the terminal sends message A (MsgA) to the network side. After receiving MsgA, the network side sends message B (MsgB) to the terminal. If the terminal does not receive MsgB within a certain period of time, the terminal will accumulate the counter that counts the number of times MsgA is sent and resend MsgA. If the counter that counts the number of times MsgA is sent reaches a certain threshold, the terminal will switch from the two-step random access process to the four-step random access process. MsgA includes the MsgA preamble part and the MsgAPUSCH part. The preamble part is sent on the RO used for the two-step random access process, and the PUSCH part is sent on the MsgA PUSCH resources associated with the sending of the MsgA preamble and the RO. MsgA PUSCH resources are a group of PUSCH resources configured relative to each PRACH time slot, including time-frequency resources and DMRS resources.

[0057] In some embodiments, during the random access process, the reception of scheduling information of the physical downlink shared channel (PDSCH) of Msg2 / MsgB / Msg4 needs to be within a certain window, and the size of the window is configured by the network.

[0058] For Msg2, the above window starts from the first symbol of the control resource set (Control resource set, CORESET) in the Type 1 PDCCH common search space set (Type1-PDCCH CSS set) after PRACH is sent. For MsgB, the above window starts from the first symbol of the CORESET in the Type 1-PDCCH CSS set after PRACH (MsgA PRACH part) sends the corresponding PUSCH (MsgAPUSCH part). For Msg3, the above window is actually controlled by the random access contention resolution timer (ra-ContentionResolutionTimer), which will start or restart after the Msg3 is sent (if Msg3 repetition is supported, it is the last repetition of the Msg3).

[0059] In some embodiments, CORESET is a collection of time domain and frequency domain resources for control information. Among them, CORESET#0 is a special CORESET, which is usually used to schedule the transmission of PDCCH of System Information Block (SIB) 1. The configuration information of CORESET#0 and the configuration information of the monitoring timing of Type0-PDCCH Common Search Space (CSS) are carried by the associated Cell Defining Synchronization Signal Block (CD-SSB). The main function of CORESET#0 is to define the time and frequency resources of Type0-PDCCHCSS and the size of the monitoring timing of Type0-PDCCH CSS.

[0060] In combination with the accompanying drawings, a message sending method, a message receiving method, an apparatus, a terminal and a network side device provided in an embodiment of the present application are described in detail through some embodiments and their application scenarios.

[0061] See also Figure 2 , Figure 2 is a flow chart of a message sending method provided by an embodiment of the present application, such as Figure 2 As shown, the following steps are included:

[0062] Step 201: The terminal sends a target message, where the target message is used for at least one of the following:

[0063] Indicating a repetition-related function of a downlink channel supported by the terminal;

[0064] Requesting to send a downlink transmission corresponding to a repeat-related function of a downlink channel to the terminal;

[0065] The downlink channel includes at least one of the following:

[0066] Public PDCCH, public PDSCH.

[0067] The terminal sending the target message may be sending the target message to a network side device.

[0068] The repetition-related function of the downlink channel is a function related to repeated transmission of the downlink channel, which may also be referred to as the repetition-related capability of the downlink channel, or the repetition capability of the downlink channel.

[0069] The downlink channel repetition related function supported by the terminal means that the terminal supports the repetition transmission of the uplink channel, that is, the terminal supports receiving the repetition transmission of the downlink channel. The terminal supports receiving the repetition transmission of the downlink channel, which means that the terminal has the ability to receive common PDCCH / PDSCH repetition transmission.

[0070] The request to send the downlink channel to the terminal for the downlink transmission corresponding to the repetition-related function can be understood as the terminal requesting the network side device to send the downlink channel according to the repetition-related function of the downlink channel. Specifically, the terminal requests the network to repeatedly transmit the common PDCCH / PDSCH, and the request may or may not carry information such as the number of requested repetitions. After receiving the request, the network side device performs repeated transmission for the downlink channel, that is, repeatedly transmits the downlink channel to the terminal.

[0071] In some implementations, when the target message indicates a repetition-related function of a downlink channel supported by the terminal, it indicates requesting a network-side device to send a downlink transmission corresponding to the repetition-related function of the downlink channel to the terminal.

[0072] In some implementations, when the target message requests to send a downlink transmission corresponding to the repetition-related function of the downlink channel to the terminal, it indicates the repetition-related function of the downlink channel supported by the terminal.

[0073] In some embodiments, the target message may indicate whether the terminal supports the repetition-related function of the downlink channel, such as whether the terminal has the ability to receive the corresponding public PDSCH / PDCCH repetition; or, the target message may indicate whether the terminal requests to send a downlink transmission corresponding to the repetition-related function of the downlink channel to the terminal, or indicates whether it has the ability to request to send a downlink transmission corresponding to the repetition-related function of the downlink channel to the terminal, such as indicating whether it has the ability to request the network to repeat the transmission of the public PDSCH / PDCCH under certain conditions.

[0074] In the embodiment of the present application, the above steps can support repeated transmission of at least one of the public PDCCH and the public PDSCH, thereby improving the success rate of the terminal receiving the downlink channel, thereby improving the service performance of the terminal.

[0075] In this embodiment, after sending the above target message, the network side device sends repeated transmission of the downlink channel to the terminal based on the above target message, and the terminal receives the repeated transmission of the uplink channel.

[0076] As an optional implementation manner, the common PDCCH includes at least one of the following:

[0077] The PDCCH that the terminal needs to receive before entering the connected state;

[0078] PDCCH transmitted on common PDCCH resources.

[0079] The PDCCH that needs to be received before the terminal enters the connected state may include at least one of the following:

[0080] Schedule the PDCCH of the PDSCH that needs to be received before the terminal enters the connected state;

[0081] PDCCH for scheduling Msg3 PUSCH retransmission;

[0082] Schedule PDCCH of Msg5.

[0083] In some implementations, the public PDCCH may specifically include at least one of the following:

[0084] SIB1 PDCCH, Other System Information (OSI) PDCCH, Msg2 PDCCH, Msg4 PDCCH, MsgB PDCCH, paging PDCCH, and PDCCH scheduling Msg3 retransmission.

[0085] The PDCCH transmitted on the common PDCCH resources may be one or more PDCCHs transmitted on the common PDCCH resources, for example, one or more PDCCHs transmitted on CORESET#0, which may be PDCCHs transmitted on the Type0 / 0A / 1 / 2 PDCCH common search space set, such as SIB1 PDCCH, OSI PDCCH, Msg2PDCCH, Msg4 PDCCH, MsgB PDCCH, Paging PDCCH, and PDCCH for scheduling Msg3 retransmission. In addition, the common PDCCH resources refer to CORESET resources supporting CSS, which may be CORESET#0 or other CORESETs, and the CSS includes: Type0 / 0A / 1 / 2 CSS set, etc. In addition, the PDCCH transmitted on the CORESET resources associated with the CSS is also called a broadcast PDCCH.

[0086] As an optional implementation manner, the public PDSCH includes at least one of the following:

[0087] The PDSCH that the terminal needs to receive before entering the connected state.

[0088] Among them, the PDSCH that needs to be received before the terminal enters the connected state may include at least one of the following:

[0089] Msg2 PDSCH, MsgB PDSCH, Msg4 PDSCH, paging PDSCH.

[0090] That is, the public PDSCH may specifically include at least one of the following:

[0091] Msg2 PDSCH, MsgB PDSCH, Msg4 PDSCH.

[0092] In this implementation, repeated transmission of at least one of Msg2 PDSCH, MsgB PDSCH, Msg4 PDSCH and paging PDSCH can be achieved, that is, enhancement of Msg2 PDSCH, MsgB PDSCH, Msg4 PDSCH and paging PDSCH is achieved, thereby improving the random access performance of the terminal and improving the paging performance of the terminal.

[0093] In some embodiments, the transmission repetition of the above-mentioned common PDCCH / PDSCH may also be referred to as common PDCCH / PDSCH repetition. For example, for downlink control and data channels related to Msg2 / MsgB / Msg4, the repetition may be referred to as Msg2 / MsgB / Msg4 PDSCH / PDCCH repetition. Here, the Msg2 / MsgB / Msg4 PDSCH repetition may also be referred to as Msg2 / MsgB / Msg4 repetition.

[0094] As an optional implementation manner, the target message includes at least one of the following:

[0095] Physical Random Access Channel (PRACH), Msg1, Msg3PUSCH, MsgA, MsgA PUSCH, messages sent by the terminal in the connected state.

[0096] The message sent by the terminal in the connected state refers to the message sent by the terminal when it enters the connected state.

[0097] The target message may be implemented by implicitly or explicitly indicating the repetition-related function of the downlink channel supported by the terminal, or requesting to send the downlink transmission corresponding to the repetition-related function of the downlink channel to the terminal.

[0098] In some implementations, the PRACH is indicated or requested by at least one of the following:

[0099] The time domain resources of the PRACH, the frequency domain resources of the PRACH, the configuration index of the PRACH, the sequence of the PRACH, the scrambling sequence of the PRACH sequence, the format of the PRACH, and whether the PRACH is repeatedly transmitted;

[0100] The indication includes: indicating a repetition-related function of a downlink channel supported by the terminal, and the request includes: requesting to send a downlink transmission corresponding to the repetition-related function of the downlink channel to the terminal.

[0101] The above PRACH may include: Msg1 PRACH or MsgA PRACH.

[0102] In this implementation, multiple resources, indexes, sequences, and formats may be preconfigured, and these resources, indexes, sequences, and formats correspond to making the above request or indication, and not making the above request or indication, respectively. In this way, the terminal selects different resources, indexes, sequences, and formats when sending PRACH to realize the above indication or request. For example: a set of preamble sequence indexes (or other factors mentioned above) is predefined, and the PRACH corresponding to the preamble sequence index implicitly indicates that one or more subsequent common PDCCH / PDSCHs will be repeatedly transmitted, that is, the above indication or request is realized.

[0103] In addition, whether the PRACH is repeatedly transmitted may be that when the terminal supports PRACH repetition (PRACHrepetition), the terminal supports subsequent repeated reception of one or more common PDCCH / PDSCHs, ie, implements the above indication or request.

[0104] In the above implementation, it can be achieved that no additional messages need to be introduced when implementing the above instructions or requests, thereby saving transmission resources.

[0105] In some implementations, the MsgA PUSCH is indicated or requested by at least one of the following:

[0106] Information carried in the MsgA PUSCH, time domain resources of the MsgA PUSCH, frequency domain resources of the MsgA PUSCH, demodulation reference signal (DMRS) resources of the MsgA PUSCH, the group to which the MsgA PUSCH belongs, and whether the MsgA PUSCH is repeatedly transmitted;

[0107] The indication includes: indicating a repetition-related function of a downlink channel supported by the terminal, and the request includes: requesting to send a downlink transmission corresponding to the repetition-related function of the downlink channel to the terminal.

[0108] In this implementation, multiple resources or groups may be preconfigured, and these resources or groups correspond to making the above request or indication, and not making the above request or indication, respectively. In this way, the above indication or request is implemented by the terminal selecting different resources or groups when sending MsgA PUSCH. For example: multiple sets of MsgA PUSCH resources can be independently configured for use by terminals that support common PDCCH / PDSCH repetition transmission and terminals that do not support common PDCCH / PDSCH repetition transmission, respectively. The network determines whether the terminal supports the commonPDCCH / PDSCH repetition function based on the MsgA PUSCH resources used by the detected terminal, that is, the above indication or request is implemented. For another example: in the MsgA configuration of two-step random access (2-step RACH), two groups of PUSCH transmission opportunities (PO group A, PO group B) are configured. PO group A (PUSCHOccasion Group A) is used by terminals that support common PDCCH / PDSCH repetition transmission, and PO group B is used by terminals that do not support common PDCCH / PDSCH repetition transmission. The network determines whether the terminal supports reception or requests PDCCH / PDSCH repetition based on detecting the PUSCH on the two PO groups, thereby implementing the above-mentioned indication or request.

[0109] In some implementations, 2-step RACH itself does not send Msg4, but when 2-step RACH falls back or switches to 4-step random access (4-step RACH), there is still MsgA PUSCH transmission. In this case, MsgA PUSCH can be used to indicate the repetition capability of the corresponding Msg4 PDCCH / PDSCH.

[0110] In addition, whether the above-mentioned MsgA PUSCH is repeatedly transmitted may be that when the terminal supports MsgA PUSCH, the terminal supports repeated reception of one or more subsequent common PDCCH / PDSCH, that is, realizes the above-mentioned indication or request.

[0111] In the above implementation, it can be achieved that no additional messages need to be introduced when implementing the above instructions or requests, thereby saving transmission resources.

[0112] In some embodiments, the MsgA is indicated or requested by at least one of the following:

[0113] The time domain resources of the MsgA, the frequency domain resources of the MsgA, and the DMRS resources of the MsgA;

[0114] The indication includes: indicating a repetition-related function of a downlink channel supported by the terminal, and the request includes: requesting to send a downlink transmission corresponding to the repetition-related function of the downlink channel to the terminal.

[0115] In this implementation, multiple resources or groups may be preconfigured, and these resources or groups correspond to making the above request or indication, and not making the above request or indication, respectively. In this way, the above indication or request is implemented by the terminal selecting different resources or groups when sending MsgA. For example: two sets of MsgA resources may be independently configured to be used by terminals that support common PDCCH / PDSCH repetition and terminals that do not support common PDCCH / PDSCH repetition, respectively. The network determines the common PDCCH / PDSCH repetition capability of the terminal based on the MsgA resources used by the detected terminal, that is, implements the above indication or request.

[0116] In the above implementation, it can be achieved that no additional messages need to be introduced when implementing the above instructions or requests, thereby saving transmission resources.

[0117] In some implementations, the Msg3 PUSCH is indicated or requested by at least one of the following:

[0118] Information carried in the Msg3 PUSCH, time domain resources of the Msg3 PUSCH, frequency domain resources of the Msg3 PUSCH, DMRS resources of the Msg3 PUSCH, payload size of the Msg3 PUSCH, and whether the Msg3 PUSCH is repeatedly transmitted;

[0119] The indication includes: indicating a repetition-related function of a downlink channel supported by the terminal, and the request includes: requesting to send a downlink transmission corresponding to the repetition-related function of the downlink channel to the terminal.

[0120] The information carried in the above Msg3 PUSCH may be indicated by reusing existing fields or introducing new fields or using a logical channel identifier (logic channel id).

[0121] In this implementation, multiple resources and payload sizes may be preconfigured, and these resources and payload sizes correspond to making the above request or indication, and not making the above request or indication, respectively. In this way, the above indication or request is implemented by the terminal selecting different resources or payload sizes when sending Msg3PUSCH. For example: two Msg3PUSCH payload sizes (such as Preamble group A, Preamble group B) can be independently configured, which are used by terminals that support common PDCCH / PDSCH repetition and terminals that do not support common PDCCH / PDSCH repetition. The network determines the common PDCCH / PDSCH repetition capability of the terminal based on the payload size used by the detected terminal, that is, implements the above indication or request.

[0122] In addition, whether the above-mentioned Msg3 PUSCH is repeatedly transmitted may be that when the terminal supports Msg3 PUSCH, the terminal supports repeated reception of one or more subsequent common PDCCH / PDSCHs, that is, realizes the above-mentioned indication or request.

[0123] In the above implementation, it can be achieved that no additional messages need to be introduced when implementing the above instructions or requests, thereby saving transmission resources.

[0124] In some implementations, the Msg1 is used to indicate the payload size of the Msg3 PUSCH or whether the Msg3 PUSCH is to be repeatedly transmitted, wherein the payload size of the Msg3 PUSCH or whether the Msg3 PUSCH is to be repeatedly transmitted is used for indication or request;

[0125] The indication includes: indicating a repetition-related function of a downlink channel supported by the terminal, and the request includes: requesting to send a downlink transmission corresponding to the repetition-related function of the downlink channel to the terminal.

[0126] In this implementation, it is possible to indicate the payload size of the Msg3 PUSCH or whether the Msg3 PUSCH is to be repeatedly transmitted through Msg1 for indication or request. Specifically, since the payload size of the Msg3 PUSCH and whether the Msg3 PUSCH is to be repeatedly transmitted can be known by the network at the step of receiving Msg1, in this implementation, the common PDCCH / PDSCH can be a downlink channel before Msg3 is sent, such as Msg2 / BPDCCH / PDSCH. For example: the network can determine the payload size of the Msg3 PUSCH or whether the Msg3 PUSCH is to be repeatedly transmitted by detecting information such as the time domain resources or frequency domain resources of Msg1.

[0127] In the above implementation, it can be achieved that no additional messages need to be introduced when implementing the above instructions or requests, thereby saving transmission resources.

[0128] As an optional implementation manner, the target message is used to indicate at least one of the following:

[0129] The priority of the terminal, the type of the terminal, the frequency band of the terminal, and the capability level of the terminal;

[0130] The priority of the terminal is used to indicate a repetition-related function of a downlink channel supported by the terminal, or to request that a downlink transmission corresponding to the repetition-related function of the downlink channel be sent to the terminal;

[0131] The type of the terminal is used to indicate a repetition-related function of a downlink channel supported by the terminal, or to request that a downlink transmission corresponding to the repetition-related function of a downlink channel be sent to the terminal;

[0132] The frequency band where the terminal is located is used to indicate a repetition-related function of a downlink channel supported by the terminal, or to request that a downlink transmission corresponding to the repetition-related function of the downlink channel be sent to the terminal;

[0133] The capability level of the terminal is used to indicate the repetition-related function of the downlink channel supported by the terminal, or to request to send a downlink transmission corresponding to the repetition-related function of the downlink channel to the terminal.

[0134] In this implementation manner, the target message may be any message that can explicitly or implicitly indicate the priority of the terminal, the type of the terminal, the frequency band where the terminal is located, and the capability level of the terminal.

[0135] In this implementation, the above indication or request can be implemented based on at least one of the priority, type, frequency band, and capability level of the terminal, thereby eliminating the need to introduce additional messages and saving transmission resources.

[0136] For example, a terminal with a priority of 1 supports Common PDCCH / PDSCH repetition, while a terminal with a priority of 2 does not support Common PDCCH / PDSCH repetition.

[0137] For example, for customer premises equipment (CPE) terminals, the downlink supports Common PDCCH / PDSCH repetition, while for smart phones, the downlink does not support Common PDCCH / PDSCH repetition because the uplink coverage of smart phones may be limited.

[0138] For example, for frequency range (FR) 2, Common PDCCH / PDSCH repetition is supported, but for FR1, Common PDCCH / PDSCH repetition is not supported, because the base station size of FR2 is usually smaller and the transmission power is even close to that of mobile phones.

[0139] For example, terminals with capability level 1 can support common PDCCH / PDSCH repetition, but terminals with capability level 2 do not support common PDCCH / PDSCH repetition.

[0140] For example, a terminal of capability level 1 can support dynamic and semi-static common PDCCH / PDSCH repetition, a terminal of capability level 2 can support semi-static common PDCCH / PDSCH repetition but does not support dynamic common PDCCH / PDSCH repetition, and a terminal of capability level 3 does not support common PDCCH / PDSCH repetition.

[0141] As an optional implementation manner, the repetition-related function of the downlink channel includes at least one of the following:

[0142] Repeated transmission of the downlink channel;

[0143] The receiving window of the downlink channel is extended;

[0144] allowing repeated transmission of the downlink channel to exceed a receiving window corresponding to the downlink channel;

[0145] The timer corresponding to the downlink channel is extended;

[0146] The repeated transmission of the downlink channel is allowed to exceed the duration of the timer corresponding to the downlink channel.

[0147] In some implementations, the receiving window of the downlink channel includes at least one of the following: a RAR window (RARwindow), a message B MsgB response window (MsgB response window).

[0148] In some implementations, the timer corresponding to the downlink channel includes: a contention resolution timer.

[0149] The extension of the receiving window of the above-mentioned downlink channel can be to expand the receiving window of the downlink channel, for example: to expand on the basis of not supporting the receiving window corresponding to the repeated transmission of the above-mentioned downlink channel to extend the duration of the receiving window, or to redefine the receiving window corresponding to supporting the repeated transmission of the above-mentioned downlink channel.

[0150] The extension of the timer corresponding to the above-mentioned downlink channel can be to expand the timer corresponding to the downlink channel, for example: to expand it on the basis of not supporting the timer corresponding to the repeated transmission of the above-mentioned downlink channel to extend the duration of the timer, or to redefine the timer corresponding to supporting the repeated transmission of the above-mentioned downlink channel.

[0151] In this implementation manner, the terminal may support one or more of the above functions.

[0152] In addition, the above-mentioned multiple items may be associated with each other, for example: indicating that the terminal supports extension of the receiving window of the downlink channel also indicates that the terminal supports repeated transmission of the downlink channel, that is, the terminal has the ability to receive repeated transmission of the downlink channel; for example: indicating that the terminal allows repeated transmission of the downlink channel to exceed the receiving window corresponding to the downlink channel, also indicates that the terminal supports repeated transmission of the downlink channel, that is, the terminal has the ability to receive repeated transmission of the downlink channel; for example: indicating that the timer corresponding to the downlink channel is extended also indicates that the terminal supports repeated transmission of the downlink channel, that is, the terminal has the ability to receive repeated transmission of the downlink channel; for example: allowing repeated transmission of the downlink channel to exceed the duration of the timer corresponding to the downlink channel also indicates that the terminal supports repeated transmission of the downlink channel, that is, the terminal has the ability to receive repeated transmission of the downlink channel.

[0153] Optionally, the repeated transmission of the downlink channel includes at least one of the following:

[0154] Repeated transmission of the downlink channel of one TRP;

[0155] Repeated transmission of the downlink channel between multiple TRPs;

[0156] Repeated transmission of the downlink channel based on available time slots;

[0157] Repeated transmission of the downlink channel based on a physical time slot;

[0158] supporting repeated transmission of the downlink channel with an extended receiving window of the downlink channel;

[0159] Repeated transmission of the downlink channel with an extended reception window of the downlink channel is not supported;

[0160] Supporting repeated transmission of the downlink channel that allows repeated transmission of the downlink channel exceeding a receiving window corresponding to the downlink channel;

[0161] Not supporting the repeated transmission of the downlink channel that allows the repeated transmission of the downlink channel to exceed the receiving window corresponding to the downlink channel;

[0162] Supporting repeated transmission of the downlink channel with an extended timer corresponding to the downlink channel;

[0163] not supporting repeated transmission of the downlink channel with the timer corresponding to the downlink channel extended;

[0164] Supporting repeated transmission of the downlink channel that allows repeated transmission of the downlink channel to exceed the duration of a timer corresponding to the downlink channel;

[0165] not supporting repeated transmission of the downlink channel that allows repeated transmission of the downlink channel to exceed the duration of the timer corresponding to the downlink channel;

[0166] repeated transmission of said downlink channel within a time slot;

[0167] repeated transmission of said downlink channel between time slots;

[0168] Repeated transmission of the downlink channel within a control resource set;

[0169] Repeated transmission of the downlink channel between control resource sets;

[0170] repeated transmission of said downlink channel within the CSS;

[0171] repeated transmission of said downlink channel between CSSs;

[0172] Repeated transmission of the downlink channel within a monitoring occasion (MO);

[0173] Repeated transmission of said downlink channel between MOs;

[0174] Time domain repeated transmission of the downlink channel;

[0175] Frequency domain repeated transmission of the downlink channel;

[0176] Dynamically repeating transmission of the downlink channel;

[0177] Semi-static repetitive transmission of the downlink channel;

[0178] Repeated transmission of the downlink channel before a Radio Resource Control (RRC) connection is established;

[0179] Repeated transmission of the downlink channel before receiving a dedicated PDSCH configuration.

[0180] The repeated transmission of the downlink channel of the above-mentioned TRP may be that the common PDCCH / PDSCH repetition is for one TRP, or the common PDCCH / PDSCH repetition comes from one TRP.

[0181] The repeated transmission of the downlink channel between the above-mentioned multiple TRPs may be that the common PDCCH / PDSCH repetition is for multiple TRPs, or the common PDCCH / PDSCH repetition comes from multiple TRPs.

[0182] The above control resource set may be CORESET#0 or any other CORESET.

[0183] The above CSS can be any one or more of the Type0 / 0A / 1 / 2 CSS set.

[0184] The above MO is the monitoring time of PDCCH, which can be the same search space or different search spaces.

[0185] The time domain repetitive transmission of the downlink channel may be referred to as time domain downlink channel repetitive transmission, for example: time domain common PDCCH repetition, and the time domain repetition may be at least one of the following:

[0186] Repetition on different PDCCH MOs in the same search space of the same CORESET;

[0187] Repetition between different search spaces of the same or different CORESETs;

[0188] Repetition within the same search space of different CORESETs.

[0189] The frequency domain repetitive transmission of the downlink channel may be referred to as frequency domain downlink channel repetitive transmission, for example: frequency domain common PDCCH repetition, and the frequency domain repetition may be at least one of the following:

[0190] Repetition on the same PDCCH MO of the same CORESET;

[0191] Repetition of the same PDCCH MO on different CORESETs.

[0192] The same PDCCH MO may be located in the same search space or in different search spaces. For example, a CORESET resource of different repetitions is replicated multiple times at one time.

[0193] The above-mentioned dynamic repeated transmission of the downlink channel may be a dynamically determined repeated transmission of the downlink channel.

[0194] The semi-static repeated transmission of the downlink channel may be a pre-configured or periodically determined repeated transmission of the downlink channel.

[0195] The repeated transmission of the downlink channel before the above-mentioned RRC connection establishment may be all common PDCCH / PDSCH repetitions before RRC establishment, and the repeated transmission of the downlink channel before receiving the dedicated PDSCH (dedicated PDSCH) configuration may be all common PDCCH / PDSCH repetitions before the dedicated PDSCH configuration is received.

[0196] In the above implementation, the capability of repeated transmission of multiple downlink channels is defined, so that the terminal can flexibly indicate or request based on demand to improve the service performance of the terminal.

[0197] Optionally, in the case where the repeated transmission of the downlink channel includes multiple repeated transmissions, the multiple repeated transmissions are independent terminal capabilities, or the multiple repeated transmissions are combined terminal capabilities; or,

[0198] In the case where the repeated transmission of the downlink channel includes multiple repeated transmissions, the multiple repeated transmissions are indicated by the same target message, or the multiple repeated transmissions are indicated by at least two target messages.

[0199] The above-mentioned multiple items may be all or part of the items included in the repeated transmission of the above-mentioned uplink channel.

[0200] The above-mentioned multiple repeated transmissions are independent terminal capabilities, which may be that each of the above-mentioned items can be understood as an independent capability, for example: the dynamic repeated transmission of the downlink channel and the semi-static repeated transmission of the downlink channel are independent capabilities; and the above-mentioned multiple repeated transmissions are combined terminal capabilities, which may be that the above-mentioned items are a whole capability, for example: the dynamic repeated transmission of the downlink channel and the semi-static repeated transmission of the downlink channel are a capability.

[0201] Among them, the flexibility of indication or request can be improved through independent terminal capabilities, and a separate indication or request can be made for each capability. The terminal capabilities that are combined through the above-mentioned multiple repeated transmissions can save transmission overhead.

[0202] The above-mentioned multiple repeated transmissions can be indicated by the same target message to realize multiple capability indications or requests through one target message, which can save transmission resources. The above-mentioned multiple repeated transmissions can be indicated by at least two target messages, and each target message indicates or requests one or more capabilities to realize flexible indications or requests.

[0203] Optionally, the repeated transmission of the downlink channel is defined based on the granularity of terminal type (ie, per UE type definition), or the repeated transmission of the downlink channel is defined based on the granularity of terminal priority (ie, per UE priority definition).

[0204] The terminal type may be a low-capability terminal (RedCap UE) or a non-RedCap UE, or a terrestrial network (terrestrial network, TN) terminal or a non-terrestrial network (non-terrestrial network, NTN) terminal.

[0205] In this implementation, it is possible to define repeated transmission of the downlink channel based on the granularity of terminal type or priority, so that the definition of repeated transmission of the downlink channel can be more refined to meet more scenarios or business requirements.

[0206] Optionally, the repetitive transmission capability of the downlink channel matches a target downlink channel repetitive transmission capability, and the target downlink channel repetitive transmission capability is the downlink channel repetitive transmission capability after the terminal enters a connected state.

[0207] The matching of the repetitive transmission capability of the downlink channel and the repetitive transmission capability of the target downlink channel may be that the repetitive transmission of the uplink channel is consistent with a certain PDCCH / PDSCH repetitive capability when the terminal enters a connected state.

[0208] For example, the capability may be an existing PDSCH multi-slot repetition (pdsch-RepetitionMultiSlots) capability, that is, as long as the terminal has the pdsch-RepetitionMultiSlots capability, the network may consider that the terminal also has the common PDSCH repetition capability.

[0209] For another example, the above capability may be a multi-TRP PDCCH repetition (mTRP-PDCCH-Repetition) capability, that is, as long as the UE has the mTRP-PDCCH-Repetition-r17 capability, the network may consider that the terminal also has the common PDCCHrepetition capability.

[0210] In this implementation, since the retransmission capability of the downlink channel matches the retransmission capability of the target downlink channel, the capability reporting can be reduced and the transmission overhead can be saved.

[0211] Optionally, in a case where the terminal supports repeated transmission of the downlink channel, the terminal supports extension of a receiving window of the downlink channel; or

[0212] In the case where the terminal supports repeated transmission of the downlink channel, the terminal supports: allowing repeated transmission of the downlink channel to exceed a receiving window corresponding to the downlink channel; or

[0213] In a case where the terminal supports repeated transmission of the downlink channel, the terminal supports extension of a timer corresponding to the downlink channel; or

[0214] In a case where the terminal supports repeated transmission of the downlink channel, the terminal supports: allowing repeated transmission of the downlink channel to exceed a duration of a timer corresponding to the downlink channel.

[0215] In this implementation, it can be achieved that the terminal supports repeated transmission of the downlink channel to determine that the terminal supports at least one of the following:

[0216] Supporting the extension of the receiving window of the downlink channel;

[0217] allowing repeated transmission of the downlink channel to exceed a receiving window corresponding to the downlink channel;

[0218] The timer corresponding to the downlink channel is extended;

[0219] The repeated transmission of the downlink channel is allowed to exceed the duration of the timer corresponding to the downlink channel.

[0220] In this way, the overhead of the target message can be reduced.

[0221] Optionally, when the repeated related functions of the downlink channel include multiple functions, the multiple functions are indicated by the same target message, or the multiple functions are indicated by at least two target messages.

[0222] The above-mentioned multiple functions refer to multiple functions as follows:

[0223] Repeated transmission of the downlink channel;

[0224] The receiving window of the downlink channel is extended;

[0225] allowing repeated transmission of the downlink channel to exceed a receiving window corresponding to the downlink channel;

[0226] The timer corresponding to the downlink channel is extended;

[0227] The repeated transmission of the downlink channel is allowed to exceed the duration of the timer corresponding to the downlink channel.

[0228] Among them, the above-mentioned multiple functions are indicated by the same target message, which can save transmission resources. The above-mentioned multiple functions can be indicated by at least two target messages, and the same target message can indicate or request one or more of the above-mentioned functions, so that the indication or request can be more flexible.

[0229] As an optional implementation manner, the terminal sending the target message includes:

[0230] The terminal sends the target message under a target condition, where the target condition includes at least one of the following:

[0231] A reference signal received power (RSRP) of the downlink signal is greater than or equal to a first threshold;

[0232] A reference signal received quality (RSRQ) of the downlink signal is higher than or equal to a second threshold;

[0233] The uplink channel corresponding to the downlink channel performs repeated transmission, or the uplink channel corresponding to the downlink channel does not perform repeated transmission;

[0234] Using the same repetition request condition for all or part of the downlink channels;

[0235] The RSRQ thresholds for all or part of the downlink channels are the same, or the RSRP thresholds for all or part of the downlink channels are different,

[0236] The RSRQ thresholds for all or part of the downlink channels are the same, or the RSRQ thresholds for all or part of the downlink channels are different.

[0237] The downlink signal may be a downlink reference signal, for example, a reference signal for estimating path loss.

[0238] The repeated transmission of the uplink channel corresponding to the downlink channel may be Msg1 or MsgA or Msg3 or Msg4 hybrid automatic repeat request acknowledgement (HARQ-ACK) repeated transmission;

[0239] The uplink channel corresponding to the downlink channel mentioned above does not perform repeated transmission, which may be that Msg1 or MsgA or Msg3 or a hybrid automatic repeat request acknowledgement (HARQ-ACK) for Msg4 does not perform repeated transmission.

[0240] Specifically, the above target conditions may be agreed upon by the protocol, configured on the network side, or determined by the terminal.

[0241] In this implementation, the target message can be sent only under the target conditions to save transmission overhead.

[0242] As an optional implementation, the method further includes:

[0243] In a case where the terminal does not send the target message, the terminal receives configuration information, where the configuration information is used to configure repeated transmission resources of the downlink channel;

[0244] Wherein, in the case of a repetition-related function of a downlink channel supported by the terminal, the terminal performs blind detection on the repeated transmission resources of the downlink channel and the non-repetitive transmission resources of the downlink channel; or, in the case of a repetition-related function of a downlink channel not supported by the terminal, the terminal performs blind detection on the non-repetitive transmission resources of the downlink channel.

[0245] The above configuration information may be configured through system information, for example, through a master information block (Master Information Block, MIB).

[0246] In the case where the terminal does not send the target message, the terminal receiving the configuration information may be that the terminal receives the configuration information before the terminal sends the target message.

[0247] In addition, the terminal may perform blind detection on the repeated transmission resources and non-repeated transmission resources of the downlink channel before sending the above-mentioned target message or after sending the target message.

[0248] In this implementation, it can be achieved that when the target message is not sent, if the terminal supports the repetition-related function of the downlink channel, the terminal can perform blind detection on the repeated transmission resources of the downlink channel and the non-repetitive transmission resources of the downlink channel, thereby improving the receiving performance of the terminal's downlink channel.

[0249] In the embodiment of the present application, the terminal sends a target message, and the target message is used for at least one of the following: indicating the repetition-related function of the downlink channel supported by the terminal; requesting to send the downlink transmission corresponding to the repetition-related function of the downlink channel to the terminal; wherein the downlink channel includes at least one of the following: public PDCCH and public PDSCH. In this way, at least one repetition transmission of the public PDCCH and the public PDSCH can be supported, thereby improving the success rate of the terminal receiving the downlink channel, so as to improve the service performance of the terminal.

[0250] For example: in some scenarios, such as the NTN scenario, when the satellite needs to support multiple beams, the downlink transmission power of each beam will be reduced. At this time, the reception performance of Common PDCCH, such as PDCCH scheduling Msg2 / MsgB / Msg4, or common PDSCH such as PDSCH carrying Msg2 or MsgB or Msg4, cannot meet the requirements due to the lack of support for repeated transmission, making it impossible to complete random access, and thus making it impossible for all services (such as new air interface carrying voice (Voice over New Radio, VoNR), low-speed data transmission) channels to proceed further. In this case, the embodiment of the present application supports reporting of the repeated transmission function of Common PDCCH and common PDSCH or the terminal's request for common PDCCH / PDSCH repetition (for example, the terminal requests the network to schedule the repetition of common PDCCH / PDSCH under certain conditions). In addition, in order to ensure that the terminal can complete the reception of these related downlink PDSCH channels within a certain time while supporting the downlink repetition function, in an embodiment of the present application, the RAR window extension or the contentionresolution timer time length extension function is supported, and these capabilities are indicated to the network, and the network side can decide whether to configure the terminal to perform these functions.

[0251] For another example: In order to enable the network to know the terminal's related functions or requests for repeated reception of common PDCCH / PDSCH, in an embodiment of the present application, some functions can be combined as a common terminal capability, thereby reducing the complexity of terminal capability reporting or repeated requests.

[0252] See also Figure 3 , Figure 3 is a flow chart of a message receiving method provided by an embodiment of the present application, such as Figure 3 As shown, the following steps are included:

[0253] Step 301: A network-side device receives a target message sent by a terminal, where the target message is used for at least one of the following:

[0254] Indicating a repetition-related function of a downlink channel supported by the terminal;

[0255] Requesting to send a downlink transmission corresponding to a repeat-related function of a downlink channel to the terminal;

[0256] The downlink channel includes at least one of the following:

[0257] Common physical downlink control channel PDCCH, common physical downlink shared channel PDSCH.

[0258] Optionally, the public PDCCH includes at least one of the following:

[0259] A PDCCH that needs to be sent before the terminal enters a connected state;

[0260] PDCCH transmitted on common PDCCH resources;

[0261] or,

[0262] The common PDSCH includes:

[0263] The received PDSCH is sent before the terminal enters the connected state.

[0264] Optionally, the target message includes at least one of the following:

[0265] Physical random access channel PRACH, Msg1, Msg3 PUSCH, MsgA, MsgA PUSCH, messages sent by the terminal in the connected state.

[0266] Optionally, the PRACH is indicated or requested by at least one of the following:

[0267] The time domain resources of the PRACH, the frequency domain resources of the PRACH, the configuration index of the PRACH, the sequence of the PRACH, the scrambling sequence of the PRACH sequence, the format of the PRACH, and whether the PRACH is repeatedly transmitted;

[0268] or,

[0269] The MsgA PUSCH is indicated or requested by at least one of the following:

[0270] Information carried in the MsgA PUSCH, time domain resources of the MsgA PUSCH, frequency domain resources of the MsgA PUSCH, demodulation reference signal DMRS resources of the MsgA PUSCH, the group to which the MsgA PUSCH belongs, and whether the MsgAPUSCH is repeatedly transmitted;

[0271] or,

[0272] The MsgA indicates or requests at least one of the following:

[0273] The time domain resources of the MsgA, the frequency domain resources of the MsgA, and the DMRS resources of the MsgA;

[0274] or,

[0275] The Msg3 PUSCH is indicated or requested by at least one of the following:

[0276] Information carried in the Msg3 PUSCH, time domain resources of the Msg3 PUSCH, frequency domain resources of the Msg3 PUSCH, DMRS resources of the Msg3 PUSCH, payload size of the Msg3 PUSCH, and whether the Msg3 PUSCH is repeatedly transmitted;

[0277] or,

[0278] The Msg1 is used to indicate the payload size of the Msg3 PUSCH or whether the Msg3 PUSCH is to be repeatedly transmitted, wherein the payload size of the Msg3 PUSCH or whether the Msg3 PUSCH is to be repeatedly transmitted is used for indication or request;

[0279] The indication includes: indicating a repetition-related function of a downlink channel supported by the terminal, and the request includes: requesting to send a downlink transmission corresponding to the repetition-related function of the downlink channel to the terminal.

[0280] Optionally, the target message is used to indicate at least one of the following:

[0281] The priority of the terminal, the type of the terminal, the frequency band of the terminal, and the capability level of the terminal;

[0282] The priority of the terminal is used to indicate a repetition-related function of a downlink channel supported by the terminal, or to request that a downlink transmission corresponding to the repetition-related function of the downlink channel be sent to the terminal;

[0283] The type of the terminal is used to indicate a repetition-related function of a downlink channel supported by the terminal, or to request that a downlink transmission corresponding to the repetition-related function of a downlink channel be sent to the terminal;

[0284] The frequency band where the terminal is located is used to indicate a repetition-related function of a downlink channel supported by the terminal, or to request that a downlink transmission corresponding to the repetition-related function of the downlink channel be sent to the terminal;

[0285] The capability level of the terminal is used to indicate the repetition-related function of the downlink channel supported by the terminal, or to request to send a downlink transmission corresponding to the repetition-related function of the downlink channel to the terminal.

[0286] Optionally, the repetition-related functions of the downlink channel include at least one of the following:

[0287] Repeated transmission of the downlink channel;

[0288] The receiving window of the downlink channel is extended;

[0289] allowing repeated transmission of the downlink channel to exceed a receiving window corresponding to the downlink channel;

[0290] The timer corresponding to the downlink channel is extended;

[0291] The repeated transmission of the downlink channel is allowed to exceed the duration of the timer corresponding to the downlink channel.

[0292] Optionally, the receiving window of the downlink channel includes at least one of the following: a RAR window, a MsgB response window; or,

[0293] The timer corresponding to the downlink channel includes: a contention resolution timer.

[0294] Optionally, the repeated transmission of the downlink channel includes at least one of the following:

[0295] Repeated transmission of the downlink channel of one TRP;

[0296] Repeated transmission of the downlink channel between multiple TRPs;

[0297] repeated transmission of said downlink channel based on available time slots;

[0298] Repeated transmission of the downlink channel based on physical time slots;

[0299] supporting repeated transmission of the downlink channel with an extended receiving window of the downlink channel;

[0300] Repeated transmission of the downlink channel with an extended reception window of the downlink channel is not supported;

[0301] Supporting repeated transmission of the downlink channel that allows repeated transmission of the downlink channel exceeding a receiving window corresponding to the downlink channel;

[0302] Not supporting the repeated transmission of the downlink channel that allows the repeated transmission of the downlink channel to exceed the receiving window corresponding to the downlink channel;

[0303] Supporting repeated transmission of the downlink channel with an extended timer corresponding to the downlink channel;

[0304] not supporting repeated transmission of the downlink channel with the timer corresponding to the downlink channel extended;

[0305] Supporting repeated transmission of the downlink channel that allows repeated transmission of the downlink channel to exceed the duration of a timer corresponding to the downlink channel;

[0306] not supporting repeated transmission of the downlink channel that allows repeated transmission of the downlink channel to exceed the duration of the timer corresponding to the downlink channel;

[0307] repeated transmission of said downlink channel within a time slot;

[0308] repeated transmission of said downlink channel between time slots;

[0309] Repeated transmission of the downlink channel within a control resource set;

[0310] Repeated transmission of the downlink channel between control resource sets;

[0311] Repeated transmission of the downlink channel within a common search space CSS;

[0312] repeated transmission of said downlink channel between CSSs;

[0313] Repeated transmission of the downlink channel within a monitoring opportunity;

[0314] repeated transmission of said downlink channel between monitoring opportunities;

[0315] Time domain repeated transmission of the downlink channel;

[0316] Frequency domain repeated transmission of the downlink channel;

[0317] Dynamically repeating transmission of the downlink channel;

[0318] Semi-static repetitive transmission of the downlink channel;

[0319] Repeated transmission of the downlink channel before radio resource control RRC connection establishment;

[0320] Repeated transmission of the downlink channel before receiving a dedicated PDSCH configuration.

[0321] Optionally, in the case where the repeated transmission of the downlink channel includes multiple repeated transmissions, the multiple repeated transmissions are independent terminal capabilities, or the multiple repeated transmissions are combined terminal capabilities; or,

[0322] In the case where the repeated transmission of the downlink channel includes multiple repeated transmissions, the multiple repeated transmissions are indicated by the same target message, or the multiple repeated transmissions are indicated by at least two target messages.

[0323] Optionally, the repeated transmission of the downlink channel is defined based on the granularity of terminal type, or the repeated transmission of the downlink channel is defined based on the granularity of terminal priority.

[0324] Optionally, the repetitive transmission capability of the downlink channel matches a target downlink channel repetitive transmission capability, and the target downlink channel repetitive transmission capability is the downlink channel repetitive transmission capability after the terminal enters a connected state.

[0325] Optionally, when the terminal supports repeated transmission of the downlink channel, determining that the terminal supports extension of a receiving window of the downlink channel; or

[0326] In a case where the terminal supports repeated transmission of the downlink channel, determining that the terminal supports: allowing repeated transmission of the downlink channel to exceed a receiving window corresponding to the downlink channel; or

[0327] In a case where the terminal supports repeated transmission of the downlink channel, determining that the terminal supports extension of a timer corresponding to the downlink channel; or

[0328] In a case where the terminal supports repeated transmission of the downlink channel, it is determined that the terminal supports: allowing repeated transmission of the downlink channel to exceed a duration of a timer corresponding to the downlink channel.

[0329] Optionally, when the repeated related functions of the downlink channel include multiple functions, the multiple functions are indicated by the same target message, or the multiple functions are indicated by at least two target messages.

[0330] Optionally, the public PDSCH includes at least one of the following:

[0331] Msg2 PDSCH, MsgB PDSCH, Msg4 PDSCH; or,

[0332] The public PDCCH includes at least one of the following:

[0333] SIB1 PDCCH, OSI PDCCH, Msg2 PDCCH, Msg4 PDCCH, MsgB PDCCH, paging PDCCH, and PDCCH scheduling Msg3 retransmission.

[0334] Optionally, the method further includes:

[0335] In a case where the target message sent by the terminal is not received, the network side device sends configuration information to the terminal, where the configuration information is used to configure repeated transmission resources of the downlink channel.

[0336] It should be noted that this embodiment is Figure 2 The implementation of the corresponding network side device in the embodiment shown in the figure can be found in the specific implementation of Figure 2 To avoid repeated description, the related description of the embodiment shown in the present invention will not be repeated in detail.

[0337] The following is an example of the method provided in the embodiment of the present application through multiple embodiments:

[0338] Embodiment 1:

[0339] This embodiment mainly describes the Common PDCCH / PDSCH repetition capability indication or repetition request indication, which is as follows:

[0340] In some embodiments, the indication of the Common PDCCH / PDSCH repetition reception capability or repetition request is at least indicated by PRACH resources or information, where the PRACH resources or information include one or more of the following:

[0341] PRACH time domain resources, PRACH frequency domain resources, PRACH configuration index, PRACH sequence, PRACH sequence scrambling sequence, PRACH format, and whether PRACH performs repetition.

[0342] For example, a group of preamble sequence indexes (or other factors mentioned above) are predefined, and the PRACH corresponding to the preamble sequence index implicitly indicates that one or more subsequent common PDCCH / PDSCHs will be repeatedly transmitted.

[0343] For example, as long as the terminal supports PRACH repetition, the terminal supports subsequent repeated reception of one or more common PDCCH / PDSCHs.

[0344] The above-mentioned PRACH may be Msg1 PRACH or MsgA PRACH.

[0345] In some embodiments, the common PDCCH / PDSCH repetition capability or repetition request is at least indicated by MsgAPUSCH, including one or more of the following methods:

[0346] Explicitly indicated by the information carried in MsgA PUSCH, for example, existing fields can be reused or new fields can be introduced or logical channel identifiers (logic channel id) can be used for indication;

[0347] Implicitly indicated by MSgA PUSCH, including one or more of the following aspects:

[0348] MsgA PUSCH time domain resources, MsgA PUSCH frequency domain resources, MsgA PUSCH DMRS resources, MsgAPUSCH group, o MsgA PUSCH repetition;

[0349] For example, multiple sets of MsgA PUSCH resources can be independently configured for use by terminals that support common PDCCH / PDSCH repetition transmission and terminals that do not support common PDCCH / PDSCH repetition transmission. The network determines whether the terminal supports the common PDCCH / PDSCH repetition function based on the MsgA PUSCH resources used by the detected terminal.

[0350] For another example: In the MsgA configuration of 2-step RACH, two groups of PUSCH transmission opportunities (PO group A, PO group B) are configured. PO group A (PUSCH Occasion Group A) is used by terminals that support common PDCCH / PDSCH repetition transmission, and PO group B is used by terminals that do not support common PDCCH / PDSCH repetition transmission. The network determines whether a terminal supports reception or requests PDCCH / PDSCH repetition based on detecting PUSCH on the two PO groups.

[0351] There is no Msg4 transmission in 2-step RACH itself, but when 2-step RACH falls back or switches to 4-step RACH, there is still MsgA PUSCH transmission. In this case, MsgAPUSCH can be used to indicate the repetition capability of the corresponding Msg4 PDCCH / PDSCH.

[0352] In some embodiments, the common PDCCH / PDSCH repetition capability or repetition request is at least implicitly indicated by MsgA, including one or more of the following:

[0353] MsgA's time domain resources, MsgA's frequency domain resources, and MsgA's DMRS resources.

[0354] For example, two sets of MsgA resources can be independently configured to be used by terminals supporting common PDCCH / PDSCH repetition and terminals not supporting common PDCCH / PDSCH repetition respectively. The network determines the common PDCCH / PDSCH repetition capability of the terminal based on the MsgA resources used by the detected terminal.

[0355] In some embodiments, the common PDCCH / PDSCH repetition capability or repetition request is determined by at least Msg3 PUSCH related parameters / attributes, including one or more of the following methods:

[0356] Explicitly indicated by the information carried in Msg3 PUSCH, for example, existing fields can be reused or new fields can be introduced or logic channel id can be used for indication, such as using spare bits in Msg3;

[0357] Implicitly indicated by Msg3 PUSCH, including one or more of the following aspects:

[0358] Time domain resources of Msg3 PUSCH, frequency domain resources of Msg3 PUSCH, DMRS resources of Msg3 PUSCH, Msg3 PUSCH payload size (Preamble group A, Preamble group B), whether Msg3 PUSCH performs repetition (whether to select PRACH resources that support Msg3 repetition).

[0359] Among them, the above-mentioned common PDCCH / PDSCH can be Msg4 PDCCH / PDSCH after Msg3 transmission.

[0360] In addition, since the size of the Msg3 payload and whether Msg3 is repeated can be known to the network at the step of receiving Msg1, the common PDCCH / PDSCH mentioned here can also be the downlink channel before Msg3 is sent, such as Msg2 / B PDCCH / PDSCH.

[0361] In some embodiments, the terminal capability reporting of Common PDCCH / PDSCH repetition or Common PDCCH / PDSCH repetition request is performed by at least one or more of the following methods:

[0362] Determined based on the priority of the terminal, such as the terminal priority indicated by MSG 3, for example, a terminal with a priority of 1 supports Common PDCCH / PDSCH repetition, and a terminal with a priority of 2 does not support Common PDCCH / PDSCH repetition;

[0363] Determined based on the terminal type, for example: for CPE terminals, downlink supports Common PDCCH / PDSCH repetition, for smart phones, downlink does not support Common PDCCH / PDSCH repetition because the uplink coverage of smart phones may be limited;

[0364] Determined based on the frequency band, for example: for FR2, Common PDCCH / PDSCH repetition is supported, and for FR1, Common PDCCH / PDSCH repetition is not supported. This is because the base station size of FR2 is usually smaller, and the transmission power is even close to that of mobile phones;

[0365] It is determined based on the capability level of the terminal. For example, terminals with capability level 1 can support common PDCCH / PDSCH repetition, and terminals with capability level 2 do not support common PDCCH / PDSCH repetition. For another example, terminals with capability level 1 can support dynamic and semi-static common PDCCH / PDSCH repetition, terminals with capability level 2 can support semi-static common PDCCH / PDSCH repetition, but do not support dynamic common PDCCH / PDSCH repetition, and terminals with capability level 3 do not support common PDCCH / PDSCH repetition.

[0366] In some embodiments, dynamic common PDCCH / PDSCH repetition and semi-static common PDCCH / PDSCH repetition are separate UE capabilities.

[0367] For example: when the network configures a repetition factor in SIB1, such common PDCCH / PDSCH repetition can correspond to semi-static repetition capability; when the network configures multiple repetition factors in SIB1, the network can dynamically configure the terminal to use which repetition factor for each common PDCCH / PDSCH transmission, and such common PDCCH / PDSCH repetition can correspond to dynamic repetition capability.

[0368] In some embodiments, dynamic common PDCCH / PDSCH repetition and semi-static common PDCCH / PDSCH repetition are a terminal capability.

[0369] In some embodiments, the common PDCCH / PDSCH repetition capability includes one or more of the following combinations:

[0370] Common PDCCH / PDSCH repetition is for one TRP;

[0371] Common PDCCH / PDSCH repetition is for multiple TRPs;

[0372] Common PDCCH / PDSCH repetition based on available slots;

[0373] Common PDCCH / PDSCH repetition based on physical slot;

[0374] Whether to support RAR window extension (RAR window extension);

[0375] Whether to support Msg2 PDCCH / PDSCH repetition beyond RAR window;

[0376] Whether to support contention resolution timer duration extension (contention resolution timerduration extension);

[0377] Whether to support Msg4 PDCCH / PDSCH repetition exceeding the contention resolution timer duration (contention resolution timer duration);

[0378] Intra-slot common PDCCH / PDSCH repetition;

[0379] Inter-slot common PDCCH / PDSCH repetition;

[0380] Control resource set (Intra-coreset) common PDCCH repetition;

[0381] Inter-coreset common PDCCH repetition; the CORESET here can be CORESET#0 or any other CORESET;

[0382] Common PDCCH repetition within CSS (Intra-CSS);

[0383] Inter-CSS common PDCCH repetition; the CSS here can be any one or more of the Type0 / 0A / 1 / 2CSS set;

[0384] Intra-MO common PDCCH repetition;

[0385] Inter-MO common PDCCH repetition; the above MO is the monitoring opportunity of PDCCH, which can be the same search space or different search spaces;

[0386] Time domain common PDCCH repetition, the time domain repetition can be at least one of the following: repetition on different PDCCH MOs in the same search space of the same CORESET; repetition between different search spaces of the same or different CORESETs; repetition in the same search space of different CORESETs;

[0387] Frequency domain common PDCCH repetition, the frequency domain repetition can be at least one of the following: repetition on the same PDCCH MO of the same CORESET; repetition on the same PDCCH MO of different CORESETs. The same PDCCH MO can be located in the same search space or in different search spaces, for example, different repetitions replicate multiple copies of CORESET resources at one time;

[0388] Common PDCCH / PDSCH repetitions come from one TRP;

[0389] Common PDCCH / PDSCH repetitions come from multiple TRPs.

[0390] In some embodiments, the two or more capabilities described above are separate UE capabilities or combined UE capabilities.

[0391] In some embodiments, the definition of the Common PDCCH / PDSCH repetition capability or the Common PDCCH / PDSCH repetition request is defined per terminal type or per terminal priority. The different types of terminals here may be, for example, RedCap terminals or non-RedCap terminals, or TN terminals or NTN terminals.

[0392] In some embodiments, when common PDCCH / PDSCH has multiple repetition capabilities, the combination of various capabilities can be reported through different PRACH / MsgA / MsgA-PUSCH / Msg3 related parameters / attributes or explicit information.

[0393] For example: using different PRACH preamble groups to distinguish various Msg2 / MsgB / Msg4 PDCCH / PDSCH repetition capabilities. Assuming that the terminal needs to report whether it supports Msg2 / MsgB / Msg4 PDCCH / PDSCH repetition based on available slots or supporting RAR window extension, four preamble groups are defined on each PRACH occasion. Group A indicates that only repetition based on available slots is supported, group B indicates that repetition based on RAR window extension is supported, group C indicates that both repetition based on available slots and repetition based on RAR window extension are supported, and group D indicates that neither repetition is supported. For example: Table 1 shows:

[0394] Table 1:

[0395]

[0396] In some embodiments, after the terminal enters the RRC connected state, it reports the capability of common PDCCH / PDSCH repetition. The capability reporting here can be one or more of the following methods:

[0397] The common PDCCH / PDSCH repetition capabilities of different types (such as channels such as msg2 / msgB / Msg4 PDCCH / PDSCH) are reported independently; for example, for Common PDCCH repetition, there may be terminal capabilities or requests for SIB1 PDCCH repetition, terminal capabilities or requests for OSI PDCCH repetition, terminal capabilities or requests for Msg2 / 4 / B PDCCH repetition, terminal capabilities or requests for Paging PDCCH repetition, and terminal capabilities or requests for PDCCH repetition for scheduling Msg3 retransmission.

[0398] The common PDCCH / PDSCH repetition capabilities of different types (such as msg2 / msgB / Msg4 PDCCH / PDSCH channels) are merged into one capability; for example, the terminal only needs to report a terminal capability for receiving common PDCCH repetition, indicating that the terminal can support repetition transmission of all Common PDCCH channels (SIB1 PDCCH, OSI PDCCH, Msg2 / 4 / BPDCCH, Paging PDCCH, and PDCCH scheduling Msg3 retransmission).

[0399] In addition, in some embodiments, one or more of the following different types of downlink common PDCCH / PDSCH repetition capabilities are defined:

[0400] All common PDCCH / PDSCH repetitions before RRC establishment;

[0401] All common PDCCH / PDSCH repetitions before the dedicated PDSCH configuration is received;

[0402] It can be consistent with a certain PDCCH / PDSCH repetition capability when the terminal enters the connected state. For example, the above capability can be the existing PDSCH multi-slot repetition (pdsch-RepetitionMultiSlots) capability, that is, as long as the terminal has the pdsch-RepetitionMultiSlots capability, the network can consider the terminal also has the common PDSCH repetition capability; for example, the above capability can be the multi-TRP PDCCH repetition (mTRP-PDCCH-Repetition) capability, that is, as long as the terminal has the mTRP-PDCCH-Repetition-r17 capability, the network can consider the terminal also has the common PDCCHrepetition capability.

[0403] In some embodiments, no terminal receives a report or request for common PDCCH repetition capability, the network configures PDCCH repetition resources through the MIB, and the terminal receives repetition transmission based on its own capability.

[0404] For example, a terminal without PDCCH repetition capability will only perform blind detection at the legacy PDCCH transmission location;

[0405] Terminals with PDCCH repetition capability will perform blind detection at both legacy PDCCH and repetition PDCCH transmission locations.

[0406] In some embodiments, the Common PDCCH / PDSCH repetition request needs to meet one or more of the following conditions:

[0407] The RSRP / RSRQ measured by the downlink signal exceeds or is not less than a certain threshold. The downlink signal here can be used as a reference signal for estimating path loss.

[0408] Whether the corresponding Msg1 or MsgA or Msg3 or the PUCCH for Msg4 HARQ-ACK feedback is repeatedly transmitted;

[0409] One or more different Common PDCCH / PDSCH, such as Msg2 / MsgB / Msg4 / Paging PDCCH / PDSCH, use at least one of the same repetition request conditions;

[0410] The RSRP / RSRQ thresholds for downlink signal measurement may be the same or different for Common PDCCH / PDSCH, for example, by adding different RSRP offsets relative to a certain reference RSRP to determine the RSRP thresholds corresponding to the Msg2 / MsgB / Msg4 PDCCH / PDSCH repetition requests.

[0411] Embodiment 2

[0412] This embodiment mainly describes the determination of the RAR (Msg2 or MsgB) window extension (i.e., the receiving window extension in the above embodiment) or the ability of Msg2 / MsgB repetition to exceed the RAR window, as follows:

[0413] In some embodiments, the reception of Msg2 / MsgB PDCCH needs to be completed within the RAR window or MsgBresponse window. When Msg2 / msgB PDCCH is repeatedly sent, in order to support enough repetitions, the RAR window length is extended in this embodiment, and the corresponding terminal needs to have corresponding capabilities.

[0414] In some embodiments, in order to allow the network to send multiple RARs within the RAR window (similar to multiple RAR transmissions within the RAR window), the transmission time of the RAR PDSCH may also need to be completed within the RAR window as much as possible. When the RAR PDSCH supports repetition, this embodiment extends the RAR window length. At the same time, it is also necessary to consider whether to allow the repetition of the RAR to exceed the RAR window.

[0415] In some embodiments, the capability of RAR window extension or Msg2 / MsgB PDCCH / PDSCH repetition exceeding the RAR window may also be indicated by one or more methods used in the first embodiment to indicate common PDCCH / PDSCH repetition capability.

[0416] In some embodiments, the capability of RAR window extension or Msg2 / MsgB PDCCH / PDSCH repetition beyond RAR window is determined by Msg2 / MsgB PDCCH / PDSCH repetition capability. For example, as long as the terminal supports Msg2 / msgB PDCCH / PDSCH repetition, RAR window extension or msg2 / MsgBPDCCH / PDSCH repetition beyond RAR window is supported.

[0417] In some embodiments, RAR window extension or Msg2 / MsgB PDCCH / PDSCH repetition capability beyond the RAR window is mandatory.

[0418] In some embodiments, the RAR window extension or Msg2 / MsgB PDCCH / PDSCH repetition capability beyond the RAR window or Common PDCCH / PDSCH repetition capability of different types of terminals can be reported independently. The different types of terminals here can be, for example, RedCap terminals or non-RedCap terminals.

[0419] Embodiment three:

[0420] This embodiment mainly describes the determination of the capability of the Contention resolution timer or Msg4 PDCCH / PDSCH repetition exceeding the Contention resolution timer duration, which is specifically as follows:

[0421] In some embodiments, the reception of Msg4 PDCCH needs to be completed when the contention resolution timer has not expired. When Msg4 PDCCH is repeatedly sent, in order to support enough repetitions, the length of the contention resolution timer is extended in this embodiment, and the corresponding terminal needs to have corresponding capabilities.

[0422] In some embodiments, in order to allow the network to schedule multiple Msg4 transmissions within the Contention resolution timer duration (similar to multiple Msg4 transmissions within the Contention resolution timer duration), the sending time of Msg4 may also need to be completed within the Contention resolution timer duration as much as possible. When Msg4 supports repetition, this embodiment extends the length of the Contention resolution timer duration. At the same time, it is also necessary to consider whether to allow the repetition of Msg4 to exceed the Contention resolution timerduration.

[0423] In some embodiments, the capability of Contention resolution timer duration extension or Msg4PDCCH / PDSCH repetition exceeding Contention resolution timer duration may also be indicated by one or more of the methods used in the first embodiment to indicate common PDCCH / PDSCH repetition capability.

[0424] In some embodiments, the capability of Contention Resolution Timer Duration Extension or Msg4PDCCH / PDSCH repetition exceeding Contention Resolution Timer Duration is determined by Msg4PDCCH / PDSCH repetition capability. For example, as long as the terminal supports Msg4 PDCCH / PDSCH repetition, the capability of Contention Resolution Timer Duration Extension or Msg4 PDCCH / PDSCH repetition exceeding Contention Resolution Timer Duration is supported.

[0425] In some embodiments, the Contention resolution timer duration extension or the ability of Msg4PDCCH / PDSCH repetition to exceed the Contention resolution timer duration is mandatory.

[0426] In some embodiments, the contention resolution timer duration extension or the capability of Msg4PDCCH / PDSCH repetition exceeding the contention resolution timer duration or the capability of Common PDCCH / PDSCH repetition of different types of terminals can be reported independently. The different types of terminals here can be, for example, RedCap terminals or non-RedCap terminals.

[0427] The embodiment of the present application proposes that Common PDCCH / PDSCH repeats transmissions to receive related function indications or transmission requests, so that the network can enable these enhanced technologies, thereby improving the transmission reliability of common PDCCH / PDSCH, thereby ensuring the success rate of random access and reducing the delay of random access. In addition, the embodiment of the present application can also merge some terminal functions that can be merged, thereby reducing the complexity of terminal capability reporting or repeated requests and improving resource utilization. Conditional capability reporting, i.e. repeated requests, is introduced to avoid using common PDCCH / PDSCH repetitions for too many terminals without coverage issues, so as to improve the service performance of these terminals.

[0428] The message sending method provided in the embodiment of the present application can be executed by a message sending device. In the embodiment of the present application, the message sending device provided in the embodiment of the present application is described by taking the execution of the message sending method by a notification device as an example.

[0429] The message receiving method provided in the embodiment of the present application can be executed by a message receiving device. In the embodiment of the present application, the message receiving device provided in the embodiment of the present application is described by taking the execution of the message receiving method by a notification device as an example.

[0430] See also Figure 4 , Figure 4 is a structural diagram of a message sending device provided in an embodiment of the present application, such as Figure 4 As shown, the message sending device 400 includes:

[0431] The sending module 401 is used to send a target message, where the target message is used for at least one of the following:

[0432] Indicating a repetition-related function of a downlink channel supported by the terminal;

[0433] Requesting to send a downlink transmission corresponding to a repeat-related function of a downlink channel to the terminal;

[0434] The downlink channel includes at least one of the following:

[0435] Public PDCCH, public PDSCH.

[0436] Optionally, the public PDCCH includes at least one of the following:

[0437] The PDCCH that the terminal needs to receive before entering the connected state;

[0438] PDCCH transmitted on common PDCCH resources;

[0439] or,

[0440] The common PDSCH includes:

[0441] The PDSCH that the terminal needs to receive before entering the connected state.

[0442] Optionally, the target message includes at least one of the following:

[0443] PRACH, Msg1, Msg3 PUSCH, MsgA, MsgA PUSCH, messages sent by the terminal in the connected state.

[0444] Optionally, the PRACH is indicated or requested by at least one of the following:

[0445] The time domain resources of the PRACH, the frequency domain resources of the PRACH, the configuration index of the PRACH, the sequence of the PRACH, the scrambling sequence of the PRACH sequence, the format of the PRACH, and whether the PRACH is repeatedly transmitted;

[0446] or,

[0447] The MsgA PUSCH is indicated or requested by at least one of the following:

[0448] Information carried in the MsgA PUSCH, time domain resources of the MsgA PUSCH, frequency domain resources of the MsgA PUSCH, demodulation reference signal DMRS resources of the MsgA PUSCH, the group to which the MsgA PUSCH belongs, and whether the MsgAPUSCH is repeatedly transmitted;

[0449] or,

[0450] The MsgA indicates or requests at least one of the following:

[0451] The time domain resources of the MsgA, the frequency domain resources of the MsgA, and the DMRS resources of the MsgA;

[0452] or,

[0453] The Msg3 PUSCH is indicated or requested by at least one of the following:

[0454] Information carried in the Msg3 PUSCH, time domain resources of the Msg3 PUSCH, frequency domain resources of the Msg3 PUSCH, DMRS resources of the Msg3 PUSCH, payload size of the Msg3 PUSCH, and whether the Msg3 PUSCH is repeatedly transmitted;

[0455] or,

[0456] The Msg1 is used to indicate the payload size of the Msg3 PUSCH or whether the Msg3 PUSCH is to be repeatedly transmitted, wherein the payload size of the Msg3 PUSCH or whether the Msg3 PUSCH is to be repeatedly transmitted is used for indication or request;

[0457] The indication includes: indicating a repetition-related function of a downlink channel supported by the terminal, and the request includes: requesting to send a downlink transmission corresponding to the repetition-related function of the downlink channel to the terminal.

[0458] Optionally, the target message is used to indicate at least one of the following:

[0459] The priority of the terminal, the type of the terminal, the frequency band of the terminal, and the capability level of the terminal;

[0460] The priority of the terminal is used to indicate a repetition-related function of a downlink channel supported by the terminal, or to request that a downlink transmission corresponding to the repetition-related function of the downlink channel be sent to the terminal;

[0461] The type of the terminal is used to indicate a repetition-related function of a downlink channel supported by the terminal, or to request that a downlink transmission corresponding to the repetition-related function of a downlink channel be sent to the terminal;

[0462] The frequency band where the terminal is located is used to indicate a repetition-related function of a downlink channel supported by the terminal, or to request that a downlink transmission corresponding to the repetition-related function of the downlink channel be sent to the terminal;

[0463] The capability level of the terminal is used to indicate the repetition-related function of the downlink channel supported by the terminal, or to request to send a downlink transmission corresponding to the repetition-related function of the downlink channel to the terminal.

[0464] Optionally, the repetition-related functions of the downlink channel include at least one of the following:

[0465] Repeated transmission of the downlink channel;

[0466] The receiving window of the downlink channel is extended;

[0467] allowing repeated transmission of the downlink channel to exceed a receiving window corresponding to the downlink channel;

[0468] The timer corresponding to the downlink channel is extended;

[0469] The repeated transmission of the downlink channel is allowed to exceed the duration of the timer corresponding to the downlink channel.

[0470] Optionally, the receiving window of the downlink channel includes at least one of the following: a random access response RAR window, a MsgB response window; or,

[0471] The timer corresponding to the downlink channel includes: a contention resolution timer.

[0472] Optionally, the repeated transmission of the downlink channel includes at least one of the following:

[0473] Repeated transmission of the downlink channel of a transmission reception point TRP;

[0474] Repeated transmission of the downlink channel between multiple TRPs;

[0475] repeated transmission of said downlink channel based on available time slots;

[0476] Repeated transmission of the downlink channel based on physical time slots;

[0477] supporting repeated transmission of the downlink channel with an extended receiving window of the downlink channel;

[0478] Repeated transmission of the downlink channel with an extended reception window of the downlink channel is not supported;

[0479] Supporting repeated transmission of the downlink channel that allows repeated transmission of the downlink channel exceeding a receiving window corresponding to the downlink channel;

[0480] Not supporting the repeated transmission of the downlink channel that allows the repeated transmission of the downlink channel to exceed the receiving window corresponding to the downlink channel;

[0481] Supporting repeated transmission of the downlink channel with an extended timer corresponding to the downlink channel;

[0482] not supporting repeated transmission of the downlink channel with the timer corresponding to the downlink channel extended;

[0483] Supporting repeated transmission of the downlink channel that allows repeated transmission of the downlink channel to exceed the duration of a timer corresponding to the downlink channel;

[0484] not supporting repeated transmission of the downlink channel that allows repeated transmission of the downlink channel to exceed the duration of the timer corresponding to the downlink channel;

[0485] repeated transmission of said downlink channel within a time slot;

[0486] repeated transmission of said downlink channel between time slots;

[0487] Repeated transmission of the downlink channel within a control resource set;

[0488] Repeated transmission of the downlink channel between control resource sets;

[0489] Repeated transmission of the downlink channel within a common search space CSS;

[0490] repeated transmission of said downlink channel between CSSs;

[0491] Repeated transmission of the downlink channel within a monitoring opportunity;

[0492] repeated transmission of said downlink channel between monitoring opportunities;

[0493] Time domain repeated transmission of the downlink channel;

[0494] Frequency domain repeated transmission of the downlink channel;

[0495] Dynamically repeating transmission of the downlink channel;

[0496] Semi-static repetitive transmission of the downlink channel;

[0497] Repeated transmission of the downlink channel before radio resource control RRC connection establishment;

[0498] Repeated transmission of the downlink channel before receiving a dedicated PDSCH configuration.

[0499] Optionally, in the case where the repeated transmission of the downlink channel includes multiple repeated transmissions, the multiple repeated transmissions are independent terminal capabilities, or the multiple repeated transmissions are combined terminal capabilities; or,

[0500] In the case where the repeated transmission of the downlink channel includes multiple repeated transmissions, the multiple repeated transmissions are indicated by the same target message, or the multiple repeated transmissions are indicated by at least two target messages.

[0501] Optionally, the repeated transmission of the downlink channel is defined based on the granularity of terminal type, or the repeated transmission of the downlink channel is defined based on the granularity of terminal priority.

[0502] Optionally, the repetitive transmission capability of the downlink channel matches a target downlink channel repetitive transmission capability, and the target downlink channel repetitive transmission capability is the downlink channel repetitive transmission capability after the terminal enters a connected state.

[0503] Optionally, in a case where the terminal supports repeated transmission of the downlink channel, the terminal supports extension of a receiving window of the downlink channel; or

[0504] In the case where the terminal supports repeated transmission of the downlink channel, the terminal supports: allowing repeated transmission of the downlink channel to exceed a receiving window corresponding to the downlink channel; or

[0505] In a case where the terminal supports repeated transmission of the downlink channel, the terminal supports extension of a timer corresponding to the downlink channel; or

[0506] In a case where the terminal supports repeated transmission of the downlink channel, the terminal supports: allowing repeated transmission of the downlink channel to exceed a duration of a timer corresponding to the downlink channel.

[0507] Optionally, when the repeated related functions of the downlink channel include multiple functions, the multiple functions are indicated by the same target message, or the multiple functions are indicated by at least two target messages.

[0508] Optionally, the terminal sends a target message, including:

[0509] The terminal sends the target message under a target condition, where the target condition includes at least one of the following:

[0510] A reference signal received power RSRP of a downlink signal is higher than or equal to a first threshold;

[0511] A reference signal received quality RSRQ of the downlink signal is higher than or equal to a second threshold;

[0512] The uplink channel corresponding to the downlink channel performs repeated transmission, or the uplink channel corresponding to the downlink channel does not perform repeated transmission;

[0513] Using the same repetition request condition for all or part of the downlink channels;

[0514] The RSRP thresholds for all or part of the downlink channels are the same, or the RSRP thresholds for all or part of the downlink channels are different,

[0515] The RSRQ thresholds for all or part of the downlink channels are the same, or the RSRQ thresholds for all or part of the downlink channels are different.

[0516] Optionally, the public PDSCH includes at least one of the following:

[0517] Msg2 PDSCH, MsgB PDSCH, Msg4 PDSCH; or,

[0518] The public PDCCH includes at least one of the following:

[0519] SIB1 PDCCH, OSI PDCCH, Msg2 PDCCH, Msg4 PDCCH, MsgB PDCCH, paging PDCCH, and PDCCH scheduling Msg3 retransmission.

[0520] Optionally, the device further comprises:

[0521] A receiving module, configured to receive configuration information when the terminal does not send the target message, wherein the configuration information is used to configure repeated transmission resources of the downlink channel;

[0522] Wherein, in the case of a repetition-related function of a downlink channel supported by the terminal, the terminal performs blind detection on the repeated transmission resources of the downlink channel and the non-repetitive transmission resources of the downlink channel; or, in the case of a repetition-related function of a downlink channel not supported by the terminal, the terminal performs blind detection on the non-repetitive transmission resources of the downlink channel.

[0523] The message sending device can improve the service performance of the terminal.

[0524] In the embodiments of the present application, the message sending device may be an electronic device, such as an electronic device with an operating system, or a component in an electronic device, such as an integrated circuit or a chip. For example, the electronic device may be a terminal, or may be other devices other than a terminal. Exemplarily, the terminal may include but is not limited to the types of terminals listed in the embodiments of the present application, and other devices may be servers, network attached storage (NAS), etc., which are not specifically limited in the embodiments of the present application.

[0525] The message sending device provided in the embodiment of the present application can achieve Figure 2 The various processes implemented by the method embodiment shown achieve the same technical effect and will not be described again here to avoid repetition.

[0526] See also Figure 5 , Figure 5 is a structural diagram of a message receiving device provided in an embodiment of the present application, such as Figure 5 As shown, the message receiving device 500 includes:

[0527] The receiving module 501 is configured to receive a target message sent by a terminal, where the target message is used for at least one of the following:

[0528] Indicating a repetition-related function of a downlink channel supported by the terminal;

[0529] Requesting to send a downlink transmission corresponding to a repeat-related function of a downlink channel to the terminal;

[0530] The downlink channel includes at least one of the following:

[0531] Common physical downlink control channel PDCCH, common physical downlink shared channel PDSCH.

[0532] Optionally, the public PDCCH includes at least one of the following:

[0533] A PDCCH that needs to be sent before the terminal enters a connected state;

[0534] PDCCH transmitted on common PDCCH resources;

[0535] or,

[0536] The common PDSCH includes:

[0537] The received PDSCH is sent before the terminal enters the connected state.

[0538] Optionally, the target message includes at least one of the following:

[0539] Physical random access channel PRACH, Msg1, Msg3 PUSCH, MsgA, MsgA PUSCH, messages sent by the terminal in the connected state.

[0540] Optionally, the PRACH is indicated or requested by at least one of the following:

[0541] The time domain resources of the PRACH, the frequency domain resources of the PRACH, the configuration index of the PRACH, the sequence of the PRACH, the scrambling sequence of the PRACH sequence, the format of the PRACH, and whether the PRACH is repeatedly transmitted;

[0542] or,

[0543] The MsgA PUSCH is indicated or requested by at least one of the following:

[0544] Information carried in the MsgA PUSCH, time domain resources of the MsgA PUSCH, frequency domain resources of the MsgA PUSCH, demodulation reference signal DMRS resources of the MsgA PUSCH, the group to which the MsgA PUSCH belongs, and whether the MsgAPUSCH is repeatedly transmitted;

[0545] or,

[0546] The MsgA indicates or requests at least one of the following:

[0547] The time domain resources of the MsgA, the frequency domain resources of the MsgA, and the DMRS resources of the MsgA;

[0548] or,

[0549] The Msg3 PUSCH is indicated or requested by at least one of the following:

[0550] Information carried in the Msg3 PUSCH, time domain resources of the Msg3 PUSCH, frequency domain resources of the Msg3 PUSCH, DMRS resources of the Msg3 PUSCH, payload size of the Msg3 PUSCH, and whether the Msg3 PUSCH is repeatedly transmitted;

[0551] or,

[0552] The Msg1 is used to indicate the payload size of the Msg3 PUSCH or whether the Msg3 PUSCH is to be repeatedly transmitted, wherein the payload size of the Msg3 PUSCH or whether the Msg3 PUSCH is to be repeatedly transmitted is used for indication or request;

[0553] The indication includes: indicating a repetition-related function of a downlink channel supported by the terminal, and the request includes: requesting to send a downlink transmission corresponding to the repetition-related function of the downlink channel to the terminal.

[0554] Optionally, the target message is used to indicate at least one of the following:

[0555] The priority of the terminal, the type of the terminal, the frequency band of the terminal, and the capability level of the terminal;

[0556] The priority of the terminal is used to indicate a repetition-related function of a downlink channel supported by the terminal, or to request that a downlink transmission corresponding to the repetition-related function of the downlink channel be sent to the terminal;

[0557] The type of the terminal is used to indicate a repetition-related function of a downlink channel supported by the terminal, or to request that a downlink transmission corresponding to the repetition-related function of a downlink channel be sent to the terminal;

[0558] The frequency band where the terminal is located is used to indicate a repetition-related function of a downlink channel supported by the terminal, or to request that a downlink transmission corresponding to the repetition-related function of the downlink channel be sent to the terminal;

[0559] The capability level of the terminal is used to indicate the repetition-related function of the downlink channel supported by the terminal, or to request to send a downlink transmission corresponding to the repetition-related function of the downlink channel to the terminal.

[0560] Optionally, the repetition-related functions of the downlink channel include at least one of the following:

[0561] Repeated transmission of the downlink channel;

[0562] The receiving window of the downlink channel is extended;

[0563] allowing repeated transmission of the downlink channel to exceed a receiving window corresponding to the downlink channel;

[0564] The timer corresponding to the downlink channel is extended;

[0565] The repeated transmission of the downlink channel is allowed to exceed the duration of the timer corresponding to the downlink channel.

[0566] Optionally, the receiving window of the downlink channel includes at least one of the following: a RAR window, a MsgB response window; or,

[0567] The timer corresponding to the downlink channel includes: a contention resolution timer.

[0568] Optionally, the repeated transmission of the downlink channel includes at least one of the following:

[0569] Repeated transmission of the downlink channel of a transmission reception point TRP;

[0570] Repeated transmission of the downlink channel between multiple TRPs;

[0571] repeated transmission of said downlink channel based on available time slots;

[0572] Repeated transmission of the downlink channel based on physical time slots;

[0573] supporting repeated transmission of the downlink channel with an extended receiving window of the downlink channel;

[0574] Repeated transmission of the downlink channel with an extended reception window of the downlink channel is not supported;

[0575] Supporting repeated transmission of the downlink channel that allows repeated transmission of the downlink channel exceeding a receiving window corresponding to the downlink channel;

[0576] Not supporting the repeated transmission of the downlink channel that allows the repeated transmission of the downlink channel to exceed the receiving window corresponding to the downlink channel;

[0577] Supporting repeated transmission of the downlink channel with an extended timer corresponding to the downlink channel;

[0578] not supporting repeated transmission of the downlink channel with the timer corresponding to the downlink channel extended;

[0579] Supporting repeated transmission of the downlink channel that allows repeated transmission of the downlink channel to exceed the duration of a timer corresponding to the downlink channel;

[0580] not supporting repeated transmission of the downlink channel that allows repeated transmission of the downlink channel to exceed the duration of the timer corresponding to the downlink channel;

[0581] repeated transmission of said downlink channel within a time slot;

[0582] repeated transmission of said downlink channel between time slots;

[0583] Repeated transmission of the downlink channel within a control resource set;

[0584] Repeated transmission of the downlink channel between control resource sets;

[0585] Repeated transmission of the downlink channel within a common search space CSS;

[0586] repeated transmission of said downlink channel between CSSs;

[0587] Repeated transmission of the downlink channel within a monitoring opportunity;

[0588] repeated transmission of said downlink channel between monitoring opportunities;

[0589] Time domain repeated transmission of the downlink channel;

[0590] Frequency domain repeated transmission of the downlink channel;

[0591] Dynamically repeating transmission of the downlink channel;

[0592] Semi-static repetitive transmission of the downlink channel;

[0593] Repeated transmission of the downlink channel before radio resource control RRC connection establishment;

[0594] Repeated transmission of the downlink channel before receiving a dedicated PDSCH configuration.

[0595] Optionally, in the case where the repeated transmission of the downlink channel includes multiple repeated transmissions, the multiple repeated transmissions are independent terminal capabilities, or the multiple repeated transmissions are combined terminal capabilities; or,

[0596] In the case where the repeated transmission of the downlink channel includes multiple repeated transmissions, the multiple repeated transmissions are indicated by the same target message, or the multiple repeated transmissions are indicated by at least two target messages.

[0597] Optionally, the repeated transmission of the downlink channel is defined based on the granularity of terminal type, or the repeated transmission of the downlink channel is defined based on the granularity of terminal priority.

[0598] Optionally, the repetitive transmission capability of the downlink channel matches a target downlink channel repetitive transmission capability, and the target downlink channel repetitive transmission capability is the downlink channel repetitive transmission capability after the terminal enters a connected state.

[0599] Optionally, when the terminal supports repeated transmission of the downlink channel, determining that the terminal supports extension of a receiving window of the downlink channel; or

[0600] In a case where the terminal supports repeated transmission of the downlink channel, determining that the terminal supports: allowing repeated transmission of the downlink channel to exceed a receiving window corresponding to the downlink channel; or

[0601] In a case where the terminal supports repeated transmission of the downlink channel, determining that the terminal supports extension of a timer corresponding to the downlink channel; or

[0602] In a case where the terminal supports repeated transmission of the downlink channel, it is determined that the terminal supports: allowing repeated transmission of the downlink channel to exceed a duration of a timer corresponding to the downlink channel.

[0603] Optionally, when the repeated related functions of the downlink channel include multiple functions, the multiple functions are indicated by the same target message, or the multiple functions are indicated by at least two target messages.

[0604] Optionally, the public PDSCH includes at least one of the following:

[0605] Msg2 PDSCH, MsgB PDSCH, Msg4 PDSCH; or,

[0606] The public PDCCH includes at least one of the following:

[0607] SIB1 PDCCH, OSI PDCCH, Msg2 PDCCH, Msg4 PDCCH, MsgB PDCCH, paging PDCCH, and PDCCH scheduling Msg3 retransmission.

[0608] Optionally, the device further comprises:

[0609] The sending module is used to send configuration information to the terminal when the target message sent by the terminal is not received, and the configuration information is used to configure the repeated transmission resources of the downlink channel.

[0610] The message receiving device can improve the service performance of the terminal.

[0611] The message receiving device in the embodiment of the present application may be an electronic device, such as an electronic device with an operating system, or a component in the electronic device, such as an integrated circuit or a chip. The electronic device may be a terminal or a network side device.

[0612] The message receiving device provided in the embodiment of the present application can realize Figure 3 The various processes implemented by the method embodiment shown achieve the same technical effect and will not be described again here to avoid repetition.

[0613] Optional, such as Figure 6As shown, the embodiment of the present application further provides a communication device 600, including a processor 601 and a memory 602, and the memory 602 stores a program or instruction that can be run on the processor 601. For example, when the communication device 600 is a terminal, the program or instruction is executed by the processor 601 to implement the various steps of the above-mentioned message sending method embodiment, and can achieve the same technical effect. When the communication device 600 is a network side device, the program or instruction is executed by the processor 601 to implement the various steps of the above-mentioned message receiving method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0614] An embodiment of the present application also provides a terminal, including a processor and a communication interface, wherein the communication interface is used to send a target message, and the target message is used for at least one of the following: indicating the repetition-related functions of the downlink channel supported by the terminal; requesting to send a downlink transmission corresponding to the repetition-related functions of the downlink channel to the terminal; wherein the downlink channel includes at least one of the following: a common PDCCH and a common PDSCH.

[0615] like Figure 7 As shown, the terminal 700 includes but is not limited to: a radio frequency unit 701, a network module 702, an audio output unit 703, an input unit 704, a sensor 705, a display unit 706, a user input unit 707, an interface unit 708, a memory 709 and at least some of the components of the processor 710.

[0616] Those skilled in the art will appreciate that the terminal 700 may also include a power source (such as a battery) for supplying power to various components, and the power source may be logically connected to the processor 710 through a power management system, thereby implementing functions such as managing charging, discharging, and power consumption management through the power management system. Figure 7 The communication device structure shown in the figure does not constitute a limitation on the communication device. The communication device may include more or fewer components than shown in the figure, or combine certain components, or arrange the components differently, which will not be described in detail here.

[0617] It should be understood that in the embodiment of the present application, the input unit 704 may include a graphics processing unit (GPU) 7041 and a microphone 7042, and the graphics processing unit 7041 processes the image data of a static picture or video obtained by an image capture device (such as a camera) in a video capture mode or an image capture mode. The display unit 706 may include a display panel 7061, and the display panel 7061 may be configured in the form of a liquid crystal display, an organic light emitting diode, etc. The user input unit 707 includes a touch panel 7071 and at least one of other input devices 7072. The touch panel 7071 is also called a touch screen. The touch panel 7071 may include two parts: a touch detection device and a touch controller. Other input devices 7072 may include, but are not limited to, a physical keyboard, function keys (such as a volume control button, a switch button, etc.), a trackball, a mouse, and a joystick, which will not be repeated here.

[0618] In the embodiment of the present application, after receiving downlink data from the network side device, the RF unit 701 can transmit the data to the processor 710 for processing; in addition, the RF unit 701 can send uplink data to the network side device. Generally, the RF unit 701 includes but is not limited to an antenna, an amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, etc.

[0619] The memory 709 can be used to store software programs or instructions and various data. The memory 709 may mainly include a first storage area for storing programs or instructions and a second storage area for storing data, wherein the first storage area may store an operating system, an application program or instruction required for at least one function (such as a sound playback function, an image playback function, etc.), etc. In addition, the memory 709 may include a volatile memory or a non-volatile memory, or the memory 709 may include both volatile and non-volatile memories. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), a static random access memory (SRAM), a dynamic random access memory (DRAM), a synchronous dynamic random access memory (SDRAM), a double data rate synchronous dynamic random access memory (DDRSDRAM), an enhanced synchronous dynamic random access memory (ESDRAM), a synchronous link dynamic random access memory (SLDRAM) and a direct memory bus random access memory (DRRAM). The memory 709 in the embodiment of the present application includes but is not limited to these and any other suitable types of memory.

[0620] The processor 710 may include one or more processing units; optionally, the processor 710 integrates an application processor and a modem processor, wherein the application processor mainly processes operations related to an operating system, a user interface, and application programs, and the modem processor mainly processes wireless communication signals, such as a baseband processor. It is understandable that the modem processor may not be integrated into the processor 710.

[0621] The radio frequency unit 701 is configured to send a target message, where the target message is used for at least one of the following:

[0622] Indicating a repetition-related function of a downlink channel supported by the terminal;

[0623] Requesting to send a downlink transmission corresponding to a repeat-related function of a downlink channel to the terminal;

[0624] The downlink channel includes at least one of the following:

[0625] Public PDCCH, public PDSCH.

[0626] Optionally, the public PDCCH includes at least one of the following:

[0627] The PDCCH that the terminal needs to receive before entering the connected state;

[0628] PDCCH transmitted on common PDCCH resources;

[0629] or,

[0630] The common PDSCH includes:

[0631] The PDSCH that the terminal needs to receive before entering the connected state.

[0632] Optionally, the target message includes at least one of the following:

[0633] PRACH, Msg1, Msg3 PUSCH, MsgA, MsgA PUSCH, messages sent by the terminal in the connected state.

[0634] Optionally, the PRACH is indicated or requested by at least one of the following:

[0635] The time domain resources of the PRACH, the frequency domain resources of the PRACH, the configuration index of the PRACH, the sequence of the PRACH, the scrambling sequence of the PRACH sequence, the format of the PRACH, and whether the PRACH is repeatedly transmitted;

[0636] or,

[0637] The MsgA PUSCH is indicated or requested by at least one of the following:

[0638] Information carried in the MsgA PUSCH, time domain resources of the MsgA PUSCH, frequency domain resources of the MsgA PUSCH, demodulation reference signal DMRS resources of the MsgA PUSCH, the group to which the MsgA PUSCH belongs, and whether the MsgAPUSCH is repeatedly transmitted;

[0639] or,

[0640] The MsgA indicates or requests at least one of the following:

[0641] The time domain resources of the MsgA, the frequency domain resources of the MsgA, and the DMRS resources of the MsgA;

[0642] or,

[0643] The Msg3 PUSCH is indicated or requested by at least one of the following:

[0644] Information carried in the Msg3 PUSCH, time domain resources of the Msg3 PUSCH, frequency domain resources of the Msg3 PUSCH, DMRS resources of the Msg3 PUSCH, payload size of the Msg3 PUSCH, and whether the Msg3 PUSCH is repeatedly transmitted;

[0645] or,

[0646] The Msg1 is used to indicate the payload size of the Msg3 PUSCH or whether the Msg3 PUSCH is to be repeatedly transmitted, wherein the payload size of the Msg3 PUSCH or whether the Msg3 PUSCH is to be repeatedly transmitted is used for indication or request;

[0647] The indication includes: indicating a repetition-related function of a downlink channel supported by the terminal, and the request includes: requesting to send a downlink transmission corresponding to the repetition-related function of the downlink channel to the terminal.

[0648] Optionally, the target message is used to indicate at least one of the following:

[0649] The priority of the terminal, the type of the terminal, the frequency band of the terminal, and the capability level of the terminal;

[0650] The priority of the terminal is used to indicate a repetition-related function of a downlink channel supported by the terminal, or to request that a downlink transmission corresponding to the repetition-related function of the downlink channel be sent to the terminal;

[0651] The type of the terminal is used to indicate a repetition-related function of a downlink channel supported by the terminal, or to request that a downlink transmission corresponding to the repetition-related function of a downlink channel be sent to the terminal;

[0652] The frequency band where the terminal is located is used to indicate a repetition-related function of a downlink channel supported by the terminal, or to request that a downlink transmission corresponding to the repetition-related function of the downlink channel be sent to the terminal;

[0653] The capability level of the terminal is used to indicate the repetition-related function of the downlink channel supported by the terminal, or to request to send a downlink transmission corresponding to the repetition-related function of the downlink channel to the terminal.

[0654] Optionally, the repetition-related functions of the downlink channel include at least one of the following:

[0655] Repeated transmission of the downlink channel;

[0656] The receiving window of the downlink channel is extended;

[0657] allowing repeated transmission of the downlink channel to exceed a receiving window corresponding to the downlink channel;

[0658] The timer corresponding to the downlink channel is extended;

[0659] The repeated transmission of the downlink channel is allowed to exceed the duration of the timer corresponding to the downlink channel.

[0660] Optionally, the receiving window of the downlink channel includes at least one of the following: a RAR window, a MsgB response window; or,

[0661] The timer corresponding to the downlink channel includes: a contention resolution timer.

[0662] Optionally, the repeated transmission of the downlink channel includes at least one of the following:

[0663] Repeated transmission of the downlink channel of a transmission reception point TRP;

[0664] Repeated transmission of the downlink channel between multiple TRPs;

[0665] repeated transmission of said downlink channel based on available time slots;

[0666] Repeated transmission of the downlink channel based on physical time slots;

[0667] supporting repeated transmission of the downlink channel with an extended receiving window of the downlink channel;

[0668] Repeated transmission of the downlink channel with an extended reception window of the downlink channel is not supported;

[0669] Supporting repeated transmission of the downlink channel that allows repeated transmission of the downlink channel exceeding a receiving window corresponding to the downlink channel;

[0670] Not supporting the repeated transmission of the downlink channel that allows the repeated transmission of the downlink channel to exceed the receiving window corresponding to the downlink channel;

[0671] Supporting repeated transmission of the downlink channel with an extended timer corresponding to the downlink channel;

[0672] not supporting repeated transmission of the downlink channel with the timer corresponding to the downlink channel extended;

[0673] Supporting repeated transmission of the downlink channel that allows repeated transmission of the downlink channel to exceed the duration of a timer corresponding to the downlink channel;

[0674] not supporting repeated transmission of the downlink channel that allows repeated transmission of the downlink channel to exceed the duration of the timer corresponding to the downlink channel;

[0675] repeated transmission of said downlink channel within a time slot;

[0676] repeated transmission of said downlink channel between time slots;

[0677] Repeated transmission of the downlink channel within a control resource set;

[0678] Repeated transmission of the downlink channel between control resource sets;

[0679] Repeated transmission of the downlink channel within a common search space CSS;

[0680] repeated transmission of said downlink channel between CSSs;

[0681] Repeated transmission of the downlink channel within a monitoring opportunity;

[0682] repeated transmission of said downlink channel between monitoring opportunities;

[0683] Time domain repeated transmission of the downlink channel;

[0684] Frequency domain repeated transmission of the downlink channel;

[0685] Dynamically repeating transmission of the downlink channel;

[0686] Semi-static repetitive transmission of the downlink channel;

[0687] Repeated transmission of the downlink channel before radio resource control RRC connection establishment;

[0688] Repeated transmission of the downlink channel before receiving a dedicated PDSCH configuration.

[0689] Optionally, in the case where the repeated transmission of the downlink channel includes multiple repeated transmissions, the multiple repeated transmissions are independent terminal capabilities, or the multiple repeated transmissions are combined terminal capabilities; or,

[0690] In the case where the repeated transmission of the downlink channel includes multiple repeated transmissions, the multiple repeated transmissions are indicated by the same target message, or the multiple repeated transmissions are indicated by at least two target messages.

[0691] Optionally, the repeated transmission of the downlink channel is defined based on the granularity of terminal type, or the repeated transmission of the downlink channel is defined based on the granularity of terminal priority.

[0692] Optionally, the repetitive transmission capability of the downlink channel matches a target downlink channel repetitive transmission capability, and the target downlink channel repetitive transmission capability is the downlink channel repetitive transmission capability after the terminal enters a connected state.

[0693] Optionally, in a case where the terminal supports repeated transmission of the downlink channel, the terminal supports extension of a receiving window of the downlink channel; or

[0694] In the case where the terminal supports repeated transmission of the downlink channel, the terminal supports: allowing repeated transmission of the downlink channel to exceed a receiving window corresponding to the downlink channel; or

[0695] In a case where the terminal supports repeated transmission of the downlink channel, the terminal supports extension of a timer corresponding to the downlink channel; or

[0696] In a case where the terminal supports repeated transmission of the downlink channel, the terminal supports: allowing repeated transmission of the downlink channel to exceed a duration of a timer corresponding to the downlink channel.

[0697] Optionally, when the repeated related functions of the downlink channel include multiple functions, the multiple functions are indicated by the same target message, or the multiple functions are indicated by at least two target messages.

[0698] Optionally, the terminal sends a target message, including:

[0699] The terminal sends the target message under a target condition, where the target condition includes at least one of the following:

[0700] A reference signal received power RSRP of a downlink signal is higher than or equal to a first threshold;

[0701] A reference signal received quality RSRQ of the downlink signal is higher than or equal to a second threshold;

[0702] The uplink channel corresponding to the downlink channel performs repeated transmission, or the uplink channel corresponding to the downlink channel does not perform repeated transmission;

[0703] Using the same repetition request condition for all or part of the downlink channels;

[0704] The RSRP thresholds for all or part of the downlink channels are the same, or the RSRP thresholds for all or part of the downlink channels are different,

[0705] The RSRQ thresholds for all or part of the downlink channels are the same, or the RSRQ thresholds for all or part of the downlink channels are different.

[0706] Optionally, the public PDSCH includes at least one of the following:

[0707] Msg2 PDSCH, MsgB PDSCH, Msg4 PDSCH; or,

[0708] The public PDCCH includes at least one of the following:

[0709] SIB1 PDCCH, OSI PDCCH, Msg2 PDCCH, Msg4 PDCCH, MsgB PDCCH, paging PDCCH, and PDCCH scheduling Msg3 retransmission.

[0710] Optionally, the radio frequency unit 701 is further configured to:

[0711] In a case where the terminal does not send the target message, receiving configuration information, where the configuration information is used to configure repeated transmission resources of the downlink channel;

[0712] Wherein, in the case of a repetition-related function of a downlink channel supported by the terminal, the terminal performs blind detection on the repeated transmission resources of the downlink channel and the non-repetitive transmission resources of the downlink channel; or, in the case of a repetition-related function of a downlink channel not supported by the terminal, the terminal performs blind detection on the non-repetitive transmission resources of the downlink channel.

[0713] The above terminal can improve the service performance of the terminal.

[0714] It can be understood that the implementation process of each implementation method mentioned in this embodiment can refer to the relevant description of the above-mentioned method embodiment, and achieve the same or corresponding technical effect. To avoid repetition, it will not be repeated here.

[0715] An embodiment of the present application also provides a network side device, including a processor and a communication interface, wherein the communication interface is used to receive a target message sent by a terminal, and the target message is used for at least one of the following: indicating the repetition-related functions of the downlink channel supported by the terminal; requesting to send a downlink transmission corresponding to the repetition-related functions of the downlink channel to the terminal; wherein the downlink channel includes at least one of the following: a common PDCCH and a common PDSCH.

[0716] like Figure 8As shown, the network side device 800 includes: an antenna 801, a radio frequency device 802, a baseband device 803, a processor 804 and a memory 805. The antenna 801 is connected to the radio frequency device 802. In the uplink direction, the radio frequency device 802 receives information through the antenna 801 and sends the received information to the baseband device 803 for processing. In the downlink direction, the baseband device 803 processes the information to be sent and sends it to the radio frequency device 802. The radio frequency device 802 processes the received information and sends it out through the antenna 801.

[0717] The method executed by the wireless access network device in the above embodiment may be implemented in the baseband device 803, which includes a baseband processor.

[0718] The baseband device 803 may include, for example, at least one baseband board on which a plurality of chips are arranged. Figure 8 As shown, one of the chips is, for example, a baseband processor, which is connected to the memory 805 through a bus interface to call the program in the memory 805 to execute the network device operations shown in the above method embodiment.

[0719] The radio access network device may further include a network interface 806, which is, for example, a common public radio interface (CPRI).

[0720] Specifically, the network side device 800 of the embodiment of the present invention further includes: instructions or programs stored in the memory 805 and executable on the processor 804, and the processor 804 calls the instructions or programs in the memory 805 to execute Figure 5 The methods executed by the modules shown achieve the same technical effects, and therefore will not be described here in detail to avoid repetition.

[0721] The radio frequency device 802 is used to receive a target message sent by a terminal, where the target message is used for at least one of the following:

[0722] Indicating a repetition-related function of a downlink channel supported by the terminal;

[0723] Requesting to send a downlink transmission corresponding to a repeat-related function of a downlink channel to the terminal;

[0724] The downlink channel includes at least one of the following:

[0725] Common physical downlink control channel PDCCH, common physical downlink shared channel PDSCH.

[0726] Optionally, the public PDCCH includes at least one of the following:

[0727] A PDCCH that needs to be sent before the terminal enters a connected state;

[0728] PDCCH transmitted on common PDCCH resources;

[0729] or,

[0730] The common PDSCH includes:

[0731] The received PDSCH is sent before the terminal enters the connected state.

[0732] Optionally, the target message includes at least one of the following:

[0733] Physical random access channel PRACH, Msg1, Msg3 PUSCHMsgA, MsgA PUSCH, messages sent by the terminal in the connected state.

[0734] Optionally, the PRACH is indicated or requested by at least one of the following:

[0735] The time domain resources of the PRACH, the frequency domain resources of the PRACH, the configuration index of the PRACH, the sequence of the PRACH, the scrambling sequence of the PRACH sequence, the format of the PRACH, and whether the PRACH is repeatedly transmitted;

[0736] or,

[0737] The MsgA PUSCH is indicated or requested by at least one of the following:

[0738] Information carried in the MsgA PUSCH, time domain resources of the MsgA PUSCH, frequency domain resources of the MsgA PUSCH, demodulation reference signal DMRS resources of the MsgA PUSCH, the group to which the MsgA PUSCH belongs, and whether the MsgAPUSCH is repeatedly transmitted;

[0739] or,

[0740] The MsgA indicates or requests at least one of the following:

[0741] The time domain resources of the MsgA, the frequency domain resources of the MsgA, and the DMRS resources of the MsgA;

[0742] or,

[0743] The Msg3 PUSCH is indicated or requested by at least one of the following:

[0744] Information carried in the Msg3 PUSCH, time domain resources of the Msg3 PUSCH, frequency domain resources of the Msg3 PUSCH, DMRS resources of the Msg3 PUSCH, payload size of the Msg3 PUSCH, and whether the Msg3 PUSCH is repeatedly transmitted;

[0745] or,

[0746] The Msg1 is used to indicate the payload size of the Msg3 PUSCH or whether the Msg3 PUSCH is to be repeatedly transmitted, wherein the payload size of the Msg3 PUSCH or whether the Msg3 PUSCH is to be repeatedly transmitted is used for indication or request;

[0747] The indication includes: indicating a repetition-related function of a downlink channel supported by the terminal, and the request includes: requesting to send a downlink transmission corresponding to the repetition-related function of the downlink channel to the terminal.

[0748] Optionally, the target message is used to indicate at least one of the following:

[0749] The priority of the terminal, the type of the terminal, the frequency band of the terminal, and the capability level of the terminal;

[0750] The priority of the terminal is used to indicate a repetition-related function of a downlink channel supported by the terminal, or to request that a downlink transmission corresponding to the repetition-related function of the downlink channel be sent to the terminal;

[0751] The type of the terminal is used to indicate a repetition-related function of a downlink channel supported by the terminal, or to request that a downlink transmission corresponding to the repetition-related function of a downlink channel be sent to the terminal;

[0752] The frequency band where the terminal is located is used to indicate a repetition-related function of a downlink channel supported by the terminal, or to request that a downlink transmission corresponding to the repetition-related function of the downlink channel be sent to the terminal;

[0753] The capability level of the terminal is used to indicate the repetition-related function of the downlink channel supported by the terminal, or to request to send a downlink transmission corresponding to the repetition-related function of the downlink channel to the terminal.

[0754] Optionally, the repetition-related functions of the downlink channel include at least one of the following:

[0755] Repeated transmission of the downlink channel;

[0756] The receiving window of the downlink channel is extended;

[0757] allowing repeated transmission of the downlink channel to exceed a receiving window corresponding to the downlink channel;

[0758] The timer corresponding to the downlink channel is extended;

[0759] The repeated transmission of the downlink channel is allowed to exceed the duration of the timer corresponding to the downlink channel.

[0760] Optionally, the receiving window of the downlink channel includes at least one of the following: a RAR window, a MsgB response window; or,

[0761] The timer corresponding to the downlink channel includes: a contention resolution timer.

[0762] Optionally, the repeated transmission of the downlink channel includes at least one of the following:

[0763] Repeated transmission of the downlink channel of a transmission reception point TRP;

[0764] Repeated transmission of the downlink channel between multiple TRPs;

[0765] repeated transmission of said downlink channel based on available time slots;

[0766] Repeated transmission of the downlink channel based on physical time slots;

[0767] supporting repeated transmission of the downlink channel with an extended receiving window of the downlink channel;

[0768] Repeated transmission of the downlink channel with an extended reception window of the downlink channel is not supported;

[0769] Supporting repeated transmission of the downlink channel that allows repeated transmission of the downlink channel exceeding a receiving window corresponding to the downlink channel;

[0770] Not supporting the repeated transmission of the downlink channel that allows the repeated transmission of the downlink channel to exceed the receiving window corresponding to the downlink channel;

[0771] Supporting repeated transmission of the downlink channel with an extended timer corresponding to the downlink channel;

[0772] not supporting repeated transmission of the downlink channel with the timer corresponding to the downlink channel extended;

[0773] Supporting repeated transmission of the downlink channel that allows repeated transmission of the downlink channel to exceed the duration of a timer corresponding to the downlink channel;

[0774] not supporting repeated transmission of the downlink channel that allows repeated transmission of the downlink channel to exceed the duration of the timer corresponding to the downlink channel;

[0775] repeated transmission of said downlink channel within a time slot;

[0776] repeated transmission of said downlink channel between time slots;

[0777] Repeated transmission of the downlink channel within a control resource set;

[0778] Repeated transmission of the downlink channel between control resource sets;

[0779] Repeated transmission of the downlink channel within a common search space CSS;

[0780] repeated transmission of said downlink channel between CSSs;

[0781] Repeated transmission of the downlink channel within a monitoring opportunity;

[0782] repeated transmission of said downlink channel between monitoring opportunities;

[0783] Time domain repeated transmission of the downlink channel;

[0784] Frequency domain repeated transmission of the downlink channel;

[0785] Dynamically repeating transmission of the downlink channel;

[0786] Semi-static repetitive transmission of the downlink channel;

[0787] Repeated transmission of the downlink channel before radio resource control RRC connection establishment;

[0788] Repeated transmission of the downlink channel before receiving a dedicated PDSCH configuration.

[0789] Optionally, in the case where the repeated transmission of the downlink channel includes multiple repeated transmissions, the multiple repeated transmissions are independent terminal capabilities, or the multiple repeated transmissions are combined terminal capabilities; or,

[0790] In the case where the repeated transmission of the downlink channel includes multiple repeated transmissions, the multiple repeated transmissions are indicated by the same target message, or the multiple repeated transmissions are indicated by at least two target messages.

[0791] Optionally, the repeated transmission of the downlink channel is defined based on the granularity of terminal type, or the repeated transmission of the downlink channel is defined based on the granularity of terminal priority.

[0792] Optionally, the repetitive transmission capability of the downlink channel matches a target downlink channel repetitive transmission capability, and the target downlink channel repetitive transmission capability is the downlink channel repetitive transmission capability after the terminal enters a connected state.

[0793] Optionally, when the terminal supports repeated transmission of the downlink channel, determining that the terminal supports extension of a receiving window of the downlink channel; or

[0794] In a case where the terminal supports repeated transmission of the downlink channel, determining that the terminal supports: allowing repeated transmission of the downlink channel to exceed a receiving window corresponding to the downlink channel; or

[0795] In a case where the terminal supports repeated transmission of the downlink channel, determining that the terminal supports extension of a timer corresponding to the downlink channel; or

[0796] In a case where the terminal supports repeated transmission of the downlink channel, it is determined that the terminal supports: allowing repeated transmission of the downlink channel to exceed a duration of a timer corresponding to the downlink channel.

[0797] Optionally, when the repeated related functions of the downlink channel include multiple functions, the multiple functions are indicated by the same target message, or the multiple functions are indicated by at least two target messages.

[0798] Optionally, the public PDSCH includes at least one of the following:

[0799] Msg2 PDSCH, MsgB PDSCH, Msg4 PDSCH; or,

[0800] The public PDCCH includes at least one of the following:

[0801] SIB1 PDCCH, OSI PDCCH, Msg2 PDCCH, Msg4 PDCCH, MsgB PDCCH, paging PDCCH, and PDCCH scheduling Msg3 retransmission.

[0802] Optionally, the radio frequency device 802 is further used for:

[0803] In case that the target message sent by the terminal is not received, configuration information is sent to the terminal, where the configuration information is used to configure repeated transmission resources of the downlink channel.

[0804] The above network side equipment can improve the service performance of the terminal.

[0805] An embodiment of the present application also provides a readable storage medium, on which a program or instruction is stored. When the program or instruction is executed by a processor, each process of the above-mentioned message sending method or message receiving method embodiment is implemented, and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

[0806] The processor is the processor in the terminal described in the above embodiment. The readable storage medium includes a computer readable storage medium, such as a computer read-only memory ROM, a random access memory RAM, a magnetic disk or an optical disk. In some examples, the readable storage medium may be a non-transient readable storage medium.

[0807] An embodiment of the present application further provides a chip, which includes a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the various processes of the above-mentioned message sending method or message receiving method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0808] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.

[0809] The embodiments of the present application further provide a computer program / program product, which is stored in a storage medium, and is executed by at least one processor to implement the various processes of the above-mentioned message sending method or message receiving method embodiments, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0810] An embodiment of the present application also provides a wireless communication system, including: a terminal and a network side device, wherein the terminal can be used to execute the steps of the message sending method provided in the embodiment of the present application, and the network side device can be used to execute the steps of the message receiving method provided in the embodiment of the present application.

[0811] It should be noted that, in this article, the terms "comprise", "include" or any other variant thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the sentence "comprises one..." does not exclude the presence of other identical elements in the process, method, article or device including the element. In addition, it should be pointed out that the scope of the method and device in the embodiment of the present application is not limited to performing functions in the order shown or discussed, and may also include performing functions in a substantially simultaneous manner or in reverse order according to the functions involved, for example, the described method may be performed in an order different from that described, and various steps may also be added, omitted or combined. In addition, the features described with reference to certain examples may be combined in other examples.

[0812] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of a computer software product plus a necessary general hardware platform, and of course, can also be implemented by hardware. The computer software product is stored in a storage medium (such as ROM, RAM, disk, CD, etc.), including several instructions to enable a terminal or a network-side device to execute the methods described in each embodiment of the present application.

[0813] The embodiments of the present application are described above in conjunction with the accompanying drawings, but the present application is not limited to the above-mentioned specific implementation methods. The above-mentioned specific implementation methods are merely illustrative and not restrictive. Under the guidance of the present application, ordinary technicians in this field can also make many forms of implementation methods without departing from the purpose of the present application and the scope of protection of the claims, and these implementation methods are all within the protection of the present application.

Claims

1. A message sending method, characterized in that: include: The terminal sends a target message, where the target message is used for at least one of the following: Indicating a repetition-related function of a downlink channel supported by the terminal; Requesting to send a downlink transmission corresponding to a repeat-related function of a downlink channel to the terminal; The downlink channel includes at least one of the following: Common physical downlink control channel PDCCH, common physical downlink shared channel PDSCH.

2. The method according to claim 1, characterized in that The public PDCCH includes at least one of the following: The PDCCH that the terminal needs to receive before entering the connected state; PDCCH transmitted on common PDCCH resources; or, The public PDSCH includes: The PDSCH that the terminal needs to receive before entering the connected state.

3. The method according to claim 1 or 2, characterized in that The target message includes at least one of the following: Physical random access channel PRACH, message 1 Msg1, message 3 Msg3 PUSCH, message A MsgA, MsgA PUSCH, and messages sent by the terminal in the connected state.

4. The method according to claim 3, characterized in that The PRACH is indicated or requested by at least one of the following: The time domain resources of the PRACH, the frequency domain resources of the PRACH, the configuration index of the PRACH, the sequence of the PRACH, the scrambling sequence of the PRACH sequence, the format of the PRACH, and whether the PRACH is repeatedly transmitted; or, The MsgA PUSCH is indicated or requested by at least one of the following: Information carried in the MsgA PUSCH, time domain resources of the MsgA PUSCH, frequency domain resources of the MsgA PUSCH, demodulation reference signal DMRS resources of the MsgA PUSCH, the group to which the MsgA PUSCH belongs, and whether the MsgAPUSCH is repeatedly transmitted; or, The MsgA indicates or requests at least one of the following: The time domain resources of the MsgA, the frequency domain resources of the MsgA, and the DMRS resources of the MsgA; or, The Msg3 PUSCH is indicated or requested by at least one of the following: Information carried in the Msg3 PUSCH, time domain resources of the Msg3 PUSCH, frequency domain resources of the Msg3 PUSCH, DMRS resources of the Msg3 PUSCH, payload size of the Msg3 PUSCH, and whether the Msg3 PUSCH is repeatedly transmitted; or, The Msg1 is used to indicate the payload size of the Msg3 PUSCH or whether the Msg3 PUSCH is to be repeatedly transmitted, wherein the payload size of the Msg3 PUSCH or whether the Msg3 PUSCH is to be repeatedly transmitted is used for indication or request; The indication includes: indicating a repetition-related function of a downlink channel supported by the terminal, and the request includes: requesting to send a downlink transmission corresponding to the repetition-related function of the downlink channel to the terminal.

5. The method according to claim 1 or 2, characterized in that: The target message is used to indicate at least one of the following: The priority of the terminal, the type of the terminal, the frequency band of the terminal, and the capability level of the terminal; The priority of the terminal is used to indicate a repetition-related function of a downlink channel supported by the terminal, or to request that a downlink transmission corresponding to the repetition-related function of the downlink channel be sent to the terminal; The type of the terminal is used to indicate a repetition-related function of a downlink channel supported by the terminal, or to request that a downlink transmission corresponding to the repetition-related function of a downlink channel be sent to the terminal; The frequency band where the terminal is located is used to indicate a repetition-related function of a downlink channel supported by the terminal, or to request that a downlink transmission corresponding to the repetition-related function of the downlink channel be sent to the terminal; The capability level of the terminal is used to indicate the repetition-related function of the downlink channel supported by the terminal, or to request to send a downlink transmission corresponding to the repetition-related function of the downlink channel to the terminal.

6. The method according to any one of claims 1 to 5, characterized in that The repetition-related functions of the downlink channel include at least one of the following: Repeated transmission of the downlink channel; The receiving window of the downlink channel is extended; allowing repeated transmission of the downlink channel to exceed a receiving window corresponding to the downlink channel; The timer corresponding to the downlink channel is extended; The repeated transmission of the downlink channel is allowed to exceed the duration of the timer corresponding to the downlink channel.

7. The method according to claim 6, characterized in that The receiving window of the downlink channel includes at least one of the following: a random access response RAR window, a message B MsgB response window; or, The timer corresponding to the downlink channel includes: a contention resolution timer.

8. The method according to claim 6 or 7, characterized in that The repeated transmission of the downlink channel includes at least one of the following: Repeated transmission of the downlink channel of a transmission reception point TRP; Repeated transmission of the downlink channel between multiple TRPs; repeated transmission of said downlink channel based on available time slots; Repeated transmission of the downlink channel based on physical time slots; supporting repeated transmission of the downlink channel with an extended receiving window of the downlink channel; Repeated transmission of the downlink channel with an extended reception window of the downlink channel is not supported; Supporting repeated transmission of the downlink channel that allows repeated transmission of the downlink channel exceeding a receiving window corresponding to the downlink channel; Not supporting the repeated transmission of the downlink channel that allows the repeated transmission of the downlink channel to exceed the receiving window corresponding to the downlink channel; Supporting repeated transmission of the downlink channel with an extended timer corresponding to the downlink channel; not supporting repeated transmission of the downlink channel with the timer corresponding to the downlink channel extended; Supporting repeated transmission of the downlink channel that allows repeated transmission of the downlink channel to exceed the duration of a timer corresponding to the downlink channel; not supporting repeated transmission of the downlink channel that allows repeated transmission of the downlink channel to exceed the duration of the timer corresponding to the downlink channel; repeated transmission of said downlink channel within a time slot; repeated transmission of said downlink channel between time slots; Repeated transmission of the downlink channel within a control resource set; Repeated transmission of the downlink channel between control resource sets; Repeated transmission of the downlink channel within a common search space CSS; repeated transmission of said downlink channel between CSSs; Repeated transmission of the downlink channel within a monitoring opportunity; repeated transmission of said downlink channel between monitoring opportunities; Time domain repeated transmission of the downlink channel; Frequency domain repeated transmission of the downlink channel; Dynamically repeating transmission of the downlink channel; Semi-static repetitive transmission of the downlink channel; Repeated transmission of the downlink channel before radio resource control RRC connection establishment; Repeated transmission of the downlink channel before receiving a dedicated PDSCH configuration.

9. The method according to claim 8, characterized in that In the case where the repeated transmission of the downlink channel includes multiple repeated transmissions, the multiple repeated transmissions are independent terminal capabilities, or the multiple repeated transmissions are combined terminal capabilities; or, In the case where the repeated transmission of the downlink channel includes multiple repeated transmissions, the multiple repeated transmissions are indicated by the same target message, or the multiple repeated transmissions are indicated by at least two target messages.

10. The method according to any one of claims 6 to 9, characterized in that The repeated transmission of the downlink channel is defined based on the granularity of the terminal type, or the repeated transmission of the downlink channel is defined based on the granularity of the terminal priority.

11. The method according to any one of claims 6 to 10, characterized in that The repetitive transmission capability of the downlink channel matches the target downlink channel repetitive transmission capability, and the target downlink channel repetitive transmission capability is the downlink channel repetitive transmission capability after the terminal enters a connected state.

12. The method according to any one of claims 6 to 11, characterized in that In a case where the terminal supports repeated transmission of the downlink channel, the terminal supports extension of a receiving window of the downlink channel; or In the case where the terminal supports repeated transmission of the downlink channel, the terminal supports: allowing repeated transmission of the downlink channel to exceed a receiving window corresponding to the downlink channel; or In a case where the terminal supports repeated transmission of the downlink channel, the terminal supports extension of a timer corresponding to the downlink channel; or In a case where the terminal supports repeated transmission of the downlink channel, the terminal supports: allowing repeated transmission of the downlink channel to exceed a duration of a timer corresponding to the downlink channel.

13. The method according to any one of claims 6 to 12, characterized in that In the case that the repeated related functions of the downlink channel include multiple functions, the multiple functions are indicated by the same target message, or the multiple functions are indicated by at least two target messages.

14. The method according to any one of claims 1 to 13, characterized in that The terminal sends a target message, including: The terminal sends the target message under a target condition, where the target condition includes at least one of the following: A reference signal received power RSRP of a downlink signal is higher than or equal to a first threshold; A reference signal received quality RSRQ of the downlink signal is higher than or equal to a second threshold; The uplink channel corresponding to the downlink channel performs repeated transmission, or the uplink channel corresponding to the downlink channel does not perform repeated transmission; Using the same repetition request condition for all or part of the downlink channels; The RSRP thresholds for all or part of the downlink channels are the same, or the RSRP thresholds for all or part of the downlink channels are different, The RSRQ thresholds for all or part of the downlink channels are the same, or the RSRQ thresholds for all or part of the downlink channels are different.

15. The method according to any one of claims 1 to 14, characterized in that The public PDSCH includes at least one of the following: Message 2 Msg2 PDSCH, message B MsgB PDSCH, message 4 Msg4 PDSCH; or, The public PDCCH includes at least one of the following: System message block 1 SIB1 PDCCH, other system messages OSI PDCCH, Msg2 PDCCH, Msg4 PDCCH, MsgBPDCCH, paging PDCCH, and PDCCH scheduling Msg3 retransmission.

16. The method according to any one of claims 1 to 15, characterized in that The method further comprises: In a case where the terminal does not send the target message, the terminal receives configuration information, where the configuration information is used to configure repeated transmission resources of the downlink channel; Wherein, in the case of a repetition-related function of a downlink channel supported by the terminal, the terminal performs blind detection on the repeated transmission resources of the downlink channel and the non-repetitive transmission resources of the downlink channel; or, in the case of a repetition-related function of a downlink channel not supported by the terminal, the terminal performs blind detection on the non-repetitive transmission resources of the downlink channel.

17. A message receiving method, characterized in that: include: The network side device receives a target message sent by the terminal, where the target message is used for at least one of the following: Indicating a repetition-related function of a downlink channel supported by the terminal; Requesting to send a downlink transmission corresponding to a repeat-related function of a downlink channel to the terminal; The downlink channel includes at least one of the following: Common physical downlink control channel PDCCH, common physical downlink shared channel PDSCH.

18. The method according to claim 17, characterized in that The public PDCCH includes at least one of the following: A PDCCH that needs to be sent before the terminal enters a connected state; PDCCH transmitted on common PDCCH resources; or, The public PDSCH includes: The received PDSCH is sent before the terminal enters the connected state.

19. The method according to claim 17 or 18, characterized in that The target message includes at least one of the following: Physical random access channel PRACH, message 1 Msg1, message 3 Msg3 PUSCH, message A MsgA, MsgA PUSCH, and messages sent by the terminal in the connected state.

20. The method of claim 19, wherein: The PRACH is indicated or requested by at least one of the following: The time domain resources of the PRACH, the frequency domain resources of the PRACH, the configuration index of the PRACH, the sequence of the PRACH, the scrambling sequence of the PRACH sequence, the format of the PRACH, and whether the PRACH is repeatedly transmitted; or, The MsgA PUSCH is indicated or requested by at least one of the following: Information carried in the MsgA PUSCH, time domain resources of the MsgA PUSCH, frequency domain resources of the MsgA PUSCH, demodulation reference signal DMRS resources of the MsgA PUSCH, the group to which the MsgA PUSCH belongs, and whether the MsgAPUSCH is repeatedly transmitted; or, The MsgA indicates or requests at least one of the following: The time domain resources of the MsgA, the frequency domain resources of the MsgA, and the DMRS resources of the MsgA; or, The Msg3 PUSCH is indicated or requested by at least one of the following: Information carried in the Msg3 PUSCH, time domain resources of the Msg3 PUSCH, frequency domain resources of the Msg3 PUSCH, DMRS resources of the Msg3 PUSCH, payload size of the Msg3 PUSCH, and whether the Msg3 PUSCH is repeatedly transmitted; or, The Msg1 is used to indicate the payload size of the Msg3 PUSCH or whether the Msg3 PUSCH is to be repeatedly transmitted, wherein the payload size of the Msg3 PUSCH or whether the Msg3 PUSCH is to be repeatedly transmitted is used for indication or request; The indication includes: indicating a repetition-related function of a downlink channel supported by the terminal, and the request includes: requesting to send a downlink transmission corresponding to the repetition-related function of the downlink channel to the terminal.

21. The method according to claim 17 or 18, characterized in that The target message is used to indicate at least one of the following: The priority of the terminal, the type of the terminal, the frequency band of the terminal, and the capability level of the terminal; The priority of the terminal is used to indicate a repetition-related function of a downlink channel supported by the terminal, or to request that a downlink transmission corresponding to the repetition-related function of the downlink channel be sent to the terminal; The type of the terminal is used to indicate a repetition-related function of a downlink channel supported by the terminal, or to request that a downlink transmission corresponding to the repetition-related function of a downlink channel be sent to the terminal; The frequency band where the terminal is located is used to indicate a repetition-related function of a downlink channel supported by the terminal, or to request that a downlink transmission corresponding to the repetition-related function of the downlink channel be sent to the terminal; The capability level of the terminal is used to indicate the repetition-related function of the downlink channel supported by the terminal, or to request to send a downlink transmission corresponding to the repetition-related function of the downlink channel to the terminal.

22. The method according to any one of claims 17 to 21, characterized in that The repetition-related functions of the downlink channel include at least one of the following: Repeated transmission of the downlink channel; The receiving window of the downlink channel is extended; allowing repeated transmission of the downlink channel to exceed a receiving window corresponding to the downlink channel; The timer corresponding to the downlink channel is extended; The repeated transmission of the downlink channel is allowed to exceed the duration of the timer corresponding to the downlink channel.

23. The method of claim 22, wherein: The receiving window of the downlink channel includes at least one of the following: a random access response RAR window, a message B MsgB response window; or, The timer corresponding to the downlink channel includes: a contention resolution timer.

24. The method according to claim 22 or 23, characterized in that The repeated transmission of the downlink channel includes at least one of the following: Repeated transmission of the downlink channel of a transmission reception point TRP; Repeated transmission of the downlink channel between multiple TRPs; repeated transmission of said downlink channel based on available time slots; Repeated transmission of the downlink channel based on physical time slots; supporting repeated transmission of the downlink channel with an extended receiving window of the downlink channel; Repeated transmission of the downlink channel with an extended reception window of the downlink channel is not supported; Supporting repeated transmission of the downlink channel that allows repeated transmission of the downlink channel exceeding a receiving window corresponding to the downlink channel; Not supporting the repeated transmission of the downlink channel that allows the repeated transmission of the downlink channel to exceed the receiving window corresponding to the downlink channel; Supporting repeated transmission of the downlink channel with an extended timer corresponding to the downlink channel; not supporting repeated transmission of the downlink channel with the timer corresponding to the downlink channel extended; Supporting repeated transmission of the downlink channel that allows repeated transmission of the downlink channel to exceed the duration of a timer corresponding to the downlink channel; not supporting repeated transmission of the downlink channel that allows repeated transmission of the downlink channel to exceed the duration of the timer corresponding to the downlink channel; repeated transmission of said downlink channel within a time slot; repeated transmission of said downlink channel between time slots; Repeated transmission of the downlink channel within a control resource set; Repeated transmission of the downlink channel between control resource sets; Repeated transmission of the downlink channel within a common search space CSS; repeated transmission of said downlink channel between CSSs; Repeated transmission of the downlink channel within a monitoring opportunity; repeated transmission of said downlink channel between monitoring opportunities; Time domain repeated transmission of the downlink channel; Frequency domain repeated transmission of the downlink channel; Dynamically repeating transmission of the downlink channel; Semi-static repetitive transmission of the downlink channel; Repeated transmission of the downlink channel before radio resource control RRC connection establishment; Repeated transmission of the downlink channel before receiving a dedicated PDSCH configuration.

25. The method of claim 24, wherein: In the case where the repeated transmission of the downlink channel includes multiple repeated transmissions, the multiple repeated transmissions are independent terminal capabilities, or the multiple repeated transmissions are combined terminal capabilities; or, In the case where the repeated transmission of the downlink channel includes multiple repeated transmissions, the multiple repeated transmissions are indicated by the same target message, or the multiple repeated transmissions are indicated by at least two target messages.

26. The method according to any one of claims 22 to 25, characterized in that The repeated transmission of the downlink channel is defined based on the granularity of the terminal type, or the repeated transmission of the downlink channel is defined based on the granularity of the terminal priority.

27. The method according to any one of claims 22 to 26, characterized in that The repetitive transmission capability of the downlink channel matches the target downlink channel repetitive transmission capability, and the target downlink channel repetitive transmission capability is the downlink channel repetitive transmission capability after the terminal enters a connected state.

28. The method according to any one of claims 22 to 27, characterized in that In a case where the terminal supports repeated transmission of the downlink channel, determining that the terminal supports extension of a receiving window of the downlink channel; or In a case where the terminal supports repeated transmission of the downlink channel, determining that the terminal supports: allowing repeated transmission of the downlink channel to exceed a receiving window corresponding to the downlink channel; or In a case where the terminal supports repeated transmission of the downlink channel, determining that the terminal supports extension of a timer corresponding to the downlink channel; or In a case where the terminal supports repeated transmission of the downlink channel, it is determined that the terminal supports: allowing repeated transmission of the downlink channel to exceed a duration of a timer corresponding to the downlink channel.

29. The method according to any one of claims 22 to 28, characterized in that In the case that the repeated related functions of the downlink channel include multiple functions, the multiple functions are indicated by the same target message, or the multiple functions are indicated by at least two target messages.

30. The method according to any one of claims 17 to 29, characterized in that The public PDSCH includes at least one of the following: Message 2 Msg2 PDSCH, message B MsgB PDSCH, message 4 Msg4 PDSCH; or, The public PDCCH includes at least one of the following: System message block 1 SIB1 PDCCH, other system messages OSI PDCCH, Msg2 PDCCH, Msg4 PDCCH, MsgBPDCCH, paging PDCCH, and PDCCH scheduling Msg3 retransmission.

31. The method according to any one of claims 17 to 30, characterized in that The method further comprises: In a case where the target message sent by the terminal is not received, the network side device sends configuration information to the terminal, where the configuration information is used to configure repeated transmission resources of the downlink channel.

32. A message sending device, characterized in that: include: The sending module is used to send a target message, where the target message is used for at least one of the following: Indicating a repetition-related function of a downlink channel supported by the terminal; Requesting to send a downlink transmission corresponding to a repeat-related function of a downlink channel to the terminal; The downlink channel includes at least one of the following: Common physical downlink control channel PDCCH, common physical downlink shared channel PDSCH.

33. A message receiving device, characterized in that: include: The receiving module is used to receive a target message sent by the terminal, where the target message is used for at least one of the following: Indicating a repetition-related function of a downlink channel supported by the terminal; Requesting to send a downlink transmission corresponding to a repeat-related function of a downlink channel to the terminal; The downlink channel includes at least one of the following: Common physical downlink control channel PDCCH, common physical downlink shared channel PDSCH.

34. A terminal, characterized in that: It includes a processor and a memory, the memory stores a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, the steps of the message sending method according to any one of claims 1 to 16 are implemented.

35. A network side device, characterized in that: It includes a processor and a memory, the memory stores a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, the steps of the message receiving method as described in any one of claims 17 to 31 are implemented.

36. A readable storage medium, characterized in that: The readable storage medium stores programs or instructions, and when the programs or instructions are executed by the processor, they implement the message sending method as described in any one of claims 1 to 16, or implement the steps of the message receiving method as described in any one of claims 17 to 31.

Images