Information reporting methods, equipment, and readable storage media

Abstract

This application discloses an information reporting method, device, and readable storage medium, belonging to the field of communication technology. The method includes: a terminal generating target information based on at least one of random access related information configured by the network, first indication information, terminal related information, and first configuration information; and the terminal reporting the target information through the physical uplink shared channel PUSCH or MSG3 of the message MSGA.

Description

Technical Field

[0001] This application belongs to the field of communication technology, specifically relating to an information reporting method, device, and readable storage medium. Background Technology

[0002] In the prior art, the terminal (UE) can use MSG3 or MASA to identify low-capability (RedCap) UEs in advance. The current protocol does not define what information to carry when using MSG3 or MASA. Summary of the Invention

[0003] The purpose of this application is to provide an information reporting method, device, and readable storage medium to solve the problem that the current protocol does not define what information to carry using MSG3 or MASA.

[0004] Firstly, an information reporting method is provided, including:

[0005] The terminal generates target information based on at least one of the following: random access-related information configured in the network, first indication information, relevant information of the terminal, and first configuration information;

[0006] The terminal reports the target information via the Physical Uplink Shared Channel (PUSCH) or MSG3 of the MSGA message.

[0007] Secondly, an information reporting device is provided, comprising:

[0008] The generation module is used for the terminal to generate target information based on at least one of the following: random access-related information configured in the network, first indication information, relevant information of the terminal, and first configuration information;

[0009] The reporting module is used by the terminal to report the target information through MSGA's PUSCH or MSG3.

[0010] Thirdly, a terminal is provided, comprising: a processor, a memory, and a program stored in the memory and executable on the processor, wherein the program, when executed by the processor, performs the steps of the method described in the first aspect.

[0011] Fourthly, a readable storage medium is provided, on which a program or instructions are stored, which, when executed by a processor, implement the steps of the method described in the first aspect.

[0012] Fifthly, a computer program product is provided, the program product being stored in a non-transient storage medium, the computer program product being executed by at least one processor to implement the steps of the method described in the first aspect.

[0013] In a sixth aspect, a chip is provided, the chip including a processor and a communication interface coupled to the processor, the processor being used to run programs or instructions to implement the steps of the method described in the first aspect.

[0014] In the embodiments of this application, the UE indicates more information when transmitting MSG3 or MSGA so that the network can obtain more relevant information about the UE, thereby enabling more reasonable scheduling of the UE. Attached Figure Description

[0015] Figure 1 This is a schematic diagram of the wireless communication system architecture provided in an embodiment of this application;

[0016] Figure 2 This is a flowchart illustrating the information reporting method provided in an embodiment of this application;

[0017] Figure 3 This is a schematic diagram of the structure of the information reporting device provided in the embodiments of this application;

[0018] Figure 4 This is a schematic diagram of the terminal structure provided in the embodiments of this application. Detailed Implementation

[0019] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0020] The terms "first," "second," etc., used in the specification and claims of this application are used to distinguish similar objects and are not used to describe a specified order or sequence. It should be understood that such terms can be used interchangeably where appropriate so that embodiments of this application can be implemented in orders other than those illustrated or described herein, and the objects distinguished by "first" and "second" are generally of the same class, not limited in number; for example, a first object can be one or more. Furthermore, in the specification and claims, "and / or" indicates at least one of the connected objects, and the character " / " generally indicates that the preceding and following objects are in an "or" relationship.

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

[0022] Figure 1This diagram illustrates a block diagram of a wireless communication system applicable to embodiments of this application. The wireless communication system includes a terminal 11 and a network-side device 12. In this context, terminal 11 can also be referred to as terminal equipment or user equipment (UE). Terminal 11 can be a mobile phone, tablet computer, laptop computer, personal digital assistant (PDA), handheld computer, netbook, ultra-mobile personal computer (UMPC), mobile internet device (MID), augmented reality (AR) / virtual reality (VR) device, robot, wearable device, vehicle-mounted device (VUE), pedestrian terminal (PUE), smart home (home devices with wireless communication functions, such as refrigerators, televisions, washing machines, or furniture), etc. Wearable devices include: smartwatches, smart bracelets, smart headphones, smart glasses, smart jewelry (smart bracelets, smart chains, smart rings, smart necklaces, smart anklets, smart anklets, etc.), smart wristbands, smart clothing, game consoles, etc. It should be noted that the specific type of terminal 11 is not limited in this embodiment. Network-side device 12 can be a base station or a core network. The base station can be referred to as a node B, evolved node B, access point, base transceiver station (BTS), radio base station, radio transceiver, basic service set (BSS), extended service set (ESS), B node, evolved B node (eNB), home B node, home evolved B node, WLAN access point, WiFi node, transmitting and receiving point (TRP), or any other suitable term in the field, as long as the same technical effect is achieved. The base station is not limited to the specified technical terms. It should be noted that in this application embodiment, only the base station in the NR system is used as an example, but the specific type of base station is not limited.

[0023] To better understand the technical solutions of the embodiments of this application, the following content will be introduced first:

[0024] RedCap UE Introduction

[0025] The R17 version of the protocol supports low-capability terminals. Compared to older / traditional terminals, the capabilities of these Redcap terminals are reduced in the following aspects, as detailed in Table 1:

[0026] Table 1

[0027]

[0028] Random access procedure

[0029] NR supports two types of random access procedures: the 4-step RACH of MSG1 and the 2-step RACH of MSGA. Both types of RA procedures support contention-based RA (CBRA) and contention-free RA (CFRA).

[0030] The UE selects the type of random access based on network configuration:

[0031] (1) When CFRA resources are not configured, the UE selects the 2-step RA type and the 4-step RA type based on the RSRP threshold value;

[0032] (2) When CFRA resources are configured for the 4-step RA type, the UE uses the 4-step RA type to perform random access;

[0033] (3) When CFRA resources are configured for the 2-step RA type, the UE performs random access using the 2-step RA type.

[0034] Competition-based 4-step RACH process

[0035] In the 4-step RACH, the UE first sends MSG1 to the network, containing a preamble. After sending the preamble, the UE listens to the PDCCH within the RAR response window, using fallback DCI format (DCI format 1_0) to receive the random access response (RAR) scheduled by the PDCCH scrambled with RA-RNTI. If the preamble index in the RAR is the same as the preamble index sent by the UE, the RAR is considered successfully received. At this point, the UE can stop listening to the RAR and send MSG3 according to the UL grant instruction carried in the RAR. MSG3 is transmitted on the UL-SCH, using HARQ, scrambling the PDCCH with the TC-RNTI indicated by the RAR, and scheduling retransmissions of MSG3 using fallback DCI format (DCI format 1_0). MSG3 contains a unique identifier for the UE. This identifier will be used for conflict resolution in step four. After receiving MSG3, the network will schedule MSG4 using PDCCH scrambled with TC-RNTI. When the UE successfully decodes the UE Contention Resolution Identity MAC control element contained in MSG4 and finds that it matches the UE Contention Resolution Identity sent by MSG3, the UE will consider the random access to be successful and set its own C-RNTI to TC-RNTI, thus completing the 4-step random access.

[0036] MAC PDU and LCID

[0037] A MAC Protocol Data Unit (PDU) contains one or more MAC subPDUs. Each MAC subPDU contains any one of the following:

[0038] (1) Contains only the MAC subheader;

[0039] (2) MAC subheader and Service Data Unit (SDU);

[0040] (3) MAC subheader and MAC CE;

[0041] (4) MAC header and padding;

[0042] The size of the MAC SDU is not fixed. Each MAC subheader corresponds to a MAC SDU, a MAC CE, or padding.

[0043] The information content of the MAC subheader is shown in Table 2:

[0044] Table 2

[0045]

[0046] The LCID values ​​used for the uplink shared channel are shown in Table 3:

[0047] Table 3

[0048] Codepoint / Index LCID values 0 Common Control Logic Channel (CCCH) (64 bits) 1-32 Logical Channel Identifier 33 Extended logical channel ID field (eLCID field for 2 octets) 34 Extended logical channel ID field (eLCID field of 1octet) 35-44 Reserved bits 45 Shortened Sidelink BSR 46 Sidelink BSR 47 Reserved bits 48 LBT failed (4 octets) 49 LBT failed (1 octets) 50 BFR (one octet Ci) 51 Truncated BFR (one octet Ci) 52 Common Control Logic Channel (CCCH) (64 bits) 53 Recommended bitrate query 54 Multi-entity power margin report (4octets Ci) 55 Configurable scheduling determination 56 Multi-entity power margin report (1octet Ci) 57 Single Entity Power Margin Report 58 C-RNTI 59 Short Truncated BSR 60 Long Truncated BSR 61 Short BSR 62 Long Buffer Report (Long BSR) 63 filling

[0049] During the current RedCap project discussions, the early identification method based on MSG1 and / or MSG3 was determined to explicitly identify RedCap UEs:

[0050] For 4-step random access, it is supported to use MSG1 for early identification, where the identification methods include configuring a dedicated PRACH resource or a dedicated preamble and / or a dedicated uplink initial BWP for the RedCap UE.

[0051] MSG3 early identification is based on a dedicated logical channel ID (LCID).

[0052] The methods and apparatus provided in this application will be described in detail below with reference to the accompanying drawings, through specific embodiments and application scenarios.

[0053] See Figure 2 This application provides an information reporting method, the execution subject of which can be a terminal, and the specific steps include:

[0054] Step 201: The terminal generates target information based on at least one of the following: random access-related information configured in the network, first indication information, terminal-related information, and first configuration information;

[0055] Step 202: The terminal reports the target information via PUSCH or MSG3 of message MSGA.

[0056] In this embodiment, the terminal generates target information based on at least one of the random access related information configured by the network, the first indication information, the terminal's related information, and the first configuration information. The terminal can confirm whether MSG1 or MSGA has been used for early identification based on the random access related information configured by the network, and the terminal determines whether the PUSCH of the terminal's MSG3 or MSG A can use the first LCID when a dedicated PRACH resource or a dedicated preamble and / or a dedicated uplink initial BWP is configured for the RedCap UE based on the first indication information. Then, the terminal determines whether the target information needs to be reported based on the terminal's related information and / or the first configuration information, specifically by reporting through the PUSCH of MSG3 and / or MSGA.

[0057] It is understandable that for the 4-step RA type, the messages involved are MSG1 and MSG3, and for the 2-step RA type, the message involved is MSGA, where MSGA includes two parts: the preamble and the PUSCH part of MSGA.

[0058] In the embodiments of this application, the UE indicates more information when transmitting MSG3 or MSGA so that the network can obtain more relevant information about the UE, thereby enabling more reasonable scheduling of the UE.

[0059] In one possible implementation, the random access-related information configured in the network includes one or more of the following:

[0060] (1) Terminal-specific random access resources or dedicated preamble;

[0061] (2) The dedicated uplink bandwidth portion (BWP) for the terminal;

[0062] (3) Whether the network enables terminals to be identified based on dedicated Physical Random Access Channel (PRACH) resources or dedicated preambles based on MSG1 and / or MSGA.

[0063] (4) Whether the network enables uplink BWP identification terminals based on MSG1 and / or MSGA.

[0064] (5) Does the network support early identification using PUSCH based on MSG3 and / or MSGA?

[0065] (6) Whether the network supports the first logical channel; the first logical channel is used to transmit the PUSCH of the terminal's MSG3 and / or MSGA, and the identifier of the first logical channel is the first logical channel identity (LCID). The first LCID is a newly introduced LCID, and specifically, the value of the first LCID can use the reserved bits in Table 3 above.

[0066] In one possible implementation, the first indication information is used to indicate whether to use the first logical channel to transmit the PUSCH of MSG 3 and / or MSGA when the network is configured with dedicated random access resources or dedicated preambles, and / or the network is configured with dedicated uplink BWPs, and the terminal is identified by MSG1 or MSGA.

[0067] In this way, through the random access information and / or first indication information configured in the network, the terminal can confirm whether it has been identified in advance through MSG1 or MSGA, and whether it supports reporting more relevant information through the PUSCH of MSG 3 and / or MSGA in the future.

[0068] In one possible implementation, if it is determined, based on random access-related information configured in the network, that the MSG1 or MSGA sent by the terminal uses dedicated PRACH resources or contains a dedicated preamble in the MSG1 or MSGA sent by the terminal, and / or the MSG1 or MSGA sent by the terminal uses a dedicated uplink BWP, the target information includes additional information; this corresponds to the case where prior identification has been performed via MSG1 or MSGA.

[0069] If, based on the random access information configured in the network, it is determined that the MSG1 or MSGA sent by the terminal does not use dedicated PRACH resources and the MSG1 or MSGA sent by the terminal does not contain a dedicated preamble, and / or the MSG1 or MSGA sent by the terminal does not use a dedicated uplink BWP, the target information includes initial access information, or the target information includes initial access information and additional information; this situation corresponds to the failure to perform prior identification through MSG1 or MSGA.

[0070] The initial access information mentioned above is used to indicate whether the terminal is a RedCap terminal. The additional information mentioned above is related to the terminal's attributes or service information, measurement results, etc. The purpose of the additional information is to allow the network side to obtain more relevant information about the UE, so as to schedule the UE more reasonably.

[0071] In one possible implementation, the additional information includes one or more of the following:

[0072] (1) The number of receiving antennas of the terminal or the maximum number of antennas supported by the terminal, for example, 1Rx or 2Rx;

[0073] (2) The working mode supported by the terminal, such as full-duplex or half-duplex;

[0074] (3) Whether the terminal needs coverage enhancement, for example, the terminal determines based on the measurement results that the network needs to perform coverage enhancement in subsequent scheduling;

[0075] (4) The modulation order level or maximum modulation coding level supported by the terminal;

[0076] (5) Serving cell quality measured by the terminal;

[0077] (6) The latency requirements of the trigger event for the terminal to enter the connected state;

[0078] (7) The maximum transmission rate supported by the terminal;

[0079] (8) Processing time supported by the terminal;

[0080] (9) Layer 2 cache information or soft cache information supported by the terminal;

[0081] (10) The number of data radio bearers (DRBs) supported by the terminal or the maximum number of DRBs;

[0082] (11) Terminal-supported Radio Resource Control (RRC) processing latency.

[0083] (12) Information from other terminals is not specifically limited.

[0084] In one possible implementation, the terminal's relevant information includes one or more of the following:

[0085] (1) Terminal attributes;

