IP Library › Granted Patent US 12,574,974
Granted Patent B2
US 12,574,974 · App. 18/059,762 · Granted Mar 10, 2026

UE RACH resource configuration selection function and resource prioritization to support slicing

Inventors: Eiko Seidel (Sauerlach, DE); Sarun Selvanesan (Berlin, DE); Thomas Wirth (Berlin, DE); Thomas Fehrenbach (Berlin, DE); Thomas Schierl (Berlin, DE); Cornelius Hellge (Berlin, DE)
Assignee: FRAUNHOFER-GESELLSCHAFT ZUR FOERDERUNG DER ANGEWANDTEN FORSCHUNG E.V.
H04W74/0833H04W74/0836H04W74/0838
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,574,974
App. No.
18/059,762
Granted
Mar 10, 2026
Kind
B2
Abstract

A user device, UE, for a wireless communication network, is connectable to two or more of a plurality of network slices of the wireless communication network, wherein a slice specific random access channel, RACH, resource configuration is associated with one or more of the plurality of slices. Responsive to a first RACH event associated with a first slice, the UE is to determine whether there is an ongoing RACH procedure triggered by a second RACH event associated with a second slice. In case of an ongoing RACH procedure, the UE is to prohibit an additional RACH procedure triggered by the first RACH event associated with the first slice, and/or suspend the additional RACH procedure for a certain time, and/or stop the ongoing RACH procedure and start the additional RACH procedure, and/or modify the ongoing RACH procedure, and/or modify the ongoing RACH procedure to start the additional RACH procedure.

Claims (79)

1 . A user device, UE, for a wireless communication network, the UE comprising:

one or more antennas or an antenna array having a plurality of antennas,

a signal processor, and

a transceiver,

wherein the transceiver is connectable to two or more of a plurality of network slices of the wireless communication network, wherein a slice specific random access channel, RACH, resource configuration is associated with one or more of the plurality of slices,

wherein, responsive to a first RACH event associated with a first slice, the signal processor is configured to determine whether there is an ongoing RACH procedure triggered by a second RACH event associated with a second slice, and

wherein, in case of the ongoing RACH procedure, the signal processor is configured to perform at least one of the following:

prohibiting an additional RACH procedure triggered by the first RACH event associated with the first slice,

suspending the additional RACH procedure for a certain time,

stopping the ongoing RACH procedure and start the additional RACH procedure,

modifying the ongoing RACH procedure, and

modifying the ongoing RACH procedure to start the additional RACH procedure.

2 . The user device, UE, of claim 1 , wherein the slice specific RACH resource configuration specifies one or more resource configurations and one or more parameters for a RACH procedure, including at least one of the following:

a physical random-access channel, PRACH, preamble, e.g., comprising a preamble format, a preamble sequence, a sequence length, a subcarrier spacing used for the preamble, a cyclic prefix, a guard time length,

a beam index,

a trigger to switch beams,

resources used for the PRACH, e.g., time and/or frequency and/or spatial resources,

one or more parameters for determining one or more root sequences and cyclic shifts of the root sequences in the PRACH preamble sequence,

an index to a logical root sequence table

a cyclic shift, N CS , and

a set type, e.g., unrestricted, restricted set A, or restricted set B.

3 . The user device, UE, of claim 1 , wherein the signal processor is configured to abort any additional RACH procedure in case there is an ongoing RACH procedure so that, at any point in time, there is only a single ongoing RACH procedure.

4 . The user device, UE, of claim 1 , wherein the signal processor is configured to suspend the additional RACH procedure until the ongoing RACH procedure is completed.

5 . The user device, UE, of claim 4 , wherein the signal processor is configured to store information related to the additional RACH procedure to be used when starting the additional RACH procedure on the second slice, once the ongoing RACH procedure on the first slice is completed.

6 . The user device, UE, of claim 5 , wherein, responsive to the ongoing RACH procedure having failed for a predefined number of times, the signal processor is configured to stop or defer the ongoing RACH procedure, and to start the additional RACH procedure.

