WO2023066129A1

WO2023066129A1 - Information reporting method, device, and readable storage medium

Info

Publication number: WO2023066129A1
Application number: PCT/CN2022/125124
Authority: WO
Inventors: 王洋洋; 鲍炜; 陈力; 莫毅韬; 郑倩
Original assignee: 维沃移动通信有限公司
Priority date: 2021-10-20
Filing date: 2022-10-13
Publication date: 2023-04-27
Also published as: CN115996479A

Abstract

The present application relates to the technical field of communications, and discloses an information reporting method, a device, and a readable storage medium. The method comprises: a terminal generates target information according to at least one of random access related information of network configuration, first indication information, related information of the terminal, and first configuration information; and the terminal reports the target information by means of a physical uplink shared channel (PUSCH) of a message MSGA or MSG3.

Description

Information reporting method, device and readable storage medium

Cross References to Related Applications

This application claims priority to Chinese Patent Application No. 202111221988.0 filed in China on October 20, 2021, the entire contents of which are hereby incorporated by reference.

technical field

The present application belongs to the technical field of communication, and in particular relates to an information reporting method, device and readable storage medium.

Background technique

In the prior art, user equipment (User Equipment, UE, ie terminal) can use message 3 (MSG3) or message A (MASA) to carry out early identification of low capability (Reduced capability, RedCap) UE, and the current protocol does not define the use of MSG3 Or what information MASA carries.

Contents of the invention

The purpose of the embodiments of the present application is to provide an information reporting method, device and readable storage medium to solve the problem that the information carried by MSG3 or MASA is not defined in the current protocol.

In the first aspect, a method for reporting information is provided, including:

The terminal generates target information according to at least one of random access related information configured by the network, first indication information, related 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.

In a second aspect, an information reporting device is provided, including:

A generating module, configured for the terminal to generate target information according to at least one of random access related information configured by the network, first indication information, related information of the terminal, and first configuration information;

The reporting module is used for the terminal to report the target information through PUSCH or MSG3 of MSGA.

In a third aspect, a terminal is provided, including: a processor, a memory, and a program stored in the memory and operable on the processor, and when the program is executed by the processor, the terminal described in the first aspect can be implemented. steps of the method described above.

In a fourth aspect, a readable storage medium is provided, where a program or an instruction is stored on the readable storage medium, and when the program or instruction is executed by a processor, the steps of the method as described in the first aspect are implemented.

In a fifth aspect, a computer program product is provided, the program product is stored in a non-transitory storage medium, and the computer program product is executed by at least one processor to implement the steps of the method described in the first aspect .

A sixth aspect provides a chip, the chip includes a processor and a communication interface, the communication interface is coupled to the processor, the processor is used to run programs or instructions, and implement the method as described in the first aspect A step of.

In a seventh aspect, the embodiment of the present application provides a communication device configured to execute the method as described in the first aspect.

In the embodiment of the present application, the UE indicates more information when transmitting MSG3 or MSGA, so that the network can obtain more relevant information of the UE, so that the UE can be scheduled more reasonably.

Description of drawings

FIG. 1 is a schematic diagram of a wireless communication system architecture provided by an embodiment of the present application;

Fig. 2 is a schematic flow chart of the information reporting method provided by the embodiment of the present application;

FIG. 3 is a schematic structural diagram of an information reporting device provided by an embodiment of the present application;

FIG. 4 is a schematic structural diagram of a terminal provided by an embodiment of the present application.

Detailed ways

The following will clearly and completely describe the technical solutions in the embodiments of the present application with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, not all of them. Based on the embodiments in this application, all other embodiments obtained by persons of ordinary skill in the art without creative efforts fall within the protection scope of this application.

The terms "first", "second" and the like in the specification and claims of the present application are used to distinguish similar objects, and are not used to describe a specified order or sequence. It is to be understood that the terms so used are interchangeable under appropriate circumstances such that the embodiments of the application are capable of operation in sequences other than those illustrated or described herein and that "first" and "second" distinguish objects. It is usually one category, and the number of objects is not limited. For example, there may be one or more first objects. In addition, "and/or" in the description and claims means at least one of the connected objects, and the character "/" generally means that the related objects are an "or" relationship.

It is worth pointing out that the technology described in the embodiment of this application is not limited to the Long Term Evolution (Long Term Evolution, LTE)/LTE-Advanced (LTE-Advanced, LTE-A) system, and can also be used in other wireless communication systems, such as code 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 (Single-carrier Frequency-Division Multiple Access, SC-FDMA) and other systems. The terms "system" and "network" in the embodiments of the present application are often used interchangeably, and the described technologies can be used for the above-mentioned systems and radio technologies as well as other systems and radio technologies. However, the following description describes the New Radio (NR) system for example purposes, and uses NR terminology in most of the following descriptions, and these technologies can also be applied to applications other than NR system applications, such as the 6th generation (6 ^th Generation, 6G) communication system.

Fig. 1 shows a block diagram of a wireless communication system to which the embodiment of the present application is applicable. The wireless communication system includes a terminal 11 and a network side device 12 . Wherein, the terminal 11 can also be called a terminal device or a user terminal (User Equipment, UE), and the terminal 11 can be a mobile phone, a tablet computer (Tablet Personal Computer), a laptop computer (Laptop Computer) or a notebook computer, a personal digital Assistant (Personal Digital Assistant, PDA), handheld computer, netbook, ultra-mobile personal computer (ultra-mobile personal computer, UMPC), mobile internet device (Mobile Internet Device, MID), augmented reality (augmented reality, AR)/virtual reality (virtual reality, VR) equipment, robot, wearable device (Wearable Device), vehicle equipment (Vehicle User Equipment, VUE), pedestrian terminal (Pedestrian User Equipment, PUE), smart home (home equipment with wireless communication function, Such as refrigerators, TVs, washing machines or furniture, etc.), wearable devices include: smart watches, smart bracelets, smart headphones, smart glasses, smart jewelry (smart bracelets, smart bracelets, smart rings, smart necklaces, smart anklets, smart anklets, etc.), smart wristbands, smart clothing, game consoles, etc. It should be noted that the embodiment of the present application does not limit the specific type of terminal 11. The network side device 12 may be a base station or a core network, where a base station may be referred to as a Node B, an evolved Node B, an access point, a Base Transceiver Station (Base TransceiverStation, BTS), a radio base station, a radio transceiver, a basic service set (BasicServiceSet, BSS), extended service set (ExtendedServiceSet, ESS), B node, evolved type B node (eNB), home node B, home evolved type B node, wireless local area network (Wireless Local Area Network, WLAN) access point, Wireless Fidelity (Wireless Fidelity, WiFi) node, Transmitting Receiving Point (Transmitting Receiving Point, TRP) or some 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 vocabulary, and requires It should be noted that, in the embodiment of the present application, only the base station in the NR system is taken as an example, but the specific type of the base station is not limited.

