CN112242893B

CN112242893B - Information reporting method and equipment, and message receiving method and equipment

Info

Publication number: CN112242893B
Application number: CN202010407603.9A
Authority: CN
Inventors: 孙霏菲; 熊琦; 王轶; 吴敏
Original assignee: Samsung Electronics Co Ltd
Current assignee: Samsung Electronics Co Ltd
Priority date: 2019-07-17
Filing date: 2020-05-14
Publication date: 2024-05-31
Anticipated expiration: 2040-05-14
Also published as: CN112242893A

Abstract

The embodiment of the application provides a method and equipment for reporting information, a method and equipment for receiving information, wherein the method for reporting information comprises the following steps: receiving auxiliary scheduling information configuration and/or reporting instructions carried in system information; generating auxiliary scheduling information according to the auxiliary scheduling information configuration and/or reporting instruction; and reporting the auxiliary scheduling information through at least one message of an Msg1 message, an Msg3 message and a MsgA message. The application realizes the fast reporting of the auxiliary scheduling information.

Description

Information reporting method and equipment, and message receiving method and equipment

Technical Field

The present application relates to the field of wireless communications technologies, and in particular, to a method and an apparatus for reporting information, and a method and an apparatus for receiving a message.

Background

Rel-15 NR (New Radio) was designed primarily for enhanced mobile broadband (enhanced mobile broadband, eMBB) communications. Rel-16 is supported for some other applications, such as enhanced Ultra-Reliable Low Latency Communications, eURLLC, vehicle communications (vehicle to everything, V2X), etc., for system optimization and design. However, current NR systems have not been optimally designed for internet of things (Internet Of Things, ioT) devices. In Rel-17, the NR reduced version (NR-Light) is a very popular topic. It is expected that NR-Light will be optimally designed based on the NR system, for the low power consumption, small size, low cost, etc. of IoT devices. The new NR-light terminal type has the characteristics of smaller bandwidth, fewer receiving antennas and the like compared with the eMBB terminal with the minimum NR requirement. Furthermore, for the feature of IoT sparse small data packets, signaling interactions between the terminal and the network may be simplified, e.g., data transmission without establishing a radio resource control (Radio Resource Control, RRC) connected state, etc. Thus, signaling can be well simplified, and the characteristic of saving power consumption is achieved. How to support NR-Light users with smaller bandwidth and fewer transceiving antennas and other users simultaneously on the same carrier is also a problem to be solved.

Disclosure of Invention

Aiming at the defects of the existing mode, the application provides a method and equipment for reporting information, and a method and equipment for receiving information, which are used for solving the problem of how to realize fast reporting of auxiliary scheduling information.

In a first aspect, a method for reporting information is provided, which is applied to a user equipment UE, and includes:

Receiving auxiliary scheduling information configuration and/or reporting instructions carried in system information;

generating auxiliary scheduling information according to the auxiliary scheduling information configuration and/or reporting instruction;

and reporting the auxiliary scheduling information through at least one message of an Msg1 message, an Msg3 message and a MsgA message.

Optionally, the secondary scheduling information includes at least one of:

Reporting PHR in the transmission power space; reporting data volume information in the UE cache; and reporting the channel state information.

Optionally, the secondary scheduling information configuration includes at least one of:

configuration information of a power space, data volume DV configuration information in UE storage, configuration information of a buffer state and configuration information of channel state information CSI.

Optionally, reporting the indication, including at least one of:

The method comprises the steps of reporting PHR indication in a power space, reporting DV information indication in data quantity stored in UE, reporting BSR indication in a buffer status, and reporting CSI indication in a channel status.

Optionally, at least one of a control element MAC CE, a MAC header, a MAC sub-header, and a radio resource control RRC of the medium access control is indicated according to system information and/or a random access response RAR as a reporting format of the secondary scheduling information.

Optionally, reporting the auxiliary scheduling information through at least one of Msg1 message, msg3 message, msgA message, including:

Ordering the auxiliary scheduling information and the logic channels according to a priority rule, and generating an Msg3 message or MsgA message for reporting; the priority rule includes: the priority of the data in the cell radio network temporary identity C-RNTI MAC CE or the uplink common control channel UL-CCCH is preceding, the priority for at least one of BSR MAC CE in Msg3 message, BSR MAC CE in MsgA message, PHR MAC CE in Msg3 message, PHR MAC CE in MsgA message is following.

Optionally, the manner of determining the order of priority of the logical channels includes at least one of:

The order of priority of the logical channels is prescribed in advance in the protocol;

The priority order of the logic channels is configured through the broadcasted system information;

the order of the priorities of the logical channels is configured by the UE-specific RRC.

Optionally, the secondary scheduling information includes UE capability reporting, and the UE capability includes at least one of:

The method comprises the steps of maximum bandwidth supported by the UE, maximum receiving antenna number of the UE, maximum sending antenna number of the UE, maximum uplink MIMO layer number supported by the UE, maximum downlink MIMO layer number supported by the UE, UE storage space, early data EDT transmission capability supported by the UE, CSI capability reported by the UE in an Msg3 message, CSI capability reported by the UE in a MsgA message, PHR capability reported by the UE in an Msg3 message and PHR capability reported by the UE in a MsgA message.

Optionally, after reporting that the data amount information in the UE cache is not zero, the method further includes:

Receiving an uplink grant for data transmission in the UE cache, and sending uplink data according to the uplink grant;

the manner of indicating the uplink grant includes at least one of:

according to a temporary cell radio network temporary identifier TC-RNTI or a new data NDI indication in DCI wound by a random access response radio network temporary identifier RA-RNTI;

an indication in an Msg4 message or MsgB message.

In a second aspect, a method for receiving a message is provided, applied to a UE, including:

Detecting a first primary synchronization signal PSS included in a first synchronization signal physical broadcast channel block SSB according to a predefined rule;

And/or detecting a second primary synchronization signal PSS included in the second SSB according to the second synchronization signal grid;

After detecting the first primary synchronization signal PSS, detecting a first secondary synchronization signal SSS included in the first SSB, and receiving a first physical broadcast channel PBCH included in the first SSB;

after detecting the second primary synchronization signal PSS, detecting a second secondary synchronization signal SSS included in the second SSB, and receiving a second physical broadcast channel PBCH included in the second SSB.

Optionally, detecting the first primary synchronization signal PSS and/or the second primary synchronization signal PSS according to a predefined rule, including:

detecting a first primary synchronization signal PSS according to a first synchronization signal grid;

And/or detecting the second primary synchronization signal PSS according to the second synchronization signal grid.

Optionally, the first synchronization signal grid and the second synchronization signal grid bias are integer multiples of the subcarrier spacing.

Optionally, at least one of the first PSS, the first SSS and the first PBCH is detected or decoded according to at least one of the first sequence, the first wraparound code;

and/or detecting or decoding at least one of the second PSS, the second SSS and the second PBCH according to at least one of the second sequence, the second wraparound code.

Optionally, when the first PSS and the second PSS are the same, and the first SSS and the second SSS are the same, and the first PBCH and the second PBCH are different, the method further comprises:

receiving a first PBCH on a first resource;

And/or receiving a second PBCH on a second resource;

The second resource is adjacent to the frequency domain location of the first resource and/or the second resource is spaced apart from the time domain location of the first resource by a pre-set interval.

Optionally, when the first SSB and the second SSB are the same, the method further comprises at least one of:

Detecting a Physical Downlink Control Channel (PDCCH) for indicating a first System Information Block (SIB) and/or a PDCCH for indicating a second SIB according to a control resource set and/or a search space indicated in a PBCH, wherein the PDCCH for indicating the first SIB is wrapped by a first system information broadcast network temporary identifier (SI-RNTI), and the PDCCH for indicating the second SIB is wrapped by a second SI-RNTI different from the first SI-RNTI;