[0086] (2) Measurement results from the terminal;

[0087] (3) The attributes of the service executed when the terminal enters the connected state;

[0088] The terminal's attributes include one or more of the following:

[0089] (1.1) The number of receiving antennas of the terminal or the maximum number of receiving antennas supported by the terminal;

[0090] (1.2) The working modes supported by the terminal;

[0091] (1.3) Does the terminal require coverage enhancement?

[0092] (1.4) The modulation order level or maximum modulation coding level supported by the terminal;

[0093] (1.5) The maximum transmission rate supported by the terminal;

[0094] (1.6) Processing time supported by the terminal;

[0095] (1.7) Layer 2 cache information or soft cache information supported by the terminal;

[0096] (1.8) The number of DRBs supported by the terminal or the maximum number of DRBs;

[0097] (1.9) RRC processing latency supported by the terminal;

[0098] (1.10) Other terminal attributes are not specifically limited.

[0099] The measurement results from the terminal include:

[0100] (2.1) Serving cell quality measured by the terminal;

[0101] (2.2) Measurement results from other terminals are not specifically limited.

[0102] The attributes of the service executed when the terminal enters the connected state include:

[0103] (3.1) The latency requirements of the triggering event for the terminal to enter the connected state.

[0104] (3.2) The attributes of services executed by other terminals in the connected state are not specifically limited.

[0105] In one possible implementation, the first configuration information includes one or more of the following:

[0106] (1) The number of receiving antennas supported by the terminal or the maximum number of receiving antennas supported by the terminal; for example, the first configuration information specifically means that when the maximum number of receiving antennas supported by the terminal is a first value, a report is made; or it is an instruction for the terminal to report the maximum number of receiving antennas supported by the terminal; the first value includes 1 and 2; the meaning of the number of receiving antennas supported by the terminal is: configure 1Rx terminal to report; or 2Rx terminal to report; or configure the terminal to report the number of supporting receiving antennas;

[0107] (2) The working mode supported by the terminal; for example, the first configuration information specifically means that when the working mode supported by the terminal is a first value, it is reported; the first value includes half duplex and full duplex; or it is an instruction for the terminal to report the working mode supported by the terminal.

[0108] (3) Whether the terminal needs coverage enhancement, for example, the first configuration information specifically states that when the terminal needs coverage enhancement, it should report it;

[0109] (4) The modulation order level or maximum modulation coding level supported by the terminal; for example, the first configuration information specifically means that when the maximum modulation order supported by the terminal is a first value, it is reported; or it is an instruction for the terminal to report the maximum modulation order supported by the terminal; the first value includes 64QAM and 256QAM;

[0110] (5) The serving cell quality measured by the terminal or the serving cell quality threshold measured by the terminal; for example, if the first configuration information includes a threshold, then the UE-related measurement results are reported when they are less than / greater than / less than or equal to / greater than or equal to the threshold; or to instruct the terminal to report the serving cell quality measured by the terminal.

[0111] (6) The latency requirements of the triggering event for the terminal to enter the connection state; for example, the first configuration information indicates that the terminal should report when the triggering event for establishing the connection is a first value; or it indicates that the terminal should report the latency requirements of the triggering time for the terminal to enter the connection state; the first value includes voice and emenrgency.

[0112] (7) The maximum transmission rate supported by the terminal or the threshold of the maximum transmission rate supported by the terminal; for example, the first configuration information includes a threshold, and when the maximum transmission rate supported by the terminal is less than / greater than / less than or equal to / greater than or equal to the threshold, a report is made; or the terminal is instructed to report the level of the maximum transmission rate supported by the terminal.

[0113] (8) The processing time supported by the terminal or the maximum processing time threshold supported by the terminal reported by the terminal.

[0114] (9) Terminal-supported Layer 2 cache information or soft cache information reported by the terminal;

[0115] (10) The number of DRBs supported by the terminal or the maximum number of DRBs reported by the terminal;

[0116] (11) The RRC processing latency reported by the terminal.

[0117] In this way, the terminal can determine the content of the additional information in the target information to be reported based on the terminal's relevant information and / or the first configuration information. For example, if the first configuration information is the number of antennas, it instructs the 1Rx terminal to report the number of antennas. When the terminal's own attribute is 1Rx, it will generate additional information and report it; the 2Rx terminal will not generate additional information.

[0118] In one possible implementation, the first configuration information is pre-configured by network configuration and / or protocol; the first indication information is pre-configured by network configuration and / or protocol.

[0119] Specifically, when the serving cell uses the MSG1-based solution (i.e., MSG1 early identification), the protocol or network specifies, through configuration, whether the LCID of MSG3 should use the newly defined LCID or the existing LCID. The same applies to MSGA early identification, so it will not be elaborated further.

[0120] In one possible implementation, the method of carrying the first target information includes one or more of the following:

[0121] (1) Use the first LCID to indicate target information, wherein the first LCID is used to identify the first logical channel, and the first logical channel is used to transmit the PUSCH of the terminal's MSG3 and / or MSGA;

[0122] Specifically, the MAC PDU format of the PUSCH of MSG3 and / or MSGA at the MAC layer is: MAC subheader (including the newly introduced LCID) + MAD SDU (including legacy RRC message), that is, the newly introduced LCID corresponds to the legacy RRC message, and the legacy RRC message refers to the RRC message that already exists in R15 and R16.

[0123] In this embodiment, the number of newly introduced LCIDs is N, where N is a positive integer greater than or equal to 1; the legacy 48-bit RRC message includes an RRC establishment request message, an RRC recovery request message, an RRC reconstruction request message, and a system information request message; the legacy 64-bit RRC message includes an RRC recovery request message. Specifically, there are currently two types of RRC messages, one 48-bit and one 64-bit, therefore at least two new LCIDs need to be introduced, one corresponding to the 48-bit RRC message and the other corresponding to the 64-bit RRC message.

[0124] In this embodiment of the application, a newly introduced LCID is used to indicate the content of the first target information. When the network receives the newly introduced LCID, it can determine the content of the corresponding first target information.

[0125] (2) Use the first MAC CE to carry target information; wherein the MAC subheader of the first MAC CE contains the first LCID;

[0126] Specifically, the MAC PDU format of the PUSCH of MSG3 and / or MSGA at the MAC layer is: MAC subheader (including a new LCID) + a new MAC CE + MAC subheader (including legacy LCID) + MAC SDU (including legacy RRC message), that is, the newly introduced LCID corresponds to a new MAC CE, which carries the first target information.

[0127] In this embodiment of the application, a new MAC CE is used to carry the information content of the first target information, and correspondingly, a new LCID is used to identify the new MAC CE.

[0128] (3) Use the first RRC message to carry target information; wherein the MAC subheader corresponding to the MAC SDU containing the first RRC message contains the first LCID.

[0129] Specifically, the MAC PDU format of the PUSCH of MSG3 and / or MSGA at the MAC layer is: MAC subheader (including legacy LCID) + MAC SDU (including a new 64-bit RRC message (RRC establishment request message, RRC recovery request message, RRC reconstruction request message, system information request message), applicable to the case of non-full I-RNTI (i.e., the case of 48-bit legacy RRC message)). The legacy LCID is the LCID corresponding to the current 64-bit RRC message. The new 64-bit RRC message is the legacy 48-bit RRC message with a new IE added to indicate the first target information.