In order to better understand the technical solutions of the embodiments of the present application, the following contents are firstly introduced:

Introduction to RedCap UE

The R17 (Release 17) protocol supports low-capability terminals. Compared with old/traditional terminals, the capabilities of this type of redcap terminal are mainly reduced in the following aspects, as shown in Table 1:

Table 1

In Table 1, Rx means reception, FR means frequency range (Frequency range), FDD means frequency division multiplexing (Frequency Division Duplex), QAM means quadrature amplitude modulation (Quadrature Amplitude Modulation).

random access procedure

NR supports two types of random access procedures: message 1 (MSG1) 4-step random access (Random Access, RA) type (4-step Random Access Channel, 4-step RACH) and MSGA 2-step RA type (2 -step RACH). Both types of RA processes support contention based random access (Contention based RA, CBRA) and contention free random access (Contention free RA, CFRA).

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

(1) When CFRA resources are not configured, the UE selects the 2-step RA type and the 4-step RA type based on the Reference Signal Received Power (RSRP) threshold;

(2) When CFRA resources are configured for the 4-step RA type, the UE performs random access using the 4-step RA type;

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

Contention-based 4-step RACH process

In 4-step RACH, the UE first sends MSG1 to the network, including the preamble; after the UE sends the preamble, it will monitor the Physical downlink control channel (PDCCH) within the RAR time window (RA Response window) ), using the fallback (fallback) downlink control information (Downlink Control Information, DCI) format, ie, DCI format 1_0, to receive a random access response (random access response, RAR) scheduled by the PDCCH scrambled with the RA-RNTI. If the preamble index (preamble index) in the RAR is the same as the preamble index sent by the UE, it is considered that the RAR has been successfully received. At this time, the UE can stop monitoring the RAR and according to the uplink scheduling grant (Uplink grant, UL grant) to send MSG3; MSG3 is transmitted on the uplink shared channel (Uplink Shared Channel, UL-SCH), and uses hybrid automatic repeat request (Hybrid Automatic Repeat Request, HARQ), using the temporary cell wireless network temporary identifier indicated by RAR (Temporary Cell RNTI, TC-RNTI) scrambles the PDCCH, and uses the fallback (fallback) DCI format, namely DCI format 1_0, to schedule the retransmission of MSG3. MSG3 contains the unique identifier of the UE. This flag will be used for conflict resolution in step four. After the network receives MSG3, it will use the TC-RNTI scrambled PDCCH to schedule MSG4. When the UE successfully decodes the "UE Contention Resolution Identity MAC control element" contained in MSG4 (that is, UE Contention Resolution Identity Medium Access Control, MAC) control unit)" matches the "UE Contention Resolution Identity (ie, UE contention resolution identity)" sent by MSG3, UE will consider the random access as successful and set its cell radio network temporary identity (Cell RNTI, C-RNTI) Set to TC-RNTI, that is, complete 4-step random access.

MAC Protocol Data Unit (Protocol Data Unit, PDU) and Logical Channel Identity (Logical Channel Identity, LCID)

A MAC protocol data unit (Protocol Data Unit, PDU) includes one or more MAC sub-PDUs (subPDU). Each MAC subPDU contains any of the following:

(1) Contains only the MAC subheader;

(2) MAC sub-header and service data unit (Service Data Unit, SDU);

(3) MAC sub-head and MAC control unit (control element, CE);

(4) MAC sub-header and padding;

The size of the MAC service data unit (Service Data Unit, SDU) is not fixed, and each MAC subheader corresponds to a MAC SDU or a MAC CE or padding.

The information content of the above MAC sub-header is shown in Table 2:

Table 2

The value of LCID used for the uplink shared channel is shown in Table 3:

table 3

During the current RedCap project discussions, it was determined that the early identification method based on MSG1 and/or MSG3 clearly identifies RedCap UE:

For 4-step random access, at least MSG1 is supported for early identification, and the identification method includes configuring dedicated Physical Random Access Channel (Physical Random Access Channel, PRACH) resources or dedicated preamble and/or dedicated The uplink initial bandwidth part (Bandwidth Part, BWP).

MSG3 early recognition is based on a dedicated logical channel ID (logical Channel ID, LCID)

The method and device provided by the embodiments of the present application will be described in detail below through specific embodiments and application scenarios with reference to the accompanying drawings.

Referring to Fig. 2, the embodiment of the present application provides a kind of information reporting method, and the executive body of this method can be terminal, and specific steps include:

Step 201: The terminal generates target information according to at least one item of random access related information configured by the network, first indication information, terminal related information, and first configuration information;

Step 202: The terminal reports the target information through the physical uplink shared channel (Physical Uplink Shared Channel, PUSCH) or MSG3 of the message MSGA.

In this embodiment of the application, the terminal generates target information according to at least one item of random access related information configured by the network, first indication information, related information of the terminal, and first configuration information, wherein the terminal generates target information according to the random access information configured by the network. It can be confirmed whether MSG1 or MSGA has been used for early identification, and the terminal determines according to the first indication information that when a dedicated PRACH resource or a dedicated preamble and/or a dedicated uplink initial BWP is configured for the RedCap UE, the terminal's Whether the PUSCH of MSG3 or MSG A can use the first LCID, and then the terminal determines whether to report the target information according to the relevant information of the terminal and/or the first configuration information, specifically through the PUSCH of MSG3 and/or MSGA.