Detecting a PDCCH for indicating a first SIB according to a first control resource set and/or a first search space indicated in the PBCH;

And detecting the PDCCH for indicating the second SIB according to the second control resource set and/or the second search space indicated in the PBCH.

Optionally, according to the indication information in the PBCH, it is determined whether the cell supports the second set of control resources and/or the second search space.

In a third aspect, there is provided a UE comprising:

The first processing module is used for receiving auxiliary scheduling information configuration and/or reporting instructions carried in the system information;

the second processing module is used for generating auxiliary scheduling information according to the auxiliary scheduling information configuration and/or reporting instruction;

And the third processing module is used for reporting the auxiliary scheduling information through at least one message of the Msg1 message, the Msg3 message and the MsgA message.

In a fourth aspect, there is provided a UE comprising:

A fourth processing module, configured to detect, according to a predefined rule, a first primary synchronization signal PSS included in a first synchronization signal physical broadcast channel block SSB; and/or detecting a second primary synchronization signal PSS included in the second SSB according to the second synchronization signal grid;

A fifth processing module, configured to detect a first secondary synchronization signal SSS included in the first SSB and receive a first physical broadcast channel PBCH included in the first SSB after detecting the first primary synchronization signal PSS; after detecting the second primary synchronization signal PSS, detecting a second secondary synchronization signal SSS included in the second SSB, and receiving a second physical broadcast channel PBCH included in the second SSB.

The technical scheme provided by the embodiment of the application has at least the following beneficial effects:

Receiving auxiliary scheduling information configuration and/or reporting instructions carried in system information; generating auxiliary scheduling information according to the auxiliary scheduling information configuration and/or reporting instruction; and reporting the auxiliary scheduling information through at least one message of an Msg1 message, an Msg3 message and a MsgA message. Thus, the auxiliary scheduling information is reported rapidly.

Additional aspects and advantages of the application will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of the application.

Drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings that are required to be used in the description of the embodiments of the present application will be briefly described below.

Fig. 1 is a schematic diagram of a wireless communication system;

fig. 2 is a schematic diagram of a conventional 4-step random access procedure;

fig. 3 is a schematic diagram of a 2-step random access procedure;

fig. 4 is a flow chart of a method for reporting information according to an embodiment of the present application;

fig. 5 is a flowchart of a method for receiving a message according to an embodiment of the present application;

fig. 6 is a schematic diagram of a random access procedure according to an embodiment of the present application;

fig. 7 is a schematic diagram of SSB on a carrier according to an embodiment of the present application;

FIG. 8 is a schematic diagram of SSB and PBCH provided in an embodiment of the present application;

FIG. 9 is a schematic diagram of SSB and PBCH according to an embodiment of the present application;

Fig. 10 is a schematic diagram of finding a corresponding CORSET and a search space where a PDCCH is located according to an SSB indication provided in an embodiment of the present application;

Fig. 11 is a schematic diagram of a configuration of obtaining CORESET according to information bits in a PBCH in a detected SSB according to an embodiment of the present application;

fig. 12 is a schematic structural diagram of a UE according to an embodiment of the present application;

Fig. 13 is a schematic structural diagram of another UE according to an embodiment of the present application.

Detailed Description

Embodiments of the present application are described in detail below, examples of which are illustrated in the accompanying drawings, wherein like or similar reference numerals refer to like or similar elements or elements having like or similar functions throughout. The embodiments described below by referring to the drawings are illustrative only and are not to be construed as limiting the application.

As used herein, the singular forms "a", "an", "the" and "the" are intended to include the plural forms as well, unless expressly stated otherwise, as understood by those skilled in the art. It will be further understood that the terms "comprises" and/or "comprising," when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof. It will be understood that when an element is referred to as being "connected" or "coupled" to another element, it can be directly connected or coupled to the other element or intervening elements may also be present. Further, "connected" or "coupled" as used herein may include wirelessly connected or wirelessly coupled. The term "and/or" as used herein includes all or any element and all combination of one or more of the associated listed items.

In order to better understand and illustrate the solution of the embodiments of the present application, some technologies related to the embodiments of the present application are briefly described below.

Fig. 1 illustrates an example of a wireless communication system 100, wherein the wireless communication system 100 includes one or more fixed infrastructure elements forming a network distributed over a geographic area. The infrastructure elements may include APs (Access points), ATs (ACCESS TERMINAL, access terminals), BSs (Base stations), node-BS (Node BS), enbs (evolved nodebs), and gnbs (next generation Base stations), among others or other terms used in the art.

As shown in fig. 1, infrastructure elements 101 and 102 serve several MSs (mobile stations) or UEs or terminal devices or users 103 and 104 in a service area, which is a cell or a cell sector area. In some systems, one or more BSs are communicatively coupled (coupled to) to a controller forming an access network, the controller being communicatively coupled to one or more core networks. The present example is not limited to any one particular wireless communication system.

In the time and/or frequency domain, the infrastructure elements 101 and 102 transmit DL (Downlink) communication signals 112 and 113 to MSs or UEs 103 and 104, respectively. The MSs or UEs 103 and 104 communicate with the infrastructure elements 101 and 102 via UL (Uplink) communication signals 111 and 114, respectively.

The wireless communication system 100 is an OFDM (Orthogonal Frequency Division Multiplexing )/OFDMA (Orthogonal Frequency Division Multiple Access, orthogonal frequency division multiplexing access) system including a plurality of base stations including a base station 101, a base station 102, and a plurality of UEs including a UE103 and a UE104. The base station 101 communicates with the UE103 via UL communication signals 111 and DL communication signals 112.

When a base station has downlink packets to send to UEs, each UE obtains a downlink allocation (resource), e.g., a set of radio resources in PDSCH (Physical Downlink SHARED CHANNEL ). When the UE needs to send a packet in the Uplink to the base station, the UE obtains an grant from the base station, wherein the grant allocates a PUSCH (Physical Uplink SHARED CHANNEL ) containing a set of Uplink radio resources. The UE acquires downlink or uplink scheduling information from a PDCCH (Physical Downlink Control Channel ) specific to itself. Downlink or uplink scheduling information and other control information carried by the PDCCH are referred to as DCI (Downlink Control Information ).

Fig. 1 also shows different physical channels for examples of downlink 112 and uplink 111. The downlink 112 includes a PDCCH121, a PDSCH122, a PBCH (Physical Broadcast Channel ) 123, and a PSS (Primary Synchronization Signal, primary synchronization signal)/SSS (Secondary Synchronization Signal, secondary synchronization signal or secondary synchronization signal) 124. In 5G NR, PSS, SSS and PBCH together constitute an SSB (SS/PBCH block) 125.PDCCH121 transmits DCI120 to the UE, i.e., DCI120 is carried over PDCCH 121. PDSCH122 transmits downlink data information to UEs. The PBCH carries MIB (Master Information Block ) for UE early discovery and cell-wide coverage. The uplink 111 includes a PUCCH (Physical Uplink Control Channel ) 131 carrying UCI (Uplink Control Information, uplink control information) 130, a PUSCH132 carrying uplink data information, and a PRACH (Physical Random ACCESS CHANNEL ) 133 carrying Random access information.

In NR, the physical resources of the UE listening to the PDCCH in one slot are called a control resource set (Control Resource Set, CORESET). In addition, the base station configures the UE with aggregation levels (aggregation level, AL), and its corresponding search spaces (e.g., periods, etc.)

The wireless communication network 100 uses an OFDMA or multicarrier architecture, including AMC (Adaptive Modulation and Coding ) on the downlink, next generation single carrier FDMA (frequency division multiple access ) architecture or multicarrier OFDMA (Orthogonal Frequency Division Multiple Access ) architecture for UL transmissions. FDMA-based single carrier architectures include IFDMA (INTERLEAVED FDMA, interleaved frequency division multiple access), LFDMA (Localized frequency division multiple access), IFDMA, or DFT-SOFDM (DFT-spread OFDM, spread discrete fourier transform orthogonal frequency division multiplexing) of LFDMA. In addition, various enhanced NOMA (non-orthogonal multiple access ) architectures of OFDMA systems are included.