[0130] In this embodiment of the application, a 64-bit legacy LCID of the RRC message is used. Thus, the RRC message identified by the legacy LCID has a message size of 64 bits. Among these 64 bits, 48 ​​bits are existing 48-bit legacy RRC messages. Therefore, there are 16 bits of message size used to indicate the first target information. That is to say, the above-mentioned new 64-bit RRC message is composed of the 48-bit legacy RRC message and the 16-bit first target information.

[0131] Alternatively, specifically, the MAC PDU format of the PUSCH of MSG3 and / or MSGA at the MAC layer is: MAC subheader (including the new LCID) + MAC SDU (including the new RRC message); the new RRC message is larger than the legacy RRC message, that is, relative to the legacy RRC message, the new RRC message should add a new IE to indicate additional information;

[0132] In this embodiment of the application, the introduced LCID indicates, for example, a new RRC message of size 80 bits. This new RRC message of size 80 bits includes a legacy RRC message of size 64 bits and a first target information of size 16 bits. That is, the new RRC message is composed of the legacy RRC message of size 64 bits and the first target information of size 16 bits.

[0133] The solution of this application is described below with reference to specific embodiments:

[0134] Embodiment 1 of the present invention: RedCap UE is identified by the network through the MSG-3 early identification method.

[0135] Step 1: If the UE is a RedCap UE and the network has not configured a preamble dedicated to RedCap UEs, or the network has not configured PRACH resources dedicated to RedCap UEs, or the UE has selected PRACH resources for legacy UEs and the UE's MAC entity has selected the RA preamble for legacy UEs.

[0136] Step 2: The RedCap UE sends MSG 3, in which the MAC subheader of MSG3 uses the newly introduced logical channel ID. The newly introduced logical channel ID is an unused value in the current uplink LCID and is used to report that the UE is a RedCap UE type.

[0137] The methods for carrying the reported messages include:

[0138] (1) Two newly introduced LCID+legacy RRC messages, where the newly introduced LCID corresponds to the legacy RRC message. For example, when introducing the UL-CCCHX logical channel, it still carries a legacy 48-bit RRC establishment request message, a 48-bit RRC recovery request message, or a 64-bit RRC establishment request message.

[0139] (2) A new LCID + a new MAC CE + legacy RRC message;

[0140] That is, the newly introduced LCID corresponds to a new MAC CE, which carries information indicating that the UE is a RedCap UE.

[0141] (3) Legacy LCID + new 64-bit RRC messages (setup-request and resume-request), applicable to non-full I-RNTI cases. The new RRC messages can add new IEs to indicate that the UE is a RedCap UE.

[0142] Embodiment 2 of the present invention: RedCap UE based on MSG1 early identification method enables the network to explicitly identify RedCap UE.

[0143] Step 1: If the UE is a RedCap UE, and the network has configured a preamble specific to RedCap UEs, and the MAC entity has selected a RA preamble specific to RedCap UEs, or the network has configured PRACH resources specific to RedCap UEs, and the UE has selected PRACH resources specific to RedCap UEs.

[0144] Step 2: The RedCap UE sends MSG 3 to determine whether to report additional information based on the first criterion (i.e., the first configuration information mentioned above);

[0145] Additional information includes at least one of the following:

[0146] (1) The number of receiving antennas, including indicating that the RedCap UE is a 1Rx RedCap UE; or that the RedCap UE is a 2Rx RedCap UE.

[0147] (2) The working mode supported by the terminal, including indicating that the RedCap UE is a full-duplex FD RedCap UE; or the RedCap UE is a half-duplex RedCap UE.

[0148] (3) Whether the terminal needs coverage enhancement, including whether the RedCap UE needs coverage enhancement.

[0149] (4) The modulation order or maximum modulation coding level supported by the terminal, including an indication that the RedCap UE supports a maximum of 64QAM in FR1 or a maximum of 256QAM in FR1.

[0150] (5) Serving cell quality measured by the terminal;

[0151] (6) The latency requirements of the trigger event for the terminal to enter the connected state;

[0152] (7) The maximum transmission rate supported by the terminal;

[0153] (8) Processing time supported by the terminal;

[0154] (9) Layer 2 cache information or soft cache information supported by the terminal;

[0155] (10) The number of data radio bearers (DRBs) supported by the terminal or the maximum number of DRBs;

[0156] (11) Terminal-supported Radio Resource Control (RRC) processing latency.

[0157] (12) Information from other terminals is not specifically limited.

[0158] The first principle includes:

[0159] (1) The number of receiving antennas: if the number of Rx antennas of the RedCap UE is the first value, then it uses the original logical channel ID; if the number of Rx antennas of the RedCap UE is the second value, then it uses the newly introduced logical channel ID; the number of Rx antennas is a positive integer greater than or equal to 1.

[0160] (2) The working mode supported by the terminal. For example, if the working mode supported by the RedCap UE is the first value, it uses the original logical channel ID. If the working mode supported by the RedCap UE is the second value, it uses the newly introduced logical channel ID. The working mode includes half-duplex, full-duplex FD, and others.

[0161] (3) Whether the terminal needs coverage enhancement, for example, if the RedCap UE wants the network to use the coverage enhancement method for scheduling later, then the new logical channel ID is used; otherwise, the original logical channel ID is used. The criteria for the RedCap UE to determine whether coverage is needed in the subsequent scheduling process can be configured by the network and / or predefined and / or implemented by the UE.

[0162] (4) The modulation order level or maximum modulation coding level supported by the terminal. For example, if the maximum modulation order supported by the RedCap UE in FR1 is the first value, it uses the original logical channel ID. If the maximum supported modulation order supported by the RedCap UE in FR1 is the second value, it uses the new logical channel ID. The maximum modulation order supported by the RedCap UE in FR1 includes 64QAM, 256QAM, and others.

[0163] (5) The serving cell quality measured by the terminal. For example, if the quality of the serving cell detected by the UE is higher than a threshold, the UE uses the newly introduced logical channel ID; otherwise, it uses the original logical channel ID. The threshold can be configured by the network, predefined, or implemented by the UE.

[0164] (6) The latency requirements of the triggering event for the terminal to enter the connected state. For example, if the UE receives a paging and the reason carried in the paging is an emergency service or voice service, which requires the latency to be as low as possible, then the UE uses the newly introduced logical channel ID; otherwise, it uses the original logical channel ID.

[0165] (7) The maximum transmission rate supported by the terminal. If the current maximum transmission rate supported by the UE is higher than the threshold, the new logical channel ID shall be used; otherwise, the original logical channel ID shall be used.

[0166] (8) The minimum required transmission rate for the current UE;

[0167] (9) Network configuration, for example, the network instructs the UE to report additional information through an indication message. If the UE receives the indication message, the newly introduced logical channel ID is used. If the UE does not receive the indication message, the original logical channel ID is used. The additional information includes: the number of Rx, the supported operating mode, the channel quality, the modulation order, whether coverage enhancement is required, the cell quality, the delay requirement, and the maximum / minimum transmission rate.

[0168] (10) Others;

[0169] Additional information can be carried in any of the following ways:

[0170] (1) Two newly introduced LCID+legacy RRC messages, where the additional information indicates whether the newly introduced LCID is used;

