MAPPING SUBSCRIBERS TO OPERATORS IN SHARED RADIO UNIT ARCHITECTURE USING RAN SLICING

Disclosed is a method for mapping a subscriber to a mobile network operator in a fifth-generation New Radio (5G NR) cellular telecommunication radio access network (RAN). The method is performed by a Radio Unit (RU) device operated by a first network operator and includes: transmitting system information including first information indicating network slices and second information indicating Physical Random Access Channel (PRACH) occasions mapped to the network slices, receiving a preamble of a Random Access Channel (RACH) during one of the PRACH occasions indicated by the second information, determining a second network operator based on the one of the PRACH occasions during which the preamble of the RACH is received, and transmitting the preamble of the RACH to a Distributed Unit (DU) device that is operated by the second network operator determined based on the one of the PRACH occasions during which the preamble of the RACH is received.

BACKGROUND

Radio Access Network (RAN) slicing capabilities are included in Third Generation Partnership Project (3GPP) Release 17. In addition, Radio Unit (RU) sharing can be used in Open RAN (O-RAN) architectures.

BRIEF SUMMARY

According to the present disclosure, RAN slicing capabilities, for example, as included in 3GPP Release 17 are combined with an O-RAN disaggregated architecture and a novel concept of RU sharing among multiple network operators, in order to map subscribers to their respective network operators in a manner that is more efficient than conventional methods that do use RU sharing.

A method for mapping a subscriber to a mobile network operator in a fifth-generation New Radio (5G NR) cellular telecommunication radio access network (RAN) according to the present disclosure may be characterized as including: transmitting, by a Radio Unit (RU) device operated by a first network operator, system information including first information indicating a plurality of network slices and second information indicating a plurality of Physical Random Access Channel (PRACH) occasions mapped to the network slices; receiving, by the RU device operated by the first network operator, from a UE device, a preamble of a Random Access Channel (RACH) during one of the PRACH occasions mapped to the network slices that is indicated by the second information; determining, by the RU device operated by the first network operator, a second network operator different from the first network operator based on the one of the PRACH occasions mapped to the network slices that is indicated by the second information during which the preamble of the RACH is received; and transmitting, by the RU device operated by the first network operator, the preamble of the RACH and information included in the RACH to a Distributed Unit (DU) device that is operated by the second network operator determined based on the one of the PRACH occasions mapped to the network slices that is indicated by the second information during which the preamble of the RACH is received.

The method may further comprise transmitting, by the RU device operated by the first network operator, information included in the RACH to the DU device that is operated by the second network operator determined based on the one of the PRACH occasions mapped to the network slices that is indicated by the second information during which the preamble of the RACH is received.

The first information may include=a Slice Service Type (SST) value of Single-Network Slice Selection Assistance Information (S-NSSAI) that is stored by the UE device, and the second information indicating the PRACH occasions mapped to the network slices may include a Slice Differentiator (SD) value of the S-NSSAI that is stored by the UE device.

The system information may include a plurality of items of Single-Network Slice Selection Assistance Information (S-NSSAI), each of the items of S-NSSAI may include a Slice Service Type (SST) value that indicates one of the network slices, and each of the items of S-NSSAI includes a Slice Differentiator (SD) value that may indicate one of the PRACH occasions. The SST value included in a first one of the items of S-NSSAI may be same as the SST value included in a second one of the items of S-NSSAI. The one of the PRACH occasions indicated by the SD value included in a first one of the items of S-NSSAI may be same as the one of the PRACH occasions indicated by the SD value included in a second one of the items of S-NSSAI. The SD value included in each of the items of S-NSSAI may be different.

The method may further comprise receiving, by the UE device, information that indicates a bandwidth part from the DU device operated by the second network operator; and receiving, by the RU device operated by the first network operator, data corresponding to one of the network slices indicated by the first information that is transmitted by the UE device using the bandwidth part. The method may further comprise transmitting, by the RU device operated by the first network operator, to the DU device operated by the second network operator, the data corresponding to the one of the network slices indicated by the first information that is transmitted by the UE device using the bandwidth part.

