The present disclosure generally relates to wireless communication technology. More particularly, the present disclosure relates to a method and an apparatus for configuring radio resource for a terminal device in a wireless network. The present disclosure also relates to a method for utilizing radio resource in a wireless network and a terminal device adapted for the same purpose. The present disclosure also relates to computer program product adapted for the same purpose.
Narrowband Internet of Things (NB-IoT) is a Low Power Wide Area Network (LPWAN) radio technology standard developed by 3GPP to enable a wide range of cellular devices and services. NB-IoT focuses specifically on indoor coverage, low cost, long battery life, and high connection density. NB-IoT uses a subset of the LTE standard, but limits the bandwidth to a single narrow-band. It uses orthogonal frequency division multiplexing (OFDM) modulation for downlink communication and single-carrier frequency-division multiple access (SC-FDMA) for uplink communications. Applications which require more frequent communications will be better served by NB-IoT, which has no duty cycle limitations operating on the licensed spectrum.
For NB-IoT, radio environment impact on communication quality is characterized by coverage enhancement levels. Typically, three coverage enhancement (CE) levels, i.e., CE level 0 to CE level 2 are introduced. Among them, CE level 0 corresponds to normal coverage, and CE level 2 represents the worst case where the coverage is assumed to be very poor. The number of repetitions for transmitting a message may be determined on the basis of the CE levels.
Physical layer random access preambles are used by NB-IoT UEs camping on a given cell to notify a base station of its intention to get access. A preamble consists of four symbol groups transmitted next to each other using a different subcarrier per symbol group. Each symbol group has a Cyclic Prefix (CP) followed by 5 symbols, the CP has different duration depending on the preamble format. Narrow physical radio access channel (NPRACH) preamble repetition unit 5.6 ms or 6.4 ms depending on the CP.
The following knowledge for related Serving Cell is assumed to be available before a Random Access Procedure is initiated for NB-IoT UEs.
And each subcarrier of a Random Access Preamble group corresponds to a Random Access Preamble.
In the existing solutions, however, the flexibility is very limited for NB-IoT carrier selection based on enhanced coverage levels for NPRACH resources.
For paging as specified in 3GPP TS 36.304, which is incorporated herein by reference in its entirety, the paging-related parameters and static parameter such as UE_ID are used for selecting a paging carrier. However, at a network side, it may assign different weights for different paging carriers to steer the paging load across the paging carriers.
If paging configuration for non-anchor carrier is provided in system information, then the paging carrier is determined by the paging carrier with smallest index n (0≤n≤Nn−1) fulfilling the following equation:
floor(UE_ID/(N*Ns))mod W<W(0)+W(1)+ . . . +W(n)
Where the parameters are identified as below:
T: DRX cycle of the UE. Except for NB-IoT, if a UE specific extended DRX value of 512 radio frames is configured by upper layers according to 7.3, T=512. Otherwise, T is determined by the shortest of the UE specific DRX value, if allocated by upper layers, and a default DRX value broadcast in system information. If UE specific DRX is not configured by upper layers, the default value is applied. UE specific DRX is not applicable for NB-IoT. In RRC_INACTIVE state, if extended DRX is not configured by upper layers as defined in 7.3, T is determined by the shortest of the RAN paging cycle, the UE specific paging cycle, and the default paging cycle, if allocated by upper layers. Otherwise, in RRC_INACTIVE state when extended DRX is configured by upper layers, T is determined by the shortest of the RAN paging cycle, the UE specific paging cycle, if allocated by upper layers and the default paging cycle during the PTW as defined in 7.3, and by the RAN paging cycle outside the PTW.
In the existing solutions, however, it provides a complicated mechanism to carry out paging carrier selection.
The present disclosure describes methods and apparatus for configuring radio resource for a terminal device in a wireless network, which allows a flexible and efficient PRACH resources selection.
According to one aspect of the present disclosure, a method for configuring radio resource for a terminal device in a wireless network comprises:
According to another aspect of the present disclosure, an apparatus for configuring radio resource for a terminal device in a wireless network comprises:
According to another aspect of the present disclosure, a method for utilizing radio resource in a wireless network comprises:
According to another aspect of the present disclosure, a terminal device comprises:
According to another aspect of the present disclosure, a computer program product for, the computer program product being embodied in a computer readable storage medium and comprising computer instructions for performing anyone of the methods as described above.
The foregoing and other objects, features, and advantages would be apparent from the following more particular description of preferred embodiments as illustrated in the accompanying drawings in which:
The invention can be implemented in numerous ways, including as a process; an apparatus; a system; a composition of matter; a computer program product embodied on a computer readable storage medium; and/or a processor, such as a processor configured to execute instructions stored on and/or provided by a memory coupled to the processor. In this specification, these implementations, or any other form that the invention may take, may be referred to as techniques. In general, the order of the steps of disclosed processes may be altered within the scope of the invention. Unless stated otherwise, a component such as a processor or a memory described as being configured to perform a task may be implemented as a general component that is temporarily configured to perform the task at a given time or a specific component that is manufactured to perform the task. As used herein, the term “processor” refers to one or more devices, circuits, and/or processing cores configured to process data, such as computer program instructions.
The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises” “comprising,” “includes” and/or “including” when used herein, 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.
Also, use of ordinal terms such as “first,” “second,” “third,” etc., in the claims to modify a claim element does not by itself connote any priority, precedence, or order of one claim element over another or the temporal order in which acts of a method are performed, but are used merely as labels to distinguish one claim element having a certain name from another element having a same name (but for use of the ordinal term) to distinguish the claim elements.
Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood. It will be further understood that terms used herein should be interpreted as having a meaning that is consistent with their meaning in the context of this specification and the relevant art and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein.
As used herein, the term “terminal device” may be referred to as, for example, device, access terminal, user equipment (UE), mobile station, mobile unit, subscriber station, or the like. It may refer to any end device that can access a wireless communication network and receive services therefrom. By way of example and not limitation, the terminal device may include a portable computer, an image capture terminal device such as a digital camera, a gaming terminal device, a music storage and playback appliance, a mobile phone, a cellular phone, a smart phone, a tablet, a wearable device, a personal digital assistant (PDA), or the like.
Throughout the disclosure, the terms “Narrowband Physical Radio Access Channel (NPRACH)” and “Physical Radio Access Channel (PRACH)” are exchangeable in use.
In an Internet of things (IoT) scenario, a terminal device may represent a machine or other device that performs monitoring and/or measurements, and transmits the results of such monitoring and/or measurements to another terminal device and/or a network equipment. In this case, the terminal device may be a machine-to-machine (M2M) device, which may, in a 3rd generation partnership project (3GPP) context, be referred to as a machine-type communication (MTC) device. Particular examples of such machines or devices may include sensors, metering devices such as power meters, industrial machineries, bikes, vehicles, or home or personal appliances, e.g. refrigerators, televisions, personal wearables such as watches, and so on.
A detailed description of one or more embodiments of the invention is provided below along with accompanying figures that illustrate the principles of the invention. The invention is described in connection with such embodiments, but the invention is not limited to any embodiment. The scope of the invention is limited only by the claims and the invention encompasses numerous alternatives, modifications and equivalents. Numerous specific details are set forth in the following description in order to provide a thorough understanding of the invention. These details are provided for the purpose of example and the invention may be practiced according to the claims without some or all of these specific details. For the purpose of clarity, technical material that is known in the technical fields related to the invention has not been described in detail so that the invention is not unnecessarily obscured.
In the present disclosure, allocation information is configured to allocate PRACH resources for non-anchor carriers to an enhanced coverage level. In particular, each of PRACH resources for non-anchor carriers has a respective selection probability. That is, a respective selection probability is assigned to each of PRACH resources for non-anchor carriers. Thus, the terminal device can make a PRACH resources selection on the basis of the respective selection probability. The selection probability can be determined based on at least one of the following aspects: performance in previous sessions on the non-anchor carriers, PRACH success rate, type of service, load, quality of service (QoS) and nrs-PowerOffsetNonAnchor. Alternatively, the selection probability can be customized by a user, e.g., an operator.
Moreover, in the present disclosure, the radio resource configuring for a terminal device, e.g., assigning the selection probabilities to the non-anchor carriers NPRACH resources, can be performed only on some enhanced coverage levels. For example, the configuring may be only made for CE levels 1 and 2 without CE level 0. In an illustrative example, the non-anchor carrier for specific NPRACH resource may be configured for one of CE levels 1 and 2 or the combination thereof, i.e.:
Preferably, in the present disclosure, for each enhanced coverage level, one anchor carrier NPRACH resource is still be allocated, or NPRACH resource partitioning is still maintained for anchor carrier, so as to provide backward compatibility for NB-IoT UEs without capability for random access on non-anchor carriers.
In the present disclosure, by means of a mapping relationship between paging carriers and the non-anchor carriers specified in paging configuring information received from RAN node, a terminal device can determine a paging carrier to be listened (also referred to as “listened paging carrier” hereinafter) by selecting from the candidate paging carriers one corresponding to the non-anchor carrier via which the terminal device carries out the physical random access.
In an illustrative example, non-anchor UL NPRACH carriers for one specific enhanced coverage level may be indexed with downlink (DL) paging carriers. Thus, upon selecting the non-anchor carrier, the listened paging carrier is determined.
In the present disclosure, the allocation information and the paging configuration information may be included in a system information block sent from a RAN node to a terminal device. Preferably, the system information block is in form of SystemInformationBlockType22-NB with some modifications. For illustrative purpose, a modified version of the SystemInformationBlockType22-NB, in which new information elements (IEs) for describing the allocation information and the paging configuration information are included, is shown as follows:
When network or RAN assigns NPRACH resources for a legacy UE, it may configure one of the following aspects:
For the enum “nprach-CELevel-r17 ENUMERATED {ce0, ce1, ce2} OPTIONAL”, it can be depicted with RSRP threshold range as below:
Basically, derived from rsrp-ThresholdsPrachInfoList as provided in 3GPP TS 36.331.
rsrp-ThresholdsPrachInfoList
The criterion for UEs to select a NPRACH resource. Up to 2 RSRP threshold values can be signaled. The first element corresponds to RSRP threshold 1, the second element corresponds to RSRP threshold 2. See 3GPP TS 36.321. If absent, there is only one NPRACH resource.
A UE that supports powerClassNB-14 dBm-r14 shall correct the RSRP threshold values before applying them as follows:
RSRP threshold=Signaled RSRP threshold−min{0,(14-min(23,P-Max))}
In the present disclosure, the uplink (UL) carrier configured for random access for a certain CE Level can also be configured for paging by network or RAN. The network may use the same CE level as NPRACH or could use different assignment for CE level for paging or only configure the UL carrier for the purpose of paging and omit the NPRACH flexible carrier selection as described above.
For pagingCarrierIndex, one non-anchor UL NPRACH carrier for one specific enhanced coverage level is associated with a DL paging carrier. If absent, it indicates that there is no associated DL paging carrier. The indices of the carriers in the list are arranged as follows: the first entry in the list is indexed with ‘1’, the second entry is indexed with ‘2’ and so on.
The following embodiments will be described in connection with the architecture as shown in
The flowchart as shown in
Step 201: The RAN node generates allocation information configured to allocate PRACH resources for non-anchor carriers to an enhanced coverage level, e.g., CE level 1 or CE level 2. In the allocation information, a respective selection probability is assigned to each of the PRACH resources for non-anchor carriers. Thus, the terminal device can make a PRACH resources selection for physical random access on the basis of the respective selection probability.
In an illustrative example, the RAN node further generates paging configuration information configured to specify a mapping relationship between paging carriers and the non-anchor carriers. Thus, the terminal device can select a listened paging carrier from the paging carriers on the basis of the mapping relationship. In particular, the listened paging carrier may be corresponding to the non-anchor carrier via which the terminal device carries out the physical random access.
In another illustrative example, besides the PRACH resources for non-anchor carriers, the allocation information is further configured to allocate a PRACH resource for an anchor carrier to the enhanced coverage level.
In another illustrative example, the allocation information is only applied to some of the enhanced coverage levels. For example, the enhanced coverage levels may be one of the CE levels 0-2, and the allocating of the PRACH resources for non-anchor carriers is only directed toward some of the CE levels, e.g., CE level 1; CE level 2; or CE levels 1 and 2.
In another illustrative example, the respective selection probability may be customized by a user or determined based on at least one of the following aspects: performance in previous sessions on the non-anchor carriers, PRACH success rate, type of service, load, quality of service (QoS) and nrs-PowerOffsetNonAnchor.
Step 202: The RAN node sends the allocation information to the terminal device. In case where the paging configuration information is generated, the RAN node also sends the paging configuration information to the terminal device.
In another illustrative example, the allocation information and the paging configuration information are included in a system information block, e.g., SystemInformationBlockType22-NB as described above.
With reference to
The flowchart as shown in
Step 401: The terminal device receives from a RAN node allocation information configured to allocate PRACH resources for non-anchor carriers to an enhanced coverage level, e.g., CE level 1 or CE level 2. In the allocation information, a respective selection probability is assigned to each of the PRACH resources for non-anchor carriers. Preferably, besides the PRACH resources for non-anchor carriers, the allocation information is further configured to allocate a PRACH resource for an anchor carrier to the enhanced coverage level.
In an illustrative example, optionally, the terminal device further receives paging configuration information configured to specify a mapping relationship between paging carriers and the non-anchor carriers. Preferably, the allocation information and the paging configuration information may be included in a system information block, e.g., SystemInformationBlockType22-NB as described above.
Step 402: The terminal device determines a current enhanced coverage level, e.g., by performing a DL measurement.
Step 403: for the current enhanced coverage level as determined at step 402, the terminal device selects one or more resources from the PRACH resources for non-anchor carriers based on the allocation information so as to carry out the physical random access.
In case where the paging configuration information is received at step 401, the flowchart may further comprises the following steps:
Step 404: The terminal device selects a listened paging carrier from the paging carriers on the basis of the mapping relationship. In particular, the listened paging carrier may be corresponding to the non-anchor carrier via which the terminal device carries out the physical random access.
Step 405: The terminal device carries out a paging process via the listened paging carrier as selected at step 404.
With reference to
In one or more embodiments as described above, the following advantages will be achieved.
It should be noted that the aforesaid embodiments are illustrative instead of restricting, substitute embodiments may be designed by those skilled in the art without departing from the scope of the claims enclosed. The wordings such as “include”, “including”, “comprise” and “comprising” do not exclude elements or steps which are present but not listed in the description and the claims. It also shall be noted that as used herein and in the appended claims, the singular forms “a”, “an”, and “the” include plural referents unless the context clearly dictates otherwise. Embodiments can be achieved by means of hardware including several different elements or by means of a suitably programmed computer. In the unit claims that list several means, several ones among these means can be specifically embodied in the same hardware item. The use of such words as first, second, third does not represent any order, which can be simply explained as names.
Number | Date | Country | Kind |
---|---|---|---|
PCT/CN2020/109863 | Aug 2020 | WO | international |
Filing Document | Filing Date | Country | Kind |
---|---|---|---|
PCT/SE2021/050794 | 8/16/2021 | WO |