[0171] (2) A new LCID + a new MAC CE + legacy RRC message, that is, the newly introduced LCID corresponds to a new MAC CE, and the new MAC CE carries an auxiliary message;

[0172] (3) legacy LCID + new 64-bit RRC message (setup-request and resume-request), applicable to non-full I-RNTI cases. The legacy LCID is the LCID corresponding to the current 64-bit RRC message. The new 64-bit RRC message is the legacy 48-bit RRC message with a new IE added to indicate auxiliary messages.

[0173] (4) New LCID + new RRC message; the new RRC message is larger than the legacy RRC message, that is, relative to the legacy RRC message, the new RRC message should add a new IE to indicate additional information;

[0174] Embodiment 3 of the present invention: Normal UE / Non-RedCap UE uses the newly introduced logical channel ID

[0175] 1. If the serving cell uses an MSG1-based solution

[0176] 2. Normal UEs / Non-RedCaps in RRC_IDLE or RRC_INACTIVE states report additional information according to the third criterion when sending Msg3.

[0177] Additional information includes at least one of the following:

[0178] (1) The number of receiving antennas, including indicating that the Normal / Non-RedCap UE is a 2Rx RedCap UE; or that the RedCap UE is a 4Rx RedCap UE.

[0179] (2) The working mode supported by the terminal, such as full-duplex or half-duplex;

[0180] (3) Whether the terminal needs coverage enhancement, including the SINR or RSRP size of the Normal / Non-RedCap UE or others.

[0181] (4) The modulation order level or maximum modulation coding level supported by the terminal;

[0182] (5) Serving cell quality measured by the terminal;

[0183] (6) The latency requirements of the trigger event for the terminal to enter the connected state;

[0184] (7) The maximum transmission rate supported by the terminal;

[0185] (8) Processing time supported by the terminal;

[0186] (9) Layer 2 cache information or soft cache information supported by the terminal;

[0187] (10) The number of data radio bearers (DRBs) supported by the terminal or the maximum number of DRBs;

[0188] (11) Terminal-supported Radio Resource Control (RRC) processing latency.

[0189] (12) Information from other terminals is not specifically limited.

[0190] The second criterion for determining the value of the logical channel ID used in the MAC subheader of MSG3 (i.e., the first configuration information mentioned above) includes:

[0191] (1) The number of receiving antennas reported by the terminal;

[0192] (2) The working mode supported by the terminal reported by the terminal;

[0193] (3) Whether the terminal reported by the terminal needs coverage enhancement. For example, if the UE receives the first network configuration information, which includes a threshold, then the UE reports the relevant measurement result when it is less than the threshold.

[0194] (4) The modulation order level or maximum modulation coding level supported by the terminal reported by the terminal;

[0195] (5) The serving cell quality reported by the terminal as measured by the terminal. For example, if the quality of the serving cell detected by the UE is higher than a threshold value, the UE uses the newly introduced logical channel ID; otherwise, it uses the original logical channel ID. The threshold value can be configured by the network, predefined, or implemented by the UE.

[0196] (6) The latency requirements for the triggering event of the terminal entering the connected state reported by the terminal;

[0197] (7) The maximum transmission rate supported by the terminal reported by the terminal;

[0198] (8) The processing time supported by the terminal reported by the terminal;

[0199] (9) Terminal-supported Layer 2 cache information or soft cache information reported by the terminal;

[0200] (10) The number of DRBs supported by the terminal or the maximum number of DRBs reported by the terminal;

[0201] (11) The RRC processing latency reported by the terminal.

[0202] (12) Random selection / UE-based implementation;

[0203] (13) Network configuration;

[0204] (14) Others;

[0205] See Figure 3 This application provides an information reporting device 300, comprising:

[0206] The generation module 301 is used for the terminal to generate target information based on at least one of the random access related information configured by the network, the first indication information, the relevant information of the terminal, and the first configuration information;

[0207] The reporting module 302 is used by the terminal to report the target information through the PUSCH or MSG3 of the MSGA.

[0208] In one possible implementation, the random access-related information of the network configuration includes one or more of the following:

[0209] The terminal-specific random access resources or dedicated preamble;

[0210] The terminal-specific uplink BWP;

[0211] Whether the network enables the identification of the terminal based on the dedicated PRACH resources or dedicated preamble of MSG1 and / or MSGA;

[0212] Whether the network enables the identification of the terminal based on the MSG1 and / or MSGA-specific uplink BWP;

[0213] Does the network support early identification using PUSCH based on MSG3 and / or MSGA?

[0214] Does the network support a first logical channel? The first logical channel is used to transmit the PUSCH of the terminal's MSG3 and / or MSGA, and the identifier of the first logical channel is a first LCID.

[0215] In one possible implementation, the first indication information is used to indicate whether to use the first logical channel to transmit the PUSCH of MSG 3 and / or MSGA when the network is configured with dedicated random access resources or dedicated preambles, and / or the network is configured with dedicated uplink BWPs, and the terminal is identified by MSG1 or MSGA.

[0216] In one possible implementation, if it is determined, based on random access-related information configured in the network, that the MSG1 or MSGA sent by the terminal uses dedicated PRACH resources or contains a dedicated preamble in the MSG1 or MSGA sent by the terminal, and / or the MSG1 or MSGA sent by the terminal uses a dedicated uplink BWP, the target information includes additional information.

[0217] If, based on the random access information configured in the network, it is determined that the MSG1 or MSGA sent by the terminal does not use dedicated PRACH resources and the MSG1 or MSGA sent by the terminal does not contain a dedicated preamble, and / or the MSG1 or MSGA sent by the terminal does not use a dedicated uplink BWP, the target information includes initial access information, or the target information includes initial access information and additional information.

[0218] The initial access information is used to indicate whether the terminal is a RedCap terminal, and the additional information is associated with the attributes of the terminal.

[0219] In one possible implementation, the additional information includes one or more of the following:

[0220] The number of receiving antennas of the terminal or the maximum number of receiving antennas supported by the terminal;

[0221] The terminal supports the following working modes:

[0222] Does the terminal require enhanced coverage?

[0223] The terminal supports modulation order levels or maximum modulation coding levels;

[0224] The terminal measures the quality of the serving cell.

[0225] The latency requirements of the triggering event for the terminal to enter the connected state;

[0226] The maximum transmission rate supported by the terminal;

[0227] The terminal supports processing time;

[0228] The terminal supports Layer 2 cache information or soft cache information;

[0229] The terminal supports the number of DRBs or the maximum number of DRBs.

[0230] The terminal supports RRC processing latency.

[0231] In one possible implementation, the relevant information of the terminal includes one or more of the following:

[0232] The attributes of the terminal;

[0233] The measurement results of the terminal;

[0234] The attributes of the service executed when the terminal enters the connected state;

[0235] The terminal's attributes include one or more of the following:

[0236] The number of receiving antennas;

[0237] The terminal supports the following working modes:

[0238] Does the terminal require enhanced coverage?

[0239] The terminal supports modulation order levels or maximum modulation coding levels;

[0240] The maximum transmission rate supported by the terminal;

[0241] The terminal supports processing time;

[0242] The terminal supports Layer 2 cache information or soft cache information;

[0243] The terminal supports the number of DRBs or the maximum number of DRBs.

[0244] The terminal supports RRC processing latency;

[0245] The measurement results of the terminal include:

[0246] The terminal measures the quality of the serving cell.