A method for mapping a subscriber to a mobile network operator in a fifth-generation New Radio (5G NR) cellular telecommunication radio access network (RAN) according to the present disclosure may be characterized as including: receiving, by a User Equipment (UE) device, system information including first information indicating a plurality of network slices and second information indicating a plurality of Physical Random Access Channel (PRACH) occasions mapped to the network slices; and transmitting, by the UE device, a preamble of a Random Access Channel (RACH) during one of the PRACH occasions mapped to the network slices indicated by the second information.

The first information may indicates a service type; and the method may further comprise transmitting, by the UE device, data corresponding to the service type.

The first information may include a Slice Service Type (SST) value of Single-Network Slice Selection Assistance Information (S-NSSAI) that is stored by the UE device, and the second information indicating the PRACH occasions mapped to the network slices may include a Slice Differentiator (SD) value of the S-NSSAI that is stored by the UE device.

The system information may include a plurality of items of Single-Network Slice Selection Assistance Information (S-NSSAI), each of the items of S-NSSAI may include a Slice Service Type (SST) value that indicates one of the network slices, and each of the items of S-NSSAI may include a Slice Differentiator (SD) value that indicates one of the PRACH occasions. The SST value included in a first one of the items of S-NSSAI may be same as the SST value included in a second one of the items of S-NSSAI. The one of the PRACH occasions indicated by the SD value included in a first one of the items of S-NSSAI may be same as the one of the PRACH occasions indicated by the SD value included in a second one of the items of S-NSSAI.

A User Equipment (UE) device that operates in a fifth-generation New Radio (5G NR) cellular telecommunication radio access network (RAN) according to the present disclosure may be characterized as including at least one memory that stores computer executable instructions; and at least one processor that executes the computer executable instructions to cause actions to be performed, the actions including: receive system information including first information indicating a plurality of network slices and second information indicating a plurality of Physical Random Access Channel (PRACH) occasions mapped to the network slices; and transmit a preamble of a Random Access Channel (RACH) during one of the PRACH occasions mapped to the network slices indicated by the second information.

The first information may include a Slice Service Type (SST) value of Single-Network Slice Selection Assistance Information (S-NSSAI) that is stored by the UE device, and the second information indicating the PRACH occasions includes a Slice Differentiator (SD) value of the S-NSSAI that is stored by the UE device. The system information may include a plurality of items of Single-Network Slice Selection Assistance Information (S-NSSAI), each of the items of S-NSSAI may include a Slice Service Type (SST) value that indicates one of the network slices, and each of the items of S-NSSAI may include a Slice Differentiator (SD) value that indicates one of the PRACH occasions. The SST value included in a first one of the items of S-NSSAI may be same as the SST value included in a second one of the items of S-NSSAI. The one of the PRACH occasions indicated by the SD value included in a first one of the items of S-NSSAI may be same as the one of the PRACH occasions indicated by the SD value included in a second one of the items of S-NSSAI.

DETAILED DESCRIPTION

3GPP TR 21.917 V0.5.0 (2022-04) (Release 17) mentions “enhancement of RAN Slicing for NR”. Slice-based cell selection or reselection may be achieved by broadcasting System Information (SI) that includes supported slice information of a current cell and neighbor cells, and cell reselection priority per slice for cell reselection assistance. Also, a SI message may be included in an RRCRelease message slice for cell reselection assistance. In addition, supported slice of a serving cell in a SI message may be broadcast for cell selection assistance. For Slice based Random Access Channel (RACH) configuration, separated PRACH occasions (e.g., time-frequency domain and preambles) can be configured for each slice or slice group, and RACH parameters prioritization can be configured for each slice or slice group.

