Method and device for reporting early auxiliary information

Abstract

The embodiment of the invention provides a method and a device for reporting early auxiliary information. The method comprises the following steps: receiving configuration information related to an early auxiliary information report from a base station; and according to the configuration information, a protocol data unit MAC PDU of a media access control layer is sent to the base station, and the MAC PDU comprises a specific MAC sub-header carrying an early auxiliary information field. According to the embodiment of the invention, the specific MAC sub-header can be set to provide the early auxiliary information for the base station, and the early auxiliary information is transmitted through the physical uplink shared channel on the premise of not increasing the size of the message, so that the problem that the auxiliary information is indicated in the random access process by using the logic channel identifier in the related technology can be solved. The number of coding points of logic channel identification is limited, and the flexibility is poor.

Description

Technical Field

[0001] The present application relates to the field of communications, and in particular, to a method and device for reporting early auxiliary information. Background Art

[0002] In current wireless communication systems, after being connected to a network, a user equipment (UE) reports auxiliary information (such as UE capabilities) to the network to help better schedule the UE.

[0003] On the one hand, although UE capability reporting usually occurs after establishing a connection to the network, it is sometimes necessary to report capabilities during the Random Access Channel (RACH) process. For example, in a non-terrestrial network (NTN), the network needs to know whether the UE supports automatic retransmission of Msg4 or MsgB, so it is necessary to specify that the UE report this capability before scheduling Msg4 or MsgB, that is, to transmit this information in the Msg3 or MsgA payload. On the other hand, since the size of the Physical Uplink Shared Channel (PUSCH) message will affect the overall coverage of the Random Access Channel (RACH), the UE needs to transmit UE capability information through PUSCH without increasing the size of a single message.

[0004] In the related art, a logical channel identifier (LCID) can be used in Msg3 / MsgA to indicate auxiliary information, but this method also has many defects: First, according to the current standards formulated by the 3rd Generation Partnership Project (3GPP), the number of code points reserved for LCID is limited. As the requirements for UE to report auxiliary information during the RACH process continue to increase, the remaining LCID code points may be exhausted quickly. Second, since LCID contains two different sizes of common control channels (CCCH), in order to distinguish between these two situations, two LCIDs are needed to indicate one type of auxiliary information. Third, considering that multiple types of auxiliary information may need to be indicated in Msg3 / MsgA in the future, in order to support the combination of all auxiliary information, assuming that there are x types of auxiliary information, up to 2^x-1 additional code points may be required for indication, which will accelerate the consumption of the remaining LCID code points. The flexibility is poor when indicating the combination of multiple groups of auxiliary information.

[0005] In summary, there is no good solution to the problem that the existing logical channel identification bits are used in the related art to indicate auxiliary information during the random access process, the number of coding points of the logical channel identification bits is limited, and the flexibility is poor. Summary of the invention

[0006] The embodiments of the present application provide a method and device for reporting early auxiliary information, so as to at least solve the problem in the related art of using a logical channel identifier to indicate auxiliary information during a random access process, and the number of coding points of the logical channel identifier is limited and the flexibility is poor.

[0007] According to one embodiment of the present application, a method for reporting early auxiliary information is provided, which is applied to a terminal, and the method includes: receiving configuration information related to early auxiliary information reporting from a base station; sending a protocol data unit MAC PDU of a media access control layer to the base station according to the configuration information, wherein the MAC PDU includes a specific MAC subheader carrying an early auxiliary information field.

[0008] According to another embodiment of the present application, a method for reporting early auxiliary information is provided, which is applied to a base station, and the method includes: sending configuration information related to early auxiliary information reporting to a terminal; receiving a media access control protocol data unit MAC PDU sent by the terminal according to the configuration information, wherein the MAC PDU includes a specific MAC subheader carrying an early auxiliary information field.

[0009] According to an embodiment of the present application, a method for reporting early assistance information is provided, which is applied to a terminal, and includes: receiving configuration information related to early assistance information reporting from a base station; and sending an early assistance message carrying early assistance information to the base station according to the configuration information.

[0010] According to another embodiment of the present application, a method for reporting early auxiliary information is also provided, which is applied to a base station, and the method includes: sending configuration information related to early auxiliary information reporting to a terminal; receiving an early auxiliary message carrying early auxiliary information sent by the terminal according to the configuration information.

[0011] According to another embodiment of the present application, a terminal is provided for receiving configuration information related to early auxiliary information reporting from a base station; and sending a protocol data unit MAC PDU of a media access control layer to the base station according to the configuration information, wherein the MAC PDU includes a specific MAC subheader carrying an early auxiliary information field.

[0012] According to another embodiment of the present application, a base station is provided for sending configuration information related to early auxiliary information reporting to a terminal; receiving a media access control protocol data unit MAC PDU sent by the terminal according to the configuration information, wherein the MAC PDU includes a specific MAC subheader carrying an early auxiliary information field.

[0013] According to another embodiment of the present application, a terminal is provided, which is used to receive configuration information related to early assistance information reporting from a base station; and send an early assistance message carrying early assistance information to the base station according to the configuration information.

[0014] According to another embodiment of the present application, a base station is provided, which is used to send configuration information related to early assistance information reporting to a terminal; and receive an early assistance message carrying early assistance information sent by the terminal according to the configuration information.

[0015] According to another embodiment of the present application, a computer-readable storage medium is provided, in which a computer program is stored, wherein the computer program executes the steps of any of the above method embodiments when executed by a processor.

[0016] According to another embodiment of the present application, an electronic device is provided, including a memory and a processor, wherein a computer program is stored in the memory, and the processor is configured to run the computer program to execute the steps in any one of the above method embodiments.

[0017] Through the embodiments of the present application, a specific MAC subheader can be set to provide early auxiliary information to the base station, such as indicating whether the terminal can support each feature in the auxiliary information. The early auxiliary information is transmitted through the PUSCH without increasing the message size, thereby solving the problem in the related technology of using logical channel identifiers to indicate auxiliary information during random access, and the limited number of coding points of logical channel identifiers and poor flexibility. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] Figure 1 is a hardware structure block diagram of a method for reporting early auxiliary information according to an embodiment of the present application;

[0019] Figure 2 is a flowchart (I) of a method for reporting early auxiliary information according to an embodiment of the present application;

[0020] Figure 3 is a flowchart (II) of a method for reporting early auxiliary information according to an embodiment of the present application;

[0021] Figure 4 is a flowchart of a four-step contention-based random access process according to an embodiment of the present application;

[0022] Figure 5 is a flowchart of a two-step contention-based random access process according to an embodiment of the present application;

[0023] Figure 6 This is a schematic diagram of the structure of a specific MAC subheader according to an embodiment of the present application (I);

[0024] Figure 7 This is a structural schematic diagram of a specific MAC subheader according to an embodiment of the present application (II);

[0025] Figure 8 This is a structural diagram of a specific MAC subheader according to an embodiment of the present application (III);

[0026] Fig. 9 This is a structural diagram of a specific MAC subheader according to an embodiment of the present application (IV);

[0027] Fig.10 This is a structural diagram of a specific MAC subheader according to an embodiment of the present application (V);

[0028] Fig.11 6 is a structural diagram of a specific MAC subheader according to an embodiment of the present application;

[0029] Fig.12 is a flowchart of a method for reporting early auxiliary information according to an embodiment of the present application (III);

[0030] Fig.13 is a flowchart of a 4-step RACH according to an embodiment of the present application;

[0031] Fig.14 is a flowchart of a 2-step RACH according to an embodiment of the present application;

[0032] Fig.15 is a flowchart of a 4-step RACH according to another embodiment of the present application;

[0033] Fig.16 It is a schematic diagram of the structure of the MAC subheader of the MAC CE identifying the C-RNTI according to an embodiment of the present application. DETAILED DESCRIPTION

[0034] The embodiments of the present application will be described in detail below with reference to the accompanying drawings and in combination with the embodiments.

[0035] It should be noted that the terms "first", "second", etc. in the specification and claims of this application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence.

[0036] The method embodiments provided in the embodiments of the present application can be executed in a mobile terminal, a computer terminal or a similar computing device. Taking running on a mobile terminal as an example, Figure 1 is a hardware structure block diagram of the method for reporting early auxiliary information in an embodiment of the present application, such as Figure 1 As shown, the hardware board may include one or more ( Figure 1 Only one is shown in the figure) a processor 12 (the processor 12 may include but is not limited to a processing device such as a microprocessor MCU or a programmable logic device) and a memory 14 for storing data, wherein the mobile terminal may also include a transmission device 16 for communication functions and an input and output device 18. It can be understood by those skilled in the art that Figure 1 The structure shown is only for illustration and does not limit the structure of the mobile terminal. Figure 1 More or fewer components as shown, or with Figure 1 Different configurations shown.

[0037] The memory 14 can be used to store computer programs, for example, software programs and modules of application software, such as the computer program corresponding to the method for reporting early auxiliary information in the embodiment of the present application. The processor 12 executes various functional applications and the method for reporting early auxiliary information by running the computer program stored in the memory 14, that is, to implement the above method. The memory 14 may include a high-speed random access memory, and may also include a non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some embodiments, the memory 14 may further include a memory remotely arranged relative to the processor 12, and these remote memories may be connected to the mobile terminal via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0038] The transmission device 16 is used to receive or send data via a network. The specific example of the above network may include a wireless network provided by a communication provider. In one example, the transmission device 16 includes a network adapter (Network Interface Controller, referred to as NIC), which can be connected to other network devices through a base station so as to communicate with the Internet. In one example, the transmission device 16 can be a radio frequency (Radio Frequency, referred to as RF) module, which is used to communicate with the Internet wirelessly.

[0039] In one embodiment of the present application, a method for reporting early auxiliary information is provided, which is applied to a terminal. Figure 2 is a flow chart (I) of a method for reporting early auxiliary information according to an embodiment of the present application, such as Figure 2As shown, the process includes the following steps:

[0040] Step S202, receiving configuration information related to early assistance information reporting from a base station;

[0041] Step S204: sending a media access control layer protocol data unit MAC PDU to the base station according to the configuration information, wherein the MAC PDU includes a specific MAC subheader carrying an early auxiliary information field.

[0042] In an embodiment of the present application, a specific MAC subheader for indicating early auxiliary information is designed through the above steps S202 to S204. The terminal can set the fields in the specific MAC subheader based on the configuration of the network according to whether the terminal supports each feature, thereby solving the problem in the related art of using logical channel identifiers to indicate auxiliary information during random access, and the limited number of coding points of logical channel identifiers and poor flexibility.

[0043] In some embodiments, the MAC subheader is used to identify a Common Control Channel (CCCH) message, which is sent by a User Equipment (UE) to a base station via a Physical Uplink Shared Channel (PUSCH). The UE can set a field indicating whether the UE supports each feature (i.e., an early auxiliary information field) in the MAC subheader that identifies the CCCH message.

[0044] In some embodiments, a specific MAC subheader carrying early assistance information may also be used to identify a DCCH message.

[0045] In an embodiment of the present application, the base station needs to send configuration information to the UE so that the UE knows that the base station can decode the specific MAC subheader used to indicate early auxiliary information, or the base station allows the UE to use the specific MAC subheader to identify the CCCH message, wherein the specific MAC subheader contains an early auxiliary information field (such as one or more UE capability-related information).

[0046] In this embodiment, the user equipment is a terminal, including but not limited to a mobile terminal, a computer terminal, etc.

[0047] In some embodiments, the early assistance information may include information related to one or more UE capabilities. The UE capability indicates whether the UE supports a feature or a function, and the present application does not limit the specific content of the early assistance information.

[0048] Furthermore, the early auxiliary information may also be replaced by other terms, such as early terminal information, early terminal identification, early terminal indication, etc., and this application does not impose any limitation on this.

[0049] In some embodiments, the early assistance information may include, but is not limited to, any one or any combination of the following information:

[0050] Indication information used to indicate whether the UE supports or requests automatic retransmission of the PUCCH of Msg4 HARQ-ACK;

[0051] Indication information used to indicate whether the UE is a UE with reduced capabilities (e.g., RedCap UE);

[0052] Indication information used to indicate whether the UE is a UE with enhanced reduction capability (e.g., eRedCap UE);

[0053] Indication information used to indicate whether UE capabilities are temporarily restricted;

[0054] Indication information used to indicate whether the UE supports a specific UE capability;

[0055] Indication information used to indicate that the RACH process is triggered by a specific reason;

[0056] Indication information used to indicate that the initial access process is triggered due to a specific reason.

[0057] In this embodiment, Msg4 is the fourth step message in the four-step random access process, HARQ-ACK is a hybrid automatic repeat request confirmation message (Hybrid Automatic Repeat Request-ACKnowledgement, referred to as HARQ-ACK), and PUCCH is a physical uplink control channel (Physical Uplink Control CHannel, referred to as PUCCH).

[0058] In an exemplary embodiment, indicating whether the UE capability is temporarily restricted may be used in a scenario where the UE supports multiple SIMs, in which the UE capability (such as supported frequency band combinations, capability to support dual connectivity) may be temporarily restricted under some conditions. For example, when the UE has established a Radio Resource Control (RRC) connection with NW1 in one SIM card, and the UE is using another SIM card to establish or restore an RRC connection with NW2, the capability of a MUSIM UE supporting multiple subscriber identity modules (MUSIM) may be temporarily restricted.

