Patent Application
20230127137
Some example embodiments may generally relate to mobile or wireless telecommunication systems, such as Long Term Evolution (LTE), fifth generation (5G) radio access technology (RAT), new radio (NR) access technology, and/or other communications systems. For example, certain example embodiments may relate to systems and/or methods for efficiently signalling feature combinations for random access channel (RACH) partitioning.
Examples of mobile or wireless telecommunication systems may include radio frequency (RF) 5G RAT, the Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (UTRAN), LTE Evolved UTRAN (E-UTRAN), LTE-Advanced (LTE-A), LTE-A Pro, NR access technology, and/or MulteFire Alliance 5G wireless systems refer to the next generation (NG) of radio systems and network architecture. A 5G system is typically built on a 5G NR, but a 5G (or NG) network may also be built on E-UTRA radio. It is expected that NR can support service categories such as enhanced mobile broadband (eMBB), ultra-reliable low-latency-communication (URLLC), and massive machine-type communication (mMTC). NR is expected to deliver extreme broadband, ultra-robust, low-latency connectivity, and massive networking to support the Internet of Things (IoT). The next generation radio access network (NG-RAN) represents the RAN for 5G, which may provide radio access for NR, LTE, and LTE-A. It is noted that the nodes in 5G providing radio access functionality to a user equipment (e.g., similar to the Node B in UTRAN or the Evolved Node B (eNB) in LTE) may be referred to as next-generation Node B (gNB) when built on NR radio, and may be referred to as next-generation eNB (NG-eNB) when built on E-UTRA radio.
In accordance with some example embodiments, a method may include transmitting, by a network entity, a radio resources configuration associated with at least one feature combination configuration and associated random access resources configuration. The at least one feature combination configuration is associated with at least one of coverage enhancement, network slicing, reduced capability user equipment, or small data transmission. The associated random access resources configuration is associated with access conditions for the at least one feature combination configuration.
In accordance with certain example embodiments, an apparatus may include means for transmitting a radio resources configuration associated with at least one feature combination configuration and associated random access resources configuration. The at least one feature combination configuration is associated with at least one of coverage enhancement, network slicing, reduced capability user equipment, or small data transmission. The associated random access resources configuration is associated with access conditions for the at least one feature combination configuration.
In accordance with various example embodiments, a non-transitory computer readable medium may be encoded with instructions that may, when executed in hardware, perform a method. The method may include transmitting a radio resources configuration associated with at least one feature combination configuration and associated random access resources configuration. The at least one feature combination configuration is associated with at least one of coverage enhancement, network slicing, reduced capability user equipment, or small data transmission. The associated random access resources configuration is associated with access conditions for the at least one feature combination configuration.
In accordance with some example embodiments, a computer program product may perform a method. The method may include transmitting a radio resources configuration associated with at least one feature combination configuration and associated random access resources configuration. The at least one feature combination configuration is associated with at least one of coverage enhancement, network slicing, reduced capability user equipment, or small data transmission. The associated random access resources configuration is associated with access conditions for the at least one feature combination configuration.
In accordance with certain example embodiments, an apparatus may include at least one processor and at least one memory including computer program code. The at least one memory and the computer program code may be configured to, with the at least one processor, cause the apparatus to at least transmit a radio resources configuration associated with at least one feature combination configuration and associated random access resources configuration. The at least one feature combination configuration is associated with at least one of coverage enhancement, network slicing, reduced capability user equipment, or small data transmission. The associated random access resources configuration is associated with access conditions for the at least one feature combination configuration.
In accordance with various example embodiments, an apparatus may include circuitry configured to transmit a radio resources configuration associated with at least one feature combination configuration and associated random access resources configuration. The at least one feature combination configuration is associated with at least one of coverage enhancement, network slicing, reduced capability user equipment, or small data transmission. The associated random access resources configuration is associated with access conditions for the at least one feature combination configuration.
In accordance with some example embodiments, a method may include receiving, by a user equipment, a radio resources configuration associated with at least one feature combination configuration and associated random access resources configuration. The at least one feature combination configuration is associated with at least one of coverage enhancement, network slicing, reduced capability user equipment, or small data transmission. The associated random access resources configuration is associated with access conditions for the at least one feature combination configuration.
In accordance with certain example embodiments, an apparatus may include means for receiving a radio resources configuration associated with at least one feature combination configuration and associated random access resources configuration. The at least one feature combination configuration is associated with at least one of coverage enhancement, network slicing, reduced capability user equipment, or small data transmission. The associated random access resources configuration is associated with access conditions for the at least one feature combination configuration.
In accordance with various example embodiments, a non-transitory computer readable medium may be encoded with instructions that may, when executed in hardware, perform a method. The method may include receiving a radio resources configuration associated with at least one feature combination configuration and associated random access resources configuration. The at least one feature combination configuration is associated with at least one of coverage enhancement, network slicing, reduced capability user equipment, or small data transmission. The associated random access resources configuration is associated with access conditions for the at least one feature combination configuration.
In accordance with some example embodiments, a computer program product may perform a method. The method may include receiving a radio resources configuration associated with at least one feature combination configuration and associated random access resources configuration. The at least one feature combination configuration is associated with at least one of coverage enhancement, network slicing, reduced capability user equipment, or small data transmission. The associated random access resources configuration is associated with access conditions for the at least one feature combination configuration.
In accordance with certain example embodiments, an apparatus may include at least one processor and at least one memory including computer program code. The at least one memory and the computer program code may be configured to, with the at least one processor, cause the apparatus to at least receive a radio resources configuration associated with at least one feature combination configuration and associated random access resources configuration. The at least one feature combination configuration is associated with at least one of coverage enhancement, network slicing, reduced capability user equipment, or small data transmission. The associated random access resources configuration is associated with access conditions for the at least one feature combination configuration.
In accordance with various example embodiments, an apparatus may include circuitry configured to receive a radio resources configuration associated with at least one feature combination configuration and associated random access resources configuration. The at least one feature combination configuration is associated with at least one of coverage enhancement, network slicing, reduced capability user equipment, or small data transmission. The associated random access resources configuration is associated with access conditions for the at least one feature combination configuration.
For proper understanding of example embodiments, reference should be made to the accompanying drawings, wherein:
It will be readily understood that the components of certain example embodiments, as generally described and illustrated in the figures herein, may be arranged and designed in a wide variety of different configurations. Thus, the following detailed description of some example embodiments of systems, methods, apparatuses, and computer program products for efficiently signalling feature combinations for RACH partitioning is not intended to limit the scope of certain example embodiments, but is instead representative of selected example embodiments.
RACH resources may define the time and frequency resources that may be used by user equipment (UE) for random access, and may include RACH occasions (ROs) in time and/or RACH preambles available in each RO. When a UE transmits a physical random access channel (PRACH) preamble, the UE may transmit according to a specific pattern or sequence, similar to a signature. Each NR cell may have 64 preamble sequences available for each RO. In contention-based random access (CBRA), once the UE determines a suitable RO, the UE may randomly select one of the valid preambles for transmission in the RO among the available ROs, as configured by the network.
In 3GPP Rel-16, the gNB may broadcast the two pools using a RACH-ConfigCommonTwoStepRA information element (IE), which may be further subdivided via a GroupB-ConfiguredTwoStepRA-r16 IE contained in the RACH-ConfigCommonTwoStepRA IE. The UE may then indicate whether it is using a 2-step or 4-step RACH procedure in message A (MsgA) for 2-step RACH procedure, or in an Msg1 for 4-step RACH, respectively, by selecting and transmitting a RACH resource from the corresponding pool of resources.
Contention-free radio access (CFRA) resources and CBRA resources may be further partitioned. For example, CFRA resources may be dedicated to a given UE (e.g., in RRC Connected mode with an assigned cell radio network temporary identifier (C-RNTI)), while the UE may need to contend for RACH resources in the contention-based pool. For CBRA partitioning, different UEs may select the same CBRA resource, and/or may interfere with other UEs, causing an undesirable RACH collision.
Currently, in order to enable the network to identify each feature based on the preamble/RO used by the UE, RACH resources may be further partitioned to support initial access of some 3GPP Rel-17 features, such as:
The partitioning of RACH resources may be achieved either by partitioning the ROs for different features (i.e., different ROs may be dedicated to different features), or by partitioning the preambles associated with an RO for different features (i.e., different preambles of an RO may be dedicated to different features, as defined in 3GPP Rel-16 for 2-step and 4-step RACH partitioning). However, dedicating ROs per feature may introduce delays in the RA procedure since the UE requiring a feature may need to wait until a valid RO becomes available, with fewer valid ROs available per feature due to splitting of resources. In contrast, preambles in an RO dedicated per feature may be realized, for example, by using a RACH mask, and may allow all features to use any RO, resulting in a lower RA latency achieved for any service in the cell. However, this may limit the number of preambles available per feature. In turn, the probability of undesirable RACH collisions may increase, which may also indirectly increase latency times. The supported cell sizes may also be limited in this case since an increased cell size may require skipping cyclic shifts when creating the PRACH preamble sequences so that larger distances between the cyclic shifts of the PRACH root sequences may be obtained. The number of root sequences may be limited by cell planning and inherent mathematical properties of the sequences themselves. The problem of preamble limitation and collision may worsen with more features to be separated.
In order to configure RACH resources, each cell may need to be selected and use one out of 256 PRACH configurations, determining the RO periodicity and the ROs location in time. Prior to 3GPP Rel-16, RACH capacity and dimensioning has been possible due to the limited number of required RACH resources. For example, with 20 ms RO periodicity and 40 MHz carrier bandwidth, about 3% of the resources may be dedicated to RACH. In contrast, beginning with 3GPP Rel-17, separate RACH configurations may need to be available to support initial access for various 3GPP Rel-17 features, thereby increasing the number of resources used for RACH in the cell. As a result, in addition to legacy RACH resources, the network may need to allocate a sufficient number of RACH resources for each additional RACH configuration dedicated to 3GPP Rel-17 features. This may ensure that the tolerable collision probability and latency key performance indicators (KPIs) are within the allowed targets for each feature (e.g., <1% PRACH collision probability).
Certain example embodiments described herein may have various benefits and/or advantages to overcome the disadvantages described above. For example, certain example embodiments may provide a more efficient, leaner, and future-proof signalling of feature combinations for RA partitioning. Thus, certain example embodiments discussed below are directed to improvements in computer-related technology.
The two example encodings may indicate 4 purposes (e.g., redCap, smallData, slicing, and CovEnh), while 4 bits may be reserved to retain enough flexibility. FeaturesCombinationIndicationBitmap may comprise a bit for each feature set to “true” in the FeatureCombination, allowing any combination out of those features to be signalled.
In another example, a bit string may be used for the spare values in the FeatureCombination (similar to master information block (MIB)), such as below:
As a result, the bit-cost in system information (SI) would be 3+(2-8)=5-11 bits added to the RA feature combination. The NE may only need to indicate the bitmap of feature combinations, and the abstract syntax notation (ASN).1 definition of the FeatureCombination indicates the remaining features.
Using the above embodiments, 3GPP Rel-17 may be configured as FeatureCombination (size 8): {RedCap: true; smallData: true; slicing: true; CovEnh: true; Reserved: false}, maxNrofFeatures=4 (4 features set to true). Alternatively, Feature CombinationIndicationBitmap (size 4) may be configured as:
Using the above embodiments, 3GPP Rel-18 may configure the following: FeatureCombination (size 8): o {RedCap: true; smallData: true; slicing: true; CovEnh: true; Rel-18 Feature: true; Reserved: false}; maxNrofFeatures=5 (5 features set to true). Alternatively, FeatureCombinationIndicationBitmap (size 4) may be configured as:
In various example embodiments, slicing may be indicated implicitly or separately, and/or may be considered or partially in the RA partition. For example, each RA partition defined for the bitmaps in certain example embodiments may be used by the UE assigned to a specific slice group. Additionally or alternatively, slicing may be considered explicitly in the RA partition, but may be restricted to be combined only with a subset of other features (e.g., CovEnh) by using, for example, “CHOICE” type of signalling, an ASN.1 encoding representing a list of options to select.
As an example, a more dynamic list of features may be populated, as shown below, thus allow for almost infinite extendibility as any number of additional RA features could be added at the cost of additional signalling, such as follows:
In this way, the bit-cost in SI would be (1−N)*3+N=N+3-4N bits (e.g., 8-20 bits in case N=5, similarly as with previous example the size depending on how many feature combinations are indicated).
In certain example embodiments, slicing may be indicated in a feature combination, with overriding or partial applicability in the RA partition. Specifically, each RA partition (and associated feature combination) may correspond to (i.e., be assigned to) one slice group, with slice group=1 corresponding to a non-slicing case (i.e., default slice). For example, slice group 2 may correspond to feature combination 1 (e.g., SDT+RedCap), while slice group 3 may correspond to feature combination 2 (e.g., SDT+covEnh).
In various example embodiments, NE 210 may further indicate a sub-partitioning and/or prioritization within the configured combination of RA features. For example, when the RA feature combination includes two features (i.e., Redcap and SmallData), various sub-partitions may be indicated via an additional bitmap, such as RedCap UEs (such as UE 220) doing SDT, Redcap UEs doing non-SDT, non-RedCap UEs doing SDT, and non-Redcap UEs doing non-SDT.
According to some example embodiments, the other cause values may be bundled with slicing; since all services may be associated with at least one slice, prioritization of those services may not be necessary, such as follows:
In the example above, the bit cost is 4*. Alternatively, the slices may be signalled separately from the feature combination set and/or with special conditions, but with the feature sets becoming associated with any slice resources, by signalling the slicingGroup outside the FeatureCombination. At 203, UE 220 may then transmit a random access response to NE 210.
The two example encodings may indicate 4 purposes (e.g., redCap, smallData, slicing, and CovEnh), while 4 bits may be reserved to retain enough flexibility. FeaturesCombinationIndicationBitmap may comprise a bit for each feature set to “true” in the FeatureCombination, allowing any combination out of those features to be signalled.
In another example, a bit string may be used for the spare values in the FeatureCombination (similar to MIB), such as below:
As a result, the bit-cost in SI would be 3+(2-8)=5-11 bits added to the RA feature combination. The NE may only need to indicate the bitmap of feature combinations, and the ASN.1 definition of the FeatureCombination indicates the remaining features.
Using the above embodiments, 3GPP Rel-17 may be configured as FeatureCombination (size 8): {RedCap: true; smallData: true; slicing: true; CovEnh: true; Reserved: false}, maxNrofFeatures=4 (4 features set to true). Alternatively, Feature CombinationIndicationBitmap (size 4) may be configured as:
Using the above embodiments, 3GPP Rel-18 may configure the following: FeatureCombination (size 8): o {RedCap: true; smallData: true; slicing: true; CovEnh: true; Rel-18 Feature: true; Reserved: false}; maxNrofFeatures=5 (5 features set to true). Alternatively, FeatureCombinationIndicationBitmap (size 4) may be configured as:
In various example embodiments, slicing may be indicated implicitly or separately, and/or may be considered or partially in the RA partition. For example, each RA partition defined for the bitmaps in certain example embodiments may be used by the UE assigned to a specific slice group. Additionally or alternatively, slicing may be considered explicitly in the RA partition, but may be restricted to be combined only with a subset of other features (e.g., CovEnh) by using “CHOICE” type of signalling, an ASN.1 encoding representing a list of options to select.
As an example, a more dynamic list of features may be populated, as shown below, thus allow for almost infinite extendibility as any number of additional RA features could be added at the cost of additional signalling, such as follows:
In this way, the bit-cost in SI would be (1−N)*3+N=N+3-4N bits (e.g., 8-20 bits in case N=5, similarly as with previous example the size depending on how many feature combinations are indicated).
In certain example embodiments, slicing may be indicated in a feature combination, with overriding or partial applicability in the RA partition. Specifically, each RA partition (and associated feature combination) may correspond to (i.e., be assigned to) one slice group, with slice group=1 corresponding to a non-slicing case (i.e., default slice). For example, slice group 2 may correspond to feature combination 1 (e.g., SDT+RedCap), while slice group 3 may correspond to feature combination 2 (e.g., SDT+covEnh).
In various example embodiments, the NE may further indicate a sub-partitioning and/or prioritization within the configured combination of RA features. For example, when the RA feature combination includes two features (i.e., Redcap and SmallData), various sub-partitions may be indicated via an additional bitmap, such as Redcap UEs (such as the UE) doing SDT, Redcap UEs doing non-SDT, non-Redcap UEs doing SDT, and non-Redcap UEs doing non-SDT.
According to some example embodiments, all other cause values may be bundled with slicing; since all services may be associated with at least one slice, prioritization of those services may not be necessary, such as follows:
In the example above, the bit cost is 4*. Alternatively, the slices may be signalled separately from the feature combination set and/or with special conditions, but with the feature sets becoming associated with slice resources, by signalling the slicingGroup outside the FeatureCombination. At 303, the method may further include receiving a random access response from the UE.
The two example encodings may indicate 4 purposes (e.g., redCap, smallData, slicing, and CovEnh), while 4 bits may be reserved to retain enough flexibility. FeaturesCombinationIndicationBitmap may comprise a bit for each feature set to “true” in the FeatureCombination, allowing any combination out of those features to be signalled.
In another example, a bit string may be used for the spare values in the FeatureCombination (similar to MIB), such as below:
As a result, the bit-cost in SI would be 3+(2-8)=5-11 bits added to the RA feature combination. The NE may only need to indicate the bitmap of feature combinations, and the ASN.1 definition of the Feature Combination indicates the remaining features.
Using the above embodiments, 3GPP Rel-17 may be configured as FeatureCombination (size 8): {RedCap: true; smallData: true; slicing: true; CovEnh: true; Reserved: false}, maxNrofFeatures=4 (4 features set to true). Alternatively, Feature CombinationIndicationBitmap (size 4) may be configured as:
Using the above embodiments, 3GPP Rel-18 may configure the following: FeatureCombination (size 8): o {RedCap: true; smallData: true; slicing: true; CovEnh: true; Rel-18 Feature: true; Reserved: false}; maxNrofFeatures=5 (5 features set to true). Alternatively, FeatureCombinationIndicationBitmap (size 4) may be configured as:
In various example embodiments, slicing may be indicated implicitly or separately, and/or may be considered or partially in the RA partition. For example, each RA partition defined for the bitmaps in certain example embodiments may be used by the UE assigned to a specific slice group. Additionally or alternatively, slicing may be considered explicitly in the RA partition, but may be restricted to be combined only with a subset of other features (e.g., CovEnh) by using “CHOICE” type of signalling, an ASN.1 encoding representing s list of options to select.
As an example, a more dynamic list of features may be populated, as shown below, thus allow for almost infinite extendibility as any number of additional RA features could be added at the cost of additional signalling, such as follows:
In this way, the bit-cost in SI would be (1−N)*3+N=N+3−4N bits (e.g., 8-20 bits in case N=5, similarly as with previous example the size depending on how many feature combinations are indicated).
In certain example embodiments, slicing may be indicated in a feature combination, with overriding or partial applicability in the RA partition. Specifically, each RA partition (and associated feature combination) may correspond to (i.e., be assigned to) one slice group, with slice group=1 corresponding to a non-slicing case (i.e., default slice). For example, slice group 2 may correspond to feature combination 1 (e.g., SDT+RedCap), while slice group 3 may correspond to feature combination 2 (e.g., SDT+covEnh).
In various example embodiments, the NE may further indicate a sub-partitioning and/or prioritization within the configured combination of RA features. For example, when the RA feature combination includes two features (i.e., Redcap and SmallData), various sub-partitions may be indicated via an additional bitmap, such as Redcap UEs (such as the UE) doing SDT, Redcap UEs doing non-SDT, non-Redcap UEs doing SDT, and non-Redcap UEs doing non-SDT.
According to some example embodiments, all other cause values may be bundled with slicing; since all services may be associated with at least one slice, prioritization of those services may not be necessary, such as follows:
In the example above, the bit cost is 4*. Alternatively, the slices may be signalled separately from the feature combination set and/or with special conditions, but with the feature sets becoming associated with slice resources, by signalling the slicingGroup outside the FeatureCombination. At 403, the method may further include transmitting a random access response to the NE.
UE 510 may include one or more of a mobile device, such as a mobile phone, smart phone, personal digital assistant (PDA), tablet, or portable media player, digital camera, pocket video camera, video game console, navigation unit, such as a global positioning system (GPS) device, desktop or laptop computer, single-location device, such as a sensor or smart meter, or any combination thereof.
NE 520 may be one or more of a base station, such as an eNB or gNB, a serving gateway, a server, and/or any other access node or combination thereof. Furthermore, UE 510 and/or NE 520 may be one or more of a citizens broadband radio service device (CBSD).
NE 520 may further comprise at least one gNB-CU, which may be associated with at least one gNB-DU. The at least one gNB-CU and the at least one gNB-DU may be in communication via at least one F1 interface, at least one Xn-C interface, and/or at least one NG interface via a 5GC.
UE 510 and/or NE 520 may include at least one processor, respectively indicated as 511 and 521. Processors 511 and 521 may be embodied by any computational or data processing device, such as a central processing unit (CPU), application specific integrated circuit (ASIC), or comparable device. The processors may be implemented as a single controller, or a plurality of controllers or processors.
At least one memory may be provided in one or more of the devices, as indicated at 512 and 522. The memory may be fixed or removable. The memory may include computer program instructions or computer code contained therein. Memories 512 and 522 may independently be any suitable storage device, such as a non-transitory computer-readable medium. A hard disk drive (HDD), random access memory (RAM), flash memory, or other suitable memory may be used. The memories may be combined on a single integrated circuit as the processor, or may be separate from the one or more processors. Furthermore, the computer program instructions stored in the memory, and which may be processed by the processors, may be any suitable form of computer program code, for example, a compiled or interpreted computer program written in any suitable programming language.
Processors 511 and 521, memories 512 and 522, and any subset thereof, may be configured to provide means corresponding to the various blocks of
As shown in
The memory and the computer program instructions may be configured, with the processor for the particular device, to cause a hardware apparatus, such as UE, to perform any of the processes described above (i.e.,
In certain example embodiments, an apparatus may include circuitry configured to perform any of the processes or functions illustrated in
According to certain example embodiments, processor 511 and memory 512 may be included in or may form a part of processing circuitry or control circuitry. In addition, in some example embodiments, transceiver 513 may be included in or may form a part of transceiving circuitry.
The features, structures, or characteristics of example embodiments described throughout this specification may be combined in any suitable manner in one or more example embodiments. For example, the usage of the phrases “various embodiments,” “certain embodiments,” “some embodiments,” or other similar language throughout this specification refers to the fact that a particular feature, structure, or characteristic described in connection with an example embodiment may be included in at least one example embodiment. Thus, appearances of the phrases “in various embodiments,” “in certain embodiments,” “in some embodiments,” or other similar language throughout this specification does not necessarily all refer to the same group of example embodiments, and the described features, structures, or characteristics may be combined in any suitable manner in one or more example embodiments.
Additionally, if desired, the different functions or procedures discussed above may be performed in a different order and/or concurrently with each other. Furthermore, if desired, one or more of the described functions or procedures may be optional or may be combined. As such, the description above should be considered as illustrative of the principles and teachings of certain example embodiments, and not in limitation thereof.
One having ordinary skill in the art will readily understand that the example embodiments discussed above may be practiced with procedures in a different order, and/or with hardware elements in configurations which are different than those which are disclosed. Therefore, although some embodiments have been described based upon these example embodiments, it would be apparent to those of skill in the art that certain modifications, variations, and alternative constructions would be apparent, while remaining within the spirit and scope of the example embodiments.
| Number | Date | Country | Kind |
|---|---|---|---|
| PCT/CN2021/125775 | Oct 2021 | CN | national |