A Network Slice Selection Assistance Information (NSSAI) format has been defined, which includes a Slice/Service Type (SST) value and a Slice Differentiator (SD) value. For example, an SST value of 1 may indicate an enhanced Mobile Broadband (eMBB) Slice/Service Type, an SST value of 2 may indicate an Ultra Reliable Low Latency Communications (URLLC) Slice/Service Type, an SST value of 3 may indicate a massive Internet of Things (mIoT) Slice/Service Type, SST values from 4 to 127 may indicate a standard Slice/Service Type, and SST values from 128 to 255 may indicate an operator-specific Slice/Service Type.

A Single NSSAI (S-NSSAI) having an STT value corresponding to a standard STT with an SD value of null may indicate that all Public Land Mobile Networks (PLMNs) are applicable to the S-NSSAI. Also, an S-NSSAI having an STT value corresponding to an operator-specific STT with an SD value of null may indicate that the S-NSSAI is PLMN specific. Any S-NSSAI having an SD value that is not null may indicate that the S-NSSAI is PLMN specific.

For example, an S-NSSAI having an SST value of 1 and an SD value of null may imply eMBB traffic. Also, an S-NSSAI having an SST value of 3 and an SD value of null may imply IoT traffic. In addition, an S-NSSAI having an SST value of 3 and an SD value that is not null may imply custom IoT traffic.

According to the present disclosure, S-NSSAIs are mapped to particular services, slices, and operators. A set of SD values are split into different disjoint subsets (e.g., SD ranges) and each of the SD value subsets or ranges are assigned to one network operator. Accordingly, network operators can be differentiated based on the SD values of S-NSSAIs. Thus, different S-NSSAIs can be mapped to different network operators. Each network operator has the flexibility to support multiple slices of the same service type. For example, a network operator with an SD value range between 0000 and 000F, can offer multiple eMBB services for an SST value of 1.

FIG.1is a block diagram illustrating a communication system100in accordance with embodiments described herein. The communication system100employs a shared Radio Unit (RU) architecture. More particularly, the communication system100includes an RU device102, which is configured to use resources (e.g., Physical Resource Blocks (PRBs))104-1that are allocated for use by the host network operator, PRBs104-2having a bandwidth BW1allocated to a first guest network operator, PRBs104-3having a bandwidth BW2allocated to a second guest network operator, and PRBs104-4having a bandwidth BW3allocated to a third guest network operator.

The RU device102is coupled to a plurality of Distributed Unit (DU) devices, including a DU device106-1that is operated by the host network operator, a DU device106-2that is operated by the first guest network operator, a DU device106-3that is operated by the second guest network operator, and a DU device106-4that is operated by the third guest network operator. The DU device106-1that is operated by the host network operator is coupled to a Centralized Unit (CU) device108-1that is operated by the host network operator. The DU device106-2that is operated by the first guest network operator is coupled to a CU device108-2that is operated by the first guest network operator. The DU device106-3that is operated by the second guest network operator is coupled to a CU device108-3that is operated by the second guest network operator. The DU device106-4that is operated by the third guest network operator is coupled to a CU device108-4that is operated by the third guest network operator.

InFIG.1, the host network operator owns the RU device102that is shared among the host network operator and all the guest network operators. The bandwidth allocation among the host and guest network operators are agreed upon and configured using the 5G BW-Part (BWP) concept. Each network operator owns its own DU device and CU device. The DU devices and CU devices owned by all of the network operators are synchronized to the RU device102on both downlink (DL) and uplink (UL). The RU device102operated by the host network operator broadcasts Master Information Block (MIB), System Information Block (SIB) Type1 (SIB1) and potentially some other SIBs.

FIG.2is a block diagram illustrating a communication system100′ in accordance with embodiments described herein. The communication system100′ shown inFIG.2is similar in many relevant respects to the system100system inFIG.1. The communication system100′ shown inFIG.2includes a plurality of User Equipment (UE) devices, including a UE device110-1that is operated by a subscriber of the host network operator, a UE device110-2that is operated by a subscriber of the first guest network operator, a UE device110-3that is operated by a subscriber of the second guest network operator, and a UE device110-4that is operated by a subscriber of the third guest network operator.