[0059] In some embodiments, the configuration information includes: an explicit indication and / or an implicit indication for indicating whether to enable the specific MAC subheader.

[0060] In an exemplary embodiment, the explicit indication may include an explicit indication for indicating whether the UE is allowed to use the above-mentioned specific MAC subheader.

[0061] In some embodiments, the implicit indication includes at least one of the following:

[0062] Msg4 Hybrid Automatic Repeat Request Confirmation HARQ-ACK automatic repeat configuration information;

[0063] Configuration information related to temporary capability restrictions of multi-user identity card MUSIM terminals;

[0064] Reduced capability RedCap terminal configuration information;

[0065] Enhanced the ability to reduce eRedCap terminal configuration information;

[0066] Random access channel RACH resource configuration information dedicated to early auxiliary information reporting;

[0067] The mapping relationship between specific MAC subheader formats and RACH resources;

[0068] Terminal capability information;

[0069] Random access process trigger information (such as trigger reason);

[0070] Initial access process trigger information (such as trigger reason, purpose of initiating the process).

[0071] In an exemplary embodiment, explicit indication and implicit indication may be used in combination, wherein the explicit indication may be used to enable a specific MAC subheader, and the implicit indication may be used to assist the UE in deciding the content of related early assistance information reported in the specific MAC subheader.

[0072] In an exemplary embodiment, the automatic retransmission configuration information may include at least one of the following:

[0073] The automatic retransmission enabling indication is used to indicate whether the UE is allowed to send an early indication to support or request automatic retransmission of HARQ-ACK. Exemplarily, sending the early indication may be limited to during the random access process.

[0074] The repetition factor of automatic retransmission is used to indicate the number of automatic retransmissions of the confirmation message that the UE can choose when sending HARQ-ACK. Exemplarily, the candidate values ​​of the repetition factor of automatic retransmission can be {1, 2, 4, 8}.

[0075] In an exemplary embodiment, the temporary capability restriction information of the MUSIM UE may be applied to all RRC states, or may be limited to certain RRC procedures, for example, during the RRC connection establishment or RRC connection recovery process.

[0076] In an exemplary embodiment, reduced capability (RedCap) is a bandwidth reduction technology, and the RedCap terminal configuration information may include at least one of the following:

[0077] RedCapUE indication, used to indicate whether the RedCapUE can use an RRC message during the RACH process to indicate that it is a RedCapUE. The RRC message may be specially designed for providing early assistance information during the RACH process.

[0078] The cell barring indication is used to indicate whether the cell is barred from access by RedCap UEs with 1 or 2 Rx bands. Alternatively, it is used to indicate whether the cell is barred from access by RedCap UEs with 1 or 2 Rx bands.

[0079] The half-duplex indication is used to indicate whether the current cell supports half-duplex frequency division duplex (Frequency Division Duplex / Duplexing, referred to as FDD) RedCapUE indication.

[0080] In an exemplary embodiment, Enhanced Reduced Capability (eRedCap) is an enhanced bandwidth reduction technology, and the eRedCap terminal configuration information may include at least one of the following:

[0081] eRedCapUE indication, used to indicate whether the eRedCapUE can indicate that it is an eRedCapUE during the RACH procedure.

[0082] The cell barring indication is used to indicate whether the cell is barred from being used by eRedCapUEs with 1 or 2 Rx bands. Alternatively, it is used to indicate whether the cell is barred from being accessed by eRedCapUEs with 1 or 2 Rx bands.

[0083] Half-duplex indication is used to indicate whether the current cell supports half-duplex FDD eRedCapUE.

[0084] In an embodiment of the present application, through the implicit indication in any of the above embodiments, the terminal can be implicitly notified that the cell allows the UE to use a specific MAC subheader related to early auxiliary information to identify the service data unit (Media Access Control Service Data Unit, MAC SDU for short) of the media access control layer.

[0085] In some embodiments, the configuration information may be cell-based configuration information, RACH resource-based configuration information, or RACH resource set-based configuration information (such as RACH resources associated with a control unit feature combination), that is, configuration is performed at a cell granularity, or configuration information is provided according to different RACH resources, or configuration information is provided according to different RACH resource sets.

[0086] In some embodiments, the UE selects a corresponding RACH resource according to the triggering event based on its own capabilities (such as functional features supported by the UE) and / or the triggering cause of this RACH process.

[0087] In some embodiments, step S202 receives configuration information related to early assistance information reporting from the base station, including at least one of the following:

[0088] Receiving system information carrying the configuration information from the base station, wherein the system information includes at least one SIB1 message or at least one system information block (SIBx), where x is a number of the system information block, and if x is 22, it refers to system information block SIB22;

[0089] receiving a broadcast message carrying the configuration information from the base station;

[0090] receiving a multicast message carrying the configuration information from the base station;

[0091] receiving a radio resource control RRC signaling carrying the configuration information from the base station;

[0092] receiving a non-access stratum NAS message carrying the configuration information from the base station;

[0093] receiving a paging message carrying the configuration information from the base station;

[0094] receiving a short message carrying the configuration information from the base station;

[0095] receiving, from the base station, a MAC layer signaling carrying the configuration information;

[0096] A physical layer signaling carrying the configuration information is received from the base station.

[0097] In an exemplary embodiment, when using system information (SI) to transmit configuration information, it can be one or more SIB1 messages or SIBx information elements (IE), where x in SIBxIE is a positive integer starting from 2, and SIBxIE can be one or more existing system information blocks (SIBs) (e.g., SIB2 to SIB21) or an introduced new SIB (e.g., SIB22).

[0098] In an exemplary embodiment, a common SIBx may be used to indicate one or more indications in the above embodiments, wherein x in SIBx may be any positive integer, such as SIB1, SIB22.

[0099] In another embodiment, multiple different system information (one or more of SIB1 messages or SIBxIEs) may be used to indicate the configuration information in any of the above embodiments. Exemplarily, SIB1 may include configuration information for RedCapUE, configuration information for eRedCapUE, configuration information for MUSIM terminals, or explicit indications to enable the terminal to use a specific MAC subheader carrying an early assistance information field. Exemplarily, SIB19 may include automatic retransmission configuration information for HARQ-ACK.

[0100] In some embodiments, the specific MAC subheader includes at least one of the following contents:

[0101] The flag bit of the specific MAC subheader;

[0102] The message type field of the common control channel CCCH message;

[0103] The early auxiliary information field.

[0104] In an exemplary embodiment, the flag bit is used to distinguish a specific MAC subheader carrying an early auxiliary information field from other common MAC subheaders not carrying an early auxiliary information field.

[0105] In an exemplary embodiment, the flag bit can be a one-bit indication field, such as a C_flag field, used to indicate that the MAC subheader contains an early auxiliary information field. Exemplarily, the C_flag field is set to 1 to indicate that the MAC subheader contains an early auxiliary information field, and the C_flag field is set to 0 to indicate that the MAC subheader does not contain an early auxiliary information field. The opposite is also possible, and the present application does not limit this. In some embodiments, this field can only be placed in the first position on the left to distinguish it from the subheader used to identify a MAC sub-PDU carrying an indefinite length.

[0106] In some embodiments, the message type of the CCCH message includes at least one of the following and possible combinations:

[0107] 48-bit CCCH or 64-bit CCCH1;

[0108] CCCH for reduced capability RedCap terminals or CCCH for non-RedCap terminals.

[0109] In an exemplary embodiment, CCCH messages may be classified differently, for example, they may be classified into 48-bit CCCH and 64-bit CCCH1 according to the message size. Alternatively, CCCH messages for RedCapUE and CCCH messages for non-RedCapUE may be classified according to whether the UE supports RedCap, wherein RedCapUE refers to a terminal supporting RedCap and non-RedCapUE refers to a terminal not supporting RedCap.

[0110] In an exemplary embodiment, the message type of the CCCH message may be a one-bit indication field. Exemplarily, the field is set to 0 to indicate that the CCCH category is CCCH, and the field is set to 1 to indicate that the CCCH category is CCCH1. The reverse is also possible, and the present application does not limit this.

[0111] In an exemplary embodiment, the message type of the CCCH message can be a two-bit indication field to allow the CCCH messages for ReCapUE and non-RedCapUE to be distinguished and the CCCH message size. The two-bit indication field can indicate 4 values ​​{00, 01, 10 and 11}, where each value can be mapped one-to-one to {CCCH of non-RedCapUE, CCCH1 of non-RedCapUE, CCCH of RedCapUE and CCCH1 of RedCapUE}. The mapping rules can be as shown in Table 1 below, but the present application is not limited thereto.

[0112] Table 1:

[0113] Message type of CCCH message (2 bits) explain 00 CCCH of non-RedCap UE 01 CCCH1 for non-RedCap UE 10 CCCH of RedCap UE 11 CCCH1 by RedCap UE

[0114] In some embodiments, the indication method of the early auxiliary information field includes at least one of the following:

[0115] The early auxiliary information field includes at least one bit of information, wherein each bit of information represents one early auxiliary information;

[0116] The value of the early assistance information field is determined by a formula of the early assistance information field including at least one subfield, wherein each of the subfields represents one of the early assistance information, and the formula of the early assistance information field is determined based on the value of the at least one subfield and the number of candidate values ​​of each of the subfields;

[0117] The early assistance information field indicates a logical channel identification index, wherein the logical channel identification index is used to indicate one or more of the early assistance information.

[0118] In some embodiments, the early auxiliary information field may further include one or more reserved bits for future expansion, and the value of each reserved bit is 0.

[0119] In some embodiments, the early assistance information field may include n bits, each bit identifying an early assistance information (such as information related to UE capabilities). Exemplarily, each bit may indicate whether the UE supports a feature or function.

[0120] In an embodiment of the present application, after the network side successfully receives the information reported by the UE, it can reversely infer the value of each subfield (each feature) based on different indication methods and the value of the corresponding early auxiliary information field, and then infer the content of the early auxiliary information reported by the UE, thereby achieving the purpose of indicating the early auxiliary information through the MAC subheader.

[0121] In some embodiments, the formula for the early assistance information field includes:

[0122] The value of the early auxiliary information field = the value of the first subfield + the value of the second subfield * the number of candidate values ​​of the first subfield + the value of the third subfield * (the number of candidate values ​​of the second subfield + the number of candidate values ​​of the first subfield) + ... + the value of the nth subfield * (the number of candidate values ​​of the n-1th subfield + ... + the number of candidate values ​​of the second subfield + the number of candidate values ​​of the first subfield)), where n is a positive integer.

[0123] In some embodiments, the early assistance information includes at least one of the following:

[0124] Indication information used to indicate whether the terminal supports or requests automatic retransmission of the physical uplink control channel PUCCH of Msg4 hybrid automatic repeat request confirmation HARQ-ACK;

[0125] Indication information used to indicate whether the terminal capability of the terminal is temporarily restricted;

[0126] Indication information used to indicate whether the terminal supports reduced capability RedCap;

[0127] Indication information used to indicate whether the terminal supports enhanced reduction capability eRedCap.

[0128] In some embodiments, the MAC PDU includes a plurality of MAC sub-PDUs, wherein each of the MAC sub-PDUs is composed of one of the following:

[0129] MAC subheader;

[0130] MAC subheader and media access control layer service data unit MAC SDU;

[0131] MAC subheader and control unit MAC CE of the media access control layer;

[0132] MAC subheader and padding.

[0133] In this embodiment, when early assistance information needs to be transmitted, any MAC subheader in the MAC PDU may be a specific MAC subheader carrying the early assistance information field.

[0134] In some embodiments, the specific MAC subheader may be a MAC subheader for identifying a service data unit (SDU) of a media access control layer (Media Access Control, MAC for short), and is sent in a common control logical channel.

[0135] In some embodiments, the specific MAC subheader may be a MAC subheader for identifying a control element (CE) of a media access control layer (MAC) for early auxiliary information reporting.

[0136] In some embodiments, the MAC CE used for early assistance information reporting may carry only the specific MAC subheader but not the payload.

[0137] In some embodiments, the MAC subheader carries an indication for identifying a MAC CE for early assistance information reporting. In this case, the early assistance information field may be included in the payload of the MAC sub-PDU, ie, the content of the MAC CE, rather than in the MAC subheader.

[0138] In some embodiments, the MAC subheader carries an indication for identifying a MAC SDU for early assistance information reporting. In this case, the early assistance information field may be included in the payload of the MAC sub-PDU, ie, the content of the MAC SDU, rather than in the MAC subheader.

[0139] In some embodiments, sending a media access control protocol data unit MAC PDU to the base station according to the configuration information includes:

[0140] In the third step of the four-step random access (such as Msg3), or in the first step of the two-step random access (such as in the payload of MsgA), a media access control protocol data unit MAC PDU is sent to the base station according to the configuration information.

[0141] Through the embodiments of the present application, the UE can set a specific MAC subheader (such as a MAC subheader used to identify the CCCH message) to indicate whether the terminal can support each feature in the auxiliary information, and transmit early auxiliary information through the PUSCH without increasing the message size, thereby solving the problem in the related technology of using logical channel identifiers to indicate auxiliary information during random access, and the limited number of coding points of logical channel identifiers and poor flexibility.

[0142] According to another embodiment of the present application, a method for reporting early auxiliary information is also provided, which is applied to a base station.

[0143] Figure 3 is a flow chart (II) of a method for reporting early auxiliary information according to an embodiment of the present application, such as Figure 3 As shown, the method comprises the following steps:

[0144] Step S302, sending configuration information related to early auxiliary information reporting to the terminal;

[0145] Step S304: receiving a media access control protocol data unit MAC PDU sent by the terminal according to the configuration information, wherein the MAC PDU includes a specific MAC subheader carrying an early auxiliary information field.

[0146] In some embodiments, the UE may send a CCCH message in an uplink transmission during a random access channel (RACH) procedure, including a specific MAC subheader carrying an early assistance information field.

[0147] In an exemplary embodiment, the CCCH message may specifically include a payload in Msg3 or MsgA. The following is described in conjunction with two random access procedures based on contention. However, the present application is not limited thereto, and the technical solution in the present application may also be implemented in a non-contention random access procedure.

[0148] Figure 4 is a flowchart of a four-step contention-based random access process according to an embodiment of the present application, such as Figure 4 As shown, the process includes the following steps:

[0149] Step 0: The UE receives configuration information related to early assistance information reporting from the base station;

[0150] Step 1: The UE sends a random access preamble (Msg1) to the base station;

[0151] Step 2: The UE receives a random access response (Msg2) from the base station;

[0152] Step 3: UE sends Msg3 to the base station based on network scheduling;

[0153] Step 4: The UE receives Msg4 from the base station for contention resolution.

[0154] In this embodiment, Msg3 includes a CCCH message, and the CCCH message in Msg3 can be identified through the MAC subheader.

[0155] In this embodiment, a specific MAC subheader carrying an early auxiliary information field is provided to implement reporting of early auxiliary information, such as indicating whether the terminal supports certain capabilities or functions.

[0156] In some embodiments, the network (Network, NW for short) configuration of the base station to the terminal includes RACH configuration in addition to the configuration information related to the early auxiliary information report in step 0. The RACH configuration can be sent together or separately with the configuration information for early auxiliary information reporting, and this application does not limit this. In some embodiments, NW can be used to refer to a base station, a core network, some network elements of a base station (such as a distributed unit, a centralized unit), or a functional entity in the network, such as an access and mobility management function (Access and Mobility management Function, AMF), operation and maintenance management (Operation Administration and Maintenance, OAM), etc.

[0157] Figure 5 is a flowchart of a two-step contention-based random access process according to an embodiment of the present application, such as Figure 5 As shown, the process includes the following steps:

[0158] Step 0: The UE receives configuration information related to early assistance information reporting from the base station;

[0159] Step A: The UE sends a random access preamble and a PUSCH payload (MsgA) containing a CCCH message to the base station;

[0160] Step B: The UE receives MsgB from the base station for contention resolution.

[0161] In this embodiment, the CCCH message included in MsgA may be identified by the MAC subheader.

[0162] In this embodiment, a specific MAC subheader carrying an early auxiliary information field is provided to implement reporting of early auxiliary information, such as indicating whether the terminal supports certain capabilities or functions.

[0163] In some embodiments, the NW configuration further includes a RACH configuration, and the RACH configuration may be sent together with or separately from the configuration information for early auxiliary information reporting, which is not limited in the present application.

[0164] In an exemplary embodiment of the present application, the base station may send configuration information to the terminal via system information SIB1.

[0165] In this embodiment, the structure of the system information SIB1 is as follows:

[0166]

[0167]

[0168] In this embodiment, SIB1-vnnmm refers to SIB1 defined in the standard. Wherein, v represents the standard version implemented, nn represents the version number of the released standard, and mm represents the mmth revision of the nnth version, that is, the mmth sub-version of the nnth version. Exemplarily, SIB1-v1800 refers to SIB1 based on the 18th version 00th revision standard.

[0169] In this embodiment, the new control unit subheaderForUECapAllowed-rnn (subheader for allowing UE capabilities) is a new field to be introduced in a future standard version.

[0170] In this embodiment, the existence of the subheaderForUECapAllowed field is used to indicate that the UE is allowed to use a specific MAC subheader containing an early assistance information field, wherein the early assistance information field is a field related to early assistance information specified in the standard TS38.321.

[0171] In this embodiment, the subheaderForUECapAllowed field is only an example, and other examples may also be earlyUEIndicationAllowed, etc. This application does not limit the field name of the configuration information.

[0172] In an exemplary embodiment of the present application, the early assistance information field in a specific MAC subheader may include n bits, each bit of which may indicate whether the UE supports a feature or function (equivalent to the above-mentioned bit information).

[0173] In an exemplary embodiment, the feature is whether the UE supports or requests automatic retransmission of PUCCH for Msg4HARQ-ACK. A one-bit subfield (such as the pucchRep field) can be used in the early auxiliary information field to indicate the UE. Exemplarily, a subfield value of 0 indicates that the UE does not support or request automatic retransmission of PUCCH for Msg4HARQ-ACK, and a subfield value of 1 indicates that the UE can support or request automatic retransmission of PUCCH for Msg4HARQ-ACK. The opposite is also true, and this application does not limit this.

[0174] In an exemplary embodiment, the feature is whether the UE is a UE with reduced capabilities (such as a RedCap UE). A one-bit subfield (such as a RedCap field) can be used in the early auxiliary information field to indicate the UE. Exemplarily, a subfield value of 0 indicates that the UE is not a RedCap UE, and a subfield value of 1 indicates that the UE is a RedCap UE. The opposite is also possible, and the present application does not limit this.

[0175] In some embodiments, when the base station or the network has indicated that the current cell supports RedCapUE, the indication is optional.

[0176] In an exemplary embodiment, the feature is whether the UE is a UE with enhanced reduction capability (such as an eRedCap UE). A one-bit subfield (such as an eRedCap field) can be used in the early auxiliary information field to indicate the UE. Exemplarily, a subfield value of 0 indicates that the UE is not an eRedCap UE, and a subfield value of 1 indicates that the UE is an eRedCap UE. The opposite is also possible, and the present application does not limit this.

[0177] In some embodiments, when the base station or the network has indicated that the current cell supports eRedCapUE, the indication is optional.

[0178] In an exemplary embodiment, the feature is whether the UE capability (such as MUSIM UE capability) is temporarily restricted. A one-bit subfield may be used in the early auxiliary information field to indicate the UE. Exemplarily, a subfield value of 0 indicates that the UE capability (such as MUSIM UE capability) is not restricted, and a subfield value of 1 indicates that the UE capability (such as MUSIM UE capability) is temporarily restricted. The reverse is also possible, and the present application does not limit this.

[0179] In an exemplary embodiment, a subfield value of 0 indicates that the temporary restriction of UE capability (such as MUSIM UE capability) is removed, and a subfield value of 1 indicates that the UE capability (such as MUSIM UE capability) is temporarily restricted. The reverse is also possible, and the present application does not limit this.

[0180] In some embodiments, when the base station or the network has indicated whether the UE is temporarily restricted in the current cell, the indication is optional.

[0181] In an exemplary embodiment of the present application, the value of the early auxiliary information field may be determined by a formula determined based on the values ​​of n subfields and the number of candidate values ​​for each subfield.

[0182] In an exemplary embodiment, assuming that the early assistance information field is m bits, the field may have a maximum value of 2^m if the initial value starts from 1, or may have a maximum value of 2^m-1 if the initial value is zero.

[0183] In an exemplary embodiment, the formula for an early assistance information field having n subfields is:

[0184] The value of the early auxiliary information field=sub_field_1+sub_field_2*numOfsub_field_1+sub_field_3*(numOfsub_field_2+numOfsub_field_1)+...+sub_field_n*(numOfsub_field_n-1+...+numOfsub_field_2+numOfsub_field_1).

[0185] Among them, sub_field_1 is the value of the first subfield associated with the first early auxiliary information, and the number of candidate values ​​of the first subfield is numOfsub_field_1; sub_field_2 is the value of the second subfield associated with the second early auxiliary information, and the number of candidate values ​​is numOfsub_field_2; and so on, sub_field_n-1 is the value of the n-1th subfield associated with the n-1th early auxiliary information, and the number of candidate values ​​is numOfsub_field_n-1; sub_field_n is the value of the nth subfield associated with the nth early auxiliary information, and the number of candidate values ​​is numOfsub_field_n.

[0186] In an exemplary embodiment, the early assistance information field includes the following three subfields related to UE capabilities:

[0187] The first subfield: device type, candidate values ​​are {0, 1, 2}, each value represents one of the device types {eRedCapUE, RedCapUE, and UE that is both non-RedCap and non-eRedCap}. For example, 0 represents a UE that is neither eRedCap nor RedCapUE, 1 represents RedCapUE, and 2 represents eRedCapUE. As long as each value is uniquely corresponding to each candidate device type, other corresponding relationships are also possible, and this application does not impose any restrictions on this.

[0188] Second subfield: MuSIM indication, indicating whether the capability of the MUSIM UE is temporarily restricted. The candidate value is 1 or 0. Exemplarily, the indication is set to 1 to indicate that the capability of the MUSIM UE is temporarily restricted, and the indication is set to 0 to indicate that the capability of the MUSIM UE is not temporarily restricted. Vice versa, this application does not limit this.

[0189] The third subfield: Msg4ACK automatic retransmission indication, indicating whether the UE supports or requests automatic retransmission for PUCCH of Msg4HARQ-ACK. For example, a value of 0 indicates that the UE does not support or request automatic retransmission for PUCCH of Msg4HARQ-ACK, and a value of 1 indicates that the UE can support or has requested automatic retransmission for PUCCH of Msg4HARQ-ACK. Vice versa, this application does not limit this.

[0190] In this embodiment, based on the above three subfields, the formula of the early auxiliary information field may be:

[0191] The value of the early assistance information field = the value of the device type + the value indicated by MuSIM*3 (the number of candidate values ​​for the device type) + the value indicated by Msg4ACK automatic retransmission*3 (the number of candidate values ​​for the device type)*2 (the number of candidate values ​​indicated by MuSIM).

[0192] The embodiment of the present application does not limit the order of the subfields, as long as the final equation follows the above formula of the early auxiliary information field with n subfields.

[0193] In an exemplary embodiment of the present application, the early assistance information field may also indicate one or more early assistance information through a logical channel identification index, wherein one logical channel identification index uniquely points to an early assistance information feature or an early assistance information feature combination.

[0194] In this embodiment, a logical channel identifier (LCID) field may be used, and the logical channel identifier field is specifically used to identify different logical channels for CCCH messages. Exemplarily, the field may be represented by LCID_CCCH.

[0195] In an exemplary embodiment, the message category of the CCCH message may include at least one of the following: CCCH1, CCCH or other CCCH. LCID_CCCH may have a fixed length of n bits, where n is a positive integer. LCID_CCCH may indicate an index corresponding to any value in the range from 0 to (2^n-1), and each index may be used to identify a logical channel type.

[0196] In an exemplary embodiment, each index may uniquely indicate any one or more combinations of the following UE capability information, and the UE capability information may include at least one of the following:

[0197] Whether the UE can or has requested automatic retransmission of the PUCCH for Msg4 HARQ-ACK;

[0198] Whether the UE is a UE with reduced capabilities (such as RedCapUE);

[0199] Whether the UE is a UE with enhanced reduction capability (such as eRedCapUE);

[0200] Whether the capabilities of the UE (such as MUSIM UE) are temporarily restricted.

[0201] In this embodiment, the above four types of UE capability information may be arbitrarily combined. For example, the UE may be a RedCapUE and support or request automatic retransmission of the PUCCH for Msg4 HARQ-ACK.

[0202] In an exemplary embodiment, it is assumed that the logical channel identification field is specifically used to identify different logical channels for CCCH messages, and an example is given in which the logical channel identification field has a length of 5 bits, as shown in Table 2 and Table 3.

[0203] Table 2:

[0204]

[0205] In Table 2, the message type field used to identify the CCCH message is included in a specific MAC subheader with a logical channel identification field, and is not represented by a logical channel identification. The message type field is one bit, with a value of 0 or 1, and the corresponding message type is CCCH or CCCH1. Exemplarily, a value of 0 indicates CCCH, and a value of 1 indicates CCCH1. Vice versa, this application does not limit this.

[0206] Table 3:

[0207]

[0208] In Table 3, the distinction between message categories (such as CCCH and CCCH1) of CCCH messages is indicated by the logical channel identification field, rather than using a separate field in the MAC subheader.

[0209] The unique mapping between the logical channel identification index / code point and the auxiliary information combination in Table 2 and Table 3 above is only an example, and other mapping modes are also possible, as long as each unique index / code point is only mapped to a unique auxiliary information or a unique auxiliary information combination, and this application does not limit this. The length of the logical channel identification field in the above example is only an example, and other field lengths are also possible (such as 6 bits), and this application does not limit this.

[0210] In other embodiments, one or more of all the fields in the above embodiments may alternatively be placed in the payload of the MAC SDU or as part of the MAC CE content. Exemplarily, in a MAC CE for early assistance information reporting, the content of the MAC CE is octet-aligned, that is, the length of the MAC CE is an integer number of bytes, each byte is 8 bits long, and the MAC CE may include an early assistance information field and at least one R bit, or it may include an early assistance information field, a CCCH message type field, and at least one R bit.

[0211] Some exemplary embodiments of a specific MAC subheader including an early assistance information field are listed below. In the following exemplary embodiments, the early assistance information discussed is UE capability related information, but other information may also be considered. The location of each field is also only an example and can be switched. The length of each field and the corresponding term are also exemplary and are not limited by this application.

[0212] In some embodiments, the MAC subheader may be a MAC subheader identifying a MAC CE for reporting early assistance information.

