Patent Description:
A communication system can be seen as a facility that enables communication sessions between two or more entities such as communication devices, base stations/access points and/or other nodes by providing carriers between the various entities involved in the communications path. A communication system can be provided for example by means of a communication network and one or more compatible communications devices.

Access to the communication system may be via an appropriate communications device or terminal. A communications device is provided with an appropriate signal receiving and transmitting apparatus for enabling communications, for example enabling access to a communication network or communications directly with other communications device. The communications device may access a carrier provided by a station or access point, and transmit and/or receive communications on the carrier.

The communication system and associated devices typically operate in accordance with a given standard or specification which sets out what the various entities associated with the system are permitted to do and how that should be achieved.

The patent application <CIT> discloses a method of wireless communication by a user equipment (UE) without a radio resource control (RRC) connection to a base station. The method includes receiving system information from the base station and transmitting a data communication to the base station over a control plane without establishing an RRC connection with the base station. A UE in an RRC suspended state may transmit a data communication to the base station over a user plane without resuming an RRC connection with the base station. The data communication may comprise data and UE identity information and/or a cause indication. A base station may indicate resources in the system information for the transmission of the data communication information and receive the data communication over the control plane without establishing an RRC connection with the UE or over a user plane without resuming an RRC connection with an RRC suspended UE.

The patent application <CIT> discloses a method of high reliability and early data transmission (EDT). EDT allows one uplink transmission (optionally) followed by one downlink data transmission during a random-access channel (RACH) procedure, which can reduce the signaling overhead and save UE power. To improve reliability, for uplink EDT, there would be different set of RACH reattempt parameters in the UE for different types of access. For downlink EDT, there would be an indication in the paging message to trigger whether the UE would use legacy RACH or not. Further, the configuration for PRACH resource for EDT can be independent to legacy PRACH resource configuration. Under certain conditions, UE can fallback to legacy RACH procedure for high reliability.