[0247] The attributes of the service executed by the terminal in the connected state include:

[0248] The latency requirements for the triggering event that causes the terminal to enter the connected state.

[0249] In one possible implementation, the first configuration information includes one or more of the following: the number of receiving antennas supported by the terminal or the maximum number of receiving antennas supported by the terminal;

[0250] The terminal supports the following working modes:

[0251] Does the terminal require enhanced coverage?

[0252] The terminal supports modulation order levels or maximum modulation coding levels;

[0253] The serving cell quality measured by the terminal or the serving cell quality threshold measured by the terminal;

[0254] The latency requirements for the triggering event of the terminal entering the connected state;

[0255] The maximum transmission rate supported by the terminal or the maximum transmission rate threshold supported by the terminal;

[0256] The processing time supported by the terminal or the maximum processing time threshold supported by the terminal;

[0257] The terminal supports Layer 2 cache information or soft cache information;

[0258] The terminal supports the number of DRBs or the maximum number of DRBs.

[0259] The terminal supports RRC processing latency.

[0260] In one possible implementation, the first configuration information is pre-configured by network configuration and / or protocol; the first indication information is pre-configured by network configuration and / or protocol.

[0261] In one possible implementation, the method of carrying the target information includes one or more of the following:

[0262] The target information is indicated by a first LCID, wherein the first LCID is used to identify a first logical channel, and the first logical channel is used to transmit the PUSCH of the terminal's MSG3 and / or MSGA;

[0263] The target information is carried by a first MAC CE; wherein the MAC subheader of the first MAC CE contains a first LCID;

[0264] The target information is carried using a first RRC message; wherein the MAC subheader corresponding to the MAC SDU containing the first RRC message contains a first LCID.

[0265] In the embodiments of this application, the UE indicates more information when transmitting MSG3 or MSGA so that the network can obtain more relevant information about the UE, thereby enabling more reasonable scheduling of the UE.

[0266] The PUCCH resource overlap processing device provided in this application embodiment can achieve Figure 2 The various processes implemented in the method embodiments shown achieve the same technical effects, and will not be described again here to avoid repetition.

[0267] Figure 4 A schematic diagram of the hardware structure of a terminal to implement an embodiment of this application.

[0268] The terminal 400 includes, but is not limited to, components such as: radio frequency unit 401, network module 402, audio output unit 403, input unit 404, sensor 405, display unit 406, user input unit 407, interface unit 408, memory 409, and processor 410.

[0269] Those skilled in the art will understand that the terminal 400 may also include a power supply (such as a battery) for supplying power to various components. The power supply may be logically connected to the processor 410 through a power management system, thereby enabling functions such as managing charging, discharging, and power consumption through the power management system. Figure 4 The terminal structure shown does not constitute a limitation on the terminal. The terminal may include more or fewer components than shown, or combine certain components, or have different component arrangements, which will not be elaborated here.

[0270] It should be understood that, in this embodiment, the input unit 404 may include a graphics processing unit (GPU) 4041 and a microphone 4042. The GPU 4041 processes image data of still images or videos obtained by an image capture device (such as a camera) in video capture mode or image capture mode. The display unit 406 may include a display panel 4061, which may be configured in the form of a liquid crystal display, an organic light-emitting diode, or the like. The user input unit 407 includes a touch panel 4061 and other input devices 4072. The touch panel 4061 is also called a touch screen. The touch panel 4061 may include a touch detection device and a touch controller. Other input devices 4072 may include, but are not limited to, a physical keyboard, function keys (such as volume control buttons, power buttons, etc.), a trackball, a mouse, and a joystick, which will not be described in detail here.

[0271] In this embodiment, the radio frequency unit 401 receives downlink data from the network-side device and processes it for the processor 410; additionally, it sends uplink data to the network-side device. Typically, the radio frequency unit 601 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low-noise amplifier, a duplexer, etc.

[0272] The memory 409 can be used to store software programs or instructions and various data. The memory 409 may primarily include a program or instruction storage area and a data storage area. The program or instruction storage area may store the operating system, application programs or instructions required for at least one function (such as sound playback, image playback, etc.). Furthermore, the memory 409 may include high-speed random access memory and non-volatile memory, which may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. For example, at least one disk storage device, flash memory device, or other non-volatile solid-state storage device.

[0273] Processor 410 may include one or more processing units; optionally, processor 410 may integrate an application processor and a modem processor, wherein the application processor mainly handles the operating system, user interface, and applications or instructions, and the modem processor mainly handles wireless communication, such as a baseband processor. It is understood that the aforementioned modem processor may also not be integrated into processor 410.

[0274] The processor 410 is configured to generate target information based on at least one of the following: random access-related information configured in the network, first indication information, relevant information of the terminal, and first configuration information;

[0275] Processor 410 is used by the terminal to report the target information via MSGA PUSCH or MSG3.

[0276] In one possible implementation, the random access-related information of the network configuration includes one or more of the following:

[0277] The terminal-specific random access resources or dedicated preamble;

[0278] The terminal-specific uplink BWP;

[0279] Whether the network enables the identification of the terminal based on the dedicated PRACH resources or dedicated preamble of MSG1 and / or MSGA;

[0280] Whether the network enables the identification of the terminal based on the MSG1 and / or MSGA-specific uplink BWP;

[0281] Does the network support early identification using PUSCH based on MSG3 and / or MSGA?

[0282] Does the network support a first logical channel? The first logical channel is used to transmit the PUSCH of the terminal's MSG3 and / or MSGA, and the identifier of the first logical channel is a first LCID.

[0283] In one possible implementation, the first indication information is used to indicate whether to use the first logical channel to transmit the PUSCH of MSG 3 and / or MSGA when the network is configured with dedicated random access resources or dedicated preambles, and / or the network is configured with dedicated uplink BWPs, and the terminal is identified by MSG1 or MSGA.

[0284] In one possible implementation, if it is determined, based on random access-related information configured in the network, that the MSG1 or MSGA sent by the terminal uses dedicated PRACH resources or contains a dedicated preamble in the MSG1 or MSGA sent by the terminal, and / or the MSG1 or MSGA sent by the terminal uses a dedicated uplink BWP, the target information includes additional information.

[0285] If, based on the random access information configured in the network, it is determined that the MSG1 or MSGA sent by the terminal does not use dedicated PRACH resources and the MSG1 or MSGA sent by the terminal does not contain a dedicated preamble, and / or the MSG1 or MSGA sent by the terminal does not use a dedicated uplink BWP, the target information includes initial access information, or the target information includes initial access information and additional information.

[0286] The initial access information is used to indicate whether the terminal is a RedCap terminal, and the additional information is associated with the attributes of the terminal.

[0287] In one possible implementation, the additional information includes one or more of the following:

[0288] The number of receiving antennas;

[0289] The terminal supports the following working modes:

[0290] Does the terminal require enhanced coverage?

[0291] The terminal supports modulation order levels or maximum modulation coding levels;

[0292] The terminal measures the quality of the serving cell.

[0293] The latency requirements of the triggering event for the terminal to enter the connected state;

[0294] The maximum transmission rate supported by the terminal;

[0295] The terminal supports processing time;

[0296] The terminal supports Layer 2 cache information or soft cache information;

[0297] The terminal supports the number of DRBs or the maximum number of DRBs.