InFIG.2, the host network operator broadcasts the System Information (SI) and the PRACH Occasion for each S-NSSAI in an SI message. Each PRACH occasion can be assigned within the BW (BWP) allocated to the appropriate network operator. Because the communication system100′ allocates separate PRACH occasions to different slices/slice groups (i.e., the slice groups are mapped to different network operators), a UE device will transmit a RACH on the appropriate Physical RACH (PRACH) occasion allocated to its network operator. The communication system100′ knows which network operator an UE device belongs to, immediately upon receipt of the RACH. The RACH is handled by the DU device of the appropriate network operator, instead of being handled by the DU device106-1operated by the host network operator as done in conventional techniques, which increases the speed at which information from the RACH is provided to the DU device of the appropriate network operator.

For example, when the UE device110-1operated by the subscriber of the host network operator uses a first PRACH occasion112-1to transmit a first RACH114-1to the RU device102, the RU device102routes or transmits information included in the RACH114-1to the DU device106-1operated by the host network operator and/or the CU device108-1operated by the host network operator. Also, when the UE device110-2operated by the subscriber of the first guest network operator uses a second PRACH occasion112-2to transmit a second RACH114-2, the RU device102routes information included in the second RACH114-2to the DU device106-2operated by the first guest network operator and/or the CU device108-2operated by the first guest network operator. Additionally, when the UE device110-3operated by the subscriber of the second guest network operator uses a third PRACH occasion112-3to transmit a third RACH114-3, the RU device102routes or transmits information included in the third RACH114-3to the DU device106-3operated by the second guest network operator and/or the CU device108-3operated by the second guest network operator. In addition, when the UE device110-4operated by the subscriber of the third guest network operator uses a fourth PRACH occasion112-4to transmit a fourth RACH114-4, the RU device102routes or transmits information included in the fourth RACH114-4to the DU device106-4operated by the third guest network operator and/or the CU device108-4operated by the third guest network operator.

FIG.3is a diagram illustrating an example of network slice information300in accordance with embodiments described herein. The network slice information300shown inFIG.3is simplified for ease of illustration. The network slice information300may be used to configure the communication system100′ shown inFIG.2. The network slice information300may be stored in a table, wherein each row of the table represent an item of network slice information and each column of the table represent a field of each item of network slice information. More particularly, each item of network slide information includes a Slice Service Type (SST) value, which is associated with a system-unique Slice Differentiator (SD) value, a value indicating a Mobile Network Operator (MNO), a value indicating one or more Physical Resource Blocks (PRBs) corresponding to a bandwidth part, and a value indicating a Physical Random Access Channel (PRACH) occasion.

FIG.4is a block diagram illustrating an example of a Radio Unit (RU) device102in accordance with embodiments described herein. In some embodiments, one or more special-purpose computing systems may be used to implement the RU device102. Accordingly, various embodiments described herein may be implemented in software, hardware, firmware, or in some combination thereof. The RU device102may include one or more memory devices404, one or more central processing units (CPUs)410, I/O interfaces412, other computer-readable media414, and network connections416.

The one or more memory devices404may include one or more various types of non-volatile and/or volatile storage technologies. Examples of the one or more memory devices404may include, but are not limited to, flash memory, hard disk drives, optical drives, solid-state drives, various types of random access memory (RAM), various types of read-only memory (ROM), other computer-readable storage media (also referred to as processor-readable storage media), or the like, or any combination thereof. The one or more memory devices404may be utilized to store information, including computer-readable instructions that are utilized by the one or more CPUs410to perform actions, including those of embodiments described herein.

The one or more memory devices404may have stored thereon a Radio Unit (RU) module406. The Radio Unit (RU) module40623configured to implement and/or perform some or all of the functions of the RU device102described herein and interface with radio transceiver418. The one or more memory devices404may also store other programs and data408, which may include PRACH information indicating one or more PRACH occasions that are associated with host and guest network operators (e.g., the network slice information300shown inFIG.3), RU digital certificates, connection recovery algorithms, connection recovery rules, network protocols, O-RAN operating rules, user interfaces, operating systems, etc.