It can be understood that, for the 4-step RA type, the messages involved are MSG1 and MSG3 respectively, and for the 2-step RA type, the messages involved are MSGA, wherein, MSGA includes two parts: the preamble and the PUSCH part (part) of MSGA;

In a possible implementation manner, the random access related information configured by the network includes one or more of the following:

(1) Terminal-specific random access resources or dedicated preambles;

(2) Uplink bandwidth part dedicated to the terminal (Bandwidth Part, BWP);

(3) Whether the network enables identification of terminals based on MSG1 and/or MSGA dedicated physical random access channel (Physical Random Access Channel, PRACH) resources or dedicated preambles;

(4) Whether the network enables terminal identification based on MSG1 and/or MSGA-specific uplink BWP;

(5) Whether the network supports PUSCH based on MSG3 and/or MSGA for early identification;

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

In a possible implementation manner, the first indication information is used to indicate: a dedicated random access resource or a dedicated preamble is configured on the network, and/or a dedicated uplink BWP is configured on the network, and MSG1 or MSGA is used to identify the terminal's In this case, whether to use the first logical channel to transmit the PUSCH of MSG 3 and/or MSGA.

In this way, through the random access related information and/or the first indication information configured by the above network, the terminal can confirm whether the terminal has been identified in advance through MSG1 or MSGA, and whether it supports subsequent PUSCH reporting through MSG 3 and/or MSGAMore Related Information.

In a possible implementation manner, according to the random access related information configured by the network, it is determined that the MSG1 or MSGA sent by the terminal uses a dedicated PRACH resource or that the MSG1 or MSGA sent by the terminal contains a dedicated preamble, and/or, When the MSG1 or MSGA sent by the terminal uses a dedicated uplink BWP, the target information includes additional information; this situation corresponds to the fact that it has been identified in advance through MSG1 or MSGA;

According to the random access related information configured by the network, it is determined that the MSG1 or MSGA sent by the terminal does not use a dedicated PRACH resource and the MSG1 or MSGA sent by the terminal does not contain a dedicated preamble, and/or, If 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 case corresponds to failure MSG1 or MSGA for early identification;

The above-mentioned initial access information is used to indicate whether the terminal is a RedCap terminal. The above-mentioned additional information is associated with the attributes of the terminal or the service information of the terminal, measurement results, etc. The function of the additional information is to allow the network side to obtain more UE-related information. Therefore, UEs can be scheduled more reasonably.

In a possible implementation manner, the additional information includes one or more of the following:

(1) The number of receiving antennas of the terminal or the maximum number of antennas supported by the terminal, such as 1 Rx or 2 Rx;

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

(3) Whether the terminal needs coverage enhancement, for example, the terminal judges that the network needs to perform coverage enhancement in subsequent scheduling according to the measurement results;

(4) Modulation order level or maximum modulation coding level supported by the terminal;

(5) The quality of the serving cell measured by the terminal;

(6) Information about the delay requirements of the trigger event for the terminal to enter the connected state;

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

(8) The processing time supported by the terminal;

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

(10) The number of DRBs or the maximum number of DRBs supported by the terminal;

(11) RRC processing delay supported by the terminal.

(12) The information of other terminals is not specifically limited.

In a possible implementation manner, the relevant information of the terminal includes one or more of the following:

(1) Attributes of the terminal;

(2) Measurement results of the terminal;

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

Among them, the attributes of the terminal include one or more of the following:

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

(1.2) The working system supported by the terminal;

(1.3) Whether the terminal needs coverage enhancement;

(1.4) Modulation order level or maximum modulation coding level supported by the terminal;

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

(1.6) The processing time supported by the terminal;

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

(1.8) The number of data radio bearers (Data Radio Bearer, DRB) or the maximum number of DRBs supported by the terminal;

(1.9) The radio resource control (Radio Resource Control, RRC) processing delay supported by the terminal;

(1.10) The attributes of other terminals are not specifically limited.

Terminal measurements, including:

(2.1) The quality of the serving cell measured by the terminal;

(2.2) The measurement results of other terminals are not specifically limited.

The attributes of the service executed when the terminal enters the connected state, including:

(3.1) Information about the delay requirements of the trigger event for the terminal to enter the connected state.

(3.2) The attributes of the services executed by other terminals entering the connected state are not specifically limited.

In a possible implementation manner, the first configuration information includes one or more of the following:

(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 is specifically to report when the maximum number of receiving antennas supported by the terminal is the first value; or to instruct the terminal to report The maximum number of receiving antennas supported by the terminal; the first value includes 1, 2; the meaning of the number of receiving antennas supported by the terminal is: configure 1 Rx terminal to report; or 2 Rx terminal to report; or configure the terminal to report supported receiving number of antennas;

(2) The working system supported by the terminal; for example, the first configuration information specifically reports when the working system supported by the terminal is the first value; the first value includes half-duplex and full-duplex; or indicates the terminal Report the working system supported by the terminal;

(3) Whether the terminal needs coverage enhancement, for example, the first configuration information specifically reports when the terminal needs coverage enhancement;

(4) The modulation order level or the maximum modulation coding level supported by the terminal; for example, the first configuration information is specifically to report when the maximum modulation order supported by the terminal is the first value; or to instruct the terminal to report the maximum modulation level supported by the terminal; Modulation order; the first value includes 64 QAM, 256 QAM;

(5) The quality of the serving cell measured by the terminal or the threshold of the quality of the serving cell measured by the terminal; for example, if the first configuration information includes the threshold, the UE-related measurement result is reported when it is less than/greater than/less than or equal to/greater than or equal to the threshold; or to indicate the terminal Report the quality of the serving cell measured by the terminal;

(6) The delay requirement of the trigger event for the terminal to enter the connected state; for example, the first configuration information indicates that the trigger event for the terminal to establish a connection is the first value to report; or instruct the terminal to report the trigger time for the terminal to enter the connected state. Extend the grade required; The first value includes voice service (voice), emergency service (emergency);

(7) The maximum transmission rate supported by the terminal or the maximum transmission rate threshold 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, report; or Instruct the terminal to report the level of the maximum transmission rate supported by the terminal;

(8) The processing duration supported by the terminal reported by the terminal or the maximum processing duration threshold supported by the terminal;

(9) Layer 2 cache information or soft cache information supported by the terminal reported by the terminal;

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

(11) The RRC processing delay supported by the terminal reported by the terminal.

In this way, the terminal can determine the content of the additional information in the target information that needs to be reported according to the relevant information of the terminal and/or the first configuration information, for example, the first configuration information is the number of antennas, which indicates that the 1 Rx terminal reports the number of antennas; then when When the terminal's own attribute is 1 Rx, it will generate additional information and report it; 2 Rx terminals will not generate additional information.

In a possible implementation manner, the foregoing first configuration information is preconfigured by network configuration and/or protocol; the foregoing first indication information is preconfigured by network configuration and/or protocol.

Specifically, when the MSG1 pre-identification (MSG1 based solution) is applied in the serving cell, the protocol stipulates or the network indicates whether the LCID of MSG3 adopts a newly defined LCID or an existing LCID through configuration. MSGA pre-identification is similar and will not be repeated here.

In a possible implementation manner, the carrying manner of the first target information includes one or more of the following:

(1) Use the first LCID to indicate the target information, where the first LCID is used to identify the first logical channel, and the first logical channel is used to transmit the MSG3 of the terminal and/or the PUSCH of the MSGA;

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) + MAC SDU (including the legacy (legacy) RRC message), that is, the newly introduced LCID corresponds to the legacy RRC message, legacy RRC message refers to R15 version, the existing RRC message in R16 version;