[0213] In one embodiment, the MAC CE for reporting the early assistance information may include only a MAC subheader (the payload of the MAC CE is 0 bytes).

[0214] In another embodiment, a specific MAC subheader may include an R / LCID field, and the early assistance information field in the above embodiment is included in the payload of the MAC (such as MAC CE). In this embodiment, an LCID index may be used to indicate that this is a MAC CE for early assistance information reporting.

[0215] In some embodiments, the specific MAC subheader may be a MAC subheader used to identify a MAC SDU containing a CCCH message.

[0216] In one embodiment of the present application, an example of a specific MAC subheader including an early auxiliary information field calculated based on the equation is also provided. The position and length of the fields given in the examples of the present invention can be changed, and the present invention does not limit this.

[0217] In some embodiments, the MAC sub-PDU carrying early assistance information may include at least one of the following fields:

[0218] A field used to indicate a specific MAC subheader containing an early assistance information field. Exemplarily, this field is 1 bit, which is set to 1 to indicate that the MAC subheader contains a field for early assistance information reporting, otherwise it is set to zero. In some embodiments, this field can only be placed in the first position on the left to distinguish it from the subheader used to identify a MAC sub-PDU carrying an indefinite length.

[0219] A field used to indicate a specific MAC CE containing an early assistance information field. Exemplarily, this field is 1 bit, which is set to 1 to indicate that the MAC CE contains a field for early assistance information reporting, otherwise it is set to zero. In some embodiments, this field can only be placed in the first position on the left to distinguish it from the subheader used to identify a MAC sub-PDU carrying an indefinite length.

[0220] Used to indicate whether the message type of the CCCH message identified by the MAC subheader is CCCH (CCCH message with a size of 48 bits) or CCCH1 (CCCH message with a size of 64 bits). Exemplarily, the CCCH_ID field is set to 0 to indicate CCCH, or is set to 1 to indicate CCCH1. The reverse is also possible.

[0221] A field for indicating early auxiliary information, used to indicate early auxiliary information reported from the UE to the base station. In some embodiments, the value of this field may be determined by the formula of the early auxiliary information field described in the present invention. In other embodiments, this field may include one or more auxiliary information bits, wherein each auxiliary information bit is used to indicate a specific auxiliary information, such as whether the UE has the ability to support a certain feature or to indicate whether the UE requests a certain function. In some other embodiments, this field may be a logical channel identifier (Logical Channel IDentify, referred to as LCID) field, which is specifically used to identify different logical channels.

[0222] Reserved field. This field is 1 bit and its value is 0. In some embodiments, the size of the MAC sub-PDU is always an integer multiple of 8 bits. In order to meet this rule, some bits that currently have no specific functions can be set as reserved bits. Therefore, based on the length of the field in different embodiments, the number of reserved fields can be 0 to multiple. For example, an 8-bit specific length MAC subheader, assuming that it contains 1 bit to indicate a field of a specific MAC subheader containing an early auxiliary information field, contains a 6-bit early auxiliary information field, then in order to make up the 8 bits, the remaining bit can be set as a reserved bit.

[0223] Figure 6 1 is a schematic diagram of a structure of a specific MAC subheader according to an embodiment of the present application (I), such as Figure 6 As shown, the specific MAC subheader is one octet, i.e., 8 bits, and the specific MAC subheader includes the following fields:

[0224] C_flag field, CCCH_ID field, early auxiliary information field, reserved field (R).

[0225] C_flag field: This field is used to indicate a specific MAC subheader that contains an early assistance information field. Exemplarily, this field is 1 bit, which is set to 1 to indicate that the MAC subheader contains a field for early assistance information reporting, otherwise it is set to zero. In some embodiments, this field can only be placed in the first position on the left to distinguish it from the subheader used to identify a MAC sub-PDU carrying an indefinite length.

[0226] CCCH_ID field: This field is used to indicate whether the message type of the CCCH message identified by the MAC subheader is CCCH (CCCH message with a size of 48 bits) or CCCH1 (CCCH message with a size of 64 bits). Exemplarily, the CCCH_ID field is set to 0 to indicate CCCH, or, is set to 1 to indicate CCCH1. The reverse is also possible.

[0227] Early Assistance Information Field: This field is used to indicate that early assistance information is reported from the UE to the base station. Exemplarily, this field has a length of 5 bits. The information includes at least information related to the UE capability. The UE sets the value of the Early Assistance Information field based on the formula of the Early Assistance Information field with n subfields in the above embodiment. The following is an example assuming three capability-related fields:

[0228] Field 1: Device type, candidate values ​​are {0, 1, 2}, where each value represents one of the device types of {eRedCapUE, RedCapUE, and UE that is non-RedCap or non-eRedCap}. Exemplarily, 0 represents non-eRedCap and non-RedCapUE, 1 represents RedCapUE, 2 represents eRedCapUE, and the UE sets the value of this field based on its device type.

[0229] Field 2: MuSIM indication, used to indicate whether the capabilities of the MuSIM UE are temporarily restricted, and the value can be 1 or 0. Exemplarily, the UE sets the indication to 1 to indicate that the capabilities of the MuSIM UE are temporarily restricted, and sets the indication to 0 to indicate that the capabilities of the MUSIM UE are not temporarily restricted. Vice versa, this application does not limit this.

[0230] Field 3: Msg4AHRQ-ACK automatic retransmission indication, used to indicate whether the UE supports or requests automatic retransmission for PUCCH of Msg4HARQ-ACK. The indication may have a value of 1 or 0. Exemplarily, the UE sets the field to a value of 0 to indicate that the UE does not support or request automatic retransmission for PUCCH of Msg4HARQ-ACK, and the UE sets the field to a value of 1 to indicate that the UE supports or requests automatic retransmission for PUCCH of Msg4HARQ-ACK. Vice versa, this application does not limit this.

[0231] In this embodiment, based on the above three fields, the formula for calculating the value of the early auxiliary information field is as follows:

[0232] The value of the early assistance information field = device type + MuSIM indication*3 + Msg4ACK automatic retransmission indication*3*2.

[0233] The UE sets each field according to the field description given above. It should be noted that the order of the above fields can be switched arbitrarily as long as the final equation follows the above formula for the early auxiliary information field with n subfields.

[0234] In another exemplary embodiment, the field may have other lengths, such as 6 bits, and the present application does not limit this. It is sufficient to ensure that the final value obtained by the formula for calculating the value of the early auxiliary information field based on the subfield value according to the solution of the present invention does not exceed the maximum value that the field can indicate, such as (2^(the length of the field in bits)). It should be noted that when the field is 6 bits, the example Figure 5 The reserved bits in the header no longer appear to ensure that the MAC subheader length is one byte (ie, the subheader contains C_flag, CCCH_ID and early auxiliary information fields).

[0235] Reserved field (R), the value is 0.

[0236] Figure 7 : is a structural diagram of a specific MAC subheader of an embodiment of the present application (II), such as Figure 7 As shown, the specific MAC subheader is one octet, i.e., 8 bits, and the specific MAC subheader includes the following fields:

[0237] C_flag field, early auxiliary information field, reserved field (R).

[0238] Compared with the previous embodiment, the present embodiment is different in that the field in the MAC subheader does not carry a field indicating the CCCH type (such as CCCH_ID). In the present embodiment, the CCCH_ID used to indicate the CCCH message type can be regarded as a subfield used to calculate the value of the early auxiliary information field, and the rest is the same as the above embodiment.

[0239] In this embodiment, the early auxiliary information field may include the following subfields:

[0240] Field 1: CCCH message type (CCCH_Type): Select from the values ​​{0, 1}, where each value corresponds to one of the CCCH message types {CCCH, CCCH1}. Exemplarily, a value of 0 indicates a CCCH message (CCCH) of 48 bits in size, and a value of 1 indicates a CCCH message (CCCH1) of 64 bits in size. Vice versa, this application does not limit this.

[0241] Field 2: Device type, candidate values ​​are {0, 1, 2}, where each value represents one of the device types of {eRedCapUE, RedCapUE, and UE that is non-RedCap or non-eRedCap}. Exemplarily, 0 represents non-eRedCap and non-RedCapUE, 1 represents RedCapUE, 2 represents eRedCapUE, and the UE sets the value of this field based on its device type.

[0242] Field 3: MuSIM indication, used to indicate whether the capability of the MuSIM UE is temporarily restricted, and the value can be 1 or 0. Exemplarily, the UE sets the indication to 1 to indicate that the capability of the MuSIM UE is temporarily restricted, and sets the indication to 0 to indicate that the capability of the MUSIM UE is not temporarily restricted. Vice versa, this application does not limit this.

[0243] Field 4: Msg4ACK automatic retransmission indication, used to indicate whether the UE supports or requests automatic retransmission of PUCCH for Msg4HARQ-ACK. The indication may have a value of 1 or 0. Exemplarily, the UE sets the field to a value of 0 to indicate that the UE does not support or request automatic retransmission of PUCCH for Msg4HARQ-ACK, and the UE sets the field to a value of 1 to indicate that the UE supports or requests automatic retransmission of PUCCH for Msg4HARQ-ACK. Vice versa, this application does not limit this.

[0244] In this embodiment, the value of the early auxiliary information field including the above-mentioned subfields may be calculated based on the following formula:

[0245] The value of the early assistance information field = the value of the CCCH message type + the value of the device type*2+the value of the MuSIM indication*2*3+the value of the Msg4ACK automatic retransmission indication*2*3*2.

[0246] In an embodiment of the present application, an auxiliary information field can be added to a specific MAC subheader, and the value of the early auxiliary information field can be calculated based on the value of each subfield and through a formula. After the network side successfully receives the information reported by the UE, the value of each subfield can be reversed based on the value of the early auxiliary information field, and then the content of the early auxiliary information reported by the UE can be calculated, thereby achieving the purpose of indicating the early auxiliary information through the MAC subheader, and thus solving the problem of using a logical channel identifier to indicate auxiliary information during a random access process in the related technology, and the limited number of coding points of the logical channel identifier and poor flexibility.

[0247] In another exemplary embodiment, the early auxiliary information field may also have other lengths, such as 6 bits, which is not limited in this application. It should be noted that when the field is 6 bits, the above Figure 7 Only one reserved bit is needed to ensure that the MAC subheader length is one byte (ie, the subheader contains C_flag, reserved bits and early auxiliary information field).

[0248] In another embodiment of the present application, a specific MAC subheader including an early auxiliary information field is provided, wherein each feature can be indicated separately in the early auxiliary information field.

[0249] Figure 8 : is a structural diagram of a specific MAC subheader of an embodiment of the present application (III), such as Figure 8 As shown, the specific MAC subheader is one octet, i.e., 8 bits, and the specific MAC subheader includes the following fields:

[0250] C_flag field, CCCH_ID field, early auxiliary information field, reserved field (R).

[0251] C_flag field: This field is used to indicate a specific MAC subheader that contains an early assistance information field. Exemplarily, this field is 1 bit, which is set to 1 to indicate that the MAC subheader contains a field for early assistance information reporting, otherwise it is set to zero.

[0252] CCCH_ID field: This field is used to indicate whether the message type of the CCCH message identified by the MAC subheader is CCCH (CCCH message with a size of 48 bits) or CCCH1 (CCCH message with a size of 64 bits). Exemplarily, the CCCH_ID field is set to 0 to indicate CCCH, or, is set to 1 to indicate CCCH1. The reverse is also possible.

[0253] Reserved field (R): The value is 0.

[0254] The Early Assistance Information field has 4 bits, where each bit is used to indicate whether the UE has the capability to support the following features:

[0255] Indication information used to indicate whether the UE supports or has requested to support or request automatic retransmission of PUCCH for Msg4HARQ-ACK. For example, a value of 0 indicates that the UE does not support or request automatic retransmission of PUCCH for Msg4HARQ-ACK, and a value of 1 indicates that the UE supports or requests automatic retransmission of PUCCH for Msg4HARQ-ACK. Vice versa.

[0256] RedCap indication, used to indicate whether the UE is a UE with reduced capabilities (such as RedCapUE). Exemplarily, a value of 0 indicates that the UE is not a RedCapUE, and a value of 1 indicates that the UE is a RedCapUE. Vice versa.

[0257] The eRedCap indication is used to indicate whether the UE is a UE with enhanced redundancy capability (such as an eRedCapUE). Exemplarily, a value of 0 indicates that the UE is not an eRedCapUE, and a value of 1 indicates that the UE is an eRedCapUE. Vice versa.

[0258] The MuSIM indication is used to indicate whether the UE capability is temporarily restricted or not. Exemplarily, a value of 0 indicates that the UE capability is not restricted, and a value of 1 indicates that the UE capability is temporarily restricted. Vice versa. In another example, a value of 0 indicates that the temporary restriction on the UE capability is removed, and a value of 1 indicates that the UE capability is temporarily restricted. Vice versa. This application does not limit this.

[0259] In an embodiment of the present application, each UE capability characteristic can be individually indicated in a specific MAC subheader, thereby realizing the indication of early auxiliary information through the MAC subheader, thereby solving the problem in the related technology of using logical channel identifiers to indicate auxiliary information during random access, and the limited number of coding points of logical channel identifiers and poor flexibility.

[0260] Fig. 9 4 is a structural diagram of a specific MAC subheader in an embodiment of the present application, such as Fig. 9 As shown, the specific MAC subheader is one octet, i.e., 8 bits, and the specific MAC subheader includes the following fields:

[0261] C_flag field, early auxiliary information field, reserved field.

[0262] Compared with the previous embodiment, this embodiment does not have CCCH_ID for indicating the CCCH message type in the MAC subheader, and the rest is the same as the above embodiment.

[0263] In another embodiment of the present application, a specific MAC subheader including an early auxiliary information field is also provided. The early auxiliary information field indicates a logical channel identifier (LCID) field, which is specifically used to identify different logical channels for CCCH messages. Exemplarily, the field can be represented by LCID_CCCH. In another exemplary embodiment, the field can also be represented by other names, which is not limited by the present application.

[0264] Fig.10 5 is a schematic diagram of the structure of a specific MAC subheader in an embodiment of the present application, such as Fig.10 As shown, the specific MAC subheader is one octet, i.e., 8 bits, and the specific MAC subheader includes the following fields:

[0265] C_flag field, reserved field (R), CCCH_ID field and LCID_CCCH field.

[0266] In this embodiment, the LCID_CCCH field is actually used to indicate early auxiliary information, so it can also be called an early auxiliary information field, or other names, and this application does not impose any limitation on this.

[0267] C_flag field: This field is used to indicate a specific MAC subheader that contains an early assistance information field. Exemplarily, this field is 1 bit, which is set to 1 to indicate that the MAC subheader contains a field for early assistance information reporting, otherwise it is set to zero.

[0268] Reserved field (R): The value is 0.

[0269] CCCH_ID field: This field is used to indicate whether the message type of the CCCH message identified by the MAC subheader is CCCH (CCCH message with a size of 48 bits) or CCCH1 (CCCH message with a size of 64 bits). Exemplarily, the CCCH_ID field is set to 0 to indicate CCCH, or, is set to 1 to indicate CCCH1. The reverse is also possible.

[0270] LCID_CCCH field: used to indicate a unique logical channel identifier defined according to the CCCH message content. Exemplarily, each index value of the logical channel identifier can uniquely indicate any one or more combinations of early auxiliary information (such as UE capability information). An exemplary mapping relationship between the index value and the early auxiliary information can be shown in Table 2 in the above embodiment. In another exemplary embodiment, the field can also have other lengths, such as 6 bits, which is not limited by the present application. It should be noted that when the field is 6 bits, the above Fig.10 The reserved bits in the MAC subheader no longer appear to ensure that the MAC subheader length is one byte (ie, the MAC subheader includes C_flag, CCCH_ID and LCID_CCCH fields).

[0271] Fig.11 6 is a structural diagram of a specific MAC subheader in an embodiment of the present application, such as Fig.11 As shown, the specific MAC subheader is one octet, i.e., 8 bits, and the specific MAC subheader includes the following fields:

[0272] C_flag field, reserved field (R), and LCID_CCCH field.

[0273] In this embodiment, the LCID_CCCH field is actually used to indicate early auxiliary information, so it can also be called an early auxiliary information field, or other names, and this application does not impose any limitation on this.

[0274] Compared with the previous embodiment, this embodiment does not have CCCH_ID for indicating the CCCH message type in the MAC subheader, and the rest is the same as the above embodiment.

[0275] C_flag field: This field is used to indicate a specific MAC subheader that contains an early assistance information field. Exemplarily, this field is 1 bit, which is set to 1 to indicate that the MAC subheader contains a field for early assistance information reporting, otherwise it is set to zero.

[0276] Reserved field (R): The value is 0.

[0277] LCID_CCCH field: used to indicate a unique logical channel identifier defined according to the CCCH message content. Exemplarily, each index value of the logical channel identifier can uniquely indicate any one or more combinations of early auxiliary information (such as UE capability information). An exemplary mapping relationship between the index value and the early auxiliary information can be shown in Table 3 in the above embodiment. In another exemplary embodiment, the field can also have other lengths, such as 6 bits, which is not limited by the present application. It should be noted that when the field is 6 bits, Fig.11 There is only one reserved bit (R) in the MAC subheader to ensure that the length of the MAC subheader is one byte (that is, the subheader contains C_flag, R and LCID_CCCH fields).

[0278] In an embodiment of the present application, by setting a logical channel identifier in a specific MAC subheader and setting a mapping relationship between the logical channel identifier and the early auxiliary information, it is possible to indicate early auxiliary information through the MAC subheader, thereby solving the problem in the related art of using a logical channel identifier to indicate auxiliary information during a random access process, and the limited number of coding points of the logical channel identifier and poor flexibility.

[0279] In another embodiment of the present application, an early assistance message specifically used for transmitting early assistance information is provided.

[0280] In some embodiments, the early assistance message may be a Radio Resource Control (RRC) message or an RRC message segment carrying early assistance information.

[0281] In some embodiments, the early assistance message may also be a MAC CE or a MAC SDU or a MAC SDU segment carrying early assistance information.

[0282] In another embodiment of the present application, a method for reporting early auxiliary information is provided, which is applied to a terminal. Fig.12 Flowchart (III) of the method for reporting early auxiliary information according to an embodiment of the present application, such as Fig.12 As shown, the process includes the following steps:

[0283] Step S402, receiving configuration information related to early assistance information reporting from a base station;

[0284] Step S404: sending an early assistance message carrying early assistance information to the base station according to the configuration information.

[0285] In this embodiment, the configuration information related to the early assistance information report in step S402 is used to let the UE know that the NW can decode the early assistance message, or the NW has requested or allowed the UE to report the early assistance information through the early assistance message during the random access process, and the NW needs to provide some relevant configuration information to the UE.

[0286] In some embodiments, the early assistance message may be an RRC message, an RRC message segment, a MAC CE or a MAC SDU or a MAC SDU segment.

[0287] In an embodiment of the present application, by introducing an early assistance message specifically used to provide early assistance information to the UE, the problem that the logical channel identifier is used to indicate auxiliary information during the random access process in the related art, the number of coding points of the logical channel identifier is limited, and the flexibility is poor can be solved.

[0288] In some embodiments, the early assistance message is a specific RRC message carrying early assistance information, and can be described by RRC Early Assistance Message (RRCEarlyInformation). In some examples, other message names may also be used, and this application does not limit this.

[0289] In some embodiments, the early assistance information may include information related to one or more UE capabilities. The UE capability refers to whether the UE supports a feature or a function. The present application does not limit the specific content of the early assistance information.

[0290] In some embodiments, the early assistance information may include any one or any combination of the following information:

[0291] Indication information used to indicate whether the UE supports or requests automatic retransmission of the PUCCH of Msg4 HARQ-ACK;

[0292] Indication information used to indicate whether the UE is a UE with reduced capabilities (e.g., RedCap UE);

[0293] Indication information used to indicate whether the UE is a UE with enhanced reduction capability (e.g., eRedCap UE);

[0294] Indication information used to indicate whether UE capabilities are temporarily restricted;

[0295] MUSIM auxiliary information;

[0296] UE identification information;

[0297] Alternate fields;

[0298] Reserved fields;

[0299] Key extension field.

[0300] In some embodiments, the configuration information in step S402 includes: at least one of an explicit indication or an implicit indication for indicating whether early auxiliary information can be reported in the random access procedure.

[0301] In an exemplary embodiment, the explicit indication may include an explicit indication for indicating whether the UE is allowed to use the early assistance message. Exemplarily, the explicit indication is that the UE can use the RRC early assistance message (RRCEarlyInformation) to report the early assistance information.

[0302] In some embodiments, the implicit indication includes at least one of the following:

[0303] Msg4 Hybrid Automatic Repeat Request Confirmation HARQ-ACK automatic repeat configuration information;

[0304] Configuration information related to temporary capability restrictions of multi-user identity module (MUSIM) terminals;

[0305] Reduced capability RedCap terminal configuration information;

[0306] Enhanced the ability to reduce eRedCap terminal configuration information;

[0307] Radio Network Temporary Identifier (RNTI) configuration information;

[0308] Search space configuration information;

[0309] Control resource set (CORESET) configuration information;

[0310] Random access process trigger information (such as trigger reason);

[0311] Initial access process trigger information (such as trigger reason, purpose of initiating the process).

[0312] In an exemplary embodiment, the automatic retransmission configuration information may include at least one of the following:

[0313] The automatic retransmission enabling indication is used to indicate whether the UE is allowed to send an early indication to support or request automatic retransmission of HARQ-ACK. Exemplarily, sending the early indication may be limited to during the random access process.

[0314] The repetition factor of automatic retransmission is used to indicate the number of automatic retransmissions of the confirmation message that the UE can choose when sending HARQ-ACK. Exemplarily, the candidate values ​​of the repetition factor of automatic retransmission can be {1, 2, 4, 8}.

[0315] In an exemplary embodiment, the temporary capability restriction information of the MUSIM UE may be applied to all RRC states, or may be limited to certain RRC procedures, for example, during the RRC connection establishment or RRC connection recovery process.

[0316] In an exemplary embodiment, reduced capability (RedCap) is a bandwidth reduction technology, and the RedCap terminal configuration information may include at least one of the following:

[0317] RedCapUE indication, used to indicate whether the RedCapUE can use an RRC message during the RACH process to indicate that it is a RedCapUE. The RRC message may be specially designed for providing early assistance information during the RACH process.

[0318] The cell barring indication is used to indicate whether the cell is barred for RedCapUE with 1 or 2 Rx bands or whether the cell is barred for RedCapUE with 1 or 2 Rx bands to access.

[0319] The half-duplex indication is used to indicate whether the current cell supports half-duplex frequency division duplex (Frequency Division Duplex / Duplexing, referred to as FDD) RedCapUE indication.

[0320] In an exemplary embodiment, Enhanced Reduced Capability (eRedCap) is an enhanced bandwidth reduction technology, and the eRedCap terminal configuration information may include at least one of the following:

[0321] eRedCapUE indication, used to indicate whether the eRedCapUE can indicate that it is an eRedCapUE during the RACH procedure.

[0322] The cell barring indication is used to indicate whether the cell is barred for eRedCapUE with 1 or 2 Rx bands or whether the cell is barred for eRedCapUE with 1 or 2 Rx bands to access.

[0323] Half-duplex indication is used to indicate whether the current cell supports half-duplex FDD eRedCapUE.

[0324] In an exemplary embodiment, the RNTI configuration information is used to monitor downlink control information (DCI) scheduling RRC messages for early assistance information. The RNTI configuration information may include at least one of the following:

[0325] RNTI offset value for temporary cell RNTI (TC-RNTI for short), if the network provides this configuration, the UE uses the modified TC-RNTI to monitor and receive the DCI scheduling RRC early assistance message after sending Msg3 carrying the indication of requesting to send early assistance information. The modified TC-RNTI is generated based on the RNTI offset value for TC-RNTI and the TC-RNTI value received in the random access response of the scheduling Msg3. Exemplarily, the modified TC-RNTI is equal to the sum of the value of TC-RNTI and the RNTI offset of TC-RNTI.

[0326] RNTI offset value for MsgB-RNTI, if the network provides this configuration, the UE uses the modified MsgB-RNTI to monitor and receive the DCI scheduling the RRC early assistance message after sending the MsgA carrying the indication of requesting to send early assistance information. The modified MsgB-RNTI is generated based on the RNTI offset value, and the MsgB-RNTI is generated based on the RACH resource selected for sending MsgA, as specified in standard 38.321. Exemplarily, the value of the modified MsgB-RNTI is equal to the sum of the value of the Msg-RNTI and the RNTI offset of the MsgB-RNTI.

[0327] In an exemplary embodiment, the search space configuration information is used to configure a dedicated search space for the UE to monitor and receive downlink control information (DCI) for scheduling RRC early assistance messages. The search space configuration may include at least time domain and frequency domain resource configuration. Exemplarily, at least one of the time domain, frequency domain, or code domain resources of the search space (configured to search for DCI for scheduling early assistance messages) may be different from a common search space, which is configured to monitor DCI for scheduling messages not for early assistance information.

[0328] In an exemplary embodiment, a control resource set (CORESET) is configured to configure a dedicated control resource set for a UE to listen to and receive downlink control information (DCI) for scheduling RRC early assistance messages. The CORESET configuration includes at least time domain and frequency domain resource configurations. Exemplarily, at least one of the time domain resources, frequency domain resources, or code domain resources of the CORESET resources (configured to search for downlink control information (DCI) for scheduling early assistance messages) may be different from a common CORESET, which is configured for the UE to listen to DCI for scheduling messages not for early assistance information.

[0329] In an embodiment of the present application, through the implicit indication in any of the above embodiments, the terminal can be implicitly notified that the cell allows the UE to use an early assistance message specifically used for the UE to provide early assistance information to the NW, and report the early assistance information during the random access process or after the random access ends.

[0330] In some embodiments, the configuration information in step S402 may be transmitted in any of the following ways: system information, broadcast message, multicast message, radio resource control RRC signaling, non-access layer NAS message, paging, short message, MAC layer signaling, physical layer signaling.

[0331] In an exemplary embodiment, when using system information (SI) to transmit configuration information, it can be delivered via a system message consisting of a SIB1 message and / or one or more SIBx information elements (IE), where x in the SIBx IE is a positive integer starting from 2, and the SIBx IE can be one or more existing system information blocks (SIBs) (e.g., SIB2 to SIB21) or an introduced new SIB (e.g., SIB22).