Network connections416are configured to communicate with other computing devices including a Distributed Unit (DU) device. In various embodiments, the network connections416include transmitters and receivers, a layer 2 (L2) switch and physical network ports (not illustrated) to send and receive data as described herein, and to send and receive instructions, commands and data to implement the processes described herein. The L2 switch plays a role as Ethernet forwarding/transparent bridge in order to support Radio Unit (RU) copy and combine function for O-RAN cascade mode. I/O interfaces412may include enhanced Common Public Radio Interface (eCPRI) ports, Antenna Interface Standards Group (AISG) interfaces, other data input or output interfaces, or the like. Other computer-readable media414may include other types of stationary or removable computer-readable media, such as removable flash drives, external hard drives, or the like.

FIG.5is a block diagram illustrating an example of a Distributed Unit (DU) device106in accordance with embodiments described herein. In some embodiments, one or more special-purpose computing systems may be used to implement the Distributed Unit (DU) device106. Accordingly, various embodiments described herein may be implemented in software, hardware, firmware, or in some combination thereof. The DU device106may include one or more memory devices504, one or more central processing units (CPUs)510, I/O interfaces512, other computer-readable media514, and network connections516.

The one or more memory devices504may include one or more various types of non-volatile and/or volatile storage technologies. Examples of the one or more memory devices504may include, but are not limited to, flash memory, hard disk drives, optical drives, solid-state drives, various types of random access memory (RAM), various types of read-only memory (ROM), other computer-readable storage media (also referred to as processor-readable storage media), or the like, or any combination thereof. The one or more memory devices504may be utilized to store information, including computer-readable instructions that are utilized by the one or more CPUs510to perform actions, including those of embodiments described herein.

The one or more memory devices504may have stored thereon a Distributed Unit (DU) module506. The Distributed Unit (DU) module506is configured to implement and/or perform some or all of the functions of the Distributed Unit (DU)502described herein. The one or more memory devices504may also store other programs and data508, which may include a Radio Link Control (RLC) module that implements a RLC sublayer of the 5G NR protocol stack, which interfaces to PDCP sublayer from above and MAC sublayer from below, a Media Access Control (MAC) module that implements a MAC sublayer of the 5G NR protocol stack, which interfaces to the RLC sublayer from above and a Physical (PHY) layer from below, and a PHY module that implements the PHY layer for Enhanced Mobile Broadband (eMBB) communications, Machine-Type-Communications (mMTC), and Ultra-Reliable Low Latency Communications (URLLC).

Network connections516are configured to communicate with other computing devices including one or more Radio Unit (RU) devices, a Centralized Unit (CU) device, and a RAN Intelligent Controller (RIC) device. In various embodiments, the network connections516include transmitters and receivers, a layer 3 (L2) switch and physical network ports (not illustrated) to send and receive data as described herein, and to send and receive instructions, commands and data to implement the processes described herein. The L2 switch plays a role as Ethernet forwarding/transparent bridge in order to support Radio Unit (RU) copy and combine function for O-RAN cascade mode. I/O interfaces512may include PCI interfaces, PCI-Express interfaces, other data input or output interfaces, or the like. Other computer-readable media514may include other types of stationary or removable computer-readable media, such as removable flash drives, external hard drives, or the like.

FIG.6is a block diagram illustrating an example of a Centralized Unit (CU) device108in accordance with embodiments described herein. In some embodiments, one or more special-purpose computing systems may be used to implement the Centralized Unit (CU) device108. Accordingly, various embodiments described herein may be implemented in software, hardware, firmware, or in some combination thereof. The DU device106may include one or more memory devices604, one or more central processing units (CPUs)610, I/O interfaces612, other computer-readable media614, and network connections616.