An OFDMA system serves a remote unit by allocating downlink or uplink radio resources, which typically contain a set of subcarriers over one or more OFDM symbols. Exemplary OFDMA protocols include the evolving LTE and 5G NR in the 3GPP UMTS standard, and the IEEE802.16 family of standards in the IEEE standard. The architecture may also include the use of transmission techniques such as MC-CDMA (multi-CARRIER CDMA ), MC-DS-CDMA (multi-CARRIER DIRECT sequence CDMA, multi-carrier direct sequence code division multiple access), OFCDM (Orthogonal Frequency and Code Division Multiplexing, orthogonal frequency code division multiplexing for one-or two-dimensional transmission). Or may employ simpler time and/or frequency division multiplexing/multiple access techniques, or a combination of these different techniques. In an alternative embodiment, the communication system may use other cellular communication system protocols including, but not limited to, TDMA (Time division multiple access ) or direct sequence CDMA (Code Division Multiple Access, code division multiple access).

In NR, it is divided into 3 states: an RRC connected state (connected), an RRC inactive state (inactive), and an RRC idle state (idle). Compared to LTE (Long Term Evolution ), NR has newly introduced RRC INACTIVE state, and signaling bearers can be restored and data connections established through an RRC connection restoration (RRC Resume) procedure. As shown in fig. 2, in the conventional 4-step random access procedure, the UE performs an RRC connection recovery request in Msg3, and the base station may perform RRC connection configuration for the UE in an Msg4 message at the earliest, and the UE may send uplink user data together with an RRC connection recovery complete (RRC resume complete) message in PUSCH on Msg5 at the earliest. For the 2-step random access procedure, as shown in fig. 3, the UE sends a random access preamble sequence and an RRC Resume request in MsgA, and the base station may configure RRC connection for the UE in MsgB message at the earliest, and the UE may Resume RRC connection in subsequent uplink grant to complete sending uplink user data at the earliest. However, some IoT traffic is packets with sparsity, e.g., transmitted once per second or more, 32bytes once, etc. If these UEs are kept in the connected state, on the one hand, storage and operation on the network side are increased, and on the other hand, the UEs need to frequently make some channel state measurements (measurement) in the connected state to keep the connected state, so that the power consumption of the UEs is increased. Then for such packet transmission, the best method is to put the UE in RRC inactive state or RRC idle state, and each small data arrives to make a random access request and carry the user data in Msg3 or MsgA. For fixed (stationary) users, the pilot part of Msg1 or MsgA may even be omitted because of the time advance (TIMING ADVANCE, TA), thereby achieving a more power efficient effect. This method is known as Early Data Transfer (EDT), and has been adopted in NB-IoT (narrow band IoT) and eMTC (ENHANCED MACHINE TYPE communication) systems. However, in NB-IoT and eMTC, the EDT is selected on condition that there is no data in the UE buffer (buffer), for example, when the EDT request is made, the Data Volume (DV) in the MAC CE of the power data volume report (Data volume and power headroom report, DPR) in NB-IoT is set to 0, and the data buffer report (buffer status report, BSR) of eMTC (if reported) is also 0. Then, this may limit the UE to determine that the size (transport block size, TBS) of the data block in the PUSCH allocated to the UE by the base station is greater than or equal to the data size in the current buffer when the UE chooses to perform EDT reporting, otherwise, it is necessary to perform data transmission after establishing the RRC connection. Wherein DV in NB-IoT represents the amount of data stored upstream in relation to MAC ENTITY that is available for transmission, which can be used to report before no establishment (Data Radio Bearer, DRB) and/or before no logical channel or MAC configuration information is received and/or before no RRC connection is established. The DPR reports the MAC CE for transmission in Msg3 as a common control channel (Common Control Channel, CCCH) service data unit (SERVICE DATA unit, SDU).

For the purpose of making the objects, technical solutions and advantages of the present application more apparent, the embodiments of the present application will be described in further detail with reference to the accompanying drawings.

Example 1

The embodiment of the application provides a method for reporting information, which is applied to UE, wherein a flow diagram of the method is shown in figure 4, and the method comprises the following steps:

Step S401, receiving auxiliary scheduling information configuration and/or reporting instruction carried in system information.

Step S402, generating auxiliary scheduling information according to the auxiliary scheduling information configuration and/or reporting instruction.

Step S403, the auxiliary scheduling information is reported through at least one of Msg1 message, msg3 message and MsgA message.

In the embodiment of the application, the configuration and/or reporting instruction of the auxiliary scheduling information carried in the system information are received; generating auxiliary scheduling information according to the auxiliary scheduling information configuration and/or reporting instruction; and reporting the auxiliary scheduling information through at least one message of an Msg1 message, an Msg3 message and a MsgA message. Thus, the auxiliary scheduling information is reported rapidly.

Optionally, the secondary scheduling information includes at least one of:

Transmitting power space report PHR (Power Headroom Report); reporting data volume information in the UE cache; and reporting the channel state information.

Optionally, reporting the indication, including at least one of:

Optionally, at least one of a Control Element (MAC) CE (Control Element), a MAC header, a MAC sub-header, and a radio resource Control RRC is indicated as the reporting format of the secondary scheduling information according to system information and/or a random access response RAR (Random Access Response).

ordering the auxiliary scheduling information and the logic channels according to a priority rule, and generating an Msg3 message or MsgA message for reporting; the priority rule includes: the priority of the data in the cell radio network temporary identity C-RNTI (CellRadioNetworkTemporaryIdentifier) MAC CE or the uplink common control channel UL-CCCH is preceding, the priority for at least one of BSR MAC CE in the Msg3 message, BSR MAC CE in the MsgA message, PHR MAC CE in the Msg3 message, PHR MAC CE in the MsgA message is following.

the manner of indicating the uplink grant includes at least one of:

According to the temporary cell radio network temporary identifier TC-RNTI (Temporary CellRadioNetworkTemporaryIdentifier) or the new data NDI indication in DCI winded by the random access response radio network temporary identifier RA-RNTI (Random Access CellRadioNetworkTemporaryIdentifier);

an indication in an Msg4 message or MsgB message.

The embodiment of the application provides a method for receiving a message, which is applied to UE, wherein a flow diagram of the method is shown in FIG. 5, and the method comprises the following steps:

Step S501, detecting a first primary synchronization signal PSS included in a first synchronization signal physical broadcast channel block SSB according to a predefined rule; and/or detecting a second primary synchronization signal PSS included in the second SSB according to the second synchronization signal grid.

Step S502, after detecting the first primary synchronization signal PSS, detecting a first secondary synchronization signal SSS included in the first SSB, and receiving a first physical broadcast channel PBCH included in the first SSB; after detecting the second primary synchronization signal PSS, detecting a second secondary synchronization signal SSS included in the second SSB, and receiving a second physical broadcast channel PBCH included in the second SSB.

In the embodiment of the application, the UE supporting different types in the same carrier is realized to receive the downlink shared message, and the signaling overhead is saved.

Optionally, the UE includes at least one of an NR UE, an NR-Light UE.

Detecting the first primary synchronization signal PSS according to a first synchronization signal grid;

And/or detecting the second primary synchronization signal PSS according to a second synchronization signal grid.

receiving a first PBCH on a first resource;

And/or receiving a second PBCH on a second resource;

The above embodiments of the present application will be described in full detail by the following examples:

in a first aspect, secondary scheduling information is reported.

For NR terminals, there may be more urgent traffic (e.g., URLLC traffic) in the buffer and not very urgent eMBB traffic, or different IoT traffic types with different latency requirements. Then some emergency services may be performed by EDT and other services may be sent after the RRC connection is established. Or may support cutting (segmentation) larger blocks of data into multiple blocks for EDT transmission separately.

