[go: up one dir, main page]

WO2025011537A1 - 消息发送方法、消息接收方法、装置、终端及网络侧设备 - Google Patents

消息发送方法、消息接收方法、装置、终端及网络侧设备 Download PDF

Info

Publication number
WO2025011537A1
WO2025011537A1 PCT/CN2024/104382 CN2024104382W WO2025011537A1 WO 2025011537 A1 WO2025011537 A1 WO 2025011537A1 CN 2024104382 W CN2024104382 W CN 2024104382W WO 2025011537 A1 WO2025011537 A1 WO 2025011537A1
Authority
WO
WIPO (PCT)
Prior art keywords
downlink channel
terminal
repeated transmission
downlink
transmission
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
PCT/CN2024/104382
Other languages
English (en)
French (fr)
Inventor
林志鹏
王勇
姜炜
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Vivo Mobile Communication Co Ltd
Original Assignee
Vivo Mobile Communication Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Vivo Mobile Communication Co Ltd filed Critical Vivo Mobile Communication Co Ltd
Publication of WO2025011537A1 publication Critical patent/WO2025011537A1/zh
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/002—Transmission of channel access control information
    • H04W74/006—Transmission of channel access control information in the downlink, i.e. towards the terminal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access

Definitions

  • 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.
  • the terminal needs to receive some public downlink channels, such as receiving the public physical downlink control channel (PDCCH) and the public physical downlink shared channel (PDSCH).
  • some public downlink channels such as receiving the public physical downlink control channel (PDCCH) and the public physical downlink shared channel (PDSCH).
  • the public 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.
  • 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.
  • the terminal sends a target message, where the target message is used for at least one of the following:
  • Public PDCCH public PDSCH.
  • a message receiving method comprising:
  • 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:
  • the downlink channel includes at least one of the following:
  • Public PDCCH public PDSCH.
  • a message sending device including:
  • the downlink channel includes at least one of the following:
  • Public PDCCH public PDSCH.
  • a message receiving device comprising:
  • 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:
  • Public PDCCH public PDSCH.
  • a terminal 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.
  • a network side device 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.
  • 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.
  • a readable storage medium on which a program or instruction is stored.
  • 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.
  • 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.
  • 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 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.
  • a computer program/program product is provided, wherein the computer program/program product 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 sending method provided in the embodiment of the present application.
  • the steps of the message receiving method are provided.
  • 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.
  • 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.
  • FIG2 is a flow chart of a message sending method provided in an embodiment of the present application.
  • FIG3 is a flow chart of a message receiving method provided in an embodiment of the present application.
  • FIG4 is a structural diagram of a message sending device provided in an embodiment of the present application.
  • FIG6 is a structural diagram of a communication device provided in an embodiment of the present application.
  • FIG7 is a structural diagram of a terminal provided in an embodiment of the present application.
  • FIG8 is a structural diagram of a network-side device provided in an embodiment of the present application.
  • 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.
  • FIG1 shows a block diagram of a wireless communication system applicable to the embodiment of the present application.
  • the wireless communication system includes a terminal 11 and a network side device 12 .
  • 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 (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), a flight vehicle (flight vehicle), a vehicle user equipment (VUE), a shipborne equipment, 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
  • the network side device 12 may include an access network device or a core network device, wherein the access network device may also be called 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.
  • WLAN wireless Local Area Network
  • AP Access Point
  • WiFi wireless Fidelity
  • 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 (SMF), User Plane Function (UPF), Policy Control Function (PCF), Policy and Charging Rules Function (PCRF), Edge Application Server Discovery Function (EASDF), Unified Data Management (UDM), Unified Data Repository (UDR), Home Subscriber Server (HSS), Centralized Network Configuration (CNC), Network Repository Function (NRF), Network Exposure Function (NEF), Local NEF (or L-NEF), Binding Support Function (BSF), Application Function (AF), etc.
  • MME mobility management entity
  • AMF Access and Mobility Management Function
  • UPF User Plane Function
  • PCF Policy Control Function
  • PCF Policy and Charging Rules Function
  • EASDF Edge Application Server Discovery Function
  • UDM Unified Data Management
  • UDR Unified Data Repository
  • HSS
  • the terminal 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 sends 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 it sent, and then sends Msg3 containing contention resolution information according to the resources indicated by RAR; after receiving Msg3, the network sends message 4 (Msg4) containing contention resolution information; when the terminal receives Msg4, it confirms that the resolution information is consistent with that sent in Msg3, thus completing the 4-step random access.
  • Msg1 message 1
  • Msg2 message 2
  • RAR Random Access Response
  • the network includes the uplink grant (UL grant) information in the RAR to indicate the scheduling information of the Msg3 physical uplink shared channel (PUSCH), and includes the random access preamble ID (RAPID), temporary cell-radio network temporary identifier (TC-RNTI), timing advance (TA), etc. If the network does not receive the Msg3 PUSCH, it can schedule the retransmission of the Msg3 PUSCH in the physical downlink control channel (PDCCH) scrambled by TC-RNTI.
  • PDCCH physical downlink control channel
  • different terminals randomly select preambles for transmission. In this way, 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).
  • RACH Occasion, RO random access opportunity
  • This situation can be understood as a terminal preamble conflict.
  • different terminals will receive the same RAR.
  • different terminals will transmit Msg3PUSCH according to the scheduling information in the RAR UL grant.
  • the network 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. Therefore, 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 information is not correct. If there is no match, the contention resolution is considered unsuccessful.
  • the terminal reselects the RACH transmission resource, sends the Physical Random Access Channel (PRACH), and makes the next random access attempt.
  • PRACH Physical Random Access Channel
  • 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 MsgA preamble and MsgA PUSCH.
  • the preamble part is sent on the RO used for the two-step random access process
  • 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 slot, including time-frequency resources and demodulation reference signal (DMRS) resources.
  • DMRS demodulation reference signal
  • the above window starts from the first symbol of the control resource set (Control resource set, CORESET) in the Type1-PDCCH common search space set (Type1-PDCCH CSS set) after PRACH is sent.
  • the above window starts from the first symbol of the CORESET in the Type1-PDCCH CSS set after PRACH (MsgA PRACH part) sends the corresponding PUSCH (MsgA PUSCH part) resources.
  • the above window is actually controlled by the random access contention resolution timer (ra-ContentionResolutionTimer), which will be started or restarted after the Msg3 is sent (if Msg3 repetition is supported, it is the last repetition of the Msg3).
  • CORESET is a collection of time domain and frequency domain resources for control information.
  • CORESET#0 is a special CORESET, which is usually used to schedule the transmission of PDCCH of System Information Block (SIB) 1.
  • SIB System Information Block
  • 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).
  • CD-SSB Cell Defining Synchronization Signal Block
  • the main function of CORESET#0 is to define the time and frequency resources of Type0-PDCCH CSS and the size of the monitoring timing of Type0-PDCCH CSS.
  • FIG. 2 is a flow chart of a message sending method provided in an embodiment of the present application. As shown in FIG. 2, the method includes the following steps:
  • Step 201 The terminal sends a target message, where the target message is used for at least one of the following:
  • the downlink channel includes at least one of the following:
  • Public PDCCH public PDSCH.
  • the terminal sending the target message may be sending the target message to a network side device.
  • 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.
  • the repetition-related function of the downlink channel supported by the terminal means that the terminal supports the repetition transmission of the above-mentioned 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 (common PDCCH/PDSCH repetition).
  • 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.
  • 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.
  • the network side device After receiving the request, performs repeated transmission for the downlink channel, that is, repeatedly transmits the downlink channel to the terminal.
  • the target message 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.
  • the target message 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.
  • 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.
  • 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.
  • the network side device after sending the target message, the network side device sends repeated transmission of the downlink channel to the terminal based on the target message, and the terminal receives the repeated transmission of the uplink channel.
  • the public PDCCH includes at least one of the following:
  • the PDCCH that needs to be received before the terminal enters the connected state may include at least one of the following:
  • the above-mentioned common PDCCH may specifically include at least one of the following:
  • SIB1 PDCCH Other System Information (OSI) PDCCH
  • OSI System Information
  • Msg2 PDCCH Msg4 PDCCH
  • MsgB PDCCH paging PDCCH
  • PDCCH scheduling Msg3 retransmission Msg3 retransmission.
  • the above-mentioned 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, OSIPDCCH, Msg2 PDCCH, Msg4 PDCCH, MsgB PDCCH, Paging PDCCH, and PDCCH for scheduling Msg3 retransmission.
  • 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, OSIPDCCH, Msg2 PDCCH, Msg4 PDCCH, MsgB PDCCH, Paging PDCCH, and PDCCH for scheduling Msg3 retransmission.
  • the above-mentioned 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.
  • the PDCCH transmitted on the CORESET resources associated with the CSS is also called a broadcast PDCCH.
  • the public PDSCH includes at least one of the following:
  • the PDSCH that the terminal needs to receive before entering the connected state is the PDSCH that the terminal needs to receive before entering the connected state.
  • the PDSCH that needs to be received before the terminal enters the connected state may include at least one of the following:
  • Msg2 PDSCH MsgB PDSCH, Msg4 PDSCH, paging PDSCH.
  • the public PDSCH may specifically include at least one of the following:
  • 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.
  • the transmission repetition of the above-mentioned common PDCCH/PDSCH may also be referred to as common PDCCH/PDSCH repetition.
  • the repetition may be referred to as Msg2/MsgB/Msg4 PDSCH/PDCCH repetition.
  • the Msg2/MsgB/Msg4 PDSCH repetition may also be referred to as Msg2/MsgB/Msg4 repetition.
  • the message sent by the terminal in the connected state refers to the message sent by the terminal when it enters the connected state.
  • 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.
  • the PRACH is indicated or requested by at least one of the following:
  • 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.
  • multiple resources, indexes, sequences, and formats may be preconfigured.
  • the index, sequence, and format correspond to making the above request or indication, and not making the above request or indication, respectively.
  • the terminal selects different resources, indexes, sequences, and formats when sending PRACH to realize the above indication or request.
  • 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.
  • whether the above-mentioned PRACH is repeated transmitted can be that when the terminal supports PRACH repetition (PRACH repetition), the terminal supports the subsequent repeated reception of one or more common PDCCH/PDSCH, that is, realizes the above-mentioned indication or request.
  • the MsgA PUSCH is indicated or requested by at least one of the following:
  • 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.
  • 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.
  • the terminal selects different resources or groups when sending MsgA PUSCH to implement the above indication or request.
  • 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, that is, to implement the above indication or request.
  • 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.
  • MsgA PUSCH can be used to indicate the repetition capability of the corresponding Msg4 PDCCH/PDSCH.
  • the MsgA is indicated or requested by at least one of the following:
  • the Msg3 PUSCH is indicated or requested by at least one of the following:
  • 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.
  • the information carried in the above-mentioned Msg3 PUSCH may be to reuse existing fields or introduce new fields or to use a logical channel ID to indicate.
  • 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.
  • the above indication or request is realized by the terminal selecting different resources or payload sizes when sending Msg3PUSCH.
  • two Msg3PUSCH payload sizes (such as Preamble group A and Preamble group B) may 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 according to the payload size used by the detected terminal, that is, realizes the above indication or request.
  • whether the above-mentioned Msg3 PUSCH is repeatedly transmitted can be that when the terminal supports Msg3 PUSCH, the terminal supports the subsequent repeated reception of one or more common PDCCH/PDSCH, that is, realizes the above-mentioned indication or request.
  • 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.
  • the common PDCCH/PDSCH can be the downlink channel before Msg3 is sent, such as Msg2/BPDCCH/PDSCH.
  • 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.
  • 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.
  • 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.
  • 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.
  • terminals with a priority of 1 support Common PDCCH/PDSCH repetition.
  • Terminals with a priority of 2 do not support Common PDCCH/PDSCH repetition.
  • the downlink supports Common PDCCH/PDSCH repetition, while for smartphones, the downlink does not support Common PDCCH/PDSCH repetition because the uplink coverage of smartphones may be limited.
  • a terminal with capability level 1 can support common PDCCH/PDSCH repetition, but a terminal with capability level 2 does not support common PDCCH/PDSCH repetition.
  • a terminal with capability level 1 can support dynamic and semi-static common PDCCH/PDSCH repetition
  • a terminal with capability level 2 can support semi-static common PDCCH/PDSCH repetition but not dynamic common PDCCH/PDSCH repetition
  • Level 3 terminals do not support common PDCCH/PDSCH repetition.
  • the repeated transmission of the downlink channel is allowed to exceed the duration of the timer corresponding to the downlink channel.
  • the receiving window of the downlink channel includes at least one of the following: a RAR window (RAR window), a message B MsgB response window (MsgB response window).
  • RAR window a RAR window
  • MsgB response window a message B MsgB response window
  • the timer corresponding to the downlink channel includes: a contention resolution timer (Contention resolution timer).
  • 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.
  • the extension of the timer corresponding to the above-mentioned downlink channel may be to extend the timer corresponding to the downlink channel, for example: to extend the timer corresponding to the downlink channel 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 the repeated transmission of the above-mentioned downlink channel.
  • the terminal may support one or more of the above functions.
  • 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.
  • the repeated transmission of the downlink channel includes at least one of the following:
  • RRC Radio Resource Control
  • 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 that the common PDCCH/PDSCH repetition comes from one TRP.
  • 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 that the common PDCCH/PDSCH repetition comes from multiple TRPs.
  • the above control resource set may be CORESET#0 or any other CORESET.
  • the above CSS can be any one or more of the Type0/0A/1/2 CSS set.
  • the above MO is the monitoring time of PDCCH, which can be the same search space or different search spaces.
  • time domain repetition transmission of the above downlink channel may be referred to as time domain downlink channel repetition transmission, for example: time domain common PDCCH repetition, and the time domain repetition may be at least one of the following:
  • frequency domain downlink channel repetition transmission for example: frequency domain common PDCCH repetition
  • frequency domain repetition may be at least one of the following:
  • the same PDCCH MO can be located in the same search space or different search spaces.
  • the CORESET resources of different repetitions are replicated multiple times at one moment.
  • the above-mentioned dynamic repeated transmission of the downlink channel may be a dynamically determined repeated transmission of the downlink channel.
  • the semi-static repeated transmission of the downlink channel may be a pre-configured or periodically determined repeated transmission of the downlink channel.
  • 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.
  • 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.
  • the multiple repeated transmissions are independent terminal capabilities, or the multiple repeated transmissions are combined terminal capabilities; or,
  • the multiple repeated transmissions are indicated by the same target message, or the multiple repeated transmissions are indicated by at least two target messages.
  • the above-mentioned multiple items may be all or part of the items included in the repeated transmission of the above-mentioned uplink channel.
  • 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.
  • 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.
  • 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.
  • the repeated transmission of the downlink channel is defined based on the granularity of terminal type (i.e., per user equipment (per User Equipment, per UE) type definition), or, the repeated transmission of the downlink channel is defined based on the granularity of terminal priority (i.e., per UE priority definition).
  • the above-mentioned terminal type can 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.
  • RedCap UE low-capability terminal
  • non-RedCap UE terrestrial network terminal
  • NTN non-terrestrial network
  • the retransmission capability of the downlink channel matches a target downlink channel retransmission capability
  • the target downlink channel retransmission capability is the downlink channel retransmission capability after the terminal enters a connected state.
  • 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.
  • 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 that the terminal also has the common PDSCH repetition capability.
  • pdsch-RepetitionMultiSlots the existing PDSCH multi-slot repetition
  • the above capability may be 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 PDCCH repetition capability.
  • mTRP-PDCCH-Repetition multi-TRP PDCCH repetition
  • the capability reporting can be reduced and the transmission overhead can be saved.
  • the terminal supports extension of a receiving window 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
  • the terminal supports repeated transmission of the downlink channel
  • the terminal supports extension of a timer corresponding to the downlink channel
  • 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.
  • the terminal supports repeated transmission of the downlink channel to determine that the terminal supports at least one of the following:
  • 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.
  • the multiple functions are indicated by the same target message, or the multiple functions are indicated by at least two target messages.
  • the receiving window of the downlink channel is extended
  • 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.
  • 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.
  • the terminal sending the target message includes:
  • 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 the 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;
  • 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,
  • 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.
  • the downlink signal may be a downlink reference signal, for example, a reference signal for estimating path loss.
  • the repeated transmission of the uplink channel corresponding to the above-mentioned downlink channel may be Msg1 or MsgA or Msg3 or Msg4 hybrid automatic repeat request acknowledgment (HARQ-ACK) repeated transmission;
  • HARQ-ACK hybrid automatic repeat request acknowledgment
  • the uplink channel corresponding to the above-mentioned downlink channel does not perform repeated transmission, which may be Msg1 or MsgA or Msg3 or Msg4 hybrid automatic repeat request acknowledgment (Hybrid automatic repeat request acknowledgment, HARQ-ACK) is not transmitted repeatedly.
  • repeated transmission which may be Msg1 or MsgA or Msg3 or Msg4 hybrid automatic repeat request acknowledgment (Hybrid automatic repeat request acknowledgment, HARQ-ACK) is not transmitted repeatedly.
  • the above target conditions may be agreed upon by the protocol, configured on the network side, or determined by the terminal.
  • the target message can be sent only under the target conditions to save transmission overhead.
  • the method further includes:
  • the terminal receives configuration information, where the configuration information is used to configure repeated transmission resources of the downlink channel;
  • 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.
  • the above configuration information can be configured through system information, for example: through the master information block (MIB).
  • MIB master information block
  • the terminal receiving the configuration information may be: Before the terminal sends the above target message, the terminal receives the above configuration information.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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 voice over New Radio (VoNR) and low-speed data transmission) channels to proceed further.
  • VoNR voice over New Radio
  • the embodiments of the present application support 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 only under certain conditions).
  • the embodiment of the present application supports the RAR window extension or the contention resolution timer time length extension function, and indicates these capabilities to the network, and the network side can decide whether to configure the terminal to perform these functions.
  • FIG. 3 is a flow chart of a message receiving method provided in an embodiment of the present application. As shown in FIG. 3, the method includes the following steps:
  • 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:
  • the downlink channel includes at least one of the following:
  • Common physical downlink control channel PDCCH common physical downlink shared channel PDSCH.
  • the public PDCCH includes at least one of the following:
  • the common PDSCH includes:
  • the Msg3 PUSCH is indicated or requested by at least one of the following:
  • 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.
  • 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 type of the terminal is used to indicate the repetition-related functions of the downlink channel supported by the terminal, or to request the terminal to The terminal sends a downlink transmission corresponding to the repetition-related function of the downlink channel;
  • 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.
  • the repetition-related functions of the downlink channel include at least one of the following:
  • the receiving window of the downlink channel is extended
  • 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.
  • the receiving window of the downlink channel includes at least one of the following: a RAR window, a MsgB response window; or,
  • the timer corresponding to the downlink channel includes: a contention resolution timer.
  • the repeated transmission of the downlink channel includes at least one of the following:
  • the multiple repeated transmissions are independent terminal capabilities, or the multiple repeated transmissions are combined terminal capabilities; or,
  • the multiple repeated transmissions are indicated by the same target message, or the multiple repeated transmissions are indicated by at least two target messages.
  • 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.
  • the retransmission capability of the downlink channel matches a target downlink channel retransmission capability
  • the target downlink channel retransmission capability is the downlink channel retransmission capability after the terminal enters a connected state.
  • the terminal 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;
  • the terminal 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.
  • the multiple functions are indicated by the same target message, or the multiple functions are indicated by at least two target messages.
  • the public PDSCH includes at least one of the following:
  • the public PDCCH includes at least one of the following:
  • SIB1 PDCCH SIB1 PDCCH, OSIPDCCH, Msg2 PDCCH, Msg4 PDCCH, MsgB PDCCH, paging PDCCH, and PDCCH scheduling Msg3 retransmission.
  • the method further comprises:
  • the network side device sends a Configuration information, where the configuration information is used to configure repeated transmission resources of the downlink channel.
  • this embodiment is an implementation of the network side device corresponding to the embodiment shown in Figure 2. Its specific implementation can refer to the relevant description of the embodiment shown in Figure 2. In order to avoid repeated description, this embodiment will not be repeated.
  • Embodiment 1 is a diagrammatic representation of Embodiment 1:
  • This embodiment mainly describes the Common PDCCH/PDSCH repetition capability indication or repetition request indication, which is as follows:
  • the indication of Common PDCCH/PDSCH repeat reception capability or repeat request is at least indicated by PRACH resources or information, where the PRACH resources or information include one or more of the following:
  • PRACH time domain resources PRACH frequency domain resources, PRACH configuration index, PRACH sequence, PRACH sequence scrambling sequence, PRACH format, and whether PRACH performs repetition.
  • the PRACH corresponding to the preamble sequence index implicitly indicates that one or more subsequent common PDCCH/PDSCHs will be repeatedly transmitted.
  • the terminal supports subsequent repeated reception of one or more common PDCCH/PDSCH.
  • the above-mentioned PRACH can be Msg1 PRACH or MsgA PRACH.
  • the common PDCCH/PDSCH repetition capability or repetition request is at least indicated by MsgA PUSCH, including one or more of the following:
  • MsgA PUSCH 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 ID can be used for indication;
  • MSgA PUSCH Implicitly indicated by MSgA PUSCH, including one or more of the following aspects:
  • 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 a terminal supports the common PDCCH/PDSCH repetition function based on the MsgA PUSCH resources used by the detected terminal.
  • two groups of PUSCH transmission opportunities are configured: PO group A and PO group B.
  • PO group A is used by terminals that support common PDCCH/PDSCH repetition transmission
  • 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.
  • MsgA PUSCH can be used to To indicate the repetition capability of the corresponding Msg4 PDCCH/PDSCH.
  • the common PDCCH/PDSCH repetition capability or repetition request is at least implicitly indicated by MsgA, including one or more of the following:
  • two sets of MsgA resources can be independently configured to be 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 MsgA resources used by the detected terminal.
  • the common PDCCH/PDSCH repetition capability or repetition request is determined by at least Msg3PUSCH related parameters/attributes, including one or more of the following methods:
  • Msg3 PUSCH 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 to indicate, such as using spare bits in Msg3;
  • Msg3 PUSCH Implicitly indicated by Msg3 PUSCH, including one or more of the following aspects:
  • the above-mentioned common PDCCH/PDSCH can be Msg4 PDCCH/PDSCH after Msg3 transmission.
  • the common PDCCH/PDSCH mentioned here can also be the downlink channel before Msg3 is sent, such as Msg2/B PDCCH/PDSCH.
  • the terminal capability reporting of Common PDCCH/PDSCH repetition or Common PDCCH/PDSCH repetition request is performed through at least one or more of the following methods:
  • 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.
  • FR2 Common PDCCH/PDSCH repetition is supported, and for FR1, Common PDCCH/PDSCH repetition is not supported. Because the size of FR2 base stations is usually smaller, and the transmission power is even close to that of mobile phones;
  • a terminal with capability level 1 can support common PDCCH/PDSCH repetition, and a terminal with capability level 2 does not support common PDCCH/PDSCH repetition; for another example: a terminal with capability level 1 can support dynamic and semi-static common PDCCH/PDSCH repetition, a terminal with capability level 2 can support semi-static common PDCCH/PDSCH repetition, but does not support dynamic common PDCCH/PDSCH repetition, and a terminal with capability level 3 does not support common PDCCH/PDSCH repetition.
  • dynamic common PDCCH/PDSCH repetition and semi-static common PDCCH/PDSCH repetition are separate UE capabilities.
  • such common PDCCH/PDSCH repetition can correspond to semi-static repetition capability
  • the network 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.
  • dynamic common PDCCH/PDSCH repetition and semi-static common PDCCH/PDSCH repetition is a terminal capability.
  • the common PDCCH/PDSCH repetition capability includes one or more of the following combinations:
  • RAR window extension Whether to support RAR window extension (RAR window extension);
  • contention resolution timer duration extension (contention resolution timer duration extension);
  • contention resolution timer duration (contention resolution timer duration);
  • Control resource set (Intra-coreset) common PDCCH repetition
  • the CORESET here can be CORESET#0 or any other CORESET;
  • the CSS here can be any one or more of the Type0/0A/1/2CSS set;
  • 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;
  • Time domain common PDCCH repetition may 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 within the same search space of different CORESETs;
  • Frequency domain common PDCCH 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 may be located in the same search space or in different search spaces, for example, multiple copies of CORESET resources at one time are made for different repetitions;
  • the above two or more capabilities are separate UE capabilities or combined UE capabilities.
  • 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 can be, for example, RedCap terminals or non-RedCap terminals. Or TN terminals or NTN terminals.
  • the combination of various capabilities can be reported through different PRACH/MsgA/MsgA-PUSCH/Msg3 related parameters/attributes or explicit information.
  • the terminal 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:
  • the common PDCCH/PDSCH repetition capabilities of different types 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 OSIPDCCH 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.
  • the common PDCCH/PDSCH repetition capabilities of different types are combined into one capability; for example, the terminal only needs to report a terminal capability to receive common PDCCH repetition, indicating that the terminal can support all Common PDCCH channels (SIB1 PDCCH, OSIPDCCH, Msg2/4/B PDCCH, Paging PDCCH, and PDCCH scheduling Msg3 retransmission) repetition transmission.
  • Common PDCCH channels SIB1 PDCCH, OSIPDCCH, Msg2/4/B PDCCH, Paging PDCCH, and PDCCH scheduling Msg3 retransmission
  • one or more of the following different types of downlink common PDCCH/PDSCH repetition capabilities are defined:
  • the capability may be the existing PDSCH multi-slot repetition (pdsch-RepetitionMultiSlots) capability, that is, as long as the terminal has the pdsch-RepetitionMultiSlots capability, the network may consider the terminal to also have the common PDSCH repetition capability.
  • pdsch-RepetitionMultiSlots the existing PDSCH multi-slot repetition
  • mTRP-PDCCH-Repetition the multi-TRP PDCCH repetition
  • no terminal receives reports or requests for common PDCCH repetition capabilities
  • the network configures PDCCH repetition resources through the MIB, and the terminal receives repetition transmissions based on its own capabilities.
  • a terminal without PDCCH repetition capability will only perform blind detection at the legacy PDCCH transmission position
  • Terminals with PDCCH repetition capability will perform blind detection on both legacy PDCCH and repetition PDCCH transmission locations.
  • the Common PDCCH/PDSCH re-request needs to meet one or more of the following conditions:
  • 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.
  • One or more different Common PDCCH/PDSCH such as Msg2/MsgB/Msg4/Paging PDCCH/PDSCH, use at least one of the same repeat request conditions;
  • the RSRP/RSRQ thresholds for downlink signal measurement can be the same or different for Common PDCCH/PDSCH.
  • the RSRP threshold corresponding to the Msg2/MsgB/Msg4PDCCH/PDSCH repeat request is determined by adding different RSRP offsets relative to a reference RSRP.
  • This embodiment mainly describes the determination of the ability of RAR (Msg2 or MsgB) window extension (i.e., the receiving window extension in the above embodiment) or Msg2/MsgB repetition exceeding the RAR window, as follows:
  • the reception of Msg2/MsgB PDCCH needs to be completed within the RAR window or the MsgB response window.
  • Msg2/msgB PDCCH is repeatedly sent, in order to support enough repetitions, the length of the RAR window is extended in this embodiment, and the corresponding terminal needs to have corresponding capabilities.
  • the transmission time of the RAR PDSCH may also need to be as close as possible to the RAR window.
  • this embodiment extends the RAR window length. It is also necessary to consider whether to allow RAR repetition to exceed the RAR window.
  • the capability of RAR window extension or Msg2/MsgB PDCCH/PDSCH repetition exceeding the RAR window may also be indicated by one or more of the methods used in the first embodiment to indicate common PDCCH/PDSCH repetition capability.
  • 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/MsgB PDCCH/PDSCH repetition beyond RAR window is supported.
  • the RAR window extension or the Msg2/MsgB PDCCH/PDSCH repetition capability beyond the RAR window is mandatory.
  • 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.
  • the reception of Msg4 PDCCH needs to be completed when the contention resolution timer has not expired.
  • Msg4 PDCCH is sent repeatedly, 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.
  • the sending time of Msg4 may also need to be completed within the Contention resolution timer duration as much as possible.
  • this embodiment extends the length of the Contention resolution timer duration. It is also necessary to consider whether the repetition of Msg4 is allowed to exceed the Contention resolution timer duration.
  • the capability of Contention resolution timer duration extension or Msg4 PDCCH/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.
  • the capability of Contention resolution timer duration extension or Msg4 PDCCH/PDSCH repetition exceeding Contention resolution timer duration is determined by Msg4 PDCCH/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.
  • the Contention resolution timer duration extension or the capability of Msg4 PDCCH/PDSCH repetition exceeding the Contention resolution timer duration is mandatory.
  • the Contention resolution timer duration extension or the ability of Msg4 PDCCH/PDSCH repetition to exceed the Contention resolution timer duration or the Common PDCCH/PDSCH repetition ability 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.
  • the embodiment of the present application proposes that Common PDCCH/PDSCH repeatedly transmits reception-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.
  • 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 that is, repeated requests, is introduced to avoid using common PDCCH/PDSCH repetition for too many terminals without coverage issues, so as to improve the service performance of these terminals.
  • the message sending method provided in the embodiment of the present application can be executed by a message sending device.
  • 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.
  • the message receiving method provided in the embodiment of the present application can be executed by a message receiving device.
  • 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.
  • FIG. 4 is a structural diagram of a message sending device provided in an embodiment of the present application.
  • the message sending device 400 includes:
  • the sending module 401 is used to send a target message, where the target message is used for at least one of the following:
  • the downlink channel includes at least one of the following:
  • Public PDCCH public PDSCH.
  • the public PDCCH includes at least one of the following:
  • the public PDSCH includes:
  • the PDSCH that the terminal needs to receive before entering the connected state is the PDSCH that the terminal needs to receive before entering the connected state.
  • the target message includes at least one of the following:
  • the PRACH is indicated or requested by at least one of the following:
  • the MsgA PUSCH is indicated or requested by at least one of the following:
  • the MsgA indicates or requests at least one of the following:
  • the Msg3 PUSCH is indicated or requested by at least one of the following:
  • 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.
  • 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.
  • the repetition-related functions of the downlink channel include at least one of the following:
  • the receiving window of the downlink channel is extended
  • 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.
  • the receiving window of the downlink channel includes at least one of the following: a random access response RAR window, MsgB response window; or,
  • the timer corresponding to the downlink channel includes: a contention resolution timer.
  • the repeated transmission of the downlink channel includes at least one of the following:
  • the multiple repeated transmissions are independent terminal capabilities, or the multiple repeated transmissions are combined terminal capabilities; or,
  • the multiple repeated transmissions are indicated by the same target message, or the multiple repeated transmissions are indicated by at least two target messages.
  • 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.
  • the retransmission capability of the downlink channel matches a target downlink channel retransmission capability
  • the target downlink channel retransmission capability is the downlink channel retransmission capability after the terminal enters a connected state.
  • the terminal supports extension of a receiving window 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
  • the terminal supports repeated transmission of the downlink channel
  • the terminal supports extension of a timer corresponding to the downlink channel
  • 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.
  • the multiple functions are indicated by the same target message, or the multiple functions are indicated by at least two target messages.
  • 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;
  • 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.
  • the public PDSCH includes at least one of the following:
  • the public PDCCH includes at least one of the following:
  • SIB1 PDCCH SIB1 PDCCH, OSIPDCCH, Msg2 PDCCH, Msg4 PDCCH, MsgB PDCCH, paging PDCCH, and PDCCH scheduling Msg3 retransmission.
  • the device further comprises:
  • 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;
  • 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.
  • the message sending device can improve the service performance of the terminal.
  • 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.
  • the electronic device may be a terminal, or may be a device other than a terminal.
  • 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.
  • NAS network attached storage
  • the message sending device provided in the embodiment of the present application can implement the various processes implemented by the method embodiment shown in Figure 2 and achieve the same technical effect. To avoid repetition, it will not be repeated here.
  • FIG. 5 is a structural diagram of a message receiving device provided in an embodiment of the present application.
  • the message receiving device 500 includes:
  • 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:
  • the downlink channel includes at least one of the following:
  • Common physical downlink control channel PDCCH common physical downlink shared channel PDSCH.
  • the public PDCCH includes at least one of the following:
  • the public PDSCH includes:
  • the received PDSCH is sent before the terminal enters the connected state.
  • the target message includes at least one of the following:
  • Physical random access channel PRACH Msg1, Msg3 PUSCH, MsgA, MsgA PUSCH, messages sent by the terminal in connected state.
  • the PRACH is indicated or requested by at least one of the following:
  • the MsgA PUSCH is indicated or requested by at least one of the following:
  • the MsgA indicates or requests at least one of the following:
  • the Msg3 PUSCH is indicated or requested by at least one of the following:
  • 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.
  • 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.
  • the repetition-related functions of the downlink channel include at least one of the following:
  • the receiving window of the downlink channel is extended
  • 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.
  • the receiving window of the downlink channel includes at least one of the following: a RAR window, a MsgB response window; or,
  • the timer corresponding to the downlink channel includes: a contention resolution timer.
  • the repeated transmission of the downlink channel includes at least one of the following:
  • the multiple repeated transmissions are independent terminal capabilities, or the multiple repeated transmissions are combined terminal capabilities; or,
  • the multiple repeated transmissions are indicated by the same target message, or the multiple repeated transmissions are indicated by at least two target messages.
  • the repeated transmission of the downlink channel is defined based on the granularity of the terminal type, or the downlink channel
  • the repetitive transmission is defined based on the terminal priority.
  • the retransmission capability of the downlink channel matches a target downlink channel retransmission capability
  • the target downlink channel retransmission capability is the downlink channel retransmission capability after the terminal enters a connected state.
  • the terminal 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;
  • the terminal 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.
  • the multiple functions are indicated by the same target message, or the multiple functions are indicated by at least two target messages.
  • the public PDSCH includes at least one of the following:
  • the public PDCCH includes at least one of the following:
  • SIB1 PDCCH SIB1 PDCCH, OSIPDCCH, Msg2 PDCCH, Msg4 PDCCH, MsgB PDCCH, paging PDCCH, and PDCCH scheduling Msg3 retransmission.
  • the device further comprises:
  • 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.
  • the message receiving device can improve the service performance of the terminal.
  • 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.
  • the message receiving device provided in the embodiment of the present application can implement the various processes implemented by the method embodiment shown in Figure 3 and achieve the same technical effect. To avoid repetition, it will not be repeated here.
  • the embodiment of the present application further provides a communication device 600, including a processor 601 and a memory 602, wherein the memory 602 stores a program or instruction that can be run on the processor 601.
  • 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.
  • 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.
  • the 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 a repeat-related function of a downlink channel supported by the terminal; requesting to send a downlink transmission corresponding to the repeat-related function of the downlink channel to the terminal; wherein the downlink The channel includes at least one of the following: a common PDCCH and a common PDSCH.
  • 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.
  • the terminal 700 may also include a power source (such as a battery) for supplying power to each component, and the power source may be logically connected to the processor 710 through a power management system, so as to implement functions such as managing charging, discharging, and power consumption management through the power management system.
  • a power source such as a battery
  • the communication device structure shown in FIG7 does not constitute a limitation on the communication device, and the communication device may include more or fewer components than shown in the figure, or combine certain components, or arrange components differently, which will not be described in detail here.
  • the input unit 704 may include a graphics processing unit (GPU) 7041 and a microphone 7042, and the graphics processor 7041 processes the image data of the static picture or video obtained by the image capture device (such as a camera) in the video capture mode or the 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 key, a switch key, etc.), a trackball, a mouse, and a joystick, which will not be repeated here.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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 memories.
  • the processor 710 may include one or more processing units; optionally, the processor 710 integrates an application processor and a modulation
  • the demodulation processor wherein the application processor mainly processes operations related to the operating system, user interface and application programs, and the modulation and demodulation processor mainly processes wireless communication signals, such as the baseband processor. It is understandable that the above-mentioned modulation and demodulation processor may not be integrated into the processor 710.
  • 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:
  • the downlink channel includes at least one of the following:
  • Public PDCCH public PDSCH.
  • the public PDCCH includes at least one of the following:
  • the public PDSCH includes:
  • the PDSCH that the terminal needs to receive before entering the connected state is the PDSCH that the terminal needs to receive before entering the connected state.
  • the target message includes at least one of the following:
  • the PRACH is indicated or requested by at least one of the following:
  • the MsgA PUSCH is indicated or requested by at least one of the following:
  • the MsgA indicates or requests at least one of the following:
  • the Msg3 PUSCH is indicated or requested by at least one of the following:
  • 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.
  • 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.
  • the repetition-related functions of the downlink channel include at least one of the following:
  • the receiving window of the downlink channel is extended
  • 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.
  • the receiving window of the downlink channel includes at least one of the following: a RAR window, a MsgB response window; or,
  • the timer corresponding to the downlink channel includes: a contention resolution timer.
  • the repeated transmission of the downlink channel includes at least one of the following:
  • the multiple repeated transmissions are independent terminal capabilities, or the multiple repeated transmissions are combined terminal capabilities; or,
  • the multiple repeated transmissions are indicated by the same target message, or the multiple repeated transmissions are indicated by at least two target messages.
  • 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.
  • the retransmission capability of the downlink channel matches a target downlink channel retransmission capability
  • the target downlink channel retransmission capability is the downlink channel retransmission capability after the terminal enters a connected state.
  • the terminal supports extension of a receiving window 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
  • the terminal supports repeated transmission of the downlink channel
  • the terminal supports extension of a timer corresponding to the downlink channel
  • the terminal supports repeated transmission of the downlink channel
  • the terminal supports: allowing the downlink channel to be transmitted; The repeated transmission of the downlink channel exceeds the duration of the timer corresponding to the downlink channel.
  • the multiple functions are indicated by the same target message, or the multiple functions are indicated by at least two target messages.
  • 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;
  • 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.
  • the public PDSCH includes at least one of the following:
  • the public PDCCH includes at least one of the following:
  • SIB1 PDCCH SIB1 PDCCH, OSIPDCCH, Msg2 PDCCH, Msg4 PDCCH, MsgB PDCCH, paging PDCCH, and PDCCH scheduling Msg3 retransmission.
  • the radio frequency unit 701 is further configured to:
  • 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;
  • 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.
  • the above terminal can improve the service performance of the terminal.
  • 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.
  • 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.
  • the radio frequency device 802 receives information through the antenna 801 and sends the received information to the baseband device 803 for processing.
  • the baseband The 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 .
  • 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.
  • the baseband device 803 may include, for example, at least one baseband board, on which a plurality of chips are arranged, as shown in FIG8 , wherein one of the chips is, for example, a baseband processor, which is connected to the memory 805 through a bus interface to call a program in the memory 805 and execute the network device operations shown in the above method embodiment.
  • the wireless access network device may also include a network interface 806, which is, for example, a common public radio interface (CPRI).
  • a network interface 806 which is, for example, a common public radio interface (CPRI).
  • CPRI common public radio interface
  • the network side device 800 of the embodiment of the present application also includes: instructions or programs stored in the memory 805 and executable on the processor 804.
  • the processor 804 calls the instructions or programs in the memory 805 to execute the methods executed by the modules shown in Figure 5 and achieve the same technical effect. To avoid repetition, it will not be described here.
  • 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:
  • the downlink channel includes at least one of the following:
  • Common physical downlink control channel PDCCH common physical downlink shared channel PDSCH.
  • the public PDCCH includes at least one of the following:
  • the common PDSCH includes:
  • the received PDSCH is sent before the terminal enters the connected state.
  • the target message includes at least one of the following:
  • Physical random access channel PRACH Msg1, Msg3 PUSCHMsgA, MsgA PUSCH, messages sent by the terminal in connected state.
  • the PRACH is indicated or requested by at least one of the following:
  • the MsgA PUSCH is indicated or requested by at least one of the following:
  • the MsgA indicates or requests at least one of the following:
  • the Msg3 PUSCH is indicated or requested by at least one of the following:
  • 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.
  • the target message is used to indicate at least one of the following:
  • 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.
  • the repetition-related functions of the downlink channel include at least one of the following:
  • the receiving window of the downlink channel is extended
  • 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.
  • the receiving window of the downlink channel includes at least one of the following: a RAR window, a MsgB response window; or,
  • the timer corresponding to the downlink channel includes: a contention resolution timer.
  • the multiple repeated transmissions are independent terminal capabilities, or the multiple repeated transmissions are combined terminal capabilities; or,
  • the multiple repeated transmissions are indicated by the same target message, or the multiple repeated transmissions are indicated by at least two target messages.
  • the repeated transmission of the downlink channel is defined based on the granularity of the terminal type, or the downlink channel
  • the repetitive transmission is defined based on the terminal priority.
  • the retransmission capability of the downlink channel matches a target downlink channel retransmission capability
  • the target downlink channel retransmission capability is the downlink channel retransmission capability after the terminal enters a connected state.
  • the terminal 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;
  • the terminal 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.
  • the multiple functions are indicated by the same target message, or the multiple functions are indicated by at least two target messages.
  • the public PDSCH includes at least one of the following:
  • the public PDCCH includes at least one of the following:
  • SIB1 PDCCH SIB1 PDCCH, OSI PDCCH, Msg2 PDCCH, Msg4 PDCCH, MsgB PDCCH, paging PDCCH, and PDCCH scheduling Msg3 retransmission.
  • the radio frequency device 802 is further used for:
  • configuration information is sent to the terminal, where the configuration information is used to configure repeated transmission resources of the downlink channel.
  • the above network side equipment can improve the service performance of the terminal.
  • An embodiment of the present application also provides a readable storage medium, on which a program or instruction is stored.
  • a program or instruction is stored.
  • 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.
  • 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.
  • the readable storage medium may be a non-transient readable storage medium.
  • 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.
  • 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.
  • the embodiment of the present application further provides a computer program/program product, wherein the computer program/program product is stored in a storage medium, and the computer program/program product is executed by at least one processor to implement the message sending method.
  • the various processes of the method or message receiving method embodiment can achieve the same technical effect. To avoid repetition, they will not be described here.
  • 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.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本申请公开了一种消息发送方法、消息接收方法、装置、终端及网络侧设备，属于通信技术领域，本申请实施例的消息发送方法包括：终端发送目标消息，所述目标消息用于如下至少一项：指示所述终端支持的下行信道的重复相关功能；请求向所述终端发送下行信道的重复相关功能对应的下行传输；其中，所述下行信道包括如下至少一项：公共PDCCH、公共PDSCH。