[0298] The terminal supports RRC processing latency.

[0299] In one possible implementation, the relevant information of the terminal includes one or more of the following:

[0300] The attributes of the terminal;

[0301] The measurement results of the terminal;

[0302] The attributes of the service executed when the terminal enters the connected state;

[0303] The terminal's attributes include one or more of the following:

[0304] The number of receiving antennas;

[0305] The terminal supports the following working modes:

[0306] Does the terminal require enhanced coverage?

[0307] The terminal supports modulation order levels or maximum modulation coding levels;

[0308] The maximum transmission rate supported by the terminal;

[0309] The terminal supports processing time;

[0310] The terminal supports Layer 2 cache information or soft cache information;

[0311] The terminal supports the number of DRBs or the maximum number of DRBs.

[0312] The terminal supports RRC processing latency;

[0313] The measurement results of the terminal include:

[0314] The terminal measures the quality of the serving cell.

[0315] The attributes of the service executed by the terminal in the connected state include:

[0316] The latency requirements for the triggering event that causes the terminal to enter the connected state.

[0317] In one possible implementation, the first configuration information includes one or more of the following:

[0318] The number of receiving antennas supported by the terminal or the maximum number of receiving antennas supported by the terminal;

[0319] The terminal supports the following working modes:

[0320] Does the terminal require enhanced coverage?

[0321] The terminal supports modulation order levels or maximum modulation coding levels;

[0322] The serving cell quality measured by the terminal or the serving cell quality threshold measured by the terminal;

[0323] The latency requirements for the triggering event of the terminal entering the connected state;

[0324] The maximum transmission rate supported by the terminal or the maximum transmission rate threshold supported by the terminal;

[0325] The processing time supported by the terminal or the maximum processing time threshold supported by the terminal;

[0326] The terminal supports Layer 2 cache information or soft cache information;

[0327] The terminal supports the number of DRBs or the maximum number of DRBs.

[0328] The terminal supports RRC processing latency.

[0329] In one possible implementation, the first configuration information is pre-configured by network configuration and / or protocol;

[0330] The first indication information is pre-configured by network configuration and / or protocol.

[0331] In one possible implementation, the method of carrying the target information includes one or more of the following:

[0332] The target information is indicated by a first LCID, wherein the first LCID is used to identify a first logical channel, and the first logical channel is used to transmit the PUSCH of the terminal's MSG3 and / or MSGA;

[0333] The target information is carried by a first MAC CE; wherein the MAC subheader of the first MAC CE contains a first LCID;

[0334] The target information is carried using a first RRC message; wherein the MAC subheader corresponding to the MAC SDU containing the first RRC message contains a first LCID.

[0335] This application also provides a program product, which is stored in a non-volatile storage medium and executed by at least one processor to implement the following: Figure 2 The steps of the method described.

[0336] This application embodiment also provides a readable storage medium storing a program or instructions that, when executed by a processor, implement the above-described functionality. Figure 2 The various processes of the method embodiments shown can achieve the same technical effect, and will not be described again here to avoid repetition.

[0337] The processor mentioned above is the processor in the terminal described in the above embodiments. The readable storage medium includes computer-readable storage media, such as computer read-only memory (ROM), random access memory (RAM), magnetic disk, or optical disk.

[0338] This application embodiment also provides a chip, the chip including a processor and a communication interface, the communication interface being coupled to the processor, the processor being used to run network-side device programs or instructions to achieve the above-mentioned... Figure 2 The various processes of the method embodiments shown can achieve the same technical effect, and will not be described again here to avoid repetition.

[0339] It should be understood that the chip mentioned in the embodiments of this application may also be referred to as a system-on-a-chip, system chip, chip system, or system-on-a-chip, etc.

[0340] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element. Furthermore, it should be noted that the scope of the methods and apparatuses in the embodiments of this application is not limited to performing functions in the order shown or discussed, but may also include performing functions substantially simultaneously or in the reverse order, depending on the functions involved. For example, the described methods may be performed in a different order than described, and various steps may be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.