In the embodiment of this application, the number of newly introduced LCIDs is N, and N is a positive integer greater than or equal to 1; legacy 48-bits RRC messages include RRC establishment request messages, RRC recovery request messages, RRC reconstruction request messages, and system information request messages ; The legacy 64-bits RRC message includes the RRC recovery request message. Specifically, there are currently two types of RRC messages, one with a size of 48 bits and one with a size of 64 bits. Therefore, at least two LCIDs need to be introduced. One LCID corresponds to an RRC message with a size of 48 bits, and the other LCID corresponds to an RRC message with a size of 64 bits. ;

In the embodiment of the present application, the newly introduced LCID is used to indicate the content of the first target information, so that the network can correspondingly determine the content of the corresponding first target information after receiving the newly introduced LCID.

(2) using the first MAC CE to carry target information; wherein, the corresponding MAC subhead of the first MAC CE includes the first LCID;

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, and the first target information is carried in the new MAC CE;

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

(3) Use the first RRC message to carry the target information; wherein, the MAC subhead corresponding to the MAC SDU containing the first RRC message contains the first LCID.

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 new 64-bits 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 (non full) inactive RNTI (Inactive RNTI, I-RNTI) (that is, the case of 48bits legacy RRC message)), the legacy LCID is the current The LCID corresponding to the 64bits RRC message is used to correspond to the new 64bits RRC message, wherein the new 64bits RRC message is a new information element (Information Element, IE) added to the legacy 48bits RRC message to indicate the first target information;

In the present application embodiment, use the legacy LCID of the RRC message of 64bits, the RRC message identified by this legacy LCID has the message size of 64bits like this, and 48bits are the legacy RRC message of existing 48bits in these 64bits, then corresponding There is a message size of 16 bits for indicating the first target information, that is to say, the above-mentioned new 64-bits RRC message is composed of a 48-bits legacy RRC message and a 16-bits first target information.

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

In the embodiment of the present application, the introduced LCID indicates, for example, a new RRC message with a size of 80 bits, and the new RRC message with a size of 80 bits includes a legacy RRC message with a size of 64 bits and a first target information with a size of 16 bits, that is, It is said that the above-mentioned new RRC message is composed of the legacy RRC message of 64bits and the first target information of 16bits.

The scheme of the present application is described below in conjunction with specific embodiment:

Embodiment 1 of the present invention: RedCap UE is based on the MSG-3 advance identification method so that the network can clearly identify RedCap UE

Step 1: If the UE is a RedCap UE, and the network does not configure the preamble dedicated to RedCap UE, or the network does not configure the PRACH resource dedicated to RedCap UE, or the UE selects the PRACH resource of the legacy UE and the MAC entity of the UE selects the legacy UE RA preamble.

Step 2: The RedCap UE sends MSG 3, wherein the newly introduced logical channel ID is used in the MAC subheader in MSG3, and 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.

The bearing manner of the reporting message includes:

(1) Two newly introduced LCID+legacy RRC messages, the newly introduced LCID corresponds to the legacy RRC message. For example, the introduction of uplink-Common Control Channel X (Uplink-Common Control Channel X, UL-CCCHX) logical channel still carries legacy 48bits RRC establishment request message or 48bit RRC recovery request message or 64bits RRC establishment request message