In addition, in order to better allocate appropriate resources for uplink data transmission as soon as possible, the base station needs to know information such as channel status, uplink transmit power space (power header), and the amount of data in the buffer at present. Then at least one of the information used for the secondary scheduling described above may be in either Msg3 or MsgA or Msg 1. The method can enable the base station to configure proper scheduling information (such as proper TBS, MCS (modulation and coding scheme), TPC (transmission power command) and the like) as soon as possible so as to allocate the next data scheduling following the Msg1, msg3 or MsgA, thereby achieving the effects of improving transmission efficiency, reducing access delay, reducing power consumption of the UE and the like.

Optionally, the secondary scheduling information is at least one of: and reporting the transmission power space, reporting the data quantity information in the buffer and reporting the channel state information.

Optionally, the auxiliary scheduling information configuration and/or reporting indication sent in the system information (system information, SI) specifically includes at least one of the following: configuration information of a power space, indication of power space reporting (PHR), configuration information of a data volume (buffer status and/or DV) in a UE storage, reporting indication of a BSR and/or DV by the data volume information in the UE storage, configuration information of channel state information, and reporting indication of channel state information (channel status information, CSI). In one example, configuration information (secondary scheduling information configuration) is received for secondary scheduling information (e.g., PHR, BSR, DV, CSI, etc.), that is, indicating that the reporting information may be reported or is required to be reported.

Alternatively, as shown in fig. 6, the UE receives the secondary scheduling information configuration from the base station, the UE transmits a random access request to the base station, and the base station transmits Msg2 (RAR) to the UE. In one example, a trigger indication to report secondary scheduling information is sent in a PDCCH or RAR MAC CE or MAC header (header) or MAC sub-header (subheader) that schedules RARs. Then, the UE sends triggered secondary scheduling information in Msg3 according to the configuration information and/or trigger indication in the PDCCH of Msg2 or scheduling Msg 2. Similarly, for two-step random access (two step random), the triggered indication of reporting the secondary scheduling information and the triggered secondary scheduling information may be sent in the check-in sequence in PUSCH or MsgA of MsgB corresponding to the RAR and MsgA corresponding to the Msg3, respectively.

Alternatively, the user data may be transmitted in Msg3 or MsgA. At this time, if there are additional bits in Msg3 or MsgA to report DV or BSR, the pending data in the UE buffer may be reported (data available for transmission). The DV or BSR may be sent prior to RRC connection establishment.

Optionally, the secondary scheduling information may design one or more MAC CEs or MAC headers or MAC sub-headers or RRC, and indicate, through the system information and/or RAR, one of the RRC, the MAC CEs or MAC headers or the MAC sub-headers as a reporting format, where the reporting format includes RRC, or MAC information, including: MACCE or MAC header, or MAC subheader. Specifically, DPR as in NB-IoT systems can be designed, including PH (power headroom) of 2 or 4 bits and DV (data volume) of 4 bits in one MAC CE. Wherein the PH of 2 or 4 bits is configured according to the system information.

Or a separate MAC CE, such as a BSR MAC CE and/or a PHR MAC CE, may be designed and reported in Msg3 or MsgA before receiving the logical signaling configuration and/or BSR configuration and/or PHR configuration and/or completing RRC connection establishment. The logical channel group (logic channel group, LCG) ID is set to a default value in the BSR MAC CE, or the first few bits of the BSR reported in Msg3 or MsgA are designed to hold the value "R". For PHR reporting, it may be predefined that only PHR of the current cell is reported in Msg3 or MsgA, and PCMAX, c for indicating the maximum transmission power is not reported. Similarly, the first few bits of PHR reported in Msg3 or MsgA are designed to hold the value "R".

Or the auxiliary scheduling information may be reported in an RRC message. For example, one or more Information Elements (IEs) may be added to the RRC message transmitted in Msg3 or MsgA to report one or more secondary scheduling information.

In a second aspect, logical channel priority.

Alternatively, the BSR trigger condition may include: when the system information includes an indication of reporting a BSR (or DV) and/or PHR in Msg3 and/or MsgA, or triggering the Msg3 to report the BSR (or DV) and/or PHR by the RAR.

If reporting of the BSR (or DV) and/or PHR is initiated, the UE may report the BSR (or DV) and/or PHR in Msg3 or MsgA. Its priority is after the data in C-RNTI MAC CE or UL-CCCH.

Specifically, the priorities of the logical channels are in the following order (highest priority listed first):

-data in C-RNTI MAC CE or UL-CCCH;

-in Msg3 (or MsgA) for BSR MAC CE and/or in Msg3 (or MsgA) for PHR MAC CE;

-configuring an authorization acknowledgement (Configured Grant Confirmation) MAC CE;

BSR MAC CE other than padding BSR not transmitted in Msg3 (or MsgA);

-single Entry (SINGLE ENTRY) PHRMAC CE or Multiple Entry (PHR MAC CE) not transmitted in Msg3 (or MsgA);

-data of any logical channel except UL-CCCH data;

-a (Recommended bit rate query) MAC CE for indicating a recommended bit rate query;

-MAC CE filling (padding) BSR.

Specifically, if the size (transport block size, TBS) of the data block corresponding to the PUSCH used for transmitting Msg3 or MsgA is enough, the data in the corresponding Buffer is selected according to the order of the priority of the logical channels, and is put in the HARQ entity (entity) of Msg3 or MsgA until the TBS is occupied, and is transmitted on the PUSCH. Alternatively, the priority order of the logical channels may be defined in advance in the protocol, or configured by broadcasted system information or UE-specific RRC. For example, a plurality of logical channel priorities are predefined, and one of them is configured through an RRC message. In addition, the priority order of the logical channels may be determined according to the UE category (including UE capability, UE type/category, etc.). For example, a different logical channel priority order is employed for a particular UE (e.g., NR-Light UE) than for other UEs. Or a specific logical channel order is adopted when a specific RRC message is transmitted. For example, when one or several of RRCSetupRequest, RRCResumeRequest, RRCReestablishmenetRequest, RRCEarlyDataRequest messages are sent, the priority of the BSR follows the data in C-RNTI MAC CE or UL-CCCH, otherwise after the configuration grant acknowledges the MAC CE.

The user data may be placed in an RRC message (control plane method) or transmitted on any logical channel outside the RRC that transmits UL-CCCH data (user plane method) before the RRC connection is not established. If the TBS in PUSCH for Msg3 or MsgA is not sufficient to carry all user data, then the UE may report DV or BSR in Msg 3. The base station may send additional uplink grants to the UE after receiving a BSR or DV that is not zero. The UE sends the remaining uplink data with the additional uplink grant.

In the random access process of step 4, the UE acquires a temporary (temporal) TC-RNTI in the RAR, and after transmitting Msg3, if a non-zero amount reported in DV or BSR is received by the UE, if an uplink grant for indicating a new transmission is received, the UE continues to transmit the remaining uplink data on the uplink grant. Wherein, the uplink grant may be an Msg3 retransmission or used for the rest of the data transmission, indicated by a new data indication (new data indicator, NDI) field in the DCI. The uplink grant may be sent over the PDCCH search space and/or CORESET of the RAR and/or Msg3 retransmission by TC-RNTI wrapping.

Similarly, in the 2-step random access procedure, the UE carries data and/or transmits auxiliary information of the BSR (or DV) in MsgA. After receiving MsgA, the base station may send an uplink grant around the RA-RNTI to the UE. Similarly, PUSCH retransmission with the uplink grant MsgA or MsgA retransmission may be indicated by a new data indication (new data indicator, NDI) field in the DCI or for the rest of the data transmission. The uplink grant may be sent on PDCCH search space and/or CORESET of the RAR and/or Msg3 retransmission.