[0332] In an exemplary embodiment, a common SIBx may be used to indicate one or more indications in the above embodiments, wherein x in SIBx may be any positive integer, such as SIB1, SIB22.

[0333] In another embodiment, multiple different system information (one or more of SIB1 messages or SIBxIEs) may be used to indicate the configuration information in any of the above embodiments. Exemplarily, SIB1 may include configuration information for RedCapUE, configuration information for eRedCapUE, configuration information for MUSIM terminals, or explicit indications to enable the terminal to use a specific MAC subheader carrying an early assistance information field. Exemplarily, SIB19 may include automatic retransmission configuration information for Msg4 HARQ-ACK.

[0334] In some embodiments, the RRC early assistance message may provide early assistance information from the UE to the NW during the RACH process. The RRC early assistance message may be sent during the RACH process, exemplarily including at least one of the RACH processes triggered by any of the RRC establishment, RRC recovery, RRC reconstruction, RRC reconfiguration process or other use cases. Alternatively, the RRC early assistance message may also be transmitted based on network scheduling after the RACH process is completed. The following is an example of the RRC early assistance message providing early assistance information from the UE to the NW during the RACH process.

[0335] In some embodiments, in a 4-step RACH process, the RRC early assistance message may be sent after the transmission of Msg3 and before the transmission of Msg4, or in a 2-step RACH process, the RRC early assistance message may be sent after the transmission of MsgA and before the transmission of MsgB. Exemplarily, in order to distinguish the RRC early assistance message from the existing Msg3 specified in the standard, Msg3bis or subsequent Msg3 may be used to describe the message containing the RRC early assistance message. The above terms such as RRC Early Information, Msg3bis, and subsequent Msg3 are all for simplifying the description, and this application does not impose any restrictions on this.

[0336] Fig.13 is a flowchart of a 4-step RACH according to an embodiment of the present application, such as Fig.13 As shown, the process includes the following steps:

[0337] Step 0: The UE receives configuration information related to early assistance information reporting from the base station;

[0338] Step 1: The UE sends a random access preamble (Msg1) to the base station;

[0339] Step 2: The UE receives a random access response (Msg2) from the base station;

[0340] Step 3a: The UE sends the first part of the uplink message (such as Msg3) based on network scheduling;

[0341] Step 3b: After sending the first part of the uplink message (such as Msg3), the UE monitors the downlink control information (Downlink Control Information, referred to as DCI) used to schedule the early auxiliary information, and sends the second part of the scheduled transmission based on the scheduling of the base station, that is, sends the early auxiliary information (such as Msg3bis) to the base station based on the scheduling information received in the DCI;

[0342] Step 4: The UE receives Msg4 from the base station for contention resolution.

[0343] In some embodiments, the uplink message in step 3a may include an indication for indicating the existence of the second part of the scheduled transmission. The uplink message may also include information indicating the size of the buffered data to be transmitted.

[0344] In some embodiments, before step 1, the UE may select a RACH opportunity or a RACH packet resource based on a buffer size of data to be sent or a potential CCCH size.

[0345] Fig.14 is a flowchart of a 2-step RACH according to an embodiment of the present application, such as Fig.14 As shown, the process includes the following steps:

[0346] Step 0: The UE receives configuration information related to early assistance information reporting from the base station;

[0347] Step A1: The UE sends a random access preamble and a PUSCH payload (MsgA) to the base station;

[0348] Step A2: After sending the PUSCH payload, the UE monitors the DCI for scheduling early auxiliary information, and sends early auxiliary information (such as MsgAbis) to the NW based on the scheduling information received in the DCI;

[0349] Step B: The UE receives MsgB from the base station for contention resolution.

[0350] In some embodiments, the uplink message (PUSCH payload) in step A1 may include an indication for indicating the existence of MsgAbis. The uplink message may also include buffer size information of data to be sent.

[0351] In some embodiments, before step 1, the UE may select a RACH opportunity or a RACH packet resource based on the size of the to-be-transmitted data buffer or the size of the potential CCCH.

[0352] Fig.15 is a flowchart of a 4-step RACH according to another embodiment of the present application, such as Fig.15 As shown, the process includes the following steps:

[0353] Step 0: The UE receives configuration information related to early assistance information reporting from the base station;

[0354] Step 1: The UE sends a random access preamble (Msg1) to the base station;

[0355] Step 2: The UE receives a random access response (Msg2) from the base station;

[0356] Step 3a: The UE sends a first part of a CCCH message (such as the first part of a CCCH message or a first CCCH message) to the base station as an uplink message (eg, Msg3) scheduled based on the NW;

[0357] Step 4: UE receives Msg4 from the base station for contention resolution;

[0358] Step 5: The UE monitors the dynamic scheduling from the base station, and executes the transmission of the second part of the CCCH message (such as the second part of the CCCH message or the second CCCH message) according to the received scheduling information.

[0359] In this embodiment, the radio resource control layer may segment the CCCH message into a first CCCH message part and a second CCCH message part, or the radio resource control layer may generate two CCCH messages as a first CCCH message and a second CCCH message. Compared with a conventional CCCH message, this embodiment may transfer part of the information to the second CCCH message part or the second CCCH message to reduce the size of a single CCCH message.

[0360] In some embodiments, the configuration information to be sent in step 0 further includes RACH configuration. The RACH configuration may be sent together with or separately from the configuration information of the early assistance information report.

[0361] In some embodiments, the base station waits to receive the first part and the second part of the CCCH message (or the first CCCH message and the second CCCH message) before starting to combine the received CCCH messages.

[0362] Through the embodiments of the present application, the transmission scheduling is divided into two parts and sent during the random access process, which can reduce the size of a single CCCH message and report early auxiliary information without increasing the size of the CCCH message, thereby solving the problem in the related art of using logical channel identifiers to indicate auxiliary information during random access, and the limited number of coding points of logical channel identifiers and poor flexibility.

[0363] In an exemplary embodiment of the present application, the base station may send configuration information to the terminal via system information SIB1.

[0364] In this embodiment, the structure of the system information SIB1 is as follows:

[0365]

[0366] In this embodiment, SIB1-vnnmm refers to SIB1 defined in the standard. Wherein, v represents the standard version implemented, nn represents the version number of the released standard, and mm represents the mmth revision of the nnth version, that is, the mmth sub-version of the nnth version. Exemplarily, SIB1-v1800 refers to SIB1 based on the 18th version 00th revision standard.

[0367] In this embodiment, the new control unit rrcEarlyInformationAllowed-rnn (allowing UE to provide early assistance information to NW during RACH) is a new field to be introduced in future standard versions. Exemplarily, a specific RRC message RRC EarlyInformation (RRC Early Assistance Message) that is allowed to carry early assistance information is an information unit in the SIB1 message.

[0368] In this embodiment, the presence of the rrcEarlyInformationAllowed field may be used to indicate that the UE is allowed to provide early assistance information to the NW during RACH.

[0369] In this embodiment, the rrcEarlyInformationAllowed field is only an example, and other fields may also be used, such as the commonCapabilityallowed field, the assistanceInformationDuringRACHAllowed field, the rrcEarlyAssistingInformationAllowed field, the rrcEarlyInformationAllowed field, or the rrcEarlyIndicationAllowed field, etc. This application does not limit the field names of the configuration information.

[0370] In another embodiment, the RRC early assistance message for providing early assistance information during the RACH process is sent from the UE to the NW using the logical channel CCCH2 (i.e., the second CCCH message). Therefore, the RRC early assistance message activation indication information may be equivalent to the indication information of activating the logical channel CCCH2.

[0371] In this embodiment, the structure of the system information SIB1 is as follows:

[0372]

[0373]

[0374] In this embodiment, the presence of the ccch2allowed field may be used to indicate that the cell supports the UE to report early assistance information to the NW via CCCH2 during the RACH procedure.

[0375] In some embodiments, a Boolean type indication information may be used instead of an explicit indication, such as the IE discussed in the above two examples may be a Boolean type indication. For example, a value of 1 may indicate that the cell supports the UE to provide assistance information to the NW using an RRC early assistance message during the RACH process, while a value of 0 indicates that the cell does not support the UE to provide assistance information to the NW using an RRC early assistance message during the RACH process. Vice versa, this application is not limited to this.

[0376] In the first two embodiments, ccch2allowed and rrcEarlyInformationAllowed-rnn are both explicit indications in the configuration information. In addition, the configuration information may also be an implicit indication to implicitly notify the cell to support the use of RRC early assistance messages to transmit assistance information to the NW.

[0377] In an exemplary embodiment, it may be specified that explicit indication is only required for RedCapUE, while implicit indication is used for other use cases.

[0378] In some embodiments, the structure of the system information SIB1 is as follows:

[0379]

[0380] In this embodiment, the presence of the rrcEarlyInformationAllowedRedCap-rnn field can be used to indicate that the cell supports RedCapUE to transmit assistance information to the NW through the RRC early assistance message.

[0381] In this embodiment, if the RedCap UE does not support the introduction of RRC Early Assistance Message during RACH, the RedCap UE will not use RRC message for transmitting early assistance information. If the RedCap UE supports the use of RRC Early Assistance Message to report assistance information during the RACH process (such as the ability of the UE to support other features), the RedCap UE can send assistance information to the NW via RRC Early Assistance Message.

[0382] In some embodiments, when explicit indication (configuration information) is provided through system information, changes in configuration content will result in changes in the system message value tag, thereby resulting in an update process for the system message.

[0383] In an exemplary embodiment of the present application, the base station may also send configuration information to the terminal through a new system information block SIBx.

[0384] In this embodiment, SIBx contains information related to evaluating whether the UE is allowed to provide early assistance information to the NW during the RACH process, such as whether the UE is allowed to report the early assistance information to the base station through a message dedicated to providing early assistance information (such as an RRC early assistance message). In this embodiment, x in SIBx can be an integer starting from 22, indicating newly introduced system information.

[0385] In some embodiments, the information unit design of SIBx is as follows:

[0386]

[0387] In this embodiment, the fields in SIBx are described as shown in Table 4 below:

[0388] Table 4:

[0389]

[0390] In this embodiment, the nonCriticalExtension field in the information unit of SIBx is used to introduce a new field in a future version of the standard. This field can also be replaced by other tags, which is not limited in this application.

[0391] In another embodiment, separate system information (one or more of SIB1 messages or SIBxIEs) may be used to indicate the configuration information in any of the above embodiments. Exemplarily, SIB1 may include configuration information for RedCapUE, configuration information for eRedCapUE, configuration information for MUSIM terminals, or explicit indications. SIB19 may include automatic retransmission configuration information for HARQ-ACK. SIB22 may include an explicit indication for enabling RRC early assistance messages from UE to NW.

[0392] In the embodiment of the present application, after receiving the configuration information, the UE needs to notify the base station that it wants to provide early assistance information in the RRC message (or RRC message segment, MAC SDU, MAC SDU segment). This process can be implemented in step 3a in the above 4-step RACH or step A1 in the 2-step RACH, so that the base station schedules uplink resources accordingly after receiving the request, so that the UE can send the corresponding early assistance information (e.g., RRC early assistance message).

[0393] In the embodiment of the present application, the UE may be indicated to want to send early assistance information (such as reporting through an RRC early assistance message) in at least one of the following ways:

[0394] Method 1 is to use a specific reserved LCID code point for indication, where the LCID code point is used to identify a CCCH / CCCH1 message and indicates that after the CCCH / CCCH1 message, the UE has a need to send an early assistance message to the NW.

[0395] Method 2: using the reserved bit R in the MAC subheader of the Cell Radio Network Temporary Identifier (C-RNTI) MAC CE to indicate whether the UE needs to send an early assistance message to the NW.

[0396] In an exemplary embodiment, the LCID table values ​​in the above method 1 are shown in Table 5:

[0397] Table 5:

[0398]

[0399] In this embodiment, the indexes m1 and m2 in Table 5 are any two reserved indexes in the LCID table, and the values ​​are any integers in [47 or 37 to 42], and m1 and m2 are different.

[0400] In this implementation, if the UE wants to transmit early assistance information in an RRC message, it can set the LCID field used to identify the CCCH message in Msg3 or MsgA to a value in [47 or 37-42]. When the base station receives Msg3 / MsgA containing the LCID identifier, the base station knows that the UE has requested resources to send the RRC early assistance message.

[0401] Fig.16 is a schematic diagram of the structure of the MAC subheader of the MAC CE identifying the C-RNTI according to an embodiment of the present application, such as Fig.16 As shown, there are two R bits in the MAC subheader.

[0402] In this embodiment, the reserved one or two R bits in the MAC subheader of the MAC CE of the C-RNTI can be identified to indicate that the UE wants to send early auxiliary information to the network side, that is, the above-mentioned method 2.

[0403] In an exemplary embodiment, the first R bit may be set to 1 to indicate that the UE wants to send early assistance information to the network side (eg, based on an RRC early assistance message).

[0404] In another exemplary embodiment, the second R bit may be set to 1 to indicate that the UE wants to send early assistance information to the network side (eg, based on an RRC early assistance message).

[0405] In an exemplary embodiment, the above-mentioned method 1 and method 2 can be used in combination. Exemplarily, when Msg3 or MsgA contains a CCCH message, the above-mentioned method 1 is used for indication, and when Msg3 or MsgA contains a MAC CE of a C-RNTI, the above-mentioned method 2 is used for indication.