The 3GPP document Report on [<NUM>#<NUM>][MTC/NB-loT] Padding issue in Msg3 is the outcome of an email discussion on how to address the padding issue in Msg3 for early data transmission, According to the document the UE initiates EDT in Msg1 when the size of Msg3 including the user data, which UE intends to transmit, is equal or smaller than the maximum possible TBS size for Msg3 broadcast per CE. PRACH partitioning for EDT indication is configured per enhanced coverage level. For EDT indication, PRACH resources can be configured as in legacy eMTC or NB-loT with respect to physical layer resources, preambles/subcarriers. PRACH resource pool, i.e. physical layer resources, preambles/subcarriers, for EDT indication is separate from PRACH resource pool for legacy RACH procedure.

Various other aspects are also described in the following detailed description and in the attached claims.

Some example embodiments will now be described in further detail, by way of example only, with reference to the following examples and accompanying drawings, in which:.

Before describing various example embodiments, the following list of abbreviations is provided for reference:.

Some example embodiments may be directed towards NR based Internet-of-things (NR-based loT or NR-loT), which is hereinafter referred to as "NR-Light". NR-Light may provide further use cases that may not be provided by New Radio Enhanced Mobile Broadband (NR eMBB), Ultra-Reliable Low Latency Communication (URLLC), or Enhanced Machine Type Communication (eMTC)/Narrowband loT (NB-loT).

NR-Light may support one or more of higher data rate & reliability and lower latency than eMTC & NB-IoT, lower cost/complexity and longer battery life than NR eMBB, and wider coverage than eMBB.

More specifically, in some example embodiments NR-Light may address one or more of the following objectives and use cases:.

UEs supporting eMTC and NB-loT technologies are currently deployed in LTE spectrum. As LTE spectrum is repurposed to NR, it may be desirable to continue to support legacy devices on the originally deployed eMTC and NB-loT carriers. To enable such operation, eMTC and/or NB-loT may be deployed within an NR carrier, as illustrated in <FIG>.

eMTC and NB-loT may have some desirable features compared to NR-Light such as very low power consumption and enhanced coverage. To take advantage of these features, UEs capable of operating in two modes are introduced. In some example embodiments, UEs may be switched between the narrowband eMTC/NB-loT carrier or the wideband NR carrier depending on which technology feature is more important at a given time.

In Rel-<NUM> of eMTC/NB-IoT, early data transmission (EDT) feature was introduced. EDT allows data to be transmitted using random access procedure. UE can therefore quickly transmit or receive data without having to connect to the system and then go back to sleep. However, EDT may be limited in terms of how much data can be transmitted. For example, in eMTC/NB-loT, up to <NUM>/<NUM> bits may be transmitted using uplink EDT.

A representation of an example method for EDT is shown in <FIG>. EDT may enable the UE to transmit a small quantity of data in Msg3. In some example embodiments, if the UE has a larger data packet, it must use other communication procedures (such as initial access request, establishing an RRC connection, and subsequent data transmission) which may have higher overhead and latency compared to EDT.

The eNB may broadcast the maximum transport block size TBS allowed for EDT in a system information block (SIB) (for example, SIB1-BR/SIB1-NB). When the size of the UE data does not exceed the maximum TBS, the UE may initiate EDT by transmitting <NUM> a random access preamble to the eNB using resources reserved for EDT. In response, the eNB may transmit <NUM> a random access response, the response indicating allocated resources for Msg3 transmission. The UE may then transmit <NUM> data in Msg3 using an autonomously selected TBS not exceeding the broadcasted TBS.

In some example implementations, the data transmitted at step <NUM> may comprise an identifier for the user equipment. The identifier may be configured to cause the network to route the data to a destination prior to connection establishment. For example, the user equipment may initially perform connection establishment in order to inform the network of information relevant to the user equipment for EDT data routing, where the information may include the identifier for the user equipment. Thereafter, having configured the network with at least the identifier for the user equipment, the user equipment may send data packets along with the identifier, which allows the network to route the data packets to an appropriate destination based on the identifier. The routing may be performed without the user equipment performing full RRC connection establishment. The destination may, for example, comprise a network node, another apparatus, or the like.

While the communication procedure shown in <FIG> has been standardized for eMTC/NB-loT, no similar procedure has yet been developed for NR/NR-Light.

As discussed previously, to support IIoT and Industry <NUM> deployment, in some cases NR-Light capable UEs may have dual mode capability - a first mode of operation for NR/NR-Light and a second mode of operation for eMTC/NB-loT. In addition, in some cases, the carrier may also be deployed using NR with eMTC/NB-IoT in-band using only one physical base station (i.e. one node acting as eNB and gNB, requiring the eNB and gNB to be co-located) and connected to the <NUM> core network. As shown in <FIG>, the eNB and gNB <NUM> are co-located and in communication with a NB-loT UE 302a, a NR UE 302b, and a dual mode NR/NB-IoT UE 302c. The eNB/gNB <NUM> is also connected to the <NUM> Core Network <NUM>.

Additionally or alternatively, the NR carrier may be deployed in one gNB while the eMTC/NB-IoT carrier is deployed from another, non-co-located eNB.

For a dual-mode capable UE 302c, it may be beneficial to keep the UE in eMTC/NB-IoT idle mode as this mode may have a very low power consumption. For example, a battery life of <NUM>-<NUM> years may be possible with eMTC/NB-IoT with high usage, and upwards of <NUM> years with low usage. With Mobile Originated (MO) data arrival, the UE may use the existing eMTC/NB-loT EDT procedure for small data packets. The small data packet may be defined as a data packet having a size below a threshold size. For example, the threshold size may be <NUM> bits for eMTC and <NUM> bits for NB-IoT.

For a larger data packet, it may be beneficial to switch to NR/NR-Light and perform NR-EDT using a larger available bandwidth compared to LTE-EDT. Otherwise, UE may have to transition from idle into connection mode which would consume large overhead and power consumption. <FIG> shows a representation of a method for NR-EDT according to some example embodiments.

At step <NUM>, the UE may transmit a random access preamble to the gNB. The random access preamble may comprise information indicating that the UE has a data packet to transmit to the gNB using early data transmission.

At step <NUM>, the gNB may transmit a random access response to the UE. The random access response may comprise information indicating resources for the UE to perform data transmission of the data packet to the gNB.

At step <NUM>, the UE may transmit the data packet to the gNB. The data packet may be sent as Msg3.

Therefore, a method is needed to allow fast switching at the UE between eMTC/NB-loT mode and NR-EDT.

As used hereinafter, the eMTC/NB-IoT mode of operation is referred to as "LTE mode", and the NR/NR-Light mode of operation is referred to as "NR mode".

Reference is made to <FIG>, which shows a method according to some example embodiments.

At step <NUM>, the method may comprise determining at least one condition.

At step <NUM>, the method may comprise, based on the at least one condition, transmitting the data packet to a first access node using one of a first early data transmission type in a first mode of operation of the apparatus and a second early data transmission type in a second mode of operation of the apparatus.

At step <NUM>, the method may comprise transmitting, to an apparatus, information indicating at least one condition configured to cause the apparatus to transmit a data packet using one of a first early data transmission type in a first mode of operation and a second early data transmission type in a second mode of operation based on the at least one condition.

At step <NUM>, the method may comprise transmitting, to the user equipment, information indicating network resources for the user equipment to perform data packet transmission to a second access node using one of the first early data transmission type in the first mode of operation and the second early data transmission type in the second mode of operation.

In one alternative. the first early data transmission type comprises an LTE early data transmission type (hereafter LTE-EDT), and the first mode of operation comprises an LTE mode of operation. The second early data transmission type comprises a NR early data transmission type (hereafter NR-EDT), and the second mode of operation comprises a NR mode of operation.

In the other alternative, the first early data transmission type comprises a NR early data transmission type, and the first mode of operation comprises a NR mode of operation. The second early data transmission type comprises an LTE early data transmission type, and the second mode of operation comprises an LTE mode of operation.

A UE autonomously switches from a first mode of operation, such as an LTE mode of operation, to a second mode of operation, such as an NR mode of operation for data packet transmission when at least one condition is met. The at least one condition compirses a data packet size being greater than a threshold data packet size. The threshold size may be any suitable size, such as but not limited to a size defined by the LTE-based EDT maximum packet size described previously.

In some example embodiments, the condition such as the threshold packet size may be configured at the UE based on signaling received from the eNB and/or gNB. That is to say, in some example embodiments, the eNB and/or gNB may transmit information comprising an indication to the UE to cause the UE to switch between NR mode and LTE mode based on the data packet size.

As an example, the UE may receive information from the eNB and/or gNB indicating that, where the data packet has a first size that is greater than a threshold size, the UE is configured to switch from LTE mode to NR mode for data packet transmission, and where subsequently the data packet has a second size that is less than the threshold size, the UE is configured to switch back to LTE mode for data packet transmission.

Reference is made to <FIG>, which shows a representation of a method according to some example embodiments.

At step <NUM>, the eNB transmits information comprising an indication of a threshold data packet size for LTE-EDT.

At step <NUM>, the UE determines whether a size of a data packet for transmission is greater than or less than the threshold data packet size.

At step <NUM>, responsive to determining that the data packet size for transmission is above the threshold, the UE switches operation mode to NR/NR-Light mode, and performs the transmission of the data packet to the gNB.

In some example embodiments, the UE may transmit to the network UE capability information for fast switching between NR mode and LTE mode. The network may then transmit the information comprising an indication to enable switching between NR mode and LTE based on the received UE capability information.

In some example embodiments the UE may be configured with NR parameters required to operate in NR mode. The NR parameters may include, for example, SIB1, SSB/PRACH, reserved preamble, NR cells/frequencies/areas (e.g. RNA or Registration area) where the UE is allowed to switch to perform UL transmission and also the CORESET region to associated with EDT PRACH Resources. The NR parameters may be transmitted to the UE via the eNB (i.e. while the UE is in LTE mode), and/or via the gNB (i.e. while the UE is in NR mode).

The UE transmits information to the UE indicating at least two PRACH resource sets. The information indicating the at least two PRACH resource sets may comprise one or more of PRACH preambles, timing information and frequency information for PRACH signaling.

A first PRACH resource set is used by the UE for LTE-EDT (for example by the method shown in <FIG>), and a second PRACH resource set is used for the UE to request for NR-EDT (for example by the method shown in <FIG>). For example, where the UE is initially operating in LTE mode, the UE may transmit the PRACH preamble on the second PRACH resource to request NR-EDT.

In some example embodiments, any suitable low-overhead data transmission procedure may be used instead of EDT during random access. For example, a two-step RACH procedure may be utilized when the UE is in NR mode instead of NR-EDT. The eNB may provide the UE with information for implementing the low-overhead data transmission procedure.

On receiving a PRACH preamble on either the first and/or second PRACH resource, the eNB may transmit a radio access response (RAR) based on the PRACH resource on which the preamble was received. The RAR may comprise one or more of a timing advance and resource allocation for NR-EDT transmission. In other words, the eNB may transmit, to the UE, information indicating network resources for data packet transmission to the gNB.

When the eNB receives the PRACH preamble on the second PRACH resource (i.e. the UE transmits the PRACH preamble to the eNB to request NR-EDT), the eNB may provide the UE with information for establishing RACH communication with the gNB for NR-EDT. The information for establishing NR-EDT may comprise one or more NR Bandwidth Parts (NR BWPs), each NR BWP comprising an indication of a time/frequency where the UE should monitor for further information. In some example embodiments, a NR Common Search Space within the NR BWP may indicate the resources (time/frequency) that the UE should monitor for downlink control channel signaling.

In some example embodiments, the UE may directly access NR uplink resources for NR-EDT based on the information received in the RAR from the eNB. In some example embodiments, when the eNB and gNB are co-located, the timing information of the gNB may be synchronized with the eNB. As such, some example embodiments may require no further network synchronization.

Reference is made to <FIG>, which shows a representation of a method according to some example embodiments, where the UE transmits the PRACH preamble on the second PRACH resource to request NR-EDT.

At step <NUM>, the eNB transmits information indicating one or more PRACH resources for NR-EDT access to the UE.

At step <NUM>, the UE determines to send a data packet by NR-EDT.

At step <NUM>, the UE transmits a random access preamble to the gNB on the one or more PRACH resources indicated by the eNB.

At step <NUM>, the gNB transmits a random access response to the UE in response to the preamble received in step <NUM>.

At step <NUM>, the UE transmits the data packet to the gNB.

In some embodiments, where no NR resources are available for NR-EDT access, the eNB may transmit a RAR comprising an indication for the UE to fall back to RRC connection setup procedures.

In some example embodiments, the RAR received at the UE from the eNB may comprise information indicating a NR control region. The NR control region may be considered information comprising an indication of timing information and/or frequency information for the UE to listen for PDCCH transmission from the gNB to receive the RAR from the gNB. Therefore, in some example embodiments, the UE initially in LTE mode may be caused to switch to NR mode to receive a RAR from the gNB without the UE having to resend a random access request to the gNB when in NR mode.

Reference is made to <FIG>, which shows an example method for the UE receiving a RAR from the gNB without having to send a random access preamble to the gNB.

At step <NUM>, the UE transmits a random access preamble to the eNB.

At step <NUM>, the eNB transmits a random access response to the UE. The random access response sent by the eNB comprises information indicating PDCCH resources for the UE to use to listen for transmissions from the gNB.

At step <NUM>, the eNB transmits information to the gNB (for example, over X2 interface) indicating that the gNB is to transmit a random access response to the UE. Step <NUM> may be performed either before, after, or at substantially the same time, as step <NUM>.

At step <NUM>, the UE listens for PDCCH transmission from the gNB.

At step <NUM>, the gNB transmits a random access response using the PDCCH resources indicated by the information comprised in the random access response sent by the eNB to the UE in step <NUM>.

At step <NUM>, the UE transmits data to the gNB based on the random access response received from the gNB in step <NUM>.

In some example embodiments, the information indicating the NR control region may further comprise one or more conditions defining when the UE should perform NR-EDT. The one or more conditions may comprise one or more of a data packet size, a reference signal received power/reference signal received quality (RSRP/RSRQ), and a power headroom.

The conditions may further define a threshold with respect to each condition - for example, the conditions may define a data packet size threshold, a RSRP/RSRQ threshold, and a power headroom threshold. The threshold(s) may be related to the eNB and/or the gNB. That is to say, for example, the RSRP/RSRQ threshold may be a threshold with respect to the eNB or the gNB.

The UE may determine one or more parameters relative to a respective parameter threshold (for example, the UE may compare a data packet size against a data packet size threshold) in order to determine whether a condition has been met, and thus whether to switch to NR-EDT, or whether to remain in LTE mode.

In some example embodiments, the information indicating the NR control space may further comprise an allocation of transmission type (for example LTE mode or NR mode). The transmission type allocated may be based on one or more of a type of data being transmitted, a priority of the data being transmitted, and a quality of service (QoS) or QoS Class Identifier (QCI). That is to say, for example, a first transmission type may be allocated for transmission in LTE mode, and a second transmission type may be allocated for transmission in NR mode.

In some example embodiments, the UE may select a synchronization signal block (SSB). The selected SSB may be selected based on any suitable parameter, such as but not limited to a highest received signal power. The UE may then transmit a random access request comprising a reserved preamble on the PRACH configuration associated with the selected SSB. The reserved preamble may indicate to the gNB that the UE is requesting NR mode EDT transmission in the random access request.

In some example embodiments, the network may require the UE to synchronize with the gNB before NR-EDT access. This may be the case, for example, where the eNB and gNB are not co-located, and the timing sequence for the eNB cannot be used for the gNB.

In some example embodiments, the UE may directly communicate with the gNB in order to set up NR-EDT.

For example, the UE may transmit a random access request requesting NR-EDT to the gNB. The gNB may determine whether to allow the UE to perform NR-EDT (for example, based on system loading, radio link condition, or traffic priority). When the gNB determines that the UE is to be allowed to perform the NR-EDT, the gNB may transmit a random access response to the UE indicating that the UE may perform NR-EDT. The random access response sent by the gNB to the UE may comprise the Modulation and Coding Selection (MCS) and/or Transport Block Size (TBS).

After receiving the random access response from the gNB indicating that the UE may perform NR-EDT, the UE may perform NR-EDT. In some example embodiments, after performing NR-EDT, the UE may switch back to LTE mode (for example, return to or resume idle or connected mode or state on the LTE carrier). By returning to LTE mode after NR transmission, some example embodiments may reduce power consumption, thereby prolonging battery life of the UE.

In some example embodiments, the eNB may exchange information with the gNB. For example, configurations (such as but not limited to PRACH configurations) and parameters (such as but not limited to RSRP/RSRQ thresholds) may be exchanged between the eNB and the gNB via an Xn interface. For example, the gNB may provide NR carrier configurations, NR-Light EDT parameters etc. to the eNB.

In some example embodiments, the eNB and/or the gNB may update respective eNB and/or gNB switching configurations based on the information exchanged.

The abovementioned embodiments have been described with reference to the UE switching from LTE mode to NR-EDT. However, in some example embodiments, the UE may switch from LTE mode to NR Connected mode.

In some example embodiments, the UE may be configured via signaling when in NR Connected mode. The signaling may be sent from the gNB to the UE. The signaling may comprise information for configuring the UE to switch to NR Connected mode transmission of data packets having a size above a threshold size. After transmitting the data packet via NR Connected mode, the UE may then switch back to LTE mode.

In some example embodiments, the switching to NR Connected mode may be configured via a NR resource or NR-EDT. In some example embodiments, the switching may be configured via control information sent via the eNB.

In some example embodiments, where switching is based on signal conditions such as but not limited to RSRP/RSRQ measurements, a hysteresis may be applied to prevent the UE from frequently switching between modes of operation. That is to say, for example, if a first RSRP measurement is below a threshold value, thereby indicating that the UE should operate in NR Connected mode, the UE may not switch back to LTE mode unless a second RSRP measurement is more than a fixed amount above the threshold value.

Some embodiments may therefore provide a method allowing a UE to stay in LTE mode, thereby consuming very little power, while being able to quickly switch to NR mode for EDT or NR Connected mode when larger amounts of data are required for transmission by the UE. This may reduce latency and power consumption for NR mode capable devices.

Furthermore, in some example embodiments, the UE may be able to switch almost instantaneously from LTE mode to NR mode, as the two operation modes utilize the same carrier, thereby enabling the UE to maintain synchronization to both LTE and NR using LTE mode signaling.

While the forgoing example embodiments have been described with reference to switching from an LTE mode of operation to a NR mode of operation for performing early data transmission, it should be understood that in some example embodiments, switching may occur from a NR mode of operation to an LTE mode of operation for performing early data transmission.

<FIG> illustrates an example of a control apparatus <NUM> for controlling a function of the eNB or gNB as described previously. The control apparatus may comprise at least one random access memory (RAM) 911a, at least on read only memory (ROM) 911b, at least one processor <NUM>, <NUM> and an input/output interface <NUM>. The at least one processor <NUM>, <NUM> may be coupled to the RAM 911a and the ROM 911b. The at least one processor <NUM>, <NUM> may be configured to execute an appropriate software code <NUM>. The software code <NUM> may for example allow to perform one or more steps to perform one or more of the present aspects. The software code <NUM> may be stored in the ROM 911b. The control apparatus <NUM> may be interconnected with another control apparatus <NUM> controlling another function of the NR network. In some embodiments, each function of the NR network comprises a control apparatus <NUM>. In alternative embodiments, two or more functions of the NR network may share a control apparatus.

<FIG> illustrates an example of a user equipment or terminal <NUM>, such as a user equipment described previously. The terminal <NUM> may be provided by any device capable of sending and receiving radio signals. Non-limiting examples comprise a mobile station (MS) or mobile device such as a mobile phone or what is known as a 'smart phone', a computer provided with a wireless interface card or other wireless interface facility (e.g., USB dongle), a personal data assistant (PDA) or a tablet provided with wireless communication capabilities, a machine-type communications (MTC) device, an Internet of things (IoT) type communication device or any combinations of these or the like. The terminal <NUM> may provide, for example, communication of data for carrying communications. The communications may be one or more of voice, electronic mail (email), text message, multimedia, data, machine data and so on.

The terminal <NUM> may receive signals over an air or radio interface <NUM> via appropriate apparatus for receiving and may transmit signals via appropriate apparatus for transmitting radio signals. In <FIG> transceiver apparatus is designated schematically by block <NUM>. The transceiver apparatus <NUM> may be provided for example by means of a radio part and associated antenna arrangement. The antenna arrangement may be arranged internally or externally to the mobile device.

The terminal <NUM> may be provided with at least one processor <NUM>, at least one memory ROM 1002a, at least one RAM 1002b and other possible components <NUM> for use in software and hardware aided execution of tasks it is designed to perform, including control of access to and communications with access systems and other communication devices. The at least one processor <NUM> is coupled to the RAM 1011a and the ROM 1011b. The at least one processor <NUM> may be configured to execute an appropriate software code <NUM>. The software code <NUM> may for example allow to perform one or more of the present aspects. The software code <NUM> may be stored in the ROM 1011b.

The processor, storage and other relevant control apparatus can be provided on an appropriate circuit board and/or in chipsets. This feature is denoted by reference <NUM>. The device may optionally have a user interface such as key pad <NUM>, touch sensitive screen or pad, combinations thereof or the like. Optionally one or more of a display, a speaker and a microphone may be provided depending on the type of the device.

<FIG> shows a schematic representation of non-volatile memory media 1100a (e.g. computer disc (CD) or digital versatile disc (DVD)) and 1100b (e.g. universal serial bus (USB) memory stick) storing instructions and/or parameters <NUM> which when executed by a processor allow the processor to perform one or more of the steps of the methods described previously.

It is to be noted that embodiments of the present invention may be implemented as circuitry, in software, hardware, application logic or a combination of software, hardware and application logic. In the context of this document, a "computer-readable medium" may be any media or means that can contain, store, communicate, propagate or transport the instructions for use by or in connection with an instruction execution system, apparatus, or device, such as a computer or smart phone, or user equipment.

Claim 1:
A user equipment (302c, <NUM>) comprising: at least one processor (<NUM>); and at least one memory (1002a, 1002b) including computer program code, the at least one memory and computer program code configured to, with the at least one processor (<NUM>), cause the user equipment (302c, <NUM>) to perform:
determining at least one condition, wherein the at least one condition is a data packet size threshold; and based on the at least one condition, transmitting a data packet to a first access node (eNB, gNB) using one of a first early data transmission type in a first mode of operation of the user equipment (302c, <NUM>) and a second early data transmission type in a second mode of operation of the user equipment (302c, <NUM>),
characterized in that the first mode of operation comprises one of a long term evolution mode and a new radio mode, and the second mode of operation comprises the other of the long term evolution mode and the new radio mode, wherein the at least one memory (1002a, 1002b) includes computer program code, the at least one memory (1002a, 1002b) and computer program code configured to, with the at least one processor (<NUM>), cause the user equipment (302c, <NUM>) to perform:
receiving from a network element (eNB, gNB) information indicating a first PRACH resource set to be used for the long term evolution mode and information indicating a second PRACH resource set to be used in the new radio mode.