Or the base station may choose to send the contention resolution (contention resolution), i.e. Msg4 or MsgB message first, but not send the UE a configuration of RRC establishment or a message of RRCearlyDatacomplete. After contention resolution, the base station may transmit a new DCI wrapped with the TC-RNTI to the UE. Or may carry an additional UL grant in Msg4 or MsgB messages for transmission of the remaining uplink data. The method can effectively avoid the system performance loss and the power loss of the UE caused by long-time collision of a plurality of UEs.

After receiving the BSR or the uplink buffer indicated by DV in PUSCH as 0, the base station sends an RRC message identifying EDT completion to the UE. After the UE receives the EDT completion message, the UE returns to the Idle or inactive state.

In addition, in order to accelerate transmission of uplink data, one or more HARQ processes may be supported and HARQ process numbers may be indicated through the PDCCH. The number of HARQ processes may be configured by the base station. Then, at this time, the base station considers that all uplink transmissions are completed only after the data in all HARQ processes are completed.

In the above process, the base station may choose to send the information of RRC connection establishment to the UE at any time.

From the outside, in order to avoid that the UE listens to the PDCCH for a long time and cannot decode successfully, or the base station does not receive the uplink message sent by the UE, a timer may be configured for the UE. The timer may be the maximum number of retransmissions or absolute time. And when the timer expires, the UE considers that the random access process fails or the uplink HARQ process which does not receive the ACK fails.

In a third aspect, UE capability reporting.

Rel-15/16 has to be required for NR terminals to have a bandwidth of 100MHz/400MHz (frequency range 1/2Frequency Range,FR1/2) and a minimum of 4 or 2 receive antennas, etc. These must make it difficult for the cost, power consumption, and size of the terminal to meet the requirements of IoT applications. Thus, NR-Light would design a Light version of the UE type/capability. Such as one or more of the following: smaller bandwidth, fewer receive antennas, smaller data storage capacity, etc. Since current NR base stations understand that UEs support a minimum of 100MHz bandwidth, a UE may not be able to access the network for NR-Light that supports smaller bandwidths. For example, before the UE reports its capability, it cannot receive system information, cannot listen to PDCCH, cannot receive RAR and/or MsgB, cannot transmit Msg3, cannot transmit MsgA (pilot and/or data part), etc. In the current NR system, the UE may report UE capability at Msg5 (on the first PUSCH after RRC connection is established) at the earliest. Thus, to support both NR-Light and other NR UEs, the base station's scheduling of all UEs (eMBB UE and NR-Light UEs) is limited to the minimum bandwidth possible for the NR-Light UEs. Due to a lack of diversity gain or a reduced number of receive antennas, the overall random access performance will be affected.

Optionally, the secondary scheduling information further includes UE capability reporting, where the UE capability includes at least one of: the maximum bandwidth supported by the UE, the maximum number of receiving and/or transmitting antennas of the UE, the maximum uplink and/or downlink MIMO layer number supported by the UE, the UE storage space, the early data transmission capability supported by the UE, the CSI capability reported by the UE in Msg3/MsgA, and the PHR capability reported by the UE in Msg 3/MsgA. Furthermore, even if some UE capabilities are reported during random access, there is still a need (based on the requirements or signaling or configuration information of the base station), and the UE may report more detailed capabilities on the subsequent uplink channel. In particular, the UE may report to the base station or the core network whether it is an NR-light UE. The UE may report directly to the core network (transparent to the base station) via NAS messages, or the base station may report to the core network after reporting to the base station by the UE. The core network, knowing the UE's capabilities, may notify one or more base stations in a tracking area (TRACKING AREA). The UE may be registered. After acquiring the information, the base station may use the information to select an appropriate paging information resource for transmission to a UE in an idle state or an inactive (inactive) state that may reside in the cell. In addition, during the communication between the base station and the UE, the UE may be further restricted as required. For example, no voice-over service configuration is performed, no cell handover is supported, and the like. Therefore, the waste of system resources can be avoided, the power consumption of the UE can be reduced, and the system performance is ensured.

For each possible combination of the above capabilities (including one or more capabilities), it may be possible to refer by 1 bit or more to whether a particular capability is supported and in particular to support one or more of several capabilities. E.g., whether 20MHz bandwidth is supported, and/or whether 1 or 2 antennas are supported. Or may be a combination that supports a predefined combination. E.g. whether 20MHz bandwidth is supported, 2 receive antennas, etc. The predefined combination may be related to the frequency band (operation band) in which it is currently operating. For example, for certain particular frequency bands (e.g., bands n7, n38, n41, n77, n78, n79 defined in TS 38.101), the particular combination may be {1 antenna, 20MHz bandwidth }, while particular combinations of other frequency bands are {2 antennas, 20MHz bandwidth } and/or {1 antenna, 20MHz bandwidth }. In another example, one or more UE capabilities are pre-designed for different frequency bands, such as FR1 and FR2, where each UE capability is one or more specific capabilities. For example, 2 UE capabilities (or one of 2) are designed for FR 1: UE capability 1 includes 2 receive antennas, 20MHz bandwidth, UE capability 2 includes 1 receive antenna, 20MHz bandwidth. 2 UE capabilities (or one of 2) are designed for FR 2: UE capability 1 includes 40MHz bandwidth and UE capability 2 includes 100MHz bandwidth. UE capabilities differ for different frequencies. Then the same bits (bits or Information Elements (IEs)) may be used to represent different UE capabilities (including UE capability combinations) for different operating bandwidths. This saves signaling overhead. Furthermore, different uplink and/or downlink decoding performance may result from different UE capabilities. Thus, after knowing the UE capabilities, the base station can select an appropriate schedule to guarantee decoding performance. Alternatively, different UE capabilities may be reported in different bits and/or different formats (including using different methods), respectively. More detailed UE capability reporting may require more bit information.

The specific solutions for reporting UE capabilities are as follows. In a specific implementation, one or more of the following methods may be used in combination to achieve the final capability reporting. The base station may also configure a method for reporting UE capabilities in one or more of the following methods. In addition, the same or different UE capability reporting methods may be employed for the 4-step random access and the 2-step random access.

The method comprises the following steps: different random access resources, i.e. resources of different Msg1 and/or MsgA, are configured for NR-Light UEs and eMBB UE.

Optionally, the resources of MsgA include the sequence resources of MsgA and/or PUSCH part resources of MsgA. Its Msg1 and/or MsgA resources include at least one of: RACH opportunity (occision), time domain of PRACH channel, frequency domain resource of PRACH channel, number or set of sequences (preambles) of PRACH channel, and resource for transmitting PUSCH part in MsgA, including one or more of the following: time domain, frequency domain, antenna ports, pilot sequences, spread spectrum codewords, etc. Wherein the PRACH channel comprises a transmission Msg1 and/or MsgA sequence part.

The NR-Light UE and other UEs may share the same PRACH and/or RACH configuration and/or configuration for beam management (beam management), indicating the portion of resources occupied by the NR-Light UE. The base station may configure resources occupied by the NR-Light UE to reserved resources and/or resources for non-contention access; or the base station may configure the resources occupied by the NR-Light UE as a subset for other UEs. At this time, if the resources for the NR-Light UE are selected for other UEs using the portion, then the subsequent Msg2/3/4 or MsgB will be treated by the base station as the NR-Light UE, and its scheduling will be limited. This approach may reduce the collision probability of PRACH resources without knowing the NR-Light UE and other UE duty cycles.

Alternatively, a set of dedicated resources may be configured independently for the NR-Light UE. Then it may be decided by the base station whether to configure to be shared with other UEs or not. Further, the system information of the NR-Light UE may be different from other UEs.

The second method is as follows: UE capabilities are reported in Msg3 and/or MsgA.