7 . The user device, UE, of claim 1 , wherein the signal processor is configured to prohibit or suspend the additional RACH procedure in case at least any one of:

parallel RACH procedures using different slice specific RACH resource configurations are not allowed, e.g., by a certain standard specification, by the defined UE capabilities

parallel RACH procedures using different slice specific RACH resource configurations are disabled, e.g., for a certain cell, a certain UE, a certain service type, a certain priority level, a certain slice, or a certain RACH trigger,

the ongoing RACH procedure has a higher priority than the additional RACH procedure,

the additional RACH procedure uses a different configuration when compared to the ongoing RACH procedure, e.g., a different numerology, a different subcarrier spacing, a different frequency band or a bandwidth part, and

the additional RACH procedure is sent to a different Base Station, BS, or Distributed Unit, DU, than the ongoing RACH procedure.

8 . The user device, UE, of claim 1 , wherein the signal processor is configured to suspend the additional RACH procedure once the ongoing RACH procedure is partly completed.

9 . The user device, UE, of claim 8 , wherein the signal processor is configured to start the additional RACH procedure such that there are no parallel uplink transmissions associated with the ongoing RACH procedure and the additional RACH procedure.

10 . The user device, UE, of claim 8 , wherein the signal processor is configured to start the additional RACH procedure responsive to a certain event associated with the ongoing RACH procedure, the certain event comprising one or more of:

the UE sending a RRC Connection Request Message 3 for the ongoing RACH procedure in an uplink,

the UE receiving a RACH Response, RAR, Message 2 for the ongoing RACH procedure in a downlink,

the UE sending a RACH Preamble Message 1 for the ongoing RACH procedure in the uplink, and

the UE receiving an RRC connection reconfiguration message in the downlink.

11 . The user device, UE, of claim 1 , wherein the signal processor is configured to stop the ongoing RACH procedure and start the additional RACH procedure

during the whole ongoing RACH procedure or until a certain stage of the ongoing RACH procedure, and/or

responsive to one or more pre-emption criteria being fulfilled.

12 . The user device, UE, of claim 11 , wherein the one or more pre-emption criteria comprise one or more of the following:

certain parameters in the RRC RACH resource configuration, like a relative slice priority, or a QoS flow or a logical channel priority,

an event that triggered the RACH procedure, like a PDCCH order, or a handover, or a CHO, or an RRC re-establishment,

a type of user plane message pending for transmission, e.g., to which logical channel, or QoS flow, or PDN session, or slice identity the message belongs to,

a QoS attribute of a user plane message pending for transmission, like priority, or latency or reliability of the logical channel or data flow the message belongs to,

a type of message pending for transmission, e.g., prioritization of an RRC control plane message transmitted over a Signaling Radio Bearer over a user plane message transmitted over a of Data Radio Bearer, and

an entity that triggered the RACH procedure, e.g., prioritization of a UE triggered RACH procedure over a base station triggered RACH procedure or SL-UE triggered RACH procedure, like a group lead UE, or an RSU.

13 . The user device of claim 1 , wherein, to modify the ongoing RACH procedure, the signal processor is configured to modify a certain message, e.g. Msg3, transmitted by the transceiver during the ongoing RACH procedure by incorporating into the certain message, in addition to an indication of the first slice, an indication of the second slice so as to allow a base station to provide in response to the certain message parameters for a configuration of the first and second slices.

14 . The user device of claim 1 , wherein, to modify the ongoing RACH procedure to start the additional RACH procedure, the signal processor is configured to modify a certain message, e.g. Msg3, transmitted by the transceiver during the ongoing RACH procedure by replacing an indication of the first slice with an indication of the second slice so as to allow a base station to provide in response to the certain message parameters for a configuration of the second slice.

15 . The user device, UE, of claim 1 , wherein the additional RACH procedure and the ongoing RACH procedure are triggered at the same time or are triggered within a certain time window.

16 . The user device, UE, of claim 1 , wherein the signal processor is configured or pre-configured to support two or more parallel ongoing RACH procedures, the ongoing RACH procedures being associated with different slices.