(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 the indication information that the UE is a RedCap UE

(3) Legacy LCID+ new 64-bits RRC message (setup request (setup-request) and resume request (resume-request)), applicable to the case of non full I-RNTI, the new RRC message can add new IE To report the indication that the UE is a RedCap UE

Embodiment 2 of the present invention: RedCap UE is based on the MSG1 early identification method so that the network can clearly identify RedCap UE

Step 1: If the UE is a RedCap UE, and the network configures a preamble dedicated to RedCap UE, and the MAC entity selects a RA preamble dedicated to RedCap UE, or the network configures a PRACH resource dedicated to RedCap UE, and the UE selects a dedicated RA preamble for RedCap UE PRACH resources.

Step 2: RedCap UE sends MSG 3, and determines whether to report additional information according to the first criterion (that is, the first configuration information mentioned above);

Additional information includes at least one of the following:

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

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

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

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

(5) The quality of the serving cell measured by the terminal.

(6) Information about the delay requirement of the trigger event for the terminal to enter the connected state.

(7) The maximum transmission rate supported by the terminal.

(8) The processing time supported by the terminal.

(9) Layer 2 cache information or soft cache information supported by the terminal.

(10) The number of DRBs or the maximum number of DRBs supported by the terminal.

(11) RRC processing delay supported by the terminal.

(12) The information of other terminals is not specifically limited.

The first criteria include:

(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 new The imported logical channel ID; the number of Rx is a positive integer greater than or equal to 1.

(2) The working system supported by the terminal, for example, if the working system supported by the RedCap UE is the first value, it uses the original logical channel ID; if the working system supported by the RedCap UE is the second value, it uses the newly introduced The logical channel ID; the working system includes half-duplex, full-duplex FD, and others.

(3) Whether the terminal needs coverage enhancement, for example, if the RedCap UE wants the network to use the coverage enhancement method for scheduling, then use the new logical channel ID, otherwise use the original logical channel ID; the RedCap UE judges the subsequent scheduling process The criterion of whether coverage is required in may be configured and/or predefined by the network and/or implemented by the UE.

(4) The modulation order level or the 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 RedCap UE is in FR1 If the maximum support in FR1 is the second value, it uses a new logical channel ID; the maximum modulation order supported by the RedCap UE in FR1 includes 64 QAM, 256 QAM, and others.

(5) The quality of the serving cell measured by the terminal, for example, when the quality of the serving cell detected by the UE is higher than the threshold value, the UE uses the newly introduced logical channel ID, otherwise the original logical channel ID is used. The threshold value may be configured by the network, or predefined, or implemented by the UE.

(6) The delay requirement of the trigger event that the terminal enters the connected state, for example, when the UE receives paging and the reason carried in the paging is an emergency service or a voice service, etc., which require as little delay as possible, Then UE uses the newly introduced logical channel ID, otherwise uses the original logical channel ID;

(7) The maximum transmission rate supported by the terminal. If the maximum transmission rate supported by the current UE is higher than the threshold value, use the new logical channel ID, otherwise use the original logical channel ID;

(8) The current UE minimum required transmission rate;

(9) Network configuration. For example, the network instructs the UE through the indication information that the network requires the UE to report additional information. If the UE receives the indication information, it uses the newly introduced logical channel ID. If the UE does not receive the indication information, it uses the original channel ID. The logical channel ID; the additional information includes: the number of Rx, supported working modes, channel quality, modulation order, whether coverage enhancement is required, cell quality, delay requirements, and maximum/minimum transmission rates;

(10) Others;

The carrying mode of additional information includes any of the following:

(1) Two newly introduced LCID+legacy RRC messages. At this time, the indication mode of the additional information is whether to use the newly introduced LCID indication;

(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 auxiliary message is carried in the new MAC CE;

(3) legacy LCID + new 64-bits RRC message (setup-request and resume-request), applicable to the case of non full I-RNTI, the legacy LCID is the LCID corresponding to the current 64-bits RRC message, use this LCID to correspond A new 64bits RRC message, wherein the new 64bits RRC message is to add a new IE to the legacy 48bits RRC message to indicate the auxiliary message;

(4) New LCID+new RRC message; The size of the new RRC message is greater than the size of the legacy RRC message, that is, with respect to the legacy RRC message, a new IE should be added in the new RRC message to indicate additional information;

Embodiment 3 of the present invention: Normal (Normal) UE/non-RedCap (Non-RedCap) UE uses the newly introduced logical channel ID

1. If the MSG1 based solution is applied in the serving cell

2. The Normal UE/Non-RedCap in the RRC idle state (RRC_IDLE) or RRC inactive state (RRC_INACTIVE) reports additional information according to the third criterion when sending Msg3.

Additional information includes at least one of the following:

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

(3) Whether the terminal needs coverage enhancement, including the Signal to Interference plus Noise Ratio (SINR) or RSRP size of the Normal/Non-RedCap UE or others.

(5) The quality of the serving cell measured by the terminal;

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

(8) The processing time supported by the terminal;

(11) RRC processing delay supported by the terminal.

(12) The information of other terminals is not specifically limited.

The second criterion for determining the value of the logical channel ID used by the MAC subheader in MSG3 (that is, the first configuration information described above) includes:

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

(2) The working system supported by the terminal reported by the terminal;

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

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

(5) The quality of the serving cell measured by the terminal reported by the terminal. For example, when the quality of the serving cell detected by the UE is higher than the threshold value, the UE uses the newly introduced logical channel ID, otherwise the original logical channel ID is used. The threshold value may be configured by the network, or predefined, or implemented by the UE;

(6) The delay requirement of the trigger event of the terminal entering the connected state reported by the terminal;

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

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

(11) The RRC processing delay supported by the terminal reported by the terminal;

(12) Random selection/realization based on UE;

(13) Network configuration;

(14) Others.

Referring to Fig. 3, the embodiment of the present application provides an information reporting device 300, including:

A generating module 301, configured for the terminal to generate target information according to at least one of random access related information configured by the network, first indication information, related information of the terminal, and first configuration information;

The reporting module 302 is used for the terminal to report the target information through PUSCH or MSG3 of MSGA.

The random access resource dedicated to the terminal or a dedicated preamble;

An uplink BWP dedicated to the terminal;

whether the network can identify the terminal based on MSG1 and/or MSGA dedicated PRACH resource or dedicated preamble;

whether the network can identify the terminal based on the uplink BWP dedicated to MSG1 and/or MSGA;

Whether the network supports PUSCH based on MSG3 and/or MSGA for early identification;

Whether the network supports the first logical channel; the first logical channel is used to transmit the MSG3 of the terminal and/or the PUSCH of the MSGA, and the identifier of the first logical channel is the first LCID.

In a possible implementation manner, the first indication information is used to indicate: a dedicated random access resource or a dedicated preamble is configured on the network, and/or a dedicated uplink BWP is configured on the network, and MSG1 or MSGA is used to identify In the case of the terminal, whether to use the first logical channel to transmit the PUSCH of MSG3 and/or MSGA.

In a possible implementation manner, according to the random access related information configured by the network, it is determined that the MSG1 or MSGA sent by the terminal uses a dedicated PRACH resource or that the MSG1 or MSGA sent by the terminal contains a dedicated preamble code, and/or, when the MSG1 or MSGA sent by the terminal uses a dedicated uplink BWP, the target information includes additional information;

According to the random access related information configured by the network, it is determined that the MSG1 or MSGA sent by the terminal does not use a dedicated PRACH resource and the MSG1 or MSGA sent by the terminal does not contain a dedicated preamble, and/or, When 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, and the additional information is associated with attributes of the terminal.

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

The working system supported by the terminal;

Whether the terminal needs coverage enhancement;

The modulation order level or the maximum modulation and coding level supported by the terminal;

The quality of the serving cell measured by the terminal;

Information on delay requirements of the trigger event for the terminal to enter the connected state;

The maximum transmission rate supported by the terminal;

The processing duration supported by the terminal;

Layer 2 cache information or soft cache information supported by the terminal;

The number of DRBs or the maximum number of DRBs supported by the terminal;

The RRC processing delay supported by the terminal.

attributes of said terminal;

a measurement result of the terminal;

The attribute of the service executed when the terminal enters the connected state;

The attributes of the terminal include one or more of the following:

The number of receiving antennas;

The working system supported by the terminal;

Whether the terminal needs coverage enhancement;

The maximum transmission rate supported by the terminal;

The processing duration supported by the terminal;

Layer 2 cache information or soft cache information supported by the terminal;

The number of DRBs or the maximum number of DRBs supported by the terminal;

The RRC processing delay supported by the terminal;

The measurement results of the terminal include:

The quality of the serving cell measured by the terminal;

The attributes of the service performed by the terminal entering the connected state include:

Information about the time delay requirements of the trigger event for the terminal to enter the connected state.

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

The working system supported by the terminal;

Whether the terminal needs coverage enhancement;

The serving cell quality measured by the terminal or the serving cell quality threshold measured by the terminal;

The trigger event for the terminal to enter the connection state requires delay;

The maximum transmission rate supported by the terminal or the maximum transmission rate threshold supported by the terminal;

The processing duration supported by the terminal or the maximum processing duration threshold supported by the terminal;

Layer 2 cache information or soft cache information supported by the terminal;

The number of DRBs or the maximum number of DRBs supported by the terminal;

The RRC processing delay supported by the terminal.

In a possible implementation manner, the first configuration information is preconfigured by network configuration and/or protocol;

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

In a possible implementation manner, the carrying manner of the target information includes one or more of the following:

Use a first LCID to indicate the target information, where the first LCID is used to identify a first logical channel, and the first logical channel is used to transmit the PUSCH of MSG3 and/or MSGA of the terminal;

Use the first MAC CE to carry the target information; wherein, the corresponding MAC subheader of the first MAC CE includes the first LCID;

Use the first RRC message to carry the target information; wherein the MAC subheader corresponding to the MAC SDU containing the first RRC message contains the first LCID.

The apparatus for processing PUCCH resource overlap provided by the embodiment of the present application can realize each process realized by the method embodiment shown in FIG. 2 and achieve the same technical effect. To avoid repetition, details are not repeated here.

FIG. 4 is a schematic diagram of a hardware structure of a terminal implementing an embodiment of the present application.

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

Those skilled in the art can understand that the terminal 400 may also include a power supply (such as a battery) for supplying power to various components, and the power supply may be logically connected to the processor 410 through the power management system, so as to manage charging, discharging, and power consumption through the power management system. Management and other functions. The terminal structure shown in FIG. 4 does not constitute a limitation on the terminal, and the terminal may include more or fewer components than shown in the figure, or combine some components, or arrange different components, which will not be repeated here.

It should be understood that, in the embodiment of the present application, the input unit 404 may include a graphics processor (Graphics Processing Unit, GPU) 4041 and a microphone 4042, and the graphics processor 4041 is used for the image capture device ( Such as the image data of the still picture or video obtained by the camera) for processing. The display unit 406 may include a display panel 4061, and the display panel 4061 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 4071 and other input devices 4072 . The touch panel 4071 is also called a touch screen. The touch panel 4071 may include two parts, a touch detection device and a touch controller. Other input devices 4072 may include, but are not limited to, physical keyboards, function keys (such as volume control keys, switch keys, etc.), trackballs, mice, and joysticks, which will not be repeated here.

In the embodiment of the present application, the radio frequency unit 401 receives the downlink data from the network side device, and processes it to the processor 410; in addition, sends the uplink data to the network side device. Generally, 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, and the like.

The memory 409 can be used to store software programs or instructions as well as various data. The memory 409 may mainly include a program or instruction storage area and a data storage area, wherein the program or instruction storage area may store an operating system, an application program or instructions required by at least one function (such as a sound playback function, an image playback function, etc.) and the like. In addition, the memory 409 may include a high-speed random access memory, and may also include a nonvolatile memory, wherein the nonvolatile memory may be a read-only memory (Read-Only Memory, ROM), a programmable read-only memory (Programmable ROM) , PROM), erasable programmable read-only memory (Erasable PROM, EPROM), electrically erasable programmable read-only memory (Electrically EPROM, EEPROM) or flash memory. For example at least one magnetic disk storage device, flash memory device, or other non-volatile solid-state storage device.

The processor 410 may include one or more processing units; optionally, the processor 410 may integrate an application processor and a modem processor, wherein the application processor mainly processes the operating system, user interface and application programs or instructions, etc., Modem processors mainly handle wireless communications, such as baseband processors. It can be understood that the foregoing modem processor may not be integrated into the processor 410 .

The processor 410 is configured for the terminal to generate target information according to at least one of random access related information configured by the network, first indication information, related information of the terminal, and first configuration information;

The processor 410 is configured for the terminal to report the target information through PUSCH or MSG3 of the MSGA.

The random access resource dedicated to the terminal or a dedicated preamble;

An uplink BWP dedicated to the terminal;

The number of receiving antennas;

The working system supported by the terminal;

Whether the terminal needs coverage enhancement;

The quality of the serving cell measured by the terminal;

The maximum transmission rate supported by the terminal;

The processing duration supported by the terminal;

Layer 2 cache information or soft cache information supported by the terminal;

The number of DRBs or the maximum number of DRBs supported by the terminal;

The RRC processing delay supported by the terminal.

attributes of said terminal;

a measurement result of the terminal;

The attributes of the terminal include one or more of the following:

The number of receiving antennas;

The working system supported by the terminal;

Whether the terminal needs coverage enhancement;

The maximum transmission rate supported by the terminal;

The processing duration supported by the terminal;

Layer 2 cache information or soft cache information supported by the terminal;

The number of DRBs or the maximum number of DRBs supported by the terminal;

The RRC processing delay supported by the terminal;

The measurement results of the terminal include:

The quality of the serving cell measured by the terminal;

The working system supported by the terminal;

Whether the terminal needs coverage enhancement;

Layer 2 cache information or soft cache information supported by the terminal;

The number of DRBs or the maximum number of DRBs supported by the terminal;

The RRC processing delay supported by the terminal.

Use the first RRC message to carry the target information; wherein the MAC subheader corresponding to the MAC SDU containing the first RRC message includes the first LCID.

An embodiment of the present application further provides a computer program product, the program product is stored in a non-volatile storage medium, and the program product is executed by at least one processor to implement the steps of the method as shown in FIG. 2 .

The embodiment of the present application also provides a readable storage medium, the readable storage medium stores a program or an instruction, and when the program or instruction is executed by the processor, the various processes of the above-mentioned method embodiment shown in FIG. 2 are implemented, and can To achieve the same technical effect, in order to avoid repetition, no more details are given here.

Wherein, the processor is the processor in the terminal described in the foregoing embodiments. The readable storage medium includes computer readable storage medium, such as computer read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), magnetic disk or optical disk, etc.

The embodiment of the present application further provides a chip, the chip includes a processor and a communication interface, the communication interface is coupled to the processor, and the processor is used to run a network-side device program or instruction to implement the above-mentioned Figure 2. Each process of the method embodiment is shown, and the same technical effect can be achieved, so in order to avoid repetition, details are not repeated here.

It should be understood that the chip mentioned in the embodiment of the present application may also be called a system-on-chip, a system-on-chip, a system-on-a-chip, or a system-on-a-chip.

It should be noted that, in this document, the term "comprising", "comprising" or any other variation thereof is intended to cover a non-exclusive inclusion such that a process, method, article or apparatus comprising a set of elements includes not only those elements, It also includes other elements not expressly listed, or elements inherent in the process, method, article, or device. Without further limitations, an element defined by the phrase "comprising a ..." does not preclude the presence of additional identical elements in the process, method, article, or apparatus comprising that element. In addition, it should be pointed out that the scope of the methods and devices in the embodiments of the present application is not limited to performing functions in the order shown or discussed, and may also include performing functions in a substantially simultaneous manner or in reverse order according to the functions involved. Functions are performed, for example, the described methods may be performed in an order different from that described, and various steps may also be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.

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

The embodiments of the present application have been described above in conjunction with the accompanying drawings, but the present application is not limited to the above-mentioned specific implementations. The above-mentioned specific implementations are only illustrative and not restrictive. Those of ordinary skill in the art will Under the inspiration of this application, without departing from the purpose of this application and the scope of protection of the claims, many forms can also be made, all of which belong to the protection of this application.

Claims

A method for reporting information, comprising:

The terminal generates target information according to at least one of random access related information configured by the network, first indication information, related 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.
The method according to claim 1, wherein the random access related information configured by the network includes one or more of the following:

The random access resource dedicated to the terminal or a dedicated preamble;

The uplink bandwidth part BWP dedicated to the terminal;

Whether the network can identify the terminal based on MSG1 and/or MSGA dedicated physical random access channel PRACH resource or dedicated preamble;

whether the network can identify the terminal based on the uplink BWP dedicated to MSG1 and/or MSGA;

Whether the network supports PUSCH based on MSG3 and/or MSGA for early identification;

Whether the network supports the first logical channel; the first logical channel is used to transmit the MSG3 of the terminal and/or the PUSCH of the MSGA, and the identifier of the first logical channel is the first logical channel identifier LCID.
The method according to claim 2, wherein the first indication information is used to indicate: a dedicated random access resource or a dedicated preamble is configured in the network, and/or a dedicated uplink BWP is configured in the network, and MSG1 or In the case where the MSGA identifies the terminal, whether to use the first logical channel to transmit the PUSCH of MSG 3 and/or MSGA.
The method according to claim 1, wherein,

According to the random access related information configured by the network, it is determined that the MSG1 or MSGA sent by the terminal uses a dedicated PRACH resource or that the MSG1 or MSGA sent by the terminal contains a dedicated preamble, and/or, the terminal In the case that the sent MSG1 or MSGA uses a dedicated uplink BWP, the target information includes additional information;

According to the random access related information configured by the network, it is determined that the MSG1 or MSGA sent by the terminal does not use a dedicated PRACH resource and the MSG1 or MSGA sent by the terminal does not contain a dedicated preamble, and/or, When 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 method according to claim 4, wherein 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 working system supported by the terminal;

Whether the terminal needs coverage enhancement;

The modulation order level or the maximum modulation and coding level supported by the terminal;

The quality of the serving cell measured by the terminal;

Information on delay requirements of the trigger event for the terminal to enter the connected state;

The maximum transmission rate supported by the terminal;

The processing duration supported by the terminal;

Layer 2 cache information or soft cache information supported by the terminal;

The number of DRBs or the maximum number of DRBs supported by the terminal;

The radio resource control RRC processing delay supported by the terminal.
The method according to claim 1, wherein the relevant information of the terminal includes one or more of the following:

attributes of said terminal;

a measurement result of the terminal;

The attribute of the service executed when the terminal enters the connected state;

The attributes of the terminal 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 working system supported by the terminal;

Whether the terminal needs coverage enhancement;

The modulation order level or the maximum modulation and coding level supported by the terminal;

The maximum transmission rate supported by the terminal;

The processing duration supported by the terminal;

Layer 2 cache information or soft cache information supported by the terminal;

The number of DRBs or the maximum number of DRBs supported by the terminal;

The RRC processing delay supported by the terminal;

The measurement results of the terminal include:

The quality of the serving cell measured by the terminal;

The attributes of the service performed by the terminal entering the connected state include:

Information about the time delay requirements of the trigger event for the terminal to enter the connected state.
The method according to claim 1, wherein 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 working system supported by the terminal;

Whether the terminal needs coverage enhancement;

The modulation order level or the maximum modulation and coding level supported by the terminal;

The serving cell quality measured by the terminal or the serving cell quality threshold measured by the terminal;

The trigger event for the terminal to enter the connection state requires delay;

The maximum transmission rate supported by the terminal or the maximum transmission rate threshold supported by the terminal;

The processing duration supported by the terminal or the maximum processing duration threshold supported by the terminal;

Layer 2 cache information or soft cache information supported by the terminal;

The number of DRBs or the maximum number of DRBs supported by the terminal;

The RRC processing delay supported by the terminal.
The method according to claim 1, wherein,

The first configuration information is preconfigured by network configuration and/or protocol;

The first indication information is pre-configured by network configuration and/or protocol.
The method according to claim 1, wherein the carrying manner of the target information includes one or more of the following:

Use a first LCID to indicate the target information, where the first LCID is used to identify a first logical channel, and the first logical channel is used to transmit the PUSCH of MSG3 and/or MSGA of the terminal;

Use the first media access control unit MAC CE to carry the target information; wherein the corresponding MAC subheader of the first MAC CE includes the first LCID;

Use the first RRC message to carry the target information; wherein, the MAC subheader corresponding to the medium access control service data unit MAC SDU including the first RRC message includes the first LCID.
An information reporting device, comprising:

A generating module, configured for the terminal to generate target information according to at least one of random access related information configured by the network, first indication information, related information of the terminal, and first configuration information;

The reporting module is used for the terminal to report the target information through PUSCH or MSG3 of MSGA.
The device according to claim 10, wherein the random access related information configured by the network includes one or more of the following:

The random access resource dedicated to the terminal or a dedicated preamble;

An uplink BWP dedicated to the terminal;

whether the network can identify the terminal based on MSG1 and/or MSGA dedicated PRACH resource or dedicated preamble;

whether the network can identify the terminal based on the uplink BWP dedicated to MSG1 and/or MSGA;

Whether the network supports PUSCH based on MSG3 and/or MSGA for early identification;

Whether the network supports the first logical channel; the first logical channel is used to transmit the MSG3 of the terminal and/or the PUSCH of the MSGA, and the identifier of the first logical channel is the first LCID.
The device according to claim 11, wherein the first indication information is used to indicate: a dedicated random access resource or a dedicated preamble is configured on the network, and/or a dedicated uplink BWP is configured on the network, and MSG1 or In the case where the MSGA identifies the terminal, whether to use the first logical channel to transmit the PUSCH of MSG 3 and/or MSGA.
The apparatus of claim 10, wherein,

According to the random access related information configured by the network, it is determined that the MSG1 or MSGA sent by the terminal uses a dedicated PRACH resource or that the MSG1 or MSGA sent by the terminal contains a dedicated preamble, and/or, the terminal In the case that the sent MSG1 or MSGA uses a dedicated uplink BWP, the target information includes additional information;

According to the random access related information configured by the network, it is determined that the MSG1 or MSGA sent by the terminal does not use a dedicated PRACH resource and the MSG1 or MSGA sent by the terminal does not contain a dedicated preamble, and/or, When 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, and the additional information is used for network scheduling of the terminal.
The device according to claim 13, wherein 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 working system supported by the terminal;

Whether the terminal needs coverage enhancement;

The modulation order level or the maximum modulation and coding level supported by the terminal;

The quality of the serving cell measured by the terminal;

Information on delay requirements of the trigger event for the terminal to enter the connected state;

The maximum transmission rate supported by the terminal;

The processing duration supported by the terminal;

Layer 2 cache information or soft cache information supported by the terminal;

The number of DRBs or the maximum number of DRBs supported by the terminal;

The RRC processing delay supported by the terminal.
The device according to claim 10, wherein the relevant information of the terminal includes one or more of the following:

attributes of said terminal;

a measurement result of the terminal;

The attribute of the service executed when the terminal enters the connected state;

The attributes of the terminal 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 working system supported by the terminal;

Whether the terminal needs coverage enhancement;

The modulation order level or the maximum modulation and coding level supported by the terminal;

The maximum transmission rate supported by the terminal;

The processing duration supported by the terminal;

Layer 2 cache information or soft cache information supported by the terminal;

The number of DRBs or the maximum number of DRBs supported by the terminal;

The RRC processing delay supported by the terminal;

The measurement results of the terminal include:

The quality of the serving cell measured by the terminal;

The attributes of the service performed by the terminal entering the connected state include:

Information about the time delay requirements of the trigger event for the terminal to enter the connected state.
The device according to claim 10, wherein 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 working system supported by the terminal;

Whether the terminal needs coverage enhancement;

The modulation order level or the maximum modulation and coding level supported by the terminal;

The serving cell quality measured by the terminal or the serving cell quality threshold measured by the terminal;

The trigger event for the terminal to enter the connection state requires delay;

The maximum transmission rate supported by the terminal or the maximum transmission rate threshold supported by the terminal;

The processing duration supported by the terminal or the maximum processing duration threshold supported by the terminal;

Layer 2 cache information or soft cache information supported by the terminal;

The number of DRBs or the maximum number of DRBs supported by the terminal;

The RRC processing delay supported by the terminal.
The apparatus of claim 10, wherein,

The first configuration information is preconfigured by network configuration and/or protocol;

The first indication information is pre-configured by network configuration and/or protocol.
The device according to claim 10, wherein the manner of carrying the target information includes one or more of the following:

Indicating the target information by using a first LCID, where the first LCID is used to identify a first logical channel, and the first logical channel is used to transmit the PUSCH of MSG3 and/or MSGA of the terminal;

Use the first MAC CE to carry the target information; wherein, the corresponding MAC subheader of the first MAC CE includes the first LCID;

Use the first RRC message to carry the target information; wherein the MAC subheader corresponding to the MAC SDU containing the first RRC message includes the first LCID.
A terminal, comprising: a processor, a memory, and a program stored on the memory and operable on the processor, when the program is executed by the processor, any one of claims 1 to 9 is realized The steps of the method.
A readable storage medium storing programs or instructions on the readable storage medium, and implementing the steps of the method according to any one of claims 1 to 9 when the programs or instructions are executed by a processor.
A chip, comprising a processor and a communication interface, the communication interface is coupled to the processor, the processor is used to run programs or instructions to implement the method according to any one of claims 1 to 9.
A computer program product, the computer program product is stored in a non-volatile storage medium, and the computer program product is executed by at least one processor to implement the method according to any one of claims 1-9.
A communication device configured to perform the method according to any one of claims 1-9.