[0406] In the embodiment of the present application, after the UE issues the above indication to the base station, it will provide early assistance information in the RRC message (or RRC message segment, MAC SDU, MAC SDU segment). This process can be implemented in step 3b of the above 4-step RACH or step A2 of the 2-step RACH. For example, if it is based on the RRC message or RRC message segment, the UE can implement it by sending an RRC early assistance message to the NW. The following will be explained in conjunction with the content of the early assistance information.

[0407] As shown below, the early assistance information content may include at least one of the following information related to UE capabilities or UE types.

[0408] In some embodiments, the indication information for indicating whether the UE supports or requests automatic retransmission of the PUCCH for Msg4 HARQ-ACK may be given in the following manner:

[0409] Indicated by a one-bit indication information of Boolean type. Exemplarily, a value of 0 indicates that the UE does not support or request PUCCH automatic retransmission for Msg4 HARQ-ACK, and a value of 1 indicates that the UE supports or has requested PUCCH automatic retransmission for Msg4 HARQ-ACK. Vice versa, this application does not limit this. Exemplarily, if the base station has configured PUCCH automatic retransmission configuration information (such as repetition factor) for Msg4 HARQ-ACK in the system information, this indication is optional.

[0410] The presence of the indication field indicates that the UE supports this capability. For example, the presence of the indication field indicates that the UE can or has requested automatic PUCCH retransmission for Msg4 HARQ-ACK, and the absence of the indication field indicates that the UE does not support or does not request automatic PUCCH retransmission for Msg4 HARQ-ACK.

[0411] In some embodiments, the indication information for indicating whether the UE is a UE with reduced capability (e.g., RedCap UE) may be given in the following manner:

[0412] The indication is performed by one-bit indication information of Boolean type. For example, a value of 0 indicates that the UE is not a RedCap UE, and a value of 1 indicates that the UE is a RedCap UE. Vice versa, this application does not limit this.

[0413] The presence of the indication field indicates that the UE supports the capability. Exemplarily, the presence of the indication field indicates that the UE is a RedCap UE, and the absence of the indication field indicates that the UE is not a RedCap UE.

[0414] In some embodiments, the indication information for indicating whether the UE is a UE with enhanced reduction capability (e.g., eRedCap UE) may be given in the following manner:

[0415] The indication is performed by one-bit indication information of Boolean type. For example, a value of 0 indicates that the UE is not an eRedCap UE, and a value of 1 indicates that the UE is an eRedCap UE. Vice versa, this application does not limit this.

[0416] The presence of the indication field indicates that the UE supports the capability. Exemplarily, the presence of the indication field indicates that the UE is an eRedCap UE, and the absence of the indication field indicates that the UE is not an eRedCap UE.

[0417] In some embodiments, the indication information for indicating whether the UE capability is temporarily restricted may be used for a terminal with multiple user identity modules MUSIM. When the UE is a terminal with activated MUSIM capability, the UE capability (e.g., supported frequency band combination, capability to support dual connectivity) may be temporarily restricted. The indication information may be given in the following manner:

[0418] The indication is performed by one-bit indication information of Boolean type. For example, a value of 0 indicates that the UE capability is not restricted or the temporary restriction of the UE capability is lifted, and a value of 1 indicates that the UE capability is temporarily restricted. Vice versa, this application does not limit this.

[0419] The presence of the indication field indicates that the UE supports the capability. Exemplarily, the presence of the indication field indicates that the UE capability is temporarily restricted, and the absence of the indication field indicates that the UE capability is not restricted or the temporary restriction of the UE capability is lifted.

[0420] In some embodiments, the MUSIM auxiliary information includes at least one of: a MUSIM gap priority preferred by the UE, a maximum number of multiple-input multiple-output (MIMO) layers preferred by the UE, a frequency band combination and bandwidth supported by the UE, and at least one of capability information that can be supported when the UE capability is temporarily restricted.

[0421] In some embodiments, the capability information supportable when the UE capability is temporarily restricted includes at least one of the following: supported frequency band combinations and supported bandwidths on a maximum number of MIMO layers, supported MUSIM gaps, and supported MUSIM gap priorities.

[0422] In some embodiments, the UE identification information is used to allow the NW to identify which UE the RRC message is sent from. The UE identification information may be generated based on the UE identification included in msg3 during the RACH process, and the UE identification information may include at least one of the following:

[0423] A UE identity included in an RRC message (e.g., an RRC Setup message) for requesting RRC establishment;

[0424] A UE identity included in an RRC message for requesting RRC recovery (e.g., an RRC recovery request or an RRC recovery request 1 message);

[0425] A UE identity included in an RRC message (e.g., an RRC reconfiguration message) for requesting RRC reestablishment;

[0426] C-RNTI.

[0427] In some embodiments, the UE identification information may be a bit string of variable length or a bit string of fixed length X.

[0428] In some embodiments, when the UE identification information is a bit string of variable length, the identification may be the same as the UE identification in msg3 sent during the RACH process.

[0429] In an exemplary embodiment, for the RRC establishment procedure, the UE identification information may be a UE identification included in an RRC message for requesting RRC establishment (e.g., an RRC establishment request message). Alternatively, for the RRC recovery procedure, the UE identification information may be a UE identification included in an RRC message for requesting RRC recovery (e.g., an RRC recovery request or an RRC recovery request 1 message). Alternatively, for the RRC reestablishment procedure, the UE identification information may be a UE identification included in an RRC message for requesting RRC reestablishment (e.g., an RRC reconfiguration message). Alternatively, for other situations where C-RNTI is available (e.g., for the RRC reconfiguration procedure), the UE identification information is C-RNTI.

[0430] In another exemplary embodiment, C-RNTI may also be considered as UE identification information in the RRC re-establishment process.

[0431] In some embodiments, when the UE identification information is a bit string of fixed length, it is assumed that its length is X bits, where X is a positive integer. The following different scenarios may be considered to generate the UE identification information based on the UE identification included in the Msg3 sent during the RACH process.

[0432] In an exemplary embodiment, when X is equal to the bit string length of the UE identifier included in Msg3, the UE identifier information has the same value as the UE identifier included in Msg3; when X is greater than the bit string length of the UE identifier included in Msg3, the UE identifier information may be equal to a combination of the UE identifier included in Msg3 and a random value of length Y bits generated by the UE. The Y-bit random value may be placed on the right or left side of the UE identifier. The quantity Y is equal to X minus (the bit string length of the UE identifier included in Msg3). In this way, the total bit string length of the UE identifier information is still X. When X is less than the bit string length of the UE identifier included in Msg3, the UE identifier information may be the X least significant bits (LSBs) and / or the X most significant bits (MSBs) of the UE identifier included in Msg3 sent during the RACH process.

[0433] In the embodiment of the present application, the spare bit is an unused bit reserved for future use, and when early auxiliary information is sent using RRC layer signaling, the field is included in the RRC message. The reserved bit is a reserved bit for future use, and the field is included in the MAC CE when early auxiliary information is transmitted using MAC layer signaling. The key extension field can be used when a key extension is required in the future.

[0434] In some embodiments, the early assistance information may be sent in an RRC message or an RRC message segment or a MAC CE or a MAC SDU or a MAC SDU segment.

[0435] In this embodiment, the logical channel used to transmit the specific RRC message carrying the early auxiliary information may be a common control channel (CCCH) or a dedicated control channel (DCCH). When the CCCH logical channel is used, the type of the signaling radio bearer (SRB) used to send the specific RRC message is SRB0. When the DCCH logical channel is used, the SRB type may be SRB1.

[0436] In some embodiments, if a specific RRC message is used to provide early assistance information, the RRC message may be a fixed-length RRC message or a variable-length RRC message. If the CCCH logical channel is used for a specific RRC message, the CCCH logical channel category may be different according to the RRC message size. Exemplarily, if the specific RRC message is a 48-bit RRC message, it can be sent from the UE to the network on the uplink CCCH logical channel. If it is a 64-bit RRC message, it can be sent from the UE to the network on the uplink CCCH1 logical channel. If the specific RRC message is a fixed-length RRC message and its size is a value different from 48 bits and 64 bits, a new uplink common control channel (UL-CCCH) category (e.g., CCCH2) other than CCCH and CCCH1 can be used to send the specific RRC message.

[0437] In an exemplary embodiment of the present application, taking the early assistance information including UE identification information as an example, the UE provides the early assistance information to the base station (or NW) through a specific RRC message. The configuration of the RRC message is as follows:

[0438] Signaling radio bearer: SRB0

[0439] RLC-SAP:TM

[0440] Logical channel: CCCH

[0441] Direction: UE to network

[0442] In this embodiment, the specific RRC message (such as the RRC early assistance message) is a fixed 48-bit RRC message that can be sent from the UE to the NW using the logical channel CCCH. The radio link control (Radio Link Control) mode used for the specific RRC message is the transparent (Transparent Mode, referred to as TM) mode. The signaling radio bearer used to carry the specific RRC message is SRB0.

[0443] In this embodiment, the content of the RRC early assistance message (RRCEarlyInformation) is as follows:

[0444]

[0445] The field names, field positions, and field sizes involved in this embodiment are all examples, and this application does not limit them. The content included in the embodiment is not limited to the content currently described, that is, other fields may also be included.

[0446] In this embodiment, the information unit fields in the RRC early assistance message are shown in Table 6:

[0447] Table 6:

[0448]

[0449]

[0450] In this embodiment, the spare field in the RRC early assistance message (RRCEarlyInformation) is n bits, which are not used now and can be used for other purposes in the future. The number n is the number of remaining bits that are not used now in the 48-bit RRC message.

[0451] In an exemplary embodiment, assuming that the length of the truncatedUE-Identity field is equal to the length of the C-RNTI, the truncated UE identity field may include the following cases:

[0452] For the RRC setup procedure, the truncated UE identity refers to the least significant X bits of the InitialUE-Identity field included in the RRCSetupRequest message.

[0453] For the RRC resumption procedure, the truncated UE identity refers to the least significant X bits of the resumeIdentity included in the RRCResumeRequest or RRCResumeRequest1 message.

[0454] For the RRC re-establishment procedure, it refers to the least significant X bits of the ReestablishabUE-Identity included in the RRCReestablishmentRequest message.

[0455] For other cases where C-RNTI is available, it may be equal to the C-RNTI value.

[0456] In another exemplary embodiment, the truncated UE identification information discussed above for the RRC reestablishment process may be the most significant X bits of the ReestablishabUE-Identity contained in the RRCReestablishmentRequest message, and the rest is the same as the above embodiment.

[0457] In another exemplary embodiment, for other situations when C-RNTI is available, it can be used to replace the truncated UE identification information of the RRC reestablishment process, where C-RNTI is the C-RNTI value included in the ReestablishabUE-Identity in the RRCReestablishmentRequest message, and the rest is the same as the above embodiment.

[0458] In an exemplary embodiment of the present application, taking the case where the early assistance information does not include the UE identification information as an example, the UE provides the early assistance information to the base station (or NW) through a specific RRC message. The configuration of the RRC message is as follows:

[0459] Signaling radio bearer: SRB0

[0460] RLC-SAP:TM

[0461] Logical channel: CCCH

[0462] Direction: UE to network

[0463] In this embodiment, the specific RRC message (such as the RRC early assistance message) is a fixed 48-bit RRC message that can be sent from the UE to the NW using the logical channel CCCH. The radio link control (Radio Link Control) mode used for the specific RRC message is the transparent mode (TM mode). The signaling radio bearer used to carry the specific RRC message is SRB0.

[0464] In this embodiment, the content of the RRC early assistance message (RRCEarlyInformation) is as follows:

[0465]

[0466]

[0467] In this embodiment, the information unit fields in the RRC early assistance message are shown in Table 7:

[0468] Table 7:

[0469]

[0470] In this embodiment, the spare field in the RRC early assistance message (RRCEarlyInformation) is n bits, which are not used now and can be used for other purposes in the future. The number n is the number of remaining bits that are not used now in the 48-bit RRC message.

[0471] In some embodiments, early assistance information may also be transmitted in MAC layer signaling.

[0472] In an exemplary embodiment, an early assistance information MAC CE (media access control layer control element) can be used to report early assistance information (e.g., information related to UE capabilities) from the UE to the NW. The early assistance information MAC CE is octet-aligned, i.e., the length of the MAC CE is an integer number of bytes, each byte is 8 bits long. In some examples, the MAC CE can be of variable length. In another example, the MAC CE has a fixed length. In yet another example, the MAC CE can be a MAC subheader without a MAC payload, i.e., the MAC CE carries only a MAC subheader, and the payload is zero bytes.

[0473] In this embodiment, the early assistance information MAC CE may include at least one of the early assistance information fields discussed for step 3 or step A in any of the above embodiments.

[0474] In some embodiments of the present application, the reporting of early assistance information may be implemented through an RRC early assistance message.

[0475] In some embodiments, in order to enable the NW to distinguish the RRC message (such as an RRC early assistance message) or RRC message segment (alternatively, MAC CE or MAC SDU or MAC SDU segment) providing early assistance information in the embodiments of the present application from other scheduled uplink transmissions specified in the current standard, a reserved LCID index can be selected in the LCID reserved bit to identify the RRC message or RRC message segment (alternatively, MAC CE or MAC SDU or MAC SDU segment) containing the early assistance information.

[0476] In an exemplary embodiment, when early assistance information is sent using RRC layer signaling, the value of the LCID of the UL-SCH that can be used to identify the RRC message carrying the early assistance information is as shown in Table 8 below:

[0477] Table 8:

[0478]