The one or more memory devices604may include one or more various types of non-volatile and/or volatile storage technologies. Examples of the one or more memory devices604may include, but are not limited to, flash memory, hard disk drives, optical drives, solid-state drives, various types of random access memory (RAM), various types of read-only memory (ROM), other computer-readable storage media (also referred to as processor-readable storage media), or the like, or any combination thereof. The one or more memory devices604may be utilized to store information, including computer-readable instructions that are utilized by the one or more CPUs610to perform actions, including those of embodiments described herein.

The one or more memory devices604may have stored thereon a Centralized Unit (CU) module606. The Centralized Unit (CU) module606is configured to implement and/or perform some or all of the functions of the Centralized Unit (CU)602described herein. The one or more memory devices604may also store other programs and data608, which may include Radio Resource Control (RRC) module that implements an RRC a layer within the 5G NR protocol stack in a control plane of a gNB, a Service Data Adaptation Protocol (SDAP) module that implements a sublayer in a plane in the gNB, and a Packet Data Convergence Protocol (PDCP) module that implements a PDCP layer within the 5G NR protocol stack.

Network connections616are configured to communicate with other computing devices including one or more Radio Unit (RU) devices, one or more Distributed Unit (CU) devices, one or more devices that implement Access and Mobility Management Function (AMF) operations, and one or more devices that implement User Plane Function (UPF) operations. In one or more implementations, the network connections616includes connections made via N2, N3, F1-C, and F1-U interfaces, for example.

FIG.7illustrates a logical flow diagram showing an example of a method700of operating a UE device in accordance with embodiments described herein. The method700begins at702.

At702, the UE device receives system information including first information that indicates a plurality of network slices, second information that indicates a plurality of Physical Random Access Channel (PRACH) occasions mapped to the network slices, and third information that indicates a range of one or more Slice Differentiator (SD) values (i.e., an SD range) associated with the network slices.

For example, the UE device110-2operated by the subscriber of the first guest network operator receives first information that indicates a plurality of SST values (e.g., 1, 2, 3) corresponding to a plurality of slice service types (e.g., eMBB, URLLC, MIoT), second information that indicates a plurality of PRACH occasions (e.g., information that indicates the PRACH occasions 2, 3, 4), and third information that indicates a plurality of SD ranges (e.g., 000000000000000000000101-000000000000000000001001,000000000000000000001010-000000000000000000001110, 000000000000000000001111-000000000000000000010011) associated with the network slices. Up to eight items of Single-Network Slice Selection Assistance Information (S-NSSAI) may be stored by and configured in the UE device110-2. The UE device110-2maps the items of S-NSSAI that have an SD value included in the SD range indicated by the third information received at702to the PRACH occasions indicated by the second information received at702. The method700then proceeds to704.

At704, the UE device transmits a preamble of a RACH during the PRACH occasion indicated by the second information received at702. For example, the UE device110-2operated by the subscriber of the first guest network operator transmits a preamble of the RACH114-2during the second PRACH occasion112-2shown inFIG.2. The method700then proceeds to706.

At706, the UE device receives information that indicates a bandwidth part from a device operated by a guest network operator. For example, after the UE device110-2operated by the subscriber of the first guest network operator has been successfully authenticated, and Radio Resource Control (RRC) and Non-Access-Stratum (NAS) have been established between the UE device110-2and the CU device108-2operated by the first guest network operator and a device operated by the first guest network operator that performs an Access and Mobility Management Function (AMF), respectively, the UE device110-2receives information that indicates a contiguous set of Physical Resource Blocks (PRBs) on a particular carrier frequency (e.g., bandwidth part BW1shown inFIG.2) from the CU device108-2or the DU device106-2by RRC signaling. The method700then proceeds to708.

