Title - APPARATUS AND METHODS FOR THE EFFICIENT SIGNALING OF CHARACTERISTIC COMBINATIONS FOR RANDOM ACCESS CHANNEL SUBDIVISION

Abstract

Systems, methods, devices, and software products for efficiently signaling feature combinations for RACH subdivision. One method may include a network entity transmitting a radio resource configuration associated with at least one feature combination configuration and an associated random access resource configuration. The at least one feature combination configuration is associated with at least one of the following features: coverage boosting, network segmentation, reduced capacity user equipment, or small data transmission. The associated random access resource configuration is associated with access conditions for the at least one feature combination configuration.

Description

EFFICIENT SIGNALING OF A COMBINATION OF FEATURES FOR AN ACCESS CHANNEL SUBDIVISION RANDOM TECHNICAL FIELD: Some example embodiments may relate generally to mobile or wireless telecommunications 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 signaling combinations of features for random access channel (RACH) subdivision. BACKGROUND: Examples of mobile or wireless telecommunications systems may include 5G radio frequency (RF) RATs, 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 network architecture and radio systems. A 5G system is typically built on a 5G NR, although a 5G (or NG) network may also be built on an E-UTRA radio. NR is expected to support service categories such as enhanced mobile broadband (eMBB), ultra-reliable low-latency communications (URLLC), and massive machine-like communication. 2000833 of 41 (mMTC). NR is expected to provide extreme bandwidth, ultra-robust and low-latency connectivity, and massive interconnections to support the Internet of Things (IoT). Next-generation radio access network (NG-RAN) represents the RAN for 5G, which can provide radio access for NR, LTE, and LTE-A. It is noted that nodes in 5G that provide radio access functionality to a user equipment (e.g., similar to Node B in UTRAN or Evolved Node B (eNB) in LTE) may be referred to as Next-generation Node B (gNB) when built on an NR radio, and may be referred to as Next-generation eNB (NG-eNB) when built on an E-UTRA radio. SUMMARY: According to some example embodiments, a method may include transmitting, by a network entity, a radio resource configuration associated with at least one feature combination configuration and an associated random access resource configuration. The at least one feature combination configuration is associated with at least one of coverage boosting, network slicing, reduced capacity user equipment, or small data transmission. The associated random access resource configuration is associated with access conditions for the at least one feature combination configuration. According to certain example embodiments, an apparatus may include means for transmitting a radio resource configuration associated with at least one feature combination configuration and an associated random access resource configuration. The at least one 2000833 of 41 feature combination configurations are associated with at least one of coverage enhancement, network segmentation, reduced capacity user equipment, or small data transmission. The associated random access resource configuration is associated with access conditions for the at least one feature combination configuration. According to various example embodiments, a non-transitory computer-readable medium may be encoded with instructions that can, when executed in hardware, perform a method. The method may include transmitting a radio resource configuration associated with at least one feature combination configuration and an associated random access resource configuration. The at least one feature combination configuration is associated with at least one of coverage enhancement, network slicing, reduced capacity user equipment, or small data transmission. The associated random access resource configuration is associated with access conditions for the at least one feature combination configuration. According to some example embodiments, a computer program product may perform a method. The method may include transmitting a radio resource configuration associated with at least one feature combination configuration and an associated random access resource configuration. The at least one feature combination configuration is associated with at least one of coverage boosting, network slicing, reduced capacity user equipment, or small data transmission. The associated random access resource configuration is associated with conditions of 2000833 of 41 access for at least one feature combination configuration. According to 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 computer program code may be configured to, with the at least one processor, cause the apparatus to at least transmit a radio resource configuration associated with at least one feature combination configuration and an associated random access resource configuration. The at least one feature combination configuration is associated with at least one of coverage boosting, network slicing, reduced capacity user equipment, or small data transmission. The associated random access resource configuration is associated with access conditions for the at least one feature combination configuration. According to various example embodiments, an apparatus may include circuitry configured to transmit a radio resource configuration associated with at least one feature combination configuration and an associated random access resource configuration. The at least one feature combination configuration is associated with at least one of coverage boosting, network slicing, reduced capacity user equipment, or small data transmission. The associated random access resource configuration is associated with access conditions for the at least one feature combination configuration. According to some example embodiments, a method may include receiving, by a user equipment, a radio resource configuration. 2000833 of 41 associated with at least one feature combination configuration and an associated random access resource configuration. The at least one feature combination configuration is associated with at least one of coverage enhancement, network slicing, reduced capacity user equipment, or small data transmission. The associated random access resource configuration is associated with access conditions for the at least one feature combination configuration. According to certain example embodiments, an apparatus may include means for receiving a radio resource configuration associated with at least one feature combination configuration and an associated random access resource configuration. The at least one feature combination configuration is associated with at least one of coverage enhancement, network slicing, reduced capacity user equipment, or small data transmission. The associated random access resource configuration is associated with access conditions for the at least one feature combination configuration. According to various example embodiments, a non-transitory computer-readable medium may be encoded with instructions that can, when executed in hardware, perform a method. The method may include receiving a radio resource configuration associated with at least one feature combination configuration and an associated random access resource configuration. The at least one feature combination configuration is associated with at least one of coverage enhancement, network slicing, reduced capacity user equipment, or small data transmission. The radio resource configuration 2000833 of 41 associated random access resources is associated with access conditions for at least one feature combination configuration. According to some example embodiments, a computer program product may implement a method. The method may include receiving a radio resource configuration associated with at least one feature combination configuration and an associated random access resource configuration. The at least one feature combination configuration is associated with at least one of coverage enhancement, network slicing, reduced capacity user equipment, or small data transmission. The associated random access resource configuration is associated with access conditions for the at least one feature combination configuration. According to 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 computer program code may be configured to, with the at least one processor, cause the apparatus to at least receive a radio resource configuration associated with at least one feature combination configuration and an associated random access resource configuration. The at least one feature combination configuration is associated with at least one of coverage boosting, network slicing, reduced capacity user equipment, or small data transmission. The associated random access resource configuration is associated with access conditions for the at least one feature combination configuration. According to various example embodiments, an apparatus may 2000833 of 41 includes circuitry configured to receive a radio resource configuration associated with at least one feature combination configuration and an associated random access resource configuration. The at least one feature combination configuration is associated with at least one of coverage enhancement, network slicing, reduced capacity user equipment, or small data transmission. The associated random access resource configuration is associated with access conditions for the at least one feature combination configuration. BRIEF DESCRIPTION OF THE DRAWINGS: For a proper understanding of the example embodiments, reference should be made to the accompanying drawings, where: Figure 1(a) illustrates an example of a 2-stage RACH procedure. Figure 1(b) illustrates an example of a 4-stage RACH procedure. Figure 2 illustrates an example of a signaling diagram according to certain example embodiments. Figure 3 illustrates an example of a flowchart of a method according to various example embodiments. Figure 4 illustrates an example of a flowchart of a method according to various example embodiments. Figure 5 illustrates an example of various network devices according to some example embodiments. Figure 6 illustrates an example of a 5G network and system architecture. 2000833 of 41 according to certain example embodiments. DETAILED DESCRIPTION: 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. Therefore, the following detailed description of some example embodiments of systems, methods, apparatus, and computer program products for efficiently signaling combinations of features for RACH subdivision 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 can be used by the user equipment (UE) for random access, and may include time-bound RACH occasions (ROs) and / or RACH preambles available on each RO. When a UE transmits a physical random access channel (PRACH) preamble, the UE may transmit in 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 has determined a suitable RO, the UE may randomly select one of the valid preambles for transmission on the RO from among the available ROs, as configured by the network. Figure 1(a) illustrates an example of a 2-stage RACH procedure for RACH resource subdivision, as defined in 3GPP Edition (Rel)-16. Similarly, Figure 1(b) illustrates an example of a 2-stage RACH procedure for RACH resource subdivision. 2000833 of 41 4-stage RACH procedure supported in 3GPP Rel-15. Subdivision in the 2-stage RACH procedure may require subdividing the entire set of RACH resources into two pools, each pool dedicated to the corresponding RACH procedure (i.e., 2-stage or 4-stage RACH). In 3GPP Rel-16, the gNB may transmit the two groupings using a RACH-ConfigCommonTwoStepRA information element (IE), which may be further subdivided via a GroupBConfiguredTwoStepRA-r16 IE contained in the RACHConfigCommonTwoStepRA IE. The UE may then indicate whether it is using a 2-stage or 4-stage RACH procedure in message A (MsgA) for the 2-stage RACH procedure, or in Msg1 for the 4-stage RACH procedure, respectively, by selecting and transmitting a RACH resource from the corresponding resource pool. Contention-free radio access (CFRA) resources and CBRA resources may be further subdivided. 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 compete for RACH resources in contention-based pooling. For CBRA subdivision, different UEs may select the same CBRA resource and / or may interfere with other UEs, resulting in an unwanted RACH collision. Currently, in order to enable the network to identify each feature based on the preamble / RO used by the UE, they can 2000833 of 41 further subdivide RACH resources to support initial access of some 3GPP Rel-17 features, such as: Feature RACH indication / split reason CovEnh To indicate the need for coverage boosting (e.g. for Msg3 repeat request) to the network Slicing To indicate the need for prioritization and isolation of a segment (including RACH isolation) to the network RedCap To indicate the reduced capabilities of the UE to the network such that the network can accommodate subsequent transmissions (compared to a regular UE) SDT To indicate the Small Data Transmission (SDT) procedure, therefore to request a larger Msg3 size or MSGA size (compared to the regular Msg3 / MSGA size for non-SDT / legacy resumption) The subdivision of RACH resources can be achieved either by subdividing the ROs for different features (i.e., different ROs can be dedicated to different features) or by subdividing the preambles associated with an RO for different features (i.e., different preambles of an RO can be dedicated to different features, as defined in 3GPP Rel-16 for a subdivision of 2-stage and 4-stage RACH). However, dedicating ROs per feature can cause delays in the RA procedure, because 2000833 of 41 The UE requesting a feature may need to wait until a valid RO becomes available, with fewer valid ROs available per feature due to resource splitting. Instead, preambles in a dedicated RO per feature can be achieved, for example, by using a RACH mask, and may allow all features to use any RO, resulting in lower RA latency being achieved for any service in the cell. However, this may limit the number of preambles available per feature. In turn, the probability of unwanted RACH collisions may increase, which may also indirectly increase latency times.Supported cell sizes may also be limited in this case, because an increased cell size may require omitting cyclic offsets when creating PRACH preamble sequences, thereby achieving larger distances between the cyclic offsets of PRACH root sequences. The number of root sequences may be limited by cell scheduling and by inherent mathematical properties of the sequences themselves. The problem of collision and preamble limitation may worsen when more features need to be separated. In order to configure RACH resources, it may be necessary to select each cell and use one of 256 PRACH configurations, determining the RO periodicity and the placement of the ROs in time. Prior to 3GPP Rel-16, RACH capacity and sizing have been possible due to the limited number of RACH resources required. For example, with an RO periodicity of 20 ms and a carrier bandwidth of 40 MHz, approximately 3% of the resources can be allocated. 2000833 of 41 dedicated to RACH. Instead, starting 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, the network may need to allocate, in addition to the legacy RACH resources, a sufficient number of RACH resources for each additional RACH configuration dedicated to 3GPP Rel-17 features. This can ensure that the tolerable collision probability and latency key performance indicators (KPIs) are within the allowable 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 more efficient, streamlined, and future-proof signaling of feature combinations for AR subdivision. Therefore, certain example embodiments discussed below are directed toward improvements in computer-related technology. Figure 2 illustrates a signaling diagram depicting an example of efficient signaling of feature combinations for RACH subdivision. NE 210 and UE 220 may be similar to NE 510 and UE 520, as illustrated in Figure 5, according to certain example embodiments. At 201, NE 210 may transmit a radio resource configuration associated with at least one feature combination, and an associated random access resource configuration, to UE 220, which 2000833 of 41 may include signaling to indicate, to the UE 220, feature combinations and associated radio access resources divided among the feature combinations applicable to a RACH configuration for the NE 210 and the UE 220. Some example embodiments may use a fixed number of bits explicitly reserved for signaling, where each end of RA may be indicated by 1 bit, and K bits may be reserved for subsequent changes. For example, each RA subdivision may be determined according to the RACHCommon configuration based on at least one intended feature, or feature combination sets. For example, two Information Elements (e.g., bitmaps) may indicate the features or feature combination sets corresponding to the given RA subdivision.A first bitmap (i.e., indicated FeatureCombination) may indicate to the UE the applicable RA purposes / features (e.g., RedCap, Small Data, CovEnh, etc.) used by the given cell (N bits max, thus, N max purposes / features), while a second bitmap (i.e., indicated FeatureCombinationIndicationBitmap) may indicate the actual RA feature and prioritization combinations (M combinations max, e.g., RedCap + Small Data combination) applicable to the UE from the features / purposes set in the first bitmap, as follows: FeatureCombination ::= SEQUENCE { redCap ENUMERATED {true} OPTIONAL, smallData ENUMERATED {true} OPTIONAL, slicing ENUMERATED {true} OPTIONAL, 2000833 of 41 covEnh ENUMERATED {true} OPTIONAL, spare1 ENUMERATED {true} OPTIONAL, spare2 ENUMERATED {true} OPTIONAL, spare3 ENUMERATED {true} OPTIONAL, spare4 ENUMERATED {true} OPTIONAL} FeaturesCombinationIndicationBitmap ::= BIT STRING (SIZE (maxNrofFeatures)) maxNrofFeatures ::= INTEGER (2..8) The two example encodings can indicate 4 purposes (e.g., redCap, smallData, slicing, and CovEnh), while reserving 4 bits to maintain sufficient flexibility. The FeaturesCombinationIndicationBitmap can comprise one bit for each feature set to true in the FeatureCombination, allowing any combination of those features to be signaled. In another example, a bit string can be used for the fallback values ​​in the FeatureCombination (similar to a Master Information Block (MIB)), such as: FeatureCombination ::= SEQUENCE { redCap ENUMERATED {true} OPTIONAL, smallData ENUMERATED {true} OPTIONAL, slicing ENUMERATED {true} OPTIONAL, covEnh ENUMERATED {true} OPTIONAL, spare BIT STRING (SIZE(4)) } 2000833 of 41 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) definition of the 5 FeatureCombination indicates the remaining features. Using the above embodiments, 3GPP Rel-17 can be configured as FeatureCombination (size 8): {RedCap: true; smallData: true; slicing: true; CovEnh: true; Reserved: false}, maxNrofFeatures = 4 (4 features set to true). Alternatively, FeatureCombinationIndicationBitmap (size 4) can be set to:_______ RedCap Small Data Slicing CovEnh combination of SDT + RedCap 1 1 0 0 Slicing + CovEnh + combination 1 1 0 0 Using the above embodiments, 3GPP Rel-18 can 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) can be set to:_______________________________________________ RedCap Small Data Slicing CovEnh R18 Feature 2000833 of 41 RedCap Small Data Slicing CovEnh Feature of R18 combination of SDT + RedCap 1 1 0 0 0 Slicing + CovEnh + combination 1 1 0 0 0 Slicing + CovEnh + R.18 1 1 0 0 1 In various example embodiments, slicing may be indicated implicitly or separately, and / or may be considered or partially included in the RA subdivision. For example, each RA subdivision 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 explicitly considered in the RA subdivision, but may be restricted to being combined with only a subset of other features (e.g., CovEnh) using, for example, the CHOICE signaling type, an ASN.1 encoding representing a list of options to be selected. As an example, a more dynamic list of features can be populated as shown below, thus allowing for almost infinite expandability, because any number could be added. 2000833 of 41 additional RA features at the cost of additional signaling, as follows: FeatureCombination ::= SEQUENCE (SIZE (1..maxNrofFeatures)) OF RAFeature RA-Feature :: CHOICE { redCap, smallData, slicing, covEnh, reserved1, -- for Rel-18+ Feature potential reserved2, -- for Rel-18+ Feature potential reserved3, -- for Rel-18+ Feature potential reserved4, -- for Rel-18+ Feature potential} FeaturesCombinationIndicationBitmap ::= BIT STRING (SIZE (maxNrofFeatures)) maxNrofFeatures ::= INTEGER (1..N) / / e.g. n = 5 Thus, the cost in bits in SI would be (1-N) * 3 + N = N + 3-4N bits (for example, 8-20 bits in the case of N = 5, the size depending, similarly to the case of the previous example, on how many combinations of characteristics are indicated). In certain example embodiments, slicing may be indicated on a combination of features, with invalidation or partial applicability to the RA subdivision. Specifically, each RA subdivision (and associated combination of features) may correspond to (i.e., be assigned to) a group 2000833 of 41 segments, with segment group = 1 corresponding to a case without segmentation (i.e., default segment). For example, segment group 2 may correspond to feature combination 1 (e.g., SDT + RedCap), while segment group 3 may correspond to feature combination 2 (e.g., SDT + covEnh). In various example embodiments, NE 210 may further indicate a subdivision and / or prioritization within the configured combination of RA features. For example, when the combination of RA features includes two features (i.e., RedCap and SmallData), various subdivisions may be indicated via an additional bitmap, such as RedCap UEs (such as UE 220) that perform SDT, RedCap UEs that perform non-SDT, non-RedCap UEs that perform SDT, and non-RedCap UEs that perform non-SDT. According to some example embodiments, the other cause values ​​may be grouped by slicing; because all services may be associated with at least one segment, prioritization of those services may not be necessary, as follows: FeatureCombination ::= SEQUENCE (SIZE (1..maxNrofFeatures)) OF RAfeature RA-feature ::= SEQUENCE { sliceGroup INTEGER (1..4), ra-Feature CHOICE { redCap, smallData, 2000833 of 41 covEnh, reservedl -- for Rel-18+ potential characteristic} FeaturesCombinationIndicationBitmap ::= BIT STRING (SIZE (maxNrofFeatures)) maxNrofFeatures ::= INTEGER (1..N) / / e.g. n = 5 In the previous example, the bit cost is 4*. Alternatively, the segments may be signaled separately from the feature combination set and / or with special conditions, but with the feature sets remaining associated with any segment resources, signaling the slicingGroup outside of the FeatureCombination. At 203, the UE 220 may then transmit a random access response to the NE 210. Figure 3 illustrates an example of a flowchart of a method that may be performed by an NE, such as NE 520 illustrated in Figure 5, according to various example embodiments. At 301, the method may include transmitting a radio resource configuration to a UE (which may be similar to UE 510 in Figure 5), which may include signaling to indicate, to the UE, feature combinations and associated radio access resources divided among the feature combinations applicable to a RACH configuration for the NE and the UE. Some example embodiments may use a fixed number of bits explicitly reserved for signaling, where each end of RA may be indicated by 1 bit, and K bits may be reserved for subsequent changes. For example, each RA subdivision may be determined according to the RACHCommon configuration based on at least one intended feature, or sets 2000833 of 41 of feature combination. For example, two bitmaps may indicate the features or feature combination sets corresponding to the given RA subdivision. A first bitmap (i.e., indicated FeatureCombination) may indicate to the UE the applicable RA purposes / features (e.g., RedCap, Small Data, CovEnh, etc.) used by the given cell (N bits max, hence N max purposes / features), while a second bitmap (i.e., indicated FeatureCombinationIndicationBitmap) may indicate the actual RA feature and prioritization combinations (M combinations max, e.g., RedCap + Small Data combination) applicable to the UE from the features / purposes set forth in the first bitmap, as follows: FeatureCombination : := SEQUENCE { redCap ENUMERATED {true} OPTIONAL, smallData ENUMERATED {true} OPTIONAL, slicing ENUMERATED {true} OPTIONAL, covEnh ENUMERATED {true} OPTIONAL, spare1 ENUMERATED {true} OPTIONAL, spare2 ENUMERATED {true} OPTIONAL, spare3 ENUMERATED {true} OPTIONAL,} spare4 ENUMERATED {true} OPTIONAL FeaturesCombinationIndicationBitmap ::= BIT STRING (SIZE (maxNrofFeatures)) maxNrofFeatures ::= INTEGER (2..8) 2000833 of 41 The two example encodings can indicate 4 purposes (e.g., redCap, smallData, slicing, and CovEnh), while reserving 4 bits to maintain sufficient flexibility. The FeaturesCombinationIndicationBitmap can comprise one bit for each feature set to true in the FeatureCombination, allowing any combination of those features to be signaled. In another example, a bit string can be used for the fallback values ​​in the FeatureCombination (similar to a MIB), as follows: FeatureCombination ::= SEQUENCE { redCap ENUMERATED {true} OPTIONAL, smallData ENUMERATED {true} OPTIONAL, slicing ENUMERATED {true} OPTIONAL, covEnh ENUMERATED {true} OPTIONAL, spare BIT STRING (SIZE(4)) } 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 can be configured as FeatureCombination (size 8): {RedCap: true; smallData: true; slicing: true; CovEnh: true; Reserved: false}, maxNrofFeatures = 4 (4 features set to true). Alternatively, 2000833 of 41 FeatureCombinationIndicationBitmap (size 4) can be set to: RedCap Small Data Slicing CovEnh combination of SDT + RedCap 1 1 0 0 Slicing + CovEnh + combination 1 1 0 0 Using the above embodiments, 3GPP Rel-18 can 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) can be set to: ___________________________________________ RedCap Small Data Slicing CovEnh Feature of R18 combination of SDT + RedCap 1 1 0 0 0 Slicing + CovEnh + combination 1 1 0 0 0 Slicing + CovEnh + R.18 1 1 0 0 1 In various example embodiments, slicing may be indicated implicitly or separately, and / or may be considered or partially included in the RA subdivision. For example, each RA subdivision defined for the bitmaps in certain example embodiments may be 2000833 of 41 used by the UE assigned to a specific segment group. Additionally or alternatively, slicing may be explicitly considered in the RA subdivision, but may be restricted to combining only with a subset of other features (e.g., CovEnh) using the CHOICE signaling type, an ASN.1 encoding representing a list of options to be selected. As an example, a more dynamic list of features can be populated as shown below, thus allowing for almost infinite expandability, because any number of additional AR features could be added at the cost of additional signaling, as follows: FeatureCombination ::= SEQUENCE (SIZE (1..maxNrofFeatures)) OF RAFeature RA-Feature :: CHOICE { redCap, smallData, slicing, covEnh, reserved1, -- for Rel-18+ Feature potential reserved2, -- for Rel-18+ Feature potential reserved3, -- for Rel-18+ Feature potential reserved4, -- for Rel-18+ Feature potential} FeaturesCombinationIndicationBitmap ::= BIT STRING (SIZE (maxNrofFeatures)) 2000833 of 41 maxNrofFeatures ::= INTEGER (1..N) / / for example, n = 5 Thus, the cost in bits in SI would be (1-N) * 3 + N = N + 3-4N bits (for example, 8-20 bits in the case of N = 5, the size depending, similarly to the case of the previous example, on how many combinations of characteristics are indicated). In certain example embodiments, slicing may be indicated on a feature combination, with invalidation or partial applicability in the RA subdivision. Specifically, each RA subdivision (and associated feature combination) may correspond to (i.e., be assigned to) a segment group, with segment group = 1 corresponding to a case of no slicing (i.e., default segment). For example, segment group 2 may correspond to feature combination 1 (e.g., SDT + RedCap), while segment group 3 may correspond to feature combination 2 (e.g., SDT + covEnh). In various example embodiments, the NE may further indicate a subdivision and / or prioritization within the configured combination of RA features. For example, when the combination of RA features includes two features (i.e., RedCap and SmallData), various subdivisions may be indicated via an additional bitmap, such as RedCap UEs (such as the UE) that perform SDT, RedCap UEs that perform non-SDT, non-RedCap UEs that perform SDT, and non-RedCap UEs that perform non-SDT. According to some example embodiments, all other cause values ​​can be grouped with slicing; because all the 2000833 of 41 services can be associated with at least one segment, prioritization of those services may not be necessary, as follows: FeatureCombination ::= SEQUENCE (SIZE (1..maxNrofFeatures)) OF RAfeature RA-feature ::= SEQUENCE { sliceGroup INTEGER (1..4), ra-Feature CHOICE { redCap, smallData, covEnh, reserved1 -- for Rel-18+ Feature potential} FeaturesCombinationIndicationBitmap ::= BIT STRING (SIZE (maxNrofFeatures)) maxNrofFeatures ::= INTEGER (1..N) / / e.g. n = 5 In the previous example, the bit cost is 4*. Alternatively, the segments may be signaled separately from the feature combination set and / or with special conditions, but with the feature sets remaining associated with segment resources, signaling the slicingGroup outside the FeatureCombination. At 303, the method may further include receiving a random access response from the UE. Figure 4 illustrates an example of a flowchart of a method that may be performed by a UE, such as UE 520 illustrated in Figure 5, according to various example embodiments. At 401, the method may include receiving a radio resource configuration from an NE (which may be 2000833 of 41 similar to NE 510 in Figure 5), which may include signaling to indicate, to the NE, feature combinations and associated radio access resources divided among the feature combinations applicable to a RACH configuration for the NE and the UE. Some example embodiments may use a fixed number of bits explicitly reserved for signaling, where each end of RA may be indicated by 1 bit, and K bits may be reserved for subsequent changes. For example, each RA subdivision may be determined according to the RACHCommon configuration based on at least one intended feature, or feature combination sets. For example, two bitmaps may indicate the features or feature combination sets corresponding to the given RA subdivision.A first bitmap (i.e., indicated FeatureCombination) may indicate to the UE the applicable RA purposes / features (e.g., RedCap, Small Data, CovEnh, etc.) used by the given cell (N bits max, thus, N max purposes / features), while a second bitmap (i.e., indicated FeatureCombinationIndicationBitmap) may indicate the actual RA feature and prioritization combinations (M combinations max, e.g., RedCap + Small Data combination) applicable to the UE from the features / purposes set in the first bitmap, as follows: FeatureCombination ::= SEQUENCE { redCap ENUMERATED {true} OPTIONAL, smallData ENUMERATED {true} OPTIONAL, slicing ENUMERATED {true} OPTIONAL, 2000833 of 41 covEnh ENUMERATED {true} OPTIONAL, spare1 ENUMERATED {true} OPTIONAL, spare2 ENUMERATED {true} OPTIONAL, spare3 ENUMERATED {true} OPTIONAL, spare4 ENUMERATED {true} OPTIONAL} FeaturesCombinationIndicationBitmap ::= BIT STRING (SIZE (maxNrofFeatures)) maxNrofFeatures ::= INTEGER (2..8) The two example encodings can indicate 4 purposes (e.g., redCap, smallData, slicing, and CovEnh), while reserving 4 bits to maintain sufficient flexibility. The FeaturesCombinationIndicationBitmap can comprise one bit for each feature set to true in the FeatureCombination, allowing any combination of those features to be signaled. In another example, a bit string can be used for the fallback values ​​in the FeatureCombination (similar to a MIB), as follows: FeatureCombination : := SEQUENCE { redCap ENUMERATED {true} OPTIONAL, smallData ENUMERATED {true} OPTIONAL, slicing ENUMERATED {true} OPTIONAL, covEnh ENUMERATED {true} OPTIONAL, spare BIT STRING (SIZE(4)) } 2000833 of 41 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 5 features. Using the above embodiments, 3GPP Rel-17 can be configured as FeatureCombination (size 8): {RedCap: true; smallData: true; slicing: true; CovEnh: true; Reserved: false}, maxNrofFeatures = 4 (4 features set to true). Alternatively, FeatureCombinationIndicationBitmap (size 4) can be set to:_______ RedCap Small Data Slicing CovEnh combination of SDT + RedCap 1 1 0 0 Slicing + CovEnh + combination 1 1 0 0 Using the above embodiments, 3GPP Rel-18 can 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) can be set to: ____________________________________________ RedCap Small Data Slicing CovEnh Feature of R18 combination 1 1 0 0 0 2000833 of 41 RedCap Small Data Slicing CovEnh Feature of R18 of SDT + RedCap Slicing + CovEnh + combination 1 1 0 0 0 Slicing + CovEnh + R.18 1 1 0 0 1 In various example embodiments, slicing may be indicated implicitly or separately, and / or may be considered or partially included in the RA subdivision. For example, each RA subdivision defined for the bitmaps in certain example embodiments may be used by the UE assigned to a specific segment group. Additionally or alternatively, slicing may be explicitly considered in the RA subdivision, but may be restricted to being combined with only a subset of other features (e.g., CovEnh) using the CHOICE signaling type, an ASN.1 encoding representing a list of options to be selected. As an example, a more dynamic list of features can be populated as shown below, thus allowing for almost infinite expandability, because any number of additional AR features could be added at the cost of additional signaling, such as 2000833 of 41 follows: Featurecombination ::= SEQUENCE (SIZE (1..maxNrofFeatures)) OF RAFeature RA-Feature :: CHOICE { redCap, smallData, slicing, covEnh, reserved1, -- for Rel-18+ Feature potential reserved2, -- for Rel-18+ Feature potential reserved3, -- for Rel-18+ Feature potential reserved4, -- for Rel-18+ Feature potential} FeaturesCombinationIndicationBitmap ::= BIT STRING (SIZE (maxNrofFeatures)) maxNrofFeatures ::= INTEGER (1..N) / / e.g. n = 5 Thus, the cost in bits in SI would be (1-N) * 3 + N = N + 3-4N bits (for example, 8-20 bits in the case of N = 5, the size depending, similarly to the case of the previous example, on how many combinations of characteristics are indicated). In certain example embodiments, slicing may be indicated on a feature combination, with invalidation or partial applicability to the RA subdivision. Specifically, each RA subdivision (and associated feature combination) may correspond to (i.e., be assigned to) a segment group, with segment group = 1 corresponding to a case without 2000833 of 41 segmentation (i.e., default segment). For example, segment group 2 may correspond to feature combination 1 (e.g., SDT + RedCap), while segment group 3 may correspond to feature combination 2 (e.g., SDT + covEnh). In various example embodiments, the NE may further indicate a subdivision and / or prioritization within the configured combination of RA features. For example, when the combination of RA features includes two features (i.e., RedCap and SmallData), various subdivisions may be indicated via an additional bitmap, such as RedCap UEs (such as the UE) that perform SDT, RedCap UEs that perform non-SDT, non-RedCap UEs that perform SDT, and non-RedCap UEs that perform non-SDT. According to some example embodiments, all other cause values ​​may be grouped by slicing; because all services may be associated with at least one segment, prioritization of those services may not be necessary, as follows: FeatureCombination ::= SEQUENCE (SIZE (1..maxNrofFeatures)) OF RAfeature RA-feature ::= SEQUENCE { sliceGroup INTEGER (1..4), ra-Feature CHOICE { redCap, smallData, covEnh, 2000833 of 41 reservedl -- for Rel-18+ Potential Feature} FeaturesCombinationIndicationBitmap ::= BIT STRING (SIZE (maxNrofFeatures)) maxNrofFeatures ::= INTEGER (1..N) / / e.g. n = 5 In the previous example, the bit cost is 4*. Alternatively, the segments may be signaled separately from the feature combination set and / or with special conditions, but with the feature sets remaining associated with segment resources, signaling the slicingGroup outside the FeatureCombination. At 403, the method may further include transmitting a random access response to the NE. Figure 5 illustrates an example of a system according to certain example embodiments. In an example embodiment, a system may include multiple devices, such as, for example, UE 510 and / or NE 520. The UE 510 may include one or more of a mobile device, such as a cellular telephone, a smartphone, a personal digital assistant (PDA), a tablet or portable media player, a digital camera, a pocket video camera, a video game console, a navigation unit, such as a global positioning system (GPS) device, a desktop or laptop computer, a single-location device, such as a sensor or smart meter, or any combination thereof. The 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. In addition, the UE 510 and / or the NE 520 may be 2000833 of 41 one or more than one citizen broadband radio service device (CBSD). The 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. The UE 510 and / or NE 520 may include at least one processor, indicated respectively as 511 and 521. The processors 511 and 521 may be embodied by any computing or data processing device, such as a central processing unit (CPU), an application-specific integrated circuit (ASIC), or a 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. The 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. In addition, the computer program instructions stored in the memory and which may be processed by the 2000833 of 41 processors may be any suitable form of computer program code, for example, a computer program compiled or interpreted 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 Figures 2-4. Although not shown, the devices may also include positioning hardware, such as GPS or microelectromechanical system (MEMS) hardware, that may be used to determine a location of the device. Other sensors are also permitted, and may be configured to determine location, elevation, speed, orientation, and so forth, such as barometers, compasses, and the like. As shown in Figure 5, transceivers 513 and 523 may be provided, and one or more devices may also include at least one antenna, illustrated respectively as 514 and 524. The device may have multiple antennas, such as an array of antennas configured for multiple-input-multiple-output (MIMO) communications, or multiple antennas for multiple RATs. Other configurations of these devices may be provided, for example. Transceivers 513 and 523 may be a transmitter, a receiver, both a transmitter and a receiver, or a unit or device that may be configured for both transmission and reception. The memory and computer program instructions may be configured, with the processor for the particular device, to cause a hardware apparatus, such as a UE, to perform any of the processes described. 2000833 of 41 above (i.e., Figures 2-4). Thus, in certain example embodiments, a non-transitory computer-readable medium may be encoded with computer instructions that, when executed in hardware, perform a process such as one of the processes described herein. Alternatively, certain example embodiments may be implemented entirely in hardware. In certain example embodiments, an apparatus may include circuitry configured to perform any of the processes or functions illustrated in Figures 2-4. For example, the circuitry may be hardware-only circuit implementations, such as analog and / or digital circuitry. In another example, the circuitry may be a combination of hardware and software circuitry, such as a combination of analog and / or digital hardware circuitry with software or firmware, and / or any portion of hardware processors with software (including digital signal processors), software, and at least one memory that work together to cause an apparatus to perform various processes or functions. In yet another example, the circuitry may be hardware circuitry and / or processors, such as a microprocessor or a portion of a microprocessor, that includes software, such as firmware, for its operation.Software may not be present in the circuitry when it is not necessary for the hardware to function. Figure 6 illustrates an example of a 5G network and system architecture according to certain example embodiments. Multiple network functions are shown that may be implemented as software operating as part of a network device or dedicated hardware, such as a network device. 2000833 of 41 itself or dedicated hardware, or as a virtual function functioning as a network device or dedicated hardware. The NE and UE illustrated in Figure 6 may be similar to UE 510 and NE 520, respectively. The user plane function (UPF) may provide services such as mobility, intra-RAT and inter-RAT routing and forwarding of data packets, packet inspection, user plane Quality of Service (QoS) processing, downlink packet caching, and / or triggering of downlink data notifications. The application function (AF) may primarily interact with the core network to facilitate application use of traffic routing and interact with the policy framework. According to certain embodiments, the processor 511 and the memory 512 may be included in or may form a part of the processing circuitry or the control circuitry. Furthermore, in some example embodiments, the transceiver 513 may be included in or may form a part of the transception circuitry. The features, structures, or characteristics of example embodiments described throughout this specification may be combined in any suitable manner into one or more example embodiments. For example, the use of the terms "various embodiments," "certain embodiments," "some embodiments," or other similar language throughout this specification refers to the fact that a feature, structure, or characteristic described in connection with an example embodiment may be included in at least one example embodiment. Thus, occurrences of the 2000833 of 41 expressions in various embodiments, in certain embodiments, in some embodiments or other similar language throughout this specification do not necessarily all refer to the same group of example embodiments, and the features, structures or characteristics described may be combined in any suitable manner in one or more example embodiments. Additionally, if desired, the various functions or procedures discussed above can be performed in a different order and / or simultaneously. Furthermore, if desired, one or more of the functions or procedures described may be optional or may be combined. In this regard, the foregoing description should be considered as illustrative of the principles and contents of certain example embodiments, and not as a limitation thereof. One skilled in the art will readily understand that the exemplary embodiments discussed above may be implemented with procedures in a different order, and / or with hardware elements in configurations that are different from those disclosed. Therefore, although some embodiments have been described based on these exemplary embodiments, it would be apparent to those skilled in the art that certain modifications, variations, and alternative constructions would be apparent, while remaining within the spirit and scope of the exemplary embodiments. Partial glossary 3GPP Third Generation Partnership Project 5G Fifth Generation 2000833 of 41 5GC Fifth Generation Core 5GS Fifth Generation System ASIC Application Specific Integrated Circuit ASN Abstract Syntax Notation BS Base Station CBRA Contention-Based Random Access CBSD Citizens Broadband Radio Service Device CFRA Contention-Free Random Access CE Coverage Boosting CG Configured Grant CN Backbone Network C-RNTI Cell Radio Network Temporary Identifier CovEnh Coverage Boosting CPU Central Processing Unit eMBB Enhanced Mobile Broadband eMTC Enhanced Machine Type Communication eNB Evolved Node B EPS Evolved Packet System gNB Next Generation Node B GPS Global Positioning System HDD Hard Disk Drive IE Information Element KPI Key Performance Indicator LTE Long Term Evolution LTE-A Long Term Evolution Advanced 2000833 of 41 MAC Medium Access Control MEMS Micro Electro Mechanical System MIB Master Information Block MIMO Multiple Input Multiple Output MME Mobility Management Entity mMTC Massive Machine Type Communication MTC Machine Type Communication NAS Non-Access Stratum NB-IoT Narrowband Internet of Things NE Network Entity NG Next Generation NG-eNB Next Generation Evolved Node B NG-RAN Next Generation Radio Access Network NR New Radio NR-U New Unlicensed Radio PDA Personal Digital Assistance PRACH Physical Random Access Channel PUR Periodic Uplink Resources RA Random Access RACH Random Access Channel RAM Random Access Memory RAN Radio Access Network RAT Radio Access Technology RedCap Reduced Capacity RNTI Radio Network Temporary Identifier 2000833 of 41 RO Random Access Channel Occasion RRC Radio Resource Control SD Small Data SDT Small Data Broadcast SI System Information SIB System Information Block SMF Session Management Function SRB Signaling Radio Bearer UE User Equipment UMTS Universal Mobile Telecommunications System UPF User Plane Function URLLC Ultra-Reliable Low Latency Communication UTRAN Universal Mobile Telecommunications System Terrestrial Radio Access Network WLAN Wireless Local Area Network 2000833 of 41 SCHMUKLER PABLO - 20117733352 Digitally signed by PORTALTRAMITES - INPI Date: 2022.10.17 12:39:05 -03:00 Reason: Digitally signed by the INPI Location: Buenos Aires, Argentina 2000833

Claims

1. An apparatus comprising means for: transmitting a radio resource configuration associated with at least one feature combination configuration and an associated random access resource configuration, wherein the at least one feature combination configuration is associated with at least one coverage boost, network segmentation, reduced capacity user equipment, or small data transmission feature, wherein the associated random access resource configuration is associated with access conditions for the at least one feature combination configuration, and wherein the apparatus is characterized in that the radio resource configuration comprises at least one radio access split allocated to at least one group of network segments. Twelve claims follow.