[0341] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) and includes several instructions to cause a terminal (which may be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in the various embodiments of this application.

[0342] The embodiments of this application have been described above with reference to the accompanying drawings. However, this application is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other forms under the guidance of this application without departing from the spirit and scope of the claims, and all of these forms are within the protection scope of this application.

Claims

1. An information reporting method, characterized in that, include: The terminal generates target information based on at least one of the following: random access-related information configured in the network, first indication information, relevant information of the terminal, and first configuration information; The terminal reports the target information through the Physical Uplink Shared Channel (PUSCH) or MSG3 of the Message MSGA. If, based on the random access information configured in the network, it is determined that the MSG1 or MSGA sent by the terminal uses dedicated PRACH resources or contains a dedicated preamble in the MSG1 or MSGA sent by the terminal, and / or the MSG1 or MSGA sent by the terminal uses a dedicated uplink BWP, the target information includes additional information. If, based on the random access-related information configured in the network, it is determined that the MSG1 or MSGA sent by the terminal does not use dedicated PRACH resources and does not contain a dedicated preamble in the MSG1 or MSGA sent by the terminal, and / or, the MSG1 or MSGA sent by the terminal does not use a dedicated uplink BWP, the target information includes initial access information, or the target information includes initial access information and additional information. The initial access information is used to indicate whether the terminal is a low-capability RedCap terminal, and the additional information is used for network scheduling of the terminal. The additional information includes one or more of the following: The number of receiving antennas of the terminal or the maximum number of receiving antennas supported by the terminal; The terminal supports the following working modes: Does the terminal require enhanced coverage? The modulation order level or maximum modulation coding level supported by the terminal; the serving cell quality measured by the terminal; The latency requirements of the trigger event for the terminal to enter the connected state; the maximum transmission rate supported by the terminal; The terminal supports processing time; The terminal supports Layer 2 cache information or soft cache information; the terminal supports the number of Data Radio Bearer (DRB) or the maximum number of DRBs; and the terminal supports Radio Resource Control (RRC) processing latency.

2. The method according to claim 1, characterized in that, The random access-related information configured in the network includes one or more of the following: The terminal-specific random access resources or dedicated preamble; the terminal-specific uplink bandwidth portion (BWP); Whether the network enables the identification of the terminal based on the dedicated physical random access channel PRACH resource of MSG1 and / or MSGA or a dedicated preamble; Whether the network enables the identification of the terminal based on the MSG1 and / or MSGA-specific uplink BWP; Does the network support early identification using PUSCH based on MSG3 and / or MSGA? Does the network support the first logical channel? The first logical channel is used to transmit the PUSCH of the terminal's MSG3 and / or MSGA, and the identifier of the first logical channel is the first logical channel identifier LCID.

3. The method according to claim 2, characterized in that, The first indication information is used to indicate whether to use the first logical channel to transmit the PUSCH of MSG3 and / or MSGA when the network is configured with dedicated random access resources or dedicated preambles, and / or the network is configured with dedicated uplink BWP, and the terminal is identified by MSG1 or MSGA.

4. The method according to claim 1, characterized in that, The relevant information of the terminal includes one or more of the following: The attributes of the terminal; The measurement results of the terminal; The attributes of the service executed when the terminal enters the connected state; The terminal's attributes include one or more of the following: The number of receiving antennas of the terminal or the maximum number of receiving antennas supported by the terminal; The terminal supports the following working modes: Does the terminal require enhanced coverage? The terminal supports modulation order levels or maximum modulation coding levels; The maximum transmission rate supported by the terminal; The terminal supports processing time; The terminal supports Layer 2 cache information or soft cache information; The terminal supports the number of DRBs or the maximum number of DRBs. The terminal supports RRC processing latency; The measurement results of the terminal include: The terminal measures the quality of the serving cell. The attributes of the service executed by the terminal in the connected state include: The latency requirements for the triggering event that causes the terminal to enter the connected state.

5. The method according to claim 1, characterized in that, The first configuration information includes one or more of the following: The number of receiving antennas supported by the terminal or the maximum number of receiving antennas supported by the terminal; The terminal supports the following working modes: Does the terminal require enhanced coverage? The terminal supports modulation order levels or maximum modulation coding levels; The serving cell quality measured by the terminal or the serving cell quality threshold measured by the terminal; The latency requirements for the triggering event of the terminal entering the connected state; The maximum transmission rate supported by the terminal or the maximum transmission rate threshold supported by the terminal; The processing time supported by the terminal or the maximum processing time threshold supported by the terminal; The terminal supports Layer 2 cache information or soft cache information; The terminal supports the number of DRBs or the maximum number of DRBs. The terminal supports RRC processing latency.

6. The method according to claim 1, characterized in that, The first configuration information is pre-configured by network configuration and / or protocol; The first indication information is pre-configured by network configuration and / or protocol.

7. The method according to claim 1, characterized in that, The method of carrying the target information includes one or more of the following: The target information is indicated by a first LCID, wherein the first LCID is used to identify a first logical channel, and the first logical channel is used to transmit the PUSCH of the terminal's MSG3 and / or MSGA; The target information is carried by a first media access control unit (MAC CE); wherein the MAC subheader of the first MAC CE contains a first LCID. The target information is carried using a first RRC message; wherein the MAC subheader corresponding to the Media Access Control Service Data Unit (MAC SDU) containing the first RRC message contains a first LCID.

8. An information reporting device, characterized in that, include: The generation module is used for the terminal to generate target information based on at least one of the following: random access-related information configured in the network, first indication information, relevant information of the terminal, and first configuration information; The reporting module is used by the terminal to report the target information through MSGA PUSCH or MSG3; If, based on the random access information configured in the network, it is determined that the MSG1 or MSGA sent by the terminal uses dedicated PRACH resources or contains a dedicated preamble in the MSG1 or MSGA sent by the terminal, and / or the MSG1 or MSGA sent by the terminal uses a dedicated uplink BWP, the target information includes additional information. If, based on the random access-related information configured in the network, it is determined that the MSG1 or MSGA sent by the terminal does not use dedicated PRACH resources and does not contain a dedicated preamble in the MSG1 or MSGA sent by the terminal, and / or, the MSG1 or MSGA sent by the terminal does not use a dedicated uplink BWP, the target information includes initial access information, or the target information includes initial access information and additional information. The initial access information is used to indicate whether the terminal is a RedCap terminal; the additional information is used for network scheduling of the terminal; the additional information includes one or more of the following: The number of receiving antennas of the terminal or the maximum number of receiving antennas supported by the terminal; The terminal supports the following working modes: Does the terminal require enhanced coverage? The modulation order level or maximum modulation coding level supported by the terminal; the serving cell quality measured by the terminal; The latency requirements of the trigger event for the terminal to enter the connected state; the maximum transmission rate supported by the terminal; The terminal supports processing time; The terminal supports Layer 2 cache information or soft cache information; the terminal supports the number of DRBs or the maximum number of DRBs; The terminal supports RRC processing latency.

9. The apparatus according to claim 8, characterized in that, The random access-related information configured in the network includes one or more of the following: The terminal-specific random access resources or dedicated preamble; the terminal-specific uplink BWP; Whether the network enables the identification of the terminal based on the dedicated PRACH resources or dedicated preamble of MSG1 and / or MSGA; Whether the network enables the identification of the terminal based on the MSG1 and / or MSGA-specific uplink BWP; Does the network support early identification using PUSCH based on MSG3 and / or MSGA? Does the network support a first logical channel? The first logical channel is used to transmit the PUSCH of the terminal's MSG3 and / or MSGA, and the identifier of the first logical channel is the -LCID.

10. The apparatus according to claim 9, characterized in that, The first indication information is used to indicate whether to use the first logical channel to transmit the PUSCH of MSG 3 and / or MSGA when the network is configured with dedicated random access resources or dedicated preambles, and / or the network is configured with dedicated uplink BWP, and the terminal is identified by MSG1 or MSGA.

11. The apparatus according to claim 8, characterized in that, The relevant information of the terminal includes one or more of the following: The attributes of the terminal; The measurement results of the terminal; The attributes of the service executed when the terminal enters the connected state; The terminal's attributes include one or more of the following: The number of receiving antennas of the terminal or the maximum number of receiving antennas supported by the terminal; The terminal supports the following working modes: Does the terminal require enhanced coverage? The modulation order level or maximum modulation coding level supported by the terminal; the maximum transmission rate supported by the terminal; The terminal supports processing time; The terminal supports Layer 2 cache information or soft cache information; The terminal supports the number of DRBs or the maximum number of DRBs. The terminal supports RRC processing latency; The measurement results of the terminal include: The terminal measures the quality of the serving cell. The attributes of the service executed by the terminal in the connected state include: The latency requirements for the triggering event that causes the terminal to enter the connected state.

12. The apparatus according to claim 8, characterized in that, The first configuration information includes one or more of the following: The number of receiving antennas supported by the terminal or the maximum number of receiving antennas supported by the terminal; The terminal supports the following working modes: Does the terminal require enhanced coverage? The terminal supports modulation order levels or maximum modulation coding levels; The serving cell quality measured by the terminal or the serving cell quality threshold measured by the terminal; The latency requirements for the triggering event of the terminal entering the connected state; The maximum transmission rate supported by the terminal or the maximum transmission rate threshold supported by the terminal; The processing time supported by the terminal or the maximum processing time threshold supported by the terminal; The terminal supports Layer 2 cache information or soft cache information; The terminal supports the number of DRBs or the maximum number of DRBs. The terminal supports RRC processing latency.

13. The apparatus according to claim 8, characterized in that, The first configuration information is pre-configured by network configuration and / or protocol; The first indication information is pre-configured by network configuration and / or protocol.

14. The apparatus according to claim 8, characterized in that, The method of carrying the target information includes one or more of the following: The target information is indicated by a first LCID, wherein the first LCID is used to identify a first logical channel, and the first logical channel is used to transmit the PUSCH of the terminal's MSG3 and / or MSGA; The target information is carried by a first MAC CE; wherein the MAC subheader of the first MAC CE contains a first LCID; The target information is carried using a first RRC message; wherein the MAC subheader corresponding to the MAC SDU containing the first RRC message contains a first LCID.

15. A terminal, characterized in that, include: A processor, a memory, and a program stored in the memory and executable on the processor, wherein the program, when executed by the processor, implements the steps of the method as described in any one of claims 1 to 7.

16. A readable storage medium, characterized in that, The readable storage medium stores a program or instructions that, when executed by a processor, implement the steps of the method as described in any one of claims 1 to 7.

Images