17 . The user device, UE, of claim 16 , wherein the signal processor is only permitted to perform two or more PRACH procedures for different slices, if the slice is configured to one or more of

use of a different BWP, and

operate on a different carrier frequency with a frequency gap of delta x between a first radio frequency, e.g. operating on FR1, and a second radio frequency, e.g. operating on FR2.

18 . A wireless communication system, comprising

one or more user devices, UEs, for a wireless communication network,

wherein the UE is connectable to two or more of a plurality of network slices of the wireless communication network, wherein a slice specific random access channel, RACH, resource configuration is associated with one or more of the plurality of slices,

wherein, responsive to a first RACH event associated with a first slice, the UE is to determine whether there is an ongoing RACH procedure triggered by a second RACH event associated with a second slice, and

wherein, in case of an ongoing RACH procedure, the UE is to

prohibit an additional RACH procedure triggered by the first RACH event associated with the first slice, and/or

suspend the additional RACH procedure for a certain time, and/or

stop the ongoing RACH procedure and start the additional RACH procedure, and/or

modify the ongoing RACH procedure, and/or

modify the ongoing RACH procedure to start the additional RACH procedure,

and/or one or more base stations, BSs, for a wireless communication network,

wherein the BS is to support one or more of a plurality of slices of the wireless communication network, wherein a slice specific random access channel, RACH, configuration is associated with one or more of the plurality of slices,

wherein the BS is to configure one or more user devices, UEs, to enable or to disable parallel ongoing RACH procedures.

19 . The wireless communication network of claim 18 , wherein,

the wireless communication network provides the plurality of network slices, and

a radio access network of the wireless communication network, RAN, comprises a cloud-RAN, C-RAN, the C-RAN comprising a plurality of slice specific distributed units, DUs, and one or more central units, CUs, shared by some or all of the slices.

20 . A method for operating a user device, UE, for a wireless communication network, wherein the UE is connectable to two or more of a plurality of network slices of the wireless communication network, wherein a slice specific random access channel, RACH, resource configuration is associated with one or more of the plurality of slices, the method comprising:

responsive to a first RACH event associated with a first slice, determining whether there is an ongoing RACH procedure triggered by a second RACH event associated with a second slice, and

in case of an ongoing RACH procedure,

prohibiting an additional RACH procedure triggered by the first RACH event associated with the first slice, and/or

suspending the additional RACH procedure for a certain time, and/or

stopping the ongoing RACH procedure and start the additional RACH procedure, and/or

modifying the ongoing RACH procedure, and/or