Optionally, an information element (information element, IE) of UE capability may be added in the RRC message sent in PUSCH of Msg3 or MsgA. For example in at least one of the following messages: RRCSetupRequest, RRCResumeRequest, RRCReestablishmenetRequest, RRCEarlyDataRequest messages. Taking RRCSetupRequest messages as an example, the maximum bandwidth supported by the UE, the number of antennas can be added in the RRC message. CSI, BSR, etc. may also be reported directly.

RRCSetupRequest message

Or a MAC CE for supporting UE capabilities may be designed, or by a specific setting in a MAC header or MAC sub-header (e.g. a specific value of LCID or a specific value of reserved bit (R)), or the UE type of NR-Light may be bound to a certain MAC CE or MAC header or MAC sub-header. For example, NR-Light UE would report PDR in Msg3 or Msg A, while other UEs would not report PDR. Thus, if the base station receives a specific MAC CE or MAC header or MAC sub-header in Msg3 or MsgA, the bandwidth supported by the UE is considered to be limited, and then an appropriate bandwidth Block (BWP) and resources of the uplink and downlink physical channels are configured for it in the subsequent random access configuration information. The UE will also restrict the subsequent transmission of Msg4/MsgB to the bandwidth that the UE can support. The initial (initial) configuration and/or default (default) BWP may be larger than the maximum bandwidth supported by the NR-Light UE, but the base station may restrict all uplink and downlink transmissions to within the bandwidth supported by the NR-Light UE before resolving the NR-Light UE and other UEs.

Optionally, depending on the traffic demand of IoT, various NR-Light UEs with different capabilities may be defined, e.g., supporting a maximum of 5mhz,10mhz bandwidth, supporting a maximum of 2 or 4 antennas or MIMO layers, etc. The above method one might only roughly tell if it is an NR-Light UE, reporting its specific capabilities further in Msg3/MsgA and/or in subsequent UE capability reporting messages. At this time, the method one and the method two may be used simultaneously. Or if more than one UE capability is to be reported, PRACH resources (e.g., time, frequency, code, etc. resources) may be divided into more than two groups, each group corresponding to one UE capability. Since MsgA includes both preamble and PUSCH parts. Then for a 2-step random access procedure, the reporting of UE capabilities may be performed by any combination of time, frequency, code resources grouping of different preambles (i.e. PRACH), and/or information carried in PUSCH.

In a fourth aspect, a method of downlink shared (common) message reception.

Because the capability of the NR-Light UE is limited, the base station may configure a set of downlink shared messages and/or uplink shared channels (e.g., PRACH) for the NR-Light UE alone, or limit the bandwidth of the downlink shared channels/signals and/or uplink shared channels/signals sent to legacy NR UEs to be within the capability of the NR-Light UE. The former may sacrifice some downlink frequencies, and the latter may sacrifice performance such as coverage of a general UE. Some methods of receiving the downlink shared message are listed below.

The method comprises the following steps: a set of SSBs is sent for each of a general NR UE and NR-Light UE. As shown in fig. 7, SSB1 (first SSB) is SSB for a general NR UE and SSB2 (second SSB) is SSB for an NR-Light UE on one carrier. In order not to affect access by legacy NR UEs, SSB2 may be placed on a different synchronization signal grid than that used to detect SSB 1. For NR, 3 different synchronization signal grids are defined for different carrier frequency ranges, as shown in table 1. Then, in order not to affect access of legacy (legacy) UEs (legacy UEs will not search for new SSBs for NR-Light UEs), the synchronization signal grid corresponding to NR-Light UEs is different from NR UEs. For example, as shown in table 2, the synchronization signal grid for NR-Light adds one variable P1, P2, P3 for each frequency domain range based on the frequency domain position of the synchronization signal grid for general NR. Wherein, P1, P2, P3 may be equal or unequal. In one example, p1=600 khz, p2=720 khz, p3=8.64=mhz, in which case the synchronization signal grid of NR-Light may be furthest from the synchronization signal grid of NR. In addition, a new set GSCN of NR-Light can be defined.

TABLE 1 NR synchronization signal grid

Note that: GSCN (Global Synchronization Channel Number) is a global synchronization signal.

TABLE 2 NR-Light synchronization signal grid

/>

As shown in fig. 7, the NR UE employs a synchronization grid 1 and the NR-Light UE employs a synchronization grid 2. At this time, both the first SSB for the NR UE and the second SSB for the NR-Light UE are transmitted on carrier a. Wherein SSBs for two UE types may be the same cell (i.e. the same cell Identity (ID)), or may be seen as different cells (unused cell IDs). If the NR UE and NR-Light UE can be transmitted from the same downlink base station on the same carrier, then it is preferable that the service be orthogonal to the OFDM subcarriers of both UE types or be aligned with the PRBs for both UE types. That is, the center frequency point deviation of the two SSBs is an integer multiple of the subcarrier spacing (as shown in tables 1 and 2, the predefined frequency deviation is an integer multiple of the corresponding subcarrier spacing). If the center frequency points of the two SSBs are not integral multiples of the RBs, the subcarrier offset of the SSBs can be indicated by the kssb indicated in the PBCH, so that the RBs of the system corresponding to the two SSBs are aligned, and the spectrum utilization rate is improved. At this time, pointA (common RB 0) may be configured identically or differently for both UEs.

Alternatively, with the UE's perspective, the two systems are transparent to each other. That is, the NR UE need not be aware of the presence of the NR-Light UE, and the NR-Light UE need not be aware of the location of the SSB of the NR system and the presence of the NR UE. At this time, the position of avoiding the shared channel may be configured by the base station. This avoids additional signaling overhead.

Alternatively, the base station may inform the SSB serving another UE of the presence of other shared channels, such as PRACH resources, etc. May be sent on a broadcast by RRC message or on a UE-specific downlink channel. This has the advantage that the UE can be further made aware of the presence of SSBs or other shared channels additionally serving other UEs, and can avoid broadcast channels/signals for other UEs according to predefined or configured rules when the UE transmits or receives.

In the first method, different sequences and/or wraparound codes can be designed for the PSS/SSS/PBCH, so as to further reduce the false alarm probability between two UEs. But for a UE supporting two systems two sets of receiver algorithm implementations are required. Different systems can be effectively distinguished by different synchronous signal grids, and for a terminal supporting two systems, two types of cells can be searched by adopting one set of receiver algorithm, so that the complexity can be reduced.

And a second method is to send a set of primary/secondary synchronization signals, but send PBCH (first PBCH) and PBCH-Light (second PBCH) for NR UE and NR-Light UE respectively. Wherein, PBCH-Light is sent in the predefined time domain, frequency domain resource. For example, different time domain positions at the same frequency domain position of the SSB of the NR. As shown in fig. 8, the first SSB is an SSB of NR, and the second PBCH is a PBCH for NR-Light, and its frequency domain position is predefined as a frequency domain position (high frequency or low frequency) adjacent to the first SSB. In time, in order to reduce unnecessary downlink storage of the UE and reserve enough time for the UE to adjust its RF center frequency point, the location of the second PBCH is at the next PBCH time domain location. For example, for 15kHz and carrier frequencies less than 3GHz, if a first SSB is on symbol 2,3,4,5, then a corresponding second PBCH is on symbol 9, 11. And so on.

Alternatively, as shown in fig. 9, for 30kHz and carrier frequencies less than 3GHz, or for 120kHz and carrier frequencies greater than 6GHz, if the first SSB is on symbol 4,5,6,7, then the corresponding second PBCH is on symbol 9, 11. If the first SSB is on symbols 8-11, then the corresponding second PBCH is on symbols 3,5 of the next slot. And so on.

Alternatively, the second PBCH may be at different time-domain locations in the same frequency domain as the NR SSB, for example, two symbols before or after the NR SSB, or a time slot before or after the NR SSB (e.g., 5ms or 10 ms), etc. This also has some effect on other signals of the NR, such as CORESET a 0.