[0479] In another exemplary embodiment, when the early assistance information is sent using MAC layer signaling, the value of the LCID that can be used to identify the UL-SCH of the MAC CE carrying the early assistance information is shown in the following Table 9:

[0480] Table 9:

[0481] Code point / index LCID value Value m MACCE is used to indicate early assistance information from UE to NW, m is an integer

[0482] In some embodiments, dedicated resources may be configured to monitor DCI for scheduling early assistance information.

[0483] In some embodiments, after sending a Msg3 or MsgA for transmitting a request for early assistance information reporting, the UE searches for downlink control information (DCI) in the configured PDCCH resources, and performs subsequent transmissions based on the scheduling information included in the downlink control information (DCI), such as transmitting an RRC message (such as an RRC early assistance message) or an RRC message segment (alternatively, a MAC CE or a MAC SDU or a MAC SDU segment) carrying early assistance information.

[0484] In an exemplary embodiment, there are UEs in the system that support or do not support the early assistance message reporting capability, and they can share the same common physical layer RACH resource configuration. In this case, the scheduling information contained in the DCI used to schedule the early assistance information and the DCI not used to schedule the early assistance information may be different. Therefore, in order to ensure that only the UE that sends a request to report the early assistance information will receive the corresponding DCI scheduling for the early assistance information transmission, at least one of the following options can be adopted:

[0485] Option 1, configure a dedicated search space (SS) for the UE to monitor the DCI that schedules the transmission of early assistance messages.

[0486] Exemplarily, after the UE transmits a request indicating that it wants to send early assistance information, it monitors DCI on a dedicated SS, which is specially configured to monitor DCI that schedules the transmission of early assistance messages.

[0487] Option 2 may configure a dedicated CORESET resource configuration for the UE to monitor the DCI that schedules the early assistance message.

[0488] Exemplarily, after the UE transmits a request indicating that it wants to send early assistance information, it monitors DCI on a CORESET that is specifically configured to monitor DCI that schedules early assistance message transmission.

[0489] Option 3: monitor DCI-scheduled RRC early assistance messages through different RNTI value ranges.

[0490] Exemplarily, it may include at least one of the following:

[0491] If the UE receives TC-RNTI in the random access response of the scheduled Msg3 transmission, and the Msg3 contains a request to send an early assistance information message, the enhanced TC-RNTI can be used to monitor the DCI scheduled RRC early assistance message. For example, the enhanced TC-RNTI value is equal to the TC-RNTI received in the random access response of the scheduled Msg3 transmission plus the RNTI offset. If the enhanced TC-RNTI value is different from the original TC-RNTI value range, it is guaranteed that only the UE that requested to report the early assistance message will receive the DCI scheduled early assistance message transmission.

[0492] Exemplarily, if the UE previously sent a MsgA carrying an indication of requesting early assistance information reporting, the UE uses an enhanced MsgB-RNTI to monitor the PDCCH. For example, the enhanced MsgB-RNTI value is equal to the MsgB-RNTI plus the RNTI offset. If the enhanced MsgB-RNTI value is different from the original MsgB-RNTI value range, it is ensured that only the UE that requested reporting of the early assistance message will receive the DCI scheduling the transmission of the early assistance message.

[0493] In some embodiments, the DCI format for scheduling early assistance message transmission may include at least one of the following information:

[0494] Success feedback information used to indicate that the NW has successfully received the previously scheduled early assistance message. Exemplarily, this field can be one bit, which indicates whether the NW has successfully received the early assistance message transmitted by the UE. For example, a value of 1 indicates that the NW has successfully received the previously scheduled early assistance message, and a value of 0 means that the NW has not received the previously scheduled early assistance message. Vice versa, this application is not limited to this.

[0495] Information used to indicate whether an early assistance message is scheduled. Exemplarily, this field may be one bit, where a value of 1 indicates that the DCI schedules a transmission that carries early assistance information, and a value of zero means that the DCI schedules a transmission that does not carry early assistance information. Vice versa, this application does not limit this.

[0496] Information used to indicate whether the NW is scheduling the UE for a new transmission or a retransmission. Exemplarily, if the value indicated in this field has changed compared to the last received DCI scheduling the same HARQ process, the UE considers this to be a new transmission. Exemplarily, if the UE receives a DCI for scheduling an early assistance message transmission for the first time, the UE always considers this to be a new transmission regardless of the value indicated in this field.

[0497] Time domain resource information is used to indicate when the UE is scheduled to transmit.

[0498] Frequency domain resource information is used to indicate the frequency and bandwidth on which the UE is scheduled to transmit.

[0499] The HARQ process number is used to indicate the HARQ process used for scheduling transmission.

[0500] In some embodiments, a UE buffer may be defined for storing early assistance message data (such as RRC early assistance information messages). The buffer allows temporary storage of content of the early assistance message data for retransmission of the early assistance information.

[0501] In some embodiments, the conditions for cleaning or flushing the cache may include at least one of the following:

[0502] receiving positive feedback from the NW indicating that a previously sent RRC Early Assistance message has been successfully received by the NW;

[0503] The RACH process is completed;

[0504] A DCI for instructing the UE to perform new transmission on the HARQ process in which the RRC Early Assistance message is sent is received from the NW.

[0505] Through the embodiments of the present application, a specific MAC subheader or MAC CE or MAC SDU or MAC SDU segment or a specific RRC message or RRC message segment can be set to provide early auxiliary information for the base station. Without increasing the message size, the early auxiliary information is transmitted through the PUSCH, thereby solving the problem in the related technology of using logical channel identifiers to indicate auxiliary information during random access, and the limited number of coding points of the logical channel identifiers and poor flexibility.

[0506] According to another aspect of an embodiment of the present application, a terminal is provided for receiving configuration information related to early auxiliary information reporting from a base station; and sending a protocol data unit MAC PDU of a media access control layer to the base station according to the configuration information, wherein the MAC PDU includes a specific MAC subheader carrying an early auxiliary information field.

[0507] In an embodiment of the present application, the terminal may execute the steps in any of the above-mentioned terminal-side method embodiments.

[0508] According to another aspect of an embodiment of the present application, a base station is provided for sending configuration information related to early auxiliary information reporting to a terminal; receiving a media access control protocol data unit MAC PDU sent by the terminal according to the configuration information, wherein the MAC PDU includes a specific MAC subheader carrying an early auxiliary information field.

[0509] In an embodiment of the present application, the base station may execute the steps in any of the above-mentioned base station side method embodiments.

[0510] An embodiment of the present application further provides a computer-readable storage medium, in which a computer program is stored, wherein the computer program executes the steps of any of the above method embodiments when executed by a processor.

[0511] In an exemplary embodiment, the computer-readable storage medium may include, but is not limited to, various media that can store computer programs, such as a USB flash drive, a read-only memory (ROM), a random access memory (RAM), a mobile hard disk, a magnetic disk or an optical disk.

[0512] An embodiment of the present application further provides an electronic device, including a memory and a processor, wherein a computer program is stored in the memory, and the processor is configured to run the computer program to execute the steps in any one of the above method embodiments.

[0513] In an exemplary embodiment, the electronic device may further include a transmission device and an input / output device, wherein the transmission device is connected to the processor, and the input / output device is connected to the processor.

[0514] For specific examples in this embodiment, reference may be made to the examples described in the above embodiments and exemplary implementation modes, and this embodiment will not be described in detail herein.

[0515] Obviously, those skilled in the art should understand that the above modules or steps of the present application can be implemented by a general computing device, they can be concentrated on a single computing device, or distributed on a network composed of multiple computing devices, they can be implemented by a program code executable by a computing device, so that they can be stored in a storage device and executed by the computing device, and in some cases, the steps shown or described can be executed in a different order from that herein, or they can be made into individual integrated circuit modules, or multiple modules or steps therein can be made into a single integrated circuit module for implementation. Thus, the present application is not limited to any specific combination of hardware and software.

[0516] The above description is only the preferred embodiment of the present application and is not intended to limit the present application. For those skilled in the art, the present application may have various modifications and variations. Any modification, equivalent replacement, improvement, etc. made within the principles of the present application shall be included in the protection scope of the present application.

Claims

1. A method for reporting early auxiliary information, characterized in that: Applied to a terminal, the method comprises: receiving configuration information related to early assistance information reporting from a base station; A media access control layer protocol data unit MAC PDU is sent to the base station according to the configuration information, wherein the MAC PDU includes a specific MAC subheader carrying an early auxiliary information field.

2. The method according to claim 1, characterized in that: The configuration information includes: an explicit indication and / or an implicit indication for indicating whether to enable the specific MAC subheader.

3. The method according to claim 2, characterized in that The implicit indication includes at least one of the following: Msg4 Hybrid Automatic Repeat Request Confirmation HARQ-ACK automatic repeat configuration information; Configuration information related to temporary capability restrictions of multi-user identity module (MUSIM) terminals; Reduced capability RedCap terminal configuration information; Enhanced the ability to reduce eRedCap terminal configuration information; Random access channel RACH resource configuration information dedicated to early auxiliary information reporting; The mapping relationship between specific MAC subheader formats and RACH resources; Terminal capability information; Random access process trigger information; Initial access process trigger information.

4. The method according to claim 1, characterized in that: The configuration information is cell-based configuration information, RACH resource-based configuration information, or RACH resource set-based configuration information.

5. The method according to claim 1, characterized in that Receiving configuration information related to early assistance information reporting from a base station includes at least one of the following: Receiving system information carrying the configuration information from the base station, wherein the system information includes at least one SIB1 message or a SIBx information unit, and the SIBx information unit includes at least one system information block; receiving a broadcast message carrying the configuration information from the base station; receiving a multicast message carrying the configuration information from the base station; A radio resource control (RRC) signaling carrying the configuration information is received from the base station.

6. The method according to claim 1, characterized in that The specific MAC subheader includes at least one of the following: The flag bit of the specific MAC subheader; The message type field of the common control channel CCCH message; The early assistance information field.

7. The method according to claim 1, characterized in that The message type of the CCCH message includes at least one of the following: 48-bit CCCH or 64-bit CCCH1; For use with reduced capacity RedCap terminals or for use with non-RedCap terminals.

8. The method according to claim 1, characterized in that The indication method of the early auxiliary information field includes at least one of the following: The early auxiliary information field includes at least one bit of information, wherein each bit of information represents one early auxiliary information; The value of the early assistance information field is determined by a formula of the early assistance information field including at least one subfield, wherein each of the subfields represents one of the early assistance information, and the formula of the early assistance information field is determined based on the value of the at least one subfield and the number of candidate values ​​of each of the subfields; A logical channel identification index, wherein the logical channel identification index is used to indicate one or more of the early auxiliary information.

9. The method according to claim 8, characterized in that The formula for the early auxiliary information field includes: The value of the early auxiliary information field = the value of the first subfield + the value of the second subfield * the number of candidate values ​​of the first subfield + the value of the third subfield * (the number of candidate values ​​of the second subfield + the number of candidate values ​​of the first subfield) + ... + the value of the nth subfield * (the number of candidate values ​​of the n-1th subfield + ... + the number of candidate values ​​of the second subfield + the number of candidate values ​​of the first subfield)), where n is a positive integer.

10. The method according to claim 8, characterized in that The early auxiliary information includes at least one of the following: Indication information used to indicate whether the terminal supports or requests automatic retransmission of the physical uplink control channel PUCCH of Msg4 hybrid automatic repeat request confirmation HARQ-ACK; Indication information used to indicate whether the terminal capability of the terminal is temporarily restricted; Indication information used to indicate whether the terminal supports reduced capability RedCap; Indication information used to indicate whether the terminal supports enhanced reduction capability eRedCap.

11. The method according to claim 1, characterized in that: The MAC PDU includes multiple MAC sub-PDUs, wherein each of the MAC sub-PDUs is composed of one of the following: MAC subheader; MAC subheader and media access control layer service data unit MAC SDU; MAC subheader and control unit MAC CE of the media access control layer; MAC subheader and padding.

12. The method according to claim 1, characterized in that Sending a media access control protocol data unit MAC PDU to the base station according to the configuration information includes: In the third step of the four-step random access, or in the first step of the two-step random access, a medium access control protocol data unit MAC PDU is sent to the base station according to the configuration information.

13. A method for reporting early auxiliary information, characterized in that: Applied to a base station, the method comprises: Sending configuration information related to early assistance information reporting to the terminal; A medium access control protocol data unit MAC PDU is received, which is sent by the terminal according to the configuration information, wherein the MAC PDU includes a specific MAC subheader carrying an early auxiliary information field.

14. A terminal, characterized in that: The terminal is used to receive configuration information related to early auxiliary information reporting from a base station; and send a media access control layer protocol data unit MAC PDU to the base station according to the configuration information, wherein the MAC PDU includes a specific MAC subheader carrying an early auxiliary information field.

15. A base station, characterized in that: The base station is used to send configuration information related to early auxiliary information reporting to the terminal; receive a media access control protocol data unit MAC PDU sent by the terminal according to the configuration information, wherein the MAC PDU includes a specific MAC subheader carrying an early auxiliary information field.

16. A computer-readable storage medium, characterized in that: The storage medium stores a computer program, wherein the computer program executes the method described in any one of claims 1 to 13 when executed by a processor.

17. An electronic device comprising a memory and a processor, characterized in that: A computer program is stored in the memory, and the processor is configured to run the computer program to perform the method according to any one of claims 1 to 13.

Images