Description

消息发送方法、消息接收方法、装置、终端及网络侧设备
相关申请的交叉引用
本申请主张在2023年07月10日在中国提交的中国专利申请No.202310840176.7的优先权，其全部内容通过引用包含于此。
技术领域
本申请属于通信技术领域，具体涉及一种消息发送方法、消息接收方法、装置、终端及网络侧设备。
背景技术
终端在一些场景或者状态下需要接收一些公共下行信道，例如：接收公共物理下行控制信道(Physical downlink control channel，PDCCH)、接收公共物理下行共享信道(Physical downlink shared channel，PDSCH)。在一些相关技术中，公共下行信道往往只支持单次传输，这样导致终端接收下行信道的成功率比较低，使得终端的业务性能比较差。
发明内容
本申请实施例提供一种消息发送方法、消息接收方法、装置、终端及网络侧设备，能够解决终端的业务性能比较差的问题。
第一方面，提供了一种消息发送方法，包括：
终端发送目标消息，所述目标消息用于如下至少一项：
指示所述终端支持的下行信道的重复相关功能；
请求向所述终端发送下行信道的重复相关功能对应的下行传输；
其中，所述下行信道包括如下至少一项：
公共PDCCH、公共PDSCH。
第二方面，提供了一种消息接收方法，包括：
网络侧设备接收终端发送的目标消息，所述目标消息用于如下至少一项：
指示所述终端支持的下行信道的重复相关功能；
请求向所述终端发送下行信道的重复相关功能对应的下行传输；
其中，所述下行信道包括如下至少一项：
公共PDCCH、公共PDSCH。
第三方面，提供了一种消息发送装置，包括：
发送模块，用于发送目标消息，所述目标消息用于如下至少一项：
指示所述终端支持的下行信道的重复相关功能；
请求向所述终端发送下行信道的重复相关功能对应的下行传输；
其中，所述下行信道包括如下至少一项：
公共PDCCH、公共PDSCH。
第四方面，提供了一种消息接收装置，包括：
接收模块，用于接收终端发送的目标消息，所述目标消息用于如下至少一项：
指示所述终端支持的下行信道的重复相关功能；
请求向所述终端发送下行信道的重复相关功能对应的下行传输；
其中，所述下行信道包括如下至少一项：
公共PDCCH、公共PDSCH。
第五方面，提供了一种终端，该终端包括处理器和存储器，所述存储器存储可在所述处理器上运行的程序或指令，所述程序或指令被所述处理器执行时实现如本申请实施例提供的消息发送方法的步骤。
第六方面，提供了一种终端，包括处理器及通信接口，其中，所述通信接口用于发送目标消息，所述目标消息用于如下至少一项：指示所述终端支持的下行信道的重复相关功能；请求向所述终端发送下行信道的重复相关功能对应的下行传输；其中，所述下行信道包括如下至少一项：公共PDCCH、公共PDSCH。
第七方面，提供了一种网络侧设备，该网络侧设备包括处理器和存储器，所述存储器存储可在所述处理器上运行的程序或指令，所述程序或指令被所述处理器执行时实现如本申请实施例提供的消息接收方法的步骤。
第八方面，提供了一种网络侧设备，包括处理器及通信接口，其中，所述通信接口用于接收终端发送的目标消息，所述目标消息用于如下至少一项：指示所述终端支持的下行信道的重复相关功能；请求向所述终端发送下行信道的重复相关功能对应的下行传输；其中，所述下行信道包括如下至少一项：公共PDCCH、公共PDSCH。
第九方面，提供了一种可读存储介质，所述可读存储介质上存储程序或指令，所述程序或指令被处理器执行时实现如本申请实施例提供的消息发送方法的步骤，或者实现如本申请实施例提供的消息接收方法的步骤。
第十方面，提供了一种无线通信系统，包括：终端及网络侧设备，所述终端可用于执行如本申请实施例提供的消息发送方法的步骤，所述网络侧设备可用于执行如本申请实施例提供的消息接收方法的步骤。
第十一方面，提供了一种芯片，所述芯片包括处理器和通信接口，所述通信接口和所述处理器耦合，所述处理器用于运行程序或指令，实现如本申请实施例提供的消息发送方法，或实现如本申请实施例提供的消息接收方法。
第十二方面，提供了一种计算机程序/程序产品，所述计算机程序/程序产品被存储在存储介质中，所述程序/程序产品被至少一个处理器执行以实现如本申请实施例提供的消息发送方法的步骤，所述程序/程序产品被至少一个处理器执行以实现如本申请实施例提 供的消息接收方法的步骤。
在本申请实施例中，终端发送目标消息，所述目标消息用于如下至少一项：指示所述终端支持的下行信道的重复相关功能；请求向所述终端发送下行信道的重复相关功能对应的下行传输；其中，所述下行信道包括如下至少一项：公共PDCCH、公共PDSCH。这样能够支持公共PDCCH、公共PDSCH中至少一项重复传输，进而提高终端接收下行信道的成功率，以提高终端的业务性能。
附图说明
图1是本申请实施例可应用的一种无线通信系统的框图；
图2是本申请实施例提供的一种消息发送方法的流程图；
图3是本申请实施例提供的一种消息接收方法的流程图；
图4是本申请实施例提供的一种消息发送装置的结构图；
图5是本申请实施例提供的一种消息接收装置的结构图；
图6是本申请实施例提供的一种通信设备的结构图；
图7是本申请实施例提供的一种终端的结构图；
图8是本申请实施例提供的一种网络侧设备的结构图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清楚描述，显然，所描述的实施例是本申请一部分实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技术人员所获得的所有其他实施例，都属于本申请保护的范围。
本申请的术语“第一”、“第二”等是用于区别类似的对象，而不用于描述特定的顺序或先后次序。应该理解这样使用的术语在适当情况下可以互换，以便本申请的实施例能够以除了在这里图示或描述的那些以外的顺序实施，且“第一”、“第二”所区别的对象通常为一类，并不限定对象的个数，例如第一对象可以是一个，也可以是多个。此外，本申请中的“或”表示所连接对象的至少其中之一。例如“A或B”涵盖三种方案，即，方案一：包括A且不包括B；方案二：包括B且不包括A；方案三：既包括A又包括B。字符“/”一般表示前后关联对象是一种“或”的关系。
本申请的术语“指示”既可以是一个直接的指示(或者说显式的指示)，也可以是一个间接的指示(或者说隐含的指示)。其中，直接的指示可以理解为，发送方在发送的指示中明确告知了接收方具体的信息、需要执行的操作或请求结果等内容；间接的指示可以理解为，接收方根据发送方发送的指示确定对应的信息，或者进行判断并根据判断结果确定需要执行的操作或请求结果等。
值得指出的是，本申请实施例所描述的技术不限于长期演进型(Long Term Evolution，LTE)/LTE的演进(LTE-Advanced，LTE-A)系统，还可用于其他无线通信系统，诸如码 分多址(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)或其他系统。本申请实施例中的术语“系统”和“网络”常被可互换地使用，所描述的技术既可用于以上提及的系统和无线电技术，也可用于其他系统和无线电技术。以下描述出于示例目的描述了新空口(New Radio，NR)系统，并且在以下大部分描述中使用NR术语，但是这些技术也可应用于NR系统以外的系统，如第6代(6th Generation，6G)通信系统。
图1示出本申请实施例可应用的一种无线通信系统的框图。无线通信系统包括终端11和网络侧设备12。其中，终端11可以是手机、平板电脑(Tablet Personal Computer)、膝上型电脑(Laptop Computer)、笔记本电脑、个人数字助理(Personal Digital Assistant，PDA)、掌上电脑、上网本、超级移动个人计算机(Ultra-mobile Personal Computer，UMPC)、移动上网装置(Mobile Internet Device，MID)、增强现实(Augmented Reality，AR)、虚拟现实(Virtual Reality，VR)设备、机器人、可穿戴式设备(Wearable Device)、飞行器(flight vehicle)、车载设备(Vehicle User Equipment，VUE)、船载设备、行人终端(Pedestrian User Equipment，PUE)、智能家居(具有无线通信功能的家居设备，如冰箱、电视、洗衣机或者家具等)、游戏机、个人计算机(Personal Computer，PC)、柜员机或者自助机等终端侧设备。可穿戴式设备包括：智能手表、智能手环、智能耳机、智能眼镜、智能首饰(智能手镯、智能手链、智能戒指、智能项链、智能脚镯、智能脚链等)、智能腕带、智能服装等。其中，车载设备也可以称为车载终端、车载控制器、车载模块、车载部件、车载芯片或车载单元等。需要说明的是，在本申请实施例并不限定终端11的具体类型。网络侧设备12可以包括接入网设备或核心网设备，其中，接入网设备也可以称为无线接入网(Radio Access Network，RAN)设备、无线接入网功能或无线接入网单元。接入网设备可以包括基站、无线局域网(Wireless Local Area Network，WLAN)接入点(Access Point，AP)或无线保真(Wireless Fidelity，WiFi)节点等。其中，基站可被称为节点B(Node B，NB)、演进节点B(Evolved Node B，eNB)、下一代节点B(the next generation Node B，gNB)、新空口节点B(New Radio Node B，NR Node B)、接入点、中继站(Relay Base Station，RBS)、服务基站(Serving Base Station，SBS)、基收发机站(Base Transceiver Station，BTS)、无线电基站、无线电收发机、基本服务集(Basic Service Set，BSS)、扩展服务集(Extended Service Set，ESS)、家用B节点(home Node B，HNB)、家用演进型B节点(home evolved Node B)、发送接收点(Transmission Reception Point，TRP)或所述领域中其他某个合适的术语，只要达到相同的技术效果，所述基站不限于特定技术词汇，需要说明的是，在本申请实施例中仅以NR系统中的基站为例进行介绍，并不限定基站的具体类型。
核心网设备可以包含但不限于如下至少一项：核心网节点、核心网功能、移动管理实体(Mobility Management Entity，MME)、接入移动管理功能(Access and Mobility  Management Function，AMF)、会话管理功能(Session Management Function，SMF)、用户平面功能(User Plane Function，UPF)、策略控制功能(Policy Control Function，PCF)、策略与计费规则功能单元(Policy and Charging Rules Function，PCRF)、边缘应用服务发现功能(Edge Application Server Discovery Function，EASDF)、统一数据管理(Unified Data Management，UDM)、统一数据仓储(Unified Data Repository，UDR)、归属用户服务器(Home Subscriber Server，HSS)、集中式网络配置(Centralized network configuration，CNC)、网络存储功能(Network Repository Function，NRF)、网络开放功能(Network Exposure Function，NEF)、本地NEF(Local NEF，或L-NEF)、绑定支持功能(Binding Support Function，BSF)、应用功能(Application Function，AF)等。需要说明的是，在本申请实施例中仅以NR系统中的核心网设备为例进行介绍，并不限定核心网设备的具体类型。
在一些实施例中，随机接入过程可以是基于竞争的随机接入流程也可以是基于非竞争的随机接入的过程。随机接入过程可以是四步随机接入过程(又叫类型1(Type-1)随机接入过程)或者两步随机接入过程(又叫类型2(Type-2)随机接入过程)。
在竞争的4步随机接入过程(Random Access Channel，RACH)中，终端首先向网络发送消息1(Msg1)，包含前导码(preamble)；网络检测到preamble后，将发送消息2(Msg2)/随机接入响应(Random Access Response，RAR)消息，包含网络所检测到的preamble的编号，以及分配给终端发送消息3(Msg3)的上行无线资源；终端接收到Msg2后，确认Msg2中携带的preamble的编号中至少有一个和自己所发送的preamble的编号一致，则根据RAR的指示的资源，发送包含竞争解决信息的Msg3；网络收到Msg3后，将发送包含竞争解决信息的消息4(Msg4)；终端收到Msg4，确认进行解决信息和自己在Msg3中发送的一致，即完成4步随机接入。
网络在RAR中包含上行授权(UL grant)信息用于指示Msg3物理上行共享信道(Physical Uplink Shared Channel，PUSCH)调度信息，并且包含随机接入前导码标识(RACH preamble ID，RAPID)，临时无线网络临时标识(temporary cell-radio network temporary identifier，TC-RNTI)，时间提前量(Timing Advance，TA)等信息。如果网络没有接收到Msg3 PUSCH，可以在TC-RNTI加扰的物理下行控制信道(Physical downlink control channel，PDCCH)中调度Msg3 PUSCH的重传。
对于竞争的随机接入过程，不同的终端随机选取preamble进行传输，这样不同的终端可能在相同的时频无线资源(如随机接入时机(RACH Occasion，RO)资源)上选取相同的preamble发送，这种情况可以理解为终端的preamble冲突。这种情况下，不同的终端会收到相同的RAR，则此时不同的终端会根据该RAR UL grant中的调度信息，进行Msg3PUSCH的传输。在一些相关技术中，由于不支持Msg3 PUSCH的重复传输，网络在一个Msg3 PUSCH调度资源上只能解出一个终端发送的PUSCH(包含竞争解决信息)，所以，网络会在Msg4中包含在Msg3中收到的竞争解决信息。如果终端收到的Msg4中的竞争解决信息和终端在Msg3 PUSCH中发送的竞争解决信息匹配，则终端认为竞争解决 成功。如果不匹配，则认为竞争解决不成功。
如果竞争解决不成功，则终端重新选择RACH发送资源，进行物理随机接入信道(Physical Random Access Channel，PRACH)发送，进行下一次随机接入尝试。
在一些实施例中，两步随机接入过程(2-step RACH)中的第一步是终端发送消息A(MsgA)给网络侧。网络侧接收到MsgA后给终端发送消息B(MsgB)给终端，如果终端在一定时间内都没有收到MsgB，终端会将统计MsgA发送次数的计数器累加一并重新发送MsgA。如果统计MsgA发送次数的计数器达到一定门限，终端会从两步随机接入过程切换到四步随机接入过程。MsgA包括MsgA preamble部分和MsgA PUSCH部分，preamble部分在用于两步随机接入过程的RO上发送，PUSCH部分在跟发送MsgA preamble以及RO想关联的MsgA PUSCH资源上发送。MsgA PUSCH资源是相对于每个PRACH时隙(slot)配置的一组PUSCH资源，包括时频资源和解调参考信号(demodulation reference signal，DMRS)资源。
在一些实施例中，在随机接入过程中，调度Msg2/MsgB/Msg4物理下行共享信道(Physical downlink shared channel，PDSCH)调度信息的接收需要在一定的窗口内，窗口的大小由网络配置。
对于Msg2，上述窗口从PRACH发送后的第一个在类型1的PDCCH公共搜索空间集(Type1-PDCCH CSS set)内的控制资源集(Control resource set，CORESET)的第一个符号(symbol)开始。对于MsgB，上述窗口从PRACH(MsgA PRACH部分)发送所对应的PUSCH(MsgA PUSCH部分)资源后的第一个在Type1-PDCCH CSS set内的CORESET的第一个symbol开始。对于Msg3,上述窗口实际上由随机接入竞争解决定时器(ra-ContentionResolutionTimer)来控制，该定时器会在发送完Msg3(如果支持Msg3重复(repetition)的话，为发送完Msg3的最后一个repetition)启动或者重启。
在一些实施例中，CORESET是控制信息的时域和频域资源的集合。其中，CORESET#0是一种特殊的CORESET，通常用于调度系统信息块(System Information Block，SIB)1的PDCCH的传输。CORESET#0的配置信息以及Type0-PDCCH公共搜索空间(Common Search Space，CSS)的监听时机的配置信息由关联的小区定义同步信号块(Cell Defining Synchronization Signal Block，CD-SSB)携带。CORESET#0的主要功能是定义Type0-PDCCH CSS的时间和频率资源以及Type0-PDCCH CSS的监听时机的大小。
下面结合附图，通过一些实施例及其应用场景对本申请实施例提供的一种消息发送方法、消息接收方法、装置、终端及网络侧设备进行详细地说明。
请参见图2，图2是本申请实施例提供的一种消息发送方法的流程图，如图2所示，包括如下步骤：
步骤201、终端发送目标消息，所述目标消息用于如下至少一项：
指示所述终端支持的下行信道的重复相关功能；
请求向所述终端发送下行信道的重复相关功能对应的下行传输；
其中，所述下行信道包括如下至少一项：
公共PDCCH、公共PDSCH。
上述终端发送目标消息可以是向网络侧设备发送目标消息。
上述下行信道的重复相关功能为，下行信道重复传输的相关功能，也可以称作下行信道的重复相关能力，或称作下行信道重复能力。
其中，终端支持的下行信道的重复相关功能表示终端支持上述上行信道的重复传输，即终端支持接收下行信道的重复传输。终端支持接收下行信道的重复传输表示终端具备能够接收公共PDCCH/PDSCH重复传输(common PDCCH/PDSCH repetition)的能力。
上述请求向所述终端发送下行信道的重复相关功能对应的下行传输可以理解为，终端请求网络侧设备按照下行信道的重复相关功能发送上述下行信道。具体为，终端请求网络重复传输公共PDCCH/PDSCH，且上述请求还可以携带或不携带请求的重复(repetition)次数等信息。网络侧设备接收到上述请求后，针对上述下行信道执行重复传输，即向上述终端重复传输上述下行信道。
在一些实施方式中，在上述目标消息指示所述终端支持的下行信道的重复相关功能情况下，表示请求网络侧设备向终端发送下行信道的重复相关功能对应的下行传输。
在一些实施方式中，在目标消息请求向所述终端发送下行信道的重复相关功能对应的下行传输的情况下，表示终端支持的下行信道的重复相关功能。
在一些实施方式中，上述目标消息可以指示上述终端是否支持的下行信道的重复相关功能，如可以指终端是否具备接收对应的公共PDSCH/PDCCH重复的能力；或，上述目标消息可以指示终端是否请求向终端发送下行信道的重复相关功能对应的下行传输，或者指示是否具备请求向终端发送下行信道的重复相关功能对应的下行传输的能力，如指示是否具备在一定条件下向网络请求公共PDSCH/PDCCH进行重复传输的能力。
本申请实施例中，这样通过上述步骤可以实现支持公共PDCCH、公共PDSCH中至少一项重复传输，进而提高终端接收下行信道的成功率，以提高终端的业务性能。
本实施例中，在发送上述目标消息之后，网络侧设备基于上述目标消息向终端发送下行信道的重复传输，终端接收所述上行信道的重复传输。
作为一种可选的实施方式，所述公共PDCCH包括如下至少一项：
所述终端进入连接态之前需要接收的PDCCH；
在公共PDCCH资源上传输的PDCCH。
其中，上述终端进入连接态之前需要接收的PDCCH可以包括如下至少一项：
调度在终端进入连接态之前需要接收的PDSCH的PDCCH；
调度Msg3 PUSCH重传的PDCCH；
调度Msg5的PDCCH。
在一些实施方式中，上述公共PDCCH，具体可以包括如下至少一项：
SIB1 PDCCH、其他系统消息(Other System Information，OSI)PDCCH、Msg2 PDCCH、 Msg4 PDCCH、MsgB PDCCH、寻呼PDCCH、调度Msg3重传的PDCCH。
上述在公共PDCCH资源上传输的PDCCH可以是，在公共PDCCH资源上传输的一种或多种PDCCH，例如：CORESET#0上传输的一种或者多种PDCCH，可以是Type0/0A/1/2PDCCH公共搜索空间集(common search space set)上传输的PDCCH，如SIB1 PDCCH，OSIPDCCH，Msg2 PDCCH，Msg4 PDCCH，MsgB PDCCH，Paging PDCCH，调度Msg3重传的PDCCH。另外，上述公共PDCCH资源是指的支持CSS的CORESET资源，可以是CORESET#0或其他CORESET，该CSS包括：Type0/0A/1/2CSS集等。另外，在CSS关联的CORESET资源上传输的PDCCH也叫做广播PDCCH(broadcast PDCCH)。
作为一种可选的实施方式，所述公共PDSCH包括如下至少一项：
所述终端进入连接态之前需要接收的PDSCH。
其中，终端进入连接态之前需要接收的PDSCH可以包括如下至少一项：
Msg2 PDSCH、MsgB PDSCH、Msg4 PDSCH、寻呼PDSCH。
即公共PDSCH具体可以包括如下至少一项：
Msg2 PDSCH、MsgB PDSCH、Msg4 PDSCH。
该实施方式中，可以实现Msg2 PDSCH、MsgB PDSCH、Msg4 PDSCH和寻呼PDSCH中至少一项的重复传输，即实现对Msg2 PDSCH、MsgB PDSCH、Msg4 PDSCH和寻呼PDSCH的增强，从而可以提高终端的随机接入性能，以及提高终端的寻呼性能。
在一些实施方式中，上述公共PDCCH/PDSCH的传输重复，也可以称作公共PDCCH/PDSCH重复，例如：对于Msg2/MsgB/Msg4相关的下行控制和数据信道，其重复可以称之为Msg2/MsgB/Msg4 PDSCH/PDCCH重复，这里的Msg2/MsgB/Msg4 PDSCH重复也可以简称为Msg2/MsgB/Msg4重复。
作为一种可选的实施方式，所述目标消息包括如下至少一项：
物理随机接入信道(Physical Random Access Channel，PRACH)、Msg1、Msg3 PUSCH、MsgA、MsgA PUSCH、所述终端在连接态发送的消息。
其中，上述终端在连接态发送的消息表示终端进入连接态发送的消息。
其中，上述目标消息可以是通过隐式或者显式的方式来实现指示所述终端支持的下行信道的重复相关功能，或，请求向所述终端发送下行信道的重复相关功能对应的下行传输。
在一些实施方式中，所述PRACH通过如下至少一项进行指示或请求：
所述PRACH的时域资源、所述PRACH的频域资源、所述PRACH的配置索引、所述PRACH的序列、所述PRACH的序列的加扰序列、所述PRACH的格式、所述PRACH是否做重复传输；
其中，所述指示包括：指示所述终端支持的下行信道的重复相关功能，所述请求包括：请求向所述终端发送下行信道的重复相关功能对应的下行传输。
上述PRACH可以包括：Msg1 PRACH或MsgA PRACH。
该实施方式中，可以是通过预先配置多个的资源、索引、序列、格式，这些资源、索 引、序列、格式分别与进行上述请求或指示，以及不进行上述请求或指示对应。这样通过终端在发送PRACH选择不同资源、索引、序列、格式实现上述指示或请求。例如：预定义一组preamble序列索引(或其它上述因素)，该preamble序列索引对应的PRACH隐式指示后续的一种或者多种common PDCCH/PDSCH会重复传输，即实现上述指示或请求。
另外，上述PRACH是否做重复传输可以是，当终端支持PRACH重复(PRACH repetition)，则终端就支持后续的一种或者多种common PDCCH/PDSCH重复接收，即实现上述指示或请求。
上述实施方式中，可以实现在实现上述指示或请求不需要引入额外的消息，进而节约传输资源。
在一些实施方式中，所述MsgA PUSCH通过如下至少一项进行指示或请求：
所述MsgA PUSCH中携带的信息、所述MsgA PUSCH的时域资源、所述MsgA PUSCH的频域资源、所述MsgA PUSCH的解调参考信号(demodulation reference signal，DMRS)资源、所述MsgA PUSCH所在的组、所述MsgA PUSCH是否做重复传输；
其中，所述指示包括：指示所述终端支持的下行信道的重复相关功能，所述请求包括：请求向所述终端发送下行信道的重复相关功能对应的下行传输。
该实施方式中，可以是通过预先配置多个的资源或组，这些资源或组分别与进行上述请求或指示，以及不进行上述请求或指示对应。这样通过终端在发送MsgA PUSCH选择不同资源或组实现上述指示或请求。例如：可以独立配置多套MsgA PUSCH资源分别给支持common PDCCH/PDSCH repetition传输的终端和不支持common PDCCH/PDSCH repetition传输的终端使用，网络根据所检测终端所用MsgA PUSCH资源确定终端是否支持common PDCCH/PDSCH重复功能，即实现上述指示或请求。又例如：在两步随机接入(2-step RACH)的MsgA配置中，配置两组PUSCH传输机会(PUSCH Occasion，PO)：PO组(group)A和PO group B，其中，PO group A由支持common PDCCH/PDSCH repetition传输的终端使用，PO group B由不支持common PDCCH/PDSCH repetition传输的终端使用，网络根据检测两个PO group上的PUSCH确定终端是否支持接收或者是否请求PDCCH/PDSCH repetition，即实现上述指示或请求。
在一些实施方式中，2-step RACH本身没有Msg4的发送，但是当2-step RACH回退(fallback)或者切换(switch)到四步随机接入(4-step RACH)后，对应还是有MsgA PUSCH传输的。这种情况下，可以通过MsgA PUSCH来指示对应的Msg4 PDCCH/PDSCH的重复能力。
另外，上述MsgA PUSCH是否做重复传输可以是，当终端支持MsgA PUSCH，则终端就支持后续的一种或者多种common PDCCH/PDSCH重复接收，即实现上述指示或请求。
上述实施方式中，可以实现在实现上述指示或请求不需要引入额外的消息，进而节约传输资源。
在一些实施方式中，所述MsgA通过如下至少一项进行指示或请求：
所述MsgA的时域资源、所述MsgA的频域资源、所述MsgA的DMRS资源；
其中，所述指示包括：指示所述终端支持的下行信道的重复相关功能，所述请求包括：请求向所述终端发送下行信道的重复相关功能对应的下行传输。
该实施方式中，可以是通过预先配置多个的资源或组，这些资源或组分别与进行上述请求或指示，以及不进行上述请求或指示对应。这样通过终端在发送MsgA选择不同资源或组实现上述指示或请求。例如：可以独立配置两套MsgA资源分别由支持common PDCCH/PDSCH重复的终端和不支持common PDCCH/PDSCH重复的终端使用。网络根据所检测终端所用MsgA资源确定终端的common PDCCH/PDSCH重复能力，即实现上述指示或请求。
上述实施方式中，可以实现在实现上述指示或请求不需要引入额外的消息，进而节约传输资源。
在一些实施方式中，所述Msg3 PUSCH通过如下至少一项进行指示或请求：
所述Msg3 PUSCH中携带的信息、所述Msg3 PUSCH的时域资源、所述Msg3 PUSCH的频域资源、所述Msg3 PUSCH的DMRS资源、所述Msg3 PUSCH的载荷大小、所述Msg3 PUSCH是否做重复传输；
其中，所述指示包括：指示所述终端支持的下行信道的重复相关功能，所述请求包括：请求向所述终端发送下行信道的重复相关功能对应的下行传输。
上述Msg3 PUSCH中携带的信息可以是，可以重用现有字段或者引入新的字段或者使用逻辑信道标识(logic channel ID)来指示。
该实施方式中，可以是通过预先配置多个的资源、载荷大小，这些资源、载荷大小分别与进行上述请求或指示，以及不进行上述请求或指示对应。这样通过终端在发送Msg3PUSCH选择不同资源或载荷大小实现上述指示或请求。例如：可以独立配置两种Msg3PUSCH载荷大小(如Preamble group A，Preamble group B)，由支持common PDCCH/PDSCH重复的终端和不支持common PDCCH/PDSCH重复的终端使用。网络根据所检测终端所用载荷大小确定终端的common PDCCH/PDSCH重复能力，即实现上述指示或请求。
另外，上述Msg3 PUSCH是否做重复传输可以是，当终端支持Msg3 PUSCH，则终端就支持后续的一种或者多种common PDCCH/PDSCH重复接收，即实现上述指示或请求。
上述实施方式中，可以实现在实现上述指示或请求不需要引入额外的消息，进而节约传输资源。
在一些实施方式中，所述Msg1用于指示所述Msg3 PUSCH的载荷大小或所述Msg3PUSCH是否做重复传输，其中，所述Msg3 PUSCH的载荷大小或所述Msg3 PUSCH是否做重复传输用于进行指示或请求；
其中，所述指示包括：指示所述终端支持的下行信道的重复相关功能，所述请求包括：请求向所述终端发送下行信道的重复相关功能对应的下行传输。
该实施方式中，可以实现通过Msg1指示所述Msg3 PUSCH的载荷大小或所述Msg3PUSCH是否做重复传输，以进行指示或请求。具体为，由于Msg3 PUSCH的载荷大小的大小以及Msg3 PUSCH是否做重复传输是在Msg1接收这一步就可以被网络知道，从而该实施方式中，公共PDCCH/PDSCH可以是Msg3发送前的下行信道，比如Msg2/BPDCCH/PDSCH。例如：网络可以通过检测Msg1的时域资源或频域资源等信息确定Msg3PUSCH的载荷大小或Msg3 PUSCH是否做重复传输。
上述实施方式中，可以实现在实现上述指示或请求不需要引入额外的消息，进而节约传输资源。
作为一种可选的实施方式，所述目标消息用于指示如下至少一项：
所述终端的优先级、所述终端的类型、所述终端所处的频段、所述终端的能力等级；
其中，所述终端的优先级用于指示所述终端支持的下行信道的重复相关功能，或用于请求向所述终端发送下行信道的重复相关功能对应的下行传输；
所述终端的类型用于指示所述终端支持的下行信道的重复相关功能，或用于请求向所述终端发送下行信道的重复相关功能对应的下行传输；
所述终端所处的频段用于指示所述终端支持的下行信道的重复相关功能，或用于请求向所述终端发送下行信道的重复相关功能对应的下行传输；
所述终端的能力等级用于指示所述终端支持的下行信道的重复相关功能，或用于请求向所述终端发送下行信道的重复相关功能对应的下行传输。
该实施方式中，上述目标消息可以是任何能够显式或隐式指示所述终端的优先级、所述终端的类型、所述终端所处的频段、所述终端的能力等级的消息。
该实施方式中，可以实现基于终端的优先级、类型、所处的频段、能力等级中的至少一项来实现上述指示或请求，从而不需要引入额外的消息，进而节约传输资源。
例如：优先级为1的终端支持Common PDCCH/PDSCH repetition。优先级为2的终端不支持Common PDCCH/PDSCH repetition。
例如：对于用户驻地设备(Customer premises equipment，CPE)终端，下行支持Common PDCCH/PDSCH repetition，对于智能手机(smart phone)，下行不支持Common PDCCH/PDSCH repetition，因为对于smart phone上行可能是覆盖受限的。
例如：对于频率范围(Frequency range，FR)2，支持Common PDCCH/PDSCH repetition，对于FR1，不支持Common PDCCH/PDSCH repetition，因为FR2的基站大小通常比较小，发射功率甚至接近手机。
例如：能力等级1的终端能够支持common PDCCH/PDSCH repetition，能力等级2的终端不支持common PDCCH/PDSCH repetition
例如：能力等级1的终端能够支持动态(dynamic)和半静态(semi-static)的common PDCCH/PDSCH repetition，能力等级2的终端能够支持semi-static的common PDCCH/PDSCH repetition，不支持dynamic的common PDCCH/PDSCH repetition，能力等 级3的终端不支持common PDCCH/PDSCH repetition。
作一种可选的实施方式，所述下行信道的重复相关功能，包括如下至少一项：
所述下行信道的重复传输；
所述下行信道的接收窗口延长；
允许所述下行信道的重复传输超过所述下行信道对应的接收窗口；
所述下行信道对应的计时器延长；
允许所述下行信道的重复传输超过所述下行信道对应的计时器的持续时间。
在一些实施方式中，所述下行信道的接收窗口，包括如下至少一项：RAR窗口(RAR window)、消息B MsgB响应窗口(MsgB response window)。
在一些实施方式中，所述下行信道对应的计时器，包括：竞争解决计时器(Contention resolution timer)。
上述下行信道的接收窗口延长可以是对下行信道的接收窗口进行扩展，例如：在不支持上述下行信道重复传输对应的接收窗口的基础上进行扩展，以延长接收窗口的时长，或者重新定义支持上述下行信道重复传输对应的接收窗口。
上述下行信道对应的计时器延长可以是对下行信道对应的计时器进行扩展，例如：在不支持上述下行信道重复传输对应的计时器的基础上进行扩展，以延长计时器的时长，或者重新定义支持上述下行信道重复传输对应的计时器。
该实施方式中，终端可以是支持上述一项或者多项功能。
另外，上述多项之前可以具备关联关系，例如：指示终端支持下行信道的接收窗口延长，也表示终端支持下行信道的重复传输，即终端具备接收下行信道的重复传输的能力；又例如：指示终端允许所述下行信道的重复传输超过所述下行信道对应的接收窗口，也表示终端支持下行信道的重复传输，即终端具备接收下行信道的重复传输的能力；又例如：指示下行信道对应的计时器延长，也表示终端支持下行信道的重复传输，即终端具备接收下行信道的重复传输的能力；又例如：允许所述下行信道的重复传输超过所述下行信道对应的计时器的持续时间，也表示终端支持下行信道的重复传输，即终端具备接收下行信道的重复传输的能力。
可选地，所述下行信道的重复传输，包括如下至少一项：
一个TRP的所述下行信道的重复传输；
多个TRP之间的所述下行信道的重复传输；
基于可用时隙(available slot)的所述下行信道的重复传输；
基于物理时隙(physical slot)的所述下行信道的重复传输；
支持所述下行信道的接收窗口延长的所述下行信道的重复传输；
不支持所述下行信道的接收窗口延长的所述下行信道的重复传输；
支持允许所述下行信道的重复传输超过所述下行信道对应的接收窗口的所述下行信道的重复传输；
不支持允许所述下行信道的重复传输超过所述下行信道对应的接收窗口的所述下行信道的重复传输；
支持所述下行信道对应的计时器延长的所述下行信道的重复传输；
不支持所述下行信道对应的计时器延长的所述下行信道的重复传输；
支持允许所述下行信道的重复传输超过所述下行信道对应的计时器的持续时间的所述下行信道的重复传输；
不支持允许所述下行信道的重复传输超过所述下行信道对应的计时器的持续时间的所述下行信道的重复传输；
在时隙内的所述下行信道的重复传输；
在时隙间的所述下行信道的重复传输；
在控制资源集内的所述下行信道的重复传输；
在控制资源集间的所述下行信道的重复传输；
在CSS内的所述下行信道的重复传输；
在CSS间的所述下行信道的重复传输；
在监视时机(monitoring occasion，MO)内的所述下行信道的重复传输；
在MO间的所述下行信道的重复传输；
所述下行信道的时域重复传输；
所述下行信道的频域重复传输；
动态的所述下行信道的重复传输；
半静态的所述下行信道的重复传输；
无线资源控制(Radio Resource Control，RRC)连接建立前的所述下行信道的重复传输；
在接收到专用PDSCH配置前的所述下行信道的重复传输。
上述一个TRP的所述下行信道的重复传输可以是，common PDCCH/PDSCH重复是针对一个TRP，或者，common PDCCH/PDSCH重复来自一个TRP。
上述多个TRP之间的所述下行信道的重复传输可以是，common PDCCH/PDSCH重复是针对多个TRP，或者，common PDCCH/PDSCH重复来自多个TRP。
上述控制资源集可以是CORESET#0或其他任意CORESET。
上述CSS可以是Type0/0A/1/2CSS集中的任意一个或多个。
上述MO为PDCCH的监视时机，可以是相同搜索空间的，也可以是不同搜索空间的。
上述下行信道的时域重复传输可以称作时域下行信道重复传输，例如：时域common PDCCH repetition，该时域重复可以是以下至少一项：
相同CORESET的相同搜索空间的不同PDCCH MO上的repetition；
相同或不同CORESET的不同搜索空间间的repetition；
不同CORESET的相同搜索空间内的repetition。
上述下行信道的频域重复传输可以称作频域下行信道重复传输，例如：频域common PDCCH repetition，该频域重复可以是以下至少一项：
相同CORESET的相同PDCCH MO上的repetition；
不同CORESET的相同PDCCH MO上的repetition。
其中，相同PDCCH MO可以位于相同的搜索空间或不同的搜索空间上，例如，不同repetition的在一个时刻的CORESET资源复制了多份。
上述动态的所述下行信道的重复传输可以是，动态确定的下行信道的重复传输。
上述半静态的所述下行信道的重复传输可以是预先配置或者周期性确定的下行信道的重复传输。
上述RRC连接建立前的所述下行信道的重复传输可以是，所有RRC建立前的common PDCCH/PDSCH重复，上述在接收到专用PDSCH(dedicated PDSCH)配置前的所述下行信道的重复传输可以是，在dedicated PDSCH配置收到前的所有common PDCCH/PDSCH重复。
上述实施方式中，定义了多种下行信道重复传输的能力，这样终端可以基于需求进行灵活指示或请求，以提高终端的业务性能。
可选地，在所述下行信道的重复传输包括多项重复传输的情况下，所述多项重复传输是独立的终端能力，或者，所述多项重复传输是合并的终端能力；或，
在所述下行信道的重复传输包括多项重复传输的情况下，所述多项重复传输通过同一所述目标消息指示，或者，所述多项重复传输通过至少两个所述目标消息指示。
其中，上述多项可以是上述上行信道的重复传输包括的全部或者部分项。
上述多项重复传输是独立的终端能力可以是，上述多项每项可以理解为一个独立的能力，例如：动态的所述下行信道的重复传输和半静态的所述下行信道的重复传输是独立的能力；而上述多项重复传输是合并的终端能力可以是，上述多项作为一种整体的能力，例如：动态的所述下行信道的重复传输和半静态的所述下行信道的重复传输是一个能力。
其中，通过独立的终端能力可以提高指示或请求的灵活性，可以针对每项能力进行单独指示或请求，通过上述多项重复传输是合并的终端能力可以节约传输开销。
上述多项重复传输通过同一所述目标消息指示可以实现通过一个目标消息实现多项能力指示或请求，这样可以节约传输资源，上述多项重复传输通过至少两个所述目标消息指示可以是，每个目标消息指示或请求一项或者多项能力，以实现灵活指示或请求。
可选地，所述下行信道的重复传输是以终端类型为粒度定义(即每个用户设备(per User Equipment，per UE)类型定义)的，或者，所述下行信道的重复传输是以终端的优先级为粒度定义(即per UE的优先级定义)的。
其中，上述终端类型可以是低能力终端(RedCap UE)或者非RedCap UE，或者地面网络(terrestrial network，TN)终端或非地面网络(non-terrestrial network，NTN)终端。
该实施方式中，可以实现以终端类型为粒度或优先级为粒度定义下行信道的重复传输， 从而可以实现下行信道的重复传输的定义更加精细化，以满足更多场景或业务需求。
可选地，所述下行信道的重复传输的能力与目标下行信道重复传输能力匹配，所述目标下行信道重复传输能力为所述终端进入连接态后的下行信道重复传输能力。
上述下行信道的重复传输的能力与目标下行信道重复传输能力匹配可以是，上述上行信道的重复传输与终端进入连接态下的某种PDCCH/PDSCH重复能力一致。
例如：上述能力可以是现有的PDSCH多时隙重复(pdsch-RepetitionMultiSlots)能力，即只要终端具备pdsch-RepetitionMultiSlots能力，网络就可以认为终端也具备common PDSCH repetition能力。
又例如：上述能力可以是多TRP PDCCH重复(mTRP-PDCCH-Repetition)能力，即只要UE具备mTRP-PDCCH-Repetition-r17能力，网络就可以认为终端也具备common PDCCH repetition能力。
该实施方式中，由于下行信道的重复传输的能力与目标下行信道重复传输能力匹配，这样可以减少能力上报，节约传输开销。
可选地，在所述终端支持所述下行信道的重复传输的情况下，所述终端支持所述下行信道的接收窗口延长；或
在所述终端支持所述下行信道的重复传输的情况下，所述终端支持：允许所述下行信道的重复传输超过所述下行信道对应的接收窗口；或
在所述终端支持所述下行信道的重复传输的情况下，所述终端支持所述下行信道对应的计时器延长；或
在所述终端支持所述下行信道的重复传输的情况下，所述终端支持：允许所述下行信道的重复传输超过所述下行信道对应的计时器的持续时间。
该实施方式中，可以实现在终端支持所述下行信道的重复传输确定终端支持如下至少一项：
持所述下行信道的接收窗口延长；
允许所述下行信道的重复传输超过所述下行信道对应的接收窗口；
所述下行信道对应的计时器延长；
允许所述下行信道的重复传输超过所述下行信道对应的计时器的持续时间。
这样，可以减少目标消息的开销。
可选地，在所述下行信道的重复相关功能包括多项功能的情况下，所述多项功能通过同一所述目标消息指示，或者，所述多项功能通过至少两个所述目标消息指示。
其中，上述多项功能是指如下中的多项：
所述下行信道的重复传输；
所述下行信道的接收窗口延长；
允许所述下行信道的重复传输超过所述下行信道对应的接收窗口；
所述下行信道对应的计时器延长；
允许所述下行信道的重复传输超过所述下行信道对应的计时器的持续时间。
其中，上述多项功能通过同一目标消息指示，这样可以节约传输资源，上述多项功能通过至少两个所述目标消息指示可以是，同一个目标消息指示或请求上述一项或多项，这样可以实现指示或请求更加灵活。
作为一种可选的实施方式，所述终端发送目标消息，包括：
所述终端在目标条件下发送所述目标消息，所述目标条件包括如下至少一项：
下行信号的参考信号接收功率(Reference Signal Received Power，RSRP)高于或者等于第一阈值；
下行信号的参考信号接收质量(Reference Signal Received Quality，RSRQ)高于或者等于第二阈值；
所述下行信道对应的上行信道做重复传输，或者，所述下行信道对应的上行信道不做重复传输；
针对所述下行信道的全部或者部分信道使用相同的重复请求条件；
所述下行信道的全部或者部分信道针对的RSRQ的阈值相同，或者，所述下行信道的全部或者部分信道针对的RSRP的阈值不相同，
所述下行信道的全部或者部分信道针对的RSRQ的阈值相同，或者，所述下行信道的全部或者部分信道针对的RSRQ的阈值不相同。
上述下行信号可以是下行参考信号，例如：用于估计路损(pathloss)的参考信号.
上述下行信道对应的上行信道做重复传输可以是，Msg1或者MsgA或者Msg3或者用于Msg4混合自动重传请求确认(Hybrid automatic repeat request acknowledgement，HARQ-ACK)做了重复传输；
上述下行信道对应的上行信道不做重复传输可以是，Msg1或者MsgA或者Msg3或者用于Msg4混合自动重传请求确认(Hybrid automatic repeat request acknowledgement，HARQ-ACK)未做重复传输。
具体的，上述目标条件可以是协议约定，或者网络侧配置，或者终端决定的。
该实施方式中，可以实现在上述目标条件下才发送上述目标消息，以节约传输开销。
作为一种可选的实施方式，所述方法还包括：
在所述终端未发送所述目标消息的情况下，所述终端接收配置信息，所述配置信息用于配置所述下行信道的重复传输资源；
其中，在所述终端支持的下行信道的重复相关功能的情况下，所述终端在所述下行信道的重复传输资源和所述下行信道的非重复传输资源进行盲检，或，在所述终端不支持的下行信道的重复相关功能的情况下，所述终端在所述下行信道的非重复传输资源进行盲检。
上述配置信息可以是通过系统信息配置的，例如：通过主信息块(Master Information Block，MIB)配置的。
上述在所述终端未发送所述目标消息的情况下，所述终端接收配置信息可以是，在终 端发送上述目标消息之前，终端接收上述配置信息。
另外，终端在下行信道的重复传输资源和下行信道的非重复传输资源进行盲检可以是在发送上述目标消息之前，或者发送目标消息之后，在下行信道的重复传输资源和下行信道的非重复传输资源进行盲检。
该实施方式中，可以实现在未发送目标消息的情况下，如果终端支持的下行信道的重复相关功能，则终端可以在下行信道的重复传输资源和下行信道的非重复传输资源进行盲检，从而提高终端下行信道的接收性能。
在本申请实施例中，终端发送目标消息，所述目标消息用于如下至少一项：指示所述终端支持的下行信道的重复相关功能；请求向所述终端发送下行信道的重复相关功能对应的下行传输；其中，所述下行信道包括如下至少一项：公共PDCCH、公共PDSCH。这样能够支持公共PDCCH、公共PDSCH中至少一项重复传输，进而提高终端接收下行信道的成功率，以提高终端的业务性能。
例如：在一些场景下，比如NTN场景下，当卫星需要支持多个波束(beam)的情况下，每个beam的下行发送功率会降低。这时Common PDCCH，如调度Msg2/MsgB/Msg4的PDCCH，或者common PDSCH比如携带Msg2或者MsgB或者Msg4的PDSCH，其接收性能由于不支持重复发送而无法满足要求，使得随机接入都无法完成，进而使所有业务(比如新空口承载语音(Voice over New Radio，VoNR)，低速数据传输)信道都无法进一步进行下去。这种情况下，本申请实施例中支持Common PDCCH和common PDSCH的重复传输功能的汇报或者终端对common PDCCH/PDSCH重复的请求(比如终端在一定条件下才请求网络调度common PDCCH/PDSCH的重复)。另外，为了确保终端能在支持下行重复功能的同时，在一定时间内结束对这些相关下行PDSCH信道的接收，本申请实施例中，支持RAR window扩展或者contention resolution timer时间长度的扩展功能，以及向网络指示这些能力，且网络侧可以决定是否配置终端执行这些功能。
又例如：为使网络能知道终端重复接收common PDCCH/PDSCH的相关功能或者请求，本申请实施例中，可以合并一些功能作为一个公共的终端能力，从而降低终端能力上报或者重复请求的复杂度。
请参见图3，图3是本申请实施例提供的一种消息接收方法的流程图，如图3所示，包括以下步骤：
步骤301、网络侧设备接收终端发送的目标消息，所述目标消息用于如下至少一项：
指示所述终端支持的下行信道的重复相关功能；
请求向所述终端发送下行信道的重复相关功能对应的下行传输；
其中，所述下行信道包括如下至少一项：
公共物理下行控制信道PDCCH、公共物理下行共享信道PDSCH。
可选地，所述公共PDCCH包括如下至少一项：
在所述终端进入连接态之前需要发送的PDCCH；
在公共PDCCH资源上传输的PDCCH；
或，
所述公共PDSCH包括：
在所述终端进入连接态之前发送接收的PDSCH。
可选地，所述目标消息包括如下至少一项：
物理随机接入信道PRACH、Msg1、Msg3 PUSCH、MsgA、MsgA PUSCH、所述终端在连接态发送的消息。
可选地，所述PRACH通过如下至少一项进行指示或请求：
所述PRACH的时域资源、所述PRACH的频域资源、所述PRACH的配置索引、所述PRACH的序列、所述PRACH的序列的加扰序列、所述PRACH的格式、所述PRACH是否做重复传输；
或，
所述MsgA PUSCH通过如下至少一项进行指示或请求：
所述MsgA PUSCH中携带的信息、所述MsgA PUSCH的时域资源、所述MsgA PUSCH的频域资源、所述MsgA PUSCH的解调参考信号DMRS资源、所述MsgA PUSCH所在的组、所述MsgA PUSCH是否做重复传输；
或，
所述MsgA通过如下至少一项进行指示或请求：
所述MsgA的时域资源、所述MsgA的频域资源、所述MsgA的DMRS资源；
或，
所述Msg3 PUSCH通过如下至少一项进行指示或请求：
所述Msg3 PUSCH中携带的信息、所述Msg3 PUSCH的时域资源、所述Msg3 PUSCH的频域资源、所述Msg3 PUSCH的DMRS资源、所述Msg3 PUSCH的载荷大小、所述Msg3 PUSCH是否做重复传输；
或，
所述Msg1用于指示所述Msg3 PUSCH的载荷大小或所述Msg3 PUSCH是否做重复传输，其中，所述Msg3 PUSCH的载荷大小或所述Msg3 PUSCH是否做重复传输用于进行指示或请求；
其中，所述指示包括：指示所述终端支持的下行信道的重复相关功能，所述请求包括：请求向所述终端发送下行信道的重复相关功能对应的下行传输。
可选地，所述目标消息用于指示如下至少一项：
所述终端的优先级、所述终端的类型、所述终端所处的频段、所述终端的能力等级；
其中，所述终端的优先级用于指示所述终端支持的下行信道的重复相关功能，或用于请求向所述终端发送下行信道的重复相关功能对应的下行传输；
所述终端的类型用于指示所述终端支持的下行信道的重复相关功能，或用于请求向所 述终端发送下行信道的重复相关功能对应的下行传输；
所述终端所处的频段用于指示所述终端支持的下行信道的重复相关功能，或用于请求向所述终端发送下行信道的重复相关功能对应的下行传输；
所述终端的能力等级用于指示所述终端支持的下行信道的重复相关功能，或用于请求向所述终端发送下行信道的重复相关功能对应的下行传输。
可选地，所述下行信道的重复相关功能，包括如下至少一项：
所述下行信道的重复传输；
所述下行信道的接收窗口延长；
允许所述下行信道的重复传输超过所述下行信道对应的接收窗口；
所述下行信道对应的计时器延长；
允许所述下行信道的重复传输超过所述下行信道对应的计时器的持续时间。
可选地，所述下行信道的接收窗口，包括如下至少一项：RAR窗口、MsgB响应窗口；或，
所述下行信道对应的计时器，包括：竞争解决计时器。
可选地，所述下行信道的重复传输，包括如下至少一项：
一个TRP的所述下行信道的重复传输；
多个TRP之间的所述下行信道的重复传输；
基于可用时隙的所述下行信道的重复传输；
基于物理时隙的所述下行信道的重复传输；
支持所述下行信道的接收窗口延长的所述下行信道的重复传输；
不支持所述下行信道的接收窗口延长的所述下行信道的重复传输；
支持允许所述下行信道的重复传输超过所述下行信道对应的接收窗口的所述下行信道的重复传输；
不支持允许所述下行信道的重复传输超过所述下行信道对应的接收窗口的所述下行信道的重复传输；
支持所述下行信道对应的计时器延长的所述下行信道的重复传输；
不支持所述下行信道对应的计时器延长的所述下行信道的重复传输；
支持允许所述下行信道的重复传输超过所述下行信道对应的计时器的持续时间的所述下行信道的重复传输；
不支持允许所述下行信道的重复传输超过所述下行信道对应的计时器的持续时间的所述下行信道的重复传输；
在时隙内的所述下行信道的重复传输；
在时隙间的所述下行信道的重复传输；
在控制资源集内的所述下行信道的重复传输；
在控制资源集间的所述下行信道的重复传输；
在公共搜索空间CSS内的所述下行信道的重复传输；
在CSS间的所述下行信道的重复传输；
在监视时机内的所述下行信道的重复传输；
在监视时机间的所述下行信道的重复传输；
所述下行信道的时域重复传输；
所述下行信道的频域重复传输；
动态的所述下行信道的重复传输；
半静态的所述下行信道的重复传输；
无线资源控制RRC连接建立前的所述下行信道的重复传输；
在接收到专用PDSCH配置前的所述下行信道的重复传输。
可选地，在所述下行信道的重复传输包括多项重复传输的情况下，所述多项重复传输是独立的终端能力，或者，所述多项重复传输是合并的终端能力；或，
在所述下行信道的重复传输包括多项重复传输的情况下，所述多项重复传输通过同一所述目标消息指示，或者，所述多项重复传输通过至少两个所述目标消息指示。
可选地，所述下行信道的重复传输是以终端类型为粒度定义的，或者，所述下行信道的重复传输是以终端的优先级为粒度定义的。
可选地，所述下行信道的重复传输的能力与目标下行信道重复传输能力匹配，所述目标下行信道重复传输能力为所述终端进入连接态后的下行信道重复传输能力。
可选地，在所述终端支持所述下行信道的重复传输的情况下，确定所述终端支持所述下行信道的接收窗口延长；或
在所述终端支持所述下行信道的重复传输的情况下，确定所述终端支持：允许所述下行信道的重复传输超过所述下行信道对应的接收窗口；或
在所述终端支持所述下行信道的重复传输的情况下，确定所述终端支持所述下行信道对应的计时器延长；或
在所述终端支持所述下行信道的重复传输的情况下，确定所述终端支持：允许所述下行信道的重复传输超过所述下行信道对应的计时器的持续时间。
可选地，在所述下行信道的重复相关功能包括多项功能的情况下，所述多项功能通过同一所述目标消息指示，或者，所述多项功能通过至少两个所述目标消息指示。
可选地，所述公共PDSCH，包括如下至少一项：
Msg2 PDSCH、MsgB PDSCH、Msg4 PDSCH；或，
所述公共PDCCH，包括如下至少一项：
SIB1 PDCCH、OSIPDCCH、Msg2 PDCCH、Msg4 PDCCH、MsgB PDCCH、寻呼PDCCH、调度Msg3重传的PDCCH。
可选地，所述方法还包括：
在未接收到所述终端发送的所述目标消息的情况下，所述网络侧设备向所述终端发送 配置信息，所述配置信息用于配置所述下行信道的重复传输资源。
需要说明的是，本实施例作为与图2所示的实施例中对应的网络侧设备的实施方式，其具体的实施方式可以参见图2所示的实施例的相关说明，以为避免重复说明，本实施例不再赘述。
下面通过多个实施例对本申请实施例提供的方法进行举例说明：
实施例一：
该实施例主要描述Common PDCCH/PDSCH重复能力指示或者重复请求指示，具体如下：
在一些实施例中，Common PDCCH/PDSCH重复接收能力或者重复请求的指示至少通过PRACH资源或者信息指示，这里的PRACH资源或者信息包括如下一种或者多种：
PRACH时域资源、PRACH频域资源、PRACH配置索引、PRACH序列、PRACH序列的加扰序列、PRACH格式PRACH是否做repetition。
如预定义一组preamble序列索引(或其它上述因素)，该preamble序列索引对应的PRACH隐式指示后续的一种或者多种common PDCCH/PDSCH会重复传输。
比如只要终端支持PRACH repetition，终端就支持后续的一种或者多种common PDCCH/PDSCH重复接收。
其中，上述PRACH可以是Msg1 PRACH或者MsgA PRACH。
在一些实施例中，common PDCCH/PDSCH重复能力或者重复请求至少通过MsgA PUSCH指示，包括如下一种或者多种方式：
显式的由MsgA PUSCH中携带的信息直接指示，比如，可以重用已有字段或者引入新的字段或者使用逻辑信道标识(logic channel ID)来指示；
隐式的由MSgA PUSCH间接指示，包括如下一种或者多种方面：
MsgA PUSCH的时域资源、MsgA PUSCH的频域资源、MsgA PUSCH的DMRS资源、MsgA PUSCH所在的组(group)、MsgA PUSCH是否做repetition；
例如：可以独立配置多套MsgA PUSCH资源分别给支持common PDCCH/PDSCH repetition传输的终端和不支持common PDCCH/PDSCH repetition传输的终端使用。网络根据所检测终端所用MsgA PUSCH资源确定终端是否支持common PDCCH/PDSCH重复功能。
又例如：在2-step RACH的MsgA配置中，配置两组PUSCH传输机会：PO group A和PO group B，其中，PO group A由支持common PDCCH/PDSCH repetition传输的终端使用，PO group B由不支持common PDCCH/PDSCH repetition传输的终端使用。网络根据检测两个PO group上的PUSCH确定某个终端是否支持接收或者是否请求PDCCH/PDSCH repetition。
其中，在2-step RACH本身没有Msg4的发送，但是当2-step RACH fallback或者switch到4-step RACH后，对应还是有MsgA PUSCH传输的。这种情况下，可以通过MsgA PUSCH 来指示对应的Msg4 PDCCH/PDSCH的重复能力。
在一些实施例中，common PDCCH/PDSCH重复能力或者重复请求至少是隐式的由MsgA间接指示，包括如下一种或者多种方式：
MsgA的时域资源、MsgA的频域资源、MsgA的DMRS资源。
例如，可以独立配置两套MsgA资源分别由支持common PDCCH/PDSCH重复的终端和不支持common PDCCH/PDSCH重复的终端使用。网络根据所检测终端所用MsgA资源确定终端的common PDCCH/PDSCH重复能力。
在一些实施例中，common PDCCH/PDSCH重复能力或者重复请求至少由Msg3PUSCH相关参数/属性确定，包括如下一种或者多种方法：
显式的由Msg3 PUSCH中携带的信息直接指示，例如：可以重用已有字段或者引入新的字段或者使用logic channel ID来指示，如，使用Msg3里的备用比特；
隐式的由Msg3 PUSCH间接指示，包括如下一种或者多种方面：
Msg3 PUSCH的时域资源、Msg3 PUSCH的频域资源、Msg3 PUSCH的DMRS资源、Msg3 PUSCH负载(payload)大小(Preamble group A，Preamble group B)、Msg3 PUSCH是否做repetition(是否选择支持msg3 repetition的PRACH资源)。
其中，上述common PDCCH/PDSCH可以是Msg3传输后的Msg4 PDCCH/PDSCH。
另外，由于Msg3 payload的大小以及Msg3是否做repetition是在Msg1接收这一步就可以被网络知道，所以这里所述common PDCCH/PDSCH也可以是Msg3发送前的下行信道，比如Msg2/B PDCCH/PDSCH。
在一些实施例中，Common PDCCH/PDSCH repetition的终端能力上报或者Common PDCCH/PDSCH repetition请求至少通过如下一种或多种方法：
基于终端的优先级来确定，比如Msg3所指示的终端优先级，例如优先级为1的终端支持Common PDCCH/PDSCH repetition，优先级为2的终端不支持Common PDCCH/PDSCH repetition；
基于终端的类型来确定，例如：对于CPE终端，下行支持Common PDCCH/PDSCH repetition，对于智能手机(smart phone)，下行不支持Common PDCCH/PDSCH repetition。因为对于smart phone上行可能是覆盖受限的；
基于频段来确定，例如：对于FR2，支持Common PDCCH/PDSCH repetition，对于FR1，不支持Common PDCCH/PDSCH repetition。因为FR2的基站大小通常比较小，发射功率甚至接近手机；
基于终端的能力等级确定，例如：能力等级1的终端能够支持common PDCCH/PDSCH repetition，能力等级2的终端不支持common PDCCH/PDSCH repetition；又例如：能力等级1的终端能够支持动态(dynamic)和半静态(semi-static)的common PDCCH/PDSCH repetition，能力等级2的终端能够支持semi-static的common PDCCH/PDSCH repetition，不支持dynamic的common PDCCH/PDSCH repetition，能力等级3的终端不支持common  PDCCH/PDSCH repetition。
在一些实施例中，dynamic common PDCCH/PDSCH重复和semi-static common PDCCH/PDSCH重复是独立终端能力(separate UE capability)。
例如：当网络在SIB1配置一个重复系数(repetition factor)时，这样的common PDCCH/PDSCH重复可以对应半静态重复能力；当网络在SIB1配置多个repetition factor时，网络可以动态配置终端对每次common PDCCH/PDSCH传输使用其中的哪一个repetition factor，这样的common PDCCH/PDSCH重复可以对应为动态重复能力。
在一些实施例中，dynamic common PDCCH/PDSCH重复和semi-static common PDCCH/PDSCH重复是一个终端能力。
在一些实施例中，common PDCCH/PDSCH重复能力包括如下一种或者多种组合：
common PDCCH/PDSCH重复是针对一个TRP；
common PDCCH/PDSCH重复是针对多个TRP；
基于可用时隙(available slot)的common PDCCH/PDSCH重复；
基于物理时隙(physical slot)的common PDCCH/PDSCH重复；
是否支持RAR window扩展(RAR window extension)；
是否支持Msg2 PDCCH/PDSCH repetition超出RAR window；
是否支持竞争解决定时器持续时间扩展(contention resolution timer duration extension)；
是否支持Msg4 PDCCH/PDSCH repetition超出竞争解决定时器持续时间(contention resolution timer duration)；
时隙内(Intra-slot)common PDCCH/PDSCH repetition；
时隙间(Inter-slot)common PDCCH/PDSCH repetition；
控制资源集内(Intra-coreset)common PDCCH repetition；
控制资源集间(Inter-coreset)common PDCCH repetition；这里的CORESET可以是CORESET#0或其他任意CORESET；
CSS内(Intra-CSS)common PDCCH repetition；
CSS间(Inter-CSS)common PDCCH repetition；这里的CSS可以是Type0/0A/1/2CSS set中的任意一个或多个；
MO内(Intra-MO)common PDCCH repetition；
MO间(Inter-MO)common PDCCH repetition；上述MO为PDCCH的监视时机，可以是相同搜索空间的，也可以是不同搜索空间的；
时域common PDCCH repetition，所述时域重复可以是以下至少一项：相同CORESET的相同搜索空间的不同PDCCH MO上的repetition；相同或不同CORESET的不同搜索空间间的repetition；不同CORESET的相同搜索空间内的repetition；
频域common PDCCH repetition，所述频域重复可以是以下至少一项：相同CORESET的相同PDCCH MO上的repetition；不同CORESET的相同PDCCH MO上的repetition。 其中，相同PDCCH MO可以位于相同的搜索空间或不同的搜索空间上，例如，不同repetition的在一个时刻的CORESET资源复制了多份；
common PDCCH/PDSCH重复来自一个TRP；
common PDCCH/PDSCH重复来自多个TRP。
在一些实施例中，上述两种或者多种能力独立终端能力(separate UE capability)或者合并的终端能力。
在一些实施例中，所述Common PDCCH/PDSCH repetition能力或者Common PDCCH/PDSCH repetition请求的定义是per终端类型定义的，或者per终端的优先级定义的。这里的不同类型终端比如可以是RedCap终端或者非RedCap终端。或者TN终端或NTN终端。
在一些实施例中，当common PDCCH/PDSCH有多种重复能力时，各种能力的组合可以通过不同PRACH/MsgA/MsgA-PUSCH/Msg3相关参数/属性或者显式信息汇报。
例如：通过PRACH不同preamble group来区分各种Msg2/MsgB/Msg4 PDCCH/PDSCH重复能力。假设终端需要汇报是否支持基于available slot的或者支持RAR window extension的Msg2/MsgB/Msg4 PDCCH/PDSCH重复，每个PRACH occasion上定义四组preamble group，group A表示只支持基于available slot的重复，group B表示支持RAR window extension的重复，group C表示既支持基于available slot的重复也支持RAR window extension的重复，group D表示两种重复都不支持。例如：表1表示：
表1：
在一些实施例中，终端进入RRC连接态状态后，汇报common PDCCH/PDSCH repetition的能力。这里的能力汇报可以是如下一种或者多种方式：
不同种类(比如Msg2/MsgB/Msg4 PDCCH/PDSCH等信道)的common PDCCH/PDSCH重复能力独立汇报；例如，对于Common PDCCH重复，可以存在SIB1 PDCCH repetition的终端能力或者请求，OSIPDCCH repetition的终端能力或者请求，Msg2/4/B PDCCH repetition的终端能力或者请求，Paging PDCCH repetition的终端能力或者请求，以及调度Msg3重传的PDCCH repetition的终端能力或者请求。
不同种类(比如Msg2/MsgB/Msg4 PDCCH/PDSCH等信道)的common PDCCH/PDSCH重复能力合并为一个能力；例如，终端只需要上报一个接收common PDCCH repetition的终端能力，表明终端可以支持所有Common PDCCH信道(SIB1 PDCCH，OSIPDCCH， Msg2/4/B PDCCH，Paging PDCCH，以及调度Msg3重传的PDCCH)的repetition传输。
另外，在一些实施例中，定义如下一种或者多种下行不同种类的common PDCCH/PDSCH重复能力：
所有RRC建立前的common PDCCH/PDSCH重复；
在专用PDSCH(dedicated PDSCH)配置收到前的所有common PDCCH/PDSCH重复；
可以于终端进入连接态下的某种PDCCH/PDSCH重复能力一致，例如：上述能力可以是现有的PDSCH多时隙重复(pdsch-RepetitionMultiSlots)能力，即只要终端具备pdsch-RepetitionMultiSlots能力，网络就可以认为终端也具备common PDSCH repetition能力；又例如：上述能力可以是多TRP PDCCH重复(mTRP-PDCCH-Repetition)能力，即只要终端具备mTRP-PDCCH-Repetition-r17能力，网络就可以认为终端也具备common PDCCH repetition能力。
在一些实施例中，没有终端接收common PDCCH repetition能力的上报或请求，网络通过MIB配置PDCCH repetition资源，终端基于自身能力来接收repetition传输。
例如：不具备PDCCH repetition能力的终端只会在legacy PDCCH发送位置进行盲检；
具备PDCCH repetition能力的终端会在legacy PDCCH和repetition PDCCH发送位置都进行盲检。
在一些实施例中，Common PDCCH/PDSCH的重复请求需要满足如下一种或者多种条件：
下行信号测量的RSRP/RSRQ超过或者不小于某个阈值，这里的下行信号比如可用于估计路损(pathloss)的参考信号；
对应的Msg1或者MsgA或者Msg3或者用于Msg4 HARQ-ACK反馈的PUCCH是否做了重复传输；
一种或者多种不同的Common PDCCH/PDSCH，比如Msg2/MsgB/Msg4/Paging PDCCH/PDSCH，使用至少一种相同的重复请求条件；
下行信号测量的RSRP/RSRQ阈值针对Common PDCCH/PDSCH可以相同或者不同，例如：通过相对于某个参考RSRP加上不同的RSRP offset确定Msg2/MsgB/Msg4PDCCH/PDSCH重复请求对应的RSRP阈值。
实施例二
该实施例中主要描述RAR(Msg2 or MsgB)window extension(即上述实施例中的接收窗口延长)或Msg2/MsgB repetition超出RAR window的能力的确定，具体如下：
在一些实施例中，Msg2/MsgB PDCCH的接收时需要在RAR window或者MsgB response window内完成的。当Msg2/msgB PDCCH重复发送时，为了能够支持足够多的重复，本实施例中对RAR window长度进行延长，对应需要终端有相应的能力。
在一些实施例中，为了允许在RAR window内让网络能够发送多次RAR(类似于RAR window内的多次RAR传输)，RAR PDSCH的发送时间可能也需要尽量在RAR window 内完成。当RAR PDSCH支持repetition时，本实施例对RAR window长度进行延长。同时也需要考虑是否允许RAR的重复超过RAR window。
在一些实施例中，RAR window extension或Msg2/MsgB PDCCH/PDSCH repetition超出RAR window的能力也可以通过前面用于实施例一中indicate common PDCCH/PDSCH重复能力的一种或者多种方法指示。
在一些实施例中，RAR window extension或Msg2/MsgB PDCCH/PDSCH repetition超出RAR window的能力由Msg2/MsgB PDCCH/PDSCH repetition能力确定。例如：只要终端支持Msg2/msgB PDCCH/PDSCH repetition,就支持RAR window extension或msg2/MsgB PDCCH/PDSCH repetition超出RAR window.。
在一些实施例中，RAR window extension或Msg2/MsgB PDCCH/PDSCH repetition超出RAR window的能力为强制(mandatory)的。
在一些实施例中，不同类型终端的RAR window extension或Msg2/MsgB PDCCH/PDSCH repetition超出RAR window的能力或Common PDCCH/PDSCH repetition能力可以独立汇报。这里的不同类型终端比如可以是RedCap终端或者非RedCap终端。
实施例三：
该实施例中主要描述Contention resolution timer或Msg4 PDCCH/PDSCH repetition超出Contention resolution timer duration的能力的确定，具体如下：
在一些实施例中，Msg4 PDCCH的接收需要在contention resolution timer没有过期的状态下完成。当Msg4 PDCCH重复发送时，为了能够支持足够多的重复，本实施例中对contention resolution timer的长度进行延长，对应需要终端有相应的能力。
在一些实施例中，为了允许在Contention resolution timer duration内让网络能够多次调度Msg4传输(有点类似于Contention resolution timer duration内的多次Msg4传输)，Msg4的发送时间可能也需要尽量在Contention resolution timer duration内完成。当Msg4支持repetition时，本实施例对Contention resolution timer duration长度进行延长。同时也需要考虑是否允许Msg4的重复超出Contention resolution timer duration。
在一些实施例中，Contention resolution timer duration extension或Msg4 PDCCH/PDSCH repetition超出Contention resolution timer duration的能力也可以通过前面用于实施例一中indicate common PDCCH/PDSCH重复能力的一种或者多种方法指示。
在一些实施例中，Contention resolution timer duration extension或Msg4 PDCCH/PDSCH repetition超出Contention resolution timer duration的能力由Msg4 PDCCH/PDSCH repetition能力确定。例如：只要终端支持Msg4 PDCCH/PDSCH repetition，就支持Contention resolution timer duration extension或Msg4 PDCCH/PDSCH repetition超出Contention resolution timer duration的能力。
在一些实施例中，Contention resolution timer duration extension或Msg4 PDCCH/PDSCH repetition超出Contention resolution timer duration的能力为强制的。
在一些实施例中，不同类型终端的Contention resolution timer duration extension或Msg4 PDCCH/PDSCH repetition超出Contention resolution timer duration的能力或Common PDCCH/PDSCH repetition能力可以独立汇报。这里的不同类型终端比如可以是RedCap终端或者非RedCap终端。
本申请实施例，提出Common PDCCH/PDSCH重复传输接收相关功能指示或者传输请求，从而使网络可以使能这些增强技术，进而提升了common PDCCH/PDSCH的传输可靠性，从而确保在随机接入的成功率及降低随机接入的延时。另外，本申请实施例还可以合并一些可以合并的终端功能，从而降低终端能力汇报或者重复请求的复杂度，提高资源利用率。引入了有条件的能力汇报，即重复请求，从而避免对太多没有覆盖问题的终端也使用common PDCCH/PDSCH重复，以提高这些终端的业务性能。
本申请实施例提供的消息发送方法，执行主体可以为消息发送装置。本申请实施例中以通知装置执行消息发送方法为例，说明本申请实施例提供的消息发送装置。
本申请实施例提供的消息接收方法，执行主体可以为消息接收装置。本申请实施例中以通知装置执行消息接收方法为例，说明本申请实施例提供的消息接收装置。
请参见图4，图4是本申请实施例提供的一种消息发送装置的结构图，如图4所示，消息发送装置400包括：
发送模块401，用于发送目标消息，所述目标消息用于如下至少一项：
指示所述终端支持的下行信道的重复相关功能；
请求向所述终端发送下行信道的重复相关功能对应的下行传输；
其中，所述下行信道包括如下至少一项：
公共PDCCH、公共PDSCH。
可选地，所述公共PDCCH包括如下至少一项：
所述终端进入连接态之前需要接收的PDCCH；
在公共PDCCH资源上传输的PDCCH；
或，
所述公共PDSCH包括：
所述终端进入连接态之前需要接收的PDSCH。
可选地，所述目标消息包括如下至少一项：
PRACH、Msg1、Msg3 PUSCH、MsgA、MsgA PUSCH、所述终端在连接态发送的消息。
可选地，所述PRACH通过如下至少一项进行指示或请求：
所述PRACH的时域资源、所述PRACH的频域资源、所述PRACH的配置索引、所述PRACH的序列、所述PRACH的序列的加扰序列、所述PRACH的格式、所述PRACH是否做重复传输；
或，
所述MsgA PUSCH通过如下至少一项进行指示或请求：
所述MsgA PUSCH中携带的信息、所述MsgA PUSCH的时域资源、所述MsgA PUSCH的频域资源、所述MsgA PUSCH的解调参考信号DMRS资源、所述MsgA PUSCH所在的组、所述MsgA PUSCH是否做重复传输；
或，
所述MsgA通过如下至少一项进行指示或请求：
所述MsgA的时域资源、所述MsgA的频域资源、所述MsgA的DMRS资源；或，
所述Msg3 PUSCH通过如下至少一项进行指示或请求：
所述Msg3 PUSCH中携带的信息、所述Msg3 PUSCH的时域资源、所述Msg3 PUSCH的频域资源、所述Msg3 PUSCH的DMRS资源、所述Msg3 PUSCH的载荷大小、所述Msg3 PUSCH是否做重复传输；
或，
所述Msg1用于指示所述Msg3 PUSCH的载荷大小或所述Msg3 PUSCH是否做重复传输，其中，所述Msg3 PUSCH的载荷大小或所述Msg3 PUSCH是否做重复传输用于进行指示或请求；
其中，所述指示包括：指示所述终端支持的下行信道的重复相关功能，所述请求包括：请求向所述终端发送下行信道的重复相关功能对应的下行传输。
可选地，所述目标消息用于指示如下至少一项：
所述终端的优先级、所述终端的类型、所述终端所处的频段、所述终端的能力等级；
其中，所述终端的优先级用于指示所述终端支持的下行信道的重复相关功能，或用于请求向所述终端发送下行信道的重复相关功能对应的下行传输；
所述终端的类型用于指示所述终端支持的下行信道的重复相关功能，或用于请求向所述终端发送下行信道的重复相关功能对应的下行传输；
所述终端所处的频段用于指示所述终端支持的下行信道的重复相关功能，或用于请求向所述终端发送下行信道的重复相关功能对应的下行传输；
所述终端的能力等级用于指示所述终端支持的下行信道的重复相关功能，或用于请求向所述终端发送下行信道的重复相关功能对应的下行传输。
可选地，所述下行信道的重复相关功能，包括如下至少一项：
所述下行信道的重复传输；
所述下行信道的接收窗口延长；
允许所述下行信道的重复传输超过所述下行信道对应的接收窗口；
所述下行信道对应的计时器延长；
允许所述下行信道的重复传输超过所述下行信道对应的计时器的持续时间。
可选地，所述下行信道的接收窗口，包括如下至少一项：随机接入响应RAR窗口、 MsgB响应窗口；或，
所述下行信道对应的计时器，包括：竞争解决计时器。
可选地，所述下行信道的重复传输，包括如下至少一项：
一个发送接收点TRP的所述下行信道的重复传输；
多个TRP之间的所述下行信道的重复传输；
基于可用时隙的所述下行信道的重复传输；
基于物理时隙的所述下行信道的重复传输；
支持所述下行信道的接收窗口延长的所述下行信道的重复传输；
不支持所述下行信道的接收窗口延长的所述下行信道的重复传输；
支持允许所述下行信道的重复传输超过所述下行信道对应的接收窗口的所述下行信道的重复传输；
不支持允许所述下行信道的重复传输超过所述下行信道对应的接收窗口的所述下行信道的重复传输；
支持所述下行信道对应的计时器延长的所述下行信道的重复传输；
不支持所述下行信道对应的计时器延长的所述下行信道的重复传输；
支持允许所述下行信道的重复传输超过所述下行信道对应的计时器的持续时间的所述下行信道的重复传输；
不支持允许所述下行信道的重复传输超过所述下行信道对应的计时器的持续时间的所述下行信道的重复传输；
在时隙内的所述下行信道的重复传输；
在时隙间的所述下行信道的重复传输；
在控制资源集内的所述下行信道的重复传输；
在控制资源集间的所述下行信道的重复传输；
在公共搜索空间CSS内的所述下行信道的重复传输；
在CSS间的所述下行信道的重复传输；
在监视时机内的所述下行信道的重复传输；
在监视时机间的所述下行信道的重复传输；
所述下行信道的时域重复传输；
所述下行信道的频域重复传输；
动态的所述下行信道的重复传输；
半静态的所述下行信道的重复传输；
无线资源控制RRC连接建立前的所述下行信道的重复传输；
在接收到专用PDSCH配置前的所述下行信道的重复传输。
可选地，在所述下行信道的重复传输包括多项重复传输的情况下，所述多项重复传输是独立的终端能力，或者，所述多项重复传输是合并的终端能力；或，
在所述下行信道的重复传输包括多项重复传输的情况下，所述多项重复传输通过同一所述目标消息指示，或者，所述多项重复传输通过至少两个所述目标消息指示。
可选地，所述下行信道的重复传输是以终端类型为粒度定义的，或者，所述下行信道的重复传输是以终端的优先级为粒度定义的。
可选地，所述下行信道的重复传输的能力与目标下行信道重复传输能力匹配，所述目标下行信道重复传输能力为所述终端进入连接态后的下行信道重复传输能力。
可选地，在所述终端支持所述下行信道的重复传输的情况下，所述终端支持所述下行信道的接收窗口延长；或
在所述终端支持所述下行信道的重复传输的情况下，所述终端支持：允许所述下行信道的重复传输超过所述下行信道对应的接收窗口；或
在所述终端支持所述下行信道的重复传输的情况下，所述终端支持所述下行信道对应的计时器延长；或
在所述终端支持所述下行信道的重复传输的情况下，所述终端支持：允许所述下行信道的重复传输超过所述下行信道对应的计时器的持续时间。
可选地，在所述下行信道的重复相关功能包括多项功能的情况下，所述多项功能通过同一所述目标消息指示，或者，所述多项功能通过至少两个所述目标消息指示。
可选地，所述终端发送目标消息，包括：
所述终端在目标条件下发送所述目标消息，所述目标条件包括如下至少一项：
下行信号的参考信号接收功率RSRP高于或者等于第一阈值；
下行信号的参考信号接收质量RSRQ高于或者等于第二阈值；
所述下行信道对应的上行信道做重复传输，或者，所述下行信道对应的上行信道不做重复传输；
针对所述下行信道的全部或者部分信道使用相同的重复请求条件；
所述下行信道的全部或者部分信道针对的RSRP的阈值相同，或者，所述下行信道的全部或者部分信道针对的RSRP的阈值不相同，
所述下行信道的全部或者部分信道针对的RSRQ的阈值相同，或者，所述下行信道的全部或者部分信道针对的RSRQ的阈值不相同。
可选地，所述公共PDSCH，包括如下至少一项：
Msg2 PDSCH、MsgB PDSCH、Msg4 PDSCH；或，
所述公共PDCCH，包括如下至少一项：
SIB1 PDCCH、OSIPDCCH、Msg2 PDCCH、Msg4 PDCCH、MsgB PDCCH、寻呼PDCCH、调度Msg3重传的PDCCH。
可选地，所述装置还包括：
接收模块，用于在所述终端未发送所述目标消息的情况下，接收配置信息，所述配置信息用于配置所述下行信道的重复传输资源；
其中，在所述终端支持的下行信道的重复相关功能的情况下，所述终端在所述下行信道的重复传输资源和所述下行信道的非重复传输资源进行盲检，或，在所述终端不支持的下行信道的重复相关功能的情况下，所述终端在所述下行信道的非重复传输资源进行盲检。
上述消息发送装置可以提高终端的业务性能。
本申请实施例中消息发送装置可以是电子设备，例如具有操作系统的电子设备，也可以是电子设备中的部件，例如集成电路或芯片。例如：该电子设备可以是终端，也可以为除终端之外的其他设备。示例性的，终端可以包括但不限于本申请实施例所列举的终端的类型，其他设备可以为服务器、网络附属存储器(Network Attached Storage，NAS)等，本申请实施例不作具体限定。
本申请实施例提供的消息发送装置能够实现图2所示的方法实施例实现的各个过程，并达到相同的技术效果，为避免重复，这里不再赘述。
请参见图5，图5是本申请实施例提供的一种消息接收装置的结构图，如图5所示，消息接收装置500包括：
接收模块501，用于接收终端发送的目标消息，所述目标消息用于如下至少一项：
指示所述终端支持的下行信道的重复相关功能；
请求向所述终端发送下行信道的重复相关功能对应的下行传输；
其中，所述下行信道包括如下至少一项：
公共物理下行控制信道PDCCH、公共物理下行共享信道PDSCH。
可选地，所述公共PDCCH包括如下至少一项：
在所述终端进入连接态之前需要发送的PDCCH；
在公共PDCCH资源上传输的PDCCH；
或，
所述公共PDSCH包括：
在所述终端进入连接态之前发送接收的PDSCH。
可选地，所述目标消息包括如下至少一项：
物理随机接入信道PRACH、Msg1、Msg3 PUSCH、MsgA、MsgA PUSCH、所述终端在连接态发送的消息。
可选地，所述PRACH通过如下至少一项进行指示或请求：
所述PRACH的时域资源、所述PRACH的频域资源、所述PRACH的配置索引、所述PRACH的序列、所述PRACH的序列的加扰序列、所述PRACH的格式、所述PRACH是否做重复传输；
或，
所述MsgA PUSCH通过如下至少一项进行指示或请求：
所述MsgA PUSCH中携带的信息、所述MsgA PUSCH的时域资源、所述MsgA PUSCH的频域资源、所述MsgA PUSCH的解调参考信号DMRS资源、所述MsgA PUSCH所在的 组、所述MsgA PUSCH是否做重复传输；
或，
所述MsgA通过如下至少一项进行指示或请求：
所述MsgA的时域资源、所述MsgA的频域资源、所述MsgA的DMRS资源；
或，
所述Msg3 PUSCH通过如下至少一项进行指示或请求：
所述Msg3 PUSCH中携带的信息、所述Msg3 PUSCH的时域资源、所述Msg3 PUSCH的频域资源、所述Msg3 PUSCH的DMRS资源、所述Msg3 PUSCH的载荷大小、所述Msg3 PUSCH是否做重复传输；
或，
所述Msg1用于指示所述Msg3 PUSCH的载荷大小或所述Msg3 PUSCH是否做重复传输，其中，所述Msg3 PUSCH的载荷大小或所述Msg3 PUSCH是否做重复传输用于进行指示或请求；
其中，所述指示包括：指示所述终端支持的下行信道的重复相关功能，所述请求包括：请求向所述终端发送下行信道的重复相关功能对应的下行传输。
可选地，所述目标消息用于指示如下至少一项：
所述终端的优先级、所述终端的类型、所述终端所处的频段、所述终端的能力等级；
其中，所述终端的优先级用于指示所述终端支持的下行信道的重复相关功能，或用于请求向所述终端发送下行信道的重复相关功能对应的下行传输；
所述终端的类型用于指示所述终端支持的下行信道的重复相关功能，或用于请求向所述终端发送下行信道的重复相关功能对应的下行传输；
所述终端所处的频段用于指示所述终端支持的下行信道的重复相关功能，或用于请求向所述终端发送下行信道的重复相关功能对应的下行传输；
所述终端的能力等级用于指示所述终端支持的下行信道的重复相关功能，或用于请求向所述终端发送下行信道的重复相关功能对应的下行传输。
可选地，所述下行信道的重复相关功能，包括如下至少一项：
所述下行信道的重复传输；
所述下行信道的接收窗口延长；
允许所述下行信道的重复传输超过所述下行信道对应的接收窗口；
所述下行信道对应的计时器延长；
允许所述下行信道的重复传输超过所述下行信道对应的计时器的持续时间。
可选地，所述下行信道的接收窗口，包括如下至少一项：RAR窗口、MsgB响应窗口；或，
所述下行信道对应的计时器，包括：竞争解决计时器。
可选地，所述下行信道的重复传输，包括如下至少一项：
一个发送接收点TRP的所述下行信道的重复传输；
多个TRP之间的所述下行信道的重复传输；
基于可用时隙的所述下行信道的重复传输；
基于物理时隙的所述下行信道的重复传输；
支持所述下行信道的接收窗口延长的所述下行信道的重复传输；
不支持所述下行信道的接收窗口延长的所述下行信道的重复传输；
支持允许所述下行信道的重复传输超过所述下行信道对应的接收窗口的所述下行信道的重复传输；
不支持允许所述下行信道的重复传输超过所述下行信道对应的接收窗口的所述下行信道的重复传输；
支持所述下行信道对应的计时器延长的所述下行信道的重复传输；
不支持所述下行信道对应的计时器延长的所述下行信道的重复传输；
支持允许所述下行信道的重复传输超过所述下行信道对应的计时器的持续时间的所述下行信道的重复传输；
不支持允许所述下行信道的重复传输超过所述下行信道对应的计时器的持续时间的所述下行信道的重复传输；
在时隙内的所述下行信道的重复传输；
在时隙间的所述下行信道的重复传输；
在控制资源集内的所述下行信道的重复传输；
在控制资源集间的所述下行信道的重复传输；
在公共搜索空间CSS内的所述下行信道的重复传输；
在CSS间的所述下行信道的重复传输；
在监视时机内的所述下行信道的重复传输；
在监视时机间的所述下行信道的重复传输；
所述下行信道的时域重复传输；
所述下行信道的频域重复传输；
动态的所述下行信道的重复传输；
半静态的所述下行信道的重复传输；
无线资源控制RRC连接建立前的所述下行信道的重复传输；
在接收到专用PDSCH配置前的所述下行信道的重复传输。
可选地，在所述下行信道的重复传输包括多项重复传输的情况下，所述多项重复传输是独立的终端能力，或者，所述多项重复传输是合并的终端能力；或，
在所述下行信道的重复传输包括多项重复传输的情况下，所述多项重复传输通过同一所述目标消息指示，或者，所述多项重复传输通过至少两个所述目标消息指示。
可选地，所述下行信道的重复传输是以终端类型为粒度定义的，或者，所述下行信道 的重复传输是以终端的优先级为粒度定义的。
可选地，所述下行信道的重复传输的能力与目标下行信道重复传输能力匹配，所述目标下行信道重复传输能力为所述终端进入连接态后的下行信道重复传输能力。
可选地，在所述终端支持所述下行信道的重复传输的情况下，确定所述终端支持所述下行信道的接收窗口延长；或
在所述终端支持所述下行信道的重复传输的情况下，确定所述终端支持：允许所述下行信道的重复传输超过所述下行信道对应的接收窗口；或
在所述终端支持所述下行信道的重复传输的情况下，确定所述终端支持所述下行信道对应的计时器延长；或
在所述终端支持所述下行信道的重复传输的情况下，确定所述终端支持：允许所述下行信道的重复传输超过所述下行信道对应的计时器的持续时间。
可选地，在所述下行信道的重复相关功能包括多项功能的情况下，所述多项功能通过同一所述目标消息指示，或者，所述多项功能通过至少两个所述目标消息指示。
可选地，所述公共PDSCH，包括如下至少一项：
Msg2 PDSCH、MsgB PDSCH、Msg4 PDSCH；或，
所述公共PDCCH，包括如下至少一项：
SIB1 PDCCH、OSIPDCCH、Msg2 PDCCH、Msg4 PDCCH、MsgB PDCCH、寻呼PDCCH、调度Msg3重传的PDCCH。
可选地，所述装置还包括：
发送模块，用于在未接收到所述终端发送的所述目标消息的情况下，向所述终端发送配置信息，所述配置信息用于配置所述下行信道的重复传输资源。
上述消息接收装置可以提高终端的业务性能。
本申请实施例中的消息接收装置可以是电子设备，例如具有操作系统的电子设备，也可以是电子设备中的部件，例如集成电路或芯片。该电子设备可以是终端或网络侧设备。
本申请实施例提供的消息接收装置能够实现图3所示的方法实施例实现的各个过程，并达到相同的技术效果，为避免重复，这里不再赘述。
可选地，如图6所示，本申请实施例还提供一种通信设备600，包括处理器601和存储器602，存储器602上存储有可在所述处理器601上运行的程序或指令，例如，该通信设备600为终端时，该程序或指令被处理器601执行时实现上述消息发送方法实施例的各个步骤，且能达到相同的技术效果。该通信设备600为网络侧设备时，该程序或指令被处理器601执行时实现上述消息接收方法实施例的各个步骤，且能达到相同的技术效果，为避免重复，这里不再赘述。
本申请实施例还提供了一种终端，包括处理器及通信接口，其中，所述通信接口用于发送目标消息，所述目标消息用于如下至少一项：指示所述终端支持的下行信道的重复相关功能；请求向所述终端发送下行信道的重复相关功能对应的下行传输；其中，所述下行 信道包括如下至少一项：公共PDCCH、公共PDSCH。
如图7所示，终端700包括但不限于：射频单元701、网络模块702、音频输出单元703、输入单元704、传感器705、显示单元706、用户输入单元707、接口单元708、存储器709以及处理器710等中的至少部分部件。
本领域技术人员可以理解，终端700还可以包括给各个部件供电的电源(比如电池)，电源可以通过电源管理系统与处理器710逻辑相连，从而通过电源管理系统实现管理充电、放电、以及功耗管理等功能。图7中示出的通信设备结构并不构成对通信设备的限定，通信设备可以包括比图示更多或更少的部件，或者组合某些部件，或者不同的部件布置，在此不再赘述。
应理解的是，本申请实施例中，输入单元704可以包括图形处理器(Graphics Processing Unit，GPU)7041和麦克风7042，图形处理器7041对在视频捕获模式或图像捕获模式中由图像捕获装置(如摄像头)获得的静态图片或视频的图像数据进行处理。显示单元706可包括显示面板7061，可以采用液晶显示器、有机发光二极管等形式来配置显示面板7061。用户输入单元707包括触控面板7071以及其他输入设备7072中的至少一种。触控面板7071，也称为触摸屏。触控面板7071可包括触摸检测装置和触摸控制器两个部分。其他输入设备7072可以包括但不限于物理键盘、功能键(比如音量控制按键、开关按键等)、轨迹球、鼠标、操作杆，在此不再赘述。
本申请实施例中，射频单元701接收来自网络侧设备的下行数据后，可以传输给处理器710进行处理；另外，射频单元701可以向网络侧设备发送上行数据。通常，射频单元701包括但不限于天线、放大器、收发信机、耦合器、低噪声放大器、双工器等。
存储器709可用于存储软件程序或指令以及各种数据。存储器709可主要包括存储程序或指令的第一存储区和存储数据的第二存储区，其中，第一存储区可存储操作系统、至少一个功能所需的应用程序或指令(比如声音播放功能、图像播放功能等)等。此外，存储器709可以包括易失性存储器或非易失性存储器，或者，存储器709可以包括易失性和非易失性存储器两者。其中，非易失性存储器可以是只读存储器(Read-Only Memory，ROM)、可编程只读存储器(Programmable ROM，PROM)、可擦除可编程只读存储器(Erasable PROM，EPROM)、电可擦除可编程只读存储器(Electrically EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(Random Access Memory，RAM)，静态随机存取存储器(Static RAM，SRAM)、动态随机存取存储器(Dynamic RAM，DRAM)、同步动态随机存取存储器(Synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(Double Data Rate SDRAM，DDRSDRAM)、增强型同步动态随机存取存储器(Enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(Synch link DRAM，SLDRAM)和直接内存总线随机存取存储器(Direct Rambus RAM，DRRAM)。本申请实施例中的存储器709包括但不限于这些和任意其它适合类型的存储器。
处理器710可包括一个或多个处理单元；可选地，处理器710集成应用处理器和调制 解调处理器，其中，应用处理器主要处理涉及操作系统、用户界面和应用程序等的操作，调制解调处理器主要处理无线通信信号，如基带处理器。可以理解的是，上述调制解调处理器也可以不集成到处理器710中。
射频单元701，用于发送目标消息，所述目标消息用于如下至少一项：
指示所述终端支持的下行信道的重复相关功能；
请求向所述终端发送下行信道的重复相关功能对应的下行传输；
其中，所述下行信道包括如下至少一项：
公共PDCCH、公共PDSCH。
可选地，所述公共PDCCH包括如下至少一项：
所述终端进入连接态之前需要接收的PDCCH；
在公共PDCCH资源上传输的PDCCH；
或，
所述公共PDSCH包括：
所述终端进入连接态之前需要接收的PDSCH。
可选地，所述目标消息包括如下至少一项：
PRACH、Msg1、Msg3 PUSCH、MsgA、MsgA PUSCH、所述终端在连接态发送的消息。
可选地，所述PRACH通过如下至少一项进行指示或请求：
所述PRACH的时域资源、所述PRACH的频域资源、所述PRACH的配置索引、所述PRACH的序列、所述PRACH的序列的加扰序列、所述PRACH的格式、所述PRACH是否做重复传输；
或，
所述MsgA PUSCH通过如下至少一项进行指示或请求：
所述MsgA PUSCH中携带的信息、所述MsgA PUSCH的时域资源、所述MsgA PUSCH的频域资源、所述MsgA PUSCH的解调参考信号DMRS资源、所述MsgA PUSCH所在的组、所述MsgA PUSCH是否做重复传输；
或，
所述MsgA通过如下至少一项进行指示或请求：
所述MsgA的时域资源、所述MsgA的频域资源、所述MsgA的DMRS资源；
或，
所述Msg3 PUSCH通过如下至少一项进行指示或请求：
所述Msg3 PUSCH中携带的信息、所述Msg3 PUSCH的时域资源、所述Msg3 PUSCH的频域资源、所述Msg3 PUSCH的DMRS资源、所述Msg3 PUSCH的载荷大小、所述Msg3 PUSCH是否做重复传输；
或，
所述Msg1用于指示所述Msg3 PUSCH的载荷大小或所述Msg3 PUSCH是否做重复传输，其中，所述Msg3 PUSCH的载荷大小或所述Msg3 PUSCH是否做重复传输用于进行指示或请求；
其中，所述指示包括：指示所述终端支持的下行信道的重复相关功能，所述请求包括：请求向所述终端发送下行信道的重复相关功能对应的下行传输。
可选地，所述目标消息用于指示如下至少一项：
所述终端的优先级、所述终端的类型、所述终端所处的频段、所述终端的能力等级；
其中，所述终端的优先级用于指示所述终端支持的下行信道的重复相关功能，或用于请求向所述终端发送下行信道的重复相关功能对应的下行传输；
所述终端的类型用于指示所述终端支持的下行信道的重复相关功能，或用于请求向所述终端发送下行信道的重复相关功能对应的下行传输；
所述终端所处的频段用于指示所述终端支持的下行信道的重复相关功能，或用于请求向所述终端发送下行信道的重复相关功能对应的下行传输；
所述终端的能力等级用于指示所述终端支持的下行信道的重复相关功能，或用于请求向所述终端发送下行信道的重复相关功能对应的下行传输。
可选地，所述下行信道的重复相关功能，包括如下至少一项：
所述下行信道的重复传输；
所述下行信道的接收窗口延长；
允许所述下行信道的重复传输超过所述下行信道对应的接收窗口；
所述下行信道对应的计时器延长；
允许所述下行信道的重复传输超过所述下行信道对应的计时器的持续时间。
可选地，所述下行信道的接收窗口，包括如下至少一项：RAR窗口、MsgB响应窗口；或，
所述下行信道对应的计时器，包括：竞争解决计时器。
可选地，所述下行信道的重复传输，包括如下至少一项：
一个发送接收点TRP的所述下行信道的重复传输；
多个TRP之间的所述下行信道的重复传输；
基于可用时隙的所述下行信道的重复传输；
基于物理时隙的所述下行信道的重复传输；
支持所述下行信道的接收窗口延长的所述下行信道的重复传输；
不支持所述下行信道的接收窗口延长的所述下行信道的重复传输；
支持允许所述下行信道的重复传输超过所述下行信道对应的接收窗口的所述下行信道的重复传输；
不支持允许所述下行信道的重复传输超过所述下行信道对应的接收窗口的所述下行信道的重复传输；
支持所述下行信道对应的计时器延长的所述下行信道的重复传输；
不支持所述下行信道对应的计时器延长的所述下行信道的重复传输；
支持允许所述下行信道的重复传输超过所述下行信道对应的计时器的持续时间的所述下行信道的重复传输；
不支持允许所述下行信道的重复传输超过所述下行信道对应的计时器的持续时间的所述下行信道的重复传输；
在时隙内的所述下行信道的重复传输；
在时隙间的所述下行信道的重复传输；
在控制资源集内的所述下行信道的重复传输；
在控制资源集间的所述下行信道的重复传输；
在公共搜索空间CSS内的所述下行信道的重复传输；
在CSS间的所述下行信道的重复传输；
在监视时机内的所述下行信道的重复传输；
在监视时机间的所述下行信道的重复传输；
所述下行信道的时域重复传输；
所述下行信道的频域重复传输；
动态的所述下行信道的重复传输；
半静态的所述下行信道的重复传输；
无线资源控制RRC连接建立前的所述下行信道的重复传输；
在接收到专用PDSCH配置前的所述下行信道的重复传输。
可选地，在所述下行信道的重复传输包括多项重复传输的情况下，所述多项重复传输是独立的终端能力，或者，所述多项重复传输是合并的终端能力；或，
在所述下行信道的重复传输包括多项重复传输的情况下，所述多项重复传输通过同一所述目标消息指示，或者，所述多项重复传输通过至少两个所述目标消息指示。
可选地，所述下行信道的重复传输是以终端类型为粒度定义的，或者，所述下行信道的重复传输是以终端的优先级为粒度定义的。
可选地，所述下行信道的重复传输的能力与目标下行信道重复传输能力匹配，所述目标下行信道重复传输能力为所述终端进入连接态后的下行信道重复传输能力。
可选地，在所述终端支持所述下行信道的重复传输的情况下，所述终端支持所述下行信道的接收窗口延长；或
在所述终端支持所述下行信道的重复传输的情况下，所述终端支持：允许所述下行信道的重复传输超过所述下行信道对应的接收窗口；或
在所述终端支持所述下行信道的重复传输的情况下，所述终端支持所述下行信道对应的计时器延长；或
在所述终端支持所述下行信道的重复传输的情况下，所述终端支持：允许所述下行信 道的重复传输超过所述下行信道对应的计时器的持续时间。
可选地，在所述下行信道的重复相关功能包括多项功能的情况下，所述多项功能通过同一所述目标消息指示，或者，所述多项功能通过至少两个所述目标消息指示。
可选地，所述终端发送目标消息，包括：
所述终端在目标条件下发送所述目标消息，所述目标条件包括如下至少一项：
下行信号的参考信号接收功率RSRP高于或者等于第一阈值；
下行信号的参考信号接收质量RSRQ高于或者等于第二阈值；
所述下行信道对应的上行信道做重复传输，或者，所述下行信道对应的上行信道不做重复传输；
针对所述下行信道的全部或者部分信道使用相同的重复请求条件；
所述下行信道的全部或者部分信道针对的RSRP的阈值相同，或者，所述下行信道的全部或者部分信道针对的RSRP的阈值不相同，
所述下行信道的全部或者部分信道针对的RSRQ的阈值相同，或者，所述下行信道的全部或者部分信道针对的RSRQ的阈值不相同。
可选地，所述公共PDSCH，包括如下至少一项：
Msg2 PDSCH、MsgB PDSCH、Msg4 PDSCH；或，
所述公共PDCCH，包括如下至少一项：
SIB1 PDCCH、OSIPDCCH、Msg2 PDCCH、Msg4 PDCCH、MsgB PDCCH、寻呼PDCCH、调度Msg3重传的PDCCH。
可选地，射频单元701还用于：
在所述终端未发送所述目标消息的情况下，接收配置信息，所述配置信息用于配置所述下行信道的重复传输资源；
其中，在所述终端支持的下行信道的重复相关功能的情况下，所述终端在所述下行信道的重复传输资源和所述下行信道的非重复传输资源进行盲检，或，在所述终端不支持的下行信道的重复相关功能的情况下，所述终端在所述下行信道的非重复传输资源进行盲检。
上述终端可以提高终端的业务性能。
可以理解，本实施例中提及的各实现方式的实现过程可以参照上述方法实施例的相关描述，并达到相同或相应的技术效果，为避免重复，在此不再赘述。
本申请实施例还提供了一种网络侧设备，包括处理器及通信接口，其中，所述通信接口用于接收终端发送的目标消息，所述目标消息用于如下至少一项：指示所述终端支持的下行信道的重复相关功能；请求向所述终端发送下行信道的重复相关功能对应的下行传输；其中，所述下行信道包括如下至少一项：公共PDCCH、公共PDSCH。
如图8所示，该网络侧设备800包括：天线801、射频装置802、基带装置803、处理器804和存储器805。天线801与射频装置802连接。在上行方向上，射频装置802通过天线801接收信息，将接收的信息发送给基带装置803进行处理。在下行方向上，基带 装置803对要发送的信息进行处理，并发送给射频装置802，射频装置802对收到的信息进行处理后经过天线801发送出去。
以上实施例中无线接入网设备执行的方法可以在基带装置803中实现，该基带装置803包括基带处理器。
基带装置803例如可以包括至少一个基带板，该基带板上设置有多个芯片，如图8所示，其中一个芯片例如为基带处理器，通过总线接口与存储器805连接，以调用存储器805中的程序，执行以上方法实施例中所示的网络设备操作。
该无线接入网设备还可以包括网络接口806，该接口例如为通用公共无线接口(common public radio interface，CPRI)。
在一些实施方式中，本申请实施例的网络侧设备800还包括：存储在存储器805上并可在处理器804上运行的指令或程序，处理器804调用存储器805中的指令或程序执行图5所示各模块执行的方法，并达到相同的技术效果，为避免重复，故不在此赘述。
其中，射频装置802，用于接收终端发送的目标消息，所述目标消息用于如下至少一项：
指示所述终端支持的下行信道的重复相关功能；
请求向所述终端发送下行信道的重复相关功能对应的下行传输；
其中，所述下行信道包括如下至少一项：
公共物理下行控制信道PDCCH、公共物理下行共享信道PDSCH。
可选地，所述公共PDCCH包括如下至少一项：
在所述终端进入连接态之前需要发送的PDCCH；
在公共PDCCH资源上传输的PDCCH；
或，
所述公共PDSCH包括：
在所述终端进入连接态之前发送接收的PDSCH。
可选地，所述目标消息包括如下至少一项：
物理随机接入信道PRACH、Msg1、Msg3 PUSCHMsgA、MsgA PUSCH、所述终端在连接态发送的消息。
可选地，所述PRACH通过如下至少一项进行指示或请求：
所述PRACH的时域资源、所述PRACH的频域资源、所述PRACH的配置索引、所述PRACH的序列、所述PRACH的序列的加扰序列、所述PRACH的格式、所述PRACH是否做重复传输；
或，
所述MsgA PUSCH通过如下至少一项进行指示或请求：
所述MsgA PUSCH中携带的信息、所述MsgA PUSCH的时域资源、所述MsgA PUSCH的频域资源、所述MsgA PUSCH的解调参考信号DMRS资源、所述MsgA PUSCH所在的 组、所述MsgA PUSCH是否做重复传输；
或，
所述MsgA通过如下至少一项进行指示或请求：
所述MsgA的时域资源、所述MsgA的频域资源、所述MsgA的DMRS资源；
或，
所述Msg3 PUSCH通过如下至少一项进行指示或请求：
所述Msg3 PUSCH中携带的信息、所述Msg3 PUSCH的时域资源、所述Msg3 PUSCH的频域资源、所述Msg3 PUSCH的DMRS资源、所述Msg3 PUSCH的载荷大小、所述Msg3 PUSCH是否做重复传输；
或，
所述Msg1用于指示所述Msg3 PUSCH的载荷大小或所述Msg3 PUSCH是否做重复传输，其中，所述Msg3 PUSCH的载荷大小或所述Msg3 PUSCH是否做重复传输用于进行指示或请求；
其中，所述指示包括：指示所述终端支持的下行信道的重复相关功能，所述请求包括：请求向所述终端发送下行信道的重复相关功能对应的下行传输。
可选地，所述目标消息用于指示如下至少一项：
所述终端的优先级、所述终端的类型、所述终端所处的频段、所述终端的能力等级；
其中，所述终端的优先级用于指示所述终端支持的下行信道的重复相关功能，或用于请求向所述终端发送下行信道的重复相关功能对应的下行传输；
所述终端的类型用于指示所述终端支持的下行信道的重复相关功能，或用于请求向所述终端发送下行信道的重复相关功能对应的下行传输；
所述终端所处的频段用于指示所述终端支持的下行信道的重复相关功能，或用于请求向所述终端发送下行信道的重复相关功能对应的下行传输；
所述终端的能力等级用于指示所述终端支持的下行信道的重复相关功能，或用于请求向所述终端发送下行信道的重复相关功能对应的下行传输。
可选地，所述下行信道的重复相关功能，包括如下至少一项：
所述下行信道的重复传输；
所述下行信道的接收窗口延长；
允许所述下行信道的重复传输超过所述下行信道对应的接收窗口；
所述下行信道对应的计时器延长；
允许所述下行信道的重复传输超过所述下行信道对应的计时器的持续时间。
可选地，所述下行信道的接收窗口，包括如下至少一项：RAR窗口、MsgB响应窗口；或，
所述下行信道对应的计时器，包括：竞争解决计时器。
可选地，所述下行信道的重复传输，包括如下至少一项：
一个发送接收点TRP的所述下行信道的重复传输；
多个TRP之间的所述下行信道的重复传输；
基于可用时隙的所述下行信道的重复传输；
基于物理时隙的所述下行信道的重复传输；
支持所述下行信道的接收窗口延长的所述下行信道的重复传输；
不支持所述下行信道的接收窗口延长的所述下行信道的重复传输；
支持允许所述下行信道的重复传输超过所述下行信道对应的接收窗口的所述下行信道的重复传输；
不支持允许所述下行信道的重复传输超过所述下行信道对应的接收窗口的所述下行信道的重复传输；
支持所述下行信道对应的计时器延长的所述下行信道的重复传输；
不支持所述下行信道对应的计时器延长的所述下行信道的重复传输；
支持允许所述下行信道的重复传输超过所述下行信道对应的计时器的持续时间的所述下行信道的重复传输；
不支持允许所述下行信道的重复传输超过所述下行信道对应的计时器的持续时间的所述下行信道的重复传输；
在时隙内的所述下行信道的重复传输；
在时隙间的所述下行信道的重复传输；
在控制资源集内的所述下行信道的重复传输；
在控制资源集间的所述下行信道的重复传输；
在公共搜索空间CSS内的所述下行信道的重复传输；
在CSS间的所述下行信道的重复传输；
在监视时机内的所述下行信道的重复传输；
在监视时机间的所述下行信道的重复传输；
所述下行信道的时域重复传输；
所述下行信道的频域重复传输；
动态的所述下行信道的重复传输；
半静态的所述下行信道的重复传输；
无线资源控制RRC连接建立前的所述下行信道的重复传输；
在接收到专用PDSCH配置前的所述下行信道的重复传输。
可选地，在所述下行信道的重复传输包括多项重复传输的情况下，所述多项重复传输是独立的终端能力，或者，所述多项重复传输是合并的终端能力；或，
在所述下行信道的重复传输包括多项重复传输的情况下，所述多项重复传输通过同一所述目标消息指示，或者，所述多项重复传输通过至少两个所述目标消息指示。
可选地，所述下行信道的重复传输是以终端类型为粒度定义的，或者，所述下行信道 的重复传输是以终端的优先级为粒度定义的。
可选地，所述下行信道的重复传输的能力与目标下行信道重复传输能力匹配，所述目标下行信道重复传输能力为所述终端进入连接态后的下行信道重复传输能力。
可选地，在所述终端支持所述下行信道的重复传输的情况下，确定所述终端支持所述下行信道的接收窗口延长；或
在所述终端支持所述下行信道的重复传输的情况下，确定所述终端支持：允许所述下行信道的重复传输超过所述下行信道对应的接收窗口；或
在所述终端支持所述下行信道的重复传输的情况下，确定所述终端支持所述下行信道对应的计时器延长；或
在所述终端支持所述下行信道的重复传输的情况下，确定所述终端支持：允许所述下行信道的重复传输超过所述下行信道对应的计时器的持续时间。
可选地，在所述下行信道的重复相关功能包括多项功能的情况下，所述多项功能通过同一所述目标消息指示，或者，所述多项功能通过至少两个所述目标消息指示。
可选地，所述公共PDSCH，包括如下至少一项：
Msg2 PDSCH、MsgB PDSCH、Msg4 PDSCH；或，
所述公共PDCCH，包括如下至少一项：
SIB1 PDCCH、OSI PDCCH、Msg2 PDCCH、Msg4 PDCCH、MsgB PDCCH、寻呼PDCCH、调度Msg3重传的PDCCH。
可选地，射频装置802还用于：
在未接收到所述终端发送的所述目标消息的情况下，向所述终端发送配置信息，所述配置信息用于配置所述下行信道的重复传输资源。
上述网络侧设备可以提高终端的业务性能。
本申请实施例还提供一种可读存储介质，所述可读存储介质上存储有程序或指令，该程序或指令被处理器执行时实现上述消息发送方法或消息接收方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
其中，所述处理器为上述实施例中所述的终端中的处理器。所述可读存储介质，包括计算机可读存储介质，如计算机只读存储器ROM、随机存取存储器RAM、磁碟或者光盘等。在一些示例中，可读存储介质可以是非瞬态的可读存储介质。
本申请实施例另提供了一种芯片，所述芯片包括处理器和通信接口，所述通信接口和所述处理器耦合，所述处理器用于运行程序或指令，实现上述消息发送方法或消息接收方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
应理解，本申请实施例提到的芯片还可以称为系统级芯片，系统芯片，芯片系统或片上系统芯片等。
本申请实施例另提供了一种计算机程序/程序产品，所述计算机程序/程序产品被存储在存储介质中，所述计算机程序/程序产品被至少一个处理器执行以实现上述消息发送方 法或消息接收方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
本申请实施例还提供了一种无线通信系统，包括：终端及网络侧设备，所述终端可用于执行如本申请实施例提供的消息发送方法的步骤，所述网络侧设备可用于执行如本申请实施例提供的消息接收方法的步骤。
需要说明的是，在本文中，术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、物品或者装置不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、物品或者装置所固有的要素。在没有更多限制的情况下，由语句“包括一个……”限定的要素，并不排除在包括该要素的过程、方法、物品或者装置中还存在另外的相同要素。此外，需要指出的是，本申请实施方式中的方法和装置的范围不限按示出或讨论的顺序来执行功能，还可包括根据所涉及的功能按基本同时的方式或按相反的顺序来执行功能，例如，可以按不同于所描述的次序来执行所描述的方法，并且还可以添加、省去或组合各种步骤。另外，参照某些示例所描述的特征可在其他示例中被组合。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到上述实施例方法可借助计算机软件产品加必需的通用硬件平台的方式来实现，当然也可以通过硬件。该计算机软件产品存储在存储介质(如ROM、RAM、磁碟、光盘等)中，包括若干指令，用以使得终端或者网络侧设备执行本申请各个实施例所述的方法。
上面结合附图对本申请的实施例进行了描述，但是本申请并不局限于上述的具体实施方式，上述的具体实施方式仅仅是示意性的，而不是限制性的，本领域的普通技术人员在本申请的启示下，在不脱离本申请宗旨和权利要求所保护的范围情况下，还可做出很多形式的实施方式，这些实施方式均属于本申请的保护之内。

Claims (36)

  1. 一种消息发送方法，包括：
    终端发送目标消息，所述目标消息用于如下至少一项：
    指示所述终端支持的下行信道的重复相关功能；
    请求向所述终端发送下行信道的重复相关功能对应的下行传输；
    其中，所述下行信道包括如下至少一项：
    公共物理下行控制信道PDCCH、公共物理下行共享信道PDSCH。
  2. 如权利要求1所述的方法，其中，所述公共PDCCH包括如下至少一项：
    所述终端进入连接态之前需要接收的PDCCH；
    在公共PDCCH资源上传输的PDCCH；
    或，
    所述公共PDSCH包括：
    所述终端进入连接态之前需要接收的PDSCH。
  3. 如权利要求1或2所述的方法，其中，所述目标消息包括如下至少一项：
    物理随机接入信道PRACH、消息1 Msg1、消息3 Msg3 PUSCH、消息A MsgA、MsgA PUSCH、所述终端在连接态发送的消息。
  4. 如权利要求3所述的方法，其中，所述PRACH通过如下至少一项进行指示或请求：
    所述PRACH的时域资源、所述PRACH的频域资源、所述PRACH的配置索引、所述PRACH的序列、所述PRACH的序列的加扰序列、所述PRACH的格式、所述PRACH是否做重复传输；
    或，
    所述MsgA PUSCH通过如下至少一项进行指示或请求：
    所述MsgA PUSCH中携带的信息、所述MsgA PUSCH的时域资源、所述MsgA PUSCH的频域资源、所述MsgA PUSCH的解调参考信号DMRS资源、所述MsgA PUSCH所在的组、所述MsgA PUSCH是否做重复传输；
    或，
    所述MsgA通过如下至少一项进行指示或请求：
    所述MsgA的时域资源、所述MsgA的频域资源、所述MsgA的DMRS资源；
    或，
    所述Msg3 PUSCH通过如下至少一项进行指示或请求：
    所述Msg3 PUSCH中携带的信息、所述Msg3 PUSCH的时域资源、所述Msg3 PUSCH的频域资源、所述Msg3 PUSCH的DMRS资源、所述Msg3 PUSCH的载荷大小、所述Msg3 PUSCH是否做重复传输；
    或，
    所述Msg1用于指示所述Msg3 PUSCH的载荷大小或所述Msg3 PUSCH是否做重复 传输，其中，所述Msg3 PUSCH的载荷大小或所述Msg3 PUSCH是否做重复传输用于进行指示或请求；
    其中，所述指示包括：指示所述终端支持的下行信道的重复相关功能，所述请求包括：请求向所述终端发送下行信道的重复相关功能对应的下行传输。
  5. 如权利要求1或2所述的方法，其中，所述目标消息用于指示如下至少一项：
    所述终端的优先级、所述终端的类型、所述终端所处的频段、所述终端的能力等级；
    其中，所述终端的优先级用于指示所述终端支持的下行信道的重复相关功能，或用于请求向所述终端发送下行信道的重复相关功能对应的下行传输；
    所述终端的类型用于指示所述终端支持的下行信道的重复相关功能，或用于请求向所述终端发送下行信道的重复相关功能对应的下行传输；
    所述终端所处的频段用于指示所述终端支持的下行信道的重复相关功能，或用于请求向所述终端发送下行信道的重复相关功能对应的下行传输；
    所述终端的能力等级用于指示所述终端支持的下行信道的重复相关功能，或用于请求向所述终端发送下行信道的重复相关功能对应的下行传输。
  6. 如权利要求1至5中任一项所述的方法，其中，所述下行信道的重复相关功能，包括如下至少一项：
    所述下行信道的重复传输；
    所述下行信道的接收窗口延长；
    允许所述下行信道的重复传输超过所述下行信道对应的接收窗口；
    所述下行信道对应的计时器延长；
    允许所述下行信道的重复传输超过所述下行信道对应的计时器的持续时间。
  7. 如权利要求6所述的方法，其中，所述下行信道的接收窗口，包括如下至少一项：随机接入响应RAR窗口、消息B MsgB响应窗口；或，
    所述下行信道对应的计时器，包括：竞争解决计时器。
  8. 如权利要求6或7所述的方法，其中，所述下行信道的重复传输，包括如下至少一项：
    一个发送接收点TRP的所述下行信道的重复传输；
    多个TRP之间的所述下行信道的重复传输；
    基于可用时隙的所述下行信道的重复传输；
    基于物理时隙的所述下行信道的重复传输；
    支持所述下行信道的接收窗口延长的所述下行信道的重复传输；
    不支持所述下行信道的接收窗口延长的所述下行信道的重复传输；
    支持允许所述下行信道的重复传输超过所述下行信道对应的接收窗口的所述下行信道的重复传输；
    不支持允许所述下行信道的重复传输超过所述下行信道对应的接收窗口的所述下行 信道的重复传输；
    支持所述下行信道对应的计时器延长的所述下行信道的重复传输；
    不支持所述下行信道对应的计时器延长的所述下行信道的重复传输；
    支持允许所述下行信道的重复传输超过所述下行信道对应的计时器的持续时间的所述下行信道的重复传输；
    不支持允许所述下行信道的重复传输超过所述下行信道对应的计时器的持续时间的所述下行信道的重复传输；
    在时隙内的所述下行信道的重复传输；
    在时隙间的所述下行信道的重复传输；
    在控制资源集内的所述下行信道的重复传输；
    在控制资源集间的所述下行信道的重复传输；
    在公共搜索空间CSS内的所述下行信道的重复传输；
    在CSS间的所述下行信道的重复传输；
    在监视时机内的所述下行信道的重复传输；
    在监视时机间的所述下行信道的重复传输；
    所述下行信道的时域重复传输；
    所述下行信道的频域重复传输；
    动态的所述下行信道的重复传输；
    半静态的所述下行信道的重复传输；
    无线资源控制RRC连接建立前的所述下行信道的重复传输；
    在接收到专用PDSCH配置前的所述下行信道的重复传输。
  9. 如权利要求8所述的方法，其中，在所述下行信道的重复传输包括多项重复传输的情况下，所述多项重复传输是独立的终端能力，或者，所述多项重复传输是合并的终端能力；或，
    在所述下行信道的重复传输包括多项重复传输的情况下，所述多项重复传输通过同一所述目标消息指示，或者，所述多项重复传输通过至少两个所述目标消息指示。
  10. 如权利要求6至9中任一项所述的方法，其中，所述下行信道的重复传输是以终端类型为粒度定义的，或者，所述下行信道的重复传输是以终端的优先级为粒度定义的。
  11. 如权利要求6至10中任一项所述的方法，其中，所述下行信道的重复传输的能力与目标下行信道重复传输能力匹配，所述目标下行信道重复传输能力为所述终端进入连接态后的下行信道重复传输能力。
  12. 如权利要求6至11中任一项所述的方法，其中，在所述终端支持所述下行信道的重复传输的情况下，所述终端支持所述下行信道的接收窗口延长；或
    在所述终端支持所述下行信道的重复传输的情况下，所述终端支持：允许所述下行信道的重复传输超过所述下行信道对应的接收窗口；或
    在所述终端支持所述下行信道的重复传输的情况下，所述终端支持所述下行信道对应的计时器延长；或
    在所述终端支持所述下行信道的重复传输的情况下，所述终端支持：允许所述下行信道的重复传输超过所述下行信道对应的计时器的持续时间。
  13. 如权利要求6至12中任一项所述的方法，其中，在所述下行信道的重复相关功能包括多项功能的情况下，所述多项功能通过同一所述目标消息指示，或者，所述多项功能通过至少两个所述目标消息指示。
  14. 如权利要求1至13中任一项所述的方法，其中，所述终端发送目标消息，包括：
    所述终端在目标条件下发送所述目标消息，所述目标条件包括如下至少一项：
    下行信号的参考信号接收功率RSRP高于或者等于第一阈值；
    下行信号的参考信号接收质量RSRQ高于或者等于第二阈值；
    所述下行信道对应的上行信道做重复传输，或者，所述下行信道对应的上行信道不做重复传输；
    针对所述下行信道的全部或者部分信道使用相同的重复请求条件；
    所述下行信道的全部或者部分信道针对的RSRP的阈值相同，或者，所述下行信道的全部或者部分信道针对的RSRP的阈值不相同，
    所述下行信道的全部或者部分信道针对的RSRQ的阈值相同，或者，所述下行信道的全部或者部分信道针对的RSRQ的阈值不相同。
  15. 如权利要求1至14中任一项所述的方法，其中，所述公共PDSCH，包括如下至少一项：
    消息2 Msg2 PDSCH、消息B MsgB PDSCH、消息4 Msg4 PDSCH；或，
    所述公共PDCCH，包括如下至少一项：
    系统消息块1 SIB1 PDCCH、其他系统消息OSI PDCCH、Msg2 PDCCH、Msg4 PDCCH、MsgB PDCCH、寻呼PDCCH、调度Msg3重传的PDCCH。
  16. 如权利要求1至15中任一项所述的方法，所述方法还包括：
    在所述终端未发送所述目标消息的情况下，所述终端接收配置信息，所述配置信息用于配置所述下行信道的重复传输资源；
    其中，在所述终端支持的下行信道的重复相关功能的情况下，所述终端在所述下行信道的重复传输资源和所述下行信道的非重复传输资源进行盲检，或，在所述终端不支持的下行信道的重复相关功能的情况下，所述终端在所述下行信道的非重复传输资源进行盲检。
  17. 一种消息接收方法，包括：
    网络侧设备接收终端发送的目标消息，所述目标消息用于如下至少一项：
    指示所述终端支持的下行信道的重复相关功能；
    请求向所述终端发送下行信道的重复相关功能对应的下行传输；
    其中，所述下行信道包括如下至少一项：
    公共物理下行控制信道PDCCH、公共物理下行共享信道PDSCH。
  18. 如权利要求17所述的方法，其中，所述公共PDCCH包括如下至少一项：
    在所述终端进入连接态之前需要发送的PDCCH；
    在公共PDCCH资源上传输的PDCCH；
    或，
    所述公共PDSCH包括：
    在所述终端进入连接态之前发送接收的PDSCH。
  19. 如权利要求17或18所述的方法，其中，所述目标消息包括如下至少一项：
    物理随机接入信道PRACH、消息1 Msg1、消息3 Msg3 PUSCH、消息A MsgA、MsgA PUSCH、所述终端在连接态发送的消息。
  20. 如权利要求19所述的方法，其中，所述PRACH通过如下至少一项进行指示或请求：
    所述PRACH的时域资源、所述PRACH的频域资源、所述PRACH的配置索引、所述PRACH的序列、所述PRACH的序列的加扰序列、所述PRACH的格式、所述PRACH是否做重复传输；
    或，
    所述MsgA PUSCH通过如下至少一项进行指示或请求：
    所述MsgA PUSCH中携带的信息、所述MsgA PUSCH的时域资源、所述MsgA PUSCH的频域资源、所述MsgA PUSCH的解调参考信号DMRS资源、所述MsgA PUSCH所在的组、所述MsgA PUSCH是否做重复传输；
    或，
    所述MsgA通过如下至少一项进行指示或请求：
    所述MsgA的时域资源、所述MsgA的频域资源、所述MsgA的DMRS资源；
    或，
    所述Msg3 PUSCH通过如下至少一项进行指示或请求：
    所述Msg3 PUSCH中携带的信息、所述Msg3 PUSCH的时域资源、所述Msg3 PUSCH的频域资源、所述Msg3 PUSCH的DMRS资源、所述Msg3 PUSCH的载荷大小、所述Msg3 PUSCH是否做重复传输；
    或，
    所述Msg1用于指示所述Msg3 PUSCH的载荷大小或所述Msg3 PUSCH是否做重复传输，其中，所述Msg3 PUSCH的载荷大小或所述Msg3 PUSCH是否做重复传输用于进行指示或请求；
    其中，所述指示包括：指示所述终端支持的下行信道的重复相关功能，所述请求包括：请求向所述终端发送下行信道的重复相关功能对应的下行传输。
  21. 如权利要求17或18所述的方法，其中，所述目标消息用于指示如下至少一项：
    所述终端的优先级、所述终端的类型、所述终端所处的频段、所述终端的能力等级；
    其中，所述终端的优先级用于指示所述终端支持的下行信道的重复相关功能，或用于请求向所述终端发送下行信道的重复相关功能对应的下行传输；
    所述终端的类型用于指示所述终端支持的下行信道的重复相关功能，或用于请求向所述终端发送下行信道的重复相关功能对应的下行传输；
    所述终端所处的频段用于指示所述终端支持的下行信道的重复相关功能，或用于请求向所述终端发送下行信道的重复相关功能对应的下行传输；
    所述终端的能力等级用于指示所述终端支持的下行信道的重复相关功能，或用于请求向所述终端发送下行信道的重复相关功能对应的下行传输。
  22. 如权利要求17至21中任一项所述的方法，其中，所述下行信道的重复相关功能，包括如下至少一项：
    所述下行信道的重复传输；
    所述下行信道的接收窗口延长；
    允许所述下行信道的重复传输超过所述下行信道对应的接收窗口；
    所述下行信道对应的计时器延长；
    允许所述下行信道的重复传输超过所述下行信道对应的计时器的持续时间。
  23. 如权利要求22所述的方法，其中，所述下行信道的接收窗口，包括如下至少一项：随机接入响应RAR窗口、消息B MsgB响应窗口；或，
    所述下行信道对应的计时器，包括：竞争解决计时器。
  24. 如权利要求22或23所述的方法，其中，所述下行信道的重复传输，包括如下至少一项：
    一个发送接收点TRP的所述下行信道的重复传输；
    多个TRP之间的所述下行信道的重复传输；
    基于可用时隙的所述下行信道的重复传输；
    基于物理时隙的所述下行信道的重复传输；
    支持所述下行信道的接收窗口延长的所述下行信道的重复传输；
    不支持所述下行信道的接收窗口延长的所述下行信道的重复传输；
    支持允许所述下行信道的重复传输超过所述下行信道对应的接收窗口的所述下行信道的重复传输；
    不支持允许所述下行信道的重复传输超过所述下行信道对应的接收窗口的所述下行信道的重复传输；
    支持所述下行信道对应的计时器延长的所述下行信道的重复传输；
    不支持所述下行信道对应的计时器延长的所述下行信道的重复传输；
    支持允许所述下行信道的重复传输超过所述下行信道对应的计时器的持续时间的所述下行信道的重复传输；
    不支持允许所述下行信道的重复传输超过所述下行信道对应的计时器的持续时间的所述下行信道的重复传输；
    在时隙内的所述下行信道的重复传输；
    在时隙间的所述下行信道的重复传输；
    在控制资源集内的所述下行信道的重复传输；
    在控制资源集间的所述下行信道的重复传输；
    在公共搜索空间CSS内的所述下行信道的重复传输；
    在CSS间的所述下行信道的重复传输；
    在监视时机内的所述下行信道的重复传输；
    在监视时机间的所述下行信道的重复传输；
    所述下行信道的时域重复传输；
    所述下行信道的频域重复传输；
    动态的所述下行信道的重复传输；
    半静态的所述下行信道的重复传输；
    无线资源控制RRC连接建立前的所述下行信道的重复传输；
    在接收到专用PDSCH配置前的所述下行信道的重复传输。
  25. 如权利要求24所述的方法，其中，在所述下行信道的重复传输包括多项重复传输的情况下，所述多项重复传输是独立的终端能力，或者，所述多项重复传输是合并的终端能力；或，
    在所述下行信道的重复传输包括多项重复传输的情况下，所述多项重复传输通过同一所述目标消息指示，或者，所述多项重复传输通过至少两个所述目标消息指示。
  26. 如权利要求22至25中任一项所述的方法，其中，所述下行信道的重复传输是以终端类型为粒度定义的，或者，所述下行信道的重复传输是以终端的优先级为粒度定义的。
  27. 如权利要求22至26中任一项所述的方法，其中，所述下行信道的重复传输的能力与目标下行信道重复传输能力匹配，所述目标下行信道重复传输能力为所述终端进入连接态后的下行信道重复传输能力。
  28. 如权利要求22至27中任一项所述的方法，其中，在所述终端支持所述下行信道的重复传输的情况下，确定所述终端支持所述下行信道的接收窗口延长；或
    在所述终端支持所述下行信道的重复传输的情况下，确定所述终端支持：允许所述下行信道的重复传输超过所述下行信道对应的接收窗口；或
    在所述终端支持所述下行信道的重复传输的情况下，确定所述终端支持所述下行信道对应的计时器延长；或
    在所述终端支持所述下行信道的重复传输的情况下，确定所述终端支持：允许所述下行信道的重复传输超过所述下行信道对应的计时器的持续时间。
  29. 如权利要求22至28中任一项所述的方法，其中，在所述下行信道的重复相关功 能包括多项功能的情况下，所述多项功能通过同一所述目标消息指示，或者，所述多项功能通过至少两个所述目标消息指示。
  30. 如权利要求17至29中任一项所述的方法，其中，所述公共PDSCH，包括如下至少一项：
    消息2 Msg2 PDSCH、消息B MsgB PDSCH、消息4 Msg4 PDSCH；或，
    所述公共PDCCH，包括如下至少一项：
    系统消息块1 SIB1 PDCCH、其他系统消息OSI PDCCH、Msg2 PDCCH、Msg4 PDCCH、MsgB PDCCH、寻呼PDCCH、调度Msg3重传的PDCCH。
  31. 如权利要求17至30中任一项所述的方法，所述方法还包括：
    在未接收到所述终端发送的所述目标消息的情况下，所述网络侧设备向所述终端发送配置信息，所述配置信息用于配置所述下行信道的重复传输资源。
  32. 一种消息发送装置，包括：
    发送模块，用于发送目标消息，所述目标消息用于如下至少一项：
    指示所述终端支持的下行信道的重复相关功能；
    请求向所述终端发送下行信道的重复相关功能对应的下行传输；
    其中，所述下行信道包括如下至少一项：
    公共物理下行控制信道PDCCH、公共物理下行共享信道PDSCH。
  33. 一种消息接收装置，包括：
    接收模块，用于接收终端发送的目标消息，所述目标消息用于如下至少一项：
    指示所述终端支持的下行信道的重复相关功能；
    请求向所述终端发送下行信道的重复相关功能对应的下行传输；
    其中，所述下行信道包括如下至少一项：
    公共物理下行控制信道PDCCH、公共物理下行共享信道PDSCH。
  34. 一种终端，包括处理器和存储器，所述存储器存储可在所述处理器上运行的程序或指令，所述程序或指令被所述处理器执行时实现如权利要求1至16任一项所述的消息发送方法的步骤。
  35. 一种网络侧设备，包括处理器和存储器，所述存储器存储可在所述处理器上运行的程序或指令，所述程序或指令被所述处理器执行时实现如权利要求17至31任一项所述的消息接收方法的步骤。
  36. 一种可读存储介质，所述可读存储介质上存储程序或指令，所述程序或指令被处理器执行时实现如权利要求1至16任一项所述的消息发送方法，或者实现如权利要求17至31任一项所述的消息接收方法的步骤。
PCT/CN2024/104382 2023-07-10 2024-07-09 消息发送方法、消息接收方法、装置、终端及网络侧设备 Pending WO2025011537A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202310840176.7A CN119300167A (zh) 2023-07-10 2023-07-10 消息发送方法、消息接收方法、装置、终端及网络侧设备
CN202310840176.7 2023-07-10

Publications (1)

Publication Number Publication Date
WO2025011537A1 true WO2025011537A1 (zh) 2025-01-16

Family

ID=94151866

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2024/104382 Pending WO2025011537A1 (zh) 2023-07-10 2024-07-09 消息发送方法、消息接收方法、装置、终端及网络侧设备

Country Status (2)

Country Link
CN (1) CN119300167A (zh)
WO (1) WO2025011537A1 (zh)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2016045715A1 (en) * 2014-09-24 2016-03-31 Nokia Solutions And Networks Oy Repeated transmission of scheduling assignment for random access response
CN115104372A (zh) * 2020-02-21 2022-09-23 高通股份有限公司 用于在无线通信中发送随机接入消息的重复的技术
CN115119329A (zh) * 2021-03-23 2022-09-27 维沃移动通信有限公司 随机接入方法、装置、终端及网络侧设备
WO2023105795A1 (ja) * 2021-12-10 2023-06-15 株式会社Ｎｔｔドコモ 端末、基地局及び無線通信方法

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2016045715A1 (en) * 2014-09-24 2016-03-31 Nokia Solutions And Networks Oy Repeated transmission of scheduling assignment for random access response
CN115104372A (zh) * 2020-02-21 2022-09-23 高通股份有限公司 用于在无线通信中发送随机接入消息的重复的技术
CN115119329A (zh) * 2021-03-23 2022-09-27 维沃移动通信有限公司 随机接入方法、装置、终端及网络侧设备
WO2023105795A1 (ja) * 2021-12-10 2023-06-15 株式会社Ｎｔｔドコモ 端末、基地局及び無線通信方法

Also Published As

Publication number Publication date
CN119300167A (zh) 2025-01-10

Similar Documents

Publication Publication Date Title
CN115334587B (zh) 传输方法、终端及网络侧设备
JP7587676B2 (ja) 補助情報を伝送する方法、端末機器とネットワーク機器
JP2024545327A (ja) 伝送決定方法、装置、端末、ネットワーク側機器及び記憶媒体
WO2025016270A1 (zh) Pdcch重复传输的处理方法、装置、终端及网络侧设备
WO2023246583A1 (zh) 频域资源确定方法、终端及网络侧设备
WO2025082253A1 (zh) 随机接入资源选择方法、资源配置方法、装置及通信设备
WO2024152994A1 (zh) 随机接入处理方法、装置、终端及网络侧设备
WO2025011537A1 (zh) 消息发送方法、消息接收方法、装置、终端及网络侧设备
WO2025016269A1 (zh) 公共pdcch接收方法、发送方法、装置及设备
US20250380310A1 (en) Small data transmission method and apparatus, terminal, and network side device
WO2025011538A1 (zh) 时间确定方法、装置、终端及网络侧设备
WO2025130755A1 (zh) 上行传输方法、装置、终端、网络侧设备及介质
WO2025108494A1 (zh) 随机接入方法、装置、终端及网络侧设备
WO2024235100A1 (zh) 切换方法、配置方法、随机接入处理方法及设备
WO2025140692A1 (zh) 无线通信方法、装置及设备
WO2024212950A1 (zh) 信息传输方法、装置及通信设备
WO2025061024A1 (zh) Prach重复传输方法、装置、设备及可读存储介质
WO2025011474A1 (zh) 下行重复传输方法、装置及相关装置
WO2025119090A1 (zh) Rar接收窗口的处理方法、终端及网络侧设备
WO2025082278A1 (zh) 资源配置方法、装置、终端及网络侧设备
WO2025162370A1 (zh) 重复传输的方法、终端及网络侧设备
WO2025148928A1 (zh) 随机接入方法、装置、终端及网络侧设备
WO2025140481A1 (zh) 功率控制方法、终端及网络侧设备
WO2025026133A1 (zh) Prach重复发送方法、装置、终端、网络侧设备及介质
WO2025124281A1 (zh) 上行数据传输方法、装置、设备及存储介质

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 24838789

Country of ref document: EP

Kind code of ref document: A1