modifying the ongoing RACH procedure to start the additional RACH procedure.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 14, 2023
From: SEIDEL, EIKO; SELVANESAN, SARUN; WIRTH, THOMAS; FEHRENBACH, THOMAS; SCHIERL, THOMAS; HELLGE, CORNELIUS
To: FRAUNHOFER-GESELLSCHAFT ZUR FOERDERUNG DER ANGEWANDTEN FORSCHUNG E.V.
Reel/Frame 062694/0158 →
Priority Claims (1)
EP 20177545 · May 29, 2020 · regional
Continuity (2)
Continuation PCTEP2021064243 · May 27, 2021
Related Publication 20230180301A1 · Jun 8, 2023
References Cited (44)
US 12231238B2 · Jeon et al. · 2025 [cited by applicant]
US 20170201968A1 · Nam · 2017 [cited by examiner]
US 20170367120A1 · Murray · 2017 [cited by examiner]
US 20180249441A1 · Ryoo et al. · 2018 [cited by applicant]
US 20180368179A1 · He et al. · 2018 [cited by applicant]
US 20190098672A1 · Murray et al. · 2019 [cited by applicant]
US 20190124561A1 · Faccin et al. · 2019 [cited by applicant]
US 20190174406A1 · Hwang et al. · 2019 [cited by applicant]
US 20190174536A1 · Han et al. · 2019 [cited by applicant]
US 20190215761A1 · Hirata et al. · 2019 [cited by applicant]
US 20190230584A1 · Lou et al. · 2019 [cited by applicant]
US 20190261185A1 · Velev · 2019 [cited by examiner]
US 20190320467A1 · Freda et al. · 2019 [cited by applicant]
US 20190327663A1 · Wirth et al. · 2019 [cited by applicant]
US 20200059987A1 · Hong et al. · 2020 [cited by applicant]
US 20220295361A1 · Naseer-Ul-Islam et al. · 2022 [cited by applicant]
US 20230029004A1 · Gao et al. · 2023 [cited by applicant]
CN 106572516A · 2017 [cited by applicant]
CN 107347202A · 2017 [cited by applicant]
CN 108811168A · 2018 [cited by applicant]
CN 110383942A · 2019 [cited by applicant]
CN 110741713A · 2020 [cited by applicant]
CN 113678423A · 2021 [cited by applicant]
CN 114946225A · 2022 [cited by applicant]
EP 3457799A1 · 2019 [cited by applicant]
EP 3598833A1 · 2020 [cited by applicant]
EP 3641433A1 · 2020 [cited by applicant]
KR 20190018170A · 2019 [cited by applicant]
KR 20200049736A · 2020 [cited by applicant]
WO WO2018127505A1 · 2018 [cited by applicant]
WO WO2018175809A1 · 2018 [cited by applicant]
WO WO2018232259A1 · 2018 [cited by applicant]
WO WO2020190646A1 · 2020 [cited by applicant]
CMCC, “Second round email discussion for R17 proposals on slicing”, 3GPP Draft; RP-192599, 3rd Generation Partnership Project (3GPP), vol. TSG RAN, No. 86. Sitges, Barcelona, Dec. 2019. [cited by applicant]
3GPP, “NR and NG-RAN Overall Description; Stage 2 Rel. 16 ”, TS 38.300, V16.0.0, 3gpp.org, Dec. 2019. [cited by applicant]
3GPP, “NR Medium Access Control (MAC) protocol specification”, ETSI TS 138.321, V15.8.0, Release 15, etsi.org, Jan. 2020. [cited by applicant]
3GPP, “5G, NG-RAN; F1 Application Protocol (F1AP)”, 3GPP TS 38.473, V15.8.0, Rel. 15, etsi.org, Jan. 2020. [cited by applicant]
3GPP, “Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); LTE; Numbering, addressing and identification”, GPP TS 23.003, V15.8.0, Release 15, etsi.org, Sep. 2… [cited by applicant]
OPPO, “Enhancements of 4-steps RACH in NR-U”, vol. RAN WG2, No. Xi'an, China; Apr. 6, 2019-Apr. 12, 2019, (Apr. 6, 2019), 3GPP Draft; R2-1903283—RACH Enhancements in NR-U, 3rd Generation Partnership Project (3GPP). [cited by applicant]
Pantech, “Priority of execution the RA procedure”, vol. RAN WG2, 3GPP Draft; R2-115185 Priority of Execution the RA Procedure, 3rd Generation Partnership Project (3GPP), 2011. [cited by applicant]
Xiaomi, “PRACH partitioning, access and congestion control Consideration for Network Slicing”, vol. RAN WG2, No. 97, Athens, Greece; Feb. 13, 2017-Feb. 17, 2017, 3GPP Draft; R2-1700998 , 3rd Generation Partnership Proje… [cited by applicant]
Xiaomi, “Visibility of Slicing to UE”, vol. RAN WG2, No. 97, Spokane, USA; Apr. 3, 2017-Apr. 7, 2017, 3GPP Draft; R2-1702529, 3rd Generation Partnership Project (3GPP). [cited by applicant]
3Gpp, “Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3”, TS 24.501, V15.6.0, Release 15, etsi.org, Jan. 2020. [cited by applicant]
3GPP TSG RAN\tsg_ran Dec. 2, 2019 RP-192599 Report. [cited by applicant]
Cited By (1)
US 12,750,755