Alternatively, it is transmitted on a different frequency domain resource (predefined in the protocol, such as a frequency domain location adjacent to the first SSB, but occupying the same symbol) of the SSB of the NR. Thus, when the UE detects PSS/SSS, PBCH in other frequency domain locations cannot be stored, which makes detection of the UE difficult.

Method three, NR-Light UE shares synchronization signal and physical broadcast channel Block (Synchronization Signal/PBCH Block, SSB) with NRUE, but sends a set of SIB1-NL, SIB2-NL, …, etc. for NR-Light UE alone. NL is NR-Light.

Two specific schemes of the third method.

Scheme 1: the NR-Light UEs share control resource set 0 (Control Resource Set, CORESET 0) and/or search space (SEARCH SPACE) with the NR UEs, but the base station sends two PDCCHs respectively, indicating different PDSCH bearers SIB1 and SIB1-NL respectively. The base station instructs the DCI of different SIB1 to wrap with different SI-RNTI. In addition, different sized DCIs may also be designed for NR-Light for distinguishing PDCCHs indicated to NR-Light from other UEs.

Optionally, as shown in fig. 10, the UE finds a corresponding CORSET0 and a search space where the PDCCH is located according to the SSB indication, and the UE monitors the PDCCH. To distinguish different DCIs, NRUE and NR-Light UE monitor different SI-RNTIs (configured in the system in advance) respectively. NRUE successfully decodes DCI1 wrapped with SI-RNTI1, indicating PDSCH1, where PDSCH1 carries SIB1 of NR UE. NR-LightUE successfully decodes DCI2 wrapped by SI-RNTI2, indicating PDSCH2, wherein PDSCH2 carries SIB1-NL of NR-Light UE. Wherein, DCI1 and DCI2 may be transmitted on the same search space or different search spaces in time.

Optionally, different monitoring window (monitoring window) lengths and/or starting positions for SIB1 detection are defined or configured for the NR-Light UE. For example, a longer monitoring window (e.g., 4 slots or 8 slots) is defined for the NR-Light UE, thereby providing more opportunities to transmit SIB1.

Alternatively, the above scheme may be an RNTI for paging (paging) for NR-Light UEs for distinguishing from other UEs. This method can also be applied to the transmission of common information in bypass (sidelink). The method of adopting different RNTI for common channel transmission can effectively avoid false alarm (FALSE ALARM) of PDCCH, thereby reducing the power consumption of UE. The different RNTIs may provide a more flexible configuration for the base station than configuring different sets of control resources, the base station transmitting PDCCH indicating PDSCH for system information of NR-Light UEs and other UEs in particular on different time-frequency resources.

Scheme 2: in order to reduce the false alarm probability of the UE PDCCH, different CORESET 0 and/or search spaces are defined or configured for NR-Light UEs and NR UEs. In particular, the second CORESET 0 and/or the second search space may be indicated in the MIB and/or defined according to predefined rules. Because of the reserved bits in the MIB, the table in the NR MIB corresponding to the bits indicating COREST0 and the search space can be extended. That is, the NR UE's COEST 0 and/or search space corresponds one-to-one with the NR-Light's COEST 0-NL and/or search space. NR UE uses the original table, and NR-Light UE uses the extended table for interpretation.

The NR-Light UE will take CORESET-NL as the initial BWP, will listen for pages in CORESET-NL, and/or search for PDCCH indicating RAR/MsgB, etc.

For both schemes, the base station may configure CORESET and/or search space in SIB1-NL where the PDCCH for transmitting other system information is located.

Alternatively, schemes 1 and 2 above may be used in combination, i.e., defining different RNTIs and configuring the same or different CORESET s 0 and/or searched spaces (including at least one of periodicity, aggregation level (aggregation level)).

Alternatively, NR-LightUE can determine whether the cell supports NR-Light UE based on the indication information (e.g., reserved bits) in the PBCH.

Optionally, for method one, if the information indicates that the cell supports NR-Light UEs, the NR-Light UEs obtain an initial BWP of the cell, CORESET0, and a search space for SIB1 scheduling according to information bits in system information indicating a control resource set and a search space, and a pre-defined CORESET0 and search space table. The NR-Light listens for a second SI-RNTI of the NR-Light UE on the search space.

Optionally, for method two, if the information indicates that the cell supports NR-Light UEs, the NR-Light UEs obtain initial BWP, CORESET0-NL for NR-Light UEs and search space for SIB1 scheduling according to information bits in system information indicating a control resource set and a search space, and a pre-defined CORESET-NL and/or search space table for NR-Light. The search space may also be used for other downlink public information, such as PDCCH for scheduling RAR, paging, other system information, and so on.

If the indication information in the PBCH does not indicate support for the NR-Light UE (e.g., no second SI-RNTI and/or no second CORESET a and/or search space), the NR-Light UE considers the cell to prohibit NR-Light UE camping (camp on).

The method four: NR-Light UEs share other minimum system information (other system information, OSI) with NRUE other than SIB 1.

To reduce the impact on NR UE and reduce the load of initial BWP, the configuration of RMSI-NL, such as SI-SchedulingInfo-NL, etc., may be configured separately in SIB 1. May be the same as RMSI or different from that used for NR. Or additional NR-Light may be configured for detecting CORESET-NL and/or search space of RMSI-NL.

As shown in fig. 11, the NR-Light UE obtains CORESET a configuration of 0 from the detected information bits in the PBCH in the SSB and listens CORESET a to SIB1 for NR-Light. Wherein the SIB1 may be SIB1 shared with the NR UE, e.g. joining a new information element (information element, IE) indication CORESET-NL and/or a corresponding search space. Or the SIB1 is SIB1-NL indicated by NR-Light UE (any of methods one to three), at this time, DCI of SIB1 used for other NR UE can be effectively reduced and detected through different RNTI, thereby avoiding wasting PDSCH channels for decoding the indication, and further saving UE power consumption. In SIB1, the NR-Light UE obtains a new CORESET-NL and/or a corresponding search space, and listens to the PDCCH at CORESET-NL and according to the corresponding search space, obtains DCI3 indicating PDSCH3 of the bearer RMSI-NL. For NR UE, the PDCCH is still monitored on CORESET0, DCI2 is obtained indicating PDSCH2 carrying RMSI-NL.

Alternatively CORESET-NL may have different frequency domain resources than CORESET. The NR-Light UE will take CORESET-NL as the initial BWP, will listen for pages in CORESET-NL, and/or search for PDCCH indicating RAR/MsgB, etc.

To reduce the power consumption of the UE, it may be indicated in SIB1 whether the cell supports NR-Light UEs. Dedicated barring (barring) information may be configured for NR-Light UEs. Or if the NR-Light UE does not receive any configuration information of the NR-Light UE, the cell is considered not to support NR-Light. The NR-Light UE cannot camp on the cell.

And a fifth method: NR-Light UE shares SIB1 and OSI with NRUE. Dedicated information for NR-Light UE configuration may be added in OSI.

Optionally, for methods four and five, it may also be indicated in the PBCH (MIB information) whether the cell supports NR-Light UEs to save UE power.

Example two

Based on the same inventive concept as the previous embodiment, the embodiment of the present application further provides a UE, and a schematic structural diagram of the UE is shown in fig. 12, and the UE70 includes a first processing module 701, a second processing module 702, and a third processing module 703.

A first processing module 701, configured to receive an auxiliary scheduling information configuration and/or reporting instruction carried in system information;

the second processing module 702 is configured to generate auxiliary scheduling information according to the auxiliary scheduling information configuration and/or reporting instruction;

The third processing module 703 is configured to report the auxiliary scheduling information through at least one of an Msg1 message, an Msg3 message, and a MsgA message.

Optionally, the secondary scheduling information includes at least one of:

Optionally, reporting the indication, including at least one of:

Optionally, the third processing module 703 is configured to sort the auxiliary scheduling information and the logical channels according to a priority rule, and generate an Msg3 message or MsgA message for reporting; the priority rule includes: the priority of the data in the cell radio network temporary identity C-RNTI MAC CE or the uplink common control channel UL-CCCH is preceding, the priority for at least one of BSR MAC CE in Msg3 message, BSR MAC CE in MsgA message, PHR MAC CE in Msg3 message, PHR MAC CE in MsgA message is following.

Optionally, after reporting that the data amount information in the UE cache is not zero, the third processing module 703 is configured to receive an uplink grant for data transmission in the UE cache, and send uplink data according to the uplink grant; the manner of indicating the uplink grant includes at least one of: according to a temporary cell radio network temporary identifier TC-RNTI or a new data NDI indication in DCI wound by a random access response radio network temporary identifier RA-RNTI; an indication in an Msg4 message or MsgB message.

The details of the UE provided in the embodiment of the present application, which are not described in detail, may refer to the method for reporting information, and the beneficial effects that the UE provided in the embodiment of the present application can achieve are the same as those of the method for reporting information, which are not described in detail herein.

Based on the same inventive concept as the previous embodiment, the embodiment of the present application further provides a first type UE, and a schematic structure diagram of the first type UE is shown in fig. 13, where the first type UE80 includes a fourth processing module 801 and a fifth processing module 802.

A fourth processing module 801, configured to detect a first primary synchronization signal PSS included in a first synchronization signal physical broadcast channel block SSB according to a predefined rule; and/or detecting a second primary synchronization signal PSS included in the second SSB according to the second synchronization signal grid;

a fifth processing module 802, configured to detect a first secondary synchronization signal SSS included in the first SSB and receive a first physical broadcast channel PBCH included in the first SSB after detecting the first primary synchronization signal PSS; after detecting the second primary synchronization signal PSS, detecting a second secondary synchronization signal SSS included in the second SSB, and receiving a second physical broadcast channel PBCH included in the second SSB.

Optionally, according to a predefined rule, a fourth processing module 801 is configured to detect the first primary synchronization signal PSS according to a first synchronization signal grid; and/or detecting the second primary synchronization signal PSS according to a second synchronization signal grid.

Optionally, a fifth processing module 802, configured to detect or decode at least one of the first PSS, the first SSS, and the first PBCH according to at least one of the first sequence and the first wraparound code; and/or detecting or decoding at least one of the second PSS, the second SSS and the second PBCH according to at least one of the second sequence, the second wraparound code.

Optionally, when the first PSS and the second PSS are the same, and the first SSS and the second SSS are the same, and the first PBCH and the second PBCH are different, the fifth processing module 802 is configured to receive the first PBCH on the first resource; and/or receiving a second PBCH on a second resource; the second resource is adjacent to the frequency domain location of the first resource and/or the second resource is spaced apart from the time domain location of the first resource by a pre-set interval.

Optionally, when the first SSB and the second SSB are the same, a fifth processing module 802 is configured to detect a physical downlink control channel PDCCH for indicating the first system information block SIB and/or a PDCCH for indicating the second SIB according to the control resource set and/or the search space indicated in the PBCH, where the PDCCH for indicating the first SIB is wrapped with a first system information broadcast network temporary identifier SI-RNTI and the PDCCH for indicating the second SIB is wrapped with a second SI-RNTI different from the first SI-RNTI; detecting a PDCCH for indicating a first SIB according to a first control resource set and/or a first search space indicated in the PBCH; and detecting the PDCCH for indicating the second SIB according to the second control resource set and/or the second search space indicated in the PBCH.

Optionally, a fifth processing module 802 is configured to determine, according to the indication information in the PBCH, whether the cell supports the second set of control resources and/or the second search space.

The details of the UE provided in the embodiment of the present application may refer to the method for receiving the message, and the beneficial effects that the UE provided in the embodiment of the present application can achieve are the same as the method for receiving the message, which is not described herein.

It will be understood by those within the art that each block of the block diagrams and/or flowchart illustrations, and combinations of blocks in the block diagrams and/or flowchart illustrations, can be implemented by computer program instructions. Those skilled in the art will appreciate that the computer program instructions can be implemented in a processor of a general purpose computer, special purpose computer, or other programmable data processing method, such that the blocks of the block diagrams and/or flowchart illustration are implemented by the processor of the computer or other programmable data processing method.

Those of skill in the art will appreciate that the various operations, methods, steps in the flow, acts, schemes, and alternatives discussed in the present application may be alternated, altered, combined, or eliminated. Further, other steps, means, or steps in a process having various operations, methods, or procedures discussed herein may be alternated, altered, rearranged, disassembled, combined, or eliminated. Further, steps, measures, schemes in the prior art with various operations, methods, flows disclosed in the present application may also be alternated, altered, rearranged, decomposed, combined, or deleted.

The foregoing is only a partial embodiment of the present application, and it should be noted that it will be apparent to those skilled in the art that modifications and adaptations can be made without departing from the principles of the present application, and such modifications and adaptations are intended to be comprehended within the scope of the present application.

Claims

1. A method performed by a user equipment, UE, in a communication system, comprising:

Obtaining information related to at least one of a random access preamble and a random access opportunity, the information being associated with capabilities supported by the UE;

Based on the information, sending a random access preamble to a base station;

Receiving a random access response from the base station in response to the random access preamble;

Transmitting an Msg3 message to the base station, the Msg3 message including a media access control, MAC, sub-header for a UE of a particular capability;

wherein the capability comprises a combination of a specific capability of the UE and an early data transmission EDT capability.

2. The method according to claim 1, wherein the MAC subheader comprises a specific value of a logical channel identifier LCID of the specific capability UE.

3. The method of claim 1, wherein the information comprises information regarding a number of random access preambles for a UE of a particular capability.

4. The method as recited in claim 1, further comprising:

capability information is sent to the base station, the capability information including information related to a maximum bandwidth supported by the specific capability UE.

5. The method as recited in claim 1, further comprising:

information relating to at least one of an initial downlink bandwidth portion BWP and an initial uplink BWP for the specific capability UE is acquired.

6. The method of claim 5, wherein a physical downlink control channel for receiving the random access response is monitored on the initial downlink BWP for the specific-capability UE.

7. The method of claim 5, wherein the random access preamble is transmitted on the initial uplink BWP for the specific capability UE.

8. A method performed by a base station in a communication system, comprising:

Transmitting information related to at least one of a random access preamble and a random access opportunity, the information being associated with capabilities supported by the UE;

based on the information, receiving a random access preamble from the user equipment UE;

transmitting a random access response to the UE in response to the random access preamble;

receiving an Msg3 message from the UE, the Msg3 message including a media access control, MAC, sub-header for a UE of a particular capability;

9. The method of claim 8, wherein the MAC subheader includes a particular value of a logical channel identifier LCID of the specific capability UE.

10. The method of claim 8, wherein the information comprises information regarding a number of random access preambles for a UE of a particular capability.

11. The method as recited in claim 8, further comprising:

Capability information is received from the UE, the capability information including information related to a maximum bandwidth supported by the specific capability UE.

12. The method as recited in claim 8, further comprising:

Information relating to at least one of an initial downlink bandwidth portion BWP and an initial uplink BWP for the specific capability UE is transmitted to the UE.

13. The method of claim 12, wherein a physical downlink control channel for receiving the random access response is transmitted on the initial downlink BWP for the specific capability UE.

14. The method of claim 12, wherein the random access preamble is received on the initial uplink BWP for the specific capability UE.

15. A user equipment, UE, in a communication system, comprising:

A transceiver;

at least one processor coupled with the transceiver and configured to perform the method of any of claims 1-7.

16. A base station in a communication system, comprising:

A transceiver;

At least one processor coupled with the transceiver and configured to perform the method of any of claims 8-14.