At708, the UE device transmits data corresponding to the service type indicated by the first information received at702to an RU device operated by the host network operator using the bandwidth part indicated by the information received from the device operated by the guest network operator at706. For example, the system information received at702includes first information that indicates an SST value of 1, which corresponds to an eMBB slice/service type, and the UE device110-2operated by the subscriber of the first guest network operator transmits eMBB data to the RU device102operated by the host network operator using the bandwidth part indicated by the information indicating the bandwidth part received from the CU device108-2operated by the first guest network operator (e.g., bandwidth part BW1shown inFIG.2). The method700then ends.

FIG.8illustrates a logical flow diagram showing an example of a method800of operating a RU device in accordance with embodiments described herein. The method800begins at802.

At802, the RU device transmits system information including first information that indicates a plurality of network slices, second information that indicates a plurality of Physical Random Access Channel (PRACH) occasions mapped to the network slices, and third information that indicates ranges of one or more Slice Differentiator (SD) values (i.e., SD ranges) associated with the network slice. For example, the RU device102operated by the host network operator transmits system information including first information that indicates a plurality of SST values (e.g., 1, 2, 3) corresponding to a plurality of slice service types (e.g., eMBB, URLLC, MIoT) for the network slices, second information that indicates a plurality of PRACH occasions (e.g., information that indicates PRACH occasions 2, 3, 4), and third information that indicates a plurality of SD ranges (e.g., 000000000000000000000101-000000000000000000001001, 000000000000000000001010-000000000000000000001110, 000000000000000000001111-000000000000000000010011). The method800then proceeds to804.

At804, the RU device receives a RACH preamble during one of the PRACH occasions indicated by the second information transmitted at802. For example, the RU device102operated by the host network operator receives a preamble of the RACH114-2shown inFIG.2during the second PRACH occasion112-2shown inFIG.2from the UE device110-2operated by the subscriber of the first guest network operator. The method800then proceeds to806.

At806, the RU device determines a network operator based on the PRACH occasion during which the RACH preamble is received at804. For example, the RU device102uses the network slice information300shown inFIG.3to determine that the network operator corresponding to the RACH114-2is the first guest network operator (e.g., Guest Operator1) based on the preamble of the RACH114-2being received during PRACH occasion2(e.g., the second PRACH occasion112-2shown inFIG.2). The method800then proceeds to808.

At808, the RU device transmits the preamble of the RACH received at804and information included in the RACH received at804to a DU device operated by the network operator determined at806. For example, the RU device102stores an Internet Protocol (IP) address in association with an identifier of the first guest network operator (e.g., Guest Operator1) and uses that IP address to route the preamble of the RACH114-2and information included in the RACH114-2to the DU device106-2operated by the first guest network operator and/or the CU device108-2operated by the first guest network operator. The method800then proceeds to810.

At810, a device operated by the guest network operator transmits information that indicates a bandwidth part to the UE device. For example, after the UE device110-2operated by the subscriber of the first guest network operator has been successfully authenticated, and Radio Resource Control (RRC) and Non-Access-Stratum (NAS) have been established between the UE device110-2and the CU device108-2operated by the first guest network operator and a device operated by the first guest network operator that performs an Access and Mobility Management Function (AMF), respectively, the CU device108-2transmits information that indicates a contiguous set of Physical Resource Blocks (PRBs) on a particular carrier frequency (e.g., bandwidth part BW1shown inFIG.2) to the UE device110-2. The method800then proceeds to812.

At812, the RU device receives data of a type corresponding to the one of the network slices indicated by first information transmitted by the UE device using the bandwidth part. For example, the RU device102receives eMBB data that is transmitted by the UE device110-2using the bandwidth part BW1shown inFIG.2. The method800then proceeds to814.

At814, the RU device transmits the data received at812to the DU device operated by guest network operator. For example, the RU device102transmits the eMBB data received at812to the DU device106-2operated by the first guest network operator operated by the first guest network operator. In one or more implantations, the RU device102determines that the eMBB data is to be transmitted to the based on the bandwidth part (e.g., bandwidth part BW1shown inFIG.2), using the network slice information300shown inFIG.